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 3 years ago
© Front End Strategy 2010
Swedish Maritime Command and Communication Systems Presenters: Karl Hertz (Front End) – Tommy Nordqvist (Front End) – Per Erik Mårdberg
© Front End Strategy 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) – Tommy Nordqvist (Front End) – Per Erik Mårdberg
Human Views for MODAF Dr Anne Bruseberg Systems Engineering & Assessment Ltd, UK on behalf of the Human Factors Integration Defence Technology Centre (HFI.
Enterprise Business Information Model Enterprise Data Services.
Architectural Framework. The business requirement for MODAF MODAF explained –What is it? –How will it work? –How is it being delivered? MODAF Meta Model.
ARCHITECTURE FRAMEWORKS IN COMPLEX ENVIRONMENTS SIMPLIFYING THE MYSTERY OF I.T. SYSTEMS IN SMALL AND LARGE ENTERPRISES JOHN HODGSON, I.T. ARCHITECT.
OOI CI LCA REVIEW August 2010 Ocean Observatories Initiative OOI Cyberinfrastructure Architecture Overview Michael Meisinger Life Cycle Architecture Review.
The Computer Science Course at Omar Al-Mukhtar University, Libya The Computer Science Course at Omar Al-Mukhtar University, Libya User-Centered Design.
2009 – E. Félix Security DSL Toward model-based security engineering: developing a security analysis DSML Véronique Normand, Edith Félix, Thales Research.
CAP 252 Lecture Topic: Requirement Analysis Class Exercise: Use Cases.
Managing Enterprise Architecture Federal Enterprise Architecture.
31 December 2013 CIPHER Study Stage An Enterprise Architecture Approach to Options Analysis in Large Acquisition Programmes.
Creative Arts K-6 Syllabus Using the syllabus for consistency of teacher judgement © 2006 Curriculum K-12 Directorate, NSW Department of Education and.
Clarke, R. J (2001) S213-02: 1 Multimedia in Organisations BUSS 213 Supplementary 2 Use Cases & Descriptions.
How business and IT interoperate using SOA
© 2004 Popkin Software & System Inc.. Enterprise Architecture and Business Process Modelling Developing a business-centred architecture Architecture Practitioners.
Quality Assessment of MFA’s evaluations Rita Tesselaar Policy and operations Evaluation Department Netherlands Ministry of Foreign Affairs.
EA Demonstration Study : Dissemination Forum – 8 June EA Views and Sub-views Patrick Bardet EA Unit.
1 DoDAF V2.0 Community Update Overview 12 August 2010 MR. MICHAEL WAYSON Architecture and Infrastructure Directorate Office of the DoD Deputy Chief Information.
A Speech Interface to Virtual Environment Authors Scott McGlashan and Tomas Axling Swedish Institute of Computer Science.
Part-financed by the European Union (European Regional Development Fund) Maritime Spatial Planning as Tool for Underwater Cultural Heritage management.
ICT 2010: "Global Information Structures for Science & Cultural heritage: The Interoperability Challenge" Networking Session Coordination Action on Digital.
Introduction A strategy was required to be able to maintain desktop configuration and reduced support cost. Hardware and software capabilities continually.
Modeling with SoaML, the Service-Oriented Architecture Modeling Language: Part 1. Service Identification Rohit Goel, Tommy Omen, Ashley Pham.
NIEM Domain Awareness June 2011 Establishing a Domain within NIEM.
Presented for discussion with Implementation SIG Heather Grain.
A GENERIC PROCESS FOR REQUIREMENTS ENGINEERING Chapter 2 1 These slides are prepared by Enas Naffar to be used in Software requirements course - Philadelphia.
Development Principles PHIN advances the use of standard vocabularies by working with Standards Development Organizations to ensure that public health.
Co-ordinated by aparsen.eu #APARSEN Co-funded by the European Union under FP7-ICT The importance of interoperability and intelligibility in digital.
EA Modelling & Communications Tutorial 5. Your EA Learning Journey So Far Week 1 Introduction Concepts WHAT IS Week 2 EA Theories WHAT IS Week 3.
The Project – Spreadsheet Specification Items to include in your Spreadsheet Specification 1)Scenario relating to the Spreadsheet part of the system 2)Problems.
Training of master Trainers Workshop 10 – 15 November 2012 e-Services Design and Delivery Module VI Emilio Bugli Innocenti.
1 A Practical Rollout & Tuning Strategy Phil Shinn 08/06.
7M701 1 Software Engineering Software Requirements Sommerville, Ian (2001) Software Engineering, 6 th edition: Chapter 5
REQUIREMENT HANDLING Requirement Analysis Phases Inception (initiation) Elicitation (gathering) Problems of scope Problems of understanding.
Information Modeling: The process and the required competencies of its participants Paul Frederiks Theo van der Weide.
Presenter(s) Name(s) Department May 18, 2010 Title of Presentation.
CPSC 871 John D. McGregor Module 4 Session 3 Architecture Evaluation.
SUBTITLE DAY, MONTH, YEAR Accreditation Support for Teachers Introduction to Accreditation at Proficient Teacher Module 4 of 5.
(SRS) SOFTWARE REQUIREMENT SPECIFICATION(SRS) 1. Topics to be discussed.. What is an SRS? Purpose of an SRS Who reads the SRS? Who writes the SRS? Characteristics.
Management & Development of Complex Projects Course Code MS Project Management Project Life Cycle & PM Process Groups Lecture # 4.
Nov.19, 2004 Jon Stuart, Ph. D Task Analysis: A Foundation for Safety.
Consistent Teacher judgement School Based Assessment and Reporting Unit Curriculum Directorate © 2006 Curriculum K-12 Directorate, NSW Department of Education.
1Tele2 SA Role Presentation, Kentor Solution Architect at Tele2 Statement Of Work Pre-study Gate1 Inception phase Gate2 Implementation.
Project Kick-off Meeting Presented By: > > > > Office of the Chief Information Officer.
SE-02 SOFTWARE ENGINEERING LECTURE 3 Today: Requirements Analysis Requirements tell us what the system should do - not how it should do it. Requirements.
Applied IT Architecture Introduction Reference IT architecture & Standards Applied Reference Architecture Governance model Governance process Problems.
IRM304 CDR Course Manager: Denny Involved Competency Leads: 26 (Cybersecurity)-Denman, 19 (Measurement)-Denny, 7 (DBS)-Corcoran [Capability Planning],
Assessing the influence on processes when evolving the software architecture By Larsson S, Wall A, Wallin P Parul Patel.
Facilitating Multi Stakeholder Processes and Social Learning Herman Brouwer/ Karèn Verhoosel Centre for Development Innovation MSP Generic Process.
Use Case Diagram (UCD) Yong Choi BPA. What is UCD? A use case is a set of scenarios that describing an interaction between a user and a system. – What.
A centre of expertise in digital information managementwww.ukoln.ac.uk Approaches To E-Learning: Developing An E-Learning Strategy Brian Kelly UKOLN University.
© 2017 SlidePlayer.com Inc. All rights reserved.