EXPERIMENT NO.

-01

AIM: Study various phases of Software Engineering & types of Models used.

Objective: To get familiar with models used for software engineering.

Theory:
Basically, Software engineering process has following phases:
1) Analysis Phase - Requirements Development - Requirement Management
2) Planning Phase - Project Planning - Risks Management
3) Design Phase - Technical Solution
4) Development Phase - Coding
5) Verification and Validation phase - Testing – Reviews
6) Implementation Phase - Product Integration
7) Maintenance Phase - Project Control

Planning Stage

The planning stage (also called the feasibility stage) is exactly what it sounds like:
the phase in which developers will plan for the upcoming project.
It helps to define the problem and scope of any existing systems, as well as
determine the objectives for their new systems.

Analysis Stage
The analysis stage includes gathering all the specific details required for a new
system as well as determining the first ideas for prototypes.
Developers may:

 Define any prototype system requirements

 Evaluate alternatives to existing prototypes
 Perform research and analysis to determine the needs of end-user’

Design Stage

The design stage is a necessary precursor to the main developer stage.

Developers will first outline the details for the overall application, alongside
specific aspects, such as its:

 User interfaces
 System interfaces
 Network and network requirements
 Databases
Development Stage
The development stage is the part where developers actually write code and build
the application according to the earlier design documents and outlined
specifications.
Programming languages can include staples such as C++, PHP, and more..

Testing Stage

Now it must be tested to make sure that there aren’t any bugs and that the end-user
experience will not negatively be affected at any point.
During the testing stage, developers will go over their software with a fine-tooth
comb, noting any bugs or defects that need to be tracked, fixed, and later retested.

Implementation and Integration Stage

After testing, the overall design for the software will come together. Different
modules or designs will be integrated into the primary source code through
developer efforts, usually by leveraging training environments to detect further
errors or defects.

Maintenance Stage
The SDLC doesn’t end when software reaches the market. Developers must now
move into a maintenance mode and begin practicing any activities required to
handle issues reported by end-users.

Role of System Analyst

An SDLC’s system analyst is, in some ways, an overseer for the entire system.
They should be totally aware of the system and all its moving parts and can help
guide the project by giving appropriate directions.
The system analyst should be:

 An expert in any technical skills required for the project

 A good communicator to help command his or her team to success

Most popular and widely used models are

-Waterfall model
-Spiral model
-Open source software Development
-Prototyping-Increment development
-Unified process
-Agile process
 EXPERIMENT NO.-02

Title : Studying Various phases of Water-Fall Model.

Objective : To get familiar with basic model used for software engineering.

Pre-requisite : Knowledge of Characteristics of software, process, project.

Theory:
It is a process model also called as “classic life cycle”, which has 5 phases:-
_ Requirement gathering
_ Requirement analysis
_ Design
_ Coding
_ Testing and maintenance
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."

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 .

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 .
 EXPERIMENT NO.-03

Title Prepare SRS for Banking or On line book store domain problem.

Objective To get familiar with preparing a document which is used before starting
the project.

Prerequisite Knowledge of Various process models. keys.

Theory

The Software requirements specification is produced as culmination of

the analysis task which contains:-

 Introduction
Goal & Objectives of Software
 Information Description
Problem Description
Information Flow
Hardware Interface
 Functional Description
Process Narrative for each function
 Design Constraints
Performance Characteristics
Behavioral Description
Validation Criteria
 EXPERIMRNT NO-04

Title Study different software engineering standards (CMMI,ISO)

Objective To get familiar with software engineering standards

References Software Engineering Roger Pressman McGraw Hill Fifth edition

Software Engineering Ian Somerville Pearson Education Sixth edition

Prerequisite Knowledge of software Industries

Theory

The Software requirements specification is produced as culmination of

the analysis task which contains:-

 Introduction
Goal & Objectives of Software
 Information Description
Problem Description
Information Flow
Hardware Interface
 Functional Description
Process Narrative for each function
 Design Constraints
Performance Characteristics
Behavioral Description
Validation Criteria
 EXPERIMENT NO-05

Title Using COCOMO model estimate effort for Banking or Online book
store domain problem

Objective To get familiar with estimation and comparing various estimation

techniques.

References Software Engineering Roger Pressman McGraw Hill Fifth edition

Software Engineering Ian Somerville Pearson Education Sixth edition

Pre-requisite Knowledge of estimation techniques.

Theory
COCOMO is an open model, which includes
The underlying cost estimation equations,
Every assumption made in the model,
Every definition,
The costs included in an estimate are explicitly stated. The most fundamental
calculation in the COCOMO model is the use of the Effort Equation to estimate the
number of Person-Months required to develop a project. The COCOMO II model
makes its estimates of required effort (measured in Person-Months � PM) based
primarily on your estimate of the software project's size
Effort = 2.94 * EAF * (KSLOC)E Where, EAF Is the Effort Adjustment Factor
derived from the Cost Drivers E Is an exponent derived from the five Scale Drivers
Duration = 3.67 * (Effort)SE
 EXPERIMENT NO-07

Title : Analyze the Risk related to the project and prepare RMMM plan.

Objective To study types of risk and preparing RMMM plan.

References Software Engineering Roger Pressman McGraw Hill Fifth editioN

Pre-requisite

Knowledge of software Analysis,Risk analysis.

Theory

Risk analysis and management are a series steps that help a software team to
understand uncertainty.

Types of Risks

1. Technical risks.

2. Business risks.

3. Project risks.

Risk table

risk id Category Probability Criticality RMMM

1 TE 0.7 2 1
 EXPERIMENT NO-08

Title : Develop Time-line chart and project table using PERT or CPM project
scheduling methods.

Objective To study project scheduling and tracking

References Software Engineering Roger Pressman McGraw Hill Fifth edition

Software Engineering Ian Somerville Pearson Education Sixth edition

Prerequisite

Knowledge of

_ Project and project scheduling.

_ Task set for the software project.

_ Adaptation criteria.

Theory

PERT and CPM are project scheduling methods that can be applied to
software development. Both techniques are driven by information already
developed in earlier project planning activities:

1. estimates of effort.

2. A decomposition of the product function.

3. The selection of the appropriate process model

4. Decomposition of tasks.

When creating a software project schedule, the planner begins with a

set of tasks(the work breakdown structure).

 EXPERIMENT NO-09
Title Draw E-R diagram,DFD,CFD and STD for the project.

Objective To understand actual system using analysis model.

References Software Engineering Roger Pressman McGraw Hill Fifth edition

Software Engineering Ian Somerville Pearson Education Sixth edition An Integrated
Approach To Software Engineering Pankaj Jalote

Narosa

Pre-requisite

Knowledge of Analysis model-data modeling, functional modeling and

behavioral model.

Theory

Analysis model is first technical representation of the system. This model

consists of data dictionary as its core, then followed by three diagrams E-R
diagrams, data flow diagram, and state-transition diagram. All these diagrams are
part of functional model.
 EXPERIMENT NO-10
Title Design of the test cases.

References Software Engineering Roger Pressman McGraw Hill Fifth edition

Software Engineering Ian Somerville Pearson Education Sixth edition An Integrated
Approach To Software Engineering Pankaj Jalote

Narosa

Objective To understand various testing techniques.

Pre-requisite

Knowledge of Various Testing strategies

Theory

Testing begins “in the small” and progresses “to the large”.The early testing
focuses on a single component and applies white- and blackbox tests to uncover
errors in program logic and function. After individual components are tested they
must be integrated. Testing

continues as the software is constructed. Finally, a series of high order tests are
executed once the full program is operational.