No description available.

Today&rsquo / s Computer Aided Software Engineering (CASE) technology covers nearly all activities in software development ranging from requirement analysis to deployment.Organizations are evaluating CASE tool solutions to automate or ease their processes. While reducing human errors, these tools also increase control, visibility and auditability of the processes. However, to achieve these benefits, the right tool or tools should be selected for usage in the intended processes. This is not an easy task when the vast number of tools in the market is considered. Failure to select the right tool may impede project&rsquo / s progress besides causing economic loss. In this thesis study, a methodology is proposed for CASE tool evaluation and selection among various candidates and the points that separate this work from similar studies in the literature are explained. Moreover, the methodology is performed on a case study.

<p>This dissertation concerns the application of a method for developing context dependent CASE-tool evaluation frameworks. Evaluation of CASE-tools prior to adoption is an important but complex issue; there are a number of reports in the literature of the unsuccessful adoption of CASE-tools. The reason for this is that the tools have often failed in meeting contextual expectations. The genuine interest and willingness among organisational stakeholder to participate in the study indicate that evaluation of CASE-tools is indeed a relevant problem, for which method support is scarce.</p><p>To overcome these problems, a systematic approach to pre-evaluation has been suggested, in which contextual demands and expectations are elucidated before evaluating technology support.</p><p>The proposed method has been successfully applied in a field study. This dissertation contains a report and reflections on its use in a specific organisational context. The application process rendered an evaluation framework, which accounts for demands and expectations covering the entire information systems development life cycle relevant to the given context.</p><p>The method user found that method transfer was indeed feasible, both from method description to the analyst and further from the analyst to the organisational context. Also, since the span of the evaluation framework and the organisation to which the method was applied is considered to be large, this indicates that the method scales appropriately for large organisations.</p>

This dissertation concerns the application of a method for developing context dependent CASE-tool evaluation frameworks. Evaluation of CASE-tools prior to adoption is an important but complex issue; there are a number of reports in the literature of the unsuccessful adoption of CASE-tools. The reason for this is that the tools have often failed in meeting contextual expectations. The genuine interest and willingness among organisational stakeholder to participate in the study indicate that evaluation of CASE-tools is indeed a relevant problem, for which method support is scarce. To overcome these problems, a systematic approach to pre-evaluation has been suggested, in which contextual demands and expectations are elucidated before evaluating technology support. The proposed method has been successfully applied in a field study. This dissertation contains a report and reflections on its use in a specific organisational context. The application process rendered an evaluation framework, which accounts for demands and expectations covering the entire information systems development life cycle relevant to the given context. The method user found that method transfer was indeed feasible, both from method description to the analyst and further from the analyst to the organisational context. Also, since the span of the evaluation framework and the organisation to which the method was applied is considered to be large, this indicates that the method scales appropriately for large organisations.

My research is about monitoring the software development process to assess Capability maturity level. Capability Maturity Model (CMM) was developed to improve the software process based on subjective assessment by teams of experts. We propose an objective CMM assessment, which replaces expensive and time-consuming human effort by a knowledge-based system. Compared to Subjective CMM assessment, Objective CMM assessment can be less expensive, takes less time, and is easy to estimate the software development environment maturity. The accuracy of Objective CMM assessment can be the same as Subjective CMM assessment if enough activities are represented as objective activities. For example, if subjective activities total 80 % and objective activities total 20 %, then the accuracy of Objective CMM assessment is not reliable. It would be reliable if the objective activity is increased up to 80% from 20%. This dissertation presents how to change from Subjective CMM assessment to Objective CMM assessment, and we will prove that Objective CMM Assessment is effective.

In this master thesis the advanced design methodology is presented by which information systems requirements represented with precise UML models are transformed to project. The first section describes a research of five existing MDA tools comparison according to evaluation criteria. This criteria covers model to model and model to code transformations approach, platform of generated code and integration with UML CASE tools abilities. For requirements model transformation to design, plug-in for CASE tool MagicDraw is created according MDA standards. Model transformation plug-in takes system requirement model as input and generates design model. In this way it is possible to implement design methods that have explicit design rules. Created plug-in requirements, functional specification and architecture described in Project section. The investigation section describes investigation of the developed plug-in. In this section were investigate the working efficiency of designer increasing and the quality of design models ensuring with create MagicDraw plug-in.

Este trabalho propõe um modelo de identificação e análise de impactos provenientes da adoção de ferramentas CASE (Computer Aided Software Engineering) interativas baseado no padrão IEEE 1175.2 Práticas Recomendadas para Interconexão de Ferramentas CASE com foco na produtividade e na qualidade do processo de desenvolvimento de software nas organizações. Os impactos são analisados considerando as funções e características da ferramenta CASE e as ações gerenciais necessárias para a adoção da ferramenta. O modelo proposto é aplicado em um caso real de implantação de ferramentas CASE em uma instituição financeira brasileira para verificar na prática os impactos causados com a implantação. / This work proposes a model for impacts identification and analysis of adoption of interactive CASE tools (Computer Aided Software Engineering) based on the standard IEEE 1175.2 - Practice for CASE Tool InterconnectionCharacterization of Interconnections focused in software process development productivity and quality in organizations. The impacts are analyzed considering the CASE tool functions and features and the management actions necessary for the tool adoption. The proposed model is applied in a real CASE tool deployment in a brazilian financial institution to verify in practice the deployment impacts.

Este trabalho propõe um modelo de identificação e análise de impactos provenientes da adoção de ferramentas CASE (Computer Aided Software Engineering) interativas baseado no padrão IEEE 1175.2 Práticas Recomendadas para Interconexão de Ferramentas CASE com foco na produtividade e na qualidade do processo de desenvolvimento de software nas organizações. Os impactos são analisados considerando as funções e características da ferramenta CASE e as ações gerenciais necessárias para a adoção da ferramenta. O modelo proposto é aplicado em um caso real de implantação de ferramentas CASE em uma instituição financeira brasileira para verificar na prática os impactos causados com a implantação. / This work proposes a model for impacts identification and analysis of adoption of interactive CASE tools (Computer Aided Software Engineering) based on the standard IEEE 1175.2 - Practice for CASE Tool InterconnectionCharacterization of Interconnections focused in software process development productivity and quality in organizations. The impacts are analyzed considering the CASE tool functions and features and the management actions necessary for the tool adoption. The proposed model is applied in a real CASE tool deployment in a brazilian financial institution to verify in practice the deployment impacts.

One of the main current research activities in Software engineering is concerned about modelling the development process of huge softwares in order to bring some help to the engineer to design and maintain an application. In general, every design process is seen as rational application of transformation operators to one or more products (mainly specifications) in order to produce new products that satisfy to some given criteria. This modelling mainly allows a methodological guidance. Indeed, at each step of the process, the set of pertinent activities and types of products are proposed to the designer, without any other. This guidance may possibly be reinforced with some help. Furthermore, this modelling allows to document the process with its history, ie with a representation of performed actvities. This history is itself the basis of maintenance activities. Two examples : a Replay function that allows, during a modification, to do (automatically or assisted) the same activities as during the design, and Reverse Engineering that allows to recover not only some technical and functional documentation of an application, but also a plausible history of its design. The thesis aims at elaborating a general model of design processes, applying it to database engineering and implementing it in the DB-MAIN CASE tool. It will be done in four phases : 1. elaboration of a model, a method specification language and a history representation 2. evaluation of this model with the specification of classical methods and case studies 3. methodological recommandation proposals for the elaboration of design methods 4. development and integration of some methodological control functions in the DB-MAIN CASE tool; this includes an extension of the repository, the definition of the interface of the methodological functions, the development of the methodological engine and the development of an history processor (analysis, replay,...)./Un des principaux sujets de recherche actuels dans le monde de l'ingénierie logicielle concerne la modélisation des processus de développement de grosses applications afin d'apporter de l'aide aux ingénieurs pour concevoir et maintenir leurs applications. En général, un processus de conception est vu comme l'application rationnelle d'opérateurs de transformation à un ou plusieurs produits (généralement des spécifications) pour obtenir de nouveaux produits qui satisfont une série de critères donnés. Cette modélisation permet principalement une aide méthodologique: à chaque étape du processus, seul l'ensemble des outils pertinents est mis à disposition du concepteur. Ce guidage peut être renforcé par des messages d'aide. Cette aide s'étend l'enregistrement de l'historique du processus, c'est-à-dire d'une représentation des actions entreprises. Cet historique peut lui-même être à la base d'activités de maintenance. Deux exemples: une fonction qui permet de rejouer, lors d'une modification, de manière automatique ou assistée, les mêmes actions que pendant la conception, et la rétro-ingénierie qui permet de recouvrer non seulement la documentation technique et fonctionnelle d'une application, mais aussi un historique plausible de la conception originelle. La thèse s'attache à élaborer un modèle général de processus de conception, à l'appliquer au monde des bases de données et à l'implémenter dans l'AGL DB-MAIN. Cela, en 4 phases: 1. Élaboration d'un modèle, d'un langage de spécification (MDL) et d'une représentation des historiques 2. Évaluation de ce modèle avec des méthodes de spécification classiques et études de cas 3. Propositions de recommandations méthodologiques pour l'élaboration de méthodes d'ingénierie 4. Développement et intégration de fonctions de contrôle méthodologique dans l'atelier DB-MAIN; ceci inclut l'extension du référentiel, la définition de l'interface homme-machine des fonctions méthodologiques et le développement du moteur méthodologique.

Today, unified modeling language (UML) has become a standard modeling language in object-oriented systems analysis and design. Specifying the business logic constraint with object constraint language (OCL) and transforming the specification into code has become a main trend in this area. This research presents a classification of OCL expressions to specify the attribute, operation and relationship constraint on Class diagram. A sample case and a CASE tool are used to test the usability (including the concepts, application, and advantages) of the proposed method. With this approach, the system developer can specify the constraints easily and transform them into code automatically and thereby enhance the efficiency and reusability of system development.