StRS,_RVTM_-_Contractor_Technical_Response_Worksheet,_ICN.xlsx
XLSX spreadsheet 27 KB Posted
- Attached to
- Internal Collaboration Network and History Hub
- Solicitation number
- NAMA-17-R-0001
About this file
NAMA-17-R-0001, Attachment 9, Proposal Submission Instructions, paragraph 1(a)(ii), StRS RVTM Contractor Technical Response Worksheet (ICN)
View the file
Other files
| File | Type | Posted |
|---|---|---|
| NAMA-17-R-0001_Amendment_002_FINAL.doc | DOC document | |
| PWS Appendix 1, NARA SDLC v1.6.pdf | ||
| NAMA-17-R-0001_ICN_-_HH_CSS_Attachments_1-12.docx | DOCX document | |
| PWS Appendix 6, Test_Plan_Template.docx | DOCX document | |
| PWS Appendix 2, NARA IT Security Requirements v6.5.pdf | ||
| PWS Appendix 5, RVTM_Template_v2.0.xlsx | XLSX spreadsheet | |
| PWS Appendix 8, Test_Report_Template.docx | DOCX document | |
| StRS,_RVTM_Contractor_Technical_Response_Worksheet,_HH.xlsx | XLSX spreadsheet | |
| PWS Appendix 4, StRS_HistoryHub_v1.1_FINAL Redacted.docx | DOCX document | |
| PWS Appendix 3, StRS_ICN_v1.1_FINAL Redacted.docx | DOCX document | |
| PWS Appendix 11, Cloud_CMDB_Template.xlsx | XLSX spreadsheet | |
| GFI_-_PWS_Appendices_1_-_8,_and_11.zip | ZIP file | |
| PWS Appendix 7, Test_Procedures_Template.xlsx | XLSX spreadsheet |
Show all 13
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
Requirements
| REQUIREMENTS | MISC | DESIGN | DEVELOPMENT | VERIFICATION | DEPLOYMENT PREPARATION | CONTRACTOR'S RESPONSE | CONTRACTOR'S TIME TO IMPLEMENT | CONTRACTOR'S NOTES | ||||||||||
| Req # | Requirement Text | Type | Category | Feature | Req Priority | |||||||||||||
| Status | Target Release | Notes | Element | Iteration | Verification Method | Verification Test Case / Step | Verification Status | Verification Criteria | UAT Test Case | UAT Status | Validation Criteria | 0-4 | Ready at Award through +90 Days | (May be Used for Brief explanations, where applicable) | ||||
| 1 | The system shall support role-based access and account management. | Stakeholder | Functional | Account Management | Must | Approved | User roles and permissions are defined in the Stakeholder Requirements Specification (StRS). | |||||||||||
| 2 | The system shall provide the capability for Application Administrators to create and maintain user accounts within the Internal Collaboration Network (ICN.) | Stakeholder | Functional | Account Management | Must | Approved | ||||||||||||
| 3 | The system shall provide the capability for registered users to create announcements. | Stakeholder | Functional | Announcements | Must | Approved | These announcements differ from blogs as they are a "one-time" broadcast. | |||||||||||
| 4 | The system shall provide the capability to display announcements across the ICN or within a group in the ICN. | Stakeholder | Functional | Announcements | Must | Approved | ||||||||||||
| 5 | The system shall provide the capability for registered users to upload artifacts within the ICN. | Stakeholder | Functional | Attachments | Must | Approved | At a minimum the following formats need to be supported for uploaded attachments: Microsoft Word (.doc/.docx), Microsoft Excel (.xls/.xlsx), Microsoft PowerPoint (.ppt/.pptx), .pdf, jpg, .tif, and .bmp. | |||||||||||
| 6 | The system shall provide the capability for registered users to download artifacts within the ICN. | Stakeholder | Functional | Attachments | Must | Approved | ||||||||||||
| 7 | The system shall provide the capability for an Application Administrator to specify the file size limitation for uploaded attachments within the ICN. | Stakeholder | Functional | Attachments | Must | Approved | ||||||||||||
| 8 | The system shall provide the capability for registered users to tag another registered user within the ICN as a connection. | Stakeholder | Functional | Contacts | Must | Approved | ||||||||||||
| 9 | The system shall provide the capability for registered users to send a direct message to other registered users within the ICN. | Stakeholder | Functional | Contacts | Must | Approved | ||||||||||||
| 10 | The system shall provide the capability for registered users to follow and unfollow other registered users within the ICN. | Stakeholder | Functional | Contacts | Must | Approved | This is a feature similar to adding a friend in Facebook. | |||||||||||
| 11 | The system shall provide the capability for registered users to create content within the ICN. | Stakeholder | Functional | Content Management | Must | Approved | ||||||||||||
| 12 | The system shall provide the capability for registered users to view content within the ICN. | Stakeholder | Functional | Content Management | Must | Approved | ||||||||||||
| 13 | The system shall provide the capability for registered users to create a private document. | Stakeholder | Functional | Content Management | Must | Approved | ||||||||||||
| 14 | The system shall provide the capability for registered users to create a document visible to only select users. | Stakeholder | Functional | Content Management | Must | Approved | ||||||||||||
| 15 | The system shall provide the capability for registered users to create a document visible to all registered users in the ICN. | Stakeholder | Functional | Content Management | Must | Approved | ||||||||||||
| 16 | The system shall provide the capability to embed photos and videos in documents. | Stakeholder | Functional | Content Management | Must | Approved | ||||||||||||
| 17 | The system shall provide the capability for groups to collaborate on documents. | Stakeholder | Functional | Content Management | Must | Approved | ||||||||||||
| 18 | The system shall provide the capability to restrict what registered users can edit a document. | Stakeholder | Functional | Content Management | Must | Approved | ||||||||||||
| 19 | The system shall provide the capability to prevent users from commenting on a document. | Stakeholder | Functional | Content Management | Must | Approved | ||||||||||||
| 20 | The system shall provide the capability for a registered user to create a personal task and assign a due date. | Stakeholder | Functional | Content Management | Must | Approved | A personal task is not associated with a particular project. | |||||||||||
| 21 | The system shall provide the capability for a registered user to create an idea for other registered users to view and vote on. | Stakeholder | Functional | Content Management | Must | Approved | ||||||||||||
| 22 | The system shall provide the capability for a registered user to create content in the ICN via their NARA email account. | Stakeholder | Functional | Content Management | Must | Approved | Creating content via email includes sending a status update; creating personal tasks, bookmarks, a private document, a private discussion, or a private idea; and responding to discussions. | |||||||||||
| 23 | The system shall provide the capability for external users to create content within the groups that are restricted to their access. | Stakeholder | Functional | Content Management | Should | Deferred | ||||||||||||
| 24 | The system shall provide the capability for external users to view content within the groups that are restricted to their access. | Stakeholder | Functional | Content Management | Should | Deferred | ||||||||||||
| 25 | The system shall provide the capability for registered users to create a private discussion thread. | Stakeholder | Functional | Discussion/Forums | Must | Approved | ||||||||||||
| 26 | The system shall provide the capability for registered users to create an open (i.e., not private) discussion thread. | Stakeholder | Functional | Discussion/Forums | Must | Approved | ||||||||||||
| 27 | The system shall provide the capability for registered users to post comments or questions via a discussion thread. | Stakeholder | Functional | Discussion/Forums | Must | Approved | ||||||||||||
| 28 | The system shall provide the capability for registered users to respond to a post within a discussion thread. | Stakeholder | Functional | Discussion/Forums | Must | Approved | ||||||||||||
| 29 | The system shall provide the capability for registered users to view initial posts and responses to discussion threads. | Stakeholder | Functional | Discussion/Forums | Must | Approved | ||||||||||||
| 30 | The system shall provide the capability for external users to post comments or questions via a discussion thread within the groups that are restricted to their access. | Stakeholder | Functional | Discussion/Forums | Should | Deferred | ||||||||||||
| 31 | The system shall provide the capability for external users to respond to a post within a discussion thread within the groups that are restricted to their access. | Stakeholder | Functional | Discussion/Forums | Should | Deferred | ||||||||||||
| 32 | The system shall provide the capability to create a workspace that allows multiple registered users to collaborate on the same project or document within a group. | Stakeholder | Functional | Document Collaboration | Must | Approved | ||||||||||||
| 33 | The system shall provide the capability for registered users to create a document and enable or disable collaborators' editing permissions at the page level. | Stakeholder | Functional | Document Collaboration | Must | Approved | Editing permissions are those related to the add, update, delete capabilities at the page and/or document level. | |||||||||||
| 34 | The system shall provide the capability for registered users to create a document and enable or disable collaborators' editing permissions at the document level. | Stakeholder | Functional | Document Collaboration | Must | Approved | ||||||||||||
| 35 | The system shall have the ability to export content in .pdf format. | Stakeholder | Functional | Export | Must | Approved | ||||||||||||
| 36 | The system shall provide the capability for registered users to flag ICN content for abuse. | Stakeholder | Functional | Flag Content | Must | Approved | ||||||||||||
| 37 | The system shall send an alert to Application Administrators when content is flagged. | Stakeholder | Functional | Flag Content | Must | Approved | ||||||||||||
| 38 | The system shall provide the capability for registered users to create groups within the ICN. | Stakeholder | Functional | Groups | Must | Approved | ||||||||||||
| 39 | The system shall provide the capability for registered users to delete a group within the ICN, if they are the owner of that group. | Stakeholder | Functional | Groups | Must | Approved | ||||||||||||
| 40 | The system shall provide the capability for Application Administrators to manage groups within the ICN, including creating, updating, and deleting groups. | Stakeholder | Functional | Groups | Must | Approved | ||||||||||||
| 41 | The system shall provide the capability to define group access as open to all registered users. | Stakeholder | Functional | Groups | Must | Approved | ||||||||||||
| 42 | The system shall provide the capability to define group access as open by invitation only, with all group members and content visible via a search. | Stakeholder | Functional | Groups | Must | Approved | ||||||||||||
| 43 | The system shall provide the capability to define group access as private and by invitation only, with all group members and content hidden via a search. | Stakeholder | Functional | Groups | Must | Approved | ||||||||||||
| 44 | The system shall provide the capability for groups to manage calendars. | Stakeholder | Functional | Groups | Must | Approved | ||||||||||||
| 45 | The system shall provide the capability for groups to manage tasks. | Stakeholder | Functional | Groups | Must | Approved | ||||||||||||
| 46 | The system shall provide the capability to support user group blogs. | Stakeholder | Functional | Groups | Must | Approved | ||||||||||||
| 47 | The system shall provide the capability for registered users to customize a group's settings and overview page, if they are the owner of that group. | Stakeholder | Functional | Groups | Must | Approved | ||||||||||||
| 48 | The system shall provide the capability for registered users to request to join a group. | Stakeholder | Functional | Groups | Must | Approved | ||||||||||||
| 49 | The system shall provide the capability for registered users to accept or deny a request to join a group, if they are the owner of that group. | Stakeholder | Functional | Groups | Must | Approved | ||||||||||||
| 50 | The system shall allow registered users to generate and display a status message. | Stakeholder | Functional | Microblogging/Status Updates | Must | Approved | ||||||||||||
| 51 | The system shall provide the capability for registered users to display a status message to all registered users or a sub-set of selected registered users. | Stakeholder | Functional | Microblogging/Status Updates | Must | Approved | ||||||||||||
| 52 | The system shall send a notification to a registered user when content followed by the user is updated within the ICN. | Stakeholder | Functional | Notifications | Must | Approved | ||||||||||||
| 53 | The system shall provide the capability for registered users to create a personal blog. | Stakeholder | Functional | Personal Blogs | Must | Approved | ||||||||||||
| 54 | The system shall provide the capability for registered users to generate a poll. | Stakeholder | Functional | Polls | Must | Approved | ||||||||||||
| 55 | The system shall provide the capability for registered users to vote on poll content. | Stakeholder | Functional | Polls | Must | Approved | ||||||||||||
| 56 | The system shall provide the capability for registered users to provide text-based responses on poll content. | Stakeholder | Functional | Polls | Must | Approved | ||||||||||||
| 57 | The system shall provide the capability for an Application Administrator to add, update, and delete user profiles. | Stakeholder | Functional | Profile Pages | Must | Approved | ||||||||||||
| 58 | The system shall provide the capability for an Application Administrator to add, update, and delete the display of user profile images. | Stakeholder | Functional | Profile Pages | Must | Approved | Profile images are user 'headshots' or profile pictures. | |||||||||||
| 59 | The system shall provide the capability for an Application Administrator to add, update, and delete the contact information from a user profile. | Stakeholder | Functional | Profile Pages | Must | Approved | ||||||||||||
| 60 | The system shall provide the capability for an Application Administrator to add, update, and delete the organizations, working groups, business functions and contacts associated with a user's profile. | Stakeholder | Functional | Profile Pages | Must | Approved | ||||||||||||
| 61 | The system shall provide the capability for an Application Administrator to define the organizational relationships between user profiles. | Stakeholder | Functional | Profile Pages | Must | Approved | Organizational relationships pertain to a user's manager/supervisor, division/branch chief, subordinates. | |||||||||||
| 62 | The system shall provide the capability for registered users to upload and display a profile image for their user profile. | Stakeholder | Functional | Profile Pages | Must | Approved | Profile images are user 'headshots' or profile pictures. | |||||||||||
| 63 | The system shall provide the capability for registered users to enter and update contact information within their user profile. | Stakeholder | Functional | Profile Pages | Must | Approved | ||||||||||||
| 64 | The system shall provide the capability for registered users to delete elements of the contact information within their user profile. | Stakeholder | Functional | Profile Pages | Must | Approved | Registered users can delete most contact information themselves, but they cannot delete their name and email address (i.e., cannot delete their entire user profile from the system.) | |||||||||||
| 65 | The system shall provide the capability for registered users to associate their user profile with organizations, working groups, business functions, and other registered users within the ICN. | Stakeholder | Functional | Profile Pages | Must | Approved | ||||||||||||
| 66 | The system shall provide the capability for registered users to define who can see elements of their profile information. | Stakeholder | Functional | Profile Pages | Must | Approved | This is the ability for a user to set privacy settings on their profile. Users may be able to define privacy settings for some portions of their user profile (i.e., make it private and not be displayed), but their name and email address will always be visible. | |||||||||||
| 67 | The system shall display a summary of a registered user's ICN activities in their profile page. | Stakeholder | Functional | Profile Pages | Must | Approved | ||||||||||||
| 68 | The system shall display a summary of a registered user's contributed ICN content in their profile page. | Stakeholder | Functional | Profile Pages | Must | Approved | ||||||||||||
| 69 | The system shall display a registered user's connections, groups, tasks, and bookmarks in their profile page. | Stakeholder | Functional | Profile Pages | Must | Approved | ||||||||||||
| 70 | The system shall provide the capability for registered users to create and describe projects and their associated timelines. | Stakeholder | Functional | Project Management | Must | Approved | ||||||||||||
| 71 | The system shall provide the capability for registered users to track and assign their own project tasks and sub-tasks, as well as, for other registered users. | Stakeholder | Functional | Project Management | Must | Approved | ||||||||||||
| 72 | The system shall provide the capability to assign a value for rating content within the ICN. | Stakeholder | Functional | Rating | Must | Approved | Rating allows a user to indicate how much he or she liked or disliked a content item. For example, a rating could be on a scale, such as 1 to 5 stars, or it could be a simple thumbs up or thumbs down, depending on the platform. Ratings contribute to the reputation and perception of that content. | |||||||||||
| 73 | The system shall provide the capability for an Application Administrator to generate standard and ad hoc reports. | Stakeholder | Functional | Reporting | Must | Approved | ||||||||||||
| 74 | The system shall provide the capability for registered users to generate standard and ad hoc reports. | Stakeholder | Functional | Reporting | Must | Approved | ||||||||||||
| 75 | The system shall provide the capability for registered users to search on content within the ICN. | Stakeholder | Functional | Search | Must | Approved | ||||||||||||
| 76 | The system shall display search results based on a user's role, permissions, and group membership within the ICN. | Stakeholder | Functional | Search | Must | Approved | Search results must respect access rights. | |||||||||||
| 77 | The system shall provide the capability for registered users to filter on search results. | Stakeholder | Functional | Search | Must | Approved | Filtering is the ability to refine and get a subset of search results based on the groups, people, or type of content associated with the search results. | |||||||||||
| 78 | When performing a search on tags, the system shall return search results based on keyword matching. | Stakeholder | Functional | Search | Must | Approved | Tag meanings shall be combined so that "web," "web site," and "website" (for example) will all be returned on a search for any one of these keywords. | |||||||||||
| 79 | The system shall provide the capability for registered users to share items of interest within the ICN and outside of the ICN. | Stakeholder | Functional | Social Bookmarking | Must | Approved | Sharing consists of sharing a link (URL) to content inside the ICN (e.g., a blog post) or content outside the ICN (e.g., an article on the internet.) | |||||||||||
| 80 | The system shall provide the capability for registered users to tag content within the ICN. | Stakeholder | Functional | Tagging | Must | Approved | Tagging will consist of allowing users to assign keywords, terms, or metadata to a piece of information. | |||||||||||
| 81 | The system shall provide the capability for registered users to enter tags as free text or by selecting from an administered pick list. | Stakeholder | Functional | Tagging | Must | Approved | ||||||||||||
| 82 | The system shall provide the capability for registered users to specify categories to be applied to content within their group. | Stakeholder | Functional | Tagging | Must | Approved | Categories are created by a group owner/administrator and can be selected when content is created or added later. Categories are used to group content that falls under the same topic. | |||||||||||
| 83 | The system user interface shall be responsive for use of the ICN on mobile devices. | Stakeholder | Functional | UI/Mobile Access | Must | Approved | The ICN should be accessible via Android, iOS, and Windows devices. | |||||||||||
| 84 | The system user interface shall provide the capability for registered users to view, post and reply to content within the ICN via a mobile device. | Stakeholder | Functional | UI/Mobile Access | Must | Approved | ||||||||||||
| 85 | The system user interface shall provide the capability for registered users to follow groups, registered users, or content within the ICN. | Stakeholder | Functional | User Interface | Must | Approved | ||||||||||||
| 86 | The system user interface shall provide the capability for registered users to unfollow groups, registered users, or content within the ICN. | Stakeholder | Functional | User Interface | Must | Approved | ||||||||||||
| 87 | The system user interface shall display an activity stream based on updates to a registered user's groups, content, or followed users. | Stakeholder | Functional | User Interface | Must | Approved | A personalized activity stream, similar to Facebook, that displays updates that occur to the groups, content or contacts associated with a registered user's profile. | |||||||||||
| 88 | The system user interface shall display trending content and trending people to show the most active content and people in the ICN. | Stakeholder | Functional | User Interface | Must | Approved | ||||||||||||
| 89 | The system shall be a web-based Software-as-a-Service (SaaS) solution. | Stakeholder | Constraint | Hosting | Must | Approved | ||||||||||||
| 90 | The system user interface shall comply with the Section 508 Standards for Electronic and Information Technology as defined in the Contactor submitted and Government accepted Government Product Accessibility Template | Stakeholder | Constraint | Usability | Must | Approved | ||||||||||||
| 91 | The system shall be compatible with the current and the one (1) prior version of Chrome, Internet Explorer, Firefox, Safari, and Microsoft Edge web browsers. | Stakeholder | Constraint | Web Browser Compatibility | Must | Approved | ||||||||||||
| 92 | The system shall be IPv6 compliant. | Stakeholder | Constraint | Web Browser Compatibility | Must | Approved | ||||||||||||
| 93 | The system shall be 99% available, 24 hours a day, 7 days a week, with the exception of scheduled maintenance downtime. | Stakeholder | Non-functional | Availability | Must | Approved | This will enable records to be accessible for agency responsiveness to discovery, FOIA, Privacy Act, or other access requests. | |||||||||||
| 94 | The system shall provide the capability for backup and recovery of the system. | Stakeholder | Non-functional | Backup and Recovery | Must | Approved | ||||||||||||
| 95 | The system shall support the bulk import of all data from the legacy ICN system to the new ICN system. | Stakeholder | Non-functional | Data Transfer | Must | Approved | This includes user accounts and user profile information, established groups and membership data, and all contributed/posted content. |
Note: The current backend database for ICN on the Jive platform is Oracle.
| 96 | The system shall be capable of integrating with Google Docs. | Stakeholder | Non-functional | Integration | Should | Approved | |
| 97 | The system shall provide the capability to assign metadata and maintain links between the content and its metadata. | Stakeholder | Non-functional | Metadata Assignment | Must | Approved | This includes user applied tags and metadata automatically attributed from the creator’s user and/or group profile. |
| 98 | The system shall support a minimum of 3,500 users. | Stakeholder | Non-functional | Performance | Must | Approved | |
| 99 | The system shall be capable of expanding support up to 5,000 users without system performance degradation. | Stakeholder | Non-functional | Performance | Must | Approved | |
| 100 | The system shall be in compliance with NARA IT Security Contractual Requirements. | Stakeholder | Non-functional | Security | Must | Approved | |
| 101 | The system shall provide secure application access and data transport. | Stakeholder | Non-functional | Security | Must | Approved | Secure access and data transport can be achieved via Secure Socket Layer (SSL). |
| 102 | The system shall be capable of using NARA’s identity management and authentication service for access control. | Stakeholder | Non-functional | Security | Must | Approved | |
| 103 | The system shall be capable of restricting access on the basis of Internet Protocol (IP) addresses. | Stakeholder | Non-functional | Security | Must | Approved | |
| 104 | The system shall prevent unauthorized access to the administration functions of the ICN. | Stakeholder | Non-functional | Security | Must | Approved | Administrative access is restricted to NARA Application Administrators and vendor System Administrators. Administrative functions include system configuration and account management tasks. |
&"+,Bold"&10Internal Collaboration Network (ICN) Requirements Verification Traceability Matrix (RVTM)
&"+,Regular"&10&F &"+,Regular"&10Page &P of &N
Contractor Response Legend
| Legend | |
| 0 - Cannot Meet | Cannot meet the requirement. Use this value if the solution cannot meet the requirement. |
| 1 - Requires Significant Development | Requires significant customization or development (modification of source). Use this value if the solution will require changes or new development at the source code level to meet the requirement. |
| 2 - Requires Advanced Configuration | Requires advanced configuration or custom development using an SDK or API. Use this value if the solution will customization using an SDK or API to meet the requirement. |
| 3 - Requires Minimal Enhancement | Requires minimal or no special enhancements. Use this value if the solution meets the requirement with minimal configuration. |
| 4 - Requires No Enhancement | Use this value if the solution meets the requirement without configuration or enhancement. |
Include costs as part of your Volume III submission for individual or grouped items in the response for each item marked 1, 2, or 3.
| Time |
| Ready at time of award |
| 30 days from award |
| 60 days from award |
| 90+ days from award |
StandardValues
| Type | Category | Priority | |||||||
| Status | Verification Method | Verification Status | UAT Status | ||||||
| Business | Functional | Must | Requirements that are CRITICAL to meeting the project's objectives | Approved | Inspection | Pass | Pass | ||
| Stakeholder | Non-functional | Should | Requirements that are critical and should be included if possible, but which can be excluded | Deferred | Analysis | Fail | Fail | ||
| System | Constraint | Could | Requirements that are part of the project's scope and add or enhance project benefits | Draft | Test | N/A | N/A | ||
| N/A | Would | Requirements that do not have a significant impact on project benefits or could be considered as a “would like to have” | Obsolete | Demonstration | |||||
| Certification | |||||||||
| N/A |
&"+,Bold"&10<Project Name> Requirements Verification Traceability Matrix (RVTM) - Standard Values
&"+,Regular"&10&F &"+,Regular"&10Page &P of &N
File details come from the government source that posted it. Updated .