PR12374555_Appendix B_ToR Development.docx
DOCX document 36 KB Posted
- Solicitation number
- 191NLE24R0020
About this file
This document is Appendix B - Terms of Reference (ToR) for the Development of an Information System (called "MINORS") for the Office of the Prosecutor General (OPG) Juvenile Department. It outlines the key deliverables and requirements for the development of this system, including:
- An Inception Report to analyze the current situation, identify key stakeholders and information systems, and provide recommendations.
- A Report on Business Processes that documents the "As Is" and "To Be" business process models.
- A Functional Requirements Document (FRD) outlining the system's general requirements, subsystems, components, and access model.
- A Draft Graphical User Interface Design for selected system views.
- A Concept Note analyzing development approaches, technology options, implementation methodology, and providing a budget estimate and project roadmap.
- A Technical Specification Document (TSD) detailing the non-functional requirements, system architecture, technology stack, and implementation services.
This Appendix is related to Solicitation Number 191NLE24R0020 for IT Consulting Services for the OPG, which requires submitting questions by April 12, 2024.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| 191NLE24R0020 Questions_ANSWERS.xlsx | XLSX spreadsheet | |
| PR12374555_SOW OPG IT Consulting Services with TOR_AMENDED.docx | DOCX document | |
| SOW for OPG IT Consulting Services with TOR.pdf | ||
| Appendix A_SOW_OPG IT Consulting Services_EN.pdf | ||
| Questions 191NLE24R0020.xlsx | XLSX spreadsheet |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Appendix B
DEVELOPMENT OF ToR FOR THE INFORMATION SYSTEM (CALLED “MINORS”)
FOR THE OPG JUVENILE DEPARTMENT
SPECIFICATIONS
Detailed Terms of Reference (ToR) should have the following deliverables:
1. Inception Report.
2. Report on Business Processes.
3. Functional Requirements Document (FRD).
4. Draft graphical user interface design.
5. Concept Note.
6. Technical Specification Document (TSD).
1: INCEPTION REPORT
Description:
- Collection and analysis of data about the needs of the OPG Juvenile Department and the future System.
- Study of the current situation, main roles and working processes of end users, their perimeters, and powers, organization’s structure, basic regulation and working instructions.
- Collection and analysis of the processes’-related legislation requirements which should be considered within the software development and covered by the ToR.
- Formation of a comprehensive and deep understanding of the project goals, scope, and limitations, as well as the expectations of the customer, its internal decision-makers, and end users regarding the product.
- Identification and preliminary analysis of the information systems and platforms with which the perspective System will exchange data and/or which should be integrated in the perspective System.
- Preparation of the Inception Report, providing conclusions and recommendations.
2: REPORT ON BUSINESS PROCESSES
Description:
- Decomposition of all Juvenile Department’s operations in business processes that are part of the automation project.
- Development of graphic Business Process Model and Notations (BPMN) 2.0-compliant schemes (graphs) of all the listed business processes:
- As they are executed in present (As Is).
- As they should be executed within the paradigm of the perspective information system (To Be).
- Preparation of the detailed descriptions to As Is and To Be business process schemes (graphs).
- Preparation of the Report on Business Processes, providing conclusions and recommendations.
3: FUNCTIONAL REQUIREMENTS DOCUMENT (FRD)
Description:
- Development of general requirements that describe the internal operation of the System.
- Development of the graph with system decomposition on subsystems and components.
- Development of detailed functional requirements for the system, its subsystems, and components.
- Development of the matrix of entities and their attributes, and the entity-related diagram (ER-Diagram).
- Development of the role-based access and functionality scope model.
4: DRAFT INTERFACE DESIGN
Description:
- Development of draft interface design of the information system’s selected view screens.
- Delivery in the format of image, PDF or the link to Figma or other relevant cloud platform.
5: CONCEPT NOTE
Description:
- Analysis of the drafted materials and listing the potential approaches to the development of the perspective System:
- In-house, outsource, staff lease or hybrid.
- Options for the selection of the technology stack and basic software.
- Analysis of the possibility and financial rationale to use ready software for the System modules, sub-systems, or components (paid or open-source, versions and other details), or consider custom software development.
- Distribution model to select for the ready-software options (SaaS, API, on-premise or hybrid), possible ways and specifics of its potential integration.
- Recommendation on the software development methodology to be used (cascaded, agile, their sub-types, or hybrid).
- Analysis of the proposed approaches, listing pros and cons, proposal of the most optimal approach.
- Recommendations for project implementation and further support.
- Budget Estimate.
- Listing project activities (development roadmap).
- Listing expected results, providing conclusions and final recommendations.
6: TECHNICAL SPECIFICATION DOCUMENT (TSD)
Description:
- Development of detailed non-functional software requirements, including:
- general requirements for the software,
- requirements for software operation, reliability, and performance,
- system security requirements,
- system unit interoperability,
- training requirements.
- Development of the block diagram of the System architecture and its components.
- Hardware requirements.
- Description of the components and the technology stack to be used for the software development.
- Development of detailed requirements for the provision of services, including:
- requirements for the project plan and stages of service provision,
- licensing requirements,
- development and adaptation requirements,
- installation and configuration requirements,
- testing and migration requirements,
- requirements for the complex system of information protection,
- requirements for documentation,
- experimental operation requirements,
- requirements for warranty, support, maintenance, and additional services.
File details come from the government source that posted it. Updated .