ITSD-11589 (Implement Document Repository - FileNet)
| Jira Request | ITSD-11589 |
|---|---|
| Application(s) | New Feature Implementation Request (FileNet) |
| Business Process(es) | Content Management |
| Requester | |
| IT Business Analyst | |
| Document Owner | |
| Document Status | DRAFT |
Document Purpose
The purpose of this document is to provide high-level business and functional requirements for Service Requests and Projects. High-level business requirements for Projects are obtained from the Business Case Evaluation or the Project Request.
Requirement Elicitation Sessions and Reviews Conducted:
The following requirement elicitation sessions and reviews were conducted with the customers on the following days:
- 08/03/2022, @a user , SME
Introduction
Request Description
The lab currently stores documents in a shared folder. This request is to create a FileNet repository to store their documents. Using FileNet will allow the lab to find documents more easily and reduces the risk of documents being deleted by accident.
Business Requirement Instructions
Business requirements are needs or wants or an organization which allows the business to achieve its end objectives, vision, and goals. They give the extent of a business need or a problem that should be addressed by a particular project. Business requirements are intended to be guide and they are not intended to be specified at a level that they could be implemented by a developer. Each requirement should be assigned a unique requirement key as this key is used for traceability from this document through to the implementation of the requirement.
Requirement Key: IT-9999-BR-9999 (IT-9999 = Jira Epic or Issue # of your project/task, BR = Business Requirement, 9999 = Unique # assigned by Requirement Yogi). Requirement Yogi will automatically assign the next consecutive number.
Requirement Type:
- Executive, Stakeholder, Product
The source column indicates the source of the requirement and can be any of the following:
- Specific Person or Persons
- Group, Division or Department
- Documentation (Forms, etc.)
- Meeting
- Application
The priority column ranks the relative importance of the requirement to the Stakeholders:
- 1 – highest priority; absolutely essential product feature OR Must have
- 2 – medium priority; individual features are not essential, but together they affect the viability of the system OR Should have
- 3 – lowest priority; nice-to-have feature; one or more of these features could be omitted without affecting the system viability OR Nice-to-have
- Not implementing
Status Legend
NEW | New requirement, details have not been worked out |
|---|---|
WIP | Requirement details are being worked out. |
PO REVIEW | PO is reviewing the requirement or implementation options. |
IN REVIEW | Requirements are in review by the project team. |
REVIEWED | Requirements have been reviewed by the project team and are ready for approval |
|---|---|
SYSTEM TEST | Requirements are in system test. |
UAT | Requirements are being tested by the customer. |
CANCELLED | The business decided they did not need the requirement (keep on matrix as they may change their mind). |
APPROVED | The requirement has been approved by the customer and can be implemented. |
|---|---|
DEPLOYED | A solution that meets the requirements have been deployed into production. |
Business Requirements
The following matrix describes the high-level business requirements:
Key | Requirement Description | Type | Source | Priority | Status | Links |
|---|---|---|---|---|---|---|
ITSD-11589-BR-001 | Add new Document Class in FileNet (similar to Admin) so that Lab can store (check-in/check-out/search) their documents. | Stakeholder | Srivi Ramamoorthy Justin Nordin | Must have | IN REVIEW |
|
ITSD-11589-BR-002 | Provide security so that only Lab staff can access/modify these documents in FileNet | Stakeholder | Srivi Ramamoorthy Justin Nordin | Must have | IN REVIEW |
Functional Requirements
This section specifies the functional requirements (FR). These should also be the basis for UAT testing.
Key | Functional Requirement | Status | Source | Category | Priority | Refines Business Requirement | Links |
|---|---|---|---|---|---|---|---|
ITSD-11589-FR-001 | Create new document master class "Laboratory" in EDM under "SRCSD Document" | IN REVIEW | Justin Nordin | Data | Must Have | Refer to Lab Document Class Details for attribute details | |
ITSD-11589-FR-002 | Add document class Reports under Laboratory | IN REVIEW | Justin Nordin | Data | Must Have | Refer to Lab Document Class Details for attribute details | |
ITSD-11589-FR-003 | Add following document sub-classes under Reports:
| IN REVIEW | Justin Nordin | Data | Must Have | Refer to Lab Document Class Details for attribute details | |
ITSD-11589-FR-004 | Add Document Class Worksheets under Laboratory class | IN REVIEW | Justin Nordin | Data | Must Have | Refer to Lab Document Class Details for attribute details | |
ITSD-11589-FR-005 | Add Document Class QA (Regulatory) Documents under Laboratory class | IN REVIEW | Justin Nordin | Data | Must Have | Refer to Lab Document Class Details for attribute details | |
ITSD-11589-FR-006 | Add following document sub-classes under QA (Regulatory) Documents:
| IN REVIEW | Justin Nordin | Data | Must Have | Refer to Lab Document Class Details for attribute details | |
ITSD-11589-FR-007 | Add Document Class Contract under Laboratory class | IN REVIEW | Justin Nordin | Data | Must Have | Refer to Lab Document Class Details for attribute details | |
ITSD-11589-FR-008 | Add following document sub-classes under Contract:
| IN REVIEW | Justin Nordin | Data | Must Have | Refer to Lab Document Class Details for attribute details | |
ITSD-11589-FR-009 | Provide a group of Lab users admin rights (checkin/checkout/manage users). These users are:
| IN REVIEW | Justin Nordin | Process | Must Have | ||
ITSD-11589-FR-010 | Provide rest of staff (not in Group above) ability to search/view documents | IN REVIEW | Justin Nordin | Process | Must Have | Refer to A/D Group "SRWTP Laboratory" for complete list of users. | |
ITSD-11589-FR-011 | Archive Documents: On Jan 1st change status of all previous year documents to Archived. Selective set of documents have to be removed from search. | IN REVIEW | Justin Nordin | Data/Process | Must Have |
Questions
Below is a list of questions to be addressed as a result of this requirements document:
Question | Outcome |
|---|---|
| Does everyone, who can access FileNet, search/view Lab document? If yes then can it have controlled access in future? |