Requirements Engineering of Village Innovation Application Using Goal-Oriented Requirements Engineering (GORE)

The delay in the absorption of village funds from the central government to the village government is due to the village government's difficulty preparing village development innovation programs. The innovation tradition will grow if the cycle of transformation of knowledge and acceptable practices from one village to another, especially villages with similar conditions and problems, can run smoothly.  For the process of exchanging knowledge and experiences between villages to run smoothly, it is necessary to codify best practices in a structured, documented, and disseminated manner. This research aims to design an application that functions as a medium for sharing knowledge about the use of village funds through government innovation narratives. The application is expected to become a reference for villages to carry out innovative practices by conducting replication studies and replicating acceptable practices that other villages have done. Therefore, it is necessary to have a system requirements elicitation method that can explore the village's requirements in sharing knowledge so that the resulting system is of high quality and by the objectives of being developed. There are several Goal-Oriented Requirements Engineering (GORE) methods used, such as Knowledge Acquisition in Automated Specification (KAOS) and requirements engineering based on business processes. In this research, the KAOS method was demonstrated as the elicitation activity of a village innovation system. Then the results were stated in the Goal Tree Model (GTM). Model building begins with discussions with the manager of the village innovation program to produce goals. The goals are then broken down into several sub-goals using the KAOS method. The KAOS method is used for the requirements elicitation process resulting in functional and non-functional requirements. This research is the elicitation of the requirement for the village innovation system so that it can demonstrate the initial steps in determining the requirements of the village innovation system before carrying out the design process and the system creation process. The results of this requirement elicitation can be used further in the software engineering process to produce quality and appropriate village innovation applications.The delay in the absorption of village funds from the central government to the village government is due to the village government's difficulty preparing village development innovation programs. The innovation tradition will grow if the cycle of transformation of knowledge and acceptable practices from one village to another, especially villages with similar conditions and problems, can run smoothly.  For the process of exchanging knowledge and experiences between villages to run smoothly, it is necessary to codify best practices in a structured, documented, and disseminated manner. This research aims to design an application that functions as a medium for sharing knowledge about the use of village funds through government innovation narratives. The application is expected to become a reference for villages to carry out innovative practices by conducting replication studies and replicating acceptable practices that other villages have done. Therefore, it is necessary to have a system requirements elicitation method that can explore the village's requirements in sharing knowledge so that the resulting system is of high quality and by the objectives of being developed. There are several Goal-Oriented Requirements Engineering (GORE) methods used, such as Knowledge Acquisition in Automated Specification (KAOS) and requirements engineering based on business processes. In this research, the KAOS method was demonstrated as the elicitation activity of a village innovation system. Then the results were stated in the Goal Tree Model (GTM). Model building begins with discussions with the manager of the village innovation program to produce goals. The goals are then broken down into several sub-goals using the KAOS method. The KAOS method is used for the requirements elicitation process resulting in functional and non-functional requirements. This research is the elicitation of the requirement for the village innovation system so that it can demonstrate the initial steps in determining the requirements of the village innovation system before carrying out the design process and the system creation process. The results of this requirement elicitation can be used further in the software engineering process to produce quality and appropriate village innovation applications

Evaluation of the Goal-Oriented Requirements Engineering Method KAOS

Software engineering is a complex task. But although there is no silver bullet that guarantees accomplishing this task, appropriate methods can support the engineer by addressing the characteristics that make it complex. The objective of this paper is to evaluate whether and how the goal-oriented requirements engineering method KAOS addresses these characteristics of complex tasks and thereby, whether it effectively supports software engineering. For serving this purpose, we conduct a literature analysis, which discloses core concepts underlying to the KAOS method, and we apply KAOS in two software development projects, which provide insights into KAOS in use. Our results show that KAOS, despite of some shortcomings, addresses all characteristics, but that applying it can be work intensive. Consequently, while KAOS supports software engineering, provided support must be weigh up against invested work

Goal-oriented requirements engineering: an extended systematic mapping study.

Over the last two decades, much attention has been paid to the area of goal-oriented requirements engineering (GORE), where goals are used as a useful conceptualization to elicit, model, and analyze requirements, capturing alternatives and conflicts. Goal modeling has been adapted and applied to many sub-topics within requirements engineering (RE) and beyond, such as agent orientation, aspect orientation, business intelligence, model-driven development, and security. Despite extensive efforts in this field, the RE community lacks a recent, general systematic literature review of the area. In this work, we present a systematic mapping study, covering the 246 top-cited GORE-related conference and journal papers, according to Scopus. Our literature map addresses several research questions: we classify the types of papers (e.g., proposals, formalizations, meta-studies), look at the presence of evaluation, the topics covered (e.g., security, agents, scenarios), frameworks used, venues, citations, author networks, and overall publication numbers. For most questions, we evaluate trends over time. Our findings show a proliferation of papers with new ideas and few citations, with a small number of authors and papers dominating citations; however, there is a slight rise in papers which build upon past work (implementations, integrations, and extensions). We see a rise in papers concerning adaptation/variability/evolution and a slight rise in case studies. Overall, interest in GORE has increased. We use our analysis results to make recommendations concerning future GORE research and make our data publicly available

Combining goal-oriented and model-driven approaches to solve the Payment Problem Scenario

Motivated by the objective to provide an improved participation of business domain experts in the design of service-oriented integration solutions, we extend our previous work on using the COSMO methodology for service mediation by introducing a goal-oriented approach to requirements engineering. With this approach, business requirements including the motivations behind the mediation solution are better understood, specified, and aligned with their technical implementations. We use the Payment Problem Scenario of the SWS Challenge to illustrate the extension

A Survey of Requirements Engineering Methods for Pervasive Services

Designing and deploying ubiquitous computing systems, such as those delivering large-scale mobile services, still requires large-scale investments in both development effort as well as infrastructure costs. Therefore, in order to develop the right system, the design process merits a thorough investigation of the wishes of the foreseen user base. Such investigations are studied in the area of requirements engineering (RE). In this report, we describe and compare three requirements engineering methods that belong to one specific form of RE, namely Goal-Oriented Requirements Engineering. By mapping these methods to a common framework, we assess their applicability in the field of ubiquitous computing systems

Modelling the Strategic Alignment of Software Requirements using Goal Graphs

This paper builds on existing Goal Oriented Requirements Engineering (GORE) research by presenting a methodology with a supporting tool for analysing and demonstrating the alignment between software requirements and business objectives. Current GORE methodologies can be used to relate business goals to software goals through goal abstraction in goal graphs. However, we argue that unless the extent of goal-goal contribution is quantified with verifiable metrics and confidence levels, goal graphs are not sufficient for demonstrating the strategic alignment of software requirements. We introduce our methodology using an example software project from Rolls-Royce. We conclude that our methodology can improve requirements by making the relationships to business problems explicit, thereby disambiguating a requirement's underlying purpose and value.Comment: v2 minor updates: 1) bitmap images replaced with vector, 2) reworded related work ref[6] for clarit

GOREWEB framework for goal oriented requirements engineering of web applications

In this paper, we propose a framework for modeling goal driven requirements of web applications. Web engineers mostly focus on design aspects only overlooking the real goals and expectations of the user. Goal oriented Requirement Engineering is a popular approach for Information system development but has not been explored much for Web applications. However, in today's times Web is dominating in every business making it imperative that its requirements are analyzed carefully and in profundity. Goal driven requirements analysis helps in capturing stakeholders' goals very finely, by choosing between alternatives and resolving conflicts. Detailed classification of both functional and non-functional requirements specific to web applications is discussed in the presented work. A framework, GOREWEB (Goal oriented Requirements Engineering for Web Applications) is proposed for analyzing goals and translating them into functional and non-functional web requirements

Goal oriented requirements engineering for blockchain based food supply chain

Blockchain technology is the buzz word in the industry and research fields and it is considered to be a disruptive technology. Every organization that interacts with agents and intermediaries for getting their business processes are trying to bring Blockchain in their business for the efficiency, security and trust it can bring. The world has started experimenting with blockchain but there are still a lot of basic issues that need attention as the technology is relatively new. The standards and practices for implementing this new technology are not yet in place which impede its full acceptance despite being useful. Blockchain applications have specific concerns like non-repudiation, data privacy, immutable transactions etc. which should be addressed for the implementation of technology. Goal oriented Requirements Engineering is a popular technique that helps in understanding business goals in a comprehensive manner. As a first step towards formalizing the requirements analysis, this paper focuses on identifying the goals and softgoals for blockchain enabled systems. Specifically, a case study on blockchain enabled food supply chain has been explored for identifying the goals and softgoals. These goals can then be used by software engineers or practitioners for requirements specification and system design