Role of Software

• Computer software tell the hardware what to do. Without any software,
hardware would be worthless. Think of the software as a subject in school
and hardware as you or your brain. Without any learning, you can't do
anything. At the very basic level, computer software contains specific
instructions for how to accomplish a specific task. These instructions tell
the hardware exactly what to do and how to do it.
• All computers operates with what is known as system software, or the
operating system. This programming provides the very basic instructions for
how the computer interacts with the user and how the various programs
and packages operate.
• One of the best example to know about software and computers is, soul
and body. Hardware is like a Human body and software is just like soul. So
software plays an Important role in computers.
Software Characteristics
What does Software Development Life Cycle
(SDLC) mean?:
• The software development life cycle (SDLC) is a framework defining tasks
performed at each step in the software development process. SDLC is a
structure followed by a development team within the software
organization. It consists of a detailed plan describing how to develop,
maintain and replace specific software. The life cycle defines a methodology
for improving the quality of software and the overall development process.

This term is also known as the software development process.

• SDLC consists of following activities:

 Planning: The most important parts of software development, requirement
gathering or requirement analysis are usually done by the most skilled and
experienced software engineers in the organization. After the requirements
are gathered from the client, a scope document is created in which the
scope of the project is determined and documented.
 Implementation: The software engineers start writing the code according
to the client's requirements.

 Testing: This is the process of finding defects or bugs in the created

software.
 Documentation: Every step in the project is documented for future
reference and for the improvement of the software in the development
process. The design documentation may include writing the application
programming interface (API).

 Deployment and maintenance: The software is deployed after it has been

approved for release.

 Maintaining: Software maintenance is done for future reference. Software

improvement and new requirements (change requests) can take longer
than the time needed to create the initial development of the software.
ˆ SDLC Models
There are various software development life cycle models defined
and designed which are followed during software development
process. These models are also referred as "Software Development
Process Models". Each process model follows a Series of steps
unique to its type, in order to ensure success in process of software
development.
Following are the most important and popular SDLC models followed
in the industry:
Waterfall Model
Iterative Model
Spiral Model
V-Model
Big Bang Model
The other related methodologies are Agile Model, RAD Model –
Rapid Application Development and Prototyping Models.
Waterfall Model
The Waterfall Model was first Process Model to be introduced. It is
also referred to as a linear-sequential life cycle model. It is very
simple to understand and use. In a waterfall model, each phase
must be completed before the next phase can begin and there is no
overlapping in the phases.
The sequential phases in Waterfall model are:
Requirement Gathering and analysis: All possible requirements
of the system to be developed are captured in this phase and
documented in a requirement specification doc.

System Design: The requirement specifications from first phase

are studied in this phase and system design is prepared. System Design
helps in specifying hardware and system requirements and also helps
in defining overall system architecture.

Implementation: With inputs from system design, 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 which is referred to as Unit Testing.

Integration and Testing: All the units developed in the

implementation phase are integrated into a system after testing of
each unit. Post integration the entire system is tested for any faults
and failures.

Deployment of system: Once the functional and non

functional testing is done, the product is deployed in the customer
environment or released into the market.

Maintenance: There are some issues which come up in the

client environment. To fix those issues patches are released. Also to
enhance the product some better versions are released. Maintenance
is done to deliver these changes in the customer environment.
Waterfall Model Application
Every software developed is different and requires a
suitable SDLC approach to be followed based on the internal
and external factors. Some situations where the use of Waterfall
model is most appropriate are:
Requirements are very well documented, clear and fixed
Product definition is stable
Technology is understood and is not dynamic
There are no ambiguous requirements
Ample resources with required expertise are available to
support the product
The project is short
Advantages of waterfall model:
• 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.
• Works well for smaller projects where requirements are very well understood.
• Clearly defined stages.
• Easy to arrange tasks.
• Process and results are well documented.

Disadvantages of waterfall model:

• No working software is produced until late during the life cycle.
• Cannot accommodate changing requirements.
• It is difficult to measure progress within stages.
• Not a good model for complex and object-oriented projects.
• Poor model for long and ongoing projects.
Iterative Model
• In Iterative model, iterative process starts with a simple implementation of
a small set of the software requirements and iteratively enhances the
evolving versions until the complete system is implemented and ready to
be deployed.

• An iterative life cycle model does not attempt to start with a full
specification of requirements. Instead, development begins by specifying
and implementing just part of the software, which is then reviewed
in order to identify further requirements. This process is then
repeated, producing a new version of the software at the end of each
iteration of the model.

Following is the pictorial representation of Iterative model:

Iterative incremental development is a combination of both iterative design or
iterative method and incremental build model for development. "During software
development, more than one iteration of the software development cycle may be
in progress at the same time." and "This process may be described as an
"evolutionary acquisition“ or "incremental build" approach."

In incremental model the whole requirement is divided into various builds.

During each iteration, the development module goes through the requirements,
design, implementation and testing phases. Each subsequent release of the
module adds function to the previous release. The process continues till the
complete system is ready as per the requirement.

The key to successful use of an iterative software development

lifecycle is rigorous validation of requirements, and verification &
testing of each version of the software against those requirements
within each cycle of the model. As the software evolves through
successive cycles, tests have to be repeated and extended to verify each version
of the software.

Iterative Model Application

Requirements of the complete system are clearly defined and understood.
Major requirements must be defined; however, some functionalities or
requested enhancements may evolve with time.
There is a time to the market constraint.
A new technology is being used and is being learnt by the development
team while working on the project.
Resources with needed skill set are not available and are planned to be
used on contract basis for specific iterations.
There are some high risk features and goals which may change in the
future.
Advantages
 Some working functionality can be developed quickly and early in
life cycle.
 Results are obtained early and periodically.
 Parallel development can be planned.
 Progress can be measured.
 Less costly to change the scope/requirements.
 Testing and debugging during smaller iteration is easy.
 Easier to manage risk - High risk part is done first.
 Risk analysis is better.
 It supports changing requirements.
 Initial Operating time is less.
 Better suited for large and mission- critical projects.
 During life cycle software is produced early which facilitates
customer evaluation and feedback.
Disadvantages
 More resources may be required.
 More management attention is required
 Not suitable for smaller projects.
 Management complexity is more.
 End of project may not be known which is a risk.
 Highly skilled resources are required for risk analysis.
 Project’s progress is highly dependent upon the risk analysis phase
Spiral Model
The spiral model combines the idea of iterative development with
the systematic, controlled aspects of the waterfall model.

Spiral model is a combination of iterative development process

model and sequential linear development model i.e. waterfall model with
very high emphasis on risk analysis. It allows for incremental
releases of the product, or incremental refinement through each
iteration around the spiral.

Spiral Model design

The spiral model has four phases. A software project repeatedly passes
through these phases in iterations called Spirals.
Identification
This phase starts with gathering the business requirements in the
baseline spiral. In the subsequent spirals as the product matures,
identification of system requirements, subsystem requirements and unit
requirements are all done in this phase. This also includes understanding the
system requirements by continuous communication between the customer
and the system analyst. At the end of the spiral the product is deployed
in the identified market.
Following is a diagrammatic representation of spiral model listing the activities
in each phase
 Design
Design phase starts with the conceptual design in the baseline
spiral and involves architectural design, logical design of modules,
physical product design and final design in the subsequent spirals.

Construct or Build
Construct phase refers to production of the actual software product at every
spiral. In the baseline spiral when the product is just thought of and
the design is being developed a POC (Proof of Concept) is developed in this
phase to get customer feedback.

Then in the subsequent spirals with higher clarity on requirements and

design details a working model of the software called build is produced
with a version number. These builds are sent to customer for feedback.
 Evaluation and Risk Analysis
Risk Analysis includes identifying, estimating, and monitoring technical
feasibility and management risks, such as schedule slippage and cost overrun.
After testing the build, at the end of first iteration, the customer evaluates the
software and provides feedback.

Based on the customer evaluation, software development process

enters into the next iteration and subsequently follows the linear approach to
implement the feedback suggested by the customer. The process of iterations
along the spiral continues throughout the life of the software.
Spiral Model Application
When costs there is a budget constraint and risk evaluation is important
For medium to high-risk projects
Long-term project commitment because of potential changes to economic
priorities as the requirements change with time
Customer is not sure of their requirements which is usually the case
Requirements are complex and need evaluation to get clarity
New product line which should be released in phases to get enough
customer feedback
Significant changes are expected in the product during the development
cycle
Advantage of Spiral model
 Changing requirements can be accommodated.
 Allows for extensive use of prototypes.
 Requirements can be captured more accurately.
 Users see the system early.
 Development can be divided into smaller parts and more risky parts can be
developed earlier which stages requires excessive helps better risk
management.
Disadvantage of Spiral model
 Management is more complex.
 End of project may not be known early.
 Not suitable for small or low risk projects and could be expensive
for small projects.
 Process is complex
 Spiral may go indefinitely.
 Large number of intermediate stages requires excessive
documentation.
What is Prototyping Model SDLC?
A prototype is made first and based on it final product is developed. A
prototype is a model or a program which is not based on strict planning,
but is an early approximation of the final product or software system. A
prototype acts as a sample to test the process. From this sample we learn
and try to build a better final product. Please note that this prototype may
or may not be completely different from the final system we are trying to
develop.

Prototyping Model
This type of System Development Method is employed when it is very difficult
to obtain exact requirements from the user. While making the model, user keeps
giving feedbacks from time to time and based on it, a prototype is made.
Completely built sample model is shown to user and based on his feedback, the
SRS(System Requirements Specifications) document is prepared. After
completion of this, a more accurate SRS is prepared, and now development work
can start using Waterfall Model.
 Prototyping process model

Now lets discuss the disadvantages and advantages of the Prototype model in
Software development method.
Advantages of Prototyping Model

1) When prototype is shown to the user, he gets a proper clarity and 'feel' of the
functionality of the software and he can suggest changes and modifications.
2) This type of approach of developing the software is used for non-IT-literate
people. They usually are not good at specifying their requirements, nor can tell
properly about what they expect from the software.
3) When client is not confident about the developer's capabilities, he asks for a
small prototype to be built. Based on this model, he judges capabilities of
developer.
4) Sometimes it helps to demonstrate the concept to prospective investors to get
funding for project.
5) It reduces risk of failure, as potential risks can be identified early and
mitigation steps can be taken.
6) Iteration between development team and client provides a very good and
conductive environment during project.
7) Time required to complete the project after getting final the SRS reduces,
since the developer has a better idea about how he should approach the project.

Disadvantages of Prototyping Model:

1) Prototyping is usually done at the cost of the developer. So it should be done
using minimal resources. It can be done using Rapid Application Development
(RAD) tools. Please note sometimes the start-up cost of building the development
team, focused on making prototype, is high.
2) Once we get proper requirements from client after showing prototype model,
it may be of no use. That is why, sometimes we refer to the prototype as
“Throw-away“ prototype.
3) It is a slow process.
4) Too much involvement of client, is not always preferred by the developer.
5) Too many changes can disturb the rhythm of the development team.
What is RAD?
Rapid application development (RAD) is a software development
methodology that uses minimal planning in favor of rapid prototyping. A
prototype is a working model that is functionally equivalent to a component of
the product. In RAD model the functional modules are developed in parallel
as prototypes and are integrated to make the complete product for faster product
delivery.

Since there is no detailed preplanning, it makes it easier to incorporate

the changes within the development process. RAD projects follow iterative and
incremental model and have small teams comprising of developers, domain
experts, customer representatives and other IT resources working progressively on
their component or prototype. The most important aspect for this model to
be successful is to make sure that the prototypes developed are reusable.

RAD Model Design

RAD model distributes the analysis, design, build, and test phases into a series of
short, iterative development cycles. Following are the phases of RAD Model:
 Business Modeling:
The business model for the product under development is designed in terms
of flow of information and the distribution of information between various
business channels. A complete business analysis is performed to find the vital
information for business, how it can be obtained, how and when is the information
processed and what are the factors driving successful flow of information.

Data Modeling:
The information gathered in the Business Modeling phase is reviewed and
analyzed to form sets of data objects vital for the business. The attributes of all
data sets is identified and defined. The relation between these data objects are
established and defined in detail in relevance to the business model.

Process Modeling:
The data object sets defined in the Data Modeling phase are converted to
establish the business information flow needed to achieve specific business
objectives as per the business model. The process model for any changes or
enhancements to the data object sets is defined in this phase. Process
descriptions for adding , deleting, retrieving or modifying a data object are
given.
 Application Generation:
The actual system is built and coding is done by using automation tools to
convert process and data models into actual prototypes.

Testing and Turnover:

The overall testing time is reduced in RAD model as the prototypes are
independently tested during every iteration. However the data flow and the
interfaces between all the components need to be thoroughly tested with
complete test coverage. Since most of the programming components have
already been tested, it reduces the risk of any major issues.

Following image illustrates the RAD Model:

 RAD Model Application
RAD should be used only when a system can be modularized to be
delivered in incremental manner.
It should be used if there’s high availability of designers for modeling
It should be used only if the budget permits use of automated code
generating tools.
RAD SDLC model should be chosen only if domain experts are available
with relevant business knowledge
Should be used where the requirements change during the course of the
project and working prototypes are to be presented to customer in small iterations
of 2- 3 months.
Advantage of RAD Model
Changing requirements can be accommodated.
Progress can be measured.
Iteration time can be short with use of powerful RAD tools.
Productivity with fewer people in short time.
Reduced development time.
Increases reusability of components
Disadvantages of RAD Model
Dependency on technically strong team members for identifying business
requirements.
Only system that can be modularized can be built using RAD
Requires highly skilled developers/designers.
High dependency on modeling skills
Inapplicable to cheaper projects as cost