2.3.3
2.3.32.3.32sfrsfsd.3.32.3.3
Post-conditions
The
post-conditions section describes what the change in state of the
system will be after the use case completes. Post-conditions are
guaranteed to be true when the use case ends.
2.3.4
Triggers
The
event that causes the use case to be initiated.
This
event can be external, temporal or internal.
Preconditions
are NOT triggers.
3.
A Complete Use Case
Name
(2.3)
Version
(0.1...review #1...1.0... review #2... 2.0... )
Goal
(2.1.2)
Summary
Actors
(2.1.1)
Preconditions
(2.3.2)
Triggers
(2.3.4)
Normal
flow (2.3.1)
Alternative
flows and Exceptions (2.3.2)
Post-conditions
(2.3.3)
Business
rules（e.g.,
coupons, upgrade membership）
Notes
* Use Case are
NOT User Stories (Scenarios).
* NOT related to
UI behaviors.
c.f.:
User choose to
withdraw.
User press
withdraw button.
Post-conditions
The
post-conditions section describes what the change in state of the
system will be after the use case completes. Post-conditions are
guaranteed to be true when the use case ends.
2.3.4
Triggers
The
event that causes the use case to be initiated.
This
event can be external, temporal or internal.
Preconditions
are NOT triggers.
3.
A Complete Use Case
Name
(2.3)
Version
(0.1...review #1...1.0... review #2... 2.0... )
Goal
(2.1.2)
Summary
Actors
(2.1.1)
Preconditions
(2.3.2)
Triggers
(2.3.4)
Normal
flow (2.3.1)
Alternative
flows and Exceptions (2.3.2)
Post-conditions
(2.3.3)
Business
rules（e.g.,
coupons, upgrade membership）
Notes
* Use Case are
NOT User Stories (Scenarios).
* NOT related to
UI behaviors.
c.f.:
User choose to
withdraw.
User press
withdraw button.
Post-conditions
The
post-conditions section describes what the change in state of the
system will be after the use case completes. Post-conditions are
guaranteed to be true when the use case ends.
2.3.4
Triggers
The
event that causes the use case to be initiated.
This
event can be external, temporal or internal.
Preconditions
are NOT triggers.
3.
A Complete Use Case
Name
(2.3)
Version
(0.1...review #1...1.0... review #2... 2.0... )
Goal
(2.1.2)
Summary
Actors
(2.1.1)
Preconditions
(2.3.2)
Triggers
(2.3.4)
Normal
flow (2.3.1)
Alternative
flows and Exceptions (2.3.2)
Post-conditions
(2.3.3)
Business
rules（e.g.,
coupons, upgrade membership）
Notes
* Use Case are
NOT User Stories (Scenarios).
* NOT related to
UI behaviors.
c.f.:
User choose to
withdraw.
User press
withdraw button.
Post-conditions
The
post-conditions section describes what the change in state of the
system will be after the use case completes. Post-conditions are
guaranteed to be true when the use case ends.
2.3.4
Triggers
The
event that causes the use case to be initiated.
This
event can be external, temporal or internal.
Preconditions
are NOT triggers.
3.
A Complete Use Case
Name
(2.3)
Version
(0.1...review #1...1.0... review #2... 2.0... )
Goal
(2.1.2)
Summary
Actors
(2.1.1)
Preconditions
(2.3.2)
Triggers
(2.3.4)
Normal
flow (2.3.1)
Alternative
flows and Exceptions (2.3.2)
Post-conditions
(2.3.3)
Business
rules（e.g.,
coupons, upgrade membership）
Notes
* Use Case are
NOT User Stories (Scenarios).
* NOT related to
UI behaviors.
c.f.:
User choose to
withdraw.
User press
withdraw button.
Post-conditions
The
post-conditions section describes what the change in state of the
system will be after the use case completes. Post-conditions are
guaranteed to be true when the use case ends.
2.3.4
Triggers
The
event that causes the use case to be initiated.
This
event can be external, temporal or internal.
Preconditions
are NOT triggers.
3.
A Complete Use Case
Name
(2.3)
Version
(0.1...review #1...1.0... review #2... 2.0... )
Goal
(2.1.2)
Summary
Actors
(2.1.1)
Preconditions
(2.3.2)
Triggers
(2.3.4)
Normal
flow (2.3.1)
Alternative
flows and Exceptions (2.3.2)
Post-conditions
(2.3.3)
Business
rules（e.g.,
coupons, upgrade membership）
Notes
* Use Case are
NOT User Stories (Scenarios).
* NOT related to
UI behaviors.
c.f.:
User choose to
withdraw.
User press
withdraw button.
网友评论