Defining subsystems by using FD can lead to poor architectural concepts FD alone cannot be used to determine whether the subsystems will provide common functionalities that could be used across many requirements. Using functional decomposition /allocation to create architecture, can produce subsystems with duplicate functionality Designing subsystems with duplicate functionalities will create unnecessarily large and complex systems The logical functional decomposition enables – Realization that multiple system functions/requirements can be met by each component or subsystem – Formulation of alternate functional concepts; e. g. utilizing subsystems interactions to meet several system requirements Subsystems should, ideally, provide services in a "one- to-many, many-to-one" relationship: – One system requirement can be decompose into many subsystem requirements – One subsystem requirement may be derived from many system requirements – The approach to subsystems service definition is a form of functional decomposition (determining subsystems first, and then deriving their requirements)
Page:
29
Related
Batch download
Cited By
noting
Similar Literature
Submit Feedback
Please wait while the file you selected is being converted