org.eclipse.epf.help.doc/html/methodcontent.html

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html
  PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html lang="en-us" xml:lang="en-us">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
<meta name="security" content="public" />
<meta name="Robots" content="index,follow" />
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
<meta name="DC.Type" content="concept" />
<meta name="DC.Title" content="Method Content" />
<meta name="DC.Relation" scheme="URI" content="methodcontentcategories.html#methodcontentcategories" />
<meta name="DC.Relation" scheme="URI" content="createmethodcontent.html#createmethodcontent" />
<meta name="DC.Relation" scheme="URI" content="createamethodplugin.html#createamethodplugin" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="creatingreusablemethodcontents" />
<meta name="DC.Language" content="en-us" />
<!-- 
    Copyright (c) 2005, 2006 IBM Corporation and others.
    All rights reserved. This program and the accompanying materials
    are made available under the terms of the Eclipse Public License v1.0
    which accompanies this distribution, and is available at
    http://www.eclipse.org/legal/epl-v10.html
    Contributors:
    IBM Corporation - initial implementation
-->
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
<title>Method Content</title>
</head>
<body id="creatingreusablemethodcontents"><a name="creatingreusablemethodcontents"><!-- --></a>

<h1 class="topictitle1">Method Content</h1>
<div><p>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. Processes take these method
elements and relate them into semi-ordered sequences that are customized to
specific types of projects.</p>
<p>Method content elements are:</p>
<ul><li><a href="task.html#task">Task</a></li>
<li><a href="role.html#role">Role</a></li>
<li><a href="workproduct.html#workproduct">Work Product</a></li>
<li><a href="guidance.html">Guidance</a></li>
</ul>
<p>A Process Engineer authors these elements, defines the relationships between
them, and then categorizes them. 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. Processes take these
method elements and relate them into semi-ordered sequences that are customized
to specific types of projects.</p>
<p>For example, a software development project that develops an application
from scratch performs development tasks such as "Develop Vision" or "Use Case
Design" similar to a project that extends an existing software system. However,
the two projects will perform the tasks at different points in time with a
different emphasis, i.e., they perform the steps of these tasks at different
points of time and perhaps apply individual variations and additions. </p>
<p>Method content elements are contained within method content packages which,
in turn, are contained within a Method plug-in. In order to separate your
own content from original OpenUP content, you should always create new
method content in a method plug-in that you produce. Creating method content
in a method plug-in of your own also allows you to update your own library
with new releases of the OpenUP library without affecting the content
that you have created in your own plug-ins.</p>
<p>See also:</p>
</div>
<div><div class="relconcepts"><strong>Related concepts</strong><br />
<div><a href="methodcontentcategories.html#methodcontentcategories">Method Content Categories</a></div>
</div>
<div class="reltasks"><strong>Related tasks</strong><br />
<div><a href="createmethodcontent.html#createmethodcontent">Create Method Content</a></div>
<div><a href="createamethodplugin.html#createamethodplugin">Create a Method Plug-in</a></div>
</div>
</div>
</body>
</html>