Luiz Marcio Cysneiros

Learn More
Nonfunctional requirements (NFRs) have been frequently neglected or forgotten in software design. They have been presented as a second or even third class type of requirement, frequently hidden inside notes. We tackle this problem by treating NFRs as first class requirements. We present a process to elicit NFRs, analyze their interdependencies, and trace(More)
1. INTRODUCTION Software developers are constantly under pressure to deliver code on time and on budget. As a result, many projects focus on delivering functionalities at the expense of meeting non-functional requirements such as reliability, security, maintainability, portability, accuracy, among others. As software complexity grows and clients demand(More)
The development of complex information systems calls for conceptual models that describe aspects beyond entities and activities. In particular, recent research has pointed out that conceptual models need to model goals, in order to capture the intentions which underlie complex situations within an organisational context. This paper focuses on one class of(More)
Usability is becoming increasingly recognized as being an important factor in the acceptance of systems by end users. Usability requirements can be considered to be requirements that capture the usability goals and associated measures for a system under development. In order to ensure usable systems we must ensure identification of appropriate requirements(More)
There are many different approaches to elicit requirements each having its strengths and weaknesses. Hence, some approaches may be ore suitable to one domain then another. Moreover, some domains may require these approaches to be carefully applied or even adapted to work efficiently. Health care domain is one of these domains. It is a complex domain with(More)
The way requirements should drive the rest of the software development process has been a subject of many research projects in the past. Unfortunately, all of them focus primarily, when not exclusively, on the functional requirements regardless of the fact that non-functional requirements (NFR) are among the most expensive and difficult to deal with [6](More)
Recently, it has been pointed out that the majority of the requirements engineering methods do not take into account non-functional requirements (NFRs) [10][11]. Consequently, we have been experiencing serious problems during the development of software systems, such as cost and schedule overruns. In order to diminish this negligence of NFRs and its(More)
Non-Functional Requirements (NFRs) have been frequently neglected or forgotten in software design. In order to treat them as first class citizens it is necessary not only to provide methods and representations, but also to deal with their organization, as to promote future reuse. In this article we offer a preliminary insight on how this knowledge could be(More)
Today, companies are continuously changing and improving their business strategies. As a consequence, stakeholders are demanding more flexible and complex software to be built . To handle this complexity, conceptual models have to describe aspects beyond entities and activities. Recent research has pointed out that dealing with goals in order to capture(More)