Professional Documents
Culture Documents
Spiral Model Is A Software Development Model Introduced by Barry Boehm To Decrease The
Spiral Model Is A Software Development Model Introduced by Barry Boehm To Decrease The
K19UWA19
Ans 1) Spiral model couples the iterative nature of the prototyping with the controlled and
systematic aspects of the linear sequential model.
Spiral model is a software development model introduced by Barry Boehm to decrease the
uncertainty at each stage of software development. This model incorporates features of both the
waterfall model and prototyping model. It is a risk-driven process model and its most important
feature is to decrease the risk of the project.
The Spiral model of software development is shown in fig. 1.1. The diagrammatic representation of
this model appears like a spiral with many loops. The exact number of loops in the spiral is not fixed.
Each loop of the spiral represents a phase of the software process.
For example, the innermost loop might be concerned with feasibility study. The next loop with
requirements specification, the next one with design, and so on. Each phase in this model is split into
four sectors (or quadrants) as shown in fig. 1.1. The following activities are carried out during each
phase of a spiral model.
Advantages
Risk management is easy in this type of model. When you are handling expensive and
complex projects, risk management is a must. Moreover, Spiral model has the ability to
make any software testing project transparent.
Customer can see and review the test and different stages
Projects can be separated into various parts to ease the management difficulty
Documentation control is strong in this type of methodology
Project estimate will tend to be more realistic as it progresses.
Disadvantages
Ans 2)
1)
Input- The user can search for any movies ,webseries etc
Output – The user will get the desired result of search for streaming movies,webseries or video etc
2)
Output- The user will get the different types of linked channels such asshemroo, playfix, eros
now,Hoichoi,sun nxt ,alt balaji ,voot etc for video related to these channels.
*Streaming search will share the same search bar with the torrent search.
*There will be a tick box to allow the user to choose to include video link searching in the search.
*Query to video link sites will retrieve the show’s name, episode name anda link to the webpage
itself.
*If no results are found on a search it will display a message “No results where found for these search.
*Performance- The system must be interactive and the delays involved must be less .So in every
action-response of the system, there are no immediate delays. In case of opening windows forms, of
popping error messages and saving the settings or sessions there is delay much below 2 seconds, In
case of opening databases, sorting questions and evaluation there are no delays and the operation is
performed in less than 2 seconds for opening ,sorting, computing, posting > 95% of the files. Also
when connecting to the server the delay is based editing on the distance of the 2 systems and the
configuration between them so there is high probability that there will be or not a successful
connection in less than 20 seconds for sake of good communication.
*Safety -Information transmission should be securely transmitted to server without any changes in
information It may leads to the hacking of accounts and illegal using of account
Ans a)
1)Incomplete Requirement
2)Inconsistence Requirement
Ex- When you watch movies or videos so much advertisement with reqular interval
3)Ambigous Requirement
4) Contradictory Requirement
Ex- When you download video you can only see by opening app then watch video can’t share with
friends
Ans b) We use Prototyping model in a data entry system for office staff that has never used
computers before. The user interface and user-friendliness are extremely important.
A prototype is a toy implementation of the system. A prototype usually exhibits limited functional
capabilities, low reliability, and inefficient performance compared to the actual software. A prototype
is usually built using several shortcuts. The shortcuts might involve using inefficient, inaccurate, or
dummy functions. The shortcut implementation of a function, for example, may produce the desired
results by using a table look-up instead of performing the actual computations. A prototype usually
turns out to be a very crude version of the actual system.
Developer considers the feedback given by the customer and modifies the prototype according
to their demand. After modification, the prototype is demonstrated to the customer for evaluation.
The customer again evaluates the prototype and provide the feedback on which developer again
modifies the prototype.
These iterations continue until the customer is satisfied with the prototype. At each iteration, the
prototype undergoes different phases which we will discuss in the further section. Once the customer
is satisfied with the prototype developers start developing the software and then deliver it to the
customer.
At this stage, the developers communicate with the customer to gather the customer’s requirement.
The objective of the software and the area where the definitions are still fuzzy are outlined. The
requirements which are clear and perfectly known are also outlined.
Analysing the customer requirements, the developers proceed to construct the prototype.
2. Construct Prototype
While constructing prototype the developers establish objectives such as what will be the use of
prototype? What features of the final system the prototype would reflect? It is taken into
consideration that the cost of the developed prototype should be low and the speed of prototype
development should be fast.
The speed and cost of the prototype are maintained by ignoring the requirements that have nothing
to do with the customer’s interest. Generally, the prototypes are developed based on the
requirements of customer’s interest like user interface and unclear functions and so on.
3. Customer Evaluation
Once the prototype of a final software is developed it is demonstrated to the customer for evaluation.
Customer evaluates the prototype against the requirements they have specified in the communication
phase. If the customers are satisfied, then the developers start developing the complete version of the
software.
In case, the customer is not satisfied with the prototype, they are supposed to suggest modifications.
4. Iterate Prototype
Based on the modifications suggested by the customer, developers start modifying the prototype and
the modified prototype is again demonstrated to the customer for evaluation.
In this way, the prototype is iterated until the customer is satisfied with the prototype. Once the
customer is satisfied with the prototype the developers get engaged in developing the complete
version of the software.
5. Deploy Software
Once the objective of the prototype is served it is thrown and the software is developed using other
process models. The main objective of the prototype is to understand the customer’s requirement
properly and completely.
As all the requirements are now understood, the developers develop the software and deliver it to the
customer with the expectation that the developed software meets all the requirements specified by
the customer.