Java News from Friday, January 9, 2009

Ascom Deutschland GmbH has submitted JSR-328: Change Management API to the Java Community Process (JCP). According to the JSR,

Change Management (CM) ensures that changes are recorded, evaluated, approved, authorized, prioritized, planned, tested, implemented, documented and reviewed in a controlled manner. The purpose of the Change Management process is to ensure that standardized methods are used for the efficient and prompt handling of all changes; that all changes are recorded in the Configuration Management System and that overall business risk is optimized. Change management delivers, to the business, reduced errors in new or changed services and faster, more accurate implementation of changes; it allows restricted funds and resources to be focused on those changes to achieve greatest benefit to the business. This JSR proposes an API Specification for Change Management systems to operate request for changes following the IT Infrastructure Library (ITIL) "Change Management" recommendations and principles (as described in Chapter 8: Change Management, of the "Service Support" document).

The data model for this API is defined around the Request For Change (RFC) entity. The main interface focuses on creating, retrieving, updating, approving and removing RFC. This JSR is defined and developed on top the OSS Common API (JSR 144). It will use or extends the Core business Entities (CBE) following the OSS Design Guidelines and format (documentation, specification, Reference Implementation and TCK bundle format).

Comments are due by January 20.

On a side note, it feels like new submissions ot the JCP have really slowed down of late. This is the first one since October. That's probably a good thing.