Prototyping
The original purpose of a prototype is to allow users of the software to evaluate developers' proposals for the design of the eventual product by actually trying them out, rather than having to interpret and evaluate the design based on descriptions.Broadly, two types of design:
- Conceptual - a concept trying to capture what the product will do and how it will behave
- Physical - concerned with the details of the design; e.g. information, screen and menu structures; icons, graphics, etc
Outline of the prototyping process
- Identify basic requirements
- Develop Initial Prototype
The initial prototype is developed that includes only user interfaces. (See Horizontal Prototype, below)
- Review
The customers, including end-users, examine the prototype and provide feedback on additions or changes.
- Revise and Enhance the Prototype
Using the feedback both the specifications and the prototype can be improved. Negotiation about what is within the scope of the contract/product may be necessary.
Conceptual design
- Transform user requirements/needs into a conceptual model
- “a description of the proposed system in terms of a set of integrated ideas and concepts about what it should do, behave and look like, that will be understandable by the users in the manner intended”
- Don’t move to a solution too quickly. Iterate, iterate, iterate,
- Consider alternatives: prototyping helps
No comments:
Post a Comment