Dashboard > Struts University > Home > Struts Classic > Information > Page Comparison
Struts Classic
Version 1 by Ted Husted
on Oct 29, 2005 20:07.

compared with
Current by Ted Husted
on Nov 03, 2005 06:31.

(show comment)
These lines were removed. This word was removed.
These lines were added. This word was added.

View page history

There are 1 changes. View first change.

 h2. Struts Classic Use Cases
 * Use cases tell coherent stories about the how the story will behave in use.
 * Use cases are requirements, but not *all* of the requirements.
 * Use cases capture contracts between the stakeholders of a system about its behavior.
 * Use Cases describe how actors achieve goals.
 * For more see, [Writing Effective Use Cases|http://www.amazon.com/exec/obidos/tg/detail/-/0201702258/husteddotcom-20/] by Cockburn.
 h2. Use Case Development Lifecycle
 # Actors and Goals
 # Use Case Briefs (stories)
 # Priority
 # Usage Narrative
 # Main Success Scenario
 # Failure Conditions
 # Failure Handling
 h3. Guidelines
 * Use simple grammar.
 * Show clearly "who has the ball".
 * Write from the bird's eye view.
 * Show the process moving forward.
 * Show the Actor's intent, not the movements.
 * Include a "reasonable" set of actions
 * "Validate", don't "Check whether".
 * Optionally, mention the timing.
 * Idiom: "User has System A kick System B".
 * Idiom: "Do Steps x-y until condition."
 h3. Defaults
 * If an extension simply returns to the next step, then "Return to MSS" can be omitted.
 * Extensions can be nested one level deep.
 * Extension steps can be numbered using the newer "dot" convention.
 * The "System Under Design" can be referred to in the third person.
 * If System is going to display the expected screen as the next step, and there are no extensions, a "System presents (expected) screen" step can be omitted.
 h3. References
 * [Structuring Use Cases with Goals|http://alistair.cockburn.us/crystal/articles/sucwg/structuringucswithgoals.htm]
 * [Writing Effective Use Cases|http://www.amazon.com/exec/obidos/tg/detail/-/0201702258/]
 h2. Vision Statement
 * Encourage application architectures based on the "Model 2" approach, a variation of the classic Model-View-Controller (MVC) design paradigm.
 h2. Design Scope UML Drawing
 (+) TODO ...
 h2. Design Scope Topics (In/Out)
 ||Topic ||In ||Out |
 |Business Logic | |(*b)|
 |Data Access Logic | |(*b)|
 |Request Processing |(*g)| |
 |Command Mapping |(*g)| |
 |Server-side Validation |(*g)| |
 |Client-side Validation |(*g)| |
 |HTML 4.1 Markup |(*g)| |
 |HTML 4.1 Extensions | |(*b)| As to existing Taglib subproject |
 |Page Composition |(*g)| |
 |Secure (SSL) mode | |(*b)|
 |JAAS Authorization |(*g)| |
 |Custom Authorization | |(*b)|
 h2. Stakeholders
 | | |
 h2. Actors
 | | |
 h2. Core Use Cases
 ||Priority||Actor||Goal||Story or Brief|
 | | | | |
 h2. Taglib Use Cases
 ||Priority||Actor||Goal||Story or Brief|
 | | | | |
  h2. EL Use Cases
 ||Priority||Actor||Goal||Story or Brief|
 | | | | |
 h2. Validator Use Cases
 ||Priority||Actor||Goal||Story or Brief|
 | | | | |
 h2. Tiles Use Cases
 ||Priority||Actor||Goal||Story or Brief|
 | | | | |
Site running on a free Atlassian Confluence Open Source Project License granted to OSS. Evaluate Confluence today.
Powered by Atlassian Confluence, the Enterprise Wiki. (Version: 2.5.5 Build:#811 Jul 25, 2007) - Bug/feature request - Contact Administrators