requirements traceability to test cases and actual test results, from build defintions to feature and defect content, from source code to change packages and back to requirements, etc.
27 Advanced Data Import Capabilities: It must be easy to import data from existing solution components. This includes source code, documents and data (e.g. problem reports, tasks, etc.)
28 Project Management with Gantt Charts and WBS Support: A basic project management capability must support Agile development (priority-based feature/task driven development), preferably with charting to show plans and progress. As well, the tool supports a work breakdown structure (WBS) so that a project may be easily decomposed into workable units.
29 Full ALM Suite, from Requirements Tracking through to Test Suite Management: The CM/ALM suite must cover version control, change control, document management, requirement tracking, test case management, build and release management, problem tracking, feature/task management and ideally can be extended to cover other development areas (e.g. lab time assignment).
30 Real-time Metrics to Support Decision Making: A 3G tool must allow easy havesting of up-to-the-minute metrics that can be used for risk assessment, quality assurance and decision making.
31 High Reliability and Availability: The CM/ALM repository content must be available at all times (less than 24 hours outage/yr). A larger outage is permissible for repository content change capability, (e.g. for consistent backups it may be disabled) providing it does not impede the project significantly.
32 Data Transaction Journaling and Data Recovery Capabilities: All changes to the repository, source code or otherwise, must be clearly tracked so that it is always possible to know who did what, and when. There must also be support for recovery in the case of a disk crash or other repository corruption. If transaction journals remain intact through such problems, it should be possible to recover without any loss of data.
33 Advanced Backup and Redundancy Capabilities: As data volumes can grow significantly, advanced backup techniques must be used so that full backups can be performed in reasonable time frames. This is especially true if changes to the repository are disabled during backups. There should be sufficient redundancy such that operation of the CM/ALM environment can survive disk crashes/errors, network problems, etc.
34 Web Access Interfaces: At a minimum, a web interface must allow access to information within the repository to support field personnel, or specific contractor or customer access. Controls must be sufficient to adequately ensure that access is restricted according to the user. Ideally, updates to the repository (e.g. feature requests, problem reports or replies) can be performed through the web interface.
35 Flexible Reporting and Interactive Query: A 3G CM/ALM tool must support flexible reporting, within a specific application and across applications. It must be possible to produce both summary and key detailed reports directly from the tool (although in some cases some scripting may have to be put in place ahead of time to define the reports). As well, the tool must provide various interactive query capabilities so that high level data displays may be drilled down to reveal details, and so that traceability information can be traversed directly through mouse clicks.
36 Selectable Differencing/Merge Tools: As various developers and technologies have preferences for how differences are treated, it should be possible to select the difference/merge tools that a user will use with the overall CM/ALM tool. However, the CM/ALM tool must provide generally adequate tools out-of-the-box.
37 Basic Management Dashboards with Drill Down: A 3G CM/ALM tool must provide dashboards to present overall status for various roles. There should be, at a minimum, product, project and configuration management dashboards which support the roles