6 - Procedure Model Flashcards
Maintenance Tasks
Error Correction + New Features + Testing for new testcases
Commonly Used Procedure Models
V-Model (XT) + Rational Unified Process (RUP) + Extreme Programming (XP) + SCRUM
Procedure Structure
development process + tasks + activities and schedule
Agile Approach is characterized by a low ____________; less ____________ and focuses on ____________.
bureaucracy/documentation/code and test
Scrum Process
Sprint Kick-Off - Sprint (30 days) - Daily Scrum (Short Meeting) - Review - Retrospective
Ways to assure quality
Formal Reviews (documents/processes) + Automated Tests (system elements) + Manual Tests
Organization Structure Model/Role Model
team structure & responsibilities
Parts of Procedure Model
Product Model (WHAT?) + Activity Model (HOW?) + Role Model (WHO?) + Process Model (WHEN?)
What can be a Work Product?
Protocols + Drafts + Reports + System Descriptions + SW/HW + Prototypes
Artifact Model
structure and relation of work products (artifacts)
Product Configuration
characterizes a set of product instances with version number + processing status
Incremental Approach
System developed in expansion stages + incremental process and expansion. PRO: high flexibility // CON: difficult decision structure
Activity Structure Model
description of activities and relationships
Project Stages
Requirements Specification - Design - Implementation - Test & Integration - Testing & Commissioning - Further Development
POM
Project Organization and Management: Organization (domain knowledge + definition of roles & responsibilities) + Management (Cost Planning/Controlling)
Agile Manifesto
individuals & interactions > processes & tools // working software > comprehensive documentation // customer collaboration > contract negotiation // change request > plans
Tool Structure Model
describe system development tools and their coupling
PROs & CONs of the Waterfall Model
Activity Orientation & Heavyweight. PRO: clear and defined procedural structure + easy planning // CON: error and change management not intended + not flexible + requirements have to be known
Name two different Development Approaches.
Top Down (System Decomposition) + Bottom Up (System Composition)
PROs & CONs of the V-Model
Extenison of Waterall. PRO: clear artifact and activity structure + easy planning // CON: error and change management not intended + not flexible
What can lead to change?
Errors + Missing/New Features + External Suppliers + Misunderstandings
Product Library
manages product instances
Spiral Model
Risk Oriented Model with various prototypes + Iterative: Repeated Execution of incremental development steps + not heavyweight/not agile
