Professional Documents
Culture Documents
Lab 2
Lab 2
Lab 1
Date: 02/09/2022
Name: - AMARJEET SINGH
Enrollment No: - A20405220165
Section: - A
Batch: - A2
Semester: -5th
Fig.1.SDLC
Stage 1: 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.
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 DDS is reviewed by all the important stakeholders and based on various parameters as risk
assessment, product robustness, design modularity, budget and time constraints, the best design
approach is selected for the product.
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.
Features of SDLC
Focuses on process and practices in an organizational context—considers all of the moving parts
—people, process and technology.
Includes templates, guidelines and metrics to jump start quality initiatives and progress
organizational maturity in a continuous improvement environment.
Excellent and comprehensive text book, ideal for collegiate Information Technology courses.
Best practice techniques for organizational change management, requirements elicitation and
analysis, system design, test-driven development, quality assurance and continuous improvement
and much, much more…
Objective 2: Write a short note on the following: -
1. Waterfall Model
2. Evolutionary Model
3. Prototype Model
4. V-Model
Waterfall Model
Requirements analysis and specification, design, implementation, and unit testing, integration
and system testing, and operation and maintenance. The steps always follow in this order and do
not overlap. The developer must complete every phase before the next phase begins. This model
is named "Waterfall Model", because its diagrammatic representation resembles a cascade of
waterfalls.
Fig.2.Waterfall Model
1. Requirements analysis and specification phase:
The aim of this phase is to understand the exact requirements of the customer and to document
them properly. Both the customer and the software developer work together so as to document
all the functions, performance, and interfacing requirement of the software. It describes the
"what" of the system to be produced and not "how." In this phase, a large document
called Software Requirement Specification (SRS) document is created which contained a
detailed description of what the system will do in the common language.
2. Design Phase
This phase aims to transform the requirements gathered in the SRS into a suitable form which permits
further coding in a programming language. It defines the overall software architecture together with high
level and detailed design. All this work is documented as a Software Design Document (SDD).
Evolutionary Model
Evolutionary model is also referred to as the successive versions model and sometimes as
the incremental model. In Evolutionary model, the software requirement is first broken down
into several modules (or functional units) that can be incrementally constructed and delivered the
users provide feedback on the product for planning stage of the next cycle and the development
team responds, often by changing the product, plans or process. These incremental cycles are
typically two or four weeks in duration and continue until the product is shipped.
Fig.2.Evolutionary Model
Prototype Model
Prototyping is defined as the process of developing a working replication of a product or
system that has to be engineered.
It offers a small-scale facsimile of the product and is used for obtaining customer feedback.
Fig.4.Prototype Model
1. Requirements Gathering and Analysis
A prototyping model starts with requirement analysis. In this phase, the requirements of the
system are defined in detail. During the process, the users of the system are interviewed to know
what their expectation from the system.
2. Quick design
The second phase is a preliminary design or a quick design. In this stage, a simple design of
the system is created. However, it is not a complete design. It gives a brief idea of the system to
the user. The quick design helps in developing the prototype.
3. Build a Prototype
In this phase, an actual prototype is designed based on the information gathered from quick
design. It is a small working model of the required system.
4. Initial user evaluation
In this stage, the proposed system is presented to the client for an initial evaluation. It helps to
find out the strength and weakness of the working model. Comment and suggestion are collected
from the customer and provided to the developer.
5. Refining Prototype
If the user is not happy with the current prototype, you need to refine the prototype according to
the user’s feedback and suggestions.
Fig. 5: V- Model
Applications of V – Model
1. It can be used for software projects of any size, whether in commerce, the military or the
public sector.
2. The model serves as a tool to facilitate the organization and execution of development,
maintenance, and advancement of diverse IT systems.