Software Requirements

Specification & Analysis

Software processes
• Software processes in software engineering refer to the methods and
techniques used to develop and maintain software.
• Software Development : In this process, designing, programming,
documenting, testing, and bug fixing is done.
Software Development life cycle (SDLC)
• Software Development Life Cycle (SDLC) is a process used by the
software industry to design, develop and test high quality softwares.
• It consists of a detailed plan describing how to develop, maintain,
replace and alter or enhance specific software.
• The life cycle defines a methodology for improving the quality of
software and the overall development process.
Planning and Requirement Analysis
• Requirement analysis is the most important and fundamental stage in
SDLC. It is performed by the senior members of the team with inputs
from the customer, the sales department, market surveys and domain
experts in the industry. This information is then used to plan the basic
project approach and to conduct product feasibility study in the
economical, operational and technical areas.
Defining Requirements
• Once the requirement analysis is done the next step is to clearly
define and document the product requirements and get them
approved from the customer or the market analysts. This is done
through an SRS (Software Requirement Specification) document
which consists of all the product requirements to be designed and
developed during the project life cycle.
Designing the Product Architecture
• SRS is the reference for product architects to come out with the best
architecture for the product to be developed. Based on the
requirements specified in SRS, usually more than one design approach
for the product architecture is proposed and documented in a DDS -
Design Document Specification.
Building or Developing the Product
• In this stage of SDLC the actual development starts and the product is
built. The programming code is generated as per DDS during this
stage. If the design is performed in a detailed and organized manner,
code generation can be accomplished without much hassle.
Testing the Product
• This stage is usually a subset of all the stages as in the modern SDLC
models, the testing activities are mostly involved in all the stages of
SDLC. However, this stage refers to the testing only stage of the
product where product defects are reported, tracked, fixed and
retested, until the product reaches the quality standards defined in
the SRS.
Deployment in the Market and Maintenance
• Once the product is tested and ready to be deployed it is released
formally in the appropriate market. Sometimes product deployment
happens in stages as per the business strategy of that organization.
The product may first be released in a limited segment and tested in
the real business environment (UAT- User acceptance testing). Then
based on the feedback, the product may be released as it is or with
suggested enhancements in the targeting market segment. After the
product is released in the market, its maintenance is done for the
existing customer base.
 Waterfall Model
• Waterfall approach was first SDLC
Model to be used widely in
Software Engineering to ensure
success of the project. In "The
Waterfall" approach, the whole
process of software development is
divided into separate phases. In this
Waterfall model, typically, the
outcome of one phase acts as the
input for the next phase
sequentially.
Waterfall Model
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 document.
• System Design − The requirement specifications from first phase are studied in this phase and
the system design is prepared. This system design helps in specifying hardware and system
requirements and helps in defining the overall system architecture.
• Implementation − With inputs from the 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.
Application
• 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
• 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.
• Well understood milestones.
• Easy to arrange tasks.
• Process and results are well documented.
Disadvantages
• No working software is produced until late during the life cycle.
• High amounts of risk and uncertainty.
• Not a good model for complex and object-oriented projects.
• Poor model for long and ongoing projects.
• Not suitable for the projects where requirements are at a moderate to high
risk of changing. So, risk and uncertainty is high with this process model.
• It is difficult to measure progress within stages.
• Cannot accommodate changing requirements.
• Adjusting scope during the life cycle can end a project.
• Integration is done as a "big-bang. at the very end, which doesn't allow
identifying any technological or business bottleneck or challenges early.
Sample Question
• Anna wants to develop an online transport system. She wants only
online booking and cancelation system. Her requirements about the
software are fixed. What SDLC model should used explain with its’
steps.
Iterative Model
• 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 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.
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 sets 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 the 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.
• Risks are identified and resolved during iteration; and each iteration is an easily managed milestone.
• Easier to manage risk - High risk part is done first.
• With every increment, operational product is delivered.
• Issues, challenges and risks identified from each increment can be utilized/applied to the next increment.
• Risk analysis is better.
• It supports changing requirements.
• Initial Operating time is less.
• Better suited for large and mission-critical projects.
• During the life cycle, software is produced early which facilitates customer evaluation and feedback.
Disadvantages
• More resources may be required.
• Although cost of change is lesser, but it is not very suitable for changing requirements.
• More management attention is required.
• System architecture or design issues may arise because not all requirements are
gathered in the beginning of the entire life cycle.
• Defining increments may require definition of the complete system.
• 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.
• Projects progress is highly dependent upon the risk analysis phase.
Sample Question
• A company ‘A’ initially introduces a music player with little amount of
features. After 6 month a new update is available with some new
features in the software. Which SDLC model is considered in this
situation?
Spiral Model
Spiral Model
• The spiral model combines the idea of iterative development with the
systematic, controlled aspects of the waterfall model. This Spiral
model is a combination of iterative development process model and
sequential linear development model i.e. the waterfall model with a
very high emphasis on risk analysis. It allows incremental releases of
the product or incremental refinement through each iteration around
the spiral.
• The spiral model has four phases.
Spiral Model
• 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 phase 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.
• Design
• The Design phase starts with the conceptual design in the baseline spiral and involves architectural
design, logical design of modules, physical product design and the final design in the subsequent spirals.
• Construct or Build
• The 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 the customer for
feedback.
• Evaluation and Risk Analysis
• Risk Analysis includes identifying, estimating and monitoring the technical feasibility and management
risks, such as schedule slippage and cost overrun. After testing the build, at the end of first iteration, the
Application
• When 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.
Advantages
• Changing requirements can be accommodated.
• Allows extensive use of prototypes.
• Requirements can be captured more accurately.
• Users see the system early.
• Development can be divided into smaller parts and the risky parts can
be developed earlier which helps in better risk management.
Disadvantages
• Management is more complex.
• End of the 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 on indefinitely.
• Large number of intermediate stages requires excessive
documentation.
Sample Question
• Initially, “A” company makes an app for online shopping with cash on
delivery. After someday the company notices that some customers
send back their products without paying delivery charges. So, It plans
to open online payment system. Which SDLC model is considered in
this situation and why?
V-Model
• The V-Model is an extension of the waterfall model and is based on
the association of a testing phase for each corresponding
development stage. This means that for every single phase in the
development cycle, there is a directly associated testing phase. This is
a highly-disciplined model and the next phase starts only after
completion of the previous phase.
• Under the V-Model, the corresponding testing phase of the
development phase is planned in parallel. So, there are Verification
phases on one side of the ‘V’ and Validation phases on the other side.
The Coding Phase joins the two sides of the V-Model.
V-Model
• The V-model is an SDLC model where execution of processes happens
in a sequential manner in a V-shape. It is also known as Verification
and Validation model.
• The V-Model is an extension of the waterfall model and is based on
the association of a testing phase for each corresponding
development stage. This means that for every single phase in the
development cycle, there is a directly associated testing phase. This is
a highly-disciplined model and the next phase starts only after
completion of the previous phase.
Verification Phases
• Business Requirement Analysis
• This is the first phase in the development cycle where the product requirements are understood from the customer’s
perspective. This phase involves detailed communication with the customer to understand his expectations and exact
requirement. This is a very important activity and needs to be managed well, as most of the customers are not sure about what
exactly they need. The acceptance test design planning is done at this stage as business requirements can be used as an input
for acceptance testing.
• System Design
• Once you have the clear and detailed product requirements, it is time to design the complete system. The system design will
have the understanding and detailing the complete hardware and communication setup for the product under development.
The system test plan is developed based on the system design. Doing this at an earlier stage leaves more time for the actual test
execution later.
• Architectural Design
• Architectural specifications are understood and designed in this phase. Usually more than one technical approach is proposed
and based on the technical and financial feasibility the final decision is taken. The system design is broken down further into
modules taking up different functionality. This is also referred to as High Level Design (HLD).
• The data transfer and communication between the internal modules and with the outside world (other systems) is clearly
understood and defined in this stage. With this information, integration tests can be designed and documented during this
stage.
• Module Design
• In this phase, the detailed internal design for all the system modules is specified, referred to as Low Level Design (LLD). It is
important that the design is compatible with the other modules in the system architecture and the other external systems. The
unit tests are an essential part of any development process and helps eliminate the maximum faults and errors at a very early
stage. These unit tests can be designed at this stage based on the internal module designs.
• Coding Phase
• The actual coding of the system modules designed in the design phase is taken up in the Coding phase. The best suitable
programming language is decided based on the system and architectural requirements.
Validation Phases
• Unit Testing
• Unit tests designed in the module design phase are executed on the code during this validation
phase. Unit testing is the testing at code level and helps eliminate bugs at an early stage,
though all defects cannot be uncovered by unit testing.
• Integration Testing
• Integration testing is associated with the architectural design phase. Integration tests are
performed to test the coexistence and communication of the internal modules within the
system.
• System Testing
• System testing is directly associated with the system design phase. System tests check the
entire system functionality and the communication of the system under development with
external systems. Most of the software and hardware compatibility issues can be uncovered
during this system test execution.
• Acceptance Testing
• Acceptance testing is associated with the business requirement analysis phase and involves
testing the product in user environment. Acceptance tests uncover the compatibility issues
with the other systems available in the user environment. It also discovers the non-functional
issues such as load and performance defects in the actual user environment.
Application
• Requirements are well defined, clearly documented and fixed.
• Product definition is stable.
• Technology is not dynamic and is well understood by the project
team.
• There are no ambiguous or undefined requirements.
• The project is short.
Advantages
• This is a highly-disciplined model and Phases are completed one at a
time.
• Works well for smaller projects where requirements are very well
understood.
• 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.
Disadvantages
• High risk and uncertainty.
• Not a good model for complex and object-oriented projects.
• Poor model for long and ongoing projects.
• Not suitable for the projects where requirements are at a moderate to
high risk of changing.
• Once an application is in the testing stage, it is difficult to go back and
change a functionality.
• No working software is produced until late during the life cycle.
Agile Mode
• Agile SDLC model is a combination of iterative and incremental
process models with focus on process adaptability and customer
satisfaction by rapid delivery of working software product. Agile
Methods break the product into small incremental builds. These
builds are provided in iterations. Each iteration typically lasts from
about one to three weeks.
• At the end of the iteration, a working product is displayed to the
customer and important stakeholders.
Advantages
• Is a very realistic approach to software development.
• Promotes teamwork and cross training.
• Functionality can be developed rapidly and demonstrated.
• Resource requirements are minimum.
• Suitable for fixed or changing requirements
• Delivers early partial working solutions.
• Good model for environments that change steadily.
• Minimal rules, documentation easily employed.
• Enables concurrent development and delivery within an overall planned context.
• Little or no planning required.
• Easy to manage.
• Gives flexibility to developers.
Disadvantages
• Not suitable for handling complex dependencies.
• More risk of sustainability, maintainability and extensibility.
• An overall plan, an agile leader and agile PM practice is a must without which it will
not work.
• Strict delivery management dictates the scope, functionality to be delivered, and
adjustments to meet the deadlines.
• Depends heavily on customer interaction, so if customer is not clear, team can be
driven in the wrong direction.
• There is a very high individual dependency, since there is minimum documentation
generated.
• Transfer of technology to new team members may be quite challenging due to lack of
documentation.