IS-556-Project-Management培训课件.pptVIP

Automatic Teller System:Functional Decomposition Diagram Even though this component is on the “grey” edge of being design info, it is included here Functional decomposition of large systems Sometimes functional decomposition is not clear A large inventory system might functionally include human interface, database, report generator, Update logic Might not functionally include human interface as high level Since above leaves out important functions such as fail-over backup Functional decomposition should create foundation for design decomposition A functional decomposition team may meet to define and select alternatives A good functional decomposition is selected based upon: Reason (logical to divide a certain way) Ease of implementation (lead to a good design) Should mirror structured program (modules, independence, etc.) Comprehensiveness (everything covered) Design Decomposition Division into lower level components that coincide with software modules is usually done after functional decomposition Done in a stepwise fashion Best used as a method for providing increasing detail For example, might decide main functional components of ATM system are The automatic teller terminal The main computer The computer network A Design Decomposition of ATM These may correspond to actual software modules These are category names (may become susbsystem names). There is not one module that represents each of these but a set developed at the lower levels. A fully decomposed design diagram There can be huge sets of modules at lowest levels. If had to review design using only the lowest level modules could be very difficult to understand and grasp system Might be the high level design. Might review this separately Design Decomposition Good design is basis for software structure Software Engineering has lots to say about design decomposition Independent software components Simple interfaces (minimize coupling) Information hiding Produce modules that hide their design and