Ch04 – Process Models

  1. originally proposed to bring order to the chaos of software development.
    Process models
  2. a natural state between order and chaos, a grand compromise between structure and surprise.
    Edge of chaos
  3. absence of variability which could be an advantage under unpredictable environments.
    Absolute order
  4. strives for structure and order in software development.
    Prescriptive process model
  5. prescribes a process flow (work flow) -that is the manner in which the process elements are interrelated to one another.
    Process model
  6. oldest paradigm for software engineering. When requirements are well-defined and reasonably stable, it leads to a linear fashion.
    Waterfall model
  7. sometimes called the classic life cycle, suggests a systematic sequential approach to software development.
    Waterfall model
  8. a variation of waterfall model that depicts the relationship of quality assurance actions associated with communication, modeling and early construction activities.
    V-model
  9. combines the elements’ linear and parallel process model that is designed to produce the software in increments.
    Incremental model
  10. When an incremental model is used, the first increment is often a ________.
    core product
  11. basic requirements are addressed but many supplementary features remain undelivered.
    Core product
  12. iterative, characterized in a manner that enables you to develop increasingly more complete versions of the software.
    Evolutionary model
  13. customer defines a set of general objectives for software, but does not identify detailed requirements for functions and features.
    Prototyping
  14. assists you and the stakeholders to better understand what is to be built when the requirements are fuzzy.
    Prototyping
  15. serves as a mechanism for identifying software requirements or can serve as ‘the first system’.
    Prototyping
  16. an evolutionary software process model that couples the iterative nature of prototyping with the controlled and systematic aspects of the waterfall model.
    Spiral model
  17. a risk driven process model generator that is used to guide multi-stakeholder concurrent engineering of software intensive systems.
    Spiral model
  18. The Spiral model is ______ for incrementally growing a system’s degree of definition and implementation while decreasing its degree of risk.
    cyclic
  19. The Spiral model is a set of ____________ for ensuring stakeholder commitment to feasible and mutually satisfactory system solutions.
    anchor point milestones
  20. a combination of work products and conditions that are attained along the path of the spiral – are noted for each evolutionary pass.
    Anchor point milestones
  21. allows a software team to represent iterative and concurrent elements of any of the process models.
    Concurrent development model
  22. defines a series of events that will trigger transitions state to state for each of the software engineering activities, actions or tasks.
    Concurrent modeling
  23. (T/F) Concurrent modeling is applicable to all types of software development and provides an accurate picture of the current state of a project.
    True
  24. (T/F) The spiral model is a realistic approach to the development of large-scale systems and software.
    True
  25. Have been developed to help software organizations analyze their current process, organize work tasks, control and monitor progress, and manage technical quality.
    Process technology tools
  26. allow a software organization to build an automated model of the process framework, task sets, and umbrella activities.
    Process technology tools
Author
FelipeJung
ID
327465
Card Set
Ch04 – Process Models
Description
2nd Semester
Updated