1 |
ON THE ALIGNMENT BETWEEN GOAL MODELS AND ENTERPRISE MODELS WITH AN ONTOLOGICAL ACCOUNTCARDOSO, E. C. S. 16 December 2009 (has links)
Made available in DSpace on 2016-08-29T15:33:10Z (GMT). No. of bitstreams: 1
tese_3334_.pdf: 6590453 bytes, checksum: 5654758329fe7af83bec07339d8a3ffb (MD5)
Previous issue date: 2009-12-16 / Business process modelling basically comprises an activity whose main goal is to provide a formalization of business processes in an organization or a set of cooperating organizations (Recker, et al., 2006) (van der Aalst, et al., 2003). By modelling an organizations business processes, it is possible to capture how the organization coordinates the work and resources with the aim of achieving its goals and strategies (Sharp, et al., 2001). Since business processes and goals are intrinsically interdependent, establishing an alignment between the process and the goal domains arises as a natural approach.
This thesis reports on a real-life exploratory case study in which we investigated the relationship between the elements of the enterprise (modeled in the ARIS framework) and the goals (modeled in the Tropos framework and modeling language) which are attained by these elements. The case study has been conducted in the Rheumatology Department of a University Hospital in Brazil. In the course of the case study, we have identified the need of splitting this effort into three phases: the elicitation phase (in which goal models and business process models are captured from the organizational domain), the harmonization phase (in which the goal domain is structured for alignment according to the business processes structures that will support it) and the alignment phase (in which the relationships between the goal domain and the elements of the organizational domain are established).
In order to investigate the relation between goals and enterprise elements, we propose an ontological account for both architectural domains. We recognize the importance in considering the business process as the means for implementing an enterprises strategy, but we do not exclude the remaining enterprise elements. Furthermore, we are concerned with both the identification of the relationships and with a classification for their nature.
|
2 |
Modelling the instrumental value of software requirementsEllis-Braithwaite, Richard January 2015 (has links)
Numerous studies have concluded that roughly half of all implemented software requirements are never or rarely used in practice, and that failure to realise expected benefits is a major cause of software project failure. This thesis presents an exploration of these concepts, claims, and causes. It evaluates the literature s proposed solutions to them, and then presents a unified framework that covers additional concerns not previously considered. The value of a requirement is assessed often during the requirements engineering (RE) process, e.g., in requirement prioritisation, release planning, and trade-off analysis. In order to support these activities, and hence to support the decisions that lead to the aforementioned waste, this thesis proposes a framework built on the modelling languages of Goal Oriented Requirements Engineering (GORE), and on the principles of Value Based Software Engineering (VBSE). The framework guides the elicitation of a requirement s value using philosophy and business theory, and aims to quantitatively model chains of instrumental value that are expected to be generated for a system s stakeholders by a proposed software capability. The framework enriches the description of the individual links comprising these chains with descriptions of probabilistic degrees of causation, non-linear dose-response and utility functions, and credibility and confidence. A software tool to support the framework s implementation is presented, employing novel features such as automated visualisation, and information retrieval and machine learning (recommendation system) techniques. These software capabilities provide more than just usability improvements to the framework. For example, they enable visual comprehension of the implications of what-if? questions, and enable re-use of previous models in order to suggest modifications to a project s requirements set, and reduce uncertainty in its value propositions. Two case studies in real-world industry contexts are presented, which explore the problem and the viability of the proposed framework for alleviating it. The thesis research questions are answered by various methods, including practitioner surveys, interviews, expert opinion, real-world examples and proofs of concept, as well as less-common methods such as natural language processing analysis of real requirements specifications (e.g., using TF-IDF to measure the proportion of software requirement traceability links that do not describe the requirement s value or problem-to-be-solved). The thesis found that in general, there is a disconnect between the state of best practice as proposed by the literature, and current industry practice in requirements engineering. The surveyed practitioners supported the notion that the aforementioned value realisation problems do exist in current practice, that they would be treatable by better requirements engineering practice, and that this thesis proposed framework would be useful and usable in projects whose complexity warrants the overhead of requirements modelling (e.g., for projects with many stakeholders, competing desires, or having high costs of deploying incorrect increments of software functionality).
|
3 |
Activity-based Process Integration Framework to Improve User Satisfaction and Decision Support in HealthcareBaslyman, Malak 12 September 2018 (has links)
Requirements Engineering (RE) approaches are widely used in several domains such as telecommunications systems, information systems, and even regulatory compliance. However, they are rarely applied in healthcare beyond requirements elicitation. Healthcare is a multidisciplinary environment in which clinical processes are often performed across multiple units. Introducing a new Information Technology (IT) system or a new process in such an environment is a very challenging task, especially in the absence of recognized RE practices. Currently, many IT systems are not welcomed by caregivers and are considered to be failures because they change what caregivers are familiar with and bring new tasks that often consume additional time.
This thesis introduces a new RE-based approach aiming to evaluate and estimate the potential impact of new system integrations on current practices, organizational goals,and user satisfaction using goal modelling and process modelling techniques. This approach is validated with two case studies conducted in real hospitals and a usability study involving healthcare practitioners. The contributions of the thesis are:
• Major: a novel Activity-based Process Integration (AbPI) framework that enables the integration of a new process into existing practices incrementally, in a way that permits continuous analysis and evaluation. AbPI also provides several alternatives to a given integration to ensure effective flowing and minimal disturbance to current practices. AbPI has a Goal Integration Method to integrate new goals, an Integration Method to integrate new processes, and an Alternative Evaluation Method exploiting multi-criteria decision-making algorithms to select among strategies.
The modelling concepts of AbPI are supported by a profile of the User Requirements Notation augmented with a new distance-based goal-oriented approach to alternative selection and a new data-quality-driven algorithm for the propagation of confidence levels in goal models.
• Minor: a usability study of AbPI to investigate the usefulness of the framework in a healthcare context. This usability study is part of the validation and is also a minor contribution due to: 1) the lack of usability studies when proposing requirements engineering frameworks, and 2) an intent to discover the potential usefulness of the framework in a context where recognized RE practices are seldom used.
|
4 |
Combining Business Intelligence, Indicators, and the User Requirements Notation for Performance MonitoringJohari Shirazi, Iman 26 November 2012 (has links)
Organizations use Business Intelligence (BI) systems to monitor how well they are meeting
their goals and objectives. Yet, very often BI systems do not include clear models of
the organization’s goals or of how to measure whether they are satisfied or not. Several
researchers now attempt to integrate goal models into BI systems, but there are still major
challenges related to how to get access to the BI data to populate the part of the goal
model (often indicators) used to assess goal satisfaction.
This thesis explores a new approach to integrate BI systems with goal models. In
particular, it explores the integration of IBM Cognos Business Intelligence, a leading BI
tool, with an Eclipse-based goal modeling tool named jUCMNav. jUCMNav is an open
source graphical editor for the User Requirements Notation (URN), which includes the
Use Case Map notation for scenarios and processes and the Goal-oriented Requirement
Language for business objectives. URN was recently extended with the concept of Key
Performance Indicator (KPI) to enable performance assessment and monitoring of business
processes. In jUCMNav, KPIs are currently calculated or modified manually. The
new integration proposed in this thesis maps these KPIs to report elements that are generated
automatically by Cognos based on the model defined in jUCMNav at runtime, with
minimum effort. We are using IBM Cognos Mashup Service, which includes web services
that enable the retrieval of report elements at the most granular level. This transformation
provides managers and analysts with useful goal-oriented and process-oriented
monitoring views fed by just-in-time BI information. This new solution also automates
retrieving data from Cognos servers, which helps reducing the high costs usually caused
by the amount of manual work required otherwise.
The novel approach presented in this thesis avoids manual report generation and
minimizes any contract with respect to the location of manually created reports, hence
leading to better usability and performance. The approach and its tool support are illustrated
with an ongoing example, validated with a case study, and verified through testing.
|
5 |
Combining Business Intelligence, Indicators, and the User Requirements Notation for Performance MonitoringJohari Shirazi, Iman 26 November 2012 (has links)
Organizations use Business Intelligence (BI) systems to monitor how well they are meeting
their goals and objectives. Yet, very often BI systems do not include clear models of
the organization’s goals or of how to measure whether they are satisfied or not. Several
researchers now attempt to integrate goal models into BI systems, but there are still major
challenges related to how to get access to the BI data to populate the part of the goal
model (often indicators) used to assess goal satisfaction.
This thesis explores a new approach to integrate BI systems with goal models. In
particular, it explores the integration of IBM Cognos Business Intelligence, a leading BI
tool, with an Eclipse-based goal modeling tool named jUCMNav. jUCMNav is an open
source graphical editor for the User Requirements Notation (URN), which includes the
Use Case Map notation for scenarios and processes and the Goal-oriented Requirement
Language for business objectives. URN was recently extended with the concept of Key
Performance Indicator (KPI) to enable performance assessment and monitoring of business
processes. In jUCMNav, KPIs are currently calculated or modified manually. The
new integration proposed in this thesis maps these KPIs to report elements that are generated
automatically by Cognos based on the model defined in jUCMNav at runtime, with
minimum effort. We are using IBM Cognos Mashup Service, which includes web services
that enable the retrieval of report elements at the most granular level. This transformation
provides managers and analysts with useful goal-oriented and process-oriented
monitoring views fed by just-in-time BI information. This new solution also automates
retrieving data from Cognos servers, which helps reducing the high costs usually caused
by the amount of manual work required otherwise.
The novel approach presented in this thesis avoids manual report generation and
minimizes any contract with respect to the location of manually created reports, hence
leading to better usability and performance. The approach and its tool support are illustrated
with an ongoing example, validated with a case study, and verified through testing.
|
6 |
Combining Business Intelligence, Indicators, and the User Requirements Notation for Performance MonitoringJohari Shirazi, Iman January 2012 (has links)
Organizations use Business Intelligence (BI) systems to monitor how well they are meeting
their goals and objectives. Yet, very often BI systems do not include clear models of
the organization’s goals or of how to measure whether they are satisfied or not. Several
researchers now attempt to integrate goal models into BI systems, but there are still major
challenges related to how to get access to the BI data to populate the part of the goal
model (often indicators) used to assess goal satisfaction.
This thesis explores a new approach to integrate BI systems with goal models. In
particular, it explores the integration of IBM Cognos Business Intelligence, a leading BI
tool, with an Eclipse-based goal modeling tool named jUCMNav. jUCMNav is an open
source graphical editor for the User Requirements Notation (URN), which includes the
Use Case Map notation for scenarios and processes and the Goal-oriented Requirement
Language for business objectives. URN was recently extended with the concept of Key
Performance Indicator (KPI) to enable performance assessment and monitoring of business
processes. In jUCMNav, KPIs are currently calculated or modified manually. The
new integration proposed in this thesis maps these KPIs to report elements that are generated
automatically by Cognos based on the model defined in jUCMNav at runtime, with
minimum effort. We are using IBM Cognos Mashup Service, which includes web services
that enable the retrieval of report elements at the most granular level. This transformation
provides managers and analysts with useful goal-oriented and process-oriented
monitoring views fed by just-in-time BI information. This new solution also automates
retrieving data from Cognos servers, which helps reducing the high costs usually caused
by the amount of manual work required otherwise.
The novel approach presented in this thesis avoids manual report generation and
minimizes any contract with respect to the location of manually created reports, hence
leading to better usability and performance. The approach and its tool support are illustrated
with an ongoing example, validated with a case study, and verified through testing.
|
7 |
TraceME: Traceability-based Method for Conceptual Model EvolutionRuiz Carmona, Luz Marcela 23 May 2016 (has links)
[EN] Renewing software systems is one of the most cost-effective ways to protect software investment, which saves time, money and ensures uninterrupted access to technical support and product upgrades. There are several motivations to promote investment and scientific effort for specifying systems by means of conceptual models and supporting its evolution. In order to contribute to the requirements engineering field with automated software production methods, we design TraceME to cover the spectrum of activities from requirements to code focusing on organisational evolution. In this sense, the spectrum of activities involves various information system perspectives of analysis that need to be integrated. In this complex setting, traceability and conceptual models are key concepts. Mechanisms to trace software specifications from requirements to code are important to justify evolution processes; versions of information systems should be traced in order to get the connection between old and new specifications. Moreover, it is necessary to find mechanisms to facilitate change specifications, measurement, and interpretation.
To design this thesis we follow Design Science by Roel Wieringa. Design Science gives us the hints on how to conduct the research, be rigorous, and put in practice scientific rules. Besides Design Science has been a key factor for structuring our research, we acknowledge the application of this framework since it has helps us to report clearly our findings.
We build TraceME by making a method engineering effort, which shapes its fragmented nature in chunks. The architecture of TraceME opens a wide window of opportunities for its application in real world situations. To facilitate industrial adoption, we develop open source tools to support the implementation of the TraceME chunks. For example, one case study and one action-research protocols have been executed in two different organisations in Spain.
The validation of TraceME has taken place in laboratory demonstrations, controlled experiments, action research and case study experiences in industry. Thanks to the validations various lessons learnt have been gathered and greatly influenced the maturity of the method. For example: the importance to consider end-users' perceptions for discovering needs to mitigate, and the significance to get knowledge from the application of TraceME in different contexts. The evidences from the validations demonstrate that TraceME is feasible to be applied to support evolution projects. In addition, future research is needed for promoting the implementation of TraceME. We envision short term and future-term work that motivate us to tackle the challenge to support evolution projects. / [ES] La evolución de sistemas software es una de las actividades mas importantes que permiten minimizar el tiempo de puesta en producción de actualizaciones y nuevos desarrollos, reducir los costos que implica desarrollar una aplicación desde cero, y además asegura el acceso ininterrumpido de servicios.
Existen variadas motivaciones para promover la investigación y desarrollo de soluciones para especificar y evolucionar sistemas de información mediante modelos conceptuales. Para contribuir al campo de la ingeniería de requisitos con métodos automáticos de producción de software, hemos diseñado el método TraceME para cubrir el espectro de actividades desde requisitos a código con un enfoque de evolución organizacional. De este modo, el espectro de actividades involucra diferentes perspectivas de análisis de sistemas de información que necesitan ser integradas. En este escenario tan complejo, la trazabilidad y los modelos conceptuales son conceptos clave. Es necesario disponer de mecanismos para trazar especificaciones de software desde requisitos a código con el fin de justificar procesos de evolución. Las versiones de los sistemas de información deben ser trazables con el fin de establecer la conexión entre especificaciones obsoletas y actuales. Adicionalmente, es necesario encontrar mecanismos para facilitar la especificación del cambio, su medición e interpretación.
Para diseñar esta tesis hemos seguido el marco de Design Science de Roel Wieringa. Design Science nos ha proporcionado las claves para conducir esta investigación, ser rigurosos y poner en práctica reglas científicas. Además de que Design Science ha sido un factor clave para estructurar nuestra investigación, reconocemos que la aplicación de este marco nos ha ayudado a reportar claramente nuestros hallazgos.
Hemos aplicado ingeniería de métodos para diseñar y construir TraceME. Gracias a esto, la naturaleza de TraceME es conformada mediante fragmentos de método. La arquitectura de TraceME abre una amplia ventana de oportunidades para su aplicación en situaciones de la vida real. Para facilitar la adopción industrial de TraceME, hemos desarrollado herramientas de software libre para dar soporte a los fragmentos de TraceME. Por ejemplo, un caso de estudio y una experiencia de action research han sido ejecutadas en dos organizaciones en España.
La validación de TraceME ha sido llevada a cabo mediante demostraciones de laboratorio, experimentos controlados, un caso de estudio y una experiencia de action research en industria. Como resultado, TraceME ha sido mejorado considerablemente; además hemos descubierto investigaciones a realizar a corto, mediano y largo plazo con el fin de implementar TraceME en la industria. Las evidencias obtenidas como resultado de las validaciones demuestra la factibilidad de TraceME para ser aplicado en proyectos de evolución organizacional. El trabajo futuro nos motiva a afrontar los retos que conlleva el soporte de proyectos de evolución de sistemas de información. / [CA] L'evolució dels sistemes programari és una de les activitats més importants que permeten minimitzar el temps de posada en producció d'actualitzacions i nous desenvolupaments, reduir els costos que involucra desenvolupar una aplicació des de cero, a més d' assegurar l'accés ininterromput de serveis.
Existixen diverses motivacions per promoure la investigació i desenvolupament de solucions per a especificar i evolucionar sistemes de informació mitjançant models conceptuals. Per tal de contribuir al camp de l'enginyeria de requisits amb mètodes automàtics de producció de programari, hem dissenyat el mètode TraceME per cobrir l'espectre d'activitats des de requisits a codi en un enfocament d'evolució organitzacional. Així, l'espectre d'activitats involucra diferents perspectives d'anàlisi de sistemes d'informació que necessiten ser integrades. En aquest escenari tan complex, la traçabilitat i els models conceptuals són conceptes clau. És necessari disposar de mecanismes per traçar especificacions de programari des de requisits a codi amb la fi de justificar processos d'evolució. Les versions dels sistemes d'informació deuen ser traçables amb la fi d'establir la connexió entre especificacions obsoletes i actuals. Addicionalment, és necessari trobar mecanismes per facilitar l'especificació del canvi, la seua mesura i interpretació.
Per tal de dissenyar aquesta tesi, hem seguit el marc de Design Science de Roel Wieringa. Design Science ens ha proporcionat les claus per conduir aquesta investigació, ser rigorosos i posar en pràctica regles científiques. A més a més, Design Science ha sigut un factor clau per estructurar la nostra investigació, reconeixem que l'aplicació de aquest marc ens a ajudat a reportar clarament els nostres resultats.
Hem aplicat enginyeria de mètodes per dissenyar i construir TraceME. Gràcies a açò, la natura de TraceME es conforma mitjançant fragments de mètodes. L'arquitectura de TraceME obri una ampla finestra d'oportunitats per a la seua aplicació en situacions de la vida real. Per facilitar l'adopció industrial de TraceME, hem desenvolupat ferramentes de programari lliure per tal de donar suport als fragments de TraceME. Per exemple, un cas d'estudi i una experiència de action research han sigut executades en dos organitzacions a Espanya.
La validació de TraceME ha sigut portada a cap mitjançant demostracions de laboratori, experiments controlats , un cas d'estudi i una experiència de action research en l'industria. Com a resultat, TraceME ha sigut millorada considerablement; a més a més, hem descobert investigacions a realitzar a curt, mig i llarg termini amb la fi d'implementar TraceME a l'industria. Les evidències obtingudes com a resultat de les validacions, demostren la factibilitat de TraceME per ser aplicat en projectes d'evolució organitzacional. El treball futur presenta nous reptes que ens motiven a afrontar el suport de projectes d'evolució de sistemes d'informació. / Ruiz Carmona, LM. (2016). TraceME: Traceability-based Method for Conceptual Model Evolution [Tesis doctoral]. Universitat Politècnica de València. https://doi.org/10.4995/Thesis/10251/64553
|
Page generated in 0.0989 seconds