Prototype - A model of a system being developed which may not be fully functional, Evolutionary - A prototype that is reviewed and improved and will eventually form the final system solution, Throwaway - A prototype that does not become part of the final system solution, User requirements - A document which details the end user's needs (i.e. the tasks they expect to be able to complete using the system designed, Navigation structure - A diagram which shows the various pathways a user can take through a multimedia package, Data dictionary - Contains details relating to the structure of data held in a database e.g. table names, attributes, validation, field length, data type, Wireframe diagram - A tool used to show the layout of the input and output screens in a digital application, Attribute - The heading given to each item of data stored about a single database entity, Scripted elements - Extracts of code, that when activated, can allow the end user to interact with the application and amend the contents being displayed, Third-party implementation - The creation of a product by someone other than the original designer, User interface - Any part of the system that the user can interact with e.g. buttons, menus, data capture forms, Interactive elements - Elements in a package that prompt interaction from the end user, Storyboard - A diagrammatic illustration of the content and layout of individual pages/screens in an application, ERD  - Entity Relationship Diagram, Types of relationships - One-to-one, many-to-many, one-to-many,

Unit 2: Designing Solutions

Print
Embed

Leaderboard

Visual style

Options

Switch template

Continue editing: ?