Presentation is loading. Please wait.

Presentation is loading. Please wait.

SE 470 Software Development Processes James Nowotarski 2 June 2003.

Similar presentations


Presentation on theme: "SE 470 Software Development Processes James Nowotarski 2 June 2003."— Presentation transcript:

1 SE 470 Software Development Processes James Nowotarski 2 June 2003

2 Course Map Overview. Introduction. History Content. Rational Unified Process. Extreme Programming Implementation. Tools, Training, Roles. CMM, Metrics. Selection & Evaluation Briefings (Term Papers) 1234678910115 Assignments Quizzes Week Memorial Day

3 Topic Duration Quiz #410 minutes Assignment 4 Recap15 minutes Term Paper Presentation #135 minutes *** Break15 minutes Term Paper Presentation #235 minutes Term Paper Presentation #335 minutes Housekeeping/Wrap-up?? minutes Today’s agenda

4 Topic Duration Quiz #410 minutes Assignment 4 Recap15 minutes Term Paper Presentation #135 minutes *** Break15 minutes Term Paper Presentation #235 minutes Term Paper Presentation #335 minutes Housekeeping/Wrap-up?? minutes Today’s agenda

5 Topic Duration Quiz #410 minutes Assignment 4 Recap15 minutes Term Paper Presentation #135 minutes *** Break15 minutes Term Paper Presentation #235 minutes Term Paper Presentation #335 minutes Housekeeping/Wrap-up?? minutes Today’s agenda

6 Assignment 4 - Medco Breadth GradeB Observations+Addresses (in varying levels of detail) the major phases of the development life cycle: Analysis Design Development Testing Deployment Maintenance +At least mentions project management activities (misnamed “Project Plan”), though no further detail is provided -Does not address: Architecture Conversion planning, preparation, or execution Development environment Various facets of project management (e.g., risk management) QA

7 Assignment 4 - Medco Depth GradeD Observations+Provides high-level view of the process + Includes rudimentary deliverable flow -Need 1-2 additional levels of detail to ensure common understanding. Too much is left to interpretation. -Other than rectangle, no further detail on project planning/mgmt. In particular, more needed on how multiple releases will be managed simultaneously

8 Assignment 4 - Medco Alignment with Best Practices GradeC Observations+Addresses (to some extent) the following best practices: Iterative development Visual modeling Reviews Testing User involvement Deployment -Does not address: Architecture Component-based development Requirements management Change control

9 Assignment 4 - Medco Conceptual Integrity GradeA Observations+No major inconsistencies found + Process is basically vanilla structured analysis/design (proven, well understood), limits exposure to integrity issues -When there is not much depth, it is relatively easy to maintain conceptual integrity

10 Assignment 4 - Medco Fit with Project and Organization GradeF Observations+Process is at least documented, which it had not been before -This is a complex, mission-critical system; this methodology is far too sketchy for a project of this magnitude - Reliance on outside contractors makes it even more important to have a better document process -Intricacies of delivering releases every 2 months need to be planned out in further detail -This process seems to reflect an informal, entrepreneurial culture; but organization is growing/maturing and needs “methodology for grown-ups” -- the stakes are higher

11 Assignment 4 - Medco Summary Grade and Recommendations GradeD RecommendationsConsider replacing data flow diagrams with use cases Provide additional detail for existing coverage areas – Possibly use outside contractor/consultant Add coverage for key areas: – Project management – Development environment – Architecture – Conversion – QA process Ensure project team is trained on the methodology

12 Topic Duration Quiz #410 minutes Assignment 4 Recap15 minutes Term Paper Presentation #135 minutes *** Break15 minutes Term Paper Presentation #235 minutes Term Paper Presentation #335 minutes Housekeeping/Wrap-up?? minutes Today’s agenda

13 Extra Slides

14 CMM Levels Repeatable (2) Repeatable (2) Defined (3) Defined (3) Managed (4) Managed (4) Optimized (5) Optimized (5) Initial (1)

15 Key process areas (KPAs) Maturity levels Process capability Indicate Key process areas Contain Key practices Contain Goals Achieve

16 Appraisal Methods Software Process Assessments (SPA) –Performed in open, collaborative environment –Focuses on improving the organization’s software process –Now called CMM-Based Appraisal for Internal Process Improvement (CBA-IPI) Software Capability Evaluations (SCE) –Performed in a more audit-oriented environment –Focuses on identifying risks associated with a contractor –Team’s recommendation will help select contractors or set fees

17 CMM Issues in the Real-World “Level envy” Areas not addressed –Business strategy and linkage to IT –Operations, help desk, support –Management of the IT human resource –Application portfolio –Tools –Risk Many question whether it is worth the effort to pursue levels 4 and 5

18 CMM Maturity Profile 10% 20% 30% 40% 50% 60% 70% 80% 90% 100% 0% Initial 19.3% Repeatable 43.2% Defined 23.4% Managed 7.3% Optimized 6.8% % of Organizations August 2002 Based on assessments from 1998-2002 of 1124 organizations

19 Time to Move Up 100 0 75 50 25 1 to 2 23 22 2 to 3 28 3 to 4 17 4 to 5 Largest observed value that is not an outlier 75th percentile Median (50th percentile) 25th percentile Smallest observed value that is not an outlier Recommended time between appraisals (18-30 mos) Number of months to move to next maturity level


Download ppt "SE 470 Software Development Processes James Nowotarski 2 June 2003."

Similar presentations


Ads by Google