PROTOTYPING



http://software-document.blogspot.com/2011/03/prototype-advantages-and-rapid.html



 PROTOTYPE is an easily modified and extensible model (representation, simulation
or demonstration) of a planned software system, likely including its
interface and input/output functionality.


CHARACTERISTICS OF A PROTOTYPE

1. TYPES OF PROTOTYPE
   1. LOW-FIDELITY versus HIGH-FIDELITY
      1. LOW-FIDELITY
         A set of drawings (e.g., storyboard) that provide a static,
         non-computerized, non-working mock-up of user interface for
         the planned system
      2. HIGH-FIDELITY
         A set of screens that provide a dynamic, computerized,
         working model of the planned system
   2. EXPLORATORY versus EXPERIMENTAL versus OPERATIONAL
      1. EXPLORATORY
         A throw-away prototype used to clarify project goals, to
         identify requirements, to examine alternative designs, or to
         investigate a large and complex system
      2. EXPERIMENTAL
         A prototype used to validate system specifications
      3. OPERATIONAL
         An iterative prototype that is progressively refined until
         it becomes the final system
   3. HORIZONTAL versus VERTICAL
      1. HORIZONTAL
         A prototype that models many features but with little detail
         • a horizontal slice of a system's structure chart from the
           top down to a specific depth
         • most useful in the early stages of design
         • purpose is to test the overall interaction metaphor, so
           includes common functions that the user is expected to
           perform frequently
      2. VERTICAL
         A prototype that models few features but with much detail
         • a vertical slice of a system's structure chart from top
           to bottom
         • most useful in the later stages of design
         • purpose is to test details of the design
      3. DIAGONAL
         A prototype that is horizontal down to a particular level,
         then vertical below that point
   4. GLOBAL versus LOCAL
      1. GLOBAL
         A prototype of the entire system
         • an expanded horizontal prototype that models a greater
           number of features and covers multiple levels of the
           system's structure chart
         • useful throughout the design process
      2. LOCAL
         A prototype of a single usability-critical system component
         • a vertical prototype that is focused on one feature
         • useful at some specific stage of the design process

Advantages of Prototyping :

Reduces development time.

Reduces development costs.

Requires user involvement.

Developers receive quantifiable user feedback.

Facilitates system implementation since users know what to expect.

Results in higher user satisfaction.

Exposes developers to potential future system enhancements.


 Disadvantages of Prototyping :

 

Can lead to insufficient analysis.

 

Users expect the performance of the ultimate system to be the same as the prototype.

Developers can become too attached to their prototypes

Can cause systems to be left unfinished and/or implemented before they are ready.

Sometimes leads to incomplete documentation.

 

If sophisticated software prototypes (4th GL or CASE Tools) are employed, the time saving benefit of prototyping can be lost.

JUST FOR SHARE ===

Hands-On With Transparent Display of the Future

http://www.youtube.com/watch?v=qeNJrim3SU4

Citation :

1. http://csweb.cs.bgsu.edu/maner/domains/Proto.htm
2. http://www.umsl.edu/~sauterv/analysis/prototyping/proto.html

CHAPTER 13: SYSTEM ANALYSIS & DESIGN

The System Development Life Cycle

http://en.wikipedia.org/wiki/File:Systems_Development_Life_Cycle.jpg

Some of the BENEFITS of integrating security into the system development life cycle include : 

• Early identification and mitigation of security vulnerabilities and problems with the configuration of systems, resulting in lower costs to implement security controls and mitigation of vulnerabilities.
• Awareness of potential engineering challenges caused by mandatory security controls.
•  Facilitation of informed executive decision making through the application of a comprehensive risk management process in a timely manner.
• Documentation of important security decisions made during the development
  process to inform management about security considerations during all phases of
  development.
• Improved organization and customer confidence to facilitate adoption and use of
  systems, and improved confidence in the continued investment in government
  systems. (1)

Phase 1 -->Preliminary Analysis

• Objectives - To identify the customer's needs, evaluate system concept for feasibility, perform economic and technical analysis, perform cost benefit analysis and create system definition that forms the foundation for all subsequent engineering works.
• In this Phases 1 you should be enough expertise available for hardware and software for doing analysis.After the preliminary analysis, the analyst should report the findings to management, with recommendations outlining the acceptance or rejection of the proposal. (2)

http://www.bakchich.info/Weapons-Sale-DCN-Thales-Slush-fund,04459.html

http://software-document.blogspot.com/2010/10/requirement-analysis-fact-finding.html

CiTaTION:::::
(1) http://csrc.nist.gov/publications/nistbul/april2009_system-development-life-cycle.pdf 
(2) http://www.freetutes.com/systemanalysis/sa3-preliminary-analysis.html