The Experts below are selected from a list of 49953 Experts worldwide ranked by ideXlab platform
Peggy Brouse - One of the best experts on this subject based on the ideXlab platform.
-
11.4.2 Measuring the Requirements Allocation Capacity within a System of Systems
INCOSE International Symposium, 2012Co-Authors: David Flanigan, Peggy BrouseAbstract:During the initial development of a System of Systems (SoS) capability, the developers and stakeholders may not be aware of all the options that are available to identify and allocate Requirements at the system level. Traditional Systems Engineering techniques do not have the ability to construct and evaluate if these SoS Requirements will be satisfied or not. This paper identifies a process in which to develop SoS Requirements, trace them to their constituent systems, and evaluate whether the Allocation was successful or not.
-
system of systems Requirements capacity Allocation
Procedia Computer Science, 2012Co-Authors: David Flanigan, Peggy BrouseAbstract:Abstract Traditional systems engineering Requirements Allocation follow a serial process to assign individual systems to execute objectives. When a System of Systems (SoS) is being developed, serial Allocation of system Requirements may be less suitable, and ensuring Requirements loading is properly balanced between systems and that SoS Requirements are covered (and not overly covered) by available systems may be less clear. This paper explores a methodology to quantitatively measure the Requirements loading of each system to achieve SoS objectives. The approach seeks to maximize the coverage of functional Requirements with a minimal number of systems, but also seeks to explore the balance of system responsibilities within the entire SoS to prevent over tasking of a particular piece of the SoS, and thus prevent the SoS objectives from being achieved. The paper seeks to identify a methodology of SoS Requirements Allocation to explore the contributions and redundancies of how the SoS Requirements are assigned to individual systems. SoS Requirements may also impose additional interoperability Requirements in order to execute the objectives, but may be traded off with a lower and less demanding number of system Requirements.
David Flanigan - One of the best experts on this subject based on the ideXlab platform.
-
11.4.2 Measuring the Requirements Allocation Capacity within a System of Systems
INCOSE International Symposium, 2012Co-Authors: David Flanigan, Peggy BrouseAbstract:During the initial development of a System of Systems (SoS) capability, the developers and stakeholders may not be aware of all the options that are available to identify and allocate Requirements at the system level. Traditional Systems Engineering techniques do not have the ability to construct and evaluate if these SoS Requirements will be satisfied or not. This paper identifies a process in which to develop SoS Requirements, trace them to their constituent systems, and evaluate whether the Allocation was successful or not.
-
system of systems Requirements capacity Allocation
Procedia Computer Science, 2012Co-Authors: David Flanigan, Peggy BrouseAbstract:Abstract Traditional systems engineering Requirements Allocation follow a serial process to assign individual systems to execute objectives. When a System of Systems (SoS) is being developed, serial Allocation of system Requirements may be less suitable, and ensuring Requirements loading is properly balanced between systems and that SoS Requirements are covered (and not overly covered) by available systems may be less clear. This paper explores a methodology to quantitatively measure the Requirements loading of each system to achieve SoS objectives. The approach seeks to maximize the coverage of functional Requirements with a minimal number of systems, but also seeks to explore the balance of system responsibilities within the entire SoS to prevent over tasking of a particular piece of the SoS, and thus prevent the SoS objectives from being achieved. The paper seeks to identify a methodology of SoS Requirements Allocation to explore the contributions and redundancies of how the SoS Requirements are assigned to individual systems. SoS Requirements may also impose additional interoperability Requirements in order to execute the objectives, but may be traded off with a lower and less demanding number of system Requirements.
Marcus Wilkerson - One of the best experts on this subject based on the ideXlab platform.
-
MBSE-driven visualization of Requirements Allocation and traceability
2016 IEEE Aerospace Conference, 2016Co-Authors: Maddalena Jackson, Marcus WilkersonAbstract:In a Model Based Systems Engineering (MBSE) infusion effort, there is a usually a concerted effort to define the information architecture, ontologies, and patterns that drive the construction and architecture of MBSE models, but less attention is given to the logical follow-on of that effort: how to practically leverage the resulting semantic richness of a well-formed populated model to enable systems engineers to work more effectively, as MBSE promises. While ontologies and patterns are absolutely necessary, an MBSE effort must also design and provide practical demonstration of value (through human-understandable representations of model data that address stakeholder concerns) or it will not succeed. This paper will discuss opportunities that exist for visualization in making the richness of a well-formed model accessible to stakeholders, specifically stakeholders who rely on the model for their day-to-day work. This paper will discuss the value added by MBSE-driven visualizations in the context of a small case study of interactive visualizations created and used on NASA's proposed Europa Mission. The case study visualizations were created for the purpose of understanding and exploring targeted aspects of Requirements flow, Allocation, and comparing the structure of that flow-down to a conceptual project decomposition. The work presented in this paper is an example of a product that leverages the richness and formalisms of our knowledge representation while also responding to the quality attributes SEs care about.
Richard Berntsson Svensson - One of the best experts on this subject based on the ideXlab platform.
-
addressing model complexity in automotive system development selection of system model elements for Allocation of Requirements
International Conference on Model-Driven Engineering and Software Development, 2016Co-Authors: Grischa Liebel, Andreea Olaru, Henrik Lönn, Henrik Kaijser, Sunith Rajendran, Urban Ingelsson, Richard Berntsson SvenssonAbstract:Modern automotive embedded systems are developed by Original Equipment Manufacturers (OEM) together with multiple suppliers. A key problem for a supplier is to allocate an OEM's Requirements specification to their own subsystem design. This is a difficult manual task especially on complex systems and it requires expert knowledge about the system design. To address this problem, this paper presents a design science research to develop and evaluate a Requirements Allocation Assistant tool (RAA). The tool provides functionality to search through and filter Requirements and system models to enable efficient Requirements Allocation even in the presence of complexity. RAA is built on top of the EATOP/Eclipse framework using EAST-ADL as system modelling language. The tool was evaluated and validated during a qualitative usability study with 17 engineers active in the Swedish automotive industry. Key findings are that searching is used to learn about a system, whereas filtering is used to narrow down a set of candidate elements of the system design. Engineers request further support in narrowing down a set of candidate elements and in checking that an Allocation is correct.
R. Holub - One of the best experts on this subject based on the ideXlab platform.
-
R&M Requirements Allocation in upgrading a system
Annual Reliability and Maintainability Symposium. 2001 Proceedings. International Symposium on Product Quality and Integrity (Cat. No.01CH37179), 2001Co-Authors: Z. Vintr, R. HolubAbstract:The article deals with a method of R&M Requirements Allocation which is applicable in upgrading technical systems. The method is based on the presumption that the basic R&M parameters of main sub-systems of original design are available and the requirement for the availability level of the upgraded system is stated. The main aim of the method is a Requirements Allocation which ensures an increase in system availability to a required level with minimal design changes. The basis of the method is a mathematical model describing dependencies between the overall system availability and availability of separate sub-systems. The model allows testing a system-availability response to changes of sub-systems availability. By using the model, a procedure was devised for specifying the sub-system (or sub-systems) which is the most suitable for upgrading. At the same time, the procedure allows Allocation of R&M Requirements for this optimal sub-system (or sub-systems) so that overall system-availability will meet the stated Requirements. The method was developed and used during the upgrading of a heavy tracked vehicle.