Integrating organizational requirements and object oriented modeling

Abstract

In recent years we have observed a growing influence of the object-orientation paradigm. Unfortunately, the current dominant object oriented modeling technique, i.e. the llnified Modeling Language -UML, is ill equipped for modeling early requirements which are typically informal and often focus on stakeholder objectives. Instead, UML is suitable for later phases of requirement capture which usually focus on completeness, consistency, and automated verification of functional requirements for the new system. In this paper, we present a set qf guidelines specifications. For early (organizational) modeling we rely on the i* framework, whereas for late (functional) requirements specification, we rely on a precise subset of UML. A small example is used to illustrate how the requirements process iterates between early and late requirements.for the integration of early and late requirements

Model-driven Techniques for Data Model Synthesis

“…Most of the identified papers present the automatic synthesis of the data model to some extent, while only two papers [81], [84] present manual data model derivation. Most of the papers reporting automated data model synthesis are mutually related and present improvements in the same approach and the same tool named GOOD/XGOOD [85]- [88]. Other proposals based on TROPOS models in [91], [92] and V-graph in [93] are also mainly automated to some extent, but not evaluated.…”

From the Business Decision Modeling to the Use Case Modeling in Data Mining Projects

“…In complex systems, a combination of natural language and graphical models can be a good choice. Some standard graphical notations used for business modeling are UML, BPMN (Russell et al, 2006), (Wilcox & Gurau, 2003), (Agulilar-Saven, 2004), (Berenbach, 2004), (Vérosle et al, 2003), (Wohed et al, 2006), (White, 2004), and i* (Yu, 1995), (Yu, 1996), (Yu & Mylopoulos, 1997), (Alencar et al, 2000), (Castro, et al, 2001), (Santander & Castro, 2002). i* is described below.…”

Business process-based requirements specification and object-oriented conceptual modelling of information systems

“…The third kind of approaches correspond to i*-based approaches that address derivation of class diagrams (e.g., (Castro, et al, 2001)). As in Section 2.3, these approaches are not reviewed because they focus on support of goals instead of on support of business processes when specifying system requirements and thus when deriving OO conceptual schemas.…”