Track A: QA Management / Track F: Configuration management


Eric Mariacher

CURRÍCULUM VITAE

Eric Mariacher has held various positions in embedded software development, coder, architect, project manager at IBM and now functional manager for wireless keyboards and receivers at Logitech. These projects are of different sizes beginning with 8Kbytes of code running in 8bits microcontrollers coded by one programmer to projects requiring tens of developers, several megabytes of code and thousands of files on 32bits microcontrollers and PC computers.

Eric Mariacher main centers of interest are to set-up the right environment for software developers to deliver products, and also to give management the best visibility on software development process from requirement phase to field support phase. Setting up the right software development often requires reengineering software development processes. Eric Mariacher enjoys driving these software development processes reengineering measured following the CMMI best practices.


ABSTRACT

Designing Change Request Workflows (Track A)

"Modern" software development companies use a change management tool. Configuration Management is one CMMI area. This paper deals with aspects of CM-SP2.1 "Track Change Requests" and CM-GP2.2 "Plan the Process".

There are two kinds of possible change requests in a software: bug correction and feature implementation. Most of change management tools offer the possibility to implement a change request workflow to get visibility on the current status of the change request. In this article, simple to complex bug or feature development worflows will be built, based on answers given to a short list of questions and concerns.



5 Steps Of Configuration Management Functionalities (Track F)

Now more than ever, companies want to faster deliver better and cheaper products. Last years, Some Industry best practices have started to emerge to help companies to achieve these goals by improving processes in their organization. Among others, CMMI is a recognized industry best practice. An important CMMI process area specific to software development projects is Configuration Management. Configuration Management has 2 main aspects, each having their own dedicated tools:

1. Source files and release configuration management.
2. Change request management affecting file and release management.

This technical paper describes different Configuration Management functionality steps and their ability to address series of Configuration Management related questions. It will be shown that it is not tools functionalities themselves that make the difference between Configuration Management functionality steps but the level of integration between those 2 kinds of tools.

Back to the Programme