Development Methods Flashcards
(12 cards)
What are the three principles of the Waterfall Method?
- Linear: Each stage is completed before the next begins
- Well Documented: Every phase has its own documentation requirements
- Low Customer Involvement: Customers are typically involved at the beginning and end
What are the five stages of the Waterfall Method?
- Analysis: Understanding and documenting system requirements
- Design: Creating architecture and design documents
- Coding: Writing code in the chosen programming language
- Testing: Verifying the code meets requirements and is bug-free
- Maintenance: Upkeep after deployment including bug fixes and updates
What are two benefits of the Waterfall Method?
- Easy to Manage: Clear structure simplifies planning and task delegation
- Works Well for Smaller Programs: Straightforward approach suitable for smaller projects
What are four drawbacks of the Waterfall Method?
- Difficult to Make Late Changes: Hard to alter completed work if requirements change
- Not Suited for Projects Subject to Change: Not ideal for programs requiring flexibility
- Working Program Produced Late: Functional version available late in the life cycle
- Not Suitable for Complex Projects: Lack of iteration can hinder complex systems
Briefly describe the Iterative Method.
The iterative method begins with an initial version, followed by multiple rounds of development. Each round extends the development if the previous one was successful.
The program development lifecycle is repeated in small segments, with high customer involvement, making it more flexible but requiring a clear understanding of the final system.
What are the main principles of the Iterative Method?
- Incremental Development: Program development lifecycle is repeated in small segments.
- High Customer Involvement: Customers are involved throughout the process.
What are the benefits of using the Iterative Method?
- Easier to Test and Debug: Simpler to identify and fix issues in smaller sections.
- More Flexible: Easier to alter requirements as the project evolves.
- Customer Involvement: Reduces surprises at project completion.
What are the drawbacks of using the Iterative Method?
- Whole System Definition: Requires a clear understanding of the final system at the start.
- Planning: Needs thorough planning throughout the process.
- Not Suitable for Simple Projects: Complexity may not be justified for small projects.
What is the basic structure of Rapid Application Development (RAD)?
- The program is divided into modules, each assigned to a different team. Each module typically goes through Analysis, Design, Coding, Testing, and Maintenance in sequence.
- RAD is a development approach that divides a program into modules for different teams, emphasizes prototyping over planning, and heavily involves customers throughout the process. It reduces development time but requires skilled teams and a system that can be modularized.
What are the main principles of RAD?
- Minimal Planning: Emphasizes adapting to changes rather than extensive upfront planning.
- Use of Prototypes: Relies on practical, working models to guide development.
- High Customer Involvement: Involves customers throughout the entire development process.
What are the benefits of using RAD?
- Reduced Development Time: Faster delivery due to iterative nature and use of prototypes.
- Rapid Feedback: Customers see working versions of the product early in development.
- Flexibility: Allows for adjustments based on customer feedback.
- Ease of Modification: Modular approach allows changes without affecting the entire system.
What are the drawbacks of using RAD?
- Need for Modularity: The system must be able to be broken into distinct modules.
- Skilled Team Requirement: Requires a skilled team that can adapt to rapid changes.
- Not Suitable for Small Projects: May not be cost-effective or practical for simple projects.