IS556ProjectManagement课件.pptVIP

IS 556 Fall 2003 Copyright 2003 Thomas Muscarello IS 556 Project Management Week 9 HOW TO HANDLE LARGE PROJECTS: Divide and Conquer Readings: On Time Within Budget - Ch.6 No presnter groupDL Group [Group 9 DL -BankIreland (DL)]?Medisys Health Group - Group [Group 8 (DL) Medisys (DL) ]DL Group 8 - local Group [group 13 DL Only - Medisys]Presenter Group [Group 10 - Eclectic - Medisys] Objectives Requirements/Design Issues Stepwise refinement Functional Decomposition Design Decomposition Task Decomposition Component based development Large Software Projects Large Software Projects have extra challenges. Many tasks to coordinate and track How do you break apart the overall project into smaller pieces? Are their pieces that can be reused? Stepwise Refinement Not possible to figure out all task at once Use and iterative method to refine each iteration Increasing level of detail Not hierarchical components Not hierarchical calling relationship between higher and lower level modules Grouping items by logical order Coding modules exist at lowest level of detail More on Hierarchy Charts System decomposition and hierarchal chart Functional Decomposition Decomposition into operational component as seen by user Part of requirements phase Objective is to define system’s functional characteristics as seen by user. Describe major functional operations of black box but nothing inside black box. E.g., A function diagram for a bank ATM system Might include ability to update account information from central computer to ATM Would not include communication method and/or protocol (this is an internal Automatic Teller System:Functional Decomposition Diagram 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 a