5 - Prototyping and Testing
global prototype
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
diagonal prototype
prototype that is horizontal down to a particular level, then vertical below that point
horizontal prototype
prototype that models many features but with little detail
vertical prototype
prototype that models with much fewer features but with much detail
experimental prototype
prototype used to validate system specs
advantages of prototyping process model
reduced time and costs; improved and increased user involvement;
prototype qualities
representation; precision; interactivity; evolution
working prototype
represents all or nearly all of the functionality of the final product
user experience prototype
represents enough of the appearance and function of the product that it can be used for user research
visual prototype
represents the size and appearance, but not the functionality, of the intended design
proof-of-principle/concept prototype
serves to verify some key functional aspects of the intended design; allows key tech of proposed product to be tested for viability and performance
component testing
testing conducted to verify the implementation of the design for one hardware or software element
representation of a prototype
the actual form of a prototype
interactivity of a prototype
the functionality open to the user
verification
the product was built right
validation
the right product was built
functional testing
verify that all functional requirements satisfied
evolution of a prototype
lifecycle of the prototype
white box
logic driven testing; based on input-output values, with expected intermediate values
testing
mechanism to assure quality of a product, system, or capability; must be addressed continuously during design process
form study prototype
preliminary type of visual prototype where geometric features emphasized
paper prototype
printed or hand-drawn representation of the user interface of a software product
system testing
process of testing an integrated hardware and software system to verify meets requirements
local prototype
prototype of single usability-critical system component; a vertical prototype that is focused on one feature
prototype
a sample, model, or release of a product built to test a concept or process or to act as a thing to be replicated or learned from
low-fidelity prototype
a set of drawings that provide a static, non-computerized, non-working mock-up of user interface for the planned system
high-fidelity prototype
a set of screens that provide a dynamic, computerized, working model of the planned system
prototype
a simulation or sample version of a final product, which is used for testing prior to launch; goal is to test products before sinking lots of time and money into the final product
exploratory prototype
a throw away prototype used to clarify project goals, identify requirements, examine alternative designs, investigate a large and complex system
integration testing
an orderly progression of testing in which various software elements and/or hardware elements are integrated together and tested
functional prototype
captures both function and appearance of intended design; may be created with different techniques from final
robustness testing
determine how system performs given unexpected inputs
software
easily modified and extensible model (representation, simulation, or demo) of a planned software system, likely including its interface and input/output functionality
hardware
easily modified and extensible model of a system, including location of individual hardware components
precision of a prototype
fidelity of a prototype; its level of detail, polish, realism
acceptance testing
formal testing conducted to determine whether or not a system satisfies its acceptance criteria and to enable the customer to determine whether or not to accept the system
black box
input/output driven testing; no knowledge of internal structure
disadvantages of prototyping process model
insufficient analysis; user confusion of prototype and finished system; developer misunderstanding of user objectives; developer attachment to prototype; excessive development time of the prototype; expense of implementing prototype
operational prototype
iterative prototype that is progressively refined until it becomes the final system