BUY YOUR TICKETS NOW for just £50
Join us on May 16th for a full day of great content.
|Welcome - Knut Paulsen
Unlike the more popular user stories, smart use cases provide a unique, and structured way to deliver requirements in both agile and traditional projects. During this high speed talk Sander Hoogendoorn, Principal Technology Officer and Global Agile Thoughtleader at Capgemini, will demonstrates a proven approach to identifying, modeling and estimating smart use cases from the project's scope and business processes. It will also show how smart use cases nicely fit your online dashboards, your software architecture, how code is generated from them, and how testing can be automated as well. This interactive talk contains live demos and answers a lot of questions:
How do you model smart use cases using Enterprise Architect?
How can we estimate smart use cases?
How do functional requirements match model driven development?
Can code actually be generated from requirements?
Can model driven development be applied in agile projects?
Can model driven development using Enterprise Architect speed up testing?
This talk is high-paced, interactive and packed with new insights. It will also demonstrate the effective use of tools in effective and pragmatic agile model driven development and contains live coding (in C#) on stage.
|Track 1: Customer Experiences
||Track 2: Using EA / EA Techniques
||Track 3: Extending EA
The power of stereotypes
Models to shout about
|Pablo Oliveira Antonino
Managing artifacts traceability
in agile development
|Systems of systems architecture presents a number of challenges that are only partially addressed by existing architecture frameworks. In the context of border security systems architecture and design, a team at Airbus Defence and Space have designed a comprehensive set of stereotypes that concurrently address architecture/design perspectives, i.e. functional, nonfunctional, deployment, roles, data and assets, and the level of abstraction of each artefact e.g. enterprise, operational, system level 0. The stereotypes are then employed to achieve the purposes of NATO Architecture Framework views through a set of predefined diagram types for each selected sub-view. A bespoke MDG Technology supports stereotypes, diagram types, toolboxes and enumerations, while eaDocX and eaXL templates are used to generate combined architecture and requirements documentation, including extensive reporting of traceabilty.
The results have been encouraging.
Users of Enterprise Architect need no convincing about the value of modelling rather than just writing down their analyses and designs.
In this presentation Ian will show how to share these benefits by targeting stakeholders with the EA information they need in a way they can understand.
Drawing on his experiences in many organisations, Ian will show how tailoring documents for specific stakeholders can improve their engagement with your project, using examples from the eaDocX document generator.
|An Enterprise Architect based solution for managing artifacts traceability in agile development|
Succeeding with Services
Model Your Enterprise Architecture
with ArchiMate and
Sparx Systems Enterprise Architect
Re-presenting elements of EA to
improve access and productivity
|Karona's approach to Service Specification has been in use at John Lewis Partnership for 10 years now and has become the de facto standard for systems analysis and design.
Benefits of the approach include:
• a clean "separation of concerns" between the logical and physical layers of the system specification
• easy incorporation of design patterns and code frameworks
• full traceability from business requirement to code
• excellent system maintainability
In this talk we will present an overview of the types of diagram used and the organisation of the project model
|How to model business organisation, processes and products using ArchiMate business layer viewpoints.
Create an application landscape and understand dependencies using ArchiMate application layer viewpoints.
Catalogue company infrastructure (hardware, system software and networks) using ArchiMate technology layer viewpoints.
Identify stakeholders, drivers, goals and requirements using the ArchiMate motivation extension.
|One of the strengths and weaknesses of EA is its flexibility, however in providing this flexibility it can mean that a user is presented with information that they don’t need.
For the new user, who may be tasked with populating a model, this may mean they are presented with information that is not relevant, or even understood, by them, and can lead to confusion.
For the experienced user, the need to trawl through long lists or switch between dialogues when creating or modifying an elements' properties can hamper their productivity.
In this talk we outline, through real examples, one of the key challenges faced by new users of EA, and the approach we have adopted to give them some familiarity, help ensure consistency and, in general, make EA more accessible to a wider range of users.
For those who have an interest in looking under the hood, we will briefly provide some insight into how the AddIn works and how it could further be extended as users’ needs expand.
Paul Hewitt, Visure
Bridging the gap between EA Model Driven System Development and Requirements Management
The aim of this paper is to explore the benefits of capturing the initial stakeholder requirements in the context of their KPI’s in a requirements management tool while maintaining explicit traceability through an integration with EA, to support the expansion and decomposition of the requirements within EA, to derive the lower level system requirements. This allows the textual requirements information to be synchronized in real time with the EA model artefacts, providing a cohesive view of the functional and non-functional requirements, including explicit traceability back to the original stakeholder objectives. By establishing this information traceability and synchronization from the origination stakeholder requirements to the EA model artefacts, management metrics reports on project progress can be produced at any time and fully formatted specifications can be published out of the requirements database, to document the ‘as delivered’ system. The presentation discusses how we can effectively ‘bridge the gap’ between engineering teams, who are familiar with EA model driven system representations, and the project managers and commercial staff, who still need the legal interpretation of the system description to be presented as text based contract documents.
Current project for the
EA Version 11 Cloud Services,
OSLC and RAS
Make EA your tool using offerings from
the Marketplace - An overview
|“We’ve developed an innovative and technically robust UML-based data management and sharing lifecycle support solution for the Environment Agency [England]. Realised through Sparx Systems' Enterprise Architect our approach profits from UML's inherent functionality, flexibility and extensibility but represents a significant departure from UML's traditional use as "the de facto standard for building Object-Oriented software".
We have developed a methodology that integrates analysis of the Environment Agency's corporate data landscape with existing, but disparate, data sharing initiatives into a coherent, efficient and effective framework. This framework has formed the basis of a step change in how the Environment Agency manages the numerous work streams and obligations that enable it to meet its data sharing objectives. This includes the opportunity for increased interoperability and data sharing brought about by the INSPIRE Directive. It does so by providing a single point of access to a vast and varied repository of information ranging from:
1. the flow of intellectual property and knowledge of the relationships between distinct geospatial and geospatial datasets,
2. the technical and legal constraints to data sharing including those specific to geospatial information,
3. the geospatial and other data standards applied, or applicable, to a dataset (including INSPIRE UML data specifications and transformation requirements),
4. the organisational or legislative drivers for data creation and data sharing,
5. the specific data sharing solutions (such the Environment Agency's DataShare portal, data.gov.uk, etc).
Importantly, the solution manages and presents all of the above complex information in a easily digestible manner which is critical to its use as a true corporate data management and sharing lifecycle tool.
The Data Flow Mapping (DFM) solution became operational within the Environment Agency during 2013. It's implementation has met all its deliverables and milestones and was delivered to time and budget. DFM has already realised significant financial, business and data management benefits for the Agency. The Environment Agency has presented the solution to other public sector bodies with very positive feedback as a genuinely innovative approach to improved service delivery in a cost effective, holistic manner that is both sustainable (critical to ensure currency and usefulness) and technically robust”
|To me one of the most exciting features in EA Version 11, is Cloud Services. During this session I will provide an overview of Cloud Services the setup required in order to use them., and the supoort of OSCL
I will then provide a demonstration of Cloud Serices and OSLC in action
The second half of the session will focus on RAS (Reusable Asset Services) which provides tantilising opportunties for collaborative and distributed working, I will describe what RAS is, what RAS can be used for and will conclude with a demonstration of RAS in action.
|Daniel will inspire you to customize EA to make it "Your Tool". An overview of Tools on the Market and ways how to customize EA will be provided.|
Enterprise Architect for an Enterprise Architecture
|Guillaume Finance and Howard Burgess
Alternatives available to set up a shared EA
repository to work in a collaborative environment
|How to introduce an Enterprise Architecture based on the ArchiMate 2.0 notation and Enterprise Architect? This mid-size government agency has an architecture team of four members. There is a problem in producing architecture documents like Project Start Architectures, it takes too much time and the resulting document has limited value for the projects. This is mainly caused by the lack of overview on the baseline and the target architecture. Introducing an architecture repository helped a lot in improving our architectural overview and producing these documents. There are positive results in the overview, generating documents and involving various stakeholders. But there are also a number of lessons learned and various new challenges.
More information: http://community.sparxsystems.com/case-studies/781-enterprise-architect-for-an-enterprise-architecture
|Enabling a team to work in a collaborative mode on the same Enterprise Architect project is paramount to share to information and let everyone participate in building the repository.
Once you start looking at the available options identified by Sparx Systems via the user guide and their White Paper, you notice that several options are available, yet there isn't one good option. Each alternative has its own advantages and disadvantages to match with the project constraints (size of the team, working on the same network or with remote teams, etc.).
The content of this presentation is based on several real life experiences where the EA configuration and choice of accompanying tools had to be tailored for each context