Strategies for real-time system specification
Strategies for real-time system specification
Rapid application development
The capability maturity model: guidelines for improving the software process
The capability maturity model: guidelines for improving the software process
An Empirical Study of Software Reuse with Special Attention to Ada
IEEE Transactions on Software Engineering
Objects, components, and frameworks with UML: the catalysis approach
Objects, components, and frameworks with UML: the catalysis approach
A systematic approach to derive the scope of software product lines
Proceedings of the 21st international conference on Software engineering
Mastering the requirements process
Mastering the requirements process
Real-time UML (2nd ed.): developing efficient objects for embedded systems
Real-time UML (2nd ed.): developing efficient objects for embedded systems
Automated prototyping tool-kit (APT)
Information Sciences—Informatics and Computer Science: An International Journal - Special issue: Software engineering: Systems and tools
Synthesis of Behavioral Models from Scenarios
IEEE Transactions on Software Engineering
Software Requirements
Object-Oriented Software Engineering: A Use Case Driven Approach
Object-Oriented Software Engineering: A Use Case Driven Approach
IEEE Transactions on Software Engineering
Structured Analysis and System Specification
Structured Analysis and System Specification
A Scenario-Matching Approach to the Description and Model Checking of Real-Time Properties
IEEE Transactions on Software Engineering
Comprehension and quality of analysis specifications-a comparison of FOOM and OPM methodologies
Information and Software Technology
| Hi-index | 0.07 |
This paper proposes an efficient method to develop requirement specifications for Plant Control Software (PCSW) using software-component-based prototypes. Prior to this proposal, domain analyses were conducted on existing PCSWs, and their functions were classified into ''similar functions'' and ''individual functions''. Then PCSW Software Components (PSC: PCSW Software Component, PSCs: PCSW Software Components) were developed to correspond to these functions. PSCs as parameter-style components were developed in order to satisfy the clients' (we define clients as owners, managers and operators of plants) requirements. A support environment for developing requirement specifications was developed. The environment consists of the Prototype Development Tool (PDT), the Behavior Check Simulator (BCS) and the Requirement Specification Development Tool (RSDT). The method consists of four steps. In the first step, PDT is used to define the parameters to customize PSCs and to compose a PCSW prototype by setting these parameters to PSCs. In the second step, BCS is used to execute the composed PCSW prototype and check its behavior and relevancy against the clients' expectations. In the third step, steps 1 and 2 are repeated until the behavior of the PCSW prototype satisfies the clients' requirements. Finally, a requirement specification is developed from the PCSW prototype which fully reflects the clients' requirements. In order to evaluate the proposed method, it has been applied in five development cases. A Requirement Coverage of 91%, a Requirement Revision Rate of 6%, a PSC Reuse Rate of 92% and a LOC Reuse Rate of 83% have been achieved. In addition, a reduction of 55% in the amount of time required to develop requirement specifications has been achieved. These results indicate that the proposed method has sufficient capability to develop an exhaustive and an adequate PCSW requirement specification. And the developed PSCs have sufficient functions and capability to compose PCSW prototypes, and the support environment is capable of shortening the time taken to develop requirement specifications.