1. CIS 4251 / CIS 5930 SOFTWARE DEVELOPMENT Fall 1999 Sept. 1, 1999 Marge Holtsinger

2. Lecture Overview 4 Review of Previous Discussion 4 Project Management 4 Project Metrics 4 Project Planning

3. Software Engineering 4 “Establishment & use of sound engineering principles in order to obtain economically software that is reliable and works efficiently on real machines.” 4 “Application of a systematic, disciplined, quantifiable approach to the development, operation, & maintenance of software; that is, the application of engineering to software.

4. Layered Approach Quality Process Methods Tools TQM Framework How Tos Case, Use, etc.

5. Spiral Model 4 Evolutionary process that combines iterative nature of prototyping with controlled & systematic aspects of the linear sequential model 4 Software is developed in a series of incremental releases

6. 90-90 Rule 4 The first 90% of a system absorbs 90 % of the allocated effort and time. 4 The last 10% takes the other 90% of the allocated effort and time.

7. 3 P’s of Effective Project Mgmt 4 People –Resource Management 4 Problem –Vision / Scope –Problem Decomposition 4 Process –Match the problem to the process

8. People 4 Recruiting 4 Selection 4 Performance Management 4 Training / Career Development 4 Compensation 4 Organization and Work Design

9. Who Are the Players? 4 Senior Management 4 Project (technical) Managers 4 Practitioners 4 Customers 4 End Users

10. Team Leader Must Be Able To 4 Motivate 4 Organize 4 Encourage people to be creative 4 Problem solve 4 Take control when necessary 4 Reward initiative and accomplishments 4 Encourage team building

11. Problem 4 Vision - represents the unbounded view of what the product can do for its users; –Business Problem –How business will change with new solution –Business context of the solution –Establishes long term vision of the product

12. Problem 4 Scope –Incorporates the vision mapped against reality –Identifies priorities; what the customer deems as essential for success –Describes functions, performance, constraints, interfaces, reliability –Obtained by preliminary customer interviews; Need enough information for a preliminary estimate.

13. Project Trade-off Matrix

14. Process 4 Melding of Problem and Process 4 Common Process Framework Activities –Customer Communication –Planning –Risk Analysis –Engineering 4 Project Proposal is the deliverable

15. Project Proposal 4 Vision Statement 4 Scope 4 Project Assumptions 4 Project Trade-off Matrix 4 Hardware / Software 4 Players –Team Roles & Responsibilities –Customer Profile

16. Software Project Planning 4 Estimating 4 Features and Priorities 4 Risk Assessment 4 Resources 4 Milestones and Deliverables

17. Software Project Estimation 4 Not an exact science 4 More accurate if delay estimation until late in the project 4 Base estimates on similar projects 4 Decomposition techniques to estimate effort & cost 4 Empirical models to estimate effort & cost

18. Decomposition Techniques 4 Software sizing –“Fuzzy-logic” sizing –Function point sizing –Standard component sizing –Change sizing

19. LOC Based Estimation 4 Major functions are identified 4 Range of values for LOC for each function are estimated 4 Must have historical data to determine productivity

20. FP-Based Estimation 4 Based on information domain values –Number of inputs –Number of outputs –Number of inquiries –Number of files –Number of external interfaces 4 Complexity factors are then determined

21. Process-Based Estimation 4 Estimate effort required for each software process / phase of the project –Vision/Scope –Project plan –Analysis –Design –Development

22. What Causes Poor Estimates 4 Scope of project not understood 4 Productivity data is incorrect

23. Empirical Estimation Models 4 Based on historical data on LOC and FP 4 Derived using regression analysis on data collected from past software projects –E=A+B*(ev) c A, B, & C are derived constants, E is the effort in person months, and ev is the estimation variable