INDEX

S. No. Name of Experiment Date Sign Remark

1. Explain Software development life cycle with the help of

stages and SDLC
2. Discuss SDLC Model a) Waterfall Model (b)RAD Model
(c)Spiral Model (d) V-Model (e) Agile Model
3. Explain the Role of QA in Software Quality Management
4. Define the ISO Standard in term of Software development

5 Describe the concept of design pattern in details

6 Write the SRS /Report of case study on Banking System in

SDLC Life cycle
7 Study report of any two design pattern.
 EXPERIMENT-1

OBJECTIVE: Explain Software development life cycle with the help of stages and
SDLC.

THEORY:
Software Development is the development of software for distinct purposes. For software
development, there is a specific programming language like Java, Python, C/C++, etc. The entire
process of software development isn’t as simple as its definition, it’s a complicated process.
Accordingly, it requires an efficient approach from the developer in the form of the Software
Development Life Cycle (SDLC).
SDLC specifies the task(s) to be performed at various stages by a software engineer/developer.
It ensures that the end product is able to meet the customer’s expectations and fits in the
overall budget. Hence, it’s vital for a software developer to have prior knowledge of this
software development process.

These 6 stages are discussed below.

1. Planning: In this stage, the team defines the problem and the requirements of the
software project. The goals and objectives of the project are also established, and a
high-level plan is created.

2. Analysis: In this stage, the team analyzes the requirements of the software project in
detail. This includes gathering and documenting requirements from stakeholders and
identifying any potential risks or challenges that may arise.

3. Design: In this stage, the team creates a detailed design of the software system. This
includes creating technical specifications, selecting software architecture and
frameworks, and developing a detailed plan for coding and testing.

4. Implementation: In this stage, the team begins to build the software system
according to the design created in the previous stage. This includes coding, unit testing,
integration testing, and debugging.
 5. Testing: In this stage, the team tests the software system thoroughly to ensure that it
meets the requirements and is free of defects. This includes functional testing,
performance testing, security testing, and user acceptance testing.

6. Deployment: In this stage, the team deploys the software system to the production
environment. This includes preparing the software for release, training users, and
ensuring that the system is ready for use.

7. Maintenance: In this stage, the team provides ongoing maintenance and support for
the software system. This includes addressing issues that arise after deployment,
releasing updates and patches, and ensuring that the system remains secure and
functional over time.

Conclusion :- Without using an exact life cycle model, the development of a software product
would not be in a systematic and disciplined manner. When a team is developing a software
product, there must be a clear understanding among team representative about when and what
to do. Otherwise, it would point to chaos and project failure.

EXPERIMENT-2
OBJECTIVE: Discuss SDLC Model a) Waterfall Model (b)RAD Model (c)Spiral
Model (d) V-Model (e) Agile Model

THEORY: A software life cycle model (also termed process model) is a pictorial and
diagrammatic representation of the software life cycle. A life cycle model represents all the
methods required to make a software product transit through its life cycle stages. It also captures
the structure in which these methods are to be undertaken.
There are several SDLC models used in software development. Here are the most popular ones:

a) Waterfall Model: The waterfall model is a sequential SDLC model that follows a linear
and structured approach to software development. The process starts with requirements
gathering, followed by design, implementation, testing, and deployment. Each phase of the
development process must be completed before the next one can begin. The waterfall
model is suitable for projects where the requirements are well-defined and changes are
unlikely to occur.

b) RAD Model: The Rapid Application Development (RAD) model is an iterative and
incremental SDLC model that focuses on rapid prototyping and feedback. It emphasizes on
customer involvement, prototyping, and quick delivery of software. The RAD model is
 suitable for projects that require a fast turnaround time and can accommodate changes in
requirements.

c) Spiral Model: The Spiral model is an iterative and incremental SDLC model that
combines elements of both waterfall and iterative development models. It emphasizes on
risk analysis and management, and the development process progresses in a series of
iterations. The Spiral model is suitable for large and complex projects where there is a high
degree of risk and uncertainty.

d) V-Model: The V-Model is a linear SDLC model that emphasizes on testing and verification
at each stage of the development process. It follows a sequential approach, where each
stage of the development process is paired with a corresponding testing phase. The V-
Model is suitable for projects where the requirements are well-defined, and testing is a
critical aspect of the development process.
 e) Agile Model: The Agile model is an iterative and incremental SDLC model that focuses on
flexibility, collaboration, and customer feedback. It emphasizes on continuous delivery,
quick adaptation to changing requirements, and a collaborative approach to software
development. The Agile model is suitable for projects where the requirements are
constantly evolving, and there is a need for frequent iterations and releases.

Conclusion :- Each SDLC model has its advantages and disadvantages, and the choice of model
depends on the project requirements and constraints. The selection of the appropriate model is
critical for the success of the software development project.

EXPERIMENT-3
OBJECTIVE: Explain the Role of QA in Software Quality Management

THEORY: QA (Quality Assurance) plays a critical role in Software Quality Management by

ensuring that the software development process is executed in a way that leads to high-quality
software products. The role of QA in Software Quality Management includes the following:

1. Defining Quality Standards: QA defines quality standards and guidelines for software
development. These standards and guidelines are used to ensure that the software meets
the required quality standards and that the development process is aligned with best
practices.

2. Reviewing Requirements: QA reviews the software requirements to ensure that they

are complete, clear, and concise. This helps to avoid misunderstandings and
misinterpretations that may lead to defects in the final product.

3. Testing: QA plays a crucial role in testing the software. This involves creating test plans,
test cases, and executing tests to ensure that the software meets the required functional,
performance, and security requirements.

4. Defect Management: QA is responsible for identifying and managing defects in the

software. This involves tracking, reporting, and prioritizing defects to ensure that they are
addressed in a timely and effective manner.

5. Continuous Improvement: QA ensures that the software development process is

continuously improved by identifying areas of improvement and implementing best
practices. This helps to ensure that the quality of the software is continuously improved
over time.
 6. Validation and Verification: QA validates and verifies the software to ensure that it
meets the required quality standards and that it is ready for release. This involves verifying
that the software meets the functional requirements, is secure, and is reliable.

Conclusion :- In summary, the role of QA in Software Quality Management is to ensure that the
software development process is executed in a way that leads to high-quality software products.
This is achieved by defining quality standards, reviewing requirements, testing, defect
management, continuous improvement, and validation and verification.

EXPERIMENT-4
OBJECTIVE: Define the ISO Standard in term of Software development

THEORY: The mission of the International Standard Organization is to market the

development of standardization and its related activities to facilitate the international
exchange of products and services. It also helps to develop cooperation within the
different activities like spheres of intellectual, scientific, technological, and economic
activity.

SO and IEEE are two of the most well-known international standards that enable software
businesses all around the globe better structure their operations by providing a well-defined and
effective framework.

ISO - International Organization for Standardization

IEEE - Electrical and Electronics Engineers

These standards are a list of principles and good practices that are used to help software companies
increase the quality of their services and organisation of processes to reach better results. The ISO is
a global standard-setting organization that spans sectors including software and food. ISO's major
purpose is to assist businesses to improve their processes and therefore their services by offering a
set of standards and norms to follow:
 ISO/IEC 12207 and ISO/IEC 15288 standards are the most important for software
development and can be replaced by each other, both referring to the Software life cycle
processes. Other standards that are relevant to software development:
 ISO/IEC 15939 (Software measurement process) specifies the activities and tasks that are
required to create, implement, and enhance the software measurement process. It doesn't
provide a list of software metrics or give tools for estimating the qualities of a software
product or process.
 ISO/IEC 14143 (Software measurement - Functional size measurement). Although
these standards are used to assist software development, they are unrelated to the current
issue and will not be discussed further.

ISO 12207 Software life cycle processes

ISO/IEC 12207 describes the following parts as:
 Software product - “The set of computer programs, procedures, and possibly associated
documentation and data.”
 Software service - “Performance of activities, work, or duties connected with a software
product, such as its development, maintenance, and operation.”
 System - “An integrated composite that consists of one or more of the processes, hardware,
software, facilities, and people, that provides a capability to satisfy a stated need or
objective.”
ISO/IEC 12207 standard establishes a framework for software life cycle procedures that spans all
stages of the software development life cycle, from conception through retirement. Primary life
cycle processes, supporting life cycle processes, and organizational life cycle processes are divided
into three categories in the framework. In each of these domains, relevant subprocesses are defined,
and specific actions are outlined for each subprocess.

ISO 12207 Compliance

Complying with ISO 12207 standard “is defined as the performance of all the processes, activities,
and tasks selected from this International Standard in the Tailoring Process ... for the software
project.” [ISO 12207].

An annex to the standard discusses how to modify ISO 12207 for a specific project. The first step is
to determine the project environment's attributes. Project criticality and team size may be factors.
All project stakeholders must be consulted on how the ISO 12207 procedure should be customized
to their specific project needs.

The project's methods, activities, and tasks should be selected based on this consultation. Not
described in ISO 12207 but included in the contract are processes, activities, and tasks. Also, record
who is accountable for each process, activity, or task. All customization decisions should be
documented with explanations.

To comply with ISO 12207, an organization must identify what procedures, actions, and tasks are
necessary to be performed in order to meet the standard's minimal requirements. Compliance can be
improved and discussed as the acquirer and supplier define the contract.

ISO 12207 in agile software development

As stated earlier, ISO 12207 is the most significant ISO standard for software engineering. This part
inspires and guides the adoption of the standard in an agile environment.

Regardless, we believe the question can be answered positively. Towards this end, we present
implementation recommendations that will ensure an agile-based project meets ISO 12207. These
rules are based on both the standard and the features of agile approaches.

One way to ensure an agile development team adheres to the ISO12207 standard is to delegate that
responsibility to one or more persons. Thus, this individual helps the team to develop the
appropriate artifacts in accordance with the standard.

To guarantee that developers, notable programmers, are not burdened by the documentation and
administrative chores required to comply with the standard, an organizational model similar to
Brooks's [Brooks 1995] is suggested. An administrator (who manages all administrative issues such
as resources and legalities), an editor (who ‘translates' the surgeon's documentation for general
usage), an administrator's secretary, an editor's secretary, and a program clerk (who maintains
changing artifacts through version and configuration control) make up this model of a so-called
Surgical Team (who is an expert on programming language usage and other specifications).

The above development team organization concept was proposed in the 1960s. While it may not be
applicable for some current software engineering projects, it does offer some important concepts.

The idea that programmers should be kept away from administrative activities and documentation is
worth examining. In an agile project, this means ensuring compliance with the ISO standards
specified should create the relevant documentation without burdening the developers. So the
documentation sub-team should collect data in a non-intrusive manner.

ISO 29119: Software Testing

The ISO 29119 set of standards outlines best practices for software and systems engineering,
including software testing. These best practices aren't tied to any particular development model, but
many of them resemble a V-model approach.

For software testing, ISO 29119 is divided into five sections:

 Testing based on keywords
 Documentation for testing
 Techniques and techniques for testing
 Definitions and concepts

The core tenet of ISO 29119 is that testing is the most important tool for risk mitigation and
avoidance. As a result, all of the standards use a risk-based approach and urge businesses to
concentrate on the most critical operations.

ISO 29119 in agile software development

In agile software development, the following questions frequently arise:
 Are you consistent with the needs of the ISO 29119 standards if you adopt agile
development best practices?
 In agile development, how do you implement the requirements of this family of standards?
 Evaluate the two process criteria to translate it to ISO 29119 agile development
 Evaluation process would be developed as a test model that outlines the atomic requirements
that must be completed before a user narrative is considered "done".
 Testing team contribute to burn-down and burn-up charts by running test cases to ensure
that each user story's acceptance requirements are satisfied. - The monitor (TMC2) activity,
task a, would be used to track the daily test execution progress. This task focuses on
gathering metrics to measure progress toward completion.
 The report activity would be used to report on the state of testing, including progress toward
testing on each user story.
What Are the Benefits of ISO Standards?
ISO forms a bridge that links the public and private sectors. Many of its member institutes are either
departments of their national governments or mandated by them. Other member organizations are
rooted solely in the private sector, having been set up by industry association partnerships within
their country. ISO helps these diverse bodies reach consensus on solutions that meet both the
requirements of business and the broader needs of society.

ISO standards help make the world a safer place and give consumers confidence that the products
they buy are safe, reliable, and of high quality. Regulators and governments count on ISO standards
to help develop better regulation, knowing they have a sound basis thanks to the involvement of
globally recognized experts.

Finally, compliance with ISO standards gives companies an advantage in the marketplace. ISO
certification provides assurance to potential customers that the company adheres to industry best
practices. In many industries, companies require that their suppliers are certified to certain relevant
ISO standards.

Conclusion :- The most important, undeniable benefits resulting from the implementation of ISO
standards are data security, greater reliability for clients, clear procedures and security of software
development lifecycle.

At SoftKraft we constantly work on making our full-cycle software product development ISO

compliant. With an ISO system in place, we benefit from regularly identifying and managing
current and future risks, thereby minimizing the impact of potential incidents.

EXPERIMENT-5

OBJECTIVE: Describe the concept of design pattern in details

THEORY:
A design pattern is a general repeatable solution to a commonly occurring problem in software
design. It is a way to capture and communicate best practices and expertise in software
development. Design patterns help developers to write code that is more modular, reusable, and
easy to understand.

Design patterns were first introduced in the 1990s by a group of software engineers known as the
"Gang of Four" (GoF) in their book "Design Patterns: Elements of Reusable Object-Oriented
Software." The book describes 23 design patterns that can be used in object-oriented programming
languages such as Java, C++, and Python.

Each design pattern has four essential elements:

1. Pattern name: A descriptive and memorable name for the pattern.

2. Problem: A description of the problem that the pattern solves.
3. Solution: A description of the elements that make up the pattern, their relationships,
responsibilities, and collaborations.
4. Consequences: A discussion of the benefits and trade-offs of using the pattern.

Design patterns are categorized into three types:

1. Creational patterns: These patterns provide a way to create objects while hiding the creation logic
from the client. Examples of creational patterns include Singleton, Factory Method, and Abstract
Factory.

2. Structural patterns: These patterns describe how objects can be composed into larger structures
while keeping the relationships between them flexible and maintainable. Examples of structural
patterns include Adapter, Facade, and Decorator.

3. Behavioral patterns: These patterns focus on communication between objects, and how they
collaborate to achieve common goals. Examples of behavioral patterns include Observer,
Command, and Template Method.
By using design patterns, developers can avoid reinventing the wheel and benefit from the
experience of others who have solved similar problems. Design patterns can also help to reduce the
complexity of software systems, making them easier to maintain, modify, and extend over time.

Conclusion:-
The most important, undeniable benefits resulting from the implementation of ISO
standards are data security, greater reliability for clients, clear procedures and security
of software development lifecycle.

At SoftKraft we constantly work on making our full-cycle software product

development ISO compliant. With an ISO system in place, we benefit from regularly
identifying and managing current and future risks, thereby minimizing the impact of
potential incidents.
NAME OF FACULTY: PRIYANKA PRADHAN
SIGNATURE:
DATE: