Luiz Marcio Cysneiros

York University · School of Information Technology

The ubiquitous presence of software in the products we use, together with Artificial Intelligence in these products, has led to an increasing need for consumer trust. Consumers often lose faith in products, and the lack of Trust propagates to the companies behind them. This is even more so in mission-critical systems such as autonomous vehicles and...

Nowadays, software is ubiquitous and present in almost everything we buy and use. Artificial intelligence (AI) is becoming prevalent in software products. The use of AI entices consumer inquisitiveness, promising software products that can make our lives easier, productive, and in some mission-critical applications safer. Similar reasoning can be a...

Requirements Engineering plays a crucial role in the software development process. Many works have pointed out that Non-Functional Requirements (NFRs) are critical to the quality of software systems. NFRs, also known as quality requirements, can be difficult to elicit due to their subjective diversity nature. In this paper, we introduce the QR Fram...

Heavy reliance on modern technologies causes the concepts of transparency and privacy to become more and more intertwined. Some recent privacy incidents illustrates that, such as: sharing of personal health information between United States and Canadian border services agencies; enabling voice recognition software by default in Samsung's smart TVs;...

Intentional Requirements Engineering (The ERi∗c-Engenharia de Requisitos Intencional) is a GORE method under evolution. After the first publication of ERi∗c, in March/2008, the method has received several changes in order to mitigate the complexity of tasks and artifacts. ERi∗c follows the i-star Framework and NFR Framework ideas and consequently d...

Non-Functional Requirements (NFR) can be seen as qualities that software should deliver to cope with the stakeholders' demands. NFRs are fuzzy in nature and hence hard to identify. Despite the fact that both developers and users may value NFRs, they frequently do not identify the need for an NFR. Even when an NFR is identified as required, possible...

Non-functional requirements (NFR) are fundamental for the software development. The NFR- Framework allows the elicitation to deeply cover necessary trade-offs involving synergetic and conflicting solutions. It also favor the capture of design decisions involving the reasons that lead one to choose between one alternative and another to implement a...

Alguns pesquisadores em Engenharia de Software afirmam que somente os experimentos, no centro do processo cientifico, podem verificar novas teorias e, indicar as correcoes cabiveis e explorar os fatores criticos dessa nova teoria. Afirmam tambem que novos metodos, tecnicas e ferramentas em Engenharia de Software nao deveriam ser publicados sem ante...

Modeling approaches are based on various paradigms, e.g., aspect-oriented, feature-oriented, object-oriented, and logic-based. Modeling approaches may cover requirements models to low-level design models, are developed for various purposes, use various means of composition, and thus are difficult to compare. However, such comparisons are critical t...

Documenting software architecture rationale is essential to reuse and evaluate architectures, and several modeling and documentation guidelines have been proposed in the literature. However, in practice creating and updating these documents rarely is a primary activity in most software projects, and rationale remains hidden in casual and semi-struc...

The Intentional Requirements Engineering method is presented as an extension of the i* Framework. The method provides the requirements engineering team a set of useful procedures and tools to guide the construction of i-Star models. The approach uses Leite’s viewpoint on Requirements Engineering (RE), which consider the following main RE activities...

Resumo O paradigma orientado a agentes introduz conceitos como proatividade e autonomia para obter sistemas mais flexíveis e robustos em ambientes computacionais complexos. Sistemas Multi-Agentes provêem a representação e implementação de novas aplicações com requisitos e características das organizações sociais, como autonomia, proatividade e mobi...

Agent orientation appears as a solution for constructing complex systems adapting the requirements identification to cope with agent properties like autonomy, sociability and pro-activeness. Many methodologies were proposed adopting this new paradigm. However, most of them are still in development and therefore need to be adapted. In this work MaSE...

Deciding how to operationalize non-functional requirements (NFR) is a complex task, and several formalisms have been proposed to represent design decisions and their rationale. Unfortunately, these models can become complex (even unreadable) for designs with many alternatives and/or a well-documented rationale, which makes very hard to review and c...

If we make a simple search on the internet for the definition of transparency there will be several different ones from optics to protocols. But most of the definitions will overlap among the notion that transparency is about how something is open enough to allow things to be deeply observed from different perspectives. Orthogonally, Transparency h...

Understanding Non-Functional Requirements (NFRs) and trade-offs among them is a key task for systems architects. Modeling notations have been proposed to represent NFRs and tradeoffs among them, yet identification of relevant knowledge inside models (for understanding and/or reuse) remains quite simplistic and manual. This paper proposes to address...

Practice has proven that softgoal interdependency graphs(SIGs) are a very useful tool for recording and reasoning about non-functional requirements [4], [6], [8]. Practical reuse and design of SIGs, however, rely on the capacity of manually identifying reusable structures, interdependencies, and eliminating harmful redundancies. In this paper, we t...

Understanding non-functional requirements (NFR) and their solutions is a key architecture task, and reusing past solutions is an effective and efficient way to satisfy NFRs. NFR catalogues have been proposed to store and reuse NFR knowledge descriptions, yet identification of reusable knowledge inside catalogues remains quite hard and tedious. This...

Modeling with i * is not a trivial task. Our work describes i * Diagnoses Framework, a quality oriented process to analyze i * models. Our process is similar to some of the reading techniques of inspection methods and bears some similarity with the inquiry based requirement analysis approach. Our process focuses on defect prevention considering bot...

Agent-Oriented Software Methods" deals with agents' goals, commitments, beliefs, and abilities, but very few of these methods properly deal with the elicitation of these concepts. We believe that to build a goal model, first of all, we must accurately elicit and work with goals in several levels. Our approach named AGFL - Agent Goals from Lexicon i...

The aim of this paper is to present the Intentional Requirements Engineering Method - ERi'*c, which is a contribution to Coal Oriented Requirements Engineering (CORE). ERi*c is based on the intentionality concept as applied by the i* Framework. Intentionality reflects organization actors' motivations and interests and is represented in the models b...

MAS methods still lack coverage to the goal elicitation process, especially on how to identify goals from corporate information, mission statements and from interviews with stakeholders. Only after eliciting goals we will be able to properly deal with goal models. On the other hand, intentionality models, for example the i* framework, are, usually,...

World Wide Web (WWW)-based electronic commerce has emerged as a mean to conduct business transactions that were previously handled through traditional interorganizational systems, phone, fax, on-site visits, or mail. Today, electronic procurement (e-procurement) accounts for most of the volume and value of the business transactions conducted over t...

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

The increasing use of multi-agent systems brings challenges that have not been studied yet, such as how should we adapt requirements elicitation to cope with agent properties like autonomy, sociability and pro-activeness. Many methodologies were proposed adopting this new paradigm. However, most of them are still in their early phases and therefore...

Recently, there has been a growing interest in the Agent-oriented paradigm to cope with the needs imposed by nowadays complex and networked systems. Developing Multi-Agent Systems (MAS) calls for addressing aspects such as interaction, autonomy, collaboration and pro-activeness. One way to cope with these needs is to have agency properties as well...

Developing Multi-Agent Systems (MAS) calls for addressing different concerns. Some of them are general and related to the technology and others are particular to each collaborating agent. Our proposal aims to provide a more holistic approach to the construction of MAS. Integrating three different perspectives for information modeling we have achiev...

Privacy is a fundamental aspect when dealing with Personal Information. Privacy requirements are those that capture privacy goals and its associated measures for a system under development. In order to ensure privacy we must identify these elements. However, there are many challenges in their identification. For example, privacy requirements may be...

The i* framework has been increasingly used by the requirements engineering community. However, good practices are not always followed. Many papers have presented the use of i* constructs in such ways that results are not coherent with their original specifications. Some cases attempt to adapt the framework to specific needs by misusing its element...

There are many different approaches to understand and model system requirements. However, systems today tend to be increasingly complex. Agent- and goal-oriented paradigms have been proposed as an alternative to object orientation to cope with these demands. Although it may be intuitive that object-oriented methods could not readily deal with issue...

Usability is becoming increasingly recognized as being an important factor in the acceptance of systems by end users. There is a basic need for systematic approaches to reason, model and analyze usability from the early stages of software development. Furthermore, it is necessary to develop a usable ontology or classification of measurable aspects...

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

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

Although Non-Functional Requirements (NFR) have been present in many software development methods, they have been faced as a second or even third class type of requirement, frequently hided inside notes and therefore frequently neglected or forgotten. Surprisingly, despite the fact that nonfunctional requirements (NFR) are among the most expensive...

Systems development methodologies continue to be a central area of research in software engineering. As the nature of applications and systems usage move in- creasingly towards open networked environments, not only are new methodologies required, but new ways for evaluating methodologies for these new environments are also required. The agent-orien...

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

Usability has been increasingly recognized as 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...

A fundamental premise of the semantic web is that a level of interoperability is guaranteed among applications running in an open environment. By the use of ontologies applications are able to share information and exchange meaningful data. In this context ontology alignment is paramount to assure communication among applications. In this paper we...

Privacy may be interpreted in different ways in different contexts, and may be achieved by means of different mechanisms. It is also frequently intertwined with security concerns. However, other requirements such as functionality, usability and reliability, must also be addressed since they often compete among each other. While the understanding of...

In a multi-agent world, privacy may have different meaning and significance for different agents. From a system design viewpoint, a practical approach to privacy should allow for a variety of perceptions and perspectives on privacy. Furthermore, privacy must be considered together with all the other requirements - functionality, usability, performa...

The agent-oriented approach to software development is transitioning from the prototyping done by researchers to the development of large-scale industrial-strength applications by software professionals. For this to succeed, methodologies are needed to systematically guide and support developers through the various stages of system development. A n...

Large-scale software systems typically involve a large number of actors playing different roles, interacting with each other to achieve personal and common goals. As agent-based software technologies advance, systematic methods are needed to support the development of large-scale multi-agent systems. As with other kinds of software systems, success...

There are many different approaches to elicit requirements, each having strengths and weaknesses. Hence, some approaches may be more suitable to one domain than 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...

Although Non-Functional Requirements (NFRs) have been present in many software development methods, they have been presented as a second or even third class type of requirement, frequently hidden inside notes and therefore, frequently neglected or forgotten. Surprisingly, despite the fact that non-functional requirements arc among the most expensiv...

Although Non-Functional Requirements (NFRs) have been present in many software development methods, they have been presented as a second or even third class type of requirement, frequently hidden inside notes and therefore, frequently neglected or forgotten. Surprisingly, despite the fact that non-functional requirements arc among the most expensiv...

Companies that are according to ISO 9000 standards have to maintain a set of documents describing the quality system that include policies, procedures and instructions to assure the final product's conformance with ISO 9000 requirements. Each change to be introduced in the certified process has to be first written down in the respective documents t...

Although business rules have been largely used in database modeling, very little can be found in requirements engineering literature. Many articles have been written about the use of business rules but only a few on how to elicit them. This article focuses on business rules as prescribed procedures that should be followed to achieve the business's...

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

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

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

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

Although Non-Functional Requirements (NFR) have been present in many software development methods, they have been faced as a second or even third class type of requirement, frequently hided inside notes and therefore frequently neglected or forgotten. Surprisingly, despite the fact that non- functional requirements (NFR) are among the most expensiv...

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

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

Business rules have been largely used in database modeling and more recently in the field of information technology, but rarely in requirements engineering. This article focuses on business rules as prescribed procedures that should be followed to achieve the business's goals. The ISO 9000 documentation includes policies, procedures and instruction...

Complex information systems need conceptual models to deal with aspects beyond the usual entity and activity framework. Recent research has pointed out that conceptual models need to deal with goals, in order to model complex situations that happen in the real world. Our work investigated a new strategy that allows the integration of non-functional...

Recent research points out that conceptual model need to deal with goals, in order to model complex situations that happen in the real world. This work proposes to use non-functional requirements to analyze data models. The analysis is anchored in the use of Language Extended Lexicon (LEL) to build both NFR graph and the data models together with t...

Requisitos não funcionais expressam qualidades de cunho geral, bem como, restrições específicas de um determinado problema. Esse tipo de requisito sempre existiu mas não vinha sendo tratado de forma sistematizada quando se pensava na definição de um software. Esse trabalho aborda diretamente o aspecto de requisitos não funcionais durante as fases i...

The agent-oriented approach to software engineering introduces concepts such as pro-activeness and autonomy to achieve more flexible and robust systems for complex applications environments. A number of AOSE (Agent Oriented Software Engineering) methodologies have been proposed so far. In order to evaluate and compare some of these methods in depth...

Business Process Management (BPM) has arisen as a new trend in information technology that aims to unify disciplines such as Process Modeling, Simulation, Workflow, Enterprise Application integration and Business-to-Business integration into a single standard [Owen 03]. The recent initiatives have emphasized process models that can lead directly to...

Resumo. Sistemas Multi-Agentes provêm a representação e implementação de novas aplicações com requisitos e características das organizações sociais, como autonomia, pro-atividade e mobilidade. O tratamento de diabetes requer um controle diário e acompanhamento sistemático do paciente, necessitando muitas vezes de ajustes perante as situações do dia...

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

Today the requirements engineer has at his or her disposal a plethora of field tested approaches in which to elicit system requirements. In a few specific domains, however, the generality of the methods prevents them from being taken by the book. The health care d omain is one of such domains. Not only it is a complex domain with many subtleties, b...