1.5.

1 Umbrella Activities

QExplain Umbrella activities of software engineering MU Dec. 19,4 Marks

generic view of software engineering (Fig. 1.5.1:

The framework described in A software process) is

complemented by number of Umbrella activities. Typical umbrella activities are:

1. Software project tracking and control

Developing team has to assess project plan and compare with predefined schedule.
 Introduction To Software Engineering
1-6
Software Engineering (MU) actions
are taken to maintain the
necessary
vredefined
schedule,
doesn't match with
POect plan
schedule.

2. Risk management outcOmes.

Hence
unwantea
causes some
happens, it
that or may not occur, But if that event
E e n t
may
proper management of risk is required.

3. Software Quality Assurance (SQA)

required to give guarantee of
of activities those
are

A 1S nothing but planned and systematic pattern

software quality.
of development to find
are conducted in every stage
For example during software development, meetings
out defects and suggest improvement to yield good quality software.

4. Formal Technical Reviews (FTR)

meeting is to detect quality problems and

FTR IS a meeting conducted by technical staff. The purpose of

suggest improvements.
customer exactly wants.
T h e technical staff focuses on quality from customer's point ofview, i.e. what

5. Measurement

It includes the efforts required to measure the software.

Software can not be measured directly. It is measured by some direct measures (e.g. cost, lines of code, size
measured in terms of other factors.
of software etc) and indirect measures (e.g. quality of software, which is
Hence it is an indirect measure ofsoftware.)

6. Software Configuration Management (SCM)

It manages the effects of change throughout the software process.

7. Reusability management
It defines criteria for product reuse.

If software components developed for certain application can be used in development of other applications,
then it's good quality software.

8. Work product preparation and production

It includes the activities required to create documents, logs, forms, lists and user manuals for developed

software.

1.6 Capability Maturity Model (CMM)

a. Explain the process of CMM.

MU- May 19, 10Marks

Tech Knouo
P u a i c a t i e a
2.3.2 The Spiral Model
MU-Dec. 17, 10 Marks
development.
With neat diagram explain the Spiral
model of software MU May 19, 5 Marks
a. a

Differentiate in between waterfall and spiral mode.

a.
iterative prototyping It yields rapid
waterfall model and
model is combination of well known
The Spiral
version of software.
development of m o r e complete initial releases, it may be
releases. During the
series of evolutionary
model software is developed as
Using spiral towards more completed stage.
later releases the version goes
prototype. But during
just paperwork or Planning
Estimation
Scheduling
Risk analysis

Modeling
Communication Analysis
Design

Deployment
Construction
Code
Delivery Test
Feedback

Model
Fig. 2.3.2: The Spiral
of the application from concept
The spiral model can be adopted to apply throughout the entire lifecycle
model is divided into set of framework
activities defined by software
development to maintenance. The spiral
one segment of spiral as shown in Fig.
2.3.2.
engineer team. Each framework activity represents
spiral of the model
of circle and developed in clockwise direction. Each
The initial activity is shown from centre

includes following steps

1. Communication

The software development process starts with communication between customer and developer.

2. Planning
It includes complete estimation (e.g. cost estimation of project) and scheduling (complete timeline chart T

project development) and risk analysis.

PUDirationd
 Software Engineering (MU) 2-13 Process Models

3. Modelling

It includes detail requirement analysis and project design (algorithm, flowchart etc).
Flowchart shows complete pictorial flow of program whereas algorithm is step by step solution of problem.

4. Construction

It includes coding and testing steps:

0 Coding: Design details are implemented using appropriate programming language

carried out.
(t) Testing: Testing is
5. Deployment

It includes software delivery, support and feedback from customer. If customer suggest some corrections,
or

demands additional capabilities then changes are required for such corrections or enhancement.

Note that after customer evaluation, next spiral implements, 'customer's suggestions' plus 'enhancement
plan'. Thus, each of iteration around the spiral leads to more completed version of software

1. Merits / Advantages
(1) In this approach, project monitoring is very easy and more effective compared to other models

(2) It reduces the number of risk in software development before they become serious problems.

(3) It is suitable for very high risk projects.

(4) Project estimates i.e. schedule and cost is more realistic.

(5) Risk management is in-built feature of spiral model.

(6) Changes can be accommodated in the later stages ofdevelopment

2. Demerits / Disadvantages

() If major risk is not discovered in early iteration of spiral, it may become a major risk in later stages.

(2) Each iteration around the spiral leads to more completed version of software. But it's difficult to convince
(especially in contract situation) to the customer that the model is controllable.

(3) Cost of this approach is usually high.

(4) It is not suitable for low risk projects.

(5) Rules and protocols must be followed very strictly to implement the approach.
 Waterfall Model Spiral Model
No.

The spiral model is

The Waterfall model
1. a lot more
is simple and easy.
complex.
While the spiral
The waterfall model
model works in the
2. works in a
sequential method.
evolutionary
method.

In the waterfall
model errors or In the spiral model
risks are identified errors or risks are
3 and rectified after identified and
the completion of rectified earlier.
stages.
The waterfall model While the spiral
4. is adopted by model is adopted
customers. by developers.
The waterfall model While the Spiral
5. is applicable for model is used for
small projects. large projects.
While in spiral
model
In waterfall model
requirements and
requirements and
6. early stage
early stage planning
is necessary.
planning is
necessary if
aaniod
4. is adopted by model is adopted
customers. by developers.
The waterfall model While the Spiral
5. is applicable for model is used for
small projects. large projects.
While in spiral
model
In waterfall model
requirements and
requirements and
6. early stage
early stage planningg
is necessary.
planningis
necessary if
required.
Flexibility to
Flexibility to change change in spiral
7. in waterfall model is
model is not
Difficult.
Difficult.
There is high There is low
8. amount risk in amount risk in
waterfall model. spiral model.

Waterfall model is While cost of spiral

9. comparatively model is very
inexpensive. expensive.
Customer In the Spiral Model
involvement is Customer
10.
minimum in involvement is
Waterfall Model high.
It requires least It requires typical
 waterfall model. spiral model.

Waterfall model is While cost of spiral

9. comparatively model is very
inexpensive. expensive.
Customer In the Spiral Model
involvement is Customer
10.
minimum in involvement is
Waterfall Model high.
It requires least It requires typical
11.
maintenance. maintenance.

It is based on linear
It is based on linear
12. and iterative
framework type.
framework type.
Testing is done
Testing is done after after the
the coding phase in
13.
the development life
engineering phase
in the development
cycle.
cycle.
To a certain extent,
Reusability is
14 reusability is
extremely unlikely. possible.

Customers have
Customer control
control over the
over the
15. administrator as
administrator is
Compared to
very limited.
waterfall model.
3.1 Agile Process Model

Q. What is Agile Methodology? MU-May 15,Dec.19,4Marks

Q. What is agility in context of software Engineering? MU- Dec. 15, May 17, 5 Marks
Q. What are Agile Processes ? MU- May 16, 5 Marks
a. Write short note on Agile Methodology MU- Dec. 16, 10 Marks
Q. Write short note on Agile Process Models. MU- May 18, 10Marks
An agile process model includes the concept of development along with a set of guidelines necessary for the
development process. The conceptual design is necessary for the satisfaction of the customer. The concept is also
necessary for the incremental delivery of the product. The concept or the philosophy makes development task
simple. The agility team must be highly motivated, updated with latest skill sets and should focus on
development simplicity.
We can say that agile development is an alternative approach to the conventional development in certain

projects.
The development guidelines emphasize on analysis and design activities and continuous communication

between developers and customers. An agile team quickly responds to changes. The changes may be in
development, changes in the team members, and changes due to new technology. The agility can be applied to
any software process. It emphasizes rapid delivery of operational software.

All the agile software processes should address three important assumptions
o Difficult to predict in advance software requirements
Design and construction are interleaved in most of the projects, it is dificult to predict design before
constructíon.

Analysis,
O
design, construction and testing are not mueh predictable
To address these assumptions of unpredictability, the agile development process must be adaptable. So an agile
process must adapt incrementally.
 VASANTDADA PATIL PRATISHTHAN'S
COLLEGE OF ENGINEERING AND VISUAL ARTS Page No.

5Expluin unctional_point ehimuhon n detuk

hoFPAhrovides a stundandiged mtthod to hunttiantlly aige Ha otuane wor

broebrodu . Tho work_þrodut He outhut h aoftsuat n dwtdopment_and
imbrovement_proje hor oubotquent releaseo J io hi aohwane hut i relocatetd
te produ chion apblication at þejcok implewentaion muunen tunchonalit4-
nom te wens_þoint eh viuw ie On He busio awhat ts wen ttucato und
receiveo in return
FPA a metihad or sek rules e Fun hon Size mensurtnmnt. uenes
Hunhonulhy delivened b to ue bwed on_the wen's exteanal vi e_
encionul reguiremenbh mcaura alagiaal vits an upplirehin
not phyin.ally implem.cnted vis o r th intennal technitwl vi
Funhion boint nulspia tehnique i wed o anlyze theunthonuluhy
deli vened_by 1o/twune _and unudjwted_funthon_þoint (UFP) He_unt
mwurmnt.

Objtt vea FPA

T objechv_FPA b muuwne te funchiontlih thut te wen rtguota cnd
recev
|Te objechive d FPA to mewune wlhwure developrment and mainttnunce
indehendently the teehnolayy_we hor imblementah on.

wsunn
Extennal inpu quenit
ILP
(Userp Hnttmat togrt- Etnak-ntengaa
Exttnnl outhus file) pile
lyp e FPA
Trans cuchon Funchonal Iupe -
Extenna Input E ): El þrocmes datu ov_wnrol inhmuhion hat corn
nn outoide the uphlicathion 's bouneluny 7he El an thmntury_þroen
Exfemal utput_ (EO): EO n clementuy_þro en hu qenenutes dauta or
wntrol inhomuron nt outoide He bblicahions boundurq
lui. Extennul Inguirito (EQ) E9 _aun elem tntury_þrocm made v n
input -outhut wmbinurion thu rubth in dau rctriewal

Detu Funchional lyh

i Inttnnul Loical Eile (/LF):Awn idenihiable graup_logicol related
edaru or ontrol inhor muhon uintuined within He boundans eh the
ehblicumon
i Extend Itentuu Fu CEIF): A_group _e wen reuwanizable_logicall
vdated dutu ullpion to t eltwane but maintuned wrthiun t bouncdary_
onothen soltwane