Software Engineering Ch 4
Waterfall Model
(classic life cycle - old fashioned but reasonable approach when requirements are well understood)
Concurrent Development Model
(concurrent engineering - allows software teams to represent the iterative and concurrent element of any process model)
Incremental Models
(deliver software in small but usable pieces, each piece builds on pieces already delivered)
Specialized Process Models
• Component-Based Development (spiral model variation in which applications are built from prepackaged software components called classes) • Formal Methods Model (rigorous mathematical notation used to specify, design, and verify computer-based systems) • Aspect-Oriented Software Development (aspect-oriented programming - provides a process for defining, specifying, designing, and constructing software aspects like user interfaces, security, and memory management that impact many parts of the system being developed)
Personal Software Process (PSP)
• Emphasizes personal measurement of both work products and the quality of the work products • Stresses importance of indentifying errors early and to understand the types of errors likely to be made
Unified Process
• Use-case driven, architecture centric, iterative, and incremental software process • Attempts to draw on best features of traditional software process models and implements many features of agile software development
Process Technology Tools
• Used to adapt process models to be used by software project team • Allow organizations to build automated models of common process framework, task sets, and umbrella activities • These automated models can be used to determine workflow and examine alternative process structures • Tools can be used to allocate, monitor, and even control all software engineering tasks defined as part of the process model
Software Process Models
• Waterfall Model • Incremental Models • Evolutionary Models o Prototyping Model o Spiral Model • Concurrent Development Model
Team Software Process Objectives
o Build self-directed teams that own their processes and plans o Show managers how to coach and motivate their teams o Accelerate software process improvement by making CCM Level 5 behavior normal and expected o Provide improvement guidance to high-maturity organizations o Facilitate university teaching of industrial team skills
Unified Process Phases
o Inception phase (customer communication and planning) o Elaboration phase (communication and modeling) o Construction phase o Transition phase (customer delivery and feedback) o Production phase (software monitoring and support)
Personal Software Process (PSP) Framework activities
o Planning (size and resource estimates based on requirements) o High-level design (external specifications developed for components and component level design is created) o High-level design review (formal verification methods used to uncover design errors, metrics maintained for important tasks) o Development (component level design refined, code is generated, reviewed, compiled, and tested, metric maintained for important tasks and work results) o Postmortem (effectiveness of processes is determined using measures and metrics collected, results of analysis should provide guidance for modifying the process to improve its effectiveness)
Team Software Process Scripts for Project Activities
o Project launch o High Level Design o Implementation o Integration and system testing o Postmortem
Evolutionary Models
o Prototyping Model (good first step when customer has a legitimate need, but is clueless about the details, developer needs to resist pressure to extend a rough prototype into a production product) o Spiral Model (couples iterative nature of prototyping with the controlled and systematic aspects of the Waterfall Model)
