This preview shows pages 1–2. Sign up to view the full content.
This preview has intentionally blurred sections. Sign up to view the full version.View Full Document
Unformatted text preview: 1 Development process models z The classic One step leads to another No going back z Software engineering in action Requirements Analysis System Design Program Design Coding Testing (several steps) Operation & Maintenance The Waterfall Model Software development activities z Note activities not steps z Often happening simultaneously z Not necessarily discrete 1. Planning: mostly study the requirements 2. Domain analysis: study the problem area 3. System design: devise the computer solution 4. Implementation: the easy step? 5. Testing, documentation, maintenance, Alternatives to waterfall model z Okay, we all agree this extreme doesnt work either z Is there a middle ground? Requirements Analysis System Design Unit Testing Software Development Reality Integration Testing Maintenance Delivery System Testing Coding Program Design Risk another reality In a waterfall lifecycle, high risk issues such as integration and load test may be tackled late. Time Potential impact of risks being tackled Requirements Analysis Design Implement Integrate & System Test z Considered wise to tackle risky issues early Engineering the risk factor z Spiral Model Includes frequent risk analyses Frequent reevaluation during an extended planning stage Testing and iterating z Because we make mistakes z Requirements change too Clients dont always know...
View Full Document
- Winter '08