Orchestrating Systems Engineering Processes and System Architectures within DoD: A Discussion of the Potentials of DoDAF

!e Department of Defense (DoD) is responsible for the development, procurement, introduction, integration, maintenance, upgrading, and retirement of all defense and related support systems. To facilitate this task, enterprise-level system architectures are used to describe capability, operational capability requirements and lower level system architectures are used to describe the functionality of system solutions which are necessary to satisfy those operational capability requirements. To ensure the attainment of the required capability solution on time and under budget, systemengineering processes are mandated to ensure consistency and rigor across all participating organizations. However, even though architecting is necessary to insure that all understand user requirements in the same way (providing logical rigor, structure, semantic and syntax), the practice of architecture is sometimes set aside as being unimportant, and programs sometimes fail for lack of good requirements. Defense engineering leadership understands this problem, and the DoD now has the challenge to determine how best to harmonize enterprise/systems architecting practices with systems engineering practices

Requirements engineering for computer integrated environments in construction

A Computer Integrated Environment (CIE) is the type of innovative integrated information system that helps to reduce fragmentation and enables the stakeholders to collaborate together in business. Researchers have observed that the concept of CIE has been the subject of research for many years but the uptake of this technology has been very limited because of the development of the technology and its effective implementation. Although CIE is very much valued by both industrialists and academics, the answers to the question of how to develop and how to implement it are still not clear. The industrialists and researchers conveyed that networking, collaboration, information sharing and communication will become popular and critical issues in the future, which can be managed through CIE systems. In order for successful development of the technology, successful delivery, and effective implementation of user and industry-oriented CIE systems, requirements engineering seems a key parameter. Therefore, through experiences and lessons learnt in various case studies of CIE systems developments, this book explains the development of a requirements engineering framework specific to the CIE system. The requirements engineering process that has been developed in the research is targeted at computer integrated environments with a particular interest in the construction industry as the implementation field. The key features of the requirements engineering framework are the following: (1) ready-to-use, (2) simple, (3) domain specific, (4) adaptable and (5) systematic, (6) integrated with the legacy systems. The method has three key constructs: i) techniques for requirements development, which includes the requirement elicitation, requirements analysis/modelling and requirements validation, ii) requirements documentation and iii) facilitating the requirements management. It focuses on system development methodologies for the human driven ICT solutions that provide communication, collaboration, information sharing and exchange through computer integrated environments for professionals situated in discrete locations but working in a multidisciplinary and interdisciplinary environment. The overview for each chapter of the book is as follows; Chapter 1 provides an overview by setting the scene and presents the issues involved in requirements engineering and CIE (Computer Integrated Environments). Furthermore, it makes an introduction to the necessity for requirements engineering for CIE system development, experiences and lessons learnt cumulatively from CIE systems developments that the authors have been involved in, and the process of the development of an ideal requirements engineering framework for CIE systems development, based on the experiences and lessons learnt from the multi-case studies. Chapter 2 aims at building up contextual knowledge to acquire a deeper understanding of the topic area. This includes a detailed definition of the requirements engineering discipline and the importance and principles of requirements engineering and its process. In addition, state of the art techniques and approaches, including contextual design approach, the use case modelling, and the agile requirements engineering processes, are explained to provide contextual knowledge and understanding about requirements engineering to the readers. After building contextual knowledge and understanding about requirements engineering in chapter 2, chapter 3 attempts to identify a scope and contextual knowledge and understanding about computer integrated environments and Building Information Modelling (BIM). In doing so, previous experiences of the authors about systems developments for computer integrated environments are explained in detail as the CIE/BIM case studies. In the light of contextual knowledge gained about requirements engineering in chapter 2, in order to realize the critical necessity of requirements engineering to combine technology, process and people issues in the right balance, chapter 4 will critically evaluate the requirements engineering activities of CIE systems developments that are explained in chapter 3. Furthermore, to support the necessity of requirements engineering for human centred CIE systems development, the findings from semi-structured interviews are shown in a concept map that is also explained in this chapter. In chapter 5, requirements engineering is investigated from different angles to pick up the key issues from discrete research studies and practice such as traceability through process and product modelling, goal-oriented requirements engineering, the essential and incidental complexities in requirements models, the measurability of quality requirements, the fundamentals of requirements engineering, identifying and involving the stakeholders, reconciling software requirements and system architectures and barriers to the industrial uptake of requirements engineering. In addition, a comprehensive research study measuring the success of requirements engineering processes through a set of evaluation criteria is introduced. Finally, the key issues and the criteria are comparatively analyzed and evaluated in order to match each other and confirm the validity of the criteria for the evaluation and assessment of the requirements engineering implementation in the CIE case study projects in chapter 7 and the key issues will be used in chapter 9 to support the CMM (Capability Maturity Model) for acceptance and wider implications of the requirements engineering framework to be proposed in chapter 8. Chapter 6 explains and particularly focuses on how the requirements engineering activities in the case study projects were handled by highlighting strengths and weaknesses. This will also include the experiences and lessons learnt from these system development practices. The findings from these developments will also be utilized to support the justification of the necessity of a requirements engineering framework for the CIE systems developments. In particular, the following are addressed. • common and shared understanding in requirements engineering efforts, • continuous improvement, • outputs of requirement engineering • reflections and the critical analysis of the requirements engineering approaches in these practices. The premise of chapter 7 is to evaluate and assess the requirements engineering approaches in the CIE case study developments from multiple viewpoints in order to find out the strengths and the weaknesses in these requirements engineering processes. This evaluation will be mainly based on the set of criteria developed by the researchers and developers in the requirements engineering community in order to measure the success rate of the requirements engineering techniques after their implementation in the various system development projects. This set of criteria has already been introduced in chapter 5. This critical assessment includes conducting a questionnaire based survey and descriptive statistical analysis. In chapter 8, the requirements engineering techniques tested in the CIE case study developments are composed and compiled into a requirements engineering process in the light of the strengths and the weaknesses identified in the previous chapter through benchmarking with a Capability Maturity Model (CMM) to ensure that it has the required level of maturity for implementation in the CIE systems developments. As a result of this chapter, a framework for a generic requirements engineering process for CIE systems development will be proposed. In chapter 9, the authors will discuss the acceptance and the wider implications of the proposed framework of requirements engineering process using the CMM from chapter 8 and the key issues from chapter 5. Chapter 10 is the concluding chapter and it summarizes the findings and brings the book to a close with recommendations for the implementation of the Proposed RE framework and also prescribes a guideline as a way forward for better implementation of requirements engineering for successful developments of the CIE systems in the future

Evaluating End User Development as a Requirements Engineering Technique for Communicating Across Social Worlds During Systems Development

Requirements engineering is a key activity in systems development. This paper examines six systems development projects that have used end user development (EUD) as a requirements engineering technique for communicating across social worlds. For this purpose, we employed the theoretical lens of design boundary object in order to focus on functional and political ecologies during the development process. Four features were investigated: (1) the capability for common representation, (2) the capability to transform design knowledge, (3) the capability to mobilise for design action, and (4) the capability to legitimise design knowledge across social worlds. We concluded that EUD means a high degree of end user involvement and takes advantage of end users’ know-how. It has the ability to capture requirements and transfer them into the final information system without the need to make an explicit design rationale available to the systems developers. However, systems developers have little or no influence on business requirements. Their role is mainly as technical experts rather than business developers. The systems developers took control and power of technical requirements, while requirements that relate to business logic remained with the end users. Consequently, the systems developers did not act as catalysts in the systems development process

IAC user manual

The User Manual for the Integrated Analysis Capability (IAC) Level 1 system is presented. The IAC system currently supports the thermal, structures, controls and system dynamics technologies, and its development is influenced by the requirements for design/analysis of large space systems. The system has many features which make it applicable to general problems in engineering, and to management of data and software. Information includes basic IAC operation, executive commands, modules, solution paths, data organization and storage, IAC utilities, and module implementation

The influence of the concept of capability-based management on the development of the systems engineering discipline

This paper explores the implications of a capability-based conceptual approach on the development of the systems engineering (SE) discipline. It deals with the identification of some potential limits and gaps of traditional SE approaches and demonstrates the need for new and innovative developments which support the concept of capability based engineering, especially as applied in the military domain and networking environments. The innovative approaches include partnership for capability planning and service descriptions for capability representations. The paper also presents a very brief assessment of the state-of-the-art of cognate domains such as capability based planning alongside requirements engineering and management, and considers the extent to which they address capability based concepts. The related concepts of system of systems (SoS) and the endeavour to extend SE to SoS are necessarily addressed

A design and implementation methodology for diagnostic systems

A methodology for design and implementation of diagnostic systems is presented. Also discussed are the advantages of embedding a diagnostic system in a host system environment. The methodology utilizes an architecture for diagnostic system development that is hierarchical and makes use of object-oriented representation techniques. Additionally, qualitative models are used to describe the host system components and their behavior. The methodology architecture includes a diagnostic engine that utilizes a combination of heuristic knowledge to control the sequence of diagnostic reasoning. The methodology provides an integrated approach to development of diagnostic system requirements that is more rigorous than standard systems engineering techniques. The advantages of using this methodology during various life cycle phases of the host systems (e.g., National Aerospace Plane (NASP)) include: the capability to analyze diagnostic instrumentation requirements during the host system design phase, a ready software architecture for implementation of diagnostics in the host system, and the opportunity to analyze instrumentation for failure coverage in safety critical host system operations

Conversion from Tree to Graph Representation of Requirements

A procedure and software to implement the procedure have been devised to enable conversion from a tree representation to a graph representation of the requirements governing the development and design of an engineering system. The need for this procedure and software and for other requirements-management tools arises as follows: In systems-engineering circles, it is well known that requirements- management capability improves the likelihood of success in the team-based development of complex systems involving multiple technological disciplines. It is especially desirable to be able to visualize (in order to identify and manage) requirements early in the system- design process, when errors can be corrected most easily and inexpensively

ECLSS and Thermal Systems Integration Challenges Across the Constellation Architecture

As the Constellation Program completes its initial capability Preliminary Design Review milestone for the Initial Capability phase, systems engineering of the Environmental Control and Life Support (ECLS) and Thermal Systems for the various architecture elements has progressed from the requirements to design phase. As designs have matured for the Ares, Orion, Ground Systems, and Extravehicular (EVA) System, a number of integration challenges have arisen requiring analyses and trades, resulting in changes to the design and/or requirements. This paper will address some of the key integration issues and results, including the Orion-to-Ares shared compartment venting and purging, Orion-to-EVA suit loop integration issues with the suit system, Orion-to-ISS and Orion-to-Altair intermodule ventilation, and Orion and Ground Systems impacts from post-landing environments