Enterprise Architect version 14.0

download
purchase

enzh-CNcsnlfrdehiiditkoplptruskessv

My Profile

Social Media Channels

facebook google plus twitter youtube linkedin

White Papers

White Papers (83)

White papers provide in-depth technical discussion and best practice guidance on a wide range of modeling topics. The information presented by industry experts from the user community will help you learn new approaches to modeling and solving real-world problems using Enterprise Architect.

Monday, 11 October 2010 00:00

SysML Modelling Language explained

Written by
This article introduces the OMG SysML modelling language, dedicated to complex systems combining software and hardware realisations. SysML, adopted in 2006 by the Object Management Group, provides a vocabulary suitable to Systems Engineering e.g. by modelling Blocks instead of classes. SysML uses a subset of UML2 and defines its own extensions, making it a smaller language that is easier to learn and apply. Abstract: UML, the standard modelling language used in the field of software engineering, has been tailored to define a modelling language for systems: SysML or Systems Modeling Language. This article is intended to provide a non-exhaustive presentation…
Tuesday, 28 September 2010 00:00

eBook: Modeling Service Oriented Architectures

Written by
Presents a practical approach to modeling Service-Oriented Architecture solutions from concept to code. Topics include: generating web service interfaces from visual models, BPEL engineering and behavioral code generation. This E-book presents a practical approach to modeling Service-Oriented Architecture solutions from concept to code. The author helps us to understand key SOA concepts and demystifies the "acronym soup" surrounding service-oriented development. Using an illustrated example, the reader is guided through the 'hands-on' ICONIX Process Roadmap for Service-Oriented Architecture. Each step of the roadmap is brought to life using Enterprise Architect Business and Software Engineering edition to derive concrete deliverables from visual…
This text is the second one of the series of articles concerning projects estimation using the function points method. In the first part entitled: “Theoretical Aspects of Projects Estimation Using the Use Case Points Method" theoretical aspects of the function points method have been presented. Here, an example along with mathematical calculations will be discussed.
This text is the first one of the series of articles concerning projects’ estimation in Enterprise Architect. In this section, theoretical aspects of function points methods have been presented.
Monday, 03 September 2012 00:00

Shaping Service Orientation using Smart Use Cases

Written by
Smart use cases is a particulary useful extension to modeling use cases. This white paper demonstrates how to model smart use cases, especially in service oriented architecture projects. In most projects Enterprise Architect is used with a smart use case UML profile to quickly model and even estimate smart use cases. When applying smart use cases to service oriented architecture, Enterprise Architect can even serve as service repository.
This White Paper examines how using EA to model relationships delivers end-to-end traceability, and looks at how we can use those relationships to bring our documents to life. One of the strengths of Enterprise Architect is that we can use it to capture the full range of project ideas. Not just individual requirements and their priorities, but user stories and use cases, classes and components, test plans and test cases. And we can also capture how those ideas change over time, by keeping risks, issues and actions, which tell the story of the project, in EA as well. Connecting all…
You may wonder why an incomplete or incorrect diagram would be useful. Shouldn't it make sense to aim at producing a good representation right from the start by modelling what needs to be built and achieved? This article deals with a simple approach: incomplete diagrams provide a visual representation of the system to be built, that once shown to stakeholders, product owners, dev teams, and project managers, will trigger feedback and discussions to move towards a shared vision.
Wednesday, 27 February 2013 08:25

Linking the Domain and Requirements Models

Written by
The advent of structured repositories such as Sparx Enterprise Architect, along with well-defined meta languages such as BPMN and UML, opens up new possibilities in the use of domain and requirements models; by linking these models we can begin to ask questions that were previously unanswerable in a rigorous, repeatable fashion.
Thursday, 21 February 2013 12:45

What actor should I use for scheduled use cases?

Written by
This article deals with a recurring question in use case modelling: given a use case that’s automatically triggered by the system clock or timer, what actor should be used? In this context, it is common use to define as the primary actor the system’s clock or timer, since this actor triggers the use case. This article compares three alternatives.
Wednesday, 23 January 2013 05:24

The Value of an Enterprise Information Model

Written by
Background An enterprise architecture reduces the cost of operations, through reuse of standard pieces of technology, application and data, and network . However siloes of information in specialist corporate IT teams are not making it through to a central knowledge base, meaning that function and data are repeated in a string of parallel universes, that are not congruent, and have synergies that remain largely unexplored. Enterprise architectures are often seen as not addressing the coalface reality of reuse and accessibility of data and services. An Enterprise Information Model can address the gap between business and technology owners, practicality and principle,…
Page 5 of 6