Ontology-based domain modelling for consistent content change management

Ontology-based modelling of multi-formatted software application content is a challenging area in content management. When the number of software content unit is huge and in continuous process of change, content change management is important. The management of content in this context requires targeted access and manipulation methods. We present a novel approach to deal with model-driven content-centric information systems and access to their content. At the core of our approach is an ontology-based semantic annotation technique for diversely formatted content that can improve the accuracy of access and systems evolution. Domain ontologies represent domain-specific concepts and conform to metamodels. Different ontologies - from application domain ontologies to software ontologies - capture and model the different properties and perspectives on a software content unit. Interdependencies between domain ontologies, the artifacts and the content are captured through a trace model. The annotation traces are formalised and a graph-based system is selected for the representation of the annotation traces

Utilising ontology-based modelling for learning content management

Learning content management needs to support a variety of open, multi-format Web-based software applications. We propose multidimensional, model-based semantic annotation as a way to support the management of access to and change of learning content. We introduce an information architecture model as the central contribution that supports multi-layered learning content structures. We discuss interactive query access, but also change management for multi-layered learning content management. An ontology-enhanced traceability approach is the solution

Study of Different Aspects of Software Configuration Management

Software configuration management (SCM) is an important activity in the software engineering life cycle. Today, most of the software project teams understand the need for SCM to manage change to their software systems. Most of the companies use the software configuration management and it is essential during the process of software development as rules to control and manage the evolution of software systems. In the Software Engineering, the Software Configuration System (SCM) is used for the tracking & controlling the changes in the software. Since evolution and change is unavoidable in software systems configuration management is considered as an integral element of software development and activity maintenance. The SCM activities are change management system, version management, and then system construction and release management. This paper is the study of software configuration management, the change control, CM process, steps and tools of SCM. The purpose of this paper is to give an idea about software configuration management and how this influences the software development process

Change Management Support for Large Software Systems

This technical report consists of three related papers in the area of management of source code changes for large software systems. Infuse: A Toolfor Automatically Managing and Coordinating Source Changes in Large Systems presents Infuse, a software engineering environment that automatically panitions the source code files to be changed in order to limit the complexity of change propagation and negotiation of conflicting changes. Workspaces and Experimental Databases: Automated Support for Cooperation Among Programmers describes Infuse in more detail, focusing on the interactions between Infuse and source code modification tools. Smarter Recompilation presents an algorithm that could be used by Infuse or other software engineering environments to reduce recompilation costs after source code changes

BPM, Agile, and Virtualization Combine to Create Effective Solutions

The rate of change in business and government is accelerating. A number of techniques for addressing that change have emerged independently to provide for automated solutions in this environment. This paper will examine three of the most popular of these technologies-business process management, the agile software development movement, and infrastructure virtualization-to expose the commonalities in these approaches and how, when used together, their combined effect results in rapidly deployed, more successful solutions

A model of case implementation and an experience of unsuccessful case adoption

Computer-Aided Software Engineering (CASE) is a revolutionary technology that seeks to automate the software development process. Current literature reports on many successes of CASE adoption Despite of such successes, many organisations are experiencing difficulties in implementing CASE technology . Even many powerful CASE tools have become 'shelfware'. It is argued that the benefits of CASE are unlikely to be realised, unless it is introduced based on a sound implementation plan This article presents a conceptual model to introduce CASE technology within a MIS department Such a plan faciliiaus change in software culture and management practice and enables management to deal with confusion and skepticism prior to its occurrence. Furthermore, a case study is described that focuses on a CASE implementation that failed to achieve its purpose The reasons for the failure are critically examined and explained in the light of the model