An example of requirements for Advanced Subsonic Civil Transport (ASCT) flight control system using structured techniques

The requirements are presented for an Advanced Subsonic Civil Transport (ASCT) flight control system generated using structured techniques. The requirements definition starts from initially performing a mission analysis to identify the high level control system requirements and functions necessary to satisfy the mission flight. The result of the study is an example set of control system requirements partially represented using a derivative of Yourdon's structured techniques. Also provided is a research focus for studying structured design methodologies and in particular design-for-validation philosophies

A goal-oriented requirements modelling language for enterprise architecture

Methods for enterprise architecture, such as TOGAF, acknowledge the importance of requirements engineering in the development of enterprise architectures. Modelling support is needed to specify, document, communicate and reason about goals and requirements. Current modelling techniques for enterprise architecture focus on the products, services, processes and applications of an enterprise. In addition, techniques may be provided to describe structured requirements lists and use cases. Little support is available however for modelling the underlying motivation of enterprise architectures in terms of stakeholder concerns and the high-level goals that address these concerns. This paper describes a language that supports the modelling of this motivation. The definition of the language is based on existing work on high-level goal and requirements modelling and is aligned with an existing standard for enterprise modelling: the ArchiMate language. Furthermore, the paper illustrates how enterprise architecture can benefit from analysis techniques in the requirements domain

System architectures for telerobotic research

Several activities are performed related to the definition and creation of telerobotic systems. The effort and investment required to create architectures for these complex systems can be enormous; however, the magnitude of process can be reduced if structured design techniques are applied. A number of informal methodologies supporting certain aspects of the design process are available. More recently, prototypes of integrated tools supporting all phases of system design from requirements analysis to code generation and hardware layout have begun to appear. Activities related to system architecture of telerobots are described, including current activities which are designed to provide a methodology for the comparison and quantitative analysis of alternative system architectures

L’analyse des phénomènes physiques, éléments essentiels vers la résolution de problèmes industriels

In this paper, we present the different elements of connection between users requirements and physical phenomena created during the use of products. We propose a structured methodology which goes from the analysis of the significant moments until the identification of the appreciation criteria of the user and design variables necessary to the product definition. The time decomposition of the product use in significant moments makes it possible to identify all actions realized by the user, to extract the physical effects and to qualify them in term of relevance. The methodological tools ensure the exhaustiveness of the analysis, to define the physical sizes associated with the criteria and the design variables as well as the relations between the criteria and design variables. Then we can take into account users requirements during preliminary design phase. This methodology is applied to the integration of the user requirements at the time of the opening for a telephone foldable

A Definition and Investigation of Cooperative Acquisition Programs Using Multiple Case Studies

This thesis is an exploratory study of the management of cooperative acquisition programs. The investigation focuses on defining the nature of a cooperative acquisition strategy, identifying potential problems associated with this approach, and evaluating the effectiveness of the current guidance and support structure for such programs. The desired outcome of this strategy is a common solution. The operational definition of cooperative acquisition builds on the Department of Defense definition of Joint Service Acquisition. A pilot study and literature review are used to develop a structured interview for three case studies. Analysis of these cases indicates that difficulty in resolving core requirements, and funding instability are the two major sources of problems on cooperative acquisition programs. Also, the guidance and support for cooperative acquisition programs has been slow to develop

A model of electronic warfare systems acquisition and engineering for Saudi Arabia

A major activity within the systems engineering process is the requirements definition and analysis phase. In technical systems, planning this phase looks too technical for top management and too broad for the engineers specialized in narrow technical fields. This categorization (too technical/too broad) represents a gap between top management and specialized engineering. In Saudi Arabia, such a gap is believed to be very wide. The main objective of this research is to find a way to narrow this gap between management and engineering when planning government systems, especially in electronic warfare (EW) systems. A solution in this effort is to streamline the process of systems acquisition, with more focus on the requirements definition phase before signing the contract. An acquisition procedural model has been developed. This model is structured in five sequenced phases linked through decision points. The first phase focuses on a method to develop threat analysis reports and why such a deterrent capability is needed. Requirements engineering is the main activity within the second phase. In this phase, the concept of structuring systems and subsystems into objects is explored by applying object-oriented expert systems to probe requirements completeness, correctness, consistency, traceability, timeliness, and documentation. Skeletons of three object-oriented knowledge bases for a Planning Support for Communication System (PSCS) were developed using EW sub-fields as the domain objects. The other three model phases are invitation for presentation, request-for-proposal (RFP) package development, and source selection. Government and corporate engineers in Saudi Arabia have reviewed the model, and it has a strong potential of becoming a Saudi national standard. Data analysis attributes the model\u27s strength to its applicability in 1) structuring the task of systems acquisition and keeping a documentation profile; 2) increasing government agencies\u27 self-reliance when planning systems; and 3) facilitating the generation of sound requirements --Abstract, page iii

JAD-CASE : Tasks and documents specification for requirements engineering process

The structured techniques for systems analysis and design are still the most widely known. One of the alternatives of this technique is the JAD methodology (Joint Application Design). This methodology is an improvement with respect to the existing ones - such as classical life cycle, spiral development, increasing prototypes - since it expands the role of the users, and allows them to define their own objectives, requirements and external design. Problem definition, as well as requirements initial analysis, are the basis for the whole software engineering process; the success of the developed system depending mostly on these two initial stages. This is the reason why the use of a methodology emphasizing these initial stages is important, since it would provide a higher quality design, easy to maintain and modify. The proposed objective was the construction of a CASE tool which would include the JAD methodology within an environment where participants (users and analysts) can interact to manage the flow of tasks and documents generated in the Requirements Engineering stage.Eje: Ingeniería de software. Bases de datosRed de Universidades con Carreras en Informática (RedUNCI

Development of an Interface Analysis Template for System Design Analysis

yesInterface definition is an essential and integral part of systems engineering. In current practice, interface requirements or control documents are generally used to define systems or subsystems interfaces. One of the challenges with the use of such documents in product development process is the diversity in their types, methodology, contents coverage, and structure across various design levels and across multidisciplinary teams, which often impedes the design process. It is important that interface information is described with appropriate detail and minimal or no ambiguity at each design level. The purpose of this paper is to present an interface analysis template (IAT) as a structured tool and coherent methodology, built upon a critical review of existing literature concepts, with the aim of using and implementing the same template for capturing interface requirements at various levels of design starting from stakeholders' level down to component level analysis. The proposed IAT is illustrated through a desktop case study of an electric pencil sharpener, and two examples of application to automotive systems

Developing a current capability design for a manufacture framework in the aerospace industry

During progressive product design and development in the aerospace industry, a lack of effective communication between the sequential functions of design, manufacturing and assembly causes delays and setbacks whereby production capabilities are unable to realise design intent in high-complexity product models. There is a need to formalise the progressive design and release of an engineering model to production functions during New Product Introduction (NPI) via defining key stages of definition maturity and information requirements through a structured process. This research develops a framework to facilitate optimal Design for Manufacture and Assembly (DfMA) based on current manufacturing capabilities within the aerospace industry, promoting effective knowledge management at all stages of design definition. The framework was developed through the accomplishment of a series of objectives: (1) Investigate optimal DfMA principles and process capability analysis through a comprehensive literature review, (2) capture the current practice of progressive drawing release in the aerospace and automotive sectors, (3) create a route map of the release process built around the optimal critical path, (4) define roles and procedures to follow at each stage and (5) validate the proposed process framework through expert opinion. These objectives were achieved through the adoption of a four-stage qualitative methodology. The framework promotes the understanding and identification of the major stages, activities, responsibilities and information requirements throughout a structured design release process where quantified manufacturing capability data is incorporated within early design definition activities. Adherence to the process route-map ensures that no engineering model is released that cannot be realised by manufacturing and assembly functions. This facilitates the efficient organisation of information on an optimal concurrent engineering platform, leading to a reduction in product development leadtimes and re-work through informed design.SAS Prize winne

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