Which of the following factors is taken into account when we develop a…

Concept: A Knowledge Management System (KMS) is an organizational information system built to capture, store, and share both explicit and tacit knowledge across an organization. Because organizational knowledge is a shared resource rather than any one employee's private property, one factor that must be settled before building a KMS is a knowledge contract: a formal understanding of who owns contributed knowledge, how it may be reused, and how contributors are recognised.

Application: Checking what each option claims against this design factor:

• It requires a knowledge contract - organisations formalise ownership and sharing terms as part of designing a KMS, since contributed knowledge needs agreed rules on use and attribution.

• It is a cheap management system - a KMS demands real spend on repositories, collaboration platforms, and staff training, so cost is a genuine planning factor.

• It is a definite process - tacit knowledge is hard to codify into one fixed procedure, so KM activity stays iterative and evolves rather than following a single set procedure.

• It has no human implications - employee willingness to share expertise and the organisation's culture directly decide whether knowledge gets captured at all, so human behaviour plays a central role.

Cross-check: The knowledge-contract requirement is the factor genuinely built into KMS design practice; real infrastructure and training cost, an evolving rather than fixed process, and a strong dependence on human behaviour are the documented characteristics that the other three claims each contradict.