Goal-driven business process analysis application in electricity deregulation

Kavakli, V; Loucopoulos, Pericles

doi:10.1016/s0306-4379(99)00015-0

Cited by 88 publications

(72 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…The goals realized by existing processes [31], [36] were then abstracted from the process descriptions and structured in a goal hierarchy, thus establishing the connection between the current enterprise purpose and behavior. In fact, the guideline associated to the map section MS2 suggests defining the goal hierarchy of the enterprise corresponding to its current state, by clustering the business processes aiming to achieve the same high-level business goal.…”

Section: Iv22 Abstracting Current Enterprise Goals: 'As-is' Statementioning

confidence: 99%

A multi-method for defining the organizational change

Nurcan

Rolland

2003

Information and Software Technology

View full text Add to dashboard Cite

The assumption of the work presented in this paper is the situatedness of the change process. The Enterprise Knowledge Development -Change Management Method (EKD-CMM) provides multiple and dynamically constructed ways of working to organize and to guide the change management. The method is built on the notion of labeled graph of intentions and strategies called a road map and the associated guidelines. The EKD-CMM road map is a navigational structure that supports the dynamic selection of the intention to be achieved next andthe appropriate strategy to achieve it whereas guidelines help in the operationalization of the selected intention following the selected strategy. This paper presents the EKD-CMM road map and guidelines and exemplifies their use with a real case study.

show abstract

Section: Iv22 Abstracting Current Enterprise Goals: 'As-is' Statementioning

confidence: 99%

A multi-method for defining the organizational change

Nurcan

Rolland

2003

Information and Software Technology

View full text Add to dashboard Cite

show abstract

“… Elicitation of the needs: A phase that helps to understand the organizational situation and the expression of needs [6], [7], [8], [9], [10].…”

Section: Needs Engineering Approachesmentioning

confidence: 99%

“…In the scenarios, we distinguish between a normal scenario and an exceptional scenario (a scenario that describes what happens if the normal scenario does not work) [8], but the limit always remains in describing what will not happen in exceptional cases and is not a real-life scenario since it does not help in achieving the goal. In our work [51], we proposed a new formalization of the associating for each goal two scenarios: normal(NS) and alternate(AS) which form both a set of steps.…”

Section: D) Scenario Life Cyclementioning

confidence: 99%

“…For example, needs can be collected in the form of queries and subsequently be formulated into goals and into decisions. The authors use an owner goals' model GDI (Goal / Decision / Information) to represent them [8]. In other works [9] to treat DNs, a model of analytical requirements' specification is used (queries / tables) to extract fact tables and dimension tables.…”

Section: Models Of the Needs" Representationmentioning

confidence: 99%

See 1 more Smart Citation

A Comparative Study of the Decisional Needs Engineering Approaches

Ahmad¹,

Zerhouni²,

Abdali³

2018

ijacsa

View full text Add to dashboard Cite

Abstract-Requirements Engineering (RE) is an important phase in a project of systems development. It helps designanalysts to design and to model the expression of the end-user needs, and their expectations vis-a-vis their future system. This engineering is studying two major issues that are: What should the system do in order to have a complete needs specification, and reason on the why: "Why do we need to build this system? ", without looking for how to build it. The vast majority of needs engineering approaches are based on two concepts: scenario or goal; there are generally three types of approaches: ScenarioOriented Approaches, Goal-Oriented Approaches and approaches generated by the couple: goals and scenarios at the same time. In the remainder of this paper, we present a comparative study of the three types of the RE approaches, then models of needs representation, and finally we conclude with the conclusions.

show abstract

“…Goals are usually explicitly stated in the user requirements document, informing the purpose of the supporting business. A goal-decomposition technique is employed, similar to [57,58], starting from analysis of high level strategic concerns and ending up with the requirements specification broken down and low-level functional requirements exposed and related.…”

Section: Requirements Model: Goal Decompositionmentioning

confidence: 99%

Adaptive Agent Model: Software Adaptivity using an Agent-oriented Model-Driven Architecture

Xiao

Greer

2009

Information and Software Technology

View full text Add to dashboard Cite

Model-Driven Architecture (MDA) promotes the development of software systems through successive building and generation of models, improving the reusability of models. Applying the same principles to the area of Agent-Oriented Software Engineering (AOSE) advances the ideas behind MDA even more significantly, due to the inherent adaptivity of software agents We describe an appropriate set of models originating from requirements specification and transformable to models understandable and executable by agents thus demonstrating an Agent-oriented Model-Driven Architecture (AMDA) approach. In AMDA, agents use hierarchical business knowledge models with business process rules at the top, business rules to control policy and logic in the middle and a base layer defining business concepts. Being externalised, knowledge is easily configurable by human beings and applied by software agents. A real case study is used to illustrate the process. The main advances over the object-oriented MDA are (i) the addition of component dynamics (ii) the use of agent-executable rule-based business models and (iii) a proposed higher level of abstraction with the direct representation of business requirements.

show abstract

Goal-driven business process analysis application in electricity deregulation

Cited by 88 publications

References 3 publications

A multi-method for defining the organizational change

A multi-method for defining the organizational change

A Comparative Study of the Decisional Needs Engineering Approaches

Adaptive Agent Model: Software Adaptivity using an Agent-oriented Model-Driven Architecture

Contact Info

Product

Resources

About