1 386SX off \ 2 386DX on \
3 486SX off \ 4 486DX off
2.10 Prototyping Model
According to Aggarwal 2006:62, prototyping is the technque of constructing partial implementation of a system so that customers, users, or
developers can learn more about a problem or a solution to that problem. It allows users to explore and criticize proposed system before undergoing the cost of a
full-scale development. The field of prototyping software system has emerged around two prototyping technologies, i.e., throwaway and evolutionary.
Still according to Aggarwal 2006:62, the benefit of developing prototype are:
1.
Misunderstanding between software developers and and customers may be identified as the system functions are demostrated.
2.
Missing user requirements may be detected.
3.
Difficult-to-use or confusing user requirements may be identified and refined.
4.
A working system is available quickly to demonstrate the feasibility and usefulness of the application to management.
5.
The prototype serves as a basis for writing the specification of the system.
Based on Pressman 2005:83, a customer defines a set of general objectives for software but does not identify detailed input, processing, or output
requirement. In other cases, the developer may be ensure of the efficiency of algorithm, the adaptability of an operating system, or the form that human
machine interaction should take. In these, ad many other situations, a prototyping paradigm may offer the best approach. Prototyping process describe in four
processes: a. Communication
The software engineer and customer meet and define the overall objectives for the software, identify whatever requirements are known, and
outline areas where further definition is mandatory. b. Quick Plan and Quick Design
A prototyping iteration is palnned quickly ad modeling in the form of a “quick design” occurs. The quick design focuses on a representation of those
aspects of the software that will be visible to the customer end-user e.g., human interface layout or output display formats
c. Construction of prototype The quick design leads to the construction of a prototype.
d. Deployment delivery and Feedback The prototype is deployed and then evaluated by the customeruser.
Feedback is used to refine requirements for the software. Iteration occurs as the prototype is tuned to satisfy the need of the customer, while at the same time
enabling the developer to better understand what needs to be done.
Figure 2.2 Prototyping Model Pressman:2005
2.11 Structured Analysis
Kategori