Technical Specifications forcomputer Aided Software Engineeering(CASE) Tools BHEL R&D requires the following CASE tools to adopt them in the Software Development Life Cycle Management at it s premises: Tools for Software Requirement Analysis and Management Tools for Software Configuration Management Tools for Software Defect(Bug) Management The following sections describe the requirements in detail: 1. Functional Specifications 1.1 Software Requirement Analysis and Management The tool shall be capable of the following features: 1.1.1 Requirements Analysis: a) Behaviour Modelling based on Use case diagrams, Scenarios and Sequence diagrams b) Problem Domain Model (PDM) building: Describe business concepts textually and graphically through class diagrams, E/R diagrams and sequence diagrams. c) Modelling of the relationships between the system and the external entities and textual and graphical description of the services. Use Case diagrams, DFDs, Sequence diagrams, state diagrams. d) Organisation of the models based on different criteria. e) Graphical representation of domains and blocks. 1.1.2 Requirements Management: a) Version management. b) User-defined requirement process and traceability rules by means of block diagrams. c) Mandatory Attributes, Filters and Workflows. d) Grid views defined by the user. e) User interface by role f) Automatic code configuration. g) Hierarchical Management of Requirements. h) Navigate through the specification using the block and domain diagrams. i) Specification validation : a. Traceability between services and requirements. b. Traceability between tests scenarios and requirements or services. j) Requirement Traceability: a. Relationships between requirements. b. Relationships between user requirements and services. c. Relationships between requirements and business concepts.
d. Traceability. e. Provides drag and drop capability for linking a requirement to a design item, to a test case or to another requirement. f. Shows full traceability reports in a single view to help prioritize development work and predict delivery schedule. 1.1.3 Integration with other Tools: b) Integrations with third party Configuration Management tool and SCC compliant. c) Integration with third party Bug management tool. d) Manual Automatic Capture from MS Office (MS Word, MS Excel, MS Outlook). e) Direct exportation to MS Excel and MS Word. f) Plug-In support. g) Integration with Microsoft visual studio. h) Requirements description with RTF format and relationships with external files in local folders or in SCM tools. 1.2 Software Configuration Management 1.2.1. Configuration Management:
1.2.2. Integration with other Tools: 1.3 Software Defect(Bug) management 1.3.1. Defect Management 1.3.2. Integration with other Tools: 2. Platform support b) Multi web browser support (where applicable): The tools supplied shall be compatible with the Internet Explorer (7.0 and above), Mozilla Fire Fox (4.0 and above), Google Chrome.
3. Licenses S# Description Licenses required 1 Software Requirement Analysis and Management 2 Software Configuration Management Tool 3 Software Defect(Bug) management One license Ten licenses Ten Licenses Remarks 1. Licenses with support for maximum concurrent licenses as specified for each of the tools. 2. The licenses shall be of perpetual type (minimum 20 years validity) Table 1: Software Tools and Licenses 4. Installation, Deployment,Configuration, Training and Support The bidder shall include the following in the scope of supply: b) c) 5. General
S# Tools Description Product Offered 1 Software Requirement Analysis and Management 2 Software Configuration Management Tool 3 Software Defect(Bug) management Compliance with Specifications 6. Vendor competence requirements 7. Deliverables