Enterprise Architect Quick Start - Training, Consulting …in2grateit.com/.../11/Enterprise_Architect_Quick_Start.pdfEnterprise Architect Quick Start Course Overview _____ Ramsay Millar,

_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________

Slide - 1

Quick Start

Enterprise Architect Quick Start Course Overview

Ramsay Millar, INTEGRATE iT ©Copyright

• Product Lifecycle Management (DevOps)• Course Objectives• Requirements• Analysis• Design• Implement• Test• EA Advanced Techniques• Case studies

Ramsay MillarPractice Leader

_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________

Slide - 2

Ramsay Millar, INTEGRATE iTCourse Author and Lead Instructor, Sparx SME Since 2001

• Mentor, Professional Skills Development– Enterprise Architect TOGAF 9.1 Certified course author– Business Architect since 1989– Business Analyst (BACP) since 2003– OMG UML since 1997– Full life-cycle Agile Unified Process since 2001– Project Manager since 1986– 31 years of success in business and IT solutions

• Aligning Business and Technology – Judge of yearly BPM Excellence Awards– OMG Business Architecture Committee– Member of Business Architecture Guild (BIZBOK)– TOGAF Certified consultant and educator– Member of IIBA

• Professional Services– ure

– TOGAF Deployments– Business Analysis– Software Engineering– Sparx Enterprise Architect SME

• Course author– Enterprise Architecture, Business Architecture, Business

Analysis, Software Engineering and CASE tools



_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________

Slide - 3Ramsay Millar, INTEGRATE iT ©Copyright


Best Practices Techniques are Covered in theseBooks and our Courses

Enterprise Architect Quick Start

Enterprise Architect for Business Analysis

Enterprise Architect for TOGAF Architects

_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________

Slide - 4

Product Lifecycle Management (DevOps)

• Beth Business Lead approves product delivery.• Clare BA develops requirements using a

disciplined iterative method using use case stories and software requirements

• Sandy PM tracks deliverable status from all work packages in the scope of work using a custom dashboard that tracks deliverables to Component Work package testing.

• Peter Design Architect reuses the work deliverable created by Clare BA to reduce duplication of knowledge across domains.

• Peter Programmer delivers code for component work packages prepared by Peter Design Architect

• Cheryl Tester tests component work packages• Clare BA runs acceptance tests once Cheryl

Tester releases component testing as passed.• Clare BA marks Component packages as User

Accepted.



_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________


“From business needs to software requirements to code and backas fast and accurately as possible”

•Different skill sets performing different tasks integrating UML traceable work items and requirements to code and back again.


_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________

Slide - 6

Product Lifecycle ManagementBroken Process?


“If a requirement was misunderstood, all modeling decisions based on that requirement are invalid, the code written is also in question, and the testing efforts are now verifying the application under the wrong conditions” ‐ Scott Ambler, Agile Unified Process

IT Project failure is common and analysts report that "as many as 53 % of software projects that fail do so because of poor requirements management, making it the single biggest reason for project failure." Scott Ambler 2015


_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________

Slide - 7

Fix the process!

Agile Unified Process - full life-cycle process• Focus on the customer and quality• Driven by story telling principles for traceability• Focus stories of high business value and risk first• Iterative and Incremental to learn as you go• Promote re-use and avoid rework



_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________

Business Architect – Slide 8

Practice a Use Case Driven Approach



_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________



Importance of Use CasesTrace-ability to All Views

• Five views of Software development• Use case view – describes functional

requirements• Structural View – shows static and dynamic

structures• Component View – depicts components and

subsystems• Concurrency View – concurrent elements of the

software system• Deployment View – determines how the system

maps to physical nodes

Advanced Use Case Modeling – Armour, Miller

_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________

Slide - 10

Use Case Story and Test Driven Requirements Named, Easy, Medium & Complex Stories



_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________



It’s All About FlowCumulative Flow diagram

• Reduce work-in-progress• Focus on quality• Balance demand against

capacity• Prioritize

Source: David Anderson – Agile Managementhttp://www.agilemanagement.net

Iteration Cumulative Flow

020406080

100120140160180200220240

10-Feb

17-Feb

24-Feb

2-Mar

9-Mar

16-M

ar

23-M

ar

30-M

ar

Time

Scen

ario

s

Inventory Started Designed Coded Complete

_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________

Slide - 12

Quick Start





_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________

Slide - 13

Enterprise Architect Quick Start Requirements, Analysis, Design, Implement, Test



_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________

Slide - 14

Quick StartObjectives

• Learn how to use Sparx Enterprise Architect to deliver your next project• Practice developing Requirements, Analysis, Design, Implement, and Test using (RADIT)• Learn how OMG UML models are effective for architecture and development projects• Learn which OG UML diagram to choose to meet your specific modeling needs• Practice using the Business Process Modeling Notation (BPMN) • Practice modeling and writing use case stories• Practice Requirements Management for re-use and traceability• Develop User Interfaces and Data models• Become practiced and confident in your use of Sparx Systems Enterprise Architect • Generate Documentation using Sparx EA



_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________

Slide - 15

Getting Started

• Loading your Course Case Study• Teamwork and Re-use using Sparx EA• Introductions• Understanding OMG UML Modeling• Sparx EA for Business Modeling, Requirements, Analysis, Design and Testing • START – Project Browser, Traceability, Search in Model, Help• DESIGN – Package, Diagram, Toolbox, Element• LAYOUT - Manage, Appearance, Status • PUBLISH – Documentation, Web, Package Control• CONFIGURE – Manage Technology, Manage Security, Images• CONSTRUCT – Resource Allocation, Change, Defects, Issues, Testing• CODE – Scripting, Edit Code • SIMULATE – Simulators, Manage BPSim• EXECUTE - Debugger, Recorder• EXTEND – Manage Add-ins



_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________

Slide - 16

Quick Start





_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________

Slide - 17

Requirements

• Requirements Management best practices • Software Requirements Specification (SRS)• Stakeholder Analysis • Systems Context• BPMN Swimlanes• Scope of Work• Use Case to Roles Matrix• Modeling Use Case stories• Writing a Use Case story • Screen Prototyping • Data Requirements• Functional Requirements• Business Rules• Non-functional Requirements • Logical Data model • Traceability and impact of change • Baseline Show Differences• Generating Documentation



_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________

Slide - 18

Stakeholder Analysisdrive Architecture and Solution Requirements



_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________

Slide - 19

Who?Stakeholder Analysis

• Stakeholder Concerns and Needs drive the requirements of change

• Concerns are a great way to learn about problems

• Problems have solutions• Solutions are requirements• Effective communication of

targeted information to the right stakeholders at the right time is a critical success factor for business architects



_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________

Slide - 20

Process Scope



_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________

Business Architect – Slide 21

TOOLS | Relationship Matrix Role to Activity matrix

• You select a Source package and a Target package, the link type, and direction• You may save your matrix Options | Profile



_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________

Slide - 22

System Context“Case Study”



_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________

Slide - 23

Scope of WorkPackaged by Functionality

• Provides scope of work• Roles are nouns• Name is story goal• Story is strong verb noun• Creates the iteration plan• Provides Work Breakdown,

Resources Allocation



_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________

Slide - 24

Roles and GoalsStoryboarding for Re-use Cases



_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________

Slide - 25

Screen Prototypingdebug Use Case story navigation



_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________

Slide - 26

Screen Prototypingusing the State Diagram



_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________

Slide - 27

Writing Business RulesBusiness Rule Concepts - Getting to the Point of Knowledge

Ronald G. Ross

Terms

A noun or noun phrase with an agreed upon definition.

A term can define:A concept (e.g. client)A property of a concept (e.g. the credit worthiness of the client)A value (e.g. male or female)A value set (e.g. Days of the week)



Statement of Fact

A statement that connects terms, through prepositions and verb phrases into sensible business relevant observations.

Example: Account Holder can courier registration request

Rules

A rule is a declarative statement that applies logic or computation to information values. A rule results either in the discovery of new information or a decision about taking action.

Example:A new customer must not place an order that exceeds $1000

_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________

Slide - 28

Writing Data Requirements

• For each Data Requirement go to the Data Requirement Catalog and see if a Requirement Element of type DR attribute may be re-used

• IF a Data Requirement may be re-used

• Drag and drop the Element over the Use Case in your Use Case diagram - It will display in the Requirement tab.

• If a Data Requirement does not exist then create a New Requirement Element of type DR in the Data Requirements package



_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________

Slide - 29

Writing a Functional Requirements

• This requirement’s “writing” checklist adapted from IEEE Standard 830 – 1998: IEEE Recommended Practice for Software Requirements Specifications (SRS)

• Use this checklist across all phases of product development including:

– Business Modeling– Business Analysis– Solutions Architecture– Design Architecture– Technology Architecture– Testing – Requirements Management

for the entire life time of the software system once delivered



_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________

Slide - 30

Writing Non-functional RequirementsInformation Technology Infrastructure Library (ITIL)



http://kpilibrary.com/categories/itsmitil

_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________

Slide - 31

Logical Data model

• Logical Data models, properly designed, should be based on the structures identified in the conceptual information model, since this describes the semantics of the business, which the logical model should also reflect.

• Even so, since the logical data model anticipates implementation and further elaborates the Conceptual Information model going into more detail to capture

– Attributes, data types, length, Multiplicity (cardinality)



_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________

Slide - 32

Quick Start





_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________

Slide - 33

Analysis

• Solutions Analysis Reference models and Standards

• Solution Architecture Document (SAD)• The Object Oriented Approach• Analysis - Sequence diagram• Boundary Objects – User Experience• Business Objects• Data Objects• Physical Data modeling• Reverse Engineer a Relational Database• Generate a Data Modeling Report• Creating Tables, Attributes, and Foreign Keys• Creating Indexes, Triggers, Procedures• QA & Peer Review



_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________

Slide - 34

Solution Architect Analysis - Construction



_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________

Slide - 35

IT service packages containthe Use Case model

• Name Use Cases with strong Verb Noun phrases

• Names are written using business terms

• All Use Cases are written from the Role view

– That is outside looking in

– Voice of the customer

• Create a package named after each Service



_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________

Slide - 36

UML Communication diagram

• Communication Diagrams are helpful when designing screen dialogs to indicate which objects are required to provide services



EA TIPYou can paste Screen images from your favorite screen painter, Dreamweaver, VBForms, etc. and place this over the EA Screen prototype object.

EA allows you to paste any image file over any object you wish to increase functionality

_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________

Slide - 37

Service Oriented Architecture – Sequence Design”“Project example”



_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________

Slide - 38

Service Oriented Architecture - Component Design“Project example”



_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________

Slide - 39

Generating or Reversing SQL Code

• Enterprise Architect’s built-in Data Modeling profile extends UML to provide an intuitive mapping from the database concepts of tables and relationships onto the UML concepts of classes and associations.

• These extensions also enable you to model database keys, triggers, constraints, referential integrity, and other relational database features.

• Enterprise Architect supports modeling of database schema and automatic generation of DDL – DB2 – InterBase– Informix – Ingres – MS Access – MySQL– MS SQL Server – Oracle – PostgreSQL– Sybase ASE, ASA – Firebird



_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________

Slide - 40

Quick Start





_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________

Slide - 41

Design

• Software Engineering best practice techniques• UML Design Patterns• Model Driven Architecture (MDA)• Code Warrior - Reverse Engineering• Construction – Design deliverables• Designing Behavior – Sequence diagram• Designing Messages & Operations• Messaging other Sequences diagrams• Designing Collections• UML State diagram• Designing Structure – Class diagram• Designing Associations, Aggregation & Inheritance• Designing Implementation packages• QA & Peer Review



_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________

Slide - 42

Design

• Moving from Elaboration to Construction• Provide delivery (beta) system for software

acceptance by sponsor• Develop the Software Architecture Class

Diagrams• Generate the Stub code for Eclipse or Visual

Studio• Analysis Use Case scenarios and realizations

are used for testing which leads to most (not all) defects being corrected

– Sequence diagrams– Messages– State Diagrams– Class Diagrams– Deployment Packages



_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________

Slide - 43

Design

“

“The faster you begin to coding when you start a new project the longer the project will take”Scott Ambler, Agile Founder and IBM Practice Leader



You guysstart coding andI'll find out whatthey want!

_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________

Slide - 44

Enterprise ArchitectJolt Productivity Award - Best Design & Code Warrior’s tool



_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________

Slide - 45

Model Driven Architecture (MDA)http://www.omg.org

Sparx Systems is committed to developing and evolving MDA support within their UML 2.1 based modeling tool, Enterprise Architect.



_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________

Slide - 46

Improving your Designby using UML Design Patterns

• Head First Design Patterns – Freeman, Sierra, Bates

• Design improvement techniques– http://www.refactoring.com/– Refactoring: Improving the Design of Existing Code

• Design patterns– Larger improvements– Often involve multiple classes working together– http://msdn.microsoft.com/practices/– Net Patterns: Architecture, Design, and Process

• Applying UML and Patterns :An Introduction to Object-Oriented Analysisand Design and the Unified Process – Craig Larman



_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________

Slide - 47

Architecture using ABB’s and SBB’s“Project example”

A Component can be composed of multiple Classes, or Components pieced together. As smaller Components come together to create bigger Components, the eventual system can be modeled, building-block style, in Component diagrams. (ie) TOGAF building blocks example from Production



_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________

Slide - 48

A Story writing drives Object-OrientedSoftware Design, and Engineering



_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________

Slide - 49

A Story drives Object-OrientedSoftware Design and Engineering



_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________

Slide - 50

Component Design



_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________

Slide - 51

Quick Start





_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________

Slide - 52

Implement

• Implementation Best Practices• Component Sequence model• Create a Component Traceability model• Component Building Block Traceability• Create a Deployment model• Adding Alternate Images• Create a Architecture Nested Traceability



_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________

Slide - 53

Solution Architecturemay be very complex



_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________

Slide - 54

Solution ArchitectureEA Models make is simpler



_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________

Slide - 55

Quick Start





_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________

Slide - 56

Testing

• Use Case stories drive all testing• Create a User acceptance test• Generating the User acceptance test report



_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________

Slide - 57

A Use Case story drives all testingA Story is written, understood, and approved

The Testing window, or Workspace, provides a quick and convenient method of working with element tests. When you select an element in a diagram or in the Project Browser, if the Testing window is visible the lists of tests for that element are loaded ready for modification or addition.



_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________

Slide - 58

Acceptance Testing Report

• Use Acceptance Testing to ensure that users are satisfied with the system• Best Practice - Build Acceptance scripts before software development and testing



_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________

Slide - 59

Quick Start





_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________

Slide - 60

EA Advanced Techniques

• Documentation - Linked Documents• Documentation - Using Work Package Templates• Documentation - Creating a Model Document• Documentation - Customizing Sparx EA Templates• Documentation - Generate the MS Word Document• Diagramming Techniques• Exporting - EA Requirements using MS Office Add-in • Searching the Repository• Tagged Values - Requirements Management• Traceability Techniques



_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________

Slide - 61

Quick Start





_______________________________________________________________________________________________________________________

___________________________________________________________________________________________________________

Slide - 62

“The voice of our clients say it all”



http://in2grateit.com/wp‐content/uploads/2015/09/Health‐Reform‐case‐study.pdf

http://in2grateit.com/wp‐content/uploads/2015/09/DrDobbsInterview.pdf