ITIS 6112 Intro to Software Process Models

STUDY
PLAY

Terms in this set (...)

LINEAR SEQUENTIAL SOFTWARE PROCESS MODEL
The Warerfall Model is formally known as the ______________?
The Waterfall Model is a DESIGN APPROACH where PROGRESS FLOWS in ONE DIRECTION through a series of development phases.
What is the Waterfall Model and how does it work?
NO. With the Waterfall Model of once a phase of development is completed, the development process proceeds to the next phase and there is NO TURNING BACK.
When using the Waterfall Model, as a developer can you revisit previous areas of development?
The Waterfall Model is the most widely used SOFTWARE PROCESS MODEL.
A PRO of the Waterfall Model is the most widely used _____________ model.
The Waterfall Model follows a NATURAL, LOGICAL PROGRESSION.
An additional PRO of the Waterfall Model is that it follows this kind of progression?
(+) Popularity, the Waterfall Model is the most widely used SOFTWARE PROCESS MODEL.
(+) The Waterfall Model follows a NATURAL, LOGICAL PROGRESSION.
State the PROS of the Waterfall Model:
A CON of the Waterfall Model is that it provides NO OPPORTUNITY for ITERATION or FEEDBACK.
A CON or drawback of the Waterfall Method is that it provides no opportunity for _____________ or _____________?
Magnified Risks is stated as an additional CON of the Waterfall Method because when using Waterfall it takes a LONG TIME to get the PRODUCT into the CUSTOMERS HANDS.
Explain why is "Magnified Risks" is stated as an additional CON of the Waterfall Method?
A Prototype Model is a design approach in which a PROTOTYPE is BUILT, TESTED and REWORKED until a final prototype is selected to build the complete system from.
In the context of Software Design, what is a Prototype Model?
A Prototype Model works best in scenarios where NOT ALL PROJECT REQUIREMENTS are known IN DETAIL ahead of time.
In what scenario of Software Design does a Prototype Model work best?
A PRO of a Prototype Model is that it provides EARLY and FREQUENT CUSTOMER FEEDBACK.
A PRO of a Prototype Model is that it provides __________ and ____________ Customer Feedback.
An additional PRO of a Prototype Model is that it leads to MORE EFFECTIVE REQUIREMENTS GATHERING.
An additional PRO of a Prototype Model is that it leads to ______________?
(+) Early Customer Feedback
(+) Frequent Customer Feedback
(+) can lead to more effective REQUIREMENTS GATHERING
State the PROs of a Prototype Model:
A CON of a Prototype Model is that it has a PERCEPTION PROBLEM as well as NON-OPTIMAL CODING practices.
A CON of a Prototype Model is that it has a ______________ Problem as well as _________ Coding practices.
An additional CON of a Prototype Model is that DEVELOPERS often make DESIGN/IMPLEMENTATION COMPROMISES.
An additional CON of a Prototype Model is that developers often make ________/_________ compromises?
(-) Perception Problem
(-) Non-Optimal Coding Practices
(-) Developers often make DESIGN/IMPLEMENTATION COMPROMISES
State the CONs of a Prototype Model:
The FORMAL METHODS SOFTWARE MODEL is concerned with the APPLICATION OF MATH TO DESIGN AND IMPLEMENT SOFTWARE.
What is the Formal Methods Software Model concerned with?
A PRO about the Formal Designs Software Model is that SPECIFICATIONS HAVE LESS AMBIGUITY, and PROPERTIES ABOUT DESIGNS CAN BE PROVEN.
A PRO about the Formal Designs Software Model is that specifications have __________ ambiguity, and properties about designs can be __________?
An additional PRO about Formal Methods Software Models is that they INTRODUCE MORE RIGOR to the ENTIRE TESTING PROCESS.
An additional PRO about Formal Methods Software Models is that they introduce _________ rigor to the ________ testing process.
(+) Specifications have LESS AMBIGUITY
(+) PROPERTIES ABOUT DESIGNS can be PROVEN
(+) Introduces MORE RIGOR to the ENTIRE TESTING PROCESS
State the PROS of a Formal Methods Software Model:
A CON about Formal Methods Software Models are that they have a STEEP LEARNING CURVE, and contain UNINTUITIVE DESIGN.
A CON about Formal Methods Software Models is that they have a _________ learning curve, and contain _________ design.
An additional CON about Formal Methods Software Models is that they are EXPENSIVE AS HELL.
An additional CON about Formal Methods Software Models is that they are ________ as Hell.
(-) STEEP LEARNING CURVE
(-) UNINTUITIVE DESIGN
(-) EXPENSIVE AS HELL
State the CONS of a Formal Methods Software Model:
The Spiral Development Model is a RISK-DRIVEN PROCESS MODEL GENERATOR for SOFTWARE PROJECTS.
What is the Spiral Development Model?
A PRO of the Spiral Development Model is that it takes the ENTIRE SOFTWARE LIFECYCLE into account, and ENABLES FEEDBACK, which leads to a DEPLOYABLE PRODUCT.
A PRO of the Spiral Development Model is that it takes the entire ________ lifecycle into account, and enables ________ which leads to a ________ product?
A CON of the Spiral Development Model is that it is TOUGH TO MANAGE THE PROCESS EFFECTIVELY.
A CON of the Spiral Development Model is that it is tough to _______ the process effectively?
(+) Takes the ENTIRE SOFTWARE LIFE CYCLE INTO ACCOUNT
(+) ENABLES FEEDBACK
(+) Leads to a DEPLOYABLE PRODUCT
State the PROS of the Spiral Development Model:
(-) TOUGH TO MANAGE THE PROCESS EFFECTIVELY
State a CON of the Spiral Development Model:
INCEPTION
ELABORATION
CONSTRUCTION
TRANSITION
State the PHASES of the UNIFIED SOFTWARE PROCESS MODEL in order:
REQUIREMENTS
ANALYSIS
DESIGN
IMPLEMENTATION
TEST
State CORE WORK FLOWS that exist within the UNIFIED SOFTWARE PROCESS MODEL:
The Unified Software Process Model separates time and activity, focuses on both function and form, while no workflow is ever declared complete.
State 3 characteristics of the Unified Software Process Model:
Agile Software Development is a GROUP OF SOFTWARE METHODS that allow REQUIREMENTS AND SOLUTIONS TO EVOLVE through COLLABORATION of CROSS-FUNCTIONAL TEAMS.
Explain what Agile Software Development is all about?
EXTREME PROGRAMMING
SCRUM
AGILE UNIFIED PROCESS
State 3 Examples of Agile Software Development Models:
Agile Methods are best for projects with LOW CRITICALITY, REQUIREMENTS THAT CHANGE OFTEN, and FEW DEVELOPERS.
State 3 scenarios in which Agile Methods would theoretically be best for a particular project:
Plan Driven methods are best for projects with High Criticality, Requirements that DO NOT change often, and MANY DEVELOPERS.
In contrast to Agile, state 3 scenarios in which Plan Driven Methods would theoretically be best for a particular project:
DAILY TEAMWORK, WELCOMING CHANGING REQUIREMENTS, and SIMPLICITY
State 3 Principles of Agile Software Development: