Viewpoints and goals: towards an integrated approach

Dissertação de Mestrado em Engenharia InformáticaRequirements elicitation and analysis have been studied according to several approaches that differ mostly on their "orientation", in this case relying on goals or viewpoints. Goal-Oriented approaches such as KAOS rely on goals to direct their process of eliciting requirements: a goal is an objective the system under consideration should achieve and represents a system property that may reflect either a functional (e.g. a service provided by the system) or a non-functional (e.g. security, performance) requirement; its satisfaction may imply the participation of several agents and the resolution of possible obstacles that may arise. The KAOS approach offers an unambiguous method for requirement decomposition and may provide a set of heuristics to approaches where one does not exist. Viewpoint-Oriented approaches such as PREview focus on gathering information pertaining to the problem from several agents that may have different, often equally valid, and incomplete perspectives on the problem. These partial intakes reflect their different responsibilities, roles, goals, or interpretations of the information sources; hence the combination of the agent and its input on the system is called a viewpoint. PREview benefits from a particularly lightweight approach to requirements encapsulation, but fails to provide a set of heuristics for the process of identifying the system's requirements. Considering the issues identified in each approach, it is verifiable that both approaches are complementary: on the one hand, KAOS offers a set of requirements elicitation heuristics through goal decomposition; on the other hand, PREview is a lightweight approach to viewpoint oriented requirements engineering, tailored especially for integration, however lacks a more systematic mechanism to guide the requirements elicitation process. The objective of this dissertation is therefore to propose a hybrid approach that builds on the PREview approach and brings together the benefits of the KAOS approach. The result is synergetic where, for example, completion is better addressed by providing a set of heuristics for requirement elicitation

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

A goal-oriented requirements modelling language for enterprise architecture

Methods for enterprise architecture, such as TOGAF, acknowledge the importance of requirements engineering in the development of enterprise architectures. Modelling support is needed to specify, document, communicate and reason about goals and requirements. Current modelling techniques for enterprise architecture focus on the products, services, processes and applications of an enterprise. In addition, techniques may be provided to describe structured requirements lists and use cases. Little support is available however for modelling the underlying motivation of enterprise architectures in terms of stakeholder concerns and the high-level goals that address these concerns. This paper describes a language that supports the modelling of this motivation. The definition of the language is based on existing work on high-level goal and requirements modelling and is aligned with an existing standard for enterprise modelling: the ArchiMate language. Furthermore, the paper illustrates how enterprise architecture can benefit from analysis techniques in the requirements domain

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

Towards a flexible service integration through separation of business rules

Driven by dynamic market demands, enterprises are continuously exploring collaborations with others to add value to their services and seize new market opportunities. Achieving enterprise collaboration is facilitated by Enterprise Application Integration and Business-to-Business approaches that employ architectural paradigms like Service Oriented Architecture and incorporate technological advancements in networking and computing. However, flexibility remains a major challenge related to enterprise collaboration. How can changes in demands and opportunities be reflected in collaboration solutions with minimum time and effort and with maximum reuse of existing applications? This paper proposes an approach towards a more flexible integration of enterprise applications in the context of service mediation. We achieve this by combining goal-based, model-driven and serviceoriented approaches. In particular, we pay special attention to the separation of business rules from the business process of the integration solution. Specifying the requirements as goal models, we separate those parts which are more likely to evolve over time in terms of business rules. These business rules are then made executable by exposing them as Web services and incorporating them into the design of the business process.\ud Thus, should the business rules change, the business process remains unaffected. Finally, this paper also provides an evaluation of the flexibility of our solution in relation to the current work in business process flexibility research

Early aspects: aspect-oriented requirements engineering and architecture design

This paper reports on the third Early Aspects: Aspect-Oriented Requirements Engineering and Architecture Design Workshop, which has been held in Lancaster, UK, on March 21, 2004. The workshop included a presentation session and working sessions in which the particular topics on early aspects were discussed. The primary goal of the workshop was to focus on challenges to defining methodical software development processes for aspects from early on in the software life cycle and explore the potential of proposed methods and techniques to scale up to industrial applications