Title: Class Outline 7
Course: KVCC_BUS205 > Section: Class Outlines

1.      User Stories

a.      What is a user story?

b.      Who, What, Why

c.      How are the developed?

d.      As a <Role>, I want to <Goal> so that <Benefit>

e.      Acceptance criteria

2.      Use Case

a.      What is a use case?

b.      User Stores - assist in identification and definition of use cases

c.      User Goal technique

i.           Identify all the potential users

ii.           Classify users by role

iii.           Classify by organizational level

iv.           Interview each type of user

v.           Create a list of use cases organized by user type

vi.           Look for duplicates and fix inconsistencies

vii.           Identify when different uses need the same use cases

viii.           Review the list with the users and other stakeholders

d.      Event Decomposition

i.           Elementary business process EBP

ii.           Events

1.      External Events

a.      Actors

b.      What to look for

i.           Agent wants something resulting in a transaction

ii.           External agent wants some information

iii.           Data changed and needs to be updated

iv.           Management wants some information

2.      Temporal events

a.      What to look for

i.           Internal outputs needed

1.      Management reports

2.      Operational Reports

3.      Internal statements and documents

ii.           External outputs needed

1.      Statements, Status reports, bills, reminders

3.      State/Internal Events

iii.           Identifying events

1.      Events vs Prior conditions and responses

2.      Event Sequencing

3.      Technology/System Controls

a.      System controls

b.      Perfect Technology Assumption

iv.           Steps

1.      External events

2.      For each event identify the use case that the system requires

3.      Temporal Events

4.      For each temporal event identify and then declare time for trigger

5.      State events

6.      For each state event identify and define change in state

7.      Analyze events and remove items such as system controls

e.      Use Cases

i.           Descriptions

ii.           Use Case Diagram

iii.           Includes Relationships

iv.           Diagram creation steps

1.      Identify all the stakeholders and users

2.      Determine what needs to be reviewed in a use case diagram and start to breakdown items such as by subsystem

3.      Select use cases and actors and draw diagram

4.      Label diagram and determine how it should be used to review the information with stakeholders

Attached Files: | - KVCC BUS205_BusSysAnalysis_Outline 7.pdf