volume_mute
System Boundary Definition Is Not Value-Free
publish date: 2026/06/08 03:53:20.437935 UTC
volume_mute
Which of the following are valid reasons why defining a system boundary is described as 'not a value-free judgment'? Select all that apply.
Correct Answer
(1) A boundary may be deliberately positioned so that the complete analysis process can be carried out on one site
(2) A boundary may be chosen so that a particularly difficult manager need not be consulted
(3) A boundary may be positioned to increase system cost so that the system development division must expand
(4) Social and organizational concerns may determine where the boundary is placed
Explanation
System boundary definition is not value-free because social and organizational concerns may determine where the boundary is placed. For example, it may be positioned to keep analysis on one site, to avoid involving a difficult manager, or to increase the system cost and scope to benefit a particular division. It is never purely a technical decision.
Reference
Software Engineering, Ian Sommerville, 9th edition