Subjects
Applied Mathematics for Electrical Engineering - 3130908
Complex Variables and Partial Differential Equations - 3130005
Engineering Graphics and Design - 3110013
Basic Electronics - 3110016
Mathematics-II - 3110015
Basic Civil Engineering - 3110004
Physics Group - II - 3110018
Basic Electrical Engineering - 3110005
Basic Mechanical Engineering - 3110006
Programming for Problem Solving - 3110003
Physics Group - I - 3110011
Mathematics-I - 3110014
English - 3110002
Environmental Science - 3110007
Software Engineering - 2160701
Data Structure - 2130702
Database Management Systems - 2130703
Operating System - 2140702
Advanced Java - 2160707
Compiler Design - 2170701
Data Mining And Business Intelligence - 2170715
Information And Network Security - 2170709
Mobile Computing And Wireless Communication - 2170710
Theory Of Computation - 2160704
Semester
Semester - 1
Semester - 2
Semester - 3
Semester - 4
Semester - 5
Semester - 6
Semester - 7
Semester - 8
Software Engineering
(2160701)
SE-2160701
Winter-2017
Question-4b
BE | Semester-
6
Winter-2017
|
11/03/2017
Q4) (b)
4 Marks
Explain the process model which is normally suits for development of large-scale software system.
The spiral model is suitable for normally suits for development of large-scale software system.
(Figure: Spiral Model)
The Spiral model is an evolutionary process model that couples iterative nature of prototyping with the controlled and systematic aspects of waterfall model
It provides the potential for rapid development.
Software is developed in a series of evolutionary releases.
Early iteration release might be prototype but later iterations provides more complete version of software.
It is divided into framework activities. Each activity represent one segment of the spiral
Each pass through the planning region results in adjustments to
the project plan
Cost & schedule based on feedback
When to use Spiral Model?
For development of large scale / high-risk projects.
When costs and risk evaluation is important.
Users are unsure of their needs.
Requirements are complex.
New product line.
Significant (considerable) changes are expected.
Advantages
High amount of risk analysis hence, avoidance of Risk is enhanced.
Strong approval and documentation control.
Additional functionality can be added at a later date.
Software is produced early in the Software Life Cycle.
Disadvantages
Can be a costly model to use.
Risk analysis requires highly specific expertise.
Project’s success is highly dependent on the risk analysis phase.
Doesn’t work well for smaller projects.
Questions
Go to Question Paper
Q1
(a)
(b)
(c)
Q2
(a)
(b)
(c)
(c)
(OR)
Q3
(a)
(b)
(c)
Q3
(a)
(OR)
(b)
(OR)
(c)
(OR)
Q4
(a)
(b)
(c)
Q4
(a)
(OR)
(b)
(OR)
(c)
(OR)
Q5
(a)
(b)
(c)
Q5
(a)
(OR)
(b)
(OR)
(c)
(OR)