Enterprise Architect version 15.2
My Profile
Help
Hot Topics
Top Community Contributors
Social Media Channels
White Papers (102)
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.
Design Driven Testing (DDT) for software was first outlined in the book Use Case Driven Object Modeling with UML: Theory and Practice (by Doug Rosenberg and Matt Stephens), and then described in detail in Design Driven Testing: Test Smarter, Not Harder by the same authors. DDT is a highly methodical approach to testing, allowing you to know when you’ve finished – i.e. when you’ve written enough tests to cover the design and the requirements. It helps you to “zoom in” and write algorithmic tests to cover intensive or mission‐critical sections of code, and to know when it’s safe to “zoom…
Published in
White Papers
Tagged under
Friday, 11 March 2011 00:00
Design Driven Testing for ArcGIS Server Development
Written by doug rosenberg
The attached presentation, from the recent ESRI Developer Summit, presents the design of the hotel mapping application, and discusses bugs that were detected and fixed before product release following the DDT approach. ICONIX has collaborated with Sparx Systems to produce a uniquely powerful set of capabilities for driving testing from Enterprise Architect UML and SysML models. By combining the functionality of Sparx's structured scenario editor and that of the Agile/ICONIX add-in, it's now possible to automatically generate test cases at multiple levels of abstraction. These include two levels of developer testing, including automatic generation of unit test code for JUnit,…
Published in
White Papers
Thursday, 27 January 2011 00:00
Design Driven Testing: Acceptance Testing - Expanding Use Cases using Structured Scenarios
Written by doug rosenberg
Here is Chapter 7 of Design Driven Testing. This chapter focuses on Acceptance Testing, and leverages Enterprise Architect's Structured Scenario editor heavily to accomplish something we call "use case thread expansion" where all of the sunny day / rainy day permutations of a use case are expanded out into a complete set of tests. In "test driven" approaches to development, unit testing often gets most of the attention. However, unit testing is generally most useful in discovering "errors of Commission" (more poetically, "whoops, I coded that wrong"). Unit testing is of much less help in discovering "errors of Omission" (more…
Published in
White Papers
Tagged under
Thursday, 02 December 2010 00:00
Design Driven Testing (Sample Chapter): Design of a Java/Flex hotel mapping (GIS) application
Written by doug rosenberg
In today's agile universe, we often hear about "test-driven" approaches to development (TDD). TDD emphasizes unit testing to such an extent that in many companies, regression testing frameworks like JUnit have largely replaced upfront design. Design Driven Testing makes the case that skipping design in favor of unit testing is not only backwards, but also Too Damn Difficult. We thought the best way to prove it was by designing and testing a real production application... My new book Design Driven Testing (co-authored with Matt Stephens) addresses both unit testing by developers and acceptance testing, performed by an independent QA organization.…
Published in
White Papers
Tagged under
Monday, 25 October 2010 00:00
Business Process Modeling with Structured Scenarios
Written by doug rosenberg
This article (which actually represents the third incarnation of the ICONIX Business Modeling Roadmap), leverages two new capabilities from Sparx Systems, now available in Enterprise Architect. These are the Structured Scenario Editor and the Business Rule Composer. The article describes how these two quantum leaps in technology combine synergistically to enable a new process by combining business process modeling with behavioral code generation for business rules.
Published in
White Papers
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…
Published in
White Papers
Tagged under
Tuesday, 28 September 2010 00:00
eBook: Modeling Service Oriented Architectures
Written by doug rosenberg
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…
Published in
White Papers
Monday, 06 September 2010 00:00
Example of the Application of the Use of the Case Points Method
Written by mw
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.
Published in
White Papers
Tagged under
Monday, 06 September 2010 00:00
Theoretical Aspects of Projects Estimation Using the Use Case Points Method
Written by mw
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.
Published in
White Papers
Monday, 03 September 2012 00:00
Shaping Service Orientation using Smart Use Cases
Written by aahoogendoorn
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.
Published in
White Papers
More...
Friday, 19 October 2012 00:00
Traceability: Making Relationships Work with Enterprise Architect and eaDocX
Written by eadocxjackie
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…
Published in
White Papers
Friday, 29 March 2013 12:11
Why incomplete diagrams are useful in reaching a common vision
Written by Guillaume
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.
Published in
White Papers
Wednesday, 27 February 2013 08:25
Linking the Domain and Requirements Models
Written by laurenceWhite
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.
Published in
White Papers
Thursday, 21 February 2013 12:45
What actor should I use for scheduled use cases?
Written by Guillaume
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.
Published in
White Papers