This paper describes early experiences in using process definitions to facilitate requirements specification. The paper emphasizes addressing the constraints posed by the particularly challenging activity of obtaining requirements for digital government systems. The use of precise definitions of processes is suggested as a vehicle for bringing diverse stakeholders together to agree on system re...

The development of requirements specifications can be supported by a cycle composed of two phases: analysis and revision. In this paper, we use the SCTL-MUS methodology to bridge the gap between these two phases. Analysis phase provides diagnostic information if a desirable property is not satisfied by the current system specification. A crucial aspect of the analysis-revision cycle is how to u...

The Behavior Tree notation has been developed as a method for systematically and traceably capturing user requirements. In this paper we extend the notation with probabilistic behaviour, so that reliability, performance, and other dependability properties can be expressed. The semantics of probabilistic timed Behavior Trees is given by mapping them to probabilistic timed automata. We gain advan...

This paper introduces a model for expressing quality according to both applications and human users perspectives. Such a model, compliant with the WS-Policy framework, not only mediates between the application and human user perspectives, but is also capable of considering the different importance that the user can assign to a quality dimension. In addition, the paper introduces a policy select...

Improper specification of systems requirements has thwarted many splendid efforts to deliver high-quality information systems. Scholars have linked this problem to, between others, poor communication among systems developers and users at this stage of systems development. Some believe that specifying requirements is the most important and the most difficult activity in systems development. Howe...

Web service composition is an important topic. Typically, no single service can fulfil all user requirements for a system. Specifying and analysing the non-functional properties (NFPs) is essential to successful service composition. Only where NFPs have been specified, can we choose between services with similar or identical functionality, based on which would better satisfy our non-functional ...

The purpose of this article is to make a holistic compilation of many different types of requirements for an automotive electronic communications / control network (though the framework is in itself more generally applicable), and organize them into an easily reusable framework. Requirements have to be correct, consistent and complete. The issue of correctness of the specification should be dea...

Although the System Requirement Specification, as a first formal and detailed document, is the base for the software project in classic software methodologies, there is a noticeable problem of assuring the completeness of this document. The lack of its completeness causes uncertainty of the project foundations. This was one of motivations for agile methodologies – if the SRS cannot be easily va...