Cheltenham, United Kingdom
Cheltenham, United Kingdom

Time filter

Source Type

Hause M.,Atego
22nd Annual International Symposium of the International Council on Systems Engineering, INCOSE 2012 and the 8th Biennial European Systems Engineering Conference 2012, EuSEC 2012 | Year: 2012

Modeling of the electric utility network is normally done using bespoke or custom tools and programs rather than generic modeling languages. This requires the engineer to develop the complete simulation system from scratch. In addition, it is difficult to model from different viewpoints and levels of abstraction. The models are normally created from a single perspective to solve a specific problem or analyze the system from a single point of view. The Systems Modeling Language (SysML) was developed by INCOSE and the OMG to provide general purpose modeling language for systems. Most published examples of SysML are of electro-mechanical software intensive systems in the aerospace and transportation industries. This paper documents a work in progress by the author to develop a model of an example electric utility network, including the user interface to show how SysML can be used to model complex systems of systems. In addition, it shows how a simulation tool integrated with SysML provides a means of integrating multiple paradigms as well as a Human Computer Interface to the simulation. © 2012 by Matthew Hause.


Coleman J.W.,University of Aarhus | Malmos A.K.,University of Aarhus | Larsen P.G.,University of Aarhus | Peleskay J.,University of Bremen | And 7 more authors.
Proceedings - 2012 7th International Conference on System of Systems Engineering, SoSE 2012 | Year: 2012

It would be useful to have a tool platform that supports systematic engineering of Systems of Systems, especially focused on the case where multiple parties are collaborating on the development. We attempt to provide a vision for a tool that allows collaboration on models developed jointly and that can be systematically analysed. The focus is on the challenges that make this kind of tool - a Collaborative Development Environment- different from a traditional Integrated Development Environment. Finally the paper describes the plans of the COMPASS project to address these challenges. © 2012 IEEE.


DeAntoni J.,French Institute for Research in Computer Science and Automation | Mallet F.,French Institute for Research in Computer Science and Automation | Thomas F.,Obeo Inc | Reydet G.,Obeo Inc | And 5 more authors.
Proceedings of the ACM SIGSOFT Symposium on the Foundations of Software Engineering | Year: 2010

This presentation demonstrates the early results from the French ANR project RT-Simex. RT-Simex proposes a set of tools to analyze parallel embedded code and trace the simulation results back to the initial models from which the code was generated. The whole tool-set relies on standard formats (UML MARTE, Open Trace Format) to ensure a perennial use. The main difficulty is to reconcile different execution traces extracted from codes running concurrently on different unsynchronized platforms. This is achieved through the polychronous logical time model of MARTE.


Woodcock J.,University of York | Cavalcanti A.,University of York | Fitzgerald J.,Newcastle University | Larsen P.,University of Aarhus | And 2 more authors.
Proceedings - 2012 7th International Conference on System of Systems Engineering, SoSE 2012 | Year: 2012

We discuss the initial design for CML, the first formal language specifically designed for modelling and analysing Systems of Systems (SoSs). It is presented through the use of an example: an SoS of independent telephone exchanges. Its overall behaviour is first specified as a communicating process: a centralised telephone exchange. This description is then refined into a network of telephone exchanges, each handling a partition of the set of subscribers (telephone users). The refinement is motivated by a non-functional requirement to minimise the cabling required to connect geographically distributed subscribers, who are clustered. The exchanges remain as independent systems with respect to their local subscribers, whose service is unaffected by the loss of remote exchanges. © 2012 IEEE.


Audsley N.C.,University of York | Gray I.,University of York | Acquaviva A.,Polytechnic University of Turin | Haines R.,ATEGO
Proceedings - IEEE International High-Level Design Validation and Test Workshop, HLDVT | Year: 2012

Run-time platform variability presents a number of challenges to the system software in order that a run-time environment is presented to applications that sufficiently masks dynamic platform variability (including fabrication variability), whilst allowing applications to tune overall system performance to exploit key aspects of dynamic energy usage and platform variability. The approach taken within the Touchmore project is to model key aspects of the platform in order that performance and variability can be understood and exploited by the system software. In turn, the system software (comprising OS and run-time) utilises the model so that aspects of variability and energy usage are abstracted from the platform, then monitored and controlled in order to meet policy goals, eg. energy minimisation. This paper documents aspects of the modeling and system software structure to show how the Touchmore project is managing energy and platform variability using customisation of the application, system software and toolchain. © 2012 IEEE.


Hause M.C.,Atego
IEEE Aerospace Conference Proceedings | Year: 2014

Systems of Systems (SoS) modeling is becoming increasingly important in both civilian and military systems. The Department of Defense (DoD) Defense Acquisition Guidebook, [1] defines a SoS as a 'set or arrangement of systems that results when independent and useful systems are integrated into a larger system that delivers unique capabilities.' Organizations are changing their emphasis from 'We need a new system' to 'We need to achieve a specific outcome.' As these outcomes become more complex and the associated systems more complex, the management, modeling and simulation of these SoS becomes equally challenging. Often, the SoS is modeled in all its complexity, often at a single level of abstraction or level of detail. Instead of a 'megamodel' approach, a standards-based 'model of models' approach is what is necessary. This approach will use the Object Management Group (OMG) Unified Profile for DoDAF and MODAF (UPDM) for modeling enterprise architectures from capabilities to detailed components, and the Reusable Asset Specification (RAS) for defining reusable assets. Combining UPDM and RAS provides a Model of Models approach with the main model specifying assets in various levels of details. The models specified by these assets can be referenced when detailed analysis is required, or hidden when a SoS viewpoint is required, allowing the analyst to see the forest through the trees. The paper will also include an assessment of the applicability and effectiveness of this approach. The International Conference on Systems Engineering (INCOSE) System of Systems Working Group (SoSWG) has collected a set of 'Pain Points on SoS' from a variety of international sources. This paper will review these pain points and discuss how the application of a Model of Model approach, combined with standards-based modeling tools and a reusable assets approach can help to alleviate some of the pain currently being felt by SoS architects and managers. Hopefully, this response to their SOS will deliver some much-needed assistance. © 2014 IEEE.


Hause M.,Atego
23rd Annual International Symposium of the International Council on Systems Engineering, INCOSE 2013 | Year: 2013

The book of Genesis tells the story of how the peoples of the earth came together to build an enormous tower. To confound them in their task, God changed the languages of the different groups of people so that they were unable to communicate. Since they could not coordinate their efforts, the project was abandoned and the different groups dispersed throughout the world. The same problem exists today in the world of Enterprise Architecture Frameworks. Although they express similar concepts, interchange between the different frameworks is awkward at best, time consuming, and leads to misunderstanding and miscommunication. This lack of communication was highlighted in a recent report on the conflict in Afghanistan, where the lack of interchange of architectures was cited as a limiting factor in coalition efforts and may have contributed to loss of life. This paper will assess the current situation, examine international efforts to solve it, and identify future challenges. This will include: • The role of standards for collaboration and communication • Standards and standards organizations • The Object Management Group (OMG) • A brief history of Military Architectural Frameworks • The interoperability problems of frameworks • The Unified Architecture Framework (UAF) effort • Using reference architectures to define a common conceptual "dictionary" • Systems engineering, acquisition, and process • Vertical and horizontally complementary emerging standards • Future problems and potential solutions. © 2013 by Author Matthew Hause.


Brownsword M.J.,Atego | Holt J.D.,Atego | Perry S.A.,Atego
IET Conference Publications | Year: 2011

There may be many points of view that need to be considered when identifying, defining and assessing risks. A contextbased approach supports the identification and understanding of risks as well as providing a focus for risk assessments through the application of different viewpoints. This paper uses the ability to focus on viewpoint to provide the identification of concerns and risks. It discusses ways to identify system views from which concerns can be elicited and proposes the views needed to present cause and effect analysis. Finally, mitigation views will be discussed which are used to present possible system changes based on the results of analysis. A safety critical situation directly related to marketing and business needs will be discussed. This case study will show how the views can be used and how they integrate with existing Model-Based Systems Engineering (MBSE) approaches.


Holt J.,Atego | Perry S.,Atego | Brownsword M.,Atego | Hause M.,Atego
2010 5th International Conference on System of Systems Engineering, SoSE 2010 | Year: 2010

This paper presents an approach to systems engineering and system-of-systems modeling that is based on the idea of context modeling. Based on over ten years of research and application the approach forms the basis of ACSE (Atego Context-based Systems Engineering). Many traditional approaches to systems modeling represent systems as high-level blocks and then show subsystems using aggregation and composition; providing a representation of a system as a structured hierarchy. This paper suggests that this structure-based approach is unrealistic and unreliable and proposes a context-based approach to systems modeling. Contexts represent systems from particular stakeholder's points of view; it is suggested that a combination of these contexts are used as a basis for systems modeling and, hence, understanding. Following this it is suggested that system of systems can be represented in this way, by defining higher-level contexts. This is illustrated thought a simple example demonstrating the principle of context-based system engineering. © 2010 IEEE.


Hause M.,Atego | Kihlstrom L.-O.,Syntell AB
23rd Annual International Symposium of the International Council on Systems Engineering, INCOSE 2013 | Year: 2013

The capture of system structure, behavior, configuration, interaction, and compliance is common practice in architectures. These are largely static views showing a specific configuration or behavior. IEEE Std 610.12-1990 defines architecture as "the fundamental organization of a system embodied in its components, their relationships to each other, and to the environment, and the principles guiding its design and evolution." (IEEE, 1990) Modeling this evolution or the temporal aspects in architecture frameworks such as the Department of Defense Architecture Framework (DoDAF) was previously problematic. With the release of DoDAF version 2.0, architectures can now take the fourth dimension (Time) into account. The challenge is to identify areas of architecture where time can be modeled and how to take best advantage of it. Also problematic is how to express these concepts without having to expose all the internal ontological relationships upon which DoDAF is built. The Unified Profile for DoDAF and MODAF (UPDM) delivers an implementation of DoDAF 2.0 that provides a clear and concise way of expressing these concepts without requiring the user to become an expert in the DoDAF 2.0 "internal wiring" and detailed ontological concepts. This paper will examine the temporal concepts defined in DoDAF 2.0 and show how time can be effectively integrated into a model to express essential temporal concepts.

Loading Atego collaborators
Loading Atego collaborators