1 / 28

Software Process Framework

Software Process Framework. Umbrella Activity. Software project management Formal technical reviews Software quality assurance Software configuration management Work product preparation and production Reusability management Measurement Risk management.

frankshields
Download Presentation

Software Process Framework

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Software Process Framework

  2. Umbrella Activity • Software project management • Formal technical reviews • Software quality assurance • Software configuration management • Work product preparation and production • Reusability management • Measurement • Risk management

  3. Example of Task Set for Req. Gathering 1. Make a list of stakeholders for the project. 2. Invite all stakeholders to an informal meeting. 3. Ask each stakeholder to make a list of features & functions required. 4. Discuss requirements and build a final list. 5. Prioritize requirements. 6. Note areas of uncertainty.

  4. Software Process Definition: Software process is defined as framework for the activities , actions & task that are required to build high quality software

  5. Process Flow

  6. Process Flow

  7. Process Flow

  8. Process Flow

  9. Prescriptive Process Model • Definition: Prescribed set of process elements and a predictable process work flow is called as Prescriptive process model.

  10. 1. Waterfall Process Model

  11. Disadvantages of Waterfall Model • It is difficult to customer to state all requirements explicitly. • Working version of program is available late in Project time span • Linear model leads ‘Blocking state’ due to dependent task.

  12. V Model

  13. V- Model • Variation in representation of Waterfall model is called V model. • V Model Provides a way of visualizing how verification and validation actions are applied to engineering work.

  14. 3. Incremental Model (RAD)

  15. Incremental Model • Incremental model combines elements of linear and parallel process flow • First increment is “Core Product” • Useful when resources are not available for complete implementation • Eg. Word processing software • Basic Product is delivered with partial functionality without delay.

  16. 1. Prototyping

  17. Prototyping Continued… • Customer defines general set of objectives for software but does not identify detailed system requirement • Prototyping assist you & other stakeholder to better understand system when requirements are Fuzzy • Serve as mechanism of identifying software requirement

  18. 2. Spiral Model

  19. Spiral Model • Risk driven process model • Features • Cyclic in nature; incrementally growing system’s degree of implementation and decrease degree of risk. • Anchor point milestones are set for ensuring stakeholder commitment of system solution. • Increasingly more complete version of engineered system is produced. • Remains operative until software is retired.

  20. Concurrent Process Model

  21. Concurrent Process Model • Also called Concurrent engineering. • All software engg. Activities exist concurrently but resides in different state.

  22. Advance Process Models1. Unified Process

  23. 2. Extreme ProgrammingXP Process

  24. XP Values • Communication: avoid voluminous documentation. 2. Simplicity XP restricts developers to design only for immediate needs rather than future needs 3. Feedback s/w, customer, other team members 4. Courage Demanding rework of the design and code. 5. Respect

  25. XP Stories developed in 3 ways 1.All stories will be implemented immediately (within a few weeks), 2.Stories with highest value will be moved up in the schedule and implemented first, or 3. High Risk stories will be moved up

  26. User stories implemented are used as basis for acceptance test • Issues Raised by XP • Requirements volatility • Conflicting customer needs • Requirements are expressed informally

  27. Class Responsibility Collaborator

  28. CRC Example

More Related