Judith Barrios

Model Driven Architectures for Enterprise Information Systems

Over the past decade, continuous challenges have been made to traditional business practices. At the same time, organisations have also experienced the effects of the integration and evolution of information and communication technologies (ICT). The Enterprise Information Systems (EIS) gained a new strategic support role as enabler of automation, monitoring, analysis and co- ordination of whole business functioning, a central role in the evolution of today organisations. These rapid changing situations originate a critical need for realistic representations -called business models- of what are the current or future business situations or what should be changed as well as its potential organisational impacts. This paper characterises the strong relationship existing between Business Models and EIS Architectures in a changing environment. Our main contribution is a set of roadmaps, which highlight the relationships between business process models and the requirements of EIS. These roadmaps provide guidance during the business modelling and the information system (IS) modelling processes.

Developing Instructional Web Sites – A Software Engineering Approach

This paper focuses on the application of software engineering practices to the development of instructional web sites. The development of a web site, to support a distance or campus-based online course, is a very complex process that involves many instructional and technical aspects, including the instructional purpose of the course, its content, its structure, its interface, and its teaching–learning activities. The use of a method is essential for dealing with the complexity of this process. We describe, in this paper, a software engineering method that helps course designers and teachers to develop high quality instructional web sites. The design of the method was based on the integration of well-known principles, concepts and process models borrowed from instructional design, method engineering, and object-oriented software engineering. The method addresses the managerial processes required to plan, organize, and control the project, as well as the instructional and technical activities involved in the development of high quality course sites.

Une méthode pour la définition de l'impact organisationnel du changement

RESUME. La variete et la continuite des changements auxquels les organisations modernes sont soumises, ont donne naissance a de multiples approches de gestion du changement organisationnel. Ces approches proposent des directives generales pour gerer le processus de changement mais ne definissent pas de formalismes permettant de representer le processus de changement, la vision du changement, l’impact sur l’organisation et/ou le(s) resultat(s) possible(s) du processus de changement. Dans cet article, nous proposons une methode pour la definition de l’impact organisationnel du changement. Cette methode se caracterise principalement par (i) l’utilisation de modeles pour representer l’organisation, ses etats actuel et futur et les scenarios alternatifs d’impact, (ii) le raisonnement au niveau intentionnel et (iii) la modelisation de l’impact organisationnel du changement comme un processus systematique et guide. ABSTRACT. Most of the current change management approaches consider the need of establishing an organisational view of change and reducing its negative impact over the organisation. These approaches prescribe a set of guidelines to help managers during change process but they do not specify a formal representation of the change process, neither for representing the organisational view of change, the impact of change over the organisation or the potential result of the change process. This paper presents a method for modelling the organisational impact of change. This method is characterised by: (i) the use of models to represent the organisation, its actual and future states and the scenarios for change; (ii) the intentional reasoning about the change problem and (iii) the proposition of a systematic and guided process for modelling the organisational impact of change.

A process model based on Enterprise Architecture for ICT management

The successful application of Information and Communication Technologies (ICT) in an enterprise depends on the implanted processes for managing such technologies. We consider that the use of the Enterprise Architecture (EA) concept for organizing these technologies into a framework would allow us to achieve a better ICT - business alignment. This article presents a process model for the ICT Management that is oriented to medium and small enterprises. The main difference between the proposed model and the others found in domains literature is that our model places EA concept at the center of the organization of ICT management activities. It provides a better definition, organization and comprehension of the essential business activities. Consequently, our model would facilitate the restructuring of organizational units responsible for the ICT management. The described model is used in several Venezuelan enterprises as a referential framework in order to improve their current ICT management processes. This experience would serve to refine and optimize its application in other Latin-American enterprises.

Visual Representation of the TOGAF Requirements Management Process

TOGAF Architecture Development Method (ADM) covers different aspects of Enterprise Architecture (EA) management as well as it provides textual guidelines to adapt and perform EA processes including the requirements management (RM) process. We observed that adopting ADM following these guidelines is an intricate task because the effort required to define a sequential interaction between related activities is meticulous and hard. During a real case experience we have formalized the ADM-TOGAF Requirements Management textual guidelines with the Business Process Model and Notation (BPMN) to facilitate its comprehension and usage. Afterwards, the usefulness of the proposed process models has been qualified with a group of engineering and master students.

Integrating the methodological frameworks WATCH and SCRUM: A method engineering approach

This paper focuses on the integration of two software development frameworks: Blue WATCH y SCRUM. SCRUM is a well known agile framework for software development; meanwhile, Blue WATCH is a balanced (agile + disciplined) methodological framework for enterprise application development. The first one is combined with concepts derived from the second one. The emphasis of the paper is on the process of integration and its result: the integrated framework. The combined framework that emerges from the integration process provides a better description, not only of the project management processes, but also of the technical and support processes which are proper of the software development endeavor. The proposed framework is expected to provide a better guidance to software development teams, since it mixes managerial and technical processes into a unique framework.