SOFTWARE ENGINEERING

Lab 1
Date: 02/09/2022
Name: - AMARJEET SINGH
Enrollment No: - A20405220165
Section: - A
Batch: - A2
Semester: -5th

Objective 1: Briefly Explain what do you understand by Software

Development Life Cycle (SDLC) also state its features?
Ans: - SDLC is a process followed for a software project, within a software organization. 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.
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.

Stage 2: 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

Stage 3: 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.

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.

Stage 4: 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.
Developers must follow the coding guidelines defined by their organization and programming
tools like compilers, interpreters, debuggers, etc. are used to generate the code. Different high
level programming languages such as C, C++, Pascal, Java and PHP are used for coding. The
programming language is chosen with respect to the type of software being developed.

Stage 5: 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.
Stage 6: 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.

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.

Never-before-published theory of the three-legged stool of IT business value.

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.

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).

3.Implementation and unit testing

During this phase, design is implemented. If the SDD is complete, the implementation or coding
phase proceeds smoothly, because all the information needed by software developers is
contained in the SDD. During testing, the code is thoroughly examined and modified. Small
modules are tested in isolation initially. After that these modules are tested by writing some
overhead code to check the interaction between these modules and the flow of intermediate
output.

4. Integration and System Testing

This phase is highly crucial as the quality of the end product is determined by the effectiveness
of the testing carried out. The better output will lead to satisfied customers, lower maintenance
costs, and accurate results. Unit testing determines the efficiency of individual modules.
However, in this phase, the modules are tested for their interactions with each other and with the
system.

5.Operation and maintenance phase:

Maintenance is the task performed by every user once the software has been delivered to the
customer, installed, and operational.

Applications of WaterFall Model

1. Waterfall model was used to develop enterprise applications like Customer Relationship
Management (CRM) systems.
2. Human Resource Management Systems (HRMS).
3. Supply Chain Management Systems.
4. Inventory Management Systems.
5. Point of Sales (POS) systems for Retail chains etc.
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.

Applications of Evolutionary Model

1. Evolutionary model is commonly used when the customer wants to start using the core
features instead of waiting for the full software.
2. Evolutionary model is also used in object-oriented software development because the
system can be easily portioned into units in terms of objects.
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 end product and is used for obtaining customer
feedback.

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.

6. Implement Product and Maintain

Once the final system is developed based on the final prototype, it is thoroughly tested and
deployed to production. The system undergoes routine maintenance for minimizing downtime
and prevent large-scale failures.
Applications of Prototype Model
1. Prototype model should be used when the desired system needs to have a lot of
interaction with the end users.
2. Evaluating and Testing the Design.
3. Clarifying Production Costs and Issues.
4. Selling the Product to Others.

V-Model
V Model is a highly disciplined SDLC model which has a testing phase parallel to each
development phase. The V model is an extension of the waterfall model wherein software
 development and testing are executed in a sequential way. It is known as the Validation or
Verification Model.

Phases of V-Model

1. Business Requirement Analysis

It is the very first phase of the development. In this phase the requirements and needs of
customers are understood. What the customer expects from the final software, what
functionalities customers want, all such things are discussed in this phase
2. System Design
In this phase, the actual design of the system is decided. After the requirement analysis phase,
based upon the finalized requirements, the complete design of the system is discussed.
3. Architectural Design
This phase is also referred to as High Level Design (HLD). After system design is analyzed, the
architecture of the system is decided. It consists of various modules, the database tables, UML
diagrams etc.
4. Module Design
This phase is also known as Low Level Design (LLD). After the high-level design is analyzed,
each component in high level design is discussed in detail.
5. Coding Phase
This is the phase where actual coding and implementation takes place. In this phase, the suitable
programming language is decided based on the requirements.

6. Validation Phase

Unit Testing: - Unit testing is performed in the module design phase. Here each module goes
through the testing by executing the code written for that module. It tests whether each module
can perform its required functions or not.
Integration Testing: - Integration testing is performed in the architectural design phase. In
integration testing, we check whether each module is working properly with other modules or
not. 
System Testing: - System testing is performed in the system design phase. Here the
functionality of the whole system is checked by checking the integration of hardware and
software and how well they are coordinating with each other.

User Acceptance Testing: - User Acceptance testing happens in the requirement analysis phase.
Here the system is checked in the user environment. 

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.