lesson 6 bme 405 fall 2010 use cases (1)

lesson 6 bme 405 fall 2010 use cases (1) - but are specific...

Info iconThis preview shows pages 1–29. Sign up to view the full content.

View Full Document Right Arrow Icon
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Background image of page 2
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Two audiences: customer and development team. Use case should be usable by both groups
Background image of page 4
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Background image of page 6
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Focus on value provided to user. Use case name should clearly indicate the benefit to the user.
Background image of page 8
Use case: narrative of how users and system interact Note the last point: Use case describes what happens, not the implementation
Background image of page 9

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Contrast between one way to describe requirements (declarative statements) and use case. Use case shows what the user is doing. Easier to present to customer. Information is the same but use case shows goal.
Background image of page 10
Special requirements: place to put requirements that are not part of the use case
Background image of page 11

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Background image of page 12
Background image of page 13

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Background image of page 14
Background image of page 15

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Background image of page 16
Background image of page 17

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Background image of page 18
Background image of page 19

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Background image of page 20
Background image of page 21

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Background image of page 22
Background image of page 23

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Background image of page 24
Background image of page 25

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Background image of page 26
Background image of page 27

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Background image of page 28
Background image of page 29
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: but are specific to the use case (for instance an algorithm). Not all elements of the template have to be filled. There may not be any post-condition for instance. There is always a main flow and at least one alternative flow. Give titles to flows for clarity. Main flow stands on its own. http://www-128.ibm.com/developerworks/rational/rationaledge/ Use case should not have two basic flows Design information should not appear in use case. Use case is used to describe functional requirements...
View Full Document

Page1 / 29

lesson 6 bme 405 fall 2010 use cases (1) - but are specific...

This preview shows document pages 1 - 29. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online