IN4MATX 43 Chapter Notes - Chapter Reading 17: Spiral Model, Software Feature, Software Engineering
2 Jun 2018
School
Department
Course
Professor
IN4MATX – 36900 – Intro to Software Engineering
Week 8 – Reading 17 – 4.1, 4.2
4 – Software Process Models
4.1 – Software Processes
• Software engineers tend to not follow systematic processes when performing
tasks with their own experience or background
o Makes for inconsistent projects, longer times and poor ends
4.1.1 – The Goal of Software Process Models
• Goal of software process models is to provide guidance for systematically
coordinating and controlling tasks performed in order
• Process model defines:
o A set of tasks that need to be performed
o The input to and output from each task
o The preconditions and postconditions for each task
o The sequence and flow of these tasks
• Is software development process necessary for a one-man project?
o Depends
4.2.1 – The ‘Simplest’ Process Model
• Code-compile-unit test cycle
o Because coding is usually central to this task, model is known as code-
and-fix model
o Problem statement – requirements specifications
o Testing – unit testing usually performed
o Problems
▪ Problem statement being incomplete, leading to the incomplete
testing as well
• Simple process model
o Served many early projects
o Tasks like design and integration were introduced with complexity
increase
o Better coordination was required
• There is no one process model to fit all software projects
4.2 – Traditional Process Models
4.2.1 – Waterfall Model
• Oldest publicized model
• Referred to as classic software life cycle model
• Name reference
find more resources at oneclass.com
find more resources at oneclass.com
Document Summary
In4matx 36900 intro to software engineering. Week 8 reading 17 4. 1, 4. 2. 4. 1 software processes: software engineers tend to not follow systematic processes when performing tasks with their own experience or background, makes for inconsistent projects, longer times and poor ends. Is software development process necessary for a one-man project: depends. Almost complete": positive aspects of waterfall model, requirements must be specified in first steps, four main tasks must be completed before software can be packaged for release, requirements, design, test. Incremental model: something akin to evolutionary software product development. 4. 2. 4 spiral model: derived from concerns with document-driven approach (waterfall, based on experiences with large gov. software projects. Integral parts: review of all activities and products completed in cycle by major stakeholders, ensure all parties are committed and agree on approach for the next phase, spiral model is based on risk reduction through iteration, convenient features.
