 |
| Software developers, requirements engineers, and business analysts who are interested in or charged with modeling functional requirements with use cases. Because it addresses only requirements modeling (and not software design), it is equally beneficial to developers and non- developers.
|
|
Course Overview: Use cases provide a valuable tool for modeling the behavior of systems and businesses. While they serve several other purposes, use cases are especially effective for describing functional requirements. Requirements in the form of use cases offer a refreshing change from the more typical large, monolithic requirements document. This two-day course explains how to apply uses cases to the task of modeling the functional requirements of a system. It illustrates how to model use cases with Unified Modeling Language (UML) use case diagrams and, more importantly, how to describe individual use cases with text and diagrams. It also describes various approaches one can use to identify use cases, and it explains various types of relationships between use cases. This course includes laboratory sessions that afford attendees an opportunity to identify and describe use cases for provided problems. Course Outline: Introduction: Course objectives. What use cases are (and are not). A description of the case study to be used throughout the course. Some references to books on uses cases. Determining System Scope: Project blast-off, including documenting the projects mission, identifying the root problem, identifying the project stakeholders, and determining system scope. Actors: What an actor is. Business actors versus system actors. Different types of actors. Modeling actors in UML. Identifying actors. Relationships between actors. Use Cases: What use cases are. Use cases versus goals. Keeping use cases at the correct level. Modeling use cases in UML. Use case scope. Identifying Use Cases: Determining the scope of the system or application. Four distinct approaches for identifying use cases. Describing Use Cases: Different ways of describing the details of individual use cases, including writing briefs, listing steps, and using activity diagrams. Alternative paths versus error paths. Writing black-box use cases that avoid design details. Use Case Relationships: Static (non-temporal) and dynamic (temporal) relationships between use cases. Describing those relationships. Process: A brief discussion of requirements elicitation and requirements sources. Running joint requirements planning (JRP) sessions. Transitions: A brief overview of how use cases can guide subsequent project activities such as estimation of development effort, application design, user interface design, and testing. Target Audience: This course is aimed at software developers, requirements engineers, and business analysts who are interested in or charged with modeling functional requirements with use cases. Because it addresses only requirements modeling (and not software design), it is equally beneficial to developers and non- developers. Prerequisites: None. No knowledge of use cases, software development, or the Unified Modeling Language is required.
Contact Information
Theresa
Dobbs
Sr. Manager
tdobbs@mail.utexas.edu
(512)
471-4875 |
Course Location
J. J. Pickle Research Campus
Commons Building, Room 1.140
10100 Burnet Road
Austin, TX 78758
Telephone: (512) 471-5898
Fax: (512) 471-3679
For a map and information on
parking, visit this link. |
|
Attendance Policy
A 90% attendance rate is required in order to earn Continuing Education Units (CEUs) and certificates of completion.
|
Cancellation Policy
A full refund, less a $100.00 processing fee, will be given for all cancellations or transfers if notification is received on or before two weeks prior to the beginning of the course. Refunds will not be given for cancellations received after this date. Substitutions may be made anytime prior to the first day of class. The CLEE programs are subject to cancellation if too few people enroll, in which case a full refund will be given.
|
|
Hotel Information
|
| 
