WISEMP workshop Friday, 23 April 2010 Montréal, Québec, Canada   CP2010 Program (PDF)

1100 rue Notre-Dame Ouest (at Peel) Directions     Hotels

Industrial software evolution and maintenance has become one of the most complex, crucial and costly disciplines within software engineering. Maintainers face new technological, methodological and organizational challenges which they must tackle in an effective and efficient manner.

This first WISEMP workshop is focused on discussion of software evolution and maintenance processes among software maintenance process researchers and practitioners in industry, educators, standards development organizations (SDO), and regulatory organizations. The objective is to share ideas, expertise and knowledge of professional strength strategies pivotal for succeeding in a rapidly changing technical, economic, and social environment.

WISEMP Program

Mira Kajko-Mattsson
An overview of Software Maintenance

This presentation will cover an overview of the software maintenance domain to start the workshop by establishing a common ground of terminology and concepts for discussions.

Marc Prunier
Experimenting design and implementation of an educational services management system based on ISO/IEC 20000 standard

Higher education European organizations are encouraged to implement quality management practices. Existing quality standards and frameworks do not capitalize an important set of best practices addressing educational services delivery. The ISO/IEC 20000 standard, elaborated from IT service management issues, is widening its field of application and may represent an interesting alternative. A specific approach needs to apprehend the particular nature of educational services, consider the systemic cooperating roles of educational system and learning system, and define ISO/IEC 20000 vocabulary and concepts adaptation to the domain. ISO/IEC 20000 may provide an answer to European Standard Guidelines compliance and improve educational services management. The current experimentation is expected to cast light on the complexity, practicality and effectiveness of the use of ISO/IEC 20000 in a first field of "non IT" services.

Philippe Galaup
Case Study of Grond Forces (French Army)

This presentation will cover the process improvement activities conducted in the French army by its software simulation software maintenance unit.

Alain April
A maintainer's nightmare

Software development is lighter and faster with Agile methods. In an era where new technology is pouring in the IT departments in greater number and at even greater speed isn't this a recipe for maintenance disaster? This presentation will present a ranking of maintenance problems as lived in our organizations and potential avenues for improvement.

Hongyu Pei Breivold
An Extended Quantitative Analysis Approach for Architecting Evolvable Software Systems

For long-lived systems, there is a need to address evolvability, i.e. a system's ability to easily accommodate changes, explicitly during the entire lifecycle. To improve the capability in being able to understand and analyze systematically software architecture evolution, we introduced in our earlier work a software evolvability model and a structured qualitative method for analyzing evolvability at the architectural level - the ARchitecture Evolvability Analysis (AREA) method. As architecture is influenced by system stakeholders representing different concerns and goals, the business and technical decisions that articulate the architecture tend to exhibit tradeoffs and need to be negotiated and resolved. To avoid intuitive choice of architectural solutions, we propose to extend the AREA method and strengthen its tradeoff analysis with explicit and quantitative treatment of stakeholders' prioritization of evolvability subcharacteristics and their preferences on design solutions. Finally, an example is used to illustrate the concept and applicability of the proposed approach.

Joris Van Geet
Reverse Engineering on the Mainframe : Presenting Lessons Learned from "in vivo" Research

There is no denying the dominance of mainframe systems in large-scale enterprise computing and --- while they are sometimes referred to as ``the dinosaurs of computing'' --- even they must adapt to the changing circumstances in their environment or are bound to be withdrawn from service. Unfortunately, current reverse- and reengineering techniques are mainly geared towards modern environments, languages and platforms. It remains to be seen whether successful techniques can be easily transferred to a mainframe context.

Joakim Snygg and Emil Hammargren
Mapping CM3: Emergency Problem Management on Emergency and Crisis Management within One Financial Company

To solve emergency software problems, organizations need guidance on how to efficiently manage them. This guidance, however, is available in only one process model today: CM3: Emergency Problem Management. In this paper, we study management of emergency software problems at Northern Finance. Our goal is to evaluate the CM3: Emergency Problem Management and provide feedback for its improvement. The most important feedback concerns the suggestions for extensions of CM3: Emergency Problem Management with a pre-alert phase and co-ordination of the management of emergency software problems with organization-wide crisis management.

Edgardo Palza
Implementing KPI with Open Source BI Software in an Academic Department

This paper proposes a model to construct and implement a set of Key Performance Indicators (KPI) to facilitate decision making and governance in academics units for universities. The model has been developed to improve the understanding, control and planning of academic activities based on historical measurement data. The entire project has made possible using Open Source Business Intelligence (BI) Software. We also propose a methodology, based on agile construction principles in order to design, model, load, transfer, process and report academic data into the model. The model has been developed, tested and is actually in use at Universidad Peruana Union (UpeU)

Ned Chapin
Governance Influence on Software Evolution and Software Maintenance

Information technology governance has been changing, and complying with those changes makes software maintenance and evolution more difficult. The root causes center around the preservation of data integrity. The consequences affect all phases of the software maintenance life cycle, but especially the analysis, design, and testing phases. Consequences of the causes also act as drivers for software evolution, because a start to satisfying the governance changes is an eight-step management process that may trigger software evolution action. Overall, the changes in information technology governance have placed increasing workload and skill demands on software maintenance personnel, and offer a challenging opportunity to management.

Aseel Hmood
A Methodology for Assessing Evolvability as a Quality Factor in Software Ecosystems

Software development and evolution are highly distributed processes that involve a multitude of supporting tools and resources. Knowledge relevant to these resources is typically dispersed over a wide range of artifacts, representation formats, and abstraction levels. In order to stay competitive, organizations are often required to assess and provide evidence that their software meets expected quality requirements. Similarly, the quality assessment of open-source or third-party components is a crucial factor in software development. In our research, we focus specifically on modeling and assessing evolvability as a quality factor. We introduce our OntEQAM methodology that supports the integration and semantic analysis of knowledge resources typically found in software ecosystems. We further illustrate how our OntEQAM methodology can be applied to support the automated analysis and assessment of different types of quality attributes related to the evolvability of software ecosystems.

Panel Discussions

An open discussion and question period on how academia should orient its work to support organizations in resolving software maintenance process problems and improvement efforts.

This workshop and the CP 2010 conference provide an opportunity for Computing Professionals to stretch their professional perspectives, learn what works now, and bring added value to themselves as professionals and their organizations. WISEMP will provide a forum for exchanging innovative concepts, ideas, applications, feedback and lessons learned.

Topics include:

• *Industrial lifecycle processes*
  • Software evolution and maintenance processes
  • Preventive maintenance
  • Predelivery process
  • Transition (handover) process
• *Evaluation and measurement processes*
  • Metrics and measurements of software evolution and maintenance
  • Evolution and maintenance dashboard
  • Testing and quality assurance
  • Productivity and benchmarking
  • Billing evolution and maintenance services
• *Management processes*
  • Planning activities and their effects
  • Production surveillance processes
  • Governance and contracts
  • Globalization aspects
  • SLA Management
• *Customer support*
  • Front-end support processes covering *Support Line 1* and *Support Line 2*
  • Improving software quality (reengineering, restructuring, refactoring, and modernization processes)
  • Managing both scheduled and unscheduled (emergency) corrective changes in the product
  • Customer satisfaction
  • Customer Profiles
• *Education and training*
  • Education and training of software engineers
  • Human resource management