Hidden Adapter

The need for writing software packages that do not depend explicitly on the server code,and do not need to be modified,when new server interfaces arise,lead to the development of the hidden adapter pattern.We will show its workings,and give an example of how complete decoupling between depended-on and dependent code can be achieved using the hidden adapter pattern.

Code Organization and Configuration Management

Industry experts are increasingly focusing on team productivity on team productivity as the key to success,the base of the team effort is the four-fold structure of software in terms of logical organisation,physical organisation,managerial organisation,and dynamical structure.We describe the ideas put into action within the CMS software for organising software into sub-systems and packages,and to establish configuration management in a multiproject environment.We use a structure that allows to maximise the independence of soft ware development in individual areas,and at the same time emphasises the overwhelming importance of the interdependencies between the packages and components in the system.We comment on release procedures,and describe the inter-relationship between release,development,integration,and testing.

Software Process Improvement in CMS—Are we Different？

One of the most challenging issues faced in HEP in recent years is the question of how to capitalise on software development and maintenance experience in a continuous manner.To capitalise inour context means to evaluate and apply new technologies as they arise,and to further evolve technologies arlready widely in use,It also implies the definition and adoption of standards,while ensuring reproducibility and quality of results.The CMS process improvement effort is two-pronged.It aims at continuous improve ment of the ways we do Object Oriented software,as well as continuous improvement in the efficiency of the working enviuronment.In particular the use and creation of de-facto software process standards within CMS has proven to be key to our successful software process improvement program.We describe the successful CMS implementation of a software process improvement strategy,following ISO 15504 since three years.We give the current status of the most important processes families formally established in CMS,and provide the guidelines we followed both for tool development,and methodology establishment.

DEPUTY：Analysing Architectural Structures and Checking Style

The DepUty(dependencies utility)can be classified as a project and process management tool.The main goal of DepUty is to assist by means of source code analysis and graphical representation using UML,in understanding dependencies of sub-systems and packages in CMS object Oriented software,to understand architectureal structure,and to schedule code release in modularised integration.It also allows a new-comer to more easily understand the global structure, of CMS software,and to void circular dependencies up-front or re-factor the code,in case it was already too close to the edge of non-maintainability.We will discuss the various views DepUty provides to analyse package dependencies and illustrate both the metrics and style checking facilities it provides.

Re—usable Templates for Documenting the Elaboration and Architectural Design of the CMS Software

Modern standards and definitions of deliverables for software development are provided by by various standards like PSS-05,CMMI,ECSS,V,Rational Unified process or SPICE(ISO 15504),Modern document templates and the corresponding documents are based on atomic shells that cross-link,and can be subsequently assembled into a set of complete documents;views of the information in the shells.This makes the information easy to maintain,and enables selective views of the documentation.We will present a catalogue of document templates that has been developed in the context of the CMS CAFE forum,as well as their cross-linkage,using UML as the modelling language The templates allow for documenting the elaboration and architectural design phases of software development,They can be used as the basis for establishing and documenting architecture,while establishing trace-ability to use-cases,requirements,constraints,and important technological choices in a maintainable manner.