12.FacadeIteration

12.FacadeIteration - Use Case Descriptions Chapter 4 Facade...

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

View Full Document Right Arrow Icon
17 1 Use Case Descriptions Chapter 4 – Facade Iteration Initial Requirements (Inception Phase)
Background image of page 1

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

View Full DocumentRight Arrow Icon
2 First Real Cut at Application Requirements Façade Use Cases Amount to ‘placeholders’ for expanded use cases (to come). Contain name and short description of the interaction; contains initiating actors. Verb…objects. Typically, we do NOT know all the details. Want to capture the ‘ architecturally significant ’ use cases… (What are these???) Trying to identify key functions / risks / interactions at a global level.
Background image of page 2
3 Intro: Façade Use Cases Ensure façade use cases are user-centric and NOT technology-centric. Why? What does this mean? Again, these are the WHATS that the users want! These are the ‘ behaviors ’ of the system. Express in terms the users understand! Involve various sources early and frequently Many different stakeholders with diverse ‘takes’ on the application…
Background image of page 3

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

View Full DocumentRight Arrow Icon
4 Use Case Index This is a Table of Contents for your Use Cases (that will be developed). Single Sheet; table in Word As you discover a Use Case, index it. For each Use Case in the index (include a designator (like UC1, UC2, …), followed by the use case name, short description (two or three sentences), actors, level (façade, filled, focused) date last updated (for now). Book states (p. 73), “Façade use cases show the basic, essential, high-level interactions that this application must support (Constantine 1999).”
Background image of page 4
5 Façade Use case: Attributes (Rows) Name of the use case – short name (verb, object); action words; Actor(s) that trigger the use case… Level (façade, filled, focused…) Short Description – two three sentences: at the most! Leave room for the Basic Course of Events…(happy path) Pre and Post conditions, and more (see ahead…) Trigger Business Rules Link (Reference Business Rules in your Use Cases (consider format on pg. 82 or other format) Risk priority (reference your Risk List preferable by number or
Background image of page 5

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

View Full DocumentRight Arrow Icon
Image of page 6
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 07/26/2011 for the course CEN 6016 taught by Professor Sanchez,a during the Spring '08 term at UNF.

Page1 / 15

12.FacadeIteration - Use Case Descriptions Chapter 4 Facade...

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

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