Software Processes


It represents the sequence of activities to be performed for efficient software development.

Abstract representation or visualization of software processes is presented by several popular
software process models form different perspectives.

Example models are waterfall, spiral and incremental.

1. Waterfall SDLC-

5 phase plan-driven sequential appraoch towards software development(SDLC).

Applications-

For long-term commitment based critical complex systems (large-scale) development like
safety-critical systems, military applications, weather systems, etc.

Advantages-

Suitable for clearly understood requirements, process is visible because of extensive
documentation, reliable software development etc.
 Software Processes-Waterfall SDLC

Disadvantages-

Not flexible for accomodating changing requirements, customer doesn’t see value in
product as soon as possible, cost of changing requirements or moving back to
previous phase and reworking is huge and sometimes lacks customer involvement
throughout the project.

Pictorial Representation-
 Waterfall Phases

The principal stages of the waterfall model directly reflect the fundamental development activities:

1. Requirements analysis and definition- The system’s services, constraints, and goals are established by consultation with
system users. They are then defined in detail and serve as a system specification.

2. System and software design- The systems design process allocates the requirements to either hardware or software
systems by establishing an overall system architecture. Software design involves identifying and describing the fundamental
software system abstractions and their relationships.

3. Implementation and unit testing- During this stage, the software design is realized as a set of programs or program units.
Unit testing involves verifying that each unit meets its specification.

4. Integration and system testing- The individual program units or programs are integrated and tested as a complete system
to ensure that the software requirements have been met. After testing, the software system is delivered to the customer.

5. Operation and maintenance- Normally (although not necessarily), this is the longest life cycle phase. The system is
installed and put into practical use. Maintenance involves correcting errors which were not discovered in earlier stages of the
life cycle, improving the implementation of system units and enhancing the system’s services as new requirements are
discovered.
 Spiral SDLC model

Iterative in nature with strong emphasis on risk management.

Risk identification and analysis is necessary throughout the SDLC. Operational risks
could include potential team changes or miscommunications. Technical risks could
involve technology malfunctions or the use of untested technology. External risks
could arise from changes in market conditions or regulatory laws.

Applications-

Large, complex and high risk projects.
Gantt chart and Game developments.
An example product that was built through the Spiral model is NASA's space shuttle
program in the 1970s. The product was complex in nature, full of algorithms and features
associated with high risk. Mainly, NASA's team used the spiral model to identify and
mitigate the risk early in the product development process.
Spiral SDLC model
 Spiral SDLC model phases

When looking at a diagram of a spiral model, the radius of the spiral represents the cost of the project and the angular degree
represents the progress made in the current phase. Each phase begins with a goal for the design and ends when the developer or
client reviews the progress.

Every phase can be broken into four quadrants: identifying and understanding requirements, performing risk analysis, building the
prototype and evaluation of the software's performance.

Phases begin in the quadrant dedicated to the identification and understanding of requirements. The overall goal of the phase should
be determined and all objectives should be elaborated and analyzed. It is important to also identify alternative solutions in case the
attempted version fails to perform.

Next, risk analysis should be performed on all possible solutions in order to find any faults or vulnerabilities -- such as running over
the budget or areas within the software that could be open to cyber attacks. Each risk should then be resolved using the most
efficient strategy.

In the next quadrant, the prototype is built and tested. This step includes: architectural design, design of modules, physical product
design and the final design. It takes the proposal that has been created in the first two quadrants and turns it into software that can
be utilized.

Finally, in the fourth quadrant, the test results of the newest version are evaluated. This analysis allows programmers to stop and
understand what worked and didn’t work before progressing with a new build. At the end of this quadrant, planning for the next phase
begins and the cycle repeats. At the end of the whole spiral, the software is finally deployed in its respective market.
 Spiral SDLC model pros/cons


Advantages-

Flexibility, Risk handling and Customer satisfaction.

Drawbacks-

Expensive, effective risk handling with expertise persona, number of required phases
is often unknown, making time management almost impossible and is more complex
than other SDLC.
 Incremental Development & Delivery
Software is developed incrementally instead as a whole
system development at once. Several versions are built
whereby initial version/increment satisfies high priority
requirements.

Advantages-
1. Flexible- accomodation of changes are easy and
customer feedback mechanism is incorporated.
2. Customers sees value in the end-product as early as
possible.
3. Rapid software development.
4. Customer involvement.

Drawbacks-

1. Limited or No Documentation.
2. Process is not visible/transparent.
3. Total cost is higher than waterfall

Suitable for small to medium-scaled projects especially