- WEB-based access to Enterprise Architect (EA) models from everywhere - No client installation required - Simple table-based user interface - no modeling knowhow required - Work on same EA models via web browser and with EA application - Customizable role-oriented views - Traceability through all development phases - Scalable from local up to enterprise level - All in one - communication platform for different roles, suppliers and customers

1. Enterprise Architect in the Web
Use Case: Requirements Management
Dr. Konrad Wieland
LieberLieber Software GmbH
http://lieberlieber.com
http://blog.lieberlieber.com
konrad.wieland@lieberlieber.com

2. LieberLieber
 Austrian Company - Vienna
 Partner of Sparx Systems
 Contributing member of OMG
 20+ Engineers
 Focus Areas:
 Model Engineering
 Multitouch
 .NET Engineering
Embedded World 2013

3. SparxSystems Enterprise Architect
 Enterprise Architect Modeling Platform
 More than 300.000 users world-wide
 Comprehensive UML analysis and design tool
 Rich modeling for business, software and systems
 Full traceability from requirements to deployment
 Code engineering in over 10 languages
 Scalable, team-based repository
Embedded World 2013

4. Motivation
 Need for heterogeneous information
 Different people need different information
 Enterprise Architect provides the possibility to manage
„all“ information, but…
 EA is a complex tool
 Many modeling languages
 Tooling (Where is what?)
 Where to start, where to end?
 Different roles need different views to get information…
 they need
 in a way to easily understand it
Embedded World 2013

5. Why not using EA alone
 EA is customizable
 Tool bars,
 toolboxes,
 menus
 But still too complex??!
 EA is a swiss army knife
 But often you only need a spoon!!??
Embedded World 2013

6. EnArWeb 1.0
EnArWeb
can be configured to show only the required
information which is needed by the user
in a comprehensive and user-friendly way
Embedded World 2013

7. EnArWeb in a Nutshell
 WEB-based access to Enterprise Architect (EA) models
from everywhere
 No client installation required
 Simple table-based user interface - no modeling
knowhow required
 Work on same EA models via web browser and with EA
application
 Customizable role-oriented views
 Traceability through all development phases
 Scalable from local up to enterprise level
 All in one - communication platform for different roles,
suppliers and customers
Embedded World 2013

8. How to benefit from EnArWeb
 Brigdes the gap between users who
 EA users and not-EA users
 Portal-based approach
 Role-based security system
 Simple and customizable UI
 Direct acces without consistency problems
 Simple views and dedicated workflow
Embedded World 2013

9. Core Domain Concept of EnArWeb
User Account
0..* Permission
Role Permission
0..* 0..* 1 1
Group
EA Repository
1
Repository Role
View

10. EA Web Client EA Web Client
Requirement Customer
Engineer
EA Web Client
EA
Data Base
Project
Server
Manager
EA Web Client EA Desktop Client
Admins System
Engineer

11. What Requirement Engineers do
 works with stakeholders and end users
 elicits, understand, analyze and document the
requirements
 control the realization of requirements
 And how to support them with EnArWeb…
Embedded World 2013

12. EnArWeb at a Glance
Create Model
Elements
Pie Chart
Granularity
Different
Views
Lock/Unlock Matrix Report
Advanced search
Filter
Embedded World 2013

13. Grid View

14. Interactive Pie Chart View (1)

15. Interactive Pie Chart View (2)

16. Interactive Matrix Report
Embedded World 2013

17. Trace View
uc Use Cases
System
Requirement1 Components::
Use Case4
Component4
(from System Requirements)
«include»
Use Case5
«include»
Use Case1
Embedded World 2013

18. And inside EA…
Embedded World 2013

19. End-to-End Traceability (within EA)
 Define, model, manage and trace requirements
 Define an organized, hierarchical requirements
model
 Trace system requirements to model elements
 Search and report on requirements
 Perform impact analysis of proposed changes to
requirements
Embedded World 2013

20. Send Link to Element
Embedded World 2013

21. Administration
User Management View Management
Application Log Application Settings

22. Administration
1. Create Roles and Users
2. Create Views
Embedded World 2013

23. Repository Role Definition

24. User Management
Embedded World 2013

25. View Definition
Embedded World 2013

26. Conclusion and Outlook
 Web-based front-end for Enterprise Architect
 No client installation
 Simple user-interface
 Different views for different roles of different users
with different rights
 … to get the right information in an optimized view
 Look forward to:
 Configurable layout
 Diagram view
Embedded World 2013

27. Enterprise Architect in the Web
Dr. Konrad Wieland
LieberLieber Software GmbH
http://lieberlieber.com
http://blog.lieberlieber.com
Embedded World 2013
konrad.wieland@lieberlieber.com