Lecture 11 - Prototyping and testing Flashcards

1
Q

what are the aims of prototyping and testing?

A
  • Bring the specification to life

- To validate the system’s functionality

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

revise 5 steps is SR process?

A

-Identify and describe use cases, -Construct the structural domain model, -Construct the structural design model, -Identify and specify atomic use cases, -Construct a an implementation (i.e. a prototype) and perform the testing

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

what are the inputs and outputs of prototyping and testing?

A

input: structural domain model and atomic use case specifications.
output: prototype and test cases for each atomic use case

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

what are 2 steps to creating a prototype?

A
  1. create the structures of the domain and system classes, including attributes, get and toString methods.
  2. Consider each atomic use case in turn, determine what methods we have to ass to complete use case, design test case, perform test
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

give example of adding the add employee use case into the prototype

A

add employee obviously requires a method to add employee. pre condition is id is new, so we need a method for searching through id list. post condition employee needs to be added to employee list, so also a constructor is needed (calls search and add)

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

how do we test the system?

A

each time we perform a test we display the state of the system object using the toString method or custom display method

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

where do tests come from?

A

pre and post conditions, we have test cases where pre conditions are met and ones where they arent

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

how do we implement testing?

A

we use a test script (tester program) - has no interactive inputs from user, each test or group of test cases should be defined in a separate method

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

last step of testing?

A

implement all atomic use cases and we get a fully functional system, test functionality of the system, we can then move onto create a UI or GUI to interact with the system

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