Specifications and prototyping Flashcards

1
Q

What are prototypes?

A

A concrete but partial representation of a system

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What is low fidelity prototyping?

A

A prototype which captures the point

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What is high fidelity prototyping?

A

A prototype which closely resembles the reality of the final product, allowing stakeholders to provide feedback before production.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What are the 3 types of prototyping?

A

Role of technology
- Powerpoints and paper
Look and feel
- UI desginers
Implementation guide

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What are the risks of prototyping?

A
  • Investing too much time on high-fidelity prototyping
  • Ad-hoc prototyping code is re-used in real system
  • Prototyping is used instead of documentation
  • Prototypes might be approved by the wrong stakeholder
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Give examples of low fidelity prototyping

A
  • Sketches
  • Paper prototypes
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

What are the qualities of a low fidelity prototype?

A
  • Developed quickly
  • Thrown away
  • Helps with client acceptance
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Give some examples of high fidelity prototypes

A
  • Simulations
  • Fully functional mock ups
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What are the qualities of a high fidelity prototype?

A
  • Built in software
  • Used in realistic studies
  • Thrown away
  • Helps clients acceptance
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What is the difference between requirements and specification?

A
  • Requirements is what the user must be able to do
  • Specifications is what the software must be able to do to meet user requirements
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

How can we write specifications?

A
  • Natural language
  • Structured specifications
  • Graphical specifications
  • Mathematical specifications
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What are some good qualities for specifications?

A
  • Correct
  • Concise
  • Clear
  • Traceable
  • Tesetable
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

What is meant by the traceability of a specification?

A

Every specification should state which user requirement it is supporting

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

What is meant by the testability of a specification?

A

Verification a specification has been met

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

What are the outputs of final specifications?

A

Tend to have a class description document that incorporates :

  • Architecture design
  • Interface design
  • Database design
  • Component design
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Explain architecture design

A

Internal architecture of objects, classes, use of APIs

17
Q

Explain interface design

A

Detailed ‘blueprints’ of final user interface

18
Q

Explain database design

A

Developers can request data from DB

19
Q

Explain component design

A

The exact class structure inside each component

20
Q

What does a class description document include?

A

Explain each variable, method and function explaining how we know it works as expected