REFSQ 2015 encouraged researchers and practitioners from the research fields covered by the conference to submit posters. The poster track at REFSQ15 is intended to provide a forum for presenting recent work and obtaining early feedback on ongoing research. All submissions were reviewed by at least three members of the program committee. In the end, five posters were accepted for display, addre...

The requirements elicitation phase is often regarded as the most critical stage of the entire software engineering effort with strong evidence suggesting that increasing the effectiveness of requirements analysts and reducing requirements elicitation errors may be the key to improve project outcomes and deliver high quality software. This paper presents a requirements elicitation approach and a...

Top-quality software architecture should consider both functional and non-functional aspects of systems and their association. In the the existing literature, considerable efforts have been directed at functional requirement analysis and design, regardless of the non-functional aspects. This disassociation makes architecture comprehension and evolution hard. This paper proposes a strategy on ho...

The aim of the paper is to determine the best method to capture the functional and non-functional requirements of software and to ensure that the acquired software is deemed suitable by the users. The paper compares the organisational learning approach to the traditional method of software requirements elicitation and adoption. We analysed the two approaches in a case study of a Bahamian horizo...

The existence of variations in the organizational environment makes the configuration of business process models a complex activity, even for experienced business analysts. The increasing adoption of business processes models by software engineers as a input for requirements analysis strengthens the importance of adressing this issue. The challenge is to configure business processes to fit the ...

When specifying user requirements, not only it is critical to ensure correct and unambiguous specification of functional requirements, but also that of non-functional requirements (NFRs). In fact, resolving ambiguities from user specified natural language NFRs and specifying the correct ones in a formal language have attracted significant attention. Our current research focuses on the issues pe...

[Context and motivation] Stakeholder requirements are notoriously informal, vague, ambiguous and often unattainable. The requirements engineering problem is to formalize these requirements and then transform them through a systematic process into a formal specification that can be handed over to designers for downstream development. [Question/problem] This paper proposes a framework for transfo...

Semantic web service compositions must be aligned with requirements from the target users in terms of quality requirements. Given a set of quality requirements, one can choose to either find the optimal composition or a “good enough” composition, which satisfies these requirements. Since optimizing compositions of semantic services under quality constraints is known to be NP-hard, it is unsuita...

There are several methods for the derivation and analysis of detailed non-functional requirements. They often are designed for a special application, like misuse cases for top-down derivation of requirements detailing the quality attribute “security”, or ATAM for evaluating given architectural alternatives. In this work, we apply misuse cases to any other quality attribute (e.g. usability, effi...

Maintainability is typically described initially as a non functional requirement at the system level. Systems engineers must subsequently apportion these system requirements very carefully as either software or hardware requirements to conform to the maintainability requirements of the system. A number of concepts are provided in the ECSS, ISO 9126, and IEEE standards to describe the various ty...