A standard-based reference framework for system operations requirements

Abstract

European series of standards for the aerospace industry, includes system operations requirements as one of 16 types of NFRs for embedded and real-time systems. A number of concepts are provided in the ECSS and Institute of Electrical and Electronics Engineers (IEEE) standards to describe the various types of candidate operations requirements at the system, software and hardware levels. In the absence of such a generic and detailed model, these NFRs are typically handled much later on in the software development life cycle, when, at system testing time, users and developers may discover that a number of system operations requirements have been overlooked and additional work is required to implement them. This paper organises these dispersed operations concepts into a standards-based reference framework of system operations requirements.

A sustainable procedural method of software design process improvements

“…The current design phase involves a Indonesian J Elec Eng & Comp Sci ISSN: 2502-4752  broad set of activities and tasks based on the identified requirements and prepared these designed requirements into design components for the products construction phase on the next step of implementations. However, the current design phase built a design model of the product or system design structure; for instance, such designed model is used to evaluate the suitability of the proposed product and communicate the recommended product to others [35][36][37]. There are many proposed models for conventional design processes in academia and the industry; the most commonly used models are presented below: a) Generic design process: Recently, [38] defined six steps for a generic design process that are more general and can apply to any software project.…”