Describe spiral model with its advantages and disadvantages.

-

Spiral Model

- The spiral model, also known as the spiral lifecycle model or Boehm's model was introduced by Barry Boehm in 1988. It is a system development model based on process iteration. 

- This model of development combines the features of the prototyping model and the waterfall model in order to eliminate almost every possible/ known risk factor from it. 

- This model follows a spiral process as the development of the software takes place. 

- In this model, the development of each modified version of the system prototype is carefully designed using the steps of the waterfall model. 

- Starting from the center of the spiral process, and moving outward in the spiral route, each iteration helps to build a more complete version of the system in a progressive manner. 

- The spiral model is similar to the incremental model, with more emphasis placed on risk analysis.

 

# The spiral model has the following major phases:



1. Customer Communication: In this step, effective communication is established between developer and customer to identify the customer requirements.

2. Planning: In this phase, the objectives, alternatives, and constraints of the projects are determined and are documented. The objectives and other specifications are fixed in order to decide which strategies to follow during the project life cycle.

3. Risk analysis: This is the most important phase of the spiral model in this phase all possible alternatives, which can help in developing a cost effective project are analyzed and strategies are decided to use them. This phase has been added especially in order to identify and resolve all the possible risks in the project development. A prototype is produced at the end of the risk analysis phase to proceed with available data.

4. Engineering: In this phase, the actual development of the project is carried out. The output of this phase is passed through all the phases iteratively in order to obtain improvements in the same. 

5. Construction and release: Tasks required constructing, testing, installing, and providing user support (e.g., documentation and training).

6. Customer evaluation: In this phase, the developed product is passed onto the customer in order to receive customer comments and suggestions which can help in identifying and resolving potential in the developed software. This phase is much similar to the testing phase. This phase allows the customer to evaluate the output of the project to date before the project continues to the next spiral.


Advantages of Spiral Model

- High amount of risk analysis hence, avoidance of Risk is enhanced.

- Good for large and mission-critical projects.

- Strong approval and documentation control.

- Additional Functionality can be added at a later date.

- Software is produced early in the software life cycle.


Disadvantages of Spiral Model

- 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.


When to use the Spiral model

- When costs and risk evaluation is important It is used for medium to high-risk projects

- When users are unsure of their needs

- When requirements are complex It is used when significant changes are expected (research and exploration)


Comments

Post a Comment

Popular posts from this blog

Suppose that a data warehouse for Big-University consists of the following four dimensions: student, course, semester, and instructor, and two measures count and avg_grade. When at the lowest conceptual level (e.g., for a given student, course, semester, and instructor combination), the avg_grade measure stores the actual course grade of the student. At higher conceptual levels, avg_grade stores the average grade for the given combination. a) Draw a snowflake schema diagram for the data warehouse. b) Starting with the base cuboid [student, course, semester, instructor], what specific OLAP operations (e.g., roll-up from semester to year) should one perform in order to list the average grade of CS courses for each BigUniversity student. c) If each dimension has five levels (including all), such as “student < major < status < university < all”, how many cuboids will this cube contain (including the base and apex cuboids)?

-
Image
a) A Snowflake Shema is shown in figure below: b) The specific OLAP operations to be performed: 1. Roll-up on course from course_id to department. 2. Roll-up on a student from student_id to university. 3. Dice on course, student with department ="CS" and university = "biguniversity" 4. Drill-down on a student from the university to student_name. c) N = 4 dimensions The cube will contain 54 = 625 cuboids.
Read more

Describe how cloud computing technology can be applied to support remote ECG monitoring.

-
Image
  Healthcare: ECG (Electrocardiogram) Analysis in cloud computing Healthcare is a field, subject, sector, or territory in which information technology has several uses. These apps are being used to aid businesses in supporting scientists in developing disease prevention solutions. Cloud computing has emerged as an appealing alternative for constructing health monitoring systems as a result of the development of the Internet or to put it another way, as a result of the availability of the internet. The ECG machine, for example, is a health monitoring device that measures the human body's heartbeat and prints the results on graph paper. The electrocardiogram (ECG) measures the electrical activity of the heart's Cardium. A waveform is created as a result of this action, which is repeated throughout time and symbolizes the heartbeat.  The analysis of the shape is used to identify arrhythmias, and it is the most common way of detecting heart diseases. Here the meaning of arrhythmias
Read more

Explain market-Oriented Cloud computing architecture.

-
Image
  Market Oriented Cloud Computing (Mocc) As customers rely on Cloud providers to cover all of their computing needs, they will expect certain Qe from their providers to fulfill their objectives and continue their operations. Cloud providers must examine and satisfy the various QoS standards of each unique consumer as stipulated in unique SLAs. To do this, cloud providers cannot continue to install traditional system-centric resource management architectures that do not give incentives for them to share their resources while still treating all service requests as equal insignificance. Instead, market-oriented resource management is required to maintain the supply and demand for Cloud resources at market equilibrium, provide feedback in the form of economic incentives for both Cloud consumers and providers, and promote QoS-based resource allocation mechanisms that differentiate service requests based on their utility. The diagram depicts a high-level architecture for enabling market-orie
Read more