A team representative can use the SystemPlanner to help guide the client through the requirements acquisition process.
Create and manage the steps of this scenario in the index below.
|
1)
|
Client and team representative meet
|
|
Up
Down
|
Edit
Delete
|
|
2)
|
Team representative loads SystemPlanner application
|
|
Up
Down
|
Edit
Delete
|
|
3)
|
Team representative creates or selects project.
|
|
Up
Down
|
Edit
Delete
|
|
4)
|
Goals are discussed, defined and recorded
|
|
Up
Down
|
Edit
Delete
|
|
5)
|
Goals are continually reviewed
|
|
Up
Down
|
Edit
Delete
|
|
6)
|
The different types of users/actors who will be using the system are discussed and recorded. (Can include non-user actors eg. external digital systems)
|
|
Up
Down
|
Edit
Delete
|
|
7)
|
Each of the individual features in the system are discussed and recorded
|
|
Up
Down
|
Edit
Delete
|
|
8)
|
Features are reviewed, discussed and clarified
|
|
Up
Down
|
Edit
Delete
|
|
9)
|
Usage scenarios are discussed and recorded
|
|
Up
Down
|
Edit
Delete
|
|
10)
|
The steps of each scenario are defined.
|
|
Up
Down
|
Edit
Delete
|
|
11)
|
Each scenario is reviewed along with the relevant steps and new steps added if necessary.
|
|
Up
Down
|
Edit
Delete
|
|
12)
|
The individual data/business entities in the system are defined.
|
|
Up
Down
|
Edit
Delete
|
|
13)
|
The properties/attributes of each entity are discussed and defined.
|
|
Up
Down
|
Edit
Delete
|
|
14)
|
All restraints, applied to various aspects of the system. are discussed and defined. (Including security, data validation, etc.)
|
|
Up
Down
|
Edit
Delete
|
|
15)
|
The project goals are reviewed again and the previous steps repeated until no more gaps can be found in the specifications.
|
|
Up
Down
|
Edit
Delete
|
|