Term
| What are the popular process models |
|
Definition
Waterfall Model
V Model
Iterative model
Incremental Model
Spiral Model
Prototype Model
RAD Model
Agile & Scrum Model
|
|
|
Term
|
Definition
| The first structured approach; original model of SDLC. Has a Big-Bang approach; focuses on the customer only in the initial phase. Requirements are fixed; client knows what they want (requirements are well understood) |
|
|
Term
|
Definition
| Characterized by sequential steps, feedback loop between two phases in development, and document driven. |
|
|
Term
| What are some advantages of the waterfall model |
|
Definition
| Documentation and clearly defined phases, maintenance easier (assuming available documents are up-to-date). |
|
|
Term
| What are some disadvantages of the waterfall method? |
|
Definition
| Customer involvment in the first phase only. Process difficult to control. Product becomes available very late in the process. Sequential and complete execution of phases often not desirable. |
|
|
Term
|
Definition
| Various testing techniques are defined and various kinds of testing are clearly separated from each other. Test designing starts well before testing phase. The model has a parallel test preparation approach. |
|
|
Term
| What are some advantages of the V-Model |
|
Definition
| Reduction in total development time due to overlapped test preparation. Better quality product due to separate testing stream. |
|
|
Term
| What are some dis-advantages of the V-Model? |
|
Definition
| Complete and frozen specification document up from often not feasible in practice. Customer involvement in the first phase only. |
|
|
Term
| What are the steps in the Agile project Life Cycle? |
|
Definition
- Planning - requirements are listed & prioritized.
- Feedback -iterative step in cycle; customer reviews the work packets and gives feedback.
- Implementation - development phase
- Testing - work packets are tested.
|
|
|
Term
| What is agile methodologies? |
|
Definition
| Flexible approach to product management typically used in software development. |
|
|
Term
|
Definition
| The ability to react to changing situations quickly, appropriately, and effectively |
|
|
Term
|
Definition
- Allows you to notice chages early
- Initiate action promptly.
- Lightweight (documentation)
- People based rather than plan based
- Follows the agile manifesto.
|
|
|
Term
|
Definition
- A statement of values
- Individuals and interactions are given importance over processes and tools
- Working software is given precedence over comprehensive documentation.
- Customer collaboration or communicaiton is given importance over contract negotiation.
- Responds to change vs. following a documented plan.
|
|
|
Term
| What is the Scrum - Agile Methodology? |
|
Definition
- Focuses on delivering the highest business value in the shortest time.
- Allows development team to rapidly and repeatedly inspect actual working software.
- Business sets the priorities and requirements.
- Teams are self managed and determine the best way to deliver the highest priority features.
- Working software can be reviewed regularly & released as is or continued to enhance for the nest iteration.
|
|
|
Term
| What are some characteristics of Scrum? |
|
Definition
- Iterative incremental framework for a project.
- Developed in short cycles of work called sprints.
|
|
|
Term
|
Definition
| Work done by a team over a period of time (usually 1 month). |
|
|
Term
| Scrum Requirements Engineering (RE) |
|
Definition
| The science and discipline concerned with analyzing & documenting requirements. |
|
|
Term
|
Definition
| A capability needed by a user to solve a problem; a documented representation of a condition or capability. |
|
|
Term
| What are some PLANNING impacts of requirements engineering in Scrum? |
|
Definition
- Poor software estimation
- Scope creep
- Project delay
|
|
|
Term
| What are some COST impacts of requirements engineering. |
|
Definition
- 50% of effort is spent on rework
- Major cause of budget overruns
|
|
|
Term
| What are some QUALITY impact requirements in Engineering? |
|
Definition
- 30% of defects are related to RE
- 50% of customer complaints are related to RE
|
|
|
Term
| What are some effects of requirements engineering? |
|
Definition
- Duration & manpower required to develop the project could be wrongly estimated resulting in huge loss of revenue.
- Could lead to scope creep.
- leads to projects being delayed & overshot in estimates.
- has an impact on cost
- 50% of effort is spent on rework
|
|
|
Term
| What are user requirements? |
|
Definition
| What the user does; requires actions on the user. |
|
|
Term
| What are some examples of user requirements? |
|
Definition
"The system shall allow users to enter..."
"The system shall allow users to input..." |
|
|
Term
| What are functional requirements? |
|
Definition
| What the software must have for the user. |
|
|
Term
| What is an example of a functional requirement? |
|
Definition
"System shall allow users to ..."
"System shall flag terminated users ..." |
|
|
Term
| What are non-functional requirements? |
|
Definition
| Requirements relating to usability, performance, security, etc. |
|
|
Term
| What is an example of a non-functional requirement? |
|
Definition
| "System shall generate a report in no longer than 5 seconds" |
|
|
Term
| Whate are some advantages of Requirements Engineering (RE)? |
|
Definition
- Helps to conrol change in requirements
- Helps to reduce rework
- Helps to reduce scope creep
- Helps to reduce project risks
|
|
|
Term
| What can you achieve from using Requirements Engineering (RE)? |
|
Definition
- On schedule project completion
- Higher quality product
- Improved customer satisfaction
- Higher profits
|
|
|
Term
| What are some characteristics of good requirements? |
|
Definition
- Complete - requirement is fully stated in one place; no missing information.
- Correct - requirement meets all or part of a business need authorized by stakeholder.
- Consistent - requirement does not contradict any other requirement.
- Unambiguous - subject ot one and only one interpretation.
- Necessary - Does the customer need the requirement.
- Verifiable - capable of being verified
|
|
|
Term
| What are the steps in the Requirements Engineering Framework? |
|
Definition
- Requirements Elicitation - meetings
- Requirements Analysis - come up with a plan
- Requirements Specification - structure customer input; diagrams/documents
- Requirements Validation - customer checks for accuracy and completeness; correct errors.
|
|
|
Term
|
Definition
- The process of managing changes to requirements during the lifecycle of the product development
- Ensures the impact of the changes on the remaining work is assessed, controlled, and monitored effectively & efficiently.
- In agreement with key stakeholders
|
|
|
Term
| What does requirements traceability mean? |
|
Definition
| The ability to describe and follow the life of a requirement in both forward and backward direction. |
|
|
Term
| What is a Requirements Traceability Matrix (RTM)? |
|
Definition
| A tool to document requirements changes through the life cycle. |
|
|
