This section outlines the tasks a developer using Serena® Dimensions® CM typically does in the course of a day's work.
This workflow assumes that developers are working with projects. Working with streams differs in certain respects. For details, see Working with Streams. It also assumes that developers are not using Dimensions CM from within an integrated development environment (IDE). In that case, this workflow would vary slightly. For information on using Dimensions CM with IDEs, see the IDE User’s Guide.
NOTE This is a simple workflow intended to give you a sense of how Dimensions CM is commonly used. It does not explain all possible options and variations. Workflows in your organization will vary depending on your development practices, how the Dimensions CM process model is set up, role assignments, and other factors.
Review your Inboxes. As a developer, you'll typically start the day by checking your Inboxes for items, requests, and baselines that have been assigned to you.
For example, your Pending Request list might contain requests for defects or enhancement requests that have been assigned to you, and the items associated with them.
Related topics:
About Content Windows
Check out items, affected by a request. Once you've determined which items you're going to work on, you'll typically check out those items.
Depending on the process model in place, you might be required to relate the new item revision to a request in order to check the item out.
Related topics:
Checking Out an Item
Alternatively, if you just need to make a quick change, you can edit the item instead of checking it out. Editing and saving an item does the equivalent of checking it out and checking it back in, saving several steps along the way.
Related topics:
About Editing Items
Editing an Item
If you are continuing with work from a previous session, and if your process model allows it, you may check out or edit items using the same revision provided the item revision is at an initial lifecycle state.
Related topics:
Revising an Item
Create items as necessary. During the course of your work, you may need to create new items.
Depending on the process model in place, you might be required to relate the new item to a request in order to create it.
Related topics:
About Creating New Items
Creating a New Item
Check items in. Once you're finished making changes, you'll check the items back in and enter comments to document what you did.
You may have had additional post-coding steps to perform, such as peer review, unit testing, and documentation. You may need to edit item attributes while checking items in to confirm that you did these steps.
Related topics:
Checking In an Item
Action and delegate items. If you are finished working on this item and it's ready to go on to the next step in the lifecycle (for example, if it's ready for QA), you can action it when you check it in.
If there are multiple people who can perform the next step and you want it to go to someone in particular, you may delegate it first.
Related topics:
Actioning an Item
Delegating an Item
Action requests. If there are requests associated with the items you've finished working on, you'll need to edit their attributes and action the requests to the next step in the lifecycle.
You may do this as you complete each request, or you may action all requests together at the end of the day.
Related topics:
Actioning a Request