We think you have liked this presentation. If you wish to download it, please recommend it to your friends in any social system. Share buttons are a little bit lower. Thank you!
Presentation is loading. Please wait.
Published bySierra Burgess
Modified over 5 years ago
© Front End Strategy 2010
Swedish Maritime Command and Communication Systems Presenters: Karl Hertz (Front End) – email@example.com Tommy Nordqvist (Front End) – firstname.lastname@example.org Per Erik Mårdberg
© Front End Strategy 2010 1.Introduction of the speakers and the project 2.Introduction to the scenario (operational context) 3.Maritime Communication and Control 1.Operational context developed further (OV) 2.Solutions perspective (SV) 4.Supported analyses 5.Lessons Learned 6.Q & A Agenda
© Front End Strategy 2010 A project in (so far) three stages 1.National C2 systems in a submarine hunting scenario 2.International C2 systems in Atalanta 2 (ME02) 3.National and international C2 capabilities over time A project under the Swedish Defense Material Department contracting Front End, HiQ and Rote Main focus: –Develop descriptions of maritime C2 assets –Develop operational context (requirement environment) for these assets. Maritime Command and Communication Systems, the project
© Front End Strategy 2010 National submarine hunting scenario, chosen for 1.The extensive range of actors 2.The interoperability requirements 3.The complexity of the operational context 4.The recognition factor All in all: Its a complex scenario, spanning over many different types of units and which most stakeholders recognize. Introduction to the scenario (operational context)
© Front End Strategy 2010 Inside the Model – Operational Context Unidentified submerged object (this scenario is fictional)
© Front End Strategy 2010 Inside the Model – OV-2
© Front End Strategy 2010 Inside the Model – other OV models (1)
© Front End Strategy 2010 Inside the Model – other OV models (2)
© Front End Strategy 2010 Inside the Model – OV-2
© Front End Strategy 2010 Inside the model – Realising information exchanges
© Front End Strategy 2010 Inside the Model – Exploring the C2 systems (part 1)
© Front End Strategy 2010 Inside the Model – Exploring the C2 systems (part 2)
© Front End Strategy 2010 Inside the model – A sample of possible analyses (1)
© Front End Strategy 2010 Inside the model – A sample of possible analyses (2)
© Front End Strategy 2010 Ongoing and future work Technical Requirements MODAF Model Operational Context Supports Textual requirements
© Front End Strategy 2010 Key success points Focused project, clear purpose and scope Using the language of the stakeholders Knowing when to stop modeling Using a clear operational context as basis for the model Describing the C2 assets and their usage prerequisite for assessing capabilities now and in the future Close cooperation between Subject Matter Experts and architects An architecture, not for the architect, but for the end user Lessons Learned
© Front End Strategy 2010 Thank you for listening! Presenters: Karl Hertz (Front End) – email@example.com Tommy Nordqvist (Front End) – firstname.lastname@example.org Per Erik Mårdberg
31 December 2013 CIPHER Study Stage An Enterprise Architecture Approach to Options Analysis in Large Acquisition Programmes.
Web Services Architecture An interoperability architecture for the World Wide Service Network.
EA Demonstration Study : Dissemination Forum – 8 June EA Views and Sub-views Patrick Bardet EA Unit.
Modeling with SoaML, the Service-Oriented Architecture Modeling Language: Part 1. Service Identification Rohit Goel, Tommy Omen, Ashley Pham.
ARCHITECTURE FRAMEWORKS IN COMPLEX ENVIRONMENTS SIMPLIFYING THE MYSTERY OF I.T. SYSTEMS IN SMALL AND LARGE ENTERPRISES JOHN HODGSON, I.T. ARCHITECT.
Descriptive Feedback Success Criteria Learning Goals
Human Views for MODAF Dr Anne Bruseberg Systems Engineering & Assessment Ltd, UK on behalf of the Human Factors Integration Defence Technology Centre.
ICT 2010: "Global Information Structures for Science & Cultural heritage: The Interoperability Challenge" Networking Session Coordination Action on Digital.
2009 – E. Félix Security DSL Toward model-based security engineering: developing a security analysis DSML Véronique Normand, Edith Félix, Thales Research.
Key Stage 3 National Strategy Standards and assessment: session 3.
DoDAF V2.0 Community Update Overview
1 © 2006 Curriculum K-12 Directorate, NSW Department of Education and Training Implementing English K-6 Using the syllabus for consistency of teacher judgement.
Creative Arts K-6 Syllabus Using the syllabus for consistency of teacher judgement © 2006 Curriculum K-12 Directorate, NSW Department of Education and.
1. Introduction OASIS Reference Model for Service Oriented Architecture 2. ECF 4.0 Architecture 2.1 Core vs. Profiles 2.2 Major Design Elements 2.3.
Consistency of Assessment
OASIS Reference Model for Service Oriented Architecture 1.0
SWE Introduction to Software Engineering
CAP 252 Lecture Topic: Requirement Analysis Class Exercise: Use Cases.
TSS Architecture Definition Context. TSS Scoping Study Context Detailed Requirements Specification (products, functionality) High Level Architecture Description.
7M701 1 Software Engineering Software Requirements Sommerville, Ian (2001) Software Engineering, 6 th edition: Chapter 5
© 2018 SlidePlayer.com Inc. All rights reserved.