Dr.

Sunil Khilari

Chapter-1
Introduction to Development Approach
SSAD and OOAD

Dr.Sunil Khilari
 Dr.Sunil Khilari

2
Objectives :
1.Overview of Software Development with SSAD
2.Basic System Development Life Cycle with different users and their role in
SDLC.
Different Approaches and Models for System Development.
3.1 Waterfall Model
3.2 Spiral Model
3.3 Prototyping Model
3.4 RAD
3.5 Rational Unified Process
SSADM divides anKhilari
Dr.Sunil application development project into modules, stages, steps and tasks. It provides a framework for
describing a project in a way that's suited to managing it.
3
SSADM's objectives are to do the following:

• improve project management and control;

• make more effective use of experienced and inexperienced
development staff;
• develop better quality systems;
• make projects resilient to the loss of staff;
• enable projects to be supported by computer-based tools such as
computer-aided software
engineering systems (CASE); and
• Establish a framework for good communications among project
participants.
Stages in SSADM :-
Dr.Sunil Khilari
1. Feasibility stage :A feasibility study investigates the goals and implications of a project to determine whether the project is
achievable. There are four main areas considered in a feasibility study.
4 feasibility study to determine if the project is
i. A technical
technically possible. 2. Requirements analysis :This step investigates the current
ii. Organizational feasibility to evaluate whether the project is environment and examines existing business systems to see what
modifications are needed. This includes a cost-benefits analysis of
compatible with existing systems.
business system options and the potential effect of the new system on
the organization and employees.
3. Definition of requirements. The requirements specification for
the new system may include a look at the life histories of the entities
involved, user role and function matrices, and process identity
modelling, data catalogues and correspondence diagrams.
4. Logical system specification. This step consists of two stages:
Technical system options define possible implementation methods and
components, such as staffing costs, the type of software and hardware
required physical limitations of the area that houses the system and
requirements for the human-computer interface. At the end of this
stage, a technical system option is chosen.
5. Physical design. The system's logical specifications are matched
to physical architecture. The function and structure of the database
component is specified based on outputs from the logical design and
technical system option steps.
 System Development Life Cycle (SDLC):-
Dr.Sunil Khilari
• The System Development Life Cycle, "SDLC" for short, is a multistep, iterative process, structured in a methodical way. It
consists of Seven stages namely Planning , Analysis , Design, Development , Testing , Implementation , Maintenance.
5
Stages In SDLC :-
1. Planning
This is the first phase in the systems development process. It identifies whether or not
there is the need for a new system to achieve a business’s strategic objectives.
This is a preliminary plan for a company’s business initiative to acquire the resources to
build on an infrastructure to modify or improve a service.
The purpose of this step is to find out the scope of the problem and determine solutions.
Resources, costs, time, benefits and other items should be considered at this stage.
2. Systems Analysis and Requirements
The second phase is where businesses will work on the source of their problem or the
need for a change. This is where teams consider the functional requirements of the
project or solution. It is also where system analysis takes place—or analysing the needs
of the end users to ensure the new system can meet their expectations.
There are several tools businesses can use that are specific to the second phase. They include:
i. CASE (Computer Aided Systems/Software Engineering)
ii. Requirements gathering
iii. Structured analysis
3. Systems Design
The third phase Dr.Sunil
describes,
Khilari in detail, the necessary specifications, features and operations that will satisfy the functional requirements of
the proposed system which will be in place.
This is the step for end users to discuss and determine their specific business information needs for the proposed system. It’s during this
6
phase that they will consider the essential components (hardware and/or software) structure (networking capabilities), processing and
procedures for the system to accomplish its objectives.
4. Development
The fourth phase is when the real work begins—in particular, when a programmer, network engineer and/or database developer are
brought on to do the major work on the project.
This work includes using a flow chart to ensure that the process of the system is properly organized. The development phase marks the
end of the initial section of the process. Additionally, this phase signifies the start of production. The development stage is also
characterized by instillation and change.
5. Integration and Testing
The fifth phase involves systems integration and system testing . Testing may be repeated, specifically to check for errors, bugs and
interoperability. This testing will be performed until the end user finds it acceptable.
Another part of this phase is verification and validation, both of which will help ensure the program’s successful completion.
6. Implementation
The sixth phase is when the majority of the code for the program is written. Additionally, this phase involves the actual installation of
the newly-developed system. This step puts the project into production by moving the data and components from the old system and
placing them in the new system via a direct cutover.
While this can be a risky (and complicated) move, the cutover typically happens during off-peak hours, thus minimizing the risk.
7. Operations and Maintenance
The seventh and final phase involves maintenance and regular required updates. This step is when end users can fine-tune the system, if
they wish, to boost performance, add new capabilities or meet additional user requirements.
 WATERFALL MODEL :-
Dr.Sunil Khilari
• Waterfall Model is a sequential model that divides software development into pre-defined phases.
• It was introduced in 1970 by Winston Royce.
7 must be completed before the next phase can begin with no overlap between the phases. Each phase is designed for
• Each phase
performing specific activity during the SDLC phase.

When to use SDLC Waterfall Model?

Waterfall Methodology can be used when:

• Requirements are not changing frequently

• Application is not complicated and big
• Project is short
• Requirement is clear
• Environment is stable
• Technology and tools used are not dynamic and is stable
• Resources are available and trained
 SPIRAL MODEL:-
Dr.Sunil Khilari
Spiral Model is a risk-driven software development process model. It is a combination of waterfall model and iterative
model. Spiral Model helps to adopt software development elements of multiple process models for the software project
8
based on unique risk patterns ensuring efficient development process.

• Each phase of spiral model in software engineering begins

with a design goal and ends with the client reviewing the
progress. The spiral model in software engineering was
first mentioned by Barry Boehm in his 1986 paper.

• The development process in Spiral model in SDLC starts

with a small set of requirement and goes through each
development phase for those set of requirements. The
software engineering team adds functionality for the
additional requirement in every-increasing spirals until the
application is ready for the production phase.
PROTOTYPING MODEL:-
Dr.Sunil Khilari
• Prototyping Model is a software
9 development model in which
prototype is built, tested, and
reworked until an acceptable
prototype is achieved. It also
creates base to produce the final
system or software.

• It works best in scenarios where

the project’s requirements are not
known in detail. It is an iterative,
trial and error method which takes
place between developer and
client.
RAD Model :-Dr.Sunil Khilari

• Rapid Application Development model is a software development process based on

10
prototyping without any specific planning.
• In RAD model, there is less attention paid to the planning and more priority is given to the
development tasks. It targets at developing software in a short span of time.
Rational Unified Process (RUP):-
Dr.Sunil Khilari
• Rational Unified Process is a software development process for object-oriented models. It is
also known as the Unified Process Model. It is created by Rational Corporation and is designed
and 11
documented using UML (Unified Modelling Language).
• This process is included in IBM Rational Method Composer (RMC) product. IBM
(International Business Machine Corporation) allows us to customize, design, and personalize
the unified process.
• RUP is proposed by Ivar Jacobson, Grady Bootch, and James Rambaugh.
Steps Involved In RUP :-
Dr.Sunil Khilari
Inception :-
• Communication and planning are the main ones.
12
• Identifies the scope of the project using a use-case model allowing managers to estimate costs and time required.
• Customers’ requirements are identified and then it becomes easy to make a plan for the project.
Elaboration :-
• Planning and modelling are the main ones.
• A detailed evaluation and development plan is carried out and diminishes the risks.
• Revise or redefine the use-case model (approx. 80%), business case, and risks.
Construction :-
• The project is developed and completed.
• System or source code is created and then testing is done.
Transition :-
• Transit the project from development into production.
• Beta testing is conducted.
Production :-
• The final phase of the model.
• The project is maintained and updated accordingly.
 Dr.Sunil Khilari

13

THANK YOU