Third Hour Lecture1030 – 1120 am September 8.pptVIP

Third Hour Lecture10:30 – 11:20 am September 8 Improving Software Economics (continuing from Chapter 3 of Royce’ book) Five Economy ImprovementDimensions Reducing the size of the software. Improving the development process. Using more-skilled personnel and better teams. Using better environments (tools) for software development. Trading off, or backing off, on quality thresholds. Improving Software Development Processes Productive activity Prototyping Modeling Coding Debugging Documentation Overhead activity Plan preparation Documentation Progress monitoring Risk assessment Financial assessment Configuration control Quality assessment Integration Testing Late scrap and rework Management Training Administration Three Levels of Process Three Dimensions for Schedule Improvement In an N-step process, improve the efficiency of each step. In an N-step process, eliminate some steps to create an M-step process. In an N-step process use more currency in the activities. Sequential Steps Every instance of rework introduces a sequential set of tasks. Start with analysis, design, coding, and testing of a feature. Suppose then a fault is found. Then we must repeat the analysis, design, etc… These rework task sequences are the primary obstacle to schedule compression. Improving Team Effectiveness Four Team Management Maxims. Five Project Staffing Principles. Five Attributes of Successful Software Managers. Four Maxims of Team Management A well-managed project can succeed with a nominal engineering team. A mismanaged project will fail, even with an expert team. A well-architected system can built by a nominal team. A poorly-architected system will flounder even with an expert team. Five Attributes of Successful Software Project Managers Hiring skills. Right persons in the right jobs. Customer-interface skills. Avoiding adversarial relationships. Decision-making skills. Timely decisions, objective, unbiased and reasoned. Team-building skills. Trust, motivating, nurturi