Software Engineering Process Models Models for Guiding the Development of Software

The Software Process Framework Process Framework: A structure applicable to all processes Framework Activities Communication, Planning, Modeling, Construction, and Deployment (see pg 31 7/e, 24 6/e for definitions) Umbrella Activities: Activities (tasks) which are applicable (or span) the entire process Estimation, Scheduling, Tracking and Control, Risk Management, Quality Assurance, and Configuration Management

Waterfall Model AKA: Linear Sequential or Classic Life-Cycle Uses: Clear requirements, traditionally applied in government, 6/e has much weaker endorsement than earlier Distinctives: Early model for SE Variation: V-Model to recognize testing Communication Planning Modeling Construct Deployment analysis design code test project initiation requirement anal. estimating scheduling tracking delivery support feedback

Incremental Model A recommended model for CS4810/EGCP4810 Distinctives: First increment core product Remaining increments add function

Spiral Model Evolutionary Model Distinctives: The “product” of each cycle more finely grained Adaptable to each life-cycle phase

Unified Process Model A recommended model for CS4810/EGCP4810 Similar to the incremental model with OO emphasis (cycles are also “pipelined”) Provides structure and notation (UML) which assists in organization and communication Modeled w/ Use Cases and/or Usage Scenarios or Stories Models system architecture and objects from user and developer perspectives

Additional Points of Emphasis Other Development Models Rapid Application Development (Incremental) Prototyping (Evolutionary) Differing opinions on the purpose of the prototype (pgs /e, /e) Most important products of the unified process: Project plan Initial use-case model Software architecture description Expanded project plan (milestones and work products) Design model Software increments Test plan results and user feedback