The paper focuses on development of requirements specification for steganographic systems. The main concepts and fields of use of steganography are briefly explained. Criteria that can be used for various non-functional requirements are grouped and their possible metrics are given with examples and sample requirements. The authors provide an original systematic approach to develop requirements ...

.... ..................................................................................................................... xiv CHAPTER

Requirements engineering (RE) is concerned with the elicitation of the goals to be achieved by the system envisioned, the operationalization of such goals into specifications of services and constraints, and the assignment of responsibilities for the resulting requirements to agents such as humans, devices, and software. Getting high-quality requirements is difficult and critical. Recent survey...

We present a novel method for capturing and writing requirements specifications that enriches disciplined use cases with screen mockups. Disciplined use cases are characterized by a quite stringent template, which allows to impose a large number of constraints helping to prevent common mistakes and to increase the quality of the specifications. Disciplined use cases are expressed using natural ...

Commercially available software components come with the built-in functionality often offering end-user more than they need. A fact that end-user has no or very little influence on component’s functionality promoted nonfunctional requirements which are getting more attention than ever before. In this paper, we identify some of the problems encountered when non-functional requirements for COTS s...

The proliferation of the Internet Things (IoT) devices and advances in their computing capabilities give an impetus to Edge Computing (EC) paradigm that can facilitate localize data storage. As a result, limitations like network connectivity issues, mobility constraints, real-time processing delays, Cloud be addressed more efficiently. EC create lot opportunities across breadth IT domains cyber...

Business stakeholders need to have clear and realistic goals if they want to meet commitments in application development. As a consequence, at early stages they prioritize requirements. However, requirements do change. The effect of change forces the stakeholders to balance alternatives and reprioritize requirements accordingly. In this paper we discuss the problem of priorities to non-function...

[Context and motivation] There is considerable flexibility in requirements specifications (both functional and non-functional), as well as in the features of available OSS components. This allows a collaborative matching and negotiation process between stakeholders such as: customers, software contractors and OSS communities, regarding desired requirements versus available and thus reusable OSS...

Service oriented architecture (SOA) is one of the latest software architectures. This architecture is created in direction of the business requirements and removed the gap between softwares and businesses. The software testing is the rising cost of activities in development software. SOA has different specifications and features proportion of the other software architectures. First this paper r...