Search Results

In this work we present a new procedure for customizing, in the desired format, requirements reports generated by a Requirements Engineering Environment. This environment includes tools for: 1- capturing textual and pictoric requirements; 2- templating requirements documents that can be adjustable to the formats required by the certification authorities or system engineering groups; 3- translating features from/to the main word processors used in the industry (Word, Excel, etc. formats); 4- managing requirements configuration. It provides gains of productivity, correctness, reusability, traceability, coverage, etc, improving the efficiency of the projects. The procedure emphasizes items 2 and 3, and is illustrated with some examples driven from the aerospace industry.

Nowadays, given the shrinking budgets and deadlines of the aerospace and automotive industries, the importance and need of the requirements engineering is becoming more and more evident. This means that progressively more users face a difficult task on the different environments of project development: 1) to write better requirements; and 2) to do it faster than ever. It would be nice if they had some tools to help them and abbreviate such a difficult task. This work summarizes the development of a new tool that does exactly that. Its wizard guides the user through the steps necessary to create good requirements when writting a requirements document, depending on the kind of requirements document desired. For example: there are significant differences between user requirements and system requirements documents. The wizard script is composed by a serie of questions related to the parts of the scheme to build a complete and effective requirement.

This paper presents the preliminary results of an "a posteriori" exercise of application of a Requirements Traceability Automation Tool (RT tool) to a set of documents. The documents have been prepared according to established Space System Engineering methodologies and with attention to text quality, but without attention to requirements traceability because the processes and methodologies used during their preparation predates the emergence of the processes and methodologies developed by Requirements Engineering (RE). This study is intended to determine some of the benefits of using a RT tool when compared with the previously used processes and methodologies. The set of documents under scrutiny have been prepared in the frame of the development of the CBERS-3 satellite (China-Brazil Earth Resources Satellite) and is composed of system, subsystem and equipment specification and covering documents related to the Electrical Power Subsystem (EPS) of the satellite.