1. Chapter 2 Generic View of process

2. Overview of Generic Process What? A Software Process-a series of predictable steps that lead to a timely, high quality product Who? Managers, Software Engineers and Customers Why? provides stability, control and organization to an otherwise activity Work Product?Programs,Data and Documents

3. Chapter 2 A Generic View of Process Software Engineering- A layered technology, A process framework The Capability Maturity Model Integration (CMMI) Process Patterns Process Assessment Chapter 2 Topics

4. Introduction Software is a logical rather than a physical system element. Characteristic-1: Software is developed or engineered, it is not manufactured in the classical sense. Characteristic-2: Software doesn't "wear out". Characteristic-3: Although the industry is moving toward component-based assembly, most software continues to be custom built.

5. What is Software Engineering The seminal definition: – [Software engineering is] the establishment and use of sound engineering principles to obtain software with better quality possible with in the estimated budget and the stipulated time.

6. Goal of Software Engineering Goal of Software Engineering is: The software produce high quality software at low cost

7. Software Engineering: A Layered Technology

8. Process: a collection of work activities, actions and tasks reside within a frame work or a model Methods: Provide the technical "how to" for building software; rely on a set of basic principles; encompass a broad array of tasks; include modeling activities Tools: Provide automated or semi-automated support for the process and methods (i.e., CASE tools)

9. A Process Framework A common process framework is established by defining a small number of framework activities that are applicable to all software projects, regardless of their size or complexity. Umbrella activities are independent of any one framework activity and occur through out the process. A number of task sets—each a collection of software engineering work tasks, project milestones, work products, and quality assurance points— enable the framework activities to be adapted to the characteristics of the software project and the requirements of the project team. Finally, umbrella activities—such as software quality assurance, software configuration management, and measurement—overlay the process model.

10. A Process Framework

11. Generic Process Framework Applicable to almost all software projects Communication Planning Modelling Construction (coding & testing) Deployment

12. The Capability Maturity Model Integration(CMMI) Capability Maturity Model Integration (CMMI) is a process improvement approach that helps organizations improve their performance. CMMI can be used to guide process improvement across a project, a division, or an entire organization. CMMI in software engineering and organizational development is a process improvement approach that provides organization with the essential elements for effective process improvement. CMMI is registered in the U.S. Patent and Trademark Office by Carnegie Mellon University.

13. The Capability Maturity Model Integration(CMMI)

14. Level 1: Initial : The process area is either or not performed or the goals not achieved Level 2: Manageable : All level 1 criteria have been satisfied. In addition all work associated with the process are confined to organizational defined policy Level 3: Defined: All level 1 criteria have been satisfied. In addition, the process is tailored from the organisation set of standard processes

15. The Capability Maturity Model Integration(CMMI) Level 4: Quantitatively Managed :All level 3 criteria have been satisfied. In addition, the process area is controlled and improved using measurement and quantitative measurement. Level 5: Optimizing. All level 4 criteria have been satisfied. In addition, the process area is adapted and optimized using quantitative measurement to meet change in customer needs.

16. Process Pattern Process patterns define a set of activities, actions, work tasks, work products and related behaviors that must be done to complete the project. In general process pattern defines a template Template for defining a process pattern: (by Ambler): -Pattern name : The pattern is provided with a meaningful name to describe the function in software process (E.g.: Customer communication) -Type: The type of pattern 1.Task pattern : Defines a software engineering action or work task 2.Stage pattern : Defines a framework activity for the process 3.Phase pattern : Defines the sequence of framework activities that occur with the process - Initial Context : Conditions initialized before applying to the pattern

17. Process Assessment A software process assessment is a disciplined examination of the software processes used by an organization, based on a process model. The assessment includes the identification and characterization of current practices, identifying areas of strengths and weaknesses, and the ability of current practices to control or avoid significant causes of poor (software) quality, cost, and schedule.

18. A software Assessment Kinds A self-assessment (first-party assessment) is performed internally by an organization's own personnel. A second-party assessment is performed by an external assessment team or the organization is assessed by a customer. A third-party assessment is performed by an external party or (e.g., a supplier being assessed by a third party to verify its ability to enter contracts with a customer).

19. Software Process Assessment Cycle According to Paulk and colleagues (1995), the CMM-based assessment approach uses a six-step cycle. They are − Select a team - The members of the team should be professionals knowledgeable in software engineering and management. The representatives of the site to be appraised complete the standard process maturity questionnaire. The assessment team performs an analysis of the questionnaire responses and identifies the areas that warrant further exploration according to the CMM key process areas. The assessment team conducts a site visit to gain an understanding of the software process followed by the site. The assessment team produces a list of findings that identifies the strengths and weakness of the organization's software process. The assessment team prepares a Key Process Area (KPA) profile analysis and presents the results to the appropriate audience.

20. Any Queries Mail Id:nelapatipraveen@gmail.com