A typical software development life-cycle requires the development, evolution, and management of things other than source files, such as requirements, models, graphics, change requests, schedules, tests, and so on.
The following table defines each built-in item type supported by the
StarTeam Web Client and shows its icon on the user interface.
| Icon
|
Item
|
Definition
|
|
File
|
StarTeam can store any kind of file. The
StarTeam Web Client allows you to work with an existing project file in the following ways.
- Bulk check in and check out.
- View and edit file properties.
- View historical information about file revisions.
- Save a file or any of its historical revisions to a local or network drive.
|
|
Change Request
|
A request to change something within the scope of a project. Development teams create change requests to record problems and enhancement requests and to track their resolution or implementation.
|
|
Requirement
|
Specifies a condition the software functionality must meet. The use of requirements enables business analysts, managers, developers, QA staff, and others to perform the following activities:
- Organize business, user, and functional requirements in a hierarchical format
- Indicate the dependencies among requirements
- Prioritize requirements by importance
- Identify the impact of changes to requirements
- Use requirements to estimate work
- Identify the person creating the requirement and the person who is responsible for completing it
- Track the requirement lifecycle from submission to completion or rejection
|
|
Task
|
Represents a needed, active, or completed unit of work. Tasks allow project team members to perform the following activities:
- Create new tasks and assign them to team members
- Review current task status
- Estimate hours required to complete a task
- Record hours spent working on a task
- Compare estimated to actual time spent completing a task
|
|
Topic
|
The first message in a threaded conversation that serves to raise a project issue to which team members can respond. Topics and their responses allow important discussions to be documented.
|
|
|
Alternate Property Editors
|
Alternate property editors (APE) created through StarFlow Extensions are now fully supported via the
StarTeam Web Client. If APEs are enabled for the project, then the user will be shown the editor as a local dialog for updating with all workflow being fully enforced. When using APEs through the
StarTeam Web Client, the APE will make a direct connection to the
StarTeam Server and thus firewall settings between the user's machine and the
StarTeam Server should be taken into consideration.
You do not need to make changes to the code of the APE but the JAR on the server does need to be signed and re-checked in to the
Starflow Extensions project.
APE forms are not modal.
Note: APEs cannot be closed by using the APE`s "X" button. You need to use the
OK or
Cancel buttons.
In order to remove the messages that the APE will show before launching:
- Firefox
-
- Ensure that you check the option
Do this automatically for files like this from now on.
- When the Java Dialog is displayed you will need to click
Run to start the APE.
- Internet Explorer
-
- Check the option
Do not show this again for apps from the published and location server.
- When the Java Dialog is displayed you will need to click
Run to start the APE.
- Chrome
-
- Click the downloaded
.JNLP file.
- When the Java Dialog is displayed you will need to click
Run to start the APE.
- Check the option
Do not show this again for apps from the published and location server.
|