원문정보
초록
영어
Currently, security requirements are defined at system levels in software engineering projects as system quality requirements. Later on system engineers must identify such system requirements into software requirements. It will be assigned to system software to conform to security at software and hardware requirements. For instance, a number of security requirements concepts and terms are described by IEEE, ISO and ECSS international standards and explained at different stages of requirements at the system, software and hardware levels. This paper assembles and systematizes these candidate security-related descriptions into a requirements model for the specification of software functional user requirements assigned from additional system security non-functional requirements. These models structure is made using the ISO-19761 international standard model of software requirements, which accept the new model to measure the functional size of software functionality and non-functionality of security systems.
목차
1. Introduction
2. Related Work
3. A Generic View of Software-FUR in ISO
4. Identification of Security Requirements Descriptions in the International Standards
4.1. Security Perspectives and Concepts as Described in IEEE
4.2. Security Perspectives and Concepts as Described in ISO
4.3. Security Perspectives and Concepts as Described in ECSS
5. Definition of Requirements Model using International Standards
5.1. IEEE, ISO and ECSS Perspectives and concepts for security are mapped
5.2. Types of Security Requirements
5.3. Software System Security Functions to be Specified
5.4. Identification of the System Security Function Types
5.5. Security Function Types: system and COSMIC modeling views
5.6. A Requirements Model of System Security
5.7. A Requirements Model of System Security using an SOA
6. Case Study: A Sizing of the Requirements Model of System Security
7. Discussion and Future work
References