Course Outline
Pre-Requisites
None
Lessons
Master use cases to develop requirements, improve quality and solidify the link between requirements and other aspects of development.It's well documented that the most common source of delays, cancellations and defects in systems development projects is our failure to understand the project requirements. We also know that the top two causes of requirements errors are lack of input from the users and missing or incomplete requirements. As you'll see in Developing Requirements with Use Cases, identifying and writing high-quality use cases is significantly enhanced with active user input and participation. In turn, that user involvement helps to ensure that all desired system functionality and behavior is explored and understood early on. This both drastically reduces the number of missed and misunderstood requirements and also provides a sound way to manage requirements on very complex systems.
Course Outline.
1.Review of Requirements Development with Use Cases
-Definitions of terms
-Levels and types of requirements
-Characteristics of effective requirements
-Requirements, use cases, and the development life cycle
-Review and assess use case quality
-Identify requirements associated with a use case
-Use cases and Agile methods
2.IT Project Initiation and Use Cases
-Project scope and stakeholders: how they relate to use cases
-Actor/goal definition and use cases
-Event identification
-User stories for Agile development
-Use case briefs and usage narratives
-The use case diagram
3.Documenting Requirements with Use Cases
-The use case preamble: the big picture
-Describing the normal course (i.e., main success scenario)
-Identifying and describing extension scenarios
-Identifying includes (sub-function use cases) and extends relationships (extension use cases)
-Linking uses cases for larger or more complex systems
4.Improving Use Case Quality
-Characteristics of well-written use cases
-Recognizing common problems with use cases
-Avoiding use case traps and pitfalls: advice and examples
-Validating use cases through reviews and inspections
5.Use Cases and Other Requirements
-Deriving non-functional requirements: business rules, data definitions, interfaces and quality attributes
-Relating use cases to other requirements
-Identifying design constraints
-Documenting requirements and use case traceability
6.Use Cases and Testing
-Benefits of early test case development
-Relating use cases to test cases
-Automated tools: reducing test procedure development time and testing time
7.Use Cases and Design Elements
-What are design elements?
-The relationship between a use case and design elements
-Functional decomposition for finding design elements
-Specifying design elements from a use case
-Validating requirements from user stories, use cases, and interface design
Cancellation Policy
If a change needs to be made to your public course registration (cancel, transfer, or substitution) ASPE must receive written notice via email at customerservice@aspeinc.com or fax at 919-816-1710. If a cancel or transfer request is made less than 15 business days prior to the class start date, payment will still be due, no refunds will be issued and you will be charged a $200 change fee. Your paid tuition will be available for one year to be used as a credit towards another course of equal value; only one reenrollment opportunity is allowed. Failure to attend the course without written notification will result in forfeiture of the full course price. Student substitutions may be made at any time prior to the start of class free of charge. If ASPE is forced to cancel a course for any reason, liability is limited to the registration fee only.
Training Location
Virtual
Your Address
Your City,
Your Province
Your Country