Analyzing requirements of knowledge management systems with the support of agent organizations

Knowledge Management (KM) is considered by many organizations a key aspect in sustaining competitive advantage. Designing appropriate KM processes and enabling technology face considerable risks, as they must be shaped to respond to specific needs of the organizational environment. Thus, many systems are abandoned or fall into disuse because of inadequate understanding of the organizational context. This motivates current research, which tends to propose agent organizations as a useful paradigm for KM systems engineering. Following these approaches, organizations are analyzed as collective systems, composed of several agents, each of them autonomously producing and managing their own local data according to their own logic, needs, and interpretative schema, i.e. their goals and beliefs. These agents interact and coordinate for goal achievement defining a coherent local knowledge system. This paper presents a novel methodology for analyzing the requirements of a KM system based on an iterative workflow where a pivotal role is played by agent-oriented modeling. Within this approach, the needs for KM systems are traced back to the organization stakeholders’ goals. A case study is used to illustrate the methodology. The relationship of this work with current studies in agent organizations and organizational knowledge management is also discussed. Differently from other works, this methodology aims at offering a practical guideline to the analyst, pointing out the appropriate abstractions to be used in the different phases of the analysis

The i* framework for goal-oriented modeling

The final publication is available at Springer via http://dx.doi.org/10.1007/978-3-319-39417-6i* is a widespread framework in the software engineering field that supports goal-oriented modeling of socio-technical systems and organizations. At its heart lies a language offering concepts such as actor, dependency, goal and decomposition. i* models resemble a network of interconnected, autonomous, collaborative and dependable strategic actors. Around this language, several analysis techniques have emerged, e.g. goal satisfaction analysis and metrics computation. In this work, we present a consolidated version of the i* language based on the most adopted versions of the language. We define the main constructs of the language and we articulate them in the form of a metamodel. Then, we implement this version and a concrete technique, goal satisfaction analys is based on goal propagation, using ADOxx. Throughout the chapter, we used an example based on open source software adoption to illustrate the concepts and test the implementation.Peer ReviewedPostprint (author's final draft

Agent Oriented Software Engineering (AOSE) Approach to Game Development Methodology

This thesis investigates existing game development methodologies, through the process of researching game and system development models. The results indicate that these methodologies are engineered to solve specific problems, and most are suitable only for specific game genres. Different approaches to building games have been proposed in recent years. However, most of these methodologies focus on the design and implementation phase. This research aims to enhance game development methodologies by proposing a novel game development methodology, with the ability to function in generic game genres, thereby guiding game developers and designers from the start of the game development phase to the end of the implementation and testing phase. On a positive note, aligning development practice with universal standards makes it far easier to incorporate extra team members at short notice. This increased the confidence when working in the same environment as super developers. In the gaming industry, most game development proceeds directly from game design to the implementation phase, and the researcher observes that this is the only industry in which this occurs. It is a consequence of the game industry’s failure to integrate with modern development techniques. The ultimate aim of this research to apply a new game development methodology using most game elements to enhance success. This development model will align with different game genres, and resolve the gap between industry and research area, so that game developers can focus on the important business of creating games. The primary aim of Agent Oriented Agile Base (AOAB) game development methodology is to present game development techniques in sequential steps to facilitate game creation and close the gap in the existing game development methodologies. Agent technology is used in complex domains such as e-commerce, health, manufacturing, games, etc. In this thesis we are interested in the game domain, which comprises a unique set of characteristics such as automata, collaboration etc. Our AOAB will be based on a predictive approach after adaptation of MaSE methodology, and an adaptive approach using Agile methodology. To ensure proof of concept, AOAB game development methodology will be evaluated against industry principles, providing an industry case study to create a driving test game, which was the problem motivating this research. Furthermore, we conducted two workshops to introduce our methodology to both academic and industry participants. Finally, we prepared an academic experiment to use AOAB in the academic sector. We have analyzed the feedbacks and comments and concluded the strengths and weakness of the AOAB methodology. The research achievements are summarized and proposals for future work outlined

Requirements-Driven Adaptation of Choreographed Interactions

Electronic services are emerging as the de-facto enabler of interaction interoperability across organization boundaries. Cross-organizational interactions are often “choreographed”, i.e. specified by a messaging protocol from a global point of view independent of the local view of each interacting organization. Local requirements motivating an interaction as well as the global contextual requirements governing the interaction inevitably evolve over time, requiring adaptation of the corresponding interaction protocol. Adaptation of an interaction protocol must ensure the satisfaction of both sets of interaction requirements while maintaining consistency between the global view and the local views of an interaction specification. Such adaptation is not possible with the current state-of-the-art representations of choreographed interactions, as they capture only operational messaging specifications detached from both local organizational requirements as well as global contextual requirements. This thesis presents three novel contributions that tackle adaptation of choreographed interaction protocols: an automated technique for deriving an interaction protocol from requirements, a formalization of consistency between local and global views, and a framework for guiding the adaptation of a choreographed interaction. A choreographed interaction is specified using models of organizational requirements motivating the interaction. We employ the formal semantics embedded in requirements models to automatically derive an interaction protocol. We propose a framework for relating the global and local views of interaction specification and maintaining consistency between them. We develop a metamodel for interaction specification, from which we enumerate adaptation operations. We build a catalogue that provides guidance on performing each operation and propagating changes between the global and local views. These contributions are evaluated using examples from the literature as well as a real-world case study

A POS Tagging Approach to Capture Security Requirements within an Agile Software Development Process

Software use is an inescapable reality. Computer systems are embedded into devices from the mundane to the complex and significantly impact daily life. Increased use expands the opportunity for malicious use which threatens security and privacy. Factors such as high profile data breaches, rising cost due to security incidents, competitive advantage and pending legislation are driving software developers to integrate security into software development rather than adding security after a product has been developed. Security requirements must be elicited, modeled, analyzed, documented and validated beginning at the initial phases of the software engineering process rather than being added at later stages. However, approaches to developing security requirements have been lacking which presents barriers to security requirements integration during the requirements phase of software development. In particular, software development organizations working within short development lifecycles (often characterized as agile lifecycle) and minimal resources need a light and practical approach to security requirements engineering that can be easily integrated into existing agile processes. In this thesis, we present an approach for eliciting, analyzing, prioritizing and developing security requirements which can be integrated into existing software development lifecycles for small, agile organizations. The approach is based on identifying candidate security goals, categorizing security goals based on security principles, understanding the stakeholder goals to develop preliminary security requirements and prioritizing preliminary security requirements. The identification activity consists of part of speech (POS) tagging of requirements related artifacts for security terminology to discover candidate security goals. The categorization activity applies a general security principle to candidate goals. Elicitation activities are undertaken to gain a deeper understanding of the security goals from stakeholders. Elicited goals are prioritized using risk management techniques and security requirements are developed from validated goals. Security goals may fail the validation activity, requiring further iterations of analysis, elicitation, and prioritization activities until stakeholders are satisfied with or have eliminated the security requirement. Finally, candidate security requirements are output which can be further modeled, defined and validated using other approaches. A security requirements repository is integrated into our proposed approach for future security requirements refinement and reuse. We validate the framework through an industrial case study with a small, agile software development organization