Explain the protoyping model of software development

-


 Prototyping Model

Prototyping is the iterative process of system development which is more appropriate for developing a new system where there is no clear idea of requirements, inputs, and output. Using prototyping, programmers can build an early version of systems. These systems are then continuously modified until the users are satisfied. Prototyping is especially helpful in situations where there will no heavy user interaction with the system, where the needed output is uncertain, and in some decision support applications where the logic is hard to determine in advance. The developer interviews the user and designs an initial system using a database management system. The user works with the prototype and suggests changes. The process repeats until the user or developer is satisfied.

 



The figure shows the steps involved in developing the type of prototype. There are 4 steps and are as follows:-

Identify the user need  
              The system analyst interviews the user to obtain an idea of what is required for the system.

Develop a prototype

The system analyst, working with other information specialists, uses one or more prototyping tools to develop a prototype.

Determine if Prototype is acceptable

 The analyst educates the user in prototype use and provides opportunities from becoming familiar with the system The user advises the analyst whether the prototype is satisfactory. If so then the next step, that is step 4 is taken else, the prototype is revised by repeating steps1,2 and 3 with a better understanding of the user's need.

Use the Prototype

The prototype becomes the operational system. This approach is possible only when the prototyping tools enable the prototype to contain all the essential elements of the new system.


Advantages of Prototype Model

  • Reduce the risk of incorrect user requirement
  • Good where requirement is changing/uncommitted
  • Regular visible process aids management
  • Support early product marketing
  • Reduce Maintenance cost.
  • Errors can be detected much earlier as the system is made side by side.


Disadvantages of Prototype Model

  • An unstable/badly implemented prototype often becomes the final product.
  • Require extensive customer collaboration
  • Costs customer money
  • Needs committed customer
  • Difficult to finish if customer withdraw
  • Maybe too customer-specific, no broad market
  • Difficult to know how long the project will last.
  • Easy to fall back into the code and fix without proper requirement analysis, design, customer evaluation, and feedback.
  • Prototyping tools are expensive.
  • Special tools & techniques are required to build a prototype.
  • It is a time-consuming process.

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