UML Process Definition

Productive software development is based on effective practice, which can be best facilitated by a understandable and documented process. Process documentation is required by may assessment guidelines like CMMI and ISO 9000.

While developing process documentation as a text document is a costly major exercise, application of UML reduces the cost of process definition dramatically and produces the definition that is easy to read, follow and modify.

Development Process Elements

The following elements should be defined:

• Process Stakeholders: key roles that provide expectations in relation to project outcome and documentation. In addition to the key clients of the project, the list of Stakeholders may include roles like maintenance manager, Poject Office etc;
• Process Expectations include documented processes, management and project approval procedures, documentation requirements, as well as more general SDLC criteria;
• Project Roles, with general definitions and skillsets ;
• Activities associated with the roles;
• Workflows, sequences of activities delivering results of value;
• Artefacts: documents, models, code, test scripts and other file types that are produced through a project;
• Model Structure, more detailed definition of model artefacts.

Development Process inputs:

• Enterprise rules, regulations and procedures;
• Enterprise strategy and IT business requirements
• Management approach and methodology;
• Existing staff skills mentality and expertise;
• Projects types, sizes and technology.