Unit 2: Software Process Models and Agile Development

A software process model is an abstraction of the software development process. It provides a structured framework specifying the sequence of activities, tasks, and phases required to develop, maintain, and deliver a software product. Selecting the appropriate model is crucial to a project's success. This unit explores traditional software process models and the modern approach of Agile development.

2.1 Select Software Process Model for Project Development

Selecting a software process model depends heavily on project characteristics, team size, client involvement, and how well the requirements are understood at the beginning. We will explore several foundational models used in project development.

Waterfall Model

The Waterfall model is the earliest and most traditional software development lifecycle (SDLC) approach. It follows a linear, sequential flow. Each phase must be completed fully before the next phase begins, and there is typically no overlapping of phases.

Phases of the Waterfall Model:

1. Requirements Gathering and Analysis: All possible requirements of the system to be developed are captured and documented.
2. System Design: The requirements studied in the first phase are used to design the software architecture.
3. Implementation: The system is first developed in small programs called units, which are integrated in the next phase. Each unit is developed and tested for its functionality.
4. Integration and Testing: All the units are integrated into a system and tested for any faults or failures.
5. Deployment of System: Once testing is complete, the product is deployed in the customer environment or released into the market.
6. Maintenance: Issues that come up in the client environment are fixed, and enhancements are made as needed.

Advantages:

• Simple and easy to understand and use.
• Easy to manage due to the rigidity of the model (each phase has specific deliverables and a review process).
• Phases are processed and completed one at a time.

Disadvantages:

• Not suitable for complex or object-oriented projects.
• Poor model for long and ongoing projects.
• High amounts of risk and uncertainty.
• Difficult to measure progress within stages.

Incremental Model

The Incremental model divides the system into multiple, standalone modules. The software is developed in smaller, manageable portions called increments. Each increment passes through the requirements, design, implementation, and testing phases. The first increment is often a core product addressing basic requirements, and subsequent increments add more features.

Advantages:

• Generates working software quickly and early during the software life cycle.
• More flexible and less costly to change scope and requirements compared to the Waterfall model.
• Easier to test and debug during a smaller iteration.
• Customer can respond to each built.

Disadvantages:

• Requires good planning and design.
• Requires a clear and complete definition of the whole system before it can be broken down and built incrementally.
• Total cost is often higher than the Waterfall model.

Prototyping Model

The Prototyping model involves building a working prototype of the system before developing the actual software. A prototype is a preliminary version of the software that demonstrates its fundamental concepts and capabilities but may not hold the exact logic or full features.

Process:

1. Initial Requirements Gathering: Understand the basic requirements.
2. Quick Design: Focus on aspects visible to the user (e.g., input approaches and output formats).
3. Build Prototype: Create the preliminary version.
4. Customer Evaluation: The customer reviews the prototype and provides feedback.
5. Refining Prototype: Requirements are refined based on feedback. The prototype is adjusted or rebuilt.
6. Engineer Product: Once the prototype is accepted, the actual software is developed.

Advantages:

• Users are actively involved in development, leading to higher satisfaction.
• Errors and missing functionalities can be detected early.
• Faster feedback helps in delivering the right product.

Disadvantages:

• Can increase the complexity of the system as the prototype might expand beyond original plans.
• Developers may become too attached to the prototype and try to patch it rather than building the final system from scratch.
• Can be time-consuming if the client keeps requesting changes.

Spiral Model

The Spiral model combines the iterative development idea with the systematic, controlled aspects of the Waterfall model. It provides high support for risk handling. In its diagrammatic representation, it looks like a spiral with many loops.

Each loop of the spiral represents a phase of the software process. The four main quadrants are:

1. Objectives determination and identify alternative solutions: Requirements are gathered from the customers and the objectives are identified.
2. Identify and resolve risks: All potential solutions are evaluated, and risks are identified and resolved. A prototype is usually built at the end of this quadrant.
3. Develop next version of the Product: The features are developed and verified through testing.
4. Review and plan for the next Phase: The customer reviews the current progress and planning is done for the next iteration.

Advantages:

• Excellent risk management.
• Good for large and mission-critical projects.
• Strong approval and documentation control.
• Additional functionality can be added at a later date.

Disadvantages:

• Can be a costly model to use.
• Requires highly specific expertise in risk evaluation.
• Not suitable for small projects.
• The spiral may continue indefinitely.

Rapid Application Development (RAD)

Rapid Application Development (RAD) is an incremental software development process model that emphasizes a very short development cycle (typically 60-90 days). The RAD model is a high-speed adaptation of the linear sequential model in which rapid development is achieved by using a component-based construction approach.

Phases of RAD:

1. Business Modeling: Information flow among business functions is defined.
2. Data Modeling: Information gathered from business modeling is refined into a set of data objects.
3. Process Modeling: Data objects are transformed to achieve the business information flow.
4. Application Generation: Automated tools are used to convert process models into code and the actual system.
5. Testing and Turnover: Since RAD relies on reusable components, many of the components are already tested, reducing overall testing time.

Advantages:

• Reduced development time.
• Increases reusability of components.
• Quick initial reviews occur.
• Encourages customer feedback.

Disadvantages:

• Requires highly skilled developers and designers.
• Applicable only to systems that can be modularized.
• Depends on strong team and individual performances for identifying business requirements.
• Unsuitable for projects with high technical risks.

---

2.2 Agile Development

As the software industry evolved, traditional models like Waterfall were found to be too rigid and slow to adapt to changing business requirements. Agile development emerged as a flexible, iterative approach that prioritizes customer satisfaction, rapid delivery, and adaptability.

Agile Process & Principles

Agile methodology is a practice that promotes continuous iteration of development and testing throughout the software development lifecycle of the project. Both development and testing activities are concurrent, unlike the Waterfall model.

The Agile Manifesto Core Values:

1. Individuals and interactions over processes and tools.
2. Working software over comprehensive documentation.
3. Customer collaboration over contract negotiation.
4. Responding to change over following a plan.

Key Agile Principles:

1. Customer Satisfaction: Highest priority is to satisfy the customer through early and continuous delivery of valuable software.
2. Welcome Changes: Accommodate changing requirements, even late in development, for the customer's competitive advantage.
3. Frequent Delivery: Deliver working software frequently, from a couple of weeks to a couple of months.
4. Collaboration: Business people and developers must work together daily throughout the project.
5. Motivated Individuals: Build projects around motivated individuals. Give them the environment and support they need.
6. Face-to-face Conversation: The most efficient and effective method of conveying information to and within a development team.
7. Working Software: The primary measure of progress.
8. Sustainable Development: Agile processes promote sustainable development. Sponsors, developers, and users should be able to maintain a constant pace indefinitely.
9. Technical Excellence: Continuous attention to technical excellence and good design enhances agility.
10. Simplicity: The art of maximizing the amount of work not done is essential.
11. Self-organizing Teams: The best architectures, requirements, and designs emerge from self-organizing teams.
12. Continuous Improvement: At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

Comparison of Agile Development with Traditional Models

Understanding the differences between Agile and traditional models (like Waterfall) helps in making informed decisions about project management approaches.

By carefully analyzing the project requirements, team capabilities, and client expectations, a software engineering team can choose the most appropriate process model to ensure a successful software delivery. While traditional models offer structure and predictability, Agile methodologies offer the flexibility and responsiveness required in fast-paced technological environments.