Agile Modeling and TDD Workshop, by Craig Larman (2)

After created a sort of infrastructure of product backlog management, we moved to learn & understand requirements via Modeling & Elaboration.

* System Sequence Diagram illustrates external I/O events for system scenarios, ours as below.

* Cockburn-style Use Case Text helps us learn details. One or more scenarios may be generated from a use case, corresponding to the detail of each possible way of achieving that goal. In computing, a scenario
is a narrative describing foreseeable interactions of types of users
(characters) and the system. Scenarios include information about goals,
expectations, motivations, actions and reactions.

Then we made :

Play Monopoly Main Success Scenario

10 Player wants to StartNewGame?

20 Player MakeMove?

30 Player PerformsAction?

40 Player EndsTurn?
(repeat steps 20-40 until game ends)


EXTENSIONS——————

30a Player buys property
This is only legal if the property is available and player has enough money
1. Player gives money to the bank
2. Board is updated to reflect the change in property

30b Player pays rent
This is only legal if the property is owned by another player
1. System identifies who is the owner of the field
2. Cash is transfered to the owner

30c Player is using a community card
This is happening in case the player has landed on a field requireging usage of a community card

40a Active Player receives rent
1. System identifies who is the owner of the land
2. Cash is transfered to the owner

* Player sells a property

* domain model, or Domain Object Model (DOM) in problem solving and software engineering can be thought of as a conceptual model of a system which describes the various entities involved in that system and their relationships.

* Acceptance Tests (in Agile Software Development) are usually created by business customers and expressed in a business domain language. These are high level tests to test the completeness of a user story or stories ‘played’ during any sprint/iteration.

At this time, also gain inspirations from prior models : SSD, use-case text and domain model.


About Kaveri, Yi XU

Agile Coach & Consutlant
This entry was posted in Agile&Scrum&Testing&TA. Bookmark the permalink.

发表评论

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / 更改 )

Twitter picture

You are commenting using your Twitter account. Log Out / 更改 )

Facebook photo

You are commenting using your Facebook account. Log Out / 更改 )

Google+ photo

You are commenting using your Google+ account. Log Out / 更改 )

Connecting to %s