While some think this is a deficiency in UML or SysML, the language is not the problem.  The way the language is being used – i.e. the methodology is the problem.  You could no more craft good textual requirements if I just offered you an English language dictionary than you could create good model-based requirements if I handed you a UML specification.  In this tutorial we will explore not only a modeling language but a method for using it to document and manage requirements.  Requirements that consist of only written statements can be confusing.  Visualizations that can be referenced by text greatly improve understanding and help to solve communications problems with stakeholders.


3 Days

Outline for Enterprise Architect Fundamentals Training

Introduction to UML


Requirements Analysis

  • Use Case modeling for Stakeholder Analysis
  • Creating high-level use case descriptions
  • Define types of requirements using the FURPS+ model
  • Define types of requirements using the Requirements Modeling Language (RML®)
  • Exploring the intersection between FURPS+ and RML®
  • Review requirements in the context of iterative development
  • UML Model Organization to support requirements management and product development


Requirements Elicitation

  • UML models for describing the business case, business facts and business rules
  • Modeling requirements and creating a requirements hierarchy
  • Grouping stakeholders for effective brainstorming and focus group activities
  • Prototyping and storyboards
  • Using models to validate requirements elicitation


Requirements Management

  • Classifying requirements using UML tags and stereotypes
  • Preparing requirements reports
  • Tracing requirements through to implementation using the EA Relationship Matrix


Enterprise Analysis

  • Modeling business objectives to define the business case
  • UML models for capability gap analysis
  • Documenting trade studies
  • Organizing models for as-is and to-be business architecture analysis


Requirements Models

  • Analyzing business, stakeholder, solution, and transition requirements;
  • Business process model  analysis and execution
  • Business domain data models
  • Refining use case models for software systems analysis and creating detailed descriptions
  • Requirements verification and validation


Solution Assessment and Validation

  • Supporting solution assessment with state diagrams, sequence diagrams
  • Test Case Development in the model


Mapping UML diagram/model type to project characteristics