logo
Home

Enterprise Architect Fundamentals Training

  • CMDBID 107281
  • Course Code WA2399
  • Duration 3 Days
Scroll

Enterprise Architecture Course

course overview

Click to View dates & book now

Overview

Despite the fact that many of the people working on the UML Profile for Systems Engineering talked about using models to discover system requirements, most of the methodologies and tutorials talk about interfacing with textual requirement management tools like DOORS and importing and exporting requirements to and from models captured in modeling tools. 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

Outline of 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

Talk to an expert

Thinking about Onsite?

If you need training for 3 or more people, you should ask us about onsite training. Putting aside the obvious location benefit, content can be customised to better meet your business objectives and more can be covered than in a public classroom. Its a cost effective option. One on one training can be delivered too, at reasonable rates.

Submit an enquiry from any page on this site, and let us know you are interested in the requirements box, or simply mention it when we contact you.

All $ prices are in USD unless it’s a NZ or AU date

SPVC = Self Paced Virtual Class

LVC = Live Virtual Class

Please Note: All courses are availaible as Live Virtual Classes

Trusted by over 1/2 million students in 15 countries

Our clients have included prestigious national organisations such as Oxford University Press, multi-national private corporations such as JP Morgan and HSBC, as well as public sector institutions such as the Department of Defence and the Department of Health.