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...

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...

Requirements for Bibliographic Records F unctional Requirements for Bibliographic Records (FRBR) [1], a report developed by the IFLA Study Group on the functional requirements for bibliographic records, has been discussed and explored for nearly a decade. FRBR offers a new perspective on how to create and relate records about information packages for more effective support of user information t...

A model of requirements determination as the process of establishing visions in context explains how both new ideas and existing habits influence diversity in a family of information systems applications. Visions are operationalized as non-functional requirements which are broken down according to constraints imposed by context, and traded off against other non-functional requirements. Context ...

Today’s companies are increasingly being challenged to develop platform-based product families to increase variety of products, while keeping production costs low. In order to provide effective platform-based method and systematically analyzing the customer needs on product design, the functional requirements are classified into basic functional requirements, expectable functional requirements ...

Non-Functional Requirements (NFR) are subjective, interactive and relative, thus realizing the need for particular NFR is by itself a challenge. Furthermore understanding what the software must implement in order to cope with these needs may prove to be an even more challenging task. One way of addressing the need for help on NFR elicitation is the use of catalogues. However, it is not clear ho...

In the 52-page document, we describe our approach to the Software Requirements Specification of the IUfA's UUIS prototype. This includes the overall system description, functional requirements, non-functional requirements, use cases, the corresponding data dictionary for all entities involved, mock user interface (UI) design, and the overall projected cost estimate. The design specification of ...