60 likes | 193 Views
Software Management Van Vliet C-2. Dr. Riggs Fall 2004. Systems View of Sftwr Dvlp. Information planning. Boundary conditions. documentation. people. software. input. output. program. program. procedures. Non-technical Reasons for Failure. Programmers avoid real code status
E N D
Software ManagementVan Vliet C-2 Dr. Riggs Fall 2004
Systems View of Sftwr Dvlp Information planning Boundary conditions documentation people software input output program program procedures Riggs -Operating Systems
Non-technical Reasons for Failure • Programmers avoid real code status • Management underestimate time • Planning time not given • Project status unclear • Productivity over estimated • Customer did not know what he wanted Riggs -Operating Systems
Project Plan Elements (I) • Introduction: goals, deliverables, summary • Process model: model and milestones • Organization: relations in project and without • Standards, procedures: documentation • Management: reports and balance • Risks: what can go wrong? what will it cost? • Staffing: Riggs -Operating Systems
Project Plan Elements (II) • Methods and Techniques: req, dsgn, code , test • Quality Assurance: organization & procedures • Work Packages • Resources: hardware, tools • Budget & Schedule • Changes: procedure, cost estimation • Delivery Riggs -Operating Systems
Axes of Control • Time • Information • Organization • Quality • Money Riggs -Operating Systems