I got this process from teaching PPT, I will support the link below.
1.Name the system scope and boundaries.
2.List the actors (Brainstorm)
3.List user goals for the system (becoming use case)
4.Capture the outmost summary use case to see "Who really cares" - seeking primary actors
5.Reconsider and revise summary use cases.Add, subtract or merge goals (Refining)
6.Select one use case to expand
7.Capture stakeholder interests and preconditions and guarantees (their requirements - there may be additional requirements)
8.Write the main succes scenario
9.List the extension conditions (Brainstorm)
10.Write the extension-handling steps
11.Extract complex flows to sub use case; merge trival sub use cases (Refining again)
12.Iterate and adjust
I think list number 1 to 6 will be helpful for SA28 who are now facing their exam on coming Monday.....
GOOD LUCK JUNIORS!!!!
Subscribe to:
Post Comments (Atom)
3 comments:
test!!!!!
A model of the requirements is the most beneficial if used in discussions with users or their representatives, and turn at the beginning of each iteration.
Cancun Flights
Blog is great
commercial dispute resolution
Post a Comment