3B: design specifications Flashcards
meaning of design specifications
forms the basis for planning and designing solution
aim of design specifications
accurately interpret needs, requirements and boundaries identified into a set of workable + realistic specifications from which a final solution can be created
what do developers consider when developing design specifications
- data types + structure
- algorithms
- variables
- dev approach
- quality assurance
- system modelling
- documentation
design specifications from user’s perspective
- interface design
- messages + icons
- data formats for display
- ergonomic issues
- relevance to user’s environment + computer config
- social + ethical issues
function of specifications from dev’s pov
provides a standard framework
- doesn’t directly affect user’s perspective
- all technical things(system modelling tools, depth of algorithm description, variable naming conventions) specified
how important are dev’s specifications
very; develops the framework so that each member of dev team will be creating sections of the solution that look, feel, and are documented using a common approach
- CASE tools used
what happens after dev specifications are developed
system model created for entire system; leads to allocation of tasks for team members, visualises overall direction of project
what do all specifications from user’s pov have in common
all include any design specifications which influence the experience of the end-user, UI(interface, menus, frames, color, common elements)
things to think about with ergonomic issues
- most used functions
- which functions require keyboard shortcuts
- switching between screen/elements
- order in which data is entered
- aesthetics
how does user environment affect specifications
- user of existing applications, which should be researched and have their design elements incorporated for transfer of skills
- consideration of hardware(RAM, video memory, hard disk space, processor speed)
e.g. keyboard shortcuts that are commonly used, OS settings
how do you get information on user environment
consultation with potential users
system model functions
assists in determining user based design specifications, especially screen designs + concept prototypes
- get user opinion, good in early stages
how should communication be conducted
as a two-way channel: users should be consulted, and their feedback should be imcorporated in design
modes of communication with users
- meetings
- questionnaires
- memos
- interviews
- phone calls + emails
- concept prototype
two methods of communication used
formal: specific tasks
informal: elicit more useful feedback on existing system, perceived problems with new system
