< Previous | Next >

Concepts

This page describes the basic concepts that are required to complete this tutorial.

Method content provides step-by-step explanations describing how specific development goals are achieved independent of the placement of these steps within a development lifecycle. Method content is always separated from its application in processes.

There are four main types of method content elements:
  • Tasks
  • Roles
  • Work products, such as: artifact, deliverable, outcome
  • Guidance, such as: checklist, concept, example, guideline, estimation consideration, practice, report, reusable asset, roadmap, supporting material, template, term definition, tool mentor, white paper

A Process Engineer typically authors these elements, categorizes them, and defines the relationships between them. Processes are then constructed from these method elements by organizing them into semi-ordered sequences that are customized to specific types of projects.

One of the most powerful features provided by EPF Composer is the reliance on extensible method plug-ins. This mechanism allows extensive customization of generated content without directly changing the base content.

The base method content included with EPF Composer is protected from direct modification. Read-only method plug-ins are dimmed in the Library view indicating that they are locked.

You should always create new content in a method plug-in that you produce. This separates your content from the original content and allows you to update your own library with new releases without affecting the content that you have created in your own plug-ins.

Standard categories provide a means to categorize core method content in line with best practices for creating structured methods. To encourage good method structure, there are standard categories for grouping tasks into disciplines, work products into domains, roles into role sets, and tool-mentors into tools. Unlike custom categories, standard categories, by definition, are linked to a specific type of method content.

Method and process elements use two names: Name and Presentation name. It is a good practice to use file names that are all lowercase with no spaces and no special characters. The Name will be used as the name of the file which stores the element. We do this so that the name is valid on all operating systems and for integration with version control software. The name is shown in the Library view.

The presentation name is the name that is shown on published pages and in the configuration view. This name can contain any uppercase characters, spaces, and special symbols such as the trademark symbol.

In the Library view you can choose to display names or presentation names. You can switch the name display using the Show Presentation Names button in the library view toolbar.

< Previous | Next >