L4A - Process Models - Use Case

L4A - Process Models - Use Case - An Introduction to...

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

View Full Document Right Arrow Icon
An Introduction to Use-Case Modeling 1 The hardest single part of building a software system is deciding precisely what to build. No other part of the conceptual work is a difficult as establishing the detailed technical requirements, including all the interfaces to people, to machines, and to other software systems. No other work so cripples the resulting system if done wrong. No other part is more difficult to rectify later. Fred Brooks
Background image of page 1

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

View Full DocumentRight Arrow Icon
Use-Case Modeling Use-case modeling – the process of modeling a system’s functions in terms of business events, who initiated the events, and how the system responds to those events. Use-case modeling has roots in object-oriented modeling. Gained popularity in nonobject development environments because of its usefulness in communicating with users. Compliments traditional modeling tools. 2
Background image of page 2
System Concepts for Use-Case Modeling Use-case diagram – a diagram that depicts the interactions between the system and external systems and users. It graphically describes who will use the system and in what ways the user expects to interact with the system. Use-case narrative – a textual description of the business even and how the user will interact with the system to accomplish the task. Use case – a behaviorally related sequence of steps (a scenario), both automated and manual, for the purpose of completing a single business task. Description of system functions from the perspective of external users in terminology they understand. 3
Background image of page 3

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

View Full DocumentRight Arrow Icon
Sample Use-Case Model Diagram 4
Background image of page 4
Use case – subset of the overall system functionality Represented graphically by a horizontal ellipse with the name of the use case appearing above, below, or inside the ellipse. Actor – anything that needs to interact with the system to exchange information. Could be a human, an organization, another information system, an external device, or even time. Temporal event
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 11/21/2011 for the course BMGT 403 taught by Professor Staff during the Fall '08 term at Maryland.

Page1 / 30

L4A - Process Models - Use Case - An Introduction to...

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