China 
Africa 
Explore chapters and articles related to this topic
Technical Writing Basics
Published in Phillip A. Laplante, Technical Writing, 2018
IEEE 830–1993 was a standard for specification documentation for “Requirements Engineering for Systems and Software” [IEEE 1993]. A System Requirements Specification is a prototypical kind of technical writing that is used in many industries to provide a high-level description of the functions and features of a proposed system. A requirements engineer is responsible for the activities needed to elicit requirements and then to translate those requirements into a written System Requirements Specification. Even though the IEEE Standard 830 was retired in 2011, it is still useful to us as a guide for technical writing. IEEE 830 proposed eight desirable qualities for SRS documents. These were:
Data and model-based triple V product development framework and methodology
Published in Enterprise Information Systems, 2022
Qing Li, Hailong Wei, Chao Yu, Shuangshuang Wang
The workflow in the functional analysis stage is described as shown in Figure 10. The purpose of this stage is transforming functional requirements to a consistent set of system operation. The analysis is carried out by translating all the system use cases identified in the previous stage to executable models, which can be verified by model execution, such as conceptual simulation. Starting from defining use case model context by an Internal Block Diagram from SysML, the next major step is defining the behaviour of the use case. It consists of three parts, defining use case functional flow by Activity Diagram, deriving use case scenarios by Sequence Diagram, defining ports and interfaces by Internal Block Diagram. Then the most important step is to generate a behaviour-based State Diagram for the use case from its black-box activity diagrams and sequence diagrams. The State Diagram can be executed to verify use case model. Not only normal cases analysis but also exceptional cases analysis is conducted to extend use case models or derive new requirements. It should be noted, whenever new requirements are identified during the workflow of functional analysis stage, they need to be documented. At the end, the System Requirements Specification Draft constructed in requirements analysis stage should be updated if there are new requirements or derived requirements being identified.