1. The Software Engineering Process
Discussion Slides

2. Why is an SE Process Important?
Organizes Development
Adds Stability to Course of Actions
Defines Controls for Managing Effort
Makes Status “Visible”
Communicates Vision and Actions to Team and Stakeholders

3. The Software Process
Process Framework: A structure applicable to all processes
Communication, Planning, Modeling, Construction, and Deployment
Umbrella Activities: Activities (tasks) which are applicable (or span) the entire process
Project Tracking and Control, Risk Management, Quality Assurance, and Configuration Management (others pg 26 6/e) – Not emphasized in 7/e

4. Additional Points of Emphasis
Task set for the communication phase of a project (pg 34 7/e, 25 6/e)
Required elements of the PMP
Project Context:
Project description from customer, user, & developer viewpoints
References of resources and stakeholders
Team structure and role/responsibility assignments
Selection of S/W engineering process
Anticipated list of deliverables: docs, software, DBs, & other files
Project Plan (schedule)
Use Gantt chart form
Risk Evaluation
Quality Assurance statement
Configuration Management statement