| Software Requirements Specification | |||||||||||
| ORIGINAL BY: | A. C. McCullough | ORIGINAL: | 4/13/2007 | REASON TO MODIFY: | The initial document was created. | ||||||
| MODIFIED BY: | LAST MODIFIED: | REASON TO MODIFY: | |||||||||
| Introduction | |||||||||||
| This spreadsheet contains the requirements for the SENTRY system. It includes all the known requirements for the external and internal web sites as well as the requirements for the data that must be used in both applications. Any modifications to this spreadsheet must be tracked within this document. When a requirement is changed please include a reason for the change and leave the original requirement. Use a numbering scheme to track changes to the original requirement. | |||||||||||
| System Overview | |||||||||||
| The SENTRY system consists of a public facing web site and an Intranet based web site. The purpose of the external site is to collect information from known registered users and the purpose of the internal site is for the analytical processing of information submitted from the external site. The complete scope of the effort includes both web sites and the transfer of information between them. | |||||||||||
| External Web Site | |
| Req. ID - Rev. | (Function) Requirement |
| (External - General) | |
| E-00010 | (General) The system shall present a banner (header) at the top of each page/form used throughout SENTRY external web site. |
| E-00020 | (General) The system shall present the NDIC seal at the top left-corner of the banner. |
| E-00030 | (General) The system shall present a consistent banner (header) to the right of the NDIC seal that includes the following: U. S. Department of Justice National Drug Intelligence Center SENTRY A synthetic drug early warning and response system (Comment: System handles other than synthetic drugs) |
| E-00040 | (General) The system shall present a page section header of : - "Logged-in user's account information" |
| E-00050 | (General) The system shall present the following user account information preceded with the appropriate field constant: - "Name" Last, (comma) First Middle - "Title/Position" Title/Position - "Organization" Organization Name, Level-2, Level-3 (establish a max-length for displaying all Organization fields, truncate if necessary - "Role" Role - use small font size to reduce percentage of the page needed to present this information This information shall be presented on several (perhaps all) logged-in pages to identify who a printed page belongs to. |
| E-00060 | (General) The system shall present a SENTRY Menu throughout the external application of all capabilities permitted based on user-function of the logged-in user. |
| E-00070 | (General) The system shall support five user roles based on these user-functions: Analyst, General User, Web Administrator, Help Desk, and Administrator; identified through the logged-in user's user-account record. Refer to "EXT Functionality Matrix" worksheet |
| E-00080 | (General) The system shall restrict each user's access to functionality based on his user-function. |
| E-00090 | (General) The system shall use a consistent method to identify all information the user is required to enter upon presentation of each page/form. |
| E-00100 | (General) The system shall ensure all required fields are present and compliant with editing rules for its page/form prior to saving the record. |
| E-00110 | (General) The system shall present error messages in a consistent, clear, and understandable format throughout the system. There shall be one error page that will display error messages based on the error which occurred. |
| E-00120 | (General) The system shall identify the page-of-pages a returned lists is positioned on and shall provide access to view each following-or-preceding page. |
| E-00130 | (General) The system shall store the user's identification, current date-and-time on each record when created. |
| E-00140 | (General) The system shall store the user's identification, current date-and-time on each record when edited. |
| E-00150 | (General) The system shall store and utilize dropdown lists that are maintained on the SENTRY internal application. |
| E-00160 | (General) The system shall store and utilize dropdown lists that are script loaded on both the SENTRY internal and external applications. |
| E-00170 | (General) The system provide the functionality for the user to sort returned lists by individual listed fields. |
| E-00180 | (General) The system shall include an initial auto-loaded administrator (user-function) user-account record. |
| E-00190 | (General) The system shall ignore search field parameters when they are not entered by the user. When the user chooses to search "Table A" and the user does not enter any search parameters the system shall return and list all "Table A" records. When the user enters search parameters into three-of-four parameter fields, the fourth field for which the user did not enter search parameters will not be considered in the query. |
| E-00200 | (General) The system shall display all record maintenance information fields on view and edit pages (Fields such as: Created-By, Date/Time Created, Edited-By, Date/Time Edited, and other similar fields). |
| E-00210 | (General) Record deletion, retention, and archive criteria needs to be determined. |
| (External - Landing Page) | |
| E-00220 | (Landing Page) The system shall present: - Information about SENTRY (What is SENTRY?) - How to request access (How Do I Participate?) - How to contact NDIC for reporting and resolution of unsuccessful login or other SENTRY problems (Contact Information) on the SENTRY landing page. The information will be supplied through a HTML document. |
| E-00230 | (Landing Page) The system shall provide functionality for each approved user that has an established, active, and unlocked user-account record to login to the SENTRY external web site. The system shall abide by all rules referenced in the Security and Accessibility sections of this document. |
| E-00240 | (Landing Page) The system shall save successful and unsuccessful logins into an audit log. The audit-log information record shall include the username, date/time, successful/unsuccessful, and if unsuccessful what reason stopped them from logging on. |
| E-00250 | (Landing Page) The system shall update the user-account record's MostRecentLogin field with the date/time of the successful login. |
| E-00260 | (Landing Page) The system shall set the Initial/Reset Password indicator to "No." |
| (External - Logged-In User / Home Page) | |
| E-00270 | (Home Page) The system shall provide a welcome message for each successfully logged-in user: The welcome message shall present the user's first and last name, such as "Welcome, John Smith". |
| E-00280 | (Home Page) The system shall provide each successfully logged-in user with a "list of" and "access to" active hyperlinked-documents and news-articles (if any posted). |
| E-00290 | (Home Page) The system shall open a separate window to access the hyperlinked-document, if the user chooses to access any that are posted and active). |
| E-00300 | (Home Page) The system shall provide each successfully logged-in user with menu options to access functionality permitted by his user-function. |
| (External - Change Password) | |
| E-00310 | (Change Password) The system shall provide each user with the functionality to change his password. |
| E-00320 | (Change Password) The system shall allow each user to choose to change his password. |
| E-00330 | (Change Password) The system shall require the user to change his password upon initial login, first login after reset of his password; password not changed within the required amount of time. (Refer to Security Section of this document for additional requirements.) |
| E-00340 | (Change Password) The system shall save all password changes in an audit log. Audit log information shall include the username, date/time password was changed, and whether user choose to change password or if time had expired on previous password. |
| (External - Submit Information also refer to SENTRY Requirements (Exhibits).xls / Exhibit {O} - Submit Info) |
|
| E-00350 | (Submit Information) The system shall provide functionality for users to submit information concerning drug related events-or-incidents. |
| E-00360 | (Submit Information) The system shall restrict the submit information functionality. (Refer to EXT Functionality Matrix) |
| E-00370 | (Submit Information) The system shall present information about the page: "Submit Information: For voluntary reporting of synthetic drug-related event or incident." |
| E-00380 | (Submit Information) The system shall present a section header for: "Logged-in user's account information" |
| E-00390 | (Submit Information) The system shall present the following user's information from his user-account-record: Last Name, (comma) First and Middle Name Title/Position Organization Name, (comma) Organization Level 2, (comma) Organization Level 3 Role User-function (on all logged in user pages ------------------------ The following City, State/Province/Territory, Zip/Postal Code, Country, and contact information may be viewed optionally City State/Province/Territory Zip/Postal Code Country Phone Number (Include Extension if any) FAX Number E-mail Address E-list Subscribed or Unsubscribed - precede each field-or-fields with field identification, such as, "Name" - use smaller font size to reduce percentage of the page needed to present this information Comment: The reason for presenting the user's information is that it allows the user to review and verify his information and to request its change when the information is incomplete or inaccurate; in addition when a logged-in user chooses to print-a-page his identification will be on the printout. |
| E-00400 | (Submit Information) The system shall present the following page section header: "Event-or-Incident Information" |
| E-00410 | (Submit Information) The system shall require the user to enter an approximate date (valid date format) of the event-or-incident. - The system shall edit the date to ensure it's a valid date and it's not a future date. |
| E-00420 | (Submit Information) The system shall allow the user to submit information for an event-or-incident that occurred within the United States of America, Canada, or Mexico. The following information formats must be internationalized when the event-or-incident information relates to Canada or Mexico. The system shall require that if the user is submitting information for within the United States of America the user will have to enter either the zip code or (city and state) of the event-or-incident. - If the user enters the zip code and either/or city and state, the system shall present an informative error message and require reentry of the field-or-fields. - If the user enters either city or state, but not both, the system shall present an informative error message and require reentry of the field-or-fields. - If the user enters only the zip code, the system shall use the zip code table to populate the city and state fields. - If the system populates the city and state fields from the zip code table the system shall present a message to the user that this was done and request the user to review results for accuracy. (An attempt to help the General User to recognize the entry of an erroneous zip code) - If the user chooses to enter city and state, the system shall support the entry of state with a dropdown list. |
| E-00430 | (Submit Information) The system shall require the entry of substance category. |
| E-00440 | (Submit Information) The system shall support user entry of substance category with a dropdown-list. |
| E-00450 | (Submit Information) The system shall require the user to enter the 'outcome attributed to the event-or-incident such as: death, abuse, seizure, investigation, etc.' |
| E-00460 | (Submit Information) The system shall require the user to enter the 'Drug/Chemical/Street Name' of the substance associated with the event-or-incident. |
| E-00470 | (Submit Information) The system shall require the user to enter information in the "Describe the Event-or-Incident" text-box |
| E-00480 | (Submit Information) The system shall require the user to activate the checkbox preceding the following message to activate it: 'Do not identify me or my organization as the submitter of this information within the SENTRY GIS map." |
| E-00490 | (Submit Information) The system shall ensure the user enters information that satisfies validity checks in all required fields prior to saving the submitted information. |
| E-00500 | (Submit Information) The system shall notify the user of all missing or invalid information and shall not save any of the submitted information until all fields are provided and valid. |
| E-00510 | (Submit Information) The system shall save the submitted information when the user has entered all required fields and all fields are valid. |
| E-00520 | (Submit Information) The system shall save the submitter's identification and the date/time submitted. |
| E-00530 | (Submit Information) The system shall present a confirmation that the information was successfully submitted. |
| E-00540 | (Submit Information) The system shall present the submitted information's tracking number (record identification) preceded with an identify constant of "Tracking Number." |
| E-00550 | (Submit Information) The system shall present the submitted date and time (mm/dd/yyyy hh:mm) preceded with an identifying constant of "Submitted Date / Time." |
| E-00560 | (Submit Information) The system shall present the user with the option to print the event-or-incident information they successfully submitted. |
| E-00570 | (Submit Information) The system shall provide a formatted printout for the submitted information that includes all: - Logged-in user's account information - Event-or-Incident Information - "Do not identify me or my organization….." and its checkbox - "Tracking Number" generated by the system when the submitted information record was saved (The submitted record's Tracking Number (record ident) needs to ensure uniqueness from all SENTRY internally submitted Tip Information records) - "Submitted Date / Time" generated by the system when the submitted information record was saved |
| E-00580 | (Submit Information) The system shall not provide for the printing of the event-or-incident information at any other time. |
| E-00590 | (Submit Information) The system shall not permit the viewing of submitted event-or-incident information by any user after the submitter has already submitted and printed the information. |
| E-00600 | (Submit Information) The system shall save submitted information to the audit log. Audit log information shall include the username, tip tracking number, date/time tip was submitted. |
| (External - Add User Account) | |
| E-00610 | (Add User Account) The system shall provide functionality for users to add external user-account records. |
| E-00620 | (Add User Account) The system shall restrict the add-user-account functionality. (Refer to EXT Functionality Matrix) |
| E-00630 | (Add User Account) The system shall require the user to enter the account record user's Organization Name. |
| E-00640 | (Add User Account) The system shall allow the user to enter the account record user's Organization Level 2. |
| E-00650 | (Add User Account) The system shall allow the user to enter the account record user's Organization Level 3. |
| E-00660 | (Add User Account) The system shall require the user to enter the account record user's Role. |
| E-00670 | (Add User Account) The system shall support user entry of Role with a dropdown-list. |
| E-00680 | (Add User Account) The system shall allow the user to enter information into the account record's Explain Other field. |
| E-00690 | (Add User Account) The system shall allow the user to enter the account record user's Title/Position. |
| E-00700 | (Add User Account) The system shall require the user to enter the account record user's First Name. |
| E-00710 | (Add User Account) The system shall allow the user to enter the account record user's Middle Name. |
| E-00720 | (Add User Account) The system shall require the user to enter the account record user's Last Name. |
| E-00730 | (Add User Account) The system shall require the user to enter the account record user's Address Line 1. |
| E-00740 | (Add User Account) The system shall allow the user to enter the account record user's Address Line 2. |
| E-00750 | (Add User Account) The system shall require the user to enter the account record user's City. |
| E-00760 | (Add User Account) The system shall require the user to enter the account record user's State, Province, or Territory. |
| E-00770 | (Add User Account) The system shall support user entry of State with a dropdown-list if the country is United States of America |
| E-00780 | (Add User Account) The system shall require the user to enter the account record user's zip or postal code (first five positions if in United States of America). |
| E-00790 | (Add User Account) The system shall require the user to enter the account record user's Country. There will only be three options: United States of America., Canada, and Mexico. |
| E-00800 | (Add User Account) The system shall support user entry of Country with a dropdown-list; the system shall preload the country field on the Add User Account page with "United States of America" |
| E-00810 | (Add User Account) The system shall include the following City/State/Country validity checks if the user is within the United States of America: - Regardless of country state/province/territory shall not be empty and zip/postal code shall not be empty. |
| E-00820 | (Add User Account) The system shall allow the user to enter information into the Contact Note field. |
| E-00830 | (Add User Account) The system shall require the user to enter the account user's phone number. Intel requires the following phone number formatting (111) 222-3333 Ext: 4444 with the user keying only the numeric portion if user is within the United States of America If the user is in Canada or Mexico the system will save up to 20 numbers for the phone number removing all non-numeric characters. |
| E-00840 | (Add User Account) The system shall allow the user to enter the account user's FAX number. Intel requires the following phone number formatting (111) 222-3333 with the user keying only the numeric portion if the user is within the United States of America If the user is in Canada or Mexico allow up to 20 characters for the fax number removing all non-numeric characters. |
| E-00850 | (Add User Account) The system shall require the user to enter the account record user's User Function. |
| E-00860 | (Add User Account) The system shall support user entry of User Function with a dropdown-list. |
| E-00870 | (Add User Account) The system shall require the user to enter the account record user's Username. |
| E-00880 | (Add User Account) The system shall assign a default password for the account user. |
| E-00890 | (Add User Account) The system shall set the Initial/Reset Password indicator to "Yes." |
| E-00900 | (Add User Account) The system shall set the e-list option as subscribed on each new user account record. The system shall allow the user to reset the e-list option to unsubscribed/subscribed. |
| E-00910 | (Add User Account) The system shall require an e-mail address if the user is to be subscribed to the e-list and the user-account record is active. |
| E-00920 | (Add User Account) The system shall set the active/inactive status to active on each new user-account record. The system shall allow the user to reset the status to inactive/active. |
| E-00930 | (Add User Account) The system shall set the unlocked/locked status to unlocked on each new user account record. The system shall not allow the user to change the unlocked status. Comment: The unlocked/locked status will be set to locked when the user fails the logon successfully -- too many failed password attempts. The unlocked/locked status will be set to unlocked when a new 'single-use' user password is generated in the EditUserAccount functionality. |
| E-00940 | (Add User Account) The system shall store the administrative user's identification in the Created-by column. |
| E-00950 | (Add User Account) The system shall store the date/time the new user account record is saved in the Created-Date/Time column. |
| E-00960 | (Add User Account) The system shall set the Edited-by column to nulls. |
| E-00970 | (Add User Account) The system shall set the Edited-Date/Time column to nulls |
| E-00980 | (Add User Account) The system shall set the E-ListEdited-by column to nulls. |
| E-00990 | (Add User Account) The system shall set the E-list Date/TimeEdited column to nulls. |
| E-01000 | (Add User Account) The system shall present a confirmation that the new user-account-record was successfully saved. |
| E-01010 | (Add User Account) The system shall save added user information to the audit log. The saved information shall include the Administrator's username who added the user, the username that was added, and the date/time the user was added. |
| (External - Search, List and Select User Accounts) | |
| E-01020 | (Search User Accounts) The system shall provide functionality for users to search, list, and select external user-account records. |
| E-01030 | (Search User Accounts) The system shall restrict the search, list, and select external user-account functionality. (Refer to the EXT Functionality Matrix) |
| E-01040 | (Search User Accounts) The system shall provide the user an option to enter data to search the following user-account-record columns: Last Name; Organization Name; State/Province/Territory; Role. |
| E-01050 | (Search User Accounts) The system shall support user entry of State with a dropdown-list. |
| E-01060 | (Search User Accounts) The system shall use data entered into the Organization Name field to search against the following user-account-record columns: Organization Name; Organization Level 2; and Organization Level 3. |
| E-01070 | (Search User Accounts) The system shall use the search-data entered to compare with each related user-account-record column's leftmost equal number of contiguous positions against search-data* (*plus a wildcard). Exception: The Organization fields shall be searched using a "contains" search. |
| E-01080 | (Search User Accounts) The system shall consider all searched columns as "and" conditions except the Organization Name, Organization Level 2 and Level 3 as "or" conditions within the Organization columns. Ex. If((Organization Name, or Organization Level 2, or Organization Level 3) and Last Name, State, and Role) return and list the record. |
| E-01090 | (Search User Accounts) The system shall display a list that contains the following columns of user-account-records that match all entered search data: Username; Last Name; First Name; Middle Name; City, State/Province/Territory, Zip Code; Country; Organization Name; Organization Level 2; Organization Level 3; Role; and E-mail Address left-to-right in the sequence of this list, ordered alphabetically by Last Name. |
| E-01100 | (Search User Accounts) The system shall allow the user to choose to access a user-account-record through selection of the Username listed for the record to access the EditUserAccount page. |
| E-01110 | (Search User Accounts) The system shall access the edit user-account-record page and present the user with the view/edit page with the selected user-account-record's data populating the user-account-record view/edit page's fields. |
| (External - Edit User Account) | |
| E-01120 | (Edit User Account) The system shall provide functionality for users to edit external user-account records. |
| E-01130 | (Edit User Account) The system shall restrict the edit-user-account functionality. (Refer to the EXT Functionality Matrix) |
| E-01140 | (Edit User Account) The system shall present the user with the view/edit user-account-record page with the selected user-account-record's data populating the user-account-record edit page's fields. |
| E-01150 | (Edit User Account) The system shall allow the user to edit the account user's Organization Name. |
| E-01160 | (Edit User Account) The system shall allow the user to edit the account user's Organization Level 2. |
| E-01170 | (Edit User Account) The system shall allow the user to edit the account user's Organization Level 3. |
| E-01180 | (Edit User Account) The system shall allow the user to edit the account user's Role. |
| E-01190 | (Edit User Account) The system shall support user editing of Role with a dropdown-list. |
| E-01200 | (Edit User Account) The system shall allow the user to edit the account record's Explain Other field. |
| E-01210 | (Edit User Account) The system shall allow the user to edit the account record user's Title/Position. |
| E-01220 | (Edit User Account) The system shall allow the user to edit the account user's First Name. |
| E-01230 | (Edit User Account) The system shall allow the user to edit the account user's Middle Name. |
| E-01240 | (Edit User Account) The system shall allow the user to edit the account user's Last Name. |
| E-01250 | (Edit User Account) The system shall allow the user to edit the account user's Address Line 1. |
| E-01260 | (Edit User Account) The system shall allow the user to edit the account user's Address Line 2. |
| E-01270 | (Edit User Account) The system shall allow the user to edit the account user's City. |
| E-01280 | (Edit User Account) The system shall allow the user to edit the account user's State/Province/Territory. |
| E-01290 | (Edit User Account) The system shall support user editing of State with a dropdown-list. |
| E-01300 | (Edit User Account) The system shall allow the user to edit the account user's zip-or-postal code (If zip code only the first five positions shall be entered). |
| E-01310 | (Edit User Account) The system shall allow the user to edit the account user's Country. |
| E-01320 | (Edit User Account) The system shall support user editing of Country with a dropdown-list. |
| E-01330 | (Edit User Account) The system shall include the following City/State/Country validity checks: - Regardless of country state/province/territory must not be blank and zip/postal code must not be blank. |
| E-01340 | (Edit User Account) The system shall allow the user to enter information into the Contact Note field. |
| E-01350 | (Edit User Account) The system shall allow the user to edit the account user's phone number. Intel requires the following phone number formatting (111) 222-3333 Ext: 4444 with the user keying only the numeric portion if the user is within the United States of America If the user is in Canada or Mexico allow up to 20 characters for the phone number removing all non-numeric characters. |
| E-01360 | (Edit User Account) The system shall allow the user to edit the account user's FAX number. Intel requires the following phone number formatting (111) 222-3333 with the administrative user keying only the number portion if the user is within United States of America If the user is in Canada or Mexico allow up to 20 characters for the phone number removing all non-numeric characters. |
| E-01370 | (Edit User Account) The system shall allow the user to edit the account user's User Function. |
| E-01380 | (Edit User Account) The system shall support user editing of User Function with a dropdown-list. |
| E-01390 | (Edit User Account) The system shall NOT allow the user to edit the account user's Username. |
| E-01400 | (Edit User Account) The system shall allow the user to generate a new single use default password for the account user. |
| E-01410 | (Edit User Account) The system shall allow the user to reset the e-list option to unsubscribed/subscribed. |
| E-01420 | (Edit User Account) The system shall allow the user to edit the account user's e-mail address; when the user's account record E-list option is set to subscribed, the system shall require the user to enter the e-mail address. |
| E-01430 | (Edit User Account) The system shall allow the user to reset the user account record status to active/inactive. |
| E-01440 | (Edit User Account) The system shall set the unlocked/locked status to unlocked and the Initial/Reset Password to "Yes" when the user generates a new single use password for the user. |
| E-01450 | (Edit User Account) The system shall store the administrative user's identification in the E-List Changed-by column and the record-saved date/time in the E-list Date/Time Edited column. |
| E-01460 | (Edit User Account) The system shall store the date/time the edited user account record is saved in the Changed-Date/Time column. |
| E-01470 | (Edit User Account) The system shall present a confirmation that the edited user-account-record was successfully saved. |
| E-01480 | (Edit User Account) The system shall save the editing of user accounts to the audit log. Information that shall be saved are the "Administrator" who performed the editing, the username of the account edited, and the date/time editing took place. |
| (External - View User Account) | |
| E-01490 | (View User Account) The system shall provide functionality for users to view external user-account records. |
| E-01500 | (View User Account) The system shall restrict the view-user-account functionality. (Refer to the EXT Functionality Matrix) |
| E-01510 | (View User Account) The system shall present all user account record fields that are presented on the Edit User Account page. All fields shall be view only. |
| (External - Reset User Account Password) | |
| E-01520 | (Reset User Password) The system shall provide functionality for users to reset external user-account password. |
| E-01530 | (Reset User Password) The system shall restrict the edit-user-account functionality. (Refer to the EXT Functionality Matrix) |
| E-01540 | (Reset User Password) The system shall not permit the user to reset the password when the user account record's status is "inactive." |
| E-01550 | (Reset User Password) The system shall provide functionality for the user to auto-generate and store an external user-account one-time use password. |
| E-01560 | (Reset User Password) The system shall reset the external user-account record's Account/Locked field. |
| E-01570 | (Reset User Password) The system shall set the external user-account record's Initial/Reset Password indicator to "Yes." |
| E-01580 | (Reset User Password) The system shall save the reset of user account passwords to the audit log. The system shall save the following Information: the username who performed the reset, the username of the account reset, and the date/time password reset took place. |
| (External - Manage E-List (Subscribe/Unsubscribe)) | |
| E-01590 | (Manage E-List) The system shall provide functionality for users to alter the e-list subscription option. If Subscribed then Unsubscribe; else if Unsubscribed then Subscribe. (Refer to EXT Functionality Matrix) |
| E-01600 | (Manage E-List) The system shall require the user to confirm their request to Subscribe or Unsubscribe. |
| E-01610 | (Manage E-List) The system shall present the user's e-mail address stored in his User-Account record and request the user to verify its accuracy. |
| E-01620 | (Manage E-List) The system shall require that the user provides an e-mail address when the E-list option is Subscribe. |
| E-01630 | (Manage E-List) The system shall store the user's identification in the E-list Changed-by column. |
| E-01640 | (Manage E-List) The system shall store the date/time the edited user account record is saved in the E-list Changed-Date/Time column. |
| E-01650 | (Manage E-List) The system shall provide the user with notification his e-list subscription option was accepted. |
| (External - Post Bulletin-Hyperlink) also refer to SENTRY Requirements (Exhibits).xls / Exhibit {Q} - PostViewEdit BulletinNews |
|
| E-01660 | (Post Bulletin-Hyperlink) The system shall provide functionality for administrative users to post a bulletin document-hyperlink. |
| E-01670 | (Post Bulletin-Hyperlink) The system shall restrict the post bulletin-document hyperlink functionality. (Refer to the EXT Functionality Matrix) |
| E-01680 | (Post Bulletin-Hyperlink) The system shall provide functionality for the user to associate the bulletin document-hyperlink with a document title, hyperlink-name, description, and active/inactive code. |
| E-01690 | (Post Bulletin-Hyperlink) The system shall provide the user with an option to verify access to the document-hyperlink. The linked-to document will be stored on the NDIC Internet web site. |
| E-01700 | (Post Bulletin-Hyperlink) The system shall store the user's identification Created-by field. |
| E-01710 | (Post Bulletin-Hyperlink) The system shall store the date-time the user created the bulletin document-hyperlink in the Created Date/Time field. |
| E-01720 | (Post Bulletin-Hyperlink) The system shall provide the user with notification the bulletin-hyperlink record was created. |
| E-01730 | (Post Bulletin-Hyperlink) The system shall save the posting of a bulletin into the audit log. Information that shall be saved are the "Web-Administrator" or "Administrator" who posted the Bulletin, Bulletin ID, and the date/time bulletin was posted. |
| (External - Post News Article) also refer to SENTRY Requirements (Exhibits).xls / Exhibit {Q} - PostViewEdit BulletinNews |
|
| E-01740 | (Post News Article) The system shall provide functionality for administrative users to post a news article. |
| E-01750 | (Post News Article) The system shall restrict the post news article functionality. (Refer to the EXT Functionality Matrix) |
| E-01760 | (Post News Article) The system shall provide functionality for the user to enter a news title, description, and active/inactive code. |
| E-01770 | (Post News Article) The system shall store the user's identification Created-by field. |
| E-01780 | (Post News Article) The system shall store the date-time the user created the news article in the Created Date/Time field. |
| E-01790 | (Post News Article) The system shall provide the user with notification the news-article record was created. |
| (External - Search Bulletin-Hyperlinks and News Articles also refer to SENTRY Requirements (Exhibits).xls / Exhibit {P} SearchSel Bulletins-News) |
|
| E-01800 | (Search Hyperlinks and News Articles) The system shall provide functionality for all users to search, list, and select bulletin document-hyperlinks and news articles. (Refer to EXT Functionality matrix) |
| E-01810 | (Search Hyperlinks and News Articles) The system shall provide functionality for users to search bulletin document-hyperlinks and news articles by "Date created range," "Title," and "Active/inactive code." |
| E-01820 | (Search Hyperlinks and News Articles) The system shall return a list of all bulletin document-hyperlinks and news articles that match entered search parameters. The following fields shall be listed: Title, Type (Bulletin-or-News), Created-By, Date Created, Edited-By, Date-Edited, and Status (Active/Inactive) ordered alphabetically by Title. The system shall NOT list Created-By and Edited-By fields when the user's User Function is "General User." |
| E-01830 | (Search Hyperlinks and News Articles) The system shall allow the user to select a listed bulletin document-hyperlink and news article to view or edit. |
| E-01840 | (Search Hyperlinks and News Articles) The system shall present the selected bulletin document-hyperlink or news article on a separate page for viewing or editing. |
| E-01850 | (Search Hyperlinks and News Articles) The system shall provide an option for the user to return from the view/edit page to the list of bulletin document-hyperlinks and news articles. |
| (External - Edit Bulletin-Hyperlink or News Article) also refer to SENTRY Requirements (Exhibits).xls / Exhibit {Q} - PostViewEdit BulletinNews |
|
| E-01860 | (Edit Hyperlink or News Article) The system shall provide functionality for administrative users to edit a selected bulletin document-hyperlink or news article. |
| E-01870 | (Edit Hyperlink or News Article) The system shall restrict the edit bulletin document-hyperlink and news article functionality. (Refer to EXT Functionality Matrix) |
| E-01880 | (Edit Hyperlink or News Article) The system shall provide functionality for the user to edit the bulletin document-hyperlink and news article's: Active/Inactive Status, Bulletin Document-Hyperlink, Document Title, and Document Description. The system shall store the user's username and the edited date/time when a changed record is saved. |
| E-01890 | (Edit Hyperlink or News Article) The system shall provide the user with an acknowledgment that the changed bulletin document-hyperlink or news article was successfully saved (including a notation identifying the type of record). |
| E-01900 | (Edit Hyperlink or News Article) The system shall provide an option for the user to return from the edit page to the list of bulletin document-hyperlinks and news articles. |
| E-01910 | (Edit Hyperlink or News Article) The system shall save the editing of a bulletin into the audit log. Information that shall be saved are the "Web-Administrator" or "Administrator" who edited the Bulletin/Hyperlink, Bulletin ID, and the date/time bulletin was edited. |
| (External - View Bulletin-Hyperlink or News Article) | |
| E-01920 | (View Hyperlink or News Article) The system shall provide functionality for users to view bulletin-hyperlink (and their linked-to document) and news articles. |
| E-01930 | (View Hyperlink or News Article) The system shall allow all users to view hyperlinks and news articles. (Refer to the EXT Functionality Matrix) |
| E-01940 | (View Hyperlink or News Article) The system shall present all bulletin-hyperlink and news-article fields that are presented on the Edit Hyperlink or News Article page. The system shall NOT present the Created-By and the Edited-By fields when the user's User Function is "General User." All fields shall be view only. |
| (External - View List of Active Bulletin-Hyperlinks and News Articles (Home Page)) | |
| E-01950 | (View List of Active Bulletin Document-Hyperlinks or News Articles) The system shall provide functionality for all users to view a list of active bulletin document-hyperlinks or news articles. (Refer to EXT Functionality Matrix) |
| E-01960 | (View List of Active Bulletin-Hyperlinks or News Articles) The system shall provide functionality for all users to select a bulletin document-hyperlink or news article's to view either the linked-to document or the news article's complete text. |
| (External - View External Audit-Trail Entries) | |
| E-01970 | (View Audit Trail) The system shall provide functionality for users to view the system audit-trail entries. |
| E-01980 | (View Audit Trail) The system shall restrict which user-function the view audit-trail. (Refer to EXT Functionality Matrix) |
| (External - View Sanitized Submitted Information in a GIS Map) | |
| E-01990 | (View Sanitized Information in GIS Map) The system shall provide functionality for all users to geographically view sanitized information by zip code. |
| E-02000 | The system shall use the ESRI ARC Spatial Data Engine (SDE) web software for geographically displaying submitted information. |
| E-02010 | The system shall expose a metalayer (view) of sanitized information by zip code to the ARC SDE. |
| E-02020 | The GIS interface shall be contained within the master page layout for the external SENTRY site. |
| E-02030 | Sanitized information shall be geocoded to zip code boundaries and viewable by all users. |
| (External - Help Text) | |
| E-02040 | (Help Text) The system shall provide instructional help text to guide all users with the primary emphasis on assisting external general users. The system shall assist all users through presenting pages and their related functionality and flow in an intuitive manner supported by help text when necessary. |
| (External - Retention of Original Submitted Information) | |
| E-02050 | (Retention) A determination needs to be made about whether each original submitted information record must be retained as entered. The possibility exists that personally identifiable information (PII), although not requested, may be included within information submitted. The externally submitted information record is passed to the SENTRY internal application where the PII shall be removed through edit of the original record by an Administrator user. Therefore, if the original record needs to be retained it must be captured prior to any editing. |
| Security (SEC) | |
| Req. ID - Rev. | Requirement |
| E-SEC001 | Every user that logs into SENTRY shall have a unique user id. (DOJ Standard 2640.2D - 17a.). |
| E-SEC002 | The system shall prevent multiple concurrent active sessions for one user identification. (DOJ Standard 2640.2D - 16b) If this is deemed impossible based on operational need, the system must then provide a user notification to identify that the user session is active in another location. |
| E-SEC003 | The system shall prevent the use of the previous six passwords. (DOJ Standard 2640.2D – 18b2.). |
| E-SEC004 | The system shall limit the password lifetime to a maximum of 90 days. (DOJ Standard 2640.2D – 18b4.). |
| E-SEC005 | The system shall expire an initial use password at the time of its first use in a manner that requires the password owner to supply a new password. (DOJ Standard 2640.2D – 18b5.) |
| E-SEC006 | The system shall maintain an audit trail of activity sufficient to reconstruct security relevant events. (DOJ Standard 2640.2D – 19a1.) |
| E-SEC007 | The audit trail should include the identification of each entity accessing the system, time and date of the access, time and date the entity terminating access, activities performed using an administrator’s identification, and activities that could modify, bypass, or negate the system security safeguards. (DOJ Standard 2640.2D – 19a2.) |
| E-SEC008 | The system shall protect the audit trail from actions such as unauthorized access, modification, and destruction that would negate its forensic value. (DOJ Standard 2640.2D – 19a3.) |
| E-SEC009 | The system shall retain the audit trail for a period of 90 days at a minimum. (DOJ Standard 2640.2D – 19a4.) |
| E-SEC010 | The system shall require the system administrator to issue initial passwords. (DOJ Standard 2640.2D - 18a.) |
| E-SEC011 | The system shall require an eight-character password composed of at least three of the following: uppercase, lower case, numeric, special characters. (DOJ Standard 2640.2D – 18b1.) |
| E-SEC012 | The system shall disable user accounts after no more than four consecutive invalid attempts are made to supply a password, and require the reinstatement of a disabled user account by an administrator. (DOJ Standard 2640.2D – 18g.) |
| E-SEC013 | The system shall prevent the display of clear text passwords. (DOJ Standard 2640.2D – 18b3.) |
| E-SEC014 | The system shall prevent the capture and viewing of passwords through operating or application system features that may allow an individual access to a clear text password or a password in any form that can be replayed. (DOJ Standard 2640.2D – 18c.) |
| E-SEC015 | The system shall disable system default passwords as soon as possible after system installation and before the system becomes operational. (DOJ Standard 2640.2D – 18d.) |
| E-SEC016 | The system shall store passwords in an encrypted form. (DOJ Standard 2640.2D – 18e.) |
| E-SEC017 | The system shall require the user to login again anytime the user's session remains idle for 20 minutes or longer. |
| Accessibility (ACC (Section 508)) | |
| Req. ID - Rev. | Requirement |
| E-ACC001 | The system shall provide a text equivalent for every non-text element. |
| E-ACC002 | Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. |
| E-ACC003 | Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup. |
| E-ACC004 | Documents shall be organized so they are readable without requiring an associated style sheet. |
| E-ACC005 | Redundant text links shall be provided for each active region of a server-side image map. |
| E-ACC006 | Client-side image maps shall be provided instead of server-side image maps except where the regions cannot be defined with an available geometric shape. |
| E-ACC007 | Row and column headers shall be identified for data tables. |
| E-ACC008 | Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers. |
| E-ACC009 | Frames shall be titled with text that facilitates frame identification and navigation. |
| E-ACC010 | Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz. |
| E-ACC011 | A text-only page, with equivalent information or functionality, shall be provided to make a web site comply with the provisions of this section, when compliance cannot be accomplished in any other way. The content of the text-only page shall be updated whenever the primary page changes. |
| E-ACC012 | When pages utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by assistive technology. |
| E-ACC013 | When electronic forms are designed to be completed on-line, the form shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues. |
| E-ACC014 | A method shall be provided that permits users to skip repetitive navigation links. |
| E-ACC015 | When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. |
| Non Functional (NF) | |
| Req. ID - Rev. | Requirement |
| E-NF001 | The system shall be developed in Microsoft Visual Studio 2005. |
| E-NF002 | The system shall be developed in Microsoft Visual Basic.NET 2005. |
| E-NF003 | The system shall be developed in ASP.NET 2.0. |
| E-NF004 | The system shall use SQL Server 2005. |
| E-NF005 | The system shall use Windows Server 2003. |
| E-NF006 | Each component of the system shall have an install package. |
| Performance (PRF) | |
| Req. ID - Rev. | Requirement |
| E-PRF001 | The system shall be scalable. (scale out) Each tier of the system shall be written to accommodate multiple installations on one or more machines. |
| E-PRF002 | The system should scale linearly when increasing concurrent users and the amount of data. |
| E-PRF003 | The system shall initially be written to support 10-50 concurrent users. |
| E-PRF004 | The response time for a client shall not be more than 2 seconds for a given concurrent load. |
| Functionality | User Function | |||||
| No. | Title / Description | Analyst | General User |
WEB Admin |
Help Desk |
Admin |
| 1 | SENTRY Landing Page (Before Login) (What is SENTRY?) (How Do I Participate?) (Login Control) (Contact Information) |
N/A | N/A | N/A | N/A | N/A |
| 2 | Login | x | x | x | x | x |
| 3 | Home Page - View "What's New?" Bulletins and News Articles Titles and Descriptions | x | x | x | x | x |
| 4 | Submit Information | x | x | |||
| 5 | User-Account Records - Search, List and Select | x | x | x | ||
| 6 | User-Account Records - Reset Password / Unlock Account | x | x | |||
| 7 | User-Account Records - Add/Edit (Includes Reset Password / Unlock Account) | x | ||||
| 8 | User-Account Records - View | x | x | x | ||
| 9 | Bulletins and News Articles - Search, List, and Select | x | x | x | x | x |
| 10 | Bulletins and News Articles - Post/Edit | x | x | |||
| 11 | Bulletins and News Articles - View | x | x | x | x | x |
| 12 | Manage E-List (Subscribe/Unsubscribe and verify e-mail address) | x | x | x | x | x |
| 13 | Change Password (Initial, Reset & Expired Password requires change, also allow User to Change on Demand) |
x | x | x | x | x |
| 14 | View Sanitized Information in GIS Map | x | x | x | x | x |
| 15 | View External Audit-Trail Entries | x | x | |||
| 16 | Maintain Role Dropdown List Table (Maintained on Internal application; available on External) | |||||
| 17 | Maintain Country Dropdown List Table (Maintained on Internal application; available on External) | |||||
| 18 | Maintain Substance Category Dropdown List Table (Maintained on Internal application; available on External) | |||||
| 19 | ||||||
| 20 | ||||||
| Intranet Web Site | |
| Req. ID - Rev. | (Function) Requirement |
| (Internal - General) | |
| I-00010 | (General) The system shall use Windows authentication to process each login attempt; a successful login must include: - Receipt of the user's Justice Network System (JNS) username - Receipt of the user's valid JNS SENTRY User-Role/Function (Analyst or Administrator) |
| I-00020 | (General) The system shall provide user notification of any failed attempt to login. The notification message shall include the JNS/SENTRY username and reason for failed login attempt. |
| I-00030 | (General) The system shall present a banner (header) at the top of each page/form used throughout SENTRY intranet site. |
| I-00040 | (General) The system shall present the NDIC seal at the top left-corner of the banner. |
| I-00050 | (General) The system shall present a consistent banner (header) to the right of the NDIC seal that includes the following: U. S. Department of Justice National Drug Intelligence Center SENTRY A synthetic drug early warning and response system (Comment: System handles other than synthetic drugs) |
| I-00060 | (General) The system shall present a page section header that includes: - Logged-in user's JNS/Username & Name (Last, First Middle) and User Function (Analyst or Administrator) - use small font size to reduce percentage of the page needed to present this information This information shall be presented on several (perhaps all) logged-in pages to identify who a printed page belongs to. |
| I-00070 | (General) The system shall present a SENTRY shield on the SENTRY landing page upon successful user login. |
| I-00080 | (General) The system shall support two user roles based on user-function: Analyst and Administrator. |
| I-00090 | (General) The system shall provide a menu of functionality available to each logged-in user based on his user function. (Refer to INT Functionality Matrix) |
| I-00100 | (General) The system shall restrict each user's access to functionality based on his user-function. |
| I-00110 | (General) The system shall use a consistent method to identify all information the user is required to enter upon presentation of each page/form. |
| I-00120 | (General) The system shall ensure all required fields are present and compliant with editing rules for its page/form prior to saving the record. |
| I-00130 | (General) The system shall present error messages in a consistent, clear, and understandable format throughout the system. There shall be one error page that will display error messages based on the error which occurred. |
| I-00140 | (General) The system shall identify the page-of-pages a returned lists is positioned on and shall provide access to view each following-or-preceding page. |
| I-00150 | (General) The system shall store the user's identification, current date-and-time on each record when created. |
| I-00160 | (General) The system shall store the user's identification, current date-and-time on each record when edited. |
| I-00170 | (General) The system shall store and utilize dropdown lists that are maintained on the SENTRY internal application. |
| I-00180 | (General) The system shall store and utilize dropdown lists that are script loaded on both the SENTRY internal and external applications. |
| I-00190 | (General) The system provide the functionality for the user to sort returned lists by individual listed fields. |
| I-00200 | (General) The system shall ignore search field parameters when they are not entered by the user. When the user chooses to search "Table A" and the user does not enter any search parameters the system shall return and list all "Table A" records. When the user enters search parameters into three-of-four parameter fields, the fourth field for which the user did not enter search parameters will not be considered in the query. |
| I-00210 | (General) The system shall display all record maintenance information fields on view and edit pages (Fields such as: Created-By, Date/Time Created, Edited-By, Date/Time Edited, and other similar fields). |
| I-00220 | (General) The Note and Research Item records shall not have a record status field; these records shall assume the status of the Project, Relationship, or Tip Information record they are linked-to. |
| I-00230 | (General) Record deletion, retention, and archive criteria needs to be determined. |
| (Internal - Pages (NDIC Seal and Banner)) | |
| I-00240 | The system shall display the NDIC Seal and Banner on all internal and external pages. |
| I-00250 | The system shall display the NDIC Seal in the upper left corner of the page. |
| I-00260 | The system shall display a Banner depicting the U.S. Department of Justice, National Drug Intelligence Center, SENTRY, and "A synthetic drug early warning and response system" in the remaining area at the top of the page. |
| (Internal - Pages (Logged-In User's Information)) | |
| I-00270 | The system shall present the Logged-In User's Information: JNS/Username and Name (Last, First Middle) and User Function (Analyst/Administrator) on all internal pages. |
| I-00280 | The system shall present the Logged-In User's Information at the top of the page just below the Seal and Banner. The system shall use the JNS/Username-Name(Last, First Middle) table to convert from username-to-name. |
| (Internal - Pages (Project Section)) | |
| I-00290 | The system shall present the Project Section when a Tip, Note, or Research Item that is directly-or-indirectly linked to a Project record is being displayed for view or edit. Also, when a Note or Research Item is about to be added and linked directly to a Project or linked indirectly through a Relationship record or Tip Information Record. |
| I-00300 | The Project Section presented shall include the following Project record information: Title, Assigned-To, Created-By, Date Created, Edited-By, Date Edited, Status & Project Record Identification |
| I-00310 | When applicable the Project record information shall be presented beneath the logged-in user's information. |
| I-00320 | When a Relationship record is linked-to multiple Project records, or a Tip Information record is linked-to multiple Relationship records that are linked-to different Project records, the system shall repeat the Project/Relationship listing to properly identify each directly-or-indirectly linked-to Project record. |
| (Internal - Pages (Relationship Section)) | |
| I-00330 | The system shall present the Relationship Section when a Tip, Note, or Research Item that is directly-or-indirectly linked to a Relationship record is being displayed for view or edit. Also, when a Note or Research Item is about to be added and linked directly to a Relationship or linked indirectly through a Tip Information Record. |
| I-00340 | The Relationship Section presented shall include the following Relationship record information: Summary, Created-By, Date-Created, Edited-By, Date Edited, Status & Relationship Record Identification. |
| I-00350 | When applicable the Relationship record information shall be presented beneath its related Project record information line. |
| I-00360 | When a Tip Information record is linked-to multiple Relationship records that are linked-to different Project records, the system shall repeat the Project/Relationship listing to properly identify each directly-or-indirectly linked-to Relationship record. |
| (Internal - Tip Information Section) | |
| I-00370 | The system shall present the Tip Information Section when a Tip Information record is being added, viewed, or edited; also when a Note or Research Item linked-to (or, to be linked-to) a Tip Information record is being added, viewed, or edited. |
| I-00380 | The system shall present the Tip Information Section comprised of the following sub-sections: - Submitter's Identification or Source-of-Information - Event-or-Incident |
| (Internal - Tip Submitter's Identification or Source-of-Information Sub-Section) | |
| I-00390 | The system shall present one of the following sub-headers for the Tip Information Section: - Submitter's Identification for externally submitted tips * Submitter's Identification (externally submitted tip information records always linked-to a User-Account record - Source-of-Information for tips entered internally by an Administrator user * Source-of-Information (internally submitted tips can be linked-to either a Source-Identification or a User-Account record |
| I-00400 | The system shall present the following Submitter's Identification or Source-of-Information following the sub-header mention in the preceding requirement: Name (Last, First Middle) Organization Name, Org. Level 2, Org. Level 3 Title/Position Role Phone FAX E-mail Address |
| (Internal -Tip Event-or-Incident Sub-Section) |
|
| I-00410 | The system shall present the following Event-or-Incident information: Tip Number, Tip Status, Submitted Date/Time, Edited-By, Edited Date/Time Approximate Date (of event-or-incident) Location's City, State/Province/Territory, Zip or Postal Code Substance Category Outcome Drug/Chemical/Street Name |
| (Internal - JNS/Username - Name Table) | |
| I-00420 | The system shall provide for script loading of the JNS/Username - Name Table. |
| I-00430 | The system shall provide functionality for the Administrator user to maintain the JNS/Username - Name Table. |
| I-00440 | The system shall use the JNS/Username - Name Table to convert each logged-in or stored username to the user's name (last, first & middle) for display. |
| (Internal - Add/View/Edit Project Records) | |
| I-00450 | (Add/View/Edit Project) The system shall allow all users to add and view Project records. |
| I-00460 | (Add/View/Edit Project) The system shall restrict editing Project records to administrator users. (Refer to INT Functionality Matrix) |
| I-00470 | (Add/View/Edit Project) The system shall allow all users to add and view the Project record's title, description, and status fields. |
| I-00480 | (Add/View/Edit Project) The system shall restrict the editing of the Project record's title, description, and status fields. |
| I-00490 | (Add/View/Edit Project) The system shall set the Created-By field to the username of the user who adds the project. |
| I-00500 | (Add/View/Edit Project) The system shall set the Date-Created to the date/time when the user creates the project. |
| I-00510 | (Add/View/Edit Project) The system shall set the Edited-By field to the username of the administrator who edited the project. |
| I-00520 | (Add/View/Edit Project) The system shall set the Date-Edited to the date/time when the user saves the edited project record. |
| I-00530 | (Add/View/Edit Project) The system shall display the created-by user's last name, first name, and middle name when displaying the Created-By field. |
| I-00540 | (Add/View/Edit Project) The system shall display the edited-by user's last name, first name, and middle name when displaying the Edited-By field. |
| I-00550 | (Add/View/Edit Project) The system shall display a save/add project record confirmation message upon successful completion of the save/add. |
| I-00560 | (Add/View/Edit Project) The system shall log the save/add project record event in the system audit-trail. |
| (Internal - Add/View/Edit Relationship Records) | |
| I-00570 | (Add/View/Edit Relationship) The system shall allow all users to add and view Relationship records. |
| I-00580 | (Add/View/Edit Relationship) The system shall restrict editing Relationship records to administrator users. (Refer to INT Functionality Matrix) |
| I-00590 | (Add/View/Edit Relationship) The system shall allow all users to add and view the Relationship record's summary, description, and status fields. |
| I-00600 | (Add/View/Edit Relationship) The system shall restrict the editing of the Relationship record's summary, description, and status fields. |
| I-00610 | (Add/View/Edit Relationship) The system shall set the Created-By field to the username of the user who adds the Relationship record. |
| I-00620 | (Add/View/Edit Relationship) The system shall set the Date-Created to the date/time when the user creates the Relationship record. |
| I-00630 | (Add/View/Edit Relationship) The system shall set the Edited-By field to the username of the administrator who edited the Relationship record. |
| I-00640 | (Add/View/Edit Relationship) The system shall set the Date-Edited to the date/time when the user saves the edited Relationship record. |
| I-00650 | (Add/View/Edit Relationship) The system shall display the created-by user's last name, first name, and middle name when displaying the Created-By field. |
| I-00660 | (Add/View/Edit Relationship) The system shall display the edited-by user's last name, first name, and middle name when displaying the Edited-By field. |
| I-00670 | (Add/View/Edit Relationship) The system shall display a save/add relationship record confirmation message upon successful completion of the save/add. |
| I-00680 | (Add/View/Edit Relationship) The system shall log the save/add relationship record event in the system audit-trail. |
| (Internal - Add Tip Information Record) | |
| I-00690 | (Add Tip) The system shall provide a way to enable or disable the functionality through which tip information records can be entered internally. The enabling/disabling of this functionality shall be controlled through NDIC's Technical Services Branch upon request from the Intel Division's Collections Management Group. |
| I-00700 | (Add Tip) The system shall restrict the add tip information functionality to Administrator users. (Refer to INT Functionality Matrix) |
| I-00710 | (Add Tip) The system shall display the Add/View/Edit Tip Information Section header. |
| I-00720 | (Add Tip) The system shall display the "Source of Information for Tip Entered Internally by (Administrator's Name, that's entering the tip information). |
| I-00730 | (Add Tip) The system shall require the user to select a source-of-information record for the purpose of linking the new tip information record to it. |
| I-00740 | (Add Tip) The system shall support the selection of a source-of-information record through the Search/List/Select Source-of-Information Records documented later in this requirements document. |
| I-00750 | (Add Tip) The system shall allow the user to reselect a source-of-information record, the preceding record selection might be incorrect and needs to be reselected. |
| I-00760 | (Add Tip) The system shall display the name(last, first, middle), organization 1-3, title/position, role, phone, fax, and e-mail of the source-of-information for the tip information record being entered. |
| I-00770 | (Add Tip) The system shall display the Event-or-Incident Section header. |
| I-00780 | (Add Tip) The system shall not initially display a tip number. The tip number shall be assigned when the tip information record is saved (added); the system shall display a confirmation message that the tip information record was successfully saved, the system shall present the tip number at that time. |
| I-00790 | (Add Tip) The system shall ensure the tip information record's identification field (Tip Number) is unique and does not duplicate record identification numbers created by the external application. (Perhaps include the letter "E" for externally submitted records and an "I" for internally added records) |
| I-00800 | (Add Tip) The system shall assign the status of "Active" for the tip being entered. |
| I-00810 | (Add Tip) The system shall allow the user to change the tip status field. |
| I-00820 | (Add Tip) The system shall support user entry of Status with a dropdown-list. |
| I-00830 | (Add Tip) The system shall require the user to enter the approximate date of the event-or-incident. The system shall ensure the date is a standard format and is not a future date. |
| I-00840 | (Add Tip) The system shall require the user to enter the event-or-incident's location: country, city, state/province/territory, and zip-or-postal code. |
| I-00850 | (Add Tip) The system shall preload the country field with the "United States of America" |
| I-00860 | (Add Tip) The system shall support user entry of country with a dropdown list. |
| I-00870 | (Add Tip) The system shall support user entry of state with a dropdown list when the country field is the "United States of America". |
| I-00880 | (Add Tip) The system shall require the user to enter the substance category. |
| I-00890 | (Add Tip) The system shall support the entry of substance category with a dropdown list. |
| I-00900 | (Add Tip) The system shall require the user to enter the event-or-incident's outcome. |
| I-00910 | (Add Tip) The system shall require the user to enter the drug/chemical/street name of substance involved in the event-or-incident. |
| I-00920 | (Add Tip) The system shall set the initial contact made field to "Yes" since the source-of-information for the tip information submitted it through NDIC's Collections Management Group. |
| I-00930 | (Add Tip) The system shall preload the contacted-by field to the user who is adding the tip information record. The system shall allow the user to enter a different contacted-by username. |
| I-00940 | (Add Tip) The system shall support user entry of username with a dropdown list from the JNS/Username/Name table. |
| I-00950 | (Add Tip) The system shall require the user to enter the contacted date and time fields. The system shall require the date and time fields to be standard formats. The system shall ensure the date/time fields are not in the future. |
| I-00960 | (Add Tip) The system shall require the user to enter the detailed description of the event-or-incident. |
| I-00970 | (Add Tip) The system shall allow the user to enter the sanitized tip description. The system shall provide functionality that supports the user copying the entire detailed description into the sanitized tip description. The system shall allow the user to further modify either the detailed description or the sanitized tip description. |
| I-00980 | (Add Tip) The system shall require the user to enter whether or not to "display the sanitized tip description in the external GIS map" |
| I-00990 | (Add Tip) The system shall require the user to enter the "Yes/No or check box" choice for "Do not identify me or my organization as the submitter of this information within the SENTRY GIS map" |
| I-01000 | (Add Tip) The system shall ensure all required fields are entered and all field entered pass their validity checking (if any). If field requirements are not met the system shall present an appropriate error message and shall not save (add) the tip information record until field requirements are met. |
| I-01010 | (Add Tip) The system shall allow the user to save (add) the tip information record when field requirements are met. The system shall populate the submitted date/time fields with the current date/time when the record is added. The submitted date/time shall be displayed when the save/add confirmation message is displayed. |
| I-01020 | (Add Tip) The system shall display a save/add tip information record confirmation message upon successful completion of the save/add. |
| I-01030 | (Add Tip) The system shall log the save/add tip information record event in the system audit-trail. |
| I-01040 | (Add Tip) The system shall allow the user to access functionality to add a note or research item record that can be linked to this newly added tip information record. |
| (Internal - View Tip Information Record) | |
| I-01050 | (View Tip) The system shall present the following applicable sections (referred to earlier in this document) for view: - NDIC Seal and Banner - Logged-in User Section - Project Section - Relationship Section - Tip Submitter's Identification or Source of Information Section - Event-or-Incident Section |
| I-01060 | (View Tip) Following these sections the following Tip Information record fields shall be presented: - Initial Contact, Contacted-By, Contacted Date and Time - Detailed Description - Sanitized Tip Description - Display Sanitized Tip (yes/No) - Selection for "Do not identify me or my organization as the submitter of this information within the SENTRY GIS map |
| I-01070 | (View Tip) The system shall allow the user to access functionality to add/view/edit a note or research item record that is or can be linked to this tip information record. |
| (Internal - Edit Tip Information Record) | |
| I-01080 | (Edit Tip) The system shall present the following applicable sections (referred to earlier in this document) for view: - NDIC Seal and Banner - Logged-in User Section - Project Section - Relationship Section |
| I-01090 | (Edit Tip) The system shall present the following applicable sections (referred to earlier in this document) for view and possible edit: - Tip Submitter's Identification or Source of Information Section * Tip Submitter's Identification (The Linked-to User-Account record can NOT be changed or deleted) * The linked-to Source of Information record for an internally submitted Tip Information record may be altered, it may be necessary to re-link the source to a different Source Identification or User-Account record; the previous linked-to record may be incorrect |
| I-01100 | (Edit Tip) Following the Submitter's Identification or Source of Information Section the following Event-or-Incident fields shall be presented: Tip Number (Can NOT be changed, informational only) - Status (If changed, user entry supported by dropdown list) - Submitted Date/Time (Can Not be changed, informational only) - Edited-By (Informational, shall be changed by the system if the record is edited and saved) - Edited Date/Time (Informational, shall be changed by the system if the record is edited and saved) |
| I-01110 | (Edit Tip) The system shall NOT permit the user to change the Tip Information Status field to "New" or "Active" when the Tip Information record is linked to one-or-more Relationship records. |
| I-01120 | (Edit Tip) The system shall present these additional Event-or-Incident fields for view and possible edit: - Event-or-Incident Approximate Date - Location's: Country, City, State/Province/Territory (state supported by dropdown list), Zip or Postal Code - Substance Category (supported by dropdown list) - Outcome - Drug/Chemical/Street Name - Initial Contact, Contacted-By, Contacted Date and Time - Detailed Description - Sanitized Tip Description - Display Sanitized Tip (yes/No) - Selection for "Do not identify me or my organization as the submitter of this information within the SENTRY GIS map |
| I-01130 | (Edit Tip) The system shall allow the user to enter/edit the sanitized tip description. The system shall provide functionality that supports the user copying the entire detailed description into the sanitized tip description. The system shall allow the user to further modify either the detailed description or the sanitized tip description. |
| I-01140 | (Edit Tip) The system shall ensure all edited fields include required data and passes validity checks. If required data not present or invalid, the system shall present appropriate error message(s) and shall not allow the edited record to be saved until all fields in error are corrected. (Field requirements and validity checking same as documented in the Add Tip Information Record section) |
| I-01150 | (Edit Tip) The system shall allow the user to save the edited record when it passes field requirement and validity checks. |
| I-01160 | (Edit Tip) The system shall display a save/add tip information record confirmation message upon successful completion of the save/add. |
| I-01170 | (Edit Tip) The system shall log the Tip Information Record editing event. |
| I-01180 | (Edit Tip) The system shall allow the user to access functionality to add/view/edit a note or research item record that is or can be linked to this tip information record. |
| (Internal - Add/View/Edit Note also refer to SENTRY Requirements (Exhibits).xls / Note (Exhibit - I)) |
|
| I-01190 | (Add/View/Edit Note) The system shall allow all users to add and view Initial Contact Information and Note records. The system shall restrict editing/deleting of these same items. (Refer to INT Functionality Matrix) |
| I-01200 | (Add/View/Edit/Note) The system shall support the selection of a source-of-information record through the Search/List/Select Source-of-Information Records documented later in this requirements document. |
| I-01210 | (Add/View/Edit/Note) The system shall support the user option to carry-forward the Tip Information record's linked-to Source-of-Information record when the note-or-research item record being added-or-edited is linked-to the Tip. |
| I-01220 | (Add/View/Edit Note) Initially blank, the system shall allow the user to enter the following Initial Contact information: ([ ], Yes/No), Contacted By, Date, and Time. After initial entry, the system will present these fields to the user. |
| I-01230 | (Add/View/Edit Note) The system shall allow the user to select a Dissemination Restriction (supported by dropdown list) when adding or editing a Note. |
| I-01240 | (Add/View/Edit Note) Initially blank, the system shall present the Created-By (name of the user who created the Note), followed by the Date/Time once the note has been saved. |
| I-01250 | (Add/View/Edit Note) Initially blank, the system shall present the Edited-By (name of the user who last edited the Note), followed by the Date/Time. |
| I-01260 | (Add/View/Edit Note) The system shall allow the user to select the Contact Type (supported by dropdown List). |
| I-01270 | (Add/View/Edit Note) The system shall allow the user to select the Initial Contact (Blank or Yes/No dropdown), and enter the Contact Date, Contact Time, Explain Other (Contact Type "Other" supported by dropdown list; explain in free text), and the actual |
| I-01280 | (Add/View/Edit Note) The system shall require the user to enter data into the Note's Text field. |
| I-01290 | (Add/View/Edit Note) The system shall provide user access to functionality to add a Note or Research Item record linked to a Project, Relationship, or Tip Information record. (The Note or Research Item record shall be linked-to the Tip Information record if presented, else the Relationship record if presented, else the Project record. Access to the AddViewEditNote page shall be limited to the following pages: (Exhibit {B} - Proj-Rel-Notes-Res) Records added (created) through this access point shall be linked-to the Project (Exhibit {D} - Rel-Notes-Res-Tips) Records added (created) through this access point shall be linked-to the Relationship unless the user identified a specific Tip record (Exhibit - {GH} - Add/View/Edit Tip) the added Note or Research Item record is to be linked-to) |
| I-01300 | (Add/View/Edit Note) The system shall present the user with a confirmation message that the new-edited-or-deleted Note or Research Item record was successfully saved-or-deleted. |
| I-01310 | (Add/View/Edit Note) The system shall log the addition/editing/deletion of Note and Research item records. |
| I-01320 | (Add/View/Edit Note) The system shall allow the user to add an additional Note or Research Item record to be linked-to this same Project, Relationship, or Tip. The system shall provide the user with the option to carry-forward the same source-of-information record for each additional Note or Research Item record. |
| I-01330 | (AddViewEdit Note) The system shall allow the user to scroll-up to the previous Notes or Research Items or scroll-down to the next one linked to this same Project, Relationship, or Tip. (Notes and Research Item records shall be ordered in reverse chronological order of Date-Created and record types may be interspersed) The system shall continue to present the content of the upper portion of the page which shows the Project, Relationship, and Tip Information dependent on which level the Notes and Research Item records are being linked-to. |
| (Internal - Add/View/Edit Research Item Information also refer to SENTRY Requirements (Exhibits).xls / Abuse (Exhibit - J)) |
|
| I-01340 | (Add/View/Edit Abuse) The system shall allow all users to add and view Abuse Information (Research Item) records. The system shall restrict editing/deleting of these same items. (Refer to INT Functionality Matrix) |
| I-01350 | (Add/View/Edit Abuse) The system shall support the selection of a source-of-information record through the Search/List/Select Source-of-Information Records documented later in this requirements document. |
| I-01360 | (Add/View/Edit Abuse) The system shall require the user to enter the type of Research Item Information record to be added (created). The user entry of Research Item information type shall be supported by a dropdown list. The dropdown list shall contain the following Research Item information types: (Abuse, Production, Packaging, Distribution, Public Awareness) The Research Item Information record type shall not be changed through the edit function. |
| I-01370 | (Add/View/Edit Abuse) The system shall allow the user to select a Dissemination Restriction (supported by dropdown list) when adding or editing an Abuse Information Record. |
| I-01380 | (Add/View/Edit Abuse) Initially blank, the system shall present the Created-By (name of the user who created the Abuse Information Record), followed by the Date/Time once the Abuse Information record has been saved. |
| I-01390 | (Add/View/Edit Abuse) Initially blank, the system shall present the Edited-By (name of the user who last edited the Abuse Information Record), followed by the Date/Time. |
| I-01400 | The system shall allow the user to select the Abuse Information Records Route of Administration (supported by dropdown list) and Gender of Population Involved (supported by dropdown list); and enter the Socioeconomic Group Involved (free text field). |
| I-01410 | (Add/View/Edit Abuse) The system shall allow the user to enter the following Abuse Information Record fields with accompanying/required To/From Date Ranges: Number of Treatment Admissions Number of Individuals Arrested Number of Emergency Room Mentions Number of Deaths Number of Non-Fatal Overdoses |
| I-01420 | (Add/View/Edit Abuse) The system shall allow the user to enter Abuse Information Comments. |
| I-01430 | (Add/View/Edit Abuse) The system shall provide user access to functionality to add a Note or Research Item record linked to a Project, Relationship, or Tip Information record. (The Note or Research Item record shall be linked-to the Tip Information record if presented, else the Relationship record if presented, else the Project record. Access to the AddViewEditNote page shall be limited to the following pages: (Exhibit {B} - Proj-Rel-Notes-Res) Records added (created) through this access point shall be linked-to the Project (Exhibit {D} - Rel-Notes-Res-Tips) Records added (created) through this access point shall be linked-to the Relationship unless the user identified a specific Tip record (Exhibit - {GH} - Add/View/Edit Tip) the added Note or Research Item record is to be linked-to) |
| I-01440 | (Add/View/Edit Abuse) The system shall present the user with a confirmation message that the new-edited-or-deleted Note or Research Item record was successfully saved-or-deleted. |
| I-01450 | (Add/View/Edit Abuse) The system shall log the addition/editing/deletion of Research Item records. |
| I-01460 | (Add/View/Edit Abuse) The system shall allow the user to add an additional Note or Research Item record to be linked-to this same Project, Relationship, or Tip. The system shall provide the user with the option to carry-forward the same source-of-information record for each additional Note or Research Item record. |
| I-01470 | (AddViewEdit Abuse) The system shall allow the user to scroll-up to the previous Notes or Research Items or scroll-down to the next one linked to this same Project, Relationship, or Tip. (Notes and Research Item records shall be ordered in reverse chronological order of Date-Created and record types may be interspersed) The system shall continue to present the content of the upper portion of the page which shows the Project, Relationship, and Tip Information dependent on which level the Notes and Research Item records are being linked-to. |
| (Internal - Add/View/Edit Research Item Information also refer to SENTRY Requirements (Exhibits).xls / Production (Exhibit - K)) |
|
| I-01480 | (Add/View/Edit Production) The system shall allow all users to add and view Production Information (Research Item) records. The system shall restrict editing/deleting of these same items. (Refer to INT Functionality Matrix) |
| I-01490 | (AddViewEdit Production) The system shall support the selection of a source-of-information record through the Search/List/Select Source-of-Information Records documented later in this requirements document. |
| I-01500 | (Add/View/Edit Production) The system shall require the user to enter the type of Research Item Information record to be added (created). The user entry of Research Item information type shall be supported by a dropdown list. The dropdown list shall contain the following Research Item information types: (Abuse, Production, Packaging, Distribution, Public Awareness) The Research Item Information record type shall not be changed through the edit function. |
| I-01510 | (Add/View/Edit Production) The system shall allow the user to select a Dissemination Restriction (supported by dropdown list) when beginning to enter the Production Information Record. |
| I-01520 | (Add/View/Edit Production) Initially blank, the system shall present the Created-By (name of the user who created the Production), followed by the Date/Time once the Production Information Record has been saved. |
| I-01530 | (Add/View/Edit Production) Initially blank, the system shall present the Edited-By (name of the user who last edited the Production Information Record), followed by the Date/Time. |
| I-01540 | (Add/View/Edit Production) The system shall allow the user to enter the following fields for the Production Information Record: Address Line 1 Address Line 2 City, State/Province/Territory (state supported by a dropdown list), Zip or Postal Code County, Country (supported by a dropdown list) |
| I-01550 | (Add/View/Edit Production) The system shall allow the user to enter these additional fields for the Production Information Record: Whose is Manufacturing the Drug Precursors or Chemicals Used Smuggling/Transportation Methods of Precursors or Chemicals Cost Associated with Production Packaging Type (supported by a dropdown list) Comments |
| I-01560 | (Add/View/Edit Production) The system shall provide user access to functionality to add a Note or Research Item record linked to a Project, Relationship, or Tip Information record. (The Note or Research Item record shall be linked-to the Tip Information record if presented, else the Relationship record if presented, else the Project record. Access to the AddViewEditNote page shall be limited to the following pages: (Exhibit {B} - Proj-Rel-Notes-Res) Records added (created) through this access point shall be linked-to the Project (Exhibit {D} - Rel-Notes-Res-Tips) Records added (created) through this access point shall be linked-to the Relationship unless the user identified a specific Tip record (Exhibit - {GH} - Add/View/Edit Tip) the added Note or Research Item record is to be linked-to) |
| I-01570 | (Add/View/Edit Production) The system shall present the user with a confirmation message that the new-edited-or-deleted Note or Research Item record was successfully saved-or-deleted. |
| I-01580 | (Add/View/Edit Production) The system shall log the addition/editing/deletion of Research Item records. |
| I-01590 | (Add/View/Edit Production) The system shall allow the user to add an additional Note or Research Item record to be linked-to this same Project, Relationship, or Tip. The system shall provide the user with the option to carry-forward the same source-of-information record for each additional Note or Research Item record. |
| I-01600 | (AddViewEdit Production) The system shall allow the user to scroll-up to the previous Notes or Research Items or scroll-down to the next one linked to this same Project, Relationship, or Tip. (Notes and Research Item records shall be ordered in reverse chronological order of Date-Created and record types may be interspersed) The system shall continue to present the content of the upper portion of the page which shows the Project, Relationship, and Tip Information dependent on which level the Notes and Research Item records are being linked-to. |
| (Internal - Add/View/Edit Research Item Information also refer to SENTRY Requirements (Exhibits).xls / Packaging (Exhibit - L)) |
|
| I-01610 | (Add/View/Edit Packaging) The system shall allow all users to add and view Packaging Information (Research Item) records. The system shall restrict editing/deleting of these same items. (Refer to INT Functionality Matrix) |
| I-01620 | (AddViewEdit Packaging) The system shall support the selection of a source-of-information record through the Search/List/Select Source-of-Information Records documented later in this requirements document. |
| I-01630 | (Add/View/Edit Packaging) The system shall require the user to enter the type of Research Item Information record to be added (created). The user entry of Research Item information type shall be supported by a dropdown list. The dropdown list shall contain the following Research Item information types: (Abuse, Production, Packaging, Distribution, Public Awareness) The Research Item Information record type shall not be changed through the edit function. |
| I-01640 | (Add/View/Edit Packaging) The system shall allow the user to select a Dissemination Restriction (supported by dropdown list) when beginning to enter the Packaging Information Record. |
| I-01650 | (Add/View/Edit Packaging) Initially blank, the system shall present the Created-By (name of the user who created the Packaging), followed by the Date/Time once the Packaging Information Record has been saved. |
| I-01660 | (Add/View/Edit Packaging) Initially blank, the system shall present the Edited-By (name of the user who last edited the Packaging Information Record), followed by the Date/Time. |
| I-01670 | (Add/View/Edit Packaging) The system shall allow the user to enter the following fields for the Packaging Information Record: Packaging Type (supported by a dropdown list) Container Type Packaging Size/Units Logos Diluents (Cutting Agents) Adulterants Comments |
| I-01680 | (Add/View/Edit Packaging) The system shall provide user access to functionality to add a Note or Research Item record linked to a Project, Relationship, or Tip Information record. (The Note or Research Item record shall be linked-to the Tip Information record if presented, else the Relationship record if presented, else the Project record. Access to the AddViewEditNote page shall be limited to the following pages: (Exhibit {B} - Proj-Rel-Notes-Res) Records added (created) through this access point shall be linked-to the Project (Exhibit {D} - Rel-Notes-Res-Tips) Records added (created) through this access point shall be linked-to the Relationship unless the user identified a specific Tip record (Exhibit - {GH} - Add/View/Edit Tip) the added Note or Research Item record is to be linked-to) |
| I-01690 | (Add/View/Edit Packaging) The system shall present the user with a confirmation message that the new-edited-or-deleted Note or Research Item record was successfully saved-or-deleted. |
| I-01700 | (Add/View/Edit Packaging) The system shall log the addition/editing/deletion of Research Item records. |
| I-01710 | (Add/View/Edit Packaging) The system shall allow the user to add an additional Note or Research Item record to be linked-to this same Project, Relationship, or Tip. The system shall provide the user with the option to carry-forward the same source-of-information record for each additional Note or Research Item record. |
| I-01720 | (AddViewEdit Packaging) The system shall allow the user to scroll-up to the previous Notes or Research Items or scroll-down to the next one linked to this same Project, Relationship, or Tip. (Notes and Research Item records shall be ordered in reverse chronological order of Date-Created and record types may be interspersed) The system shall continue to present the content of the upper portion of the page which shows the Project, Relationship, and Tip Information dependent on which level the Notes and Research Item records are being linked-to. |
| (Internal - Add/View/Edit Research Item Information also refer to SENTRY Requirements (Exhibits).xls / Distribution (Exhibit - M)) |
|
| I-01730 | (Add/View/Edit Distribution) The system shall allow all users to add and view Distribution Information (Research Item) records. The system shall restrict editing/deleting of these same items. (Refer to INT Functionality Matrix) |
| I-01740 | (Add/View/Edit Distribution) The system shall support the selection of a source-of-information record through the Search/List/Select Source-of-Information Records documented later in this requirements document. |
| I-01750 | (Add/View/Edit Distribution) The system shall require the user to enter the type of Research Item Information record to be added (created). The user entry of Research Item information type shall be supported by a dropdown list. The dropdown list shall contain the following Research Item information types: (Abuse, Production, Packaging, Distribution, Public Awareness) The Research Item Information record type shall not be changed through the edit function. |
| I-01760 | (Add/View/Edit Distribution) The system shall allow the user to select a Dissemination Restriction (supported by dropdown list) when beginning to enter the Distribution Information Record. |
| I-01770 | (Add/View/Edit Distribution) Initially blank, the system shall present the Created-By (name of the user who created the Distribution Information Record), followed by the Date/Time once the Distribution has been saved. |
| I-01780 | (Add/View/Edit Distribution) Initially blank, the system shall present the Edited-By (name of the user who last edited the Distribution Information Record followed by the Date/Time. |
| I-01790 | (Add/View/Edit Distribution) The system shall allow the user to enter the following fields for the Distribution Information Record: Distribution Type (supported by a dropdown list) Address Line 1 Address Line 2 City, State/Province/Territory (state is supported by a dropdown list), Zip or Postal Code County, Country (supported by a dropdown list) |
| I-01800 | (Add/View/Edit Distribution) The system shall allow the user to enter these additional fields for the Distribution Information Record: Whose is Distributing the Drug How are they Distributing Price/Per (secondary field is required when Price entered) Quantity Seized/Units (secondary field is required when Quantity entered) Tested Purity/Tested By (secondary field is required when Tested Purity entered) Comments |
| I-01810 | (Add/View/Edit Distribution) The system shall provide user access to functionality to add a Note or Research Item record linked to a Project, Relationship, or Tip Information record. (The Note or Research Item record shall be linked-to the Tip Information record if presented, else the Relationship record if presented, else the Project record. Access to the AddViewEditNote page shall be limited to the following pages: (Exhibit {B} - Proj-Rel-Notes-Res) Records added (created) through this access point shall be linked-to the Project (Exhibit {D} - Rel-Notes-Res-Tips) Records added (created) through this access point shall be linked-to the Relationship unless the user identified a specific Tip record (Exhibit - {GH} - Add/View/Edit Tip) the added Note or Research Item record is to be linked-to) |
| I-01820 | (Add/View/Edit Distribution) The system shall present the user with a confirmation message that the new-edited-or-deleted Note or Research Item record was successfully saved-or-deleted. |
| I-01830 | (Add/View/Edit Distribution) The system shall log the addition/editing/deletion of Research Item records. |
| I-01840 | (Add/View/Edit Distribution) The system shall allow the user to add an additional Note or Research Item record to be linked-to this same Project, Relationship, or Tip. The system shall provide the user with the option to carry-forward the same source-of-information record for each additional Note or Research Item record. |
| I-01850 | (AddViewEdit Distribution) The system shall allow the user to scroll-up to the previous Notes or Research Items or scroll-down to the next one linked to this same Project, Relationship, or Tip. (Notes and Research Item records shall be ordered in reverse chronological order of Date-Created and record types may be interspersed) The system shall continue to present the content of the upper portion of the page which shows the Project, Relationship, and Tip Information dependent on which level the Notes and Research Item records are being linked-to. |
| (Internal - Add/View/Edit Research Item Information also refer to SENTRY Requirements (Exhibits).xls / Awareness (Exhibit - N)) |
|
| I-01860 | (Add/View/Edit Awareness) The system shall allow all users to add and view Public Awareness Information (Research Item) records. The system shall restrict editing/deleting of these same items. (Refer to INT Functionality Matrix) |
| I-01870 | (Add/View/EditAwareness) The system shall support the selection of a source-of-information record through the Search/List/Select Source-of-Information Records documented later in this requirements document. |
| I-01880 | (Add/View/Edit Awareness) The system shall require the user to enter the type of Research Item Information record to be added (created). The user entry of Research Item information type shall be supported by a dropdown list. The dropdown list shall contain the following Research Item information types: (Abuse, Production, Packaging, Distribution, Public Awareness) The Research Item Information record type shall not be not changed through the edit function. |
| I-01890 | (Add/View/Edit Awareness) The system shall allow the user to select a Dissemination Restriction (supported by dropdown list) when adding or editing the Awareness Information Record. |
| I-01900 | (Add/View/Edit Awareness) Initially blank, the system shall present the Created-By (name of the user who created the Awareness), followed by the Date/Time once the Awareness Information Record has been saved. |
| I-01910 | (Add/View/Edit Awareness) Initially blank, the system shall present the Edited-By (name of the user who last edited the Awareness Information Record), followed by the Date/Time. |
| I-01920 | (Add/View/Edit Awareness) The system shall allow the user to enter the following information for the Public Awareness Information Record: Awareness Type (supported by dropdown list) Text |
| I-01930 | (Add/View/Edit Awareness) The system shall provide user access to functionality to add a Note or Research Item record linked to a Project, Relationship, or Tip Information record. (The Note or Research Item record shall be linked-to the Tip Information record if presented, else the Relationship record if presented, else the Project record. Access to the AddViewEditNote page shall be limited to the following pages: (Exhibit {B} - Proj-Rel-Notes-Res) Records added (created) through this access point shall be linked-to the Project (Exhibit {D} - Rel-Notes-Res-Tips) Records added (created) through this access point shall be linked-to the Relationship unless the user identified a specific Tip record (Exhibit - {GH} - Add/View/Edit Tip) the added Note or Research Item record is to be linked-to) |
| I-01940 | (Add/View/Edit Awareness) The system shall present the user with a confirmation message that the new-edited-or-deleted Note or Research Item record was successfully saved-or-deleted. |
| I-01950 | (Add/View/Edit Awareness) The system shall log the addition/editing/deletion of Research Item records. |
| I-01960 | (Add/View/Edit Awareness) The system shall allow the user to add an additional Note or Research Item record to be linked-to this same Project, Relationship, or Tip. The system shall provide the user with the option to carry-forward the same source-of-information record for each additional Note or Research Item record. |
| I-01970 | (AddViewEdit Awareness) The system shall allow the user to scroll-up to the previous Notes or Research Items or scroll-down to the next one linked to this same Project, Relationship, or Tip. (Notes and Research Item records shall be ordered in reverse chronological order of Date-Created and record types may be interspersed) The system shall continue to present the content of the upper portion of the page which shows the Project, Relationship, and Tip Information dependent on which level the Notes and Research Item records are being linked-to. |
| (Internal - Project Record and Its Linkages) | |
| I-01980 | The Project record does not link-to other records. Relationship, Note, and Research Item records can be linked-to the Project record. |
| (Internal - Relationship Record and Its Linkages) | |
| I-01990 | The Relationship record can be linked to one-or-more Project records |
| I-02000 | NDIC Intel SENTRY business rules shall require all Relationship records to be linked-to at least one Project record. NDIC Intel shall establish a generic Project record that Relationship records not part of a formal project shall be linked-to. |
| I-02010 | Tip Information, Note, and Research Item records can be linked-to the Relationship record. |
| (Internal - Tip Information Record and Its Linkages) | |
| I-02020 | The externally submitted Tip Information record must be linked-to its submitter's user-account record stored in the internal copy of the external User-Account table. The link is permanent and must not be altered or removed. |
| I-02030 | The internally entered Tip Information record must be linked-to a source-of-information record; the linked-to source-of-information record might be stored in the internal copy of the external User-Account table or in the internal Source-Identification table. A Tip to Source-of-Information record link must be established at the time the Tip is entered. The Tip's link may be reassigned to a different source-of-Information record; the reason the system must allow for reassignment is because the previous assignment may be erroneous. |
| I-02040 | The Tip Information record may be linked to one-or-more Relationship records. |
| (Internal - Note Record and Its Linkages) | |
| I-02050 | The Note record must be linked-to a source-of-information record; the linked-to source-of-information record might be stored in the internal copy of the external User-Account table or in the internal Source-Identification table. A Note to Source-of-Information record link must be established at the time the Note is entered. The Note's link may be reassigned to a different source-of-Information record; the reason the system must allow for reassignment is because the previous assignment may be erroneous. |
| I-02060 | Each Note record can be linked-to a single Tip Information, Relationship, or Project record. |
| (Internal - Research Item Record and Its Linkages) | |
| I-02070 | The Research Item record must be linked-to a source-of-information record; the linked-to source-of-information record might be stored in the internal copy of the external User-Account table or in the internal Source-Identification table. A Research Item to Source-of-Information record link must be established at the time the Research Item is entered. The Research Item's link may be reassigned to a different source-of-Information record; the reason the system must allow for reassignment is because the previous assignment may be erroneous. |
| I-02080 | Each Research Item record can be linked-to a single Tip Information, Relationship, or Project record. |
| (Internal - Search/List/Select Source-of-Information Records) | |
| I-02090 | (Search Source Record) The system shall provide functionality for all users to search, list, and select a source-of-information record to associate with a note, research item, and internally entered tip information record. Each note, research item, and internally entered tip information record must be linked-to either a Source Identification or external User-Account record. |
| I-02100 | (Select Source Record) The system shall provide access to the search/list/select Source Identification record page from the add/edit Note, Research Item, and Tip pages. |
| I-02110 | (Search Source Record) While populating the resulting list the system shall select from both the internal copy of the external User-Account table and the Source Identification table. |
| I-02120 | (Search Source Record) The system shall allow users to search by last name, organization name, and role. |
| I-02130 | (Search Source Record) The system shall support user entry of Role with a dropdown-list. |
| I-02140 | (Search Source Record) The system shall use the Last-Name search parameter entered to compare with each external user-account record and source-identification record last-name column's leftmost equal number of contiguous positions (last-name positions provided*). The Organization Name search parameter entered shall be used to conduct a "contains" search of these same record's Organization Name, Level-2 & Level-3 fields (This search shall be done as an "or" condition among the three Organization fields, a "contains" match within any Organization field shall satisfy this portion of the search). The Role search parameter shall be used to conduct an "exact match" against these same record's Role field. When the user enters more than one search parameter field, the system shall process the search as an "and" condition among the search parameters entered. When the user does not enter any search parameter, the system shall return and list all Source Identification and external User-Account records. Note: The default sort of returned data from searching will be alphabetically by last name. |
| I-02150 | (Search Source Record) The system shall allow users to not enter anything in the last name, organization name, and roles to return all external user-account and source identification records. |
| I-02160 | (Search Source Record) The system shall list the following external-user-accounts and source identification column: Last Name, First Name, Middle Name, Organization Name, Organization Level-2, Organization Level-3, Title/Position, Role, Phone, FAX, and E-mail address. |
| I-02170 | (Search Source Record) The system shall allow only "Administrators" to edit source identification records. "Administrators" will not be able to edit external user records from this page, only source identification records. |
| I-02180 | (Search Source Record) The system shall allow the user to choose a returned source and associate that source to the research item, note, or tip the user is adding or editing. |
| I-02190 | (Search Source Record) The system shall allow the user to add a new source identification record if needed. |
| I-02200 | (Search Source Record) The system shall allow the user to select a source identification record and edit the record in the edit source identification page. |
| (Internal - Add Source Identification Record) | |
| I-02210 | (Add Source Identification) The system shall provide functionality for all users to add source identification records. |
| I-02220 | (Add Source Identification) The system shall require the user to enter the source record's Organization Name field. |
| I-02230 | (Add Source Identification) The system shall allow the user to enter the source record's Organization Level 2 field. |
| I-02240 | (Add Source Identification) The system shall allow the user to enter the source record's Organization Level 3 field. |
| I-02250 | (Add Source Identification) The system shall require the user to enter the source record's Role field. |
| I-02260 | (Add Source Identification) The system shall support user entry of Role with a dropdown-list. |
| I-02270 | (Add Source Identification) The system shall allow the user to enter the source record's Explain Other field. |
| I-02280 | (Add Source Identification) The system shall allow the user to enter the source record's Title/Position field. |
| I-02290 | (Add Source Identification) The system shall allow the user to enter the source record's First Name. |
| I-02300 | (Add Source Identification) The system shall allow the user to enter the source record's Middle Name. |
| I-02310 | (Add Source Identification) The system shall allow the user to enter the source records Last Name. |
| I-02320 | (Add Source Identification) The system shall allow the user to enter the source record's Address Line 1. |
| I-02330 | (Add Source Identification) The system shall allow the user to enter the source record's Address Line 2. |
| I-02340 | (Add Source Identification) The system shall allow the user to enter the source record's City. |
| I-02350 | (Add Source Identification) The system shall allow the user to enter the source record's State, Province, or Territory. |
| I-02360 | (Add Source Identification) The system shall support user entry of State with a dropdown-list if the country is United States of America |
| I-02370 | (Add Source Identification) The system shall allow the user to enter the source record's zip or postal code (first five positions if in United States of America). |
| I-02380 | (Add Source Identification) The system shall allow the user to enter the source record's Country. There will only be three options: United States of America., Canada, and Mexico. |
| I-02390 | (Add Source Identification) The system shall support user entry of Country with a dropdown-list; the system shall preload the country field on the Add User Account page with "United States of America" |
| I-02400 | (Add Source Identification) The system shall allow the user to enter the source record's contact note field. |
| I-02410 | (Add Source Identification) The system shall require the user to enter the source record's phone number. Intel requires the following phone number formatting (111) 222-3333 Ext: 4444 with the user keying only the numeric portion if the source record's country is the United States of America If the source record's country is Canada or Mexico the system will save up to 20 numbers for the phone number removing all non-numeric characters. |
| I-02420 | (Add Source Identification) The system shall allow the user to enter the source record's FAX number. Intel requires the following phone number formatting (111) 222-3333 with the user keying only the numeric portion if the source record's country is the United States of America If the source record's country is Canada or Mexico allow up to 20 characters for the fax number removing all non-numeric characters. |
| I-02430 | (Add Source Identification) The system shall allow the user to enter the source record's E-List choice (Subscribed/Unsubscribed). |
| I-02440 | (Add Source Identification) The system shall allow the user to enter the source record's E-mail address. Note: If the Source Identification record is coded as active and the record's E-List choice equals "Subscribed" the E-Mail address must be entered. |
| I-02450 | (Add Source Identification) The system shall set the active/inactive status to active on each new source-identification record. The system shall allow the user to reset the status to inactive/active. |
| I-02460 | (Add Source Identification) The system shall support user entry of active/inactive field with a dropdown-list (or, check-box). |
| I-02470 | (Add Source Identification) The system shall store the user's username in the Created-By field. |
| I-02480 | (Add Source Identification) The system shall store the date/time the record was created in the source identification Date-Created field. |
| I-02490 | (Add Source Identification) The system shall set the Edited-By field to nulls. |
| I-02500 | (Add Source Identification) The system shall set the Date/Time Edited field to nulls. |
| I-02510 | (Add Source Identification) The system shall set the E-ListEdited-by column to nulls. |
| I-02520 | (Add Source identification) The system shall set the E-list Date/TimeEdited column to nulls. |
| I-02530 | (Add Source Identification) The system shall present a confirmation that the new source identification record was successfully saved. |
| I-02540 | (Add Source Identification) The system shall allow user to choose the newly added source identification record to be the linked-to source record for the note, research item, or tip the user is adding or editing. |
| I-02550 | (Add Source Identification) The system shall allow the user to add more than one source identification record if the user so chooses. |
| I-02560 | (Add Source Identification) The system shall allow the user to re-search source records after the user has entered one-or-more new source records. The system shall allow the user to re-search source records whether or not the user adds new source records. |
| I-02570 | (Add Source Identification) The system shall save added source identification to the audit log. The saved information shall include the user who added the source identification, the source identification, and the date/time the user-record was added. |
| (Internal - Edit Source Identification Records) | |
| I-02580 | (Edit Source Identification) The system shall provide functionality for users to edit source identification records. |
| I-02590 | (Edit Source Identification) The system shall restrict the edit-source-identification functionality to user function of "Administrator." (Refer to INT Functionality Matrix) |
| I-02600 | (Edit Source Identification) The system shall present the user with the edit source-identification record page with the selected source-identification-record's data populating the source-identification edit page. |
| I-02610 | (Edit Source Identification) The system shall allow the user to edit the source record's Organization Name |
| I-02620 | (Edit Source Identification) The system shall allow the user to edit the source record's Organization Level 2. |
| I-02630 | (Edit Source Identification) The system shall allow the user to edit the source record's Organization Level 3. |
| I-02640 | (Edit Source Identification) The system shall allow the user to edit the source record's Role. |
| I-02650 | (Edit Source Identification) The system shall support user entry of Role with a dropdown-list. |
| I-02660 | (Edit Source Identification) The system shall allow the user to edit the source record's Explain Other field. |
| I-02670 | (Edit Source Identification) The system shall allow the user to edit the source record's Title/Position. |
| I-02680 | (Edit Source Identification) The system shall allow the user to edit the source record's First Name. |
| I-02690 | (Edit Source Identification) The system shall allow the user to edit the source record's Middle Name. |
| I-02700 | (Edit Source Identification) The system shall allow the user to edit the source record's Last Name. |
| I-02710 | (Edit Source Identification) The system shall allow the user to edit the source record's Address Line 1. |
| I-02720 | (Edit Source Identification) The system shall allow the user to edit the source record's Address Line 2. |
| I-02730 | (Edit Source Identification) The system shall allow the user to edit the source record's City. |
| I-02740 | (Edit Source Identification) The system shall allow the user to edit the source record's State, Province, or Territory. |
| I-02750 | (Edit Source Identification) The system shall support the user entry of State with a dropdown-list if the country is United States of America |
| I-02760 | (Edit Source Identification) The system shall allow the user to edit the source record's zip or postal code (first five positions if in United States of America). |
| I-02770 | (Edit Source Identification) The system shall allow the user to edit the source record's Country. There will only be three options: United States of America., Canada, and Mexico. |
| I-02780 | (Edit Source Identification) The system shall support user entry of Country with a dropdown-list; the system shall preload the country field on the Add User Account page with "United States of America" |
| I-02790 | (Edit Source Identification) The system shall allow the user to edit the source record's contact note field. |
| I-02800 | (Edit Source Identification) The system shall require the user to edit the source record's phone number. Intel requires the following phone number formatting (111) 222-3333 Ext: 4444 with the user keying only the numeric portion if the source record's country is the United States of America If the source record's country is Canada or Mexico the system will save up to 20 numbers for the phone number removing all non-numeric characters. |
| I-02810 | (Edit Source Identification) The system shall allow the user to edit the source record's FAX number. Intel requires the following phone number formatting (111) 222-3333 with the user keying only the numeric portion if the source record's country is the United States of America If the source record's country is Canada or Mexico allow up to 20 characters for the fax number removing all non-numeric characters. |
| I-02820 | (Edit Source Identification) The system shall allow the user to edit the source record's contact note (duplicate of I-02790). |
| I-02830 | (Edit Source Identification) The system shall allow the user to edit the source record's E-List choice. |
| I-02840 | (Edit Source Identification) The system shall allow the user to edit the source record's E-mail address. Note: If the Source Identification record is coded as active and the record's E-List choice equals "Subscribed" the E-Mail address must be entered. |
| I-02850 | (Edit Source Identification) The system shall allow the user to edit the source record's active/inactive field. |
| I-02860 | (Edit Source Identification) The system shall store the current date/time the edited record is saved in the Date-Edited field. |
| I-02870 | (Edit Source Identification) The system shall store the username in the Edited-By field of the "Administrator" user who completed the editing. |
| I-02880 | (Edit Source Identification) The system shall allow the Administrator to delete a Source-Identification record when the record does NOT have any Note, Research Item, or Tip Information records linked-to it. |
| I-02890 | (Edit Source Identification) The system shall present a confirmation that the edited source identification record was successfully saved-or-deleted. |
| I-02900 | (Edit Source Identification) The system shall save edited/deleted source identification to the audit log. The saved information shall include the "Administrator" who edited/deleted the source identification, the source identification, and the date/time the user was edit |
| (Internal - View Source Identification) | |
| I-02910 | (View Source Identification) The system shall provide functionality for all users to view internal source-identification records. (Refer to the INT Functionality Matrix) |
| I-02920 | (View Source Identification) The system shall present all source identification fields that are presented on the Edit Source Identification page. All fields shall be view only. |
| (Internal - Search, List, and Select Projects also refer to SENTRY Requirements (Exhibits).xls / Exhibit {A} SLS Projects) |
|
| I-02930 | (SLS Projects) The system shall provide functionality for all users to search for Project records. (Refer to "INT Functionality Matrix" worksheet) |
| I-02940 | (SLS Projects) The system shall provide functionality to search Projects by: Title, Assigned-To, Created-By, Status, and Date Project Created Range (From and To). |
| I-02950 | (SLS Projects) The system shall handle multiple search parameters as "and" conditions--all search parameters must be satisfied. |
| I-02960 | (SLS Projects) The system shall conduct a "contains" search of the Title field with entered search parameters. |
| I-02970 | (SLS Projects) The system shall conduct an "exact match" search of Assigned-To with entered search parameters. |
| I-02980 | (SLS Projects) The system shall support user entry of the Assigned-To field through the "JNS/Username Name" table. |
| I-02990 | (SLS Projects) The system shall conduct an "exact match" search of Created-By with entered search parameters. |
| I-03000 | (SLS Projects) The system shall support user entry of the Created-By field through the "JNS/Username Name" table. |
| I-03010 | (SLS Projects) The system shall conduct an "Open/Closed" search of Status with entered search parameters. |
| I-03020 | (SLS Projects) The system shall support user entry of the Status field with a dropdown list (Open/Closed). |
| I-03030 | (SLS Projects) The system shall compare the Date Project Created Range (From and To) field parameters against the Project's Date Created. Either or both the "Date From" and "Date To" might be empty. When the user key enters into either date field the system shall require the content to be a valid date format. When the user enters both the "Date From" and "Date To" the system shall compare the dates to each other to ensure the "From Date" is not greater than the "To Date." When the user key enters a valid "From Date" the system shall compare it against the Project's Date Created field. If the Date Created is not less than the "From Date" the searched field/parameter comparison is satisfied When the user key enters a valid "To Date" the system shall compare it against the Project's Date Created field. If the Date Created is not greater than the "To Date" the search field/parameter comparison is satisfied |
| I-03040 | (SLS Projects) The system may list multiple Project records when search parameters have been entered. |
| I-03050 | (SLS Projects) The system shall list all Project records when no search parameters have been entered. |
| I-03060 | (SLS Projects) The system shall list the following project fields left-to-right: Title; Assigned-To; Created-By; Date Created; Edited-By, Date Edited, Status, and Project Record ID. |
| I-03070 | (SLS Projects) The system shall order the returned list of projects alphabetically by Title. |
| I-03080 | (SLS Projects) The system shall allow the user to select a listed Project to access it through an AddViewEditProject page. |
| I-03090 | (SLS Projects) The system shall allow the user to select a listed Project to list its Relationships to possibly remove (deselect) the Relationship or to search for additional Relationships to add to (select) the selected Project. (Refer to Search, List, Select & Deselect: Relationships for Project (Exhibit C)) |
| I-03100 | (SLS Projects) The system shall allow the user to select a listed Project to list Relationships, Notes, and Research Items already linked-to the Project and to also list unassigned Notes and Research Items. (Refer to List Select Project's: Relationships, Notes & Research Items (Exhibit - B)) |
| I-03110 | (SLS Projects) The system shall allow the user to select a listed Project to generate a report including information from the Project record and all Relationship, Tip, Note, and Research Item records linked directly-or-indirectly to the selected Project. |
| (Internal - List Selected Project's Relationships, Notes & Research Items also refer to SENTRY Requirements (Exhibits).xls / Exhibit {B} Proj-Rel-Notes-Res) |
|
| I-03120 | (Proj-Rel-Notes-Res) The system shall provide functionality that lists Relationship, Note, and Research Item records linked directly to the Project record the user selected on the Search, List and Select Projects page (Exhibit - A). |
| I-03130 | (Proj-Rel-Notes-Res) The system shall list all unassigned Note and Research Item records not linked to any Project, Relationship, or Tip record. |
| I-03140 | (Proj-Rel-Notes-Res) The system shall present the selected Project's Title, Assigned-To, Created-By, Date Created, Edited-By, Date Edited, Status & Project Record ID near the top of the page. |
| I-03150 | (Proj-Rel-Notes-Res) The system shall provide functionality for an Administrator user to delete the Project record when there are no Relationship, Note, or Research Item records linked-to the Project record. |
| I-03160 | (Proj-Rel-Notes-Res) The system shall list all Relationship Records (regardless of status) linked directly to the Project prior to listing of Notes and Research Items either unassigned or linked directly to the Project. |
| I-03170 | (Proj-Rel-Notes-Res) The system shall list all Project records (if any), other than the selected Project listed at the top of the page, each Relationship record is linked-to. The Project's: Title, Assigned-To, Created-By, Date Created, Edited-By, Date Edited, Status & Project Record ID shall be listed preceding the Relationship. |
| I-03180 | (Proj-Rel-Notes-Res) The Relationship's: Summary, Created-By, Date Created, Edited-By, Date Edited, Status & Relationship Record ID fields shall be listed left-to-right. The Relationships shall be ordered alphabetically by Relationship Summary. |
| I-03190 | (Proj-Rel-Notes-Res) The system shall list all Notes and Research Items either unassigned or linked directly to the Project following the list of Relationship Summaries. The Note or Research Item's: Created-By, Date Created, Edited-By, Date-Edited, Type (Ex: Note), Sub-Type (Ex: E-mail), First 180 characters of Note, Comments, or Text (3-lines, 60 characters each, Source of Information: Name(Last, First Middle), Organization Name, and Role. |
| I-03200 | (Proj-Rel-Notes-Res) The system shall list all Notes and Research Items in reverse chronological order by date-created. Notes and Research Items might be interspersed. |
| I-03210 | (Proj-Rel-Notes-Res) The system shall allow the user to select a Relationship and access it through an AddViewEditRelationship page. |
| I-03220 | (Proj-Rel-Notes-Res) The system shall allow the user to select a Note and access it through an AddViewEditNote page. |
| I-03230 | (Proj-Rel-Notes-Res) The system shall allow the user to select a Research Item and access it through an AddViewEditResearchItem page. |
| I-03240 | (Proj-Rel-Notes-Res) The system shall allow the user to select a Relationship to list all Notes, Research Items, and Tips linked directly to the Relationship along with unassigned Notes and Research Items not linked to any Project, Relationship, or Tip. (Exhibit - D - Rel-Notes-Res-Tips). |
| I-03250 | (Proj-Rel-Notes-Res) The system shall allow the user to select a Relationship to search for additional Tips, then list all Tips linked directly to the Relationship along with those chosen through the entry of search parameters (Exhibit - E - SLS Tips-for-Rels). |
| I-03260 | (Proj-Rel-Notes-Res) The system shall provide functionality for all users to select ([x] checkbox) to link an unassigned Note or Research Item to the Project identified at the top of this page. (Refer to INT Functionality Matrix) |
| I-03270 | (Proj-Rel-Notes-Res) The system shall provide functionality for all Administrator users to deselect ([ ] checkbox) to remove a Relationship, Note, or Research Item record previously linked-to the Project identified at the top of this page. (Refer to INT Functionality Matrix) |
| (Internal - Search, List, Select, Deselect: Relationships for Project also refer to SENTRY Requirements (Exhibits).xls / Exhibit {C} SLS Rels-for-Proj) |
|
| I-03280 | (SLS Rels-for-Proj) The system shall list the Title, Assigned-To, Created-By, Date Created, Edited-By, Date Edited, Status & Project Record ID near the top of the page for the Project record selected on the SLS Projects page (Exhibit - A) |
| I-03290 | (SLS Rels-for-Proj) The system shall provide functionality for all users to search relationship records by their Summary, Created-By, Edited-By, Status, Created Date, and Edited Date fields. |
| I-03300 | (SLS Rels-for-Proj) The system shall use a contains search when the user enters a Summary search parameter. |
| I-03310 | (SLS Rels-for-Proj) The system shall support user entry of Created-By and Edited-By search parameters through the JNS/Username - Name table. |
| I-03320 | (SLS Rels-for-Proj) The system shall support user entry of Status with a dropdown list (Open/Closed). |
| I-03330 | (SLS Rels-for-Proj) The system shall provide functionality to search relationship records by Created Date and Edited Date through entry of Date Range (From/To). The system shall require these date range fields are entered as valid date formats. The system shall ensure the From-Date is not greater than the To-Date. The system shall ensure the Dates are not future dates. When both the From-Date and the To-Date search parameters are entered, the system shall consider the search parameter as satisfied if the record's date (Created or Edited) is not prior to the search From-Date and not beyond the search To-Date. When only the From-Date is entered, the system shall consider the search parameter as satisfied when the record's date (Created-or-Edited) is not less than the From-Date. When only the To-Date is entered, the system shall consider the search parameter as satisfied if the record's date (Created-or-Edited) is not greater than the To-Date. |
| I-03340 | (SLS Rels-for-Proj) The system shall present the user with an informative error message when any entered search parameter fails a validity or reasonableness check. |
| I-03350 | (SLS Rels-for-Proj) The system shall require the searched-for Relationship record to meet all search parameters entered by the user. If the user does not enter any search parameters all Relationship records will be listed. |
| I-03360 | (SLS Rels-for-Proj) The system shall list all Relationship records already linked-to the Project record identified in the page header without regard to the search parameters entered. |
| I-03370 | (SLS Rels-for-Proj) The system shall list all other Projects the listed Relationship records are linked-to. These other Projects, ones not identified in at the top of the page, shall be listed prior to the Relationship record or records that are linked to it. |
| I-03380 | (SLS Rels-for-Proj) The system shall list the Title, Assigned-To, Created-By, Date Created, Edited-By, Date Edited, Status & Project Record ID for these other Projects. |
| I-03390 | (SLS Rels-for-Proj) The system shall list the Summary, Created-By, Date Created, Edited-By, Date Edited, Status & Relationship Record ID fields for all listed Relationship records. |
| I-03400 | (SLS Rels-for-Proj) The system shall order listed Relationship records alphabetically by Summary. |
| I-03410 | (SLS Rels-for-Proj) The system shall present a [ ] checkbox preceding each listed Relationship record. A checked [x] checkbox will be presented for Relationship records already linked-to the Project identified at the top of the page. An unchecked [ ] checkbox will be presented for Relationship records listed based on search parameters and not already linked-to the Project. |
| I-03420 | (SLS Rels-for-Proj) The system shall allow all users to [x] select Relationship records to link-to the Project identified at the top-of-this page. (Refer to INT Functionality Matrix) |
| I-03430 | (SLS Rels-for-Proj) The system shall restrict the functionality to [ ] deselect Relationship records previously linked-to the Project identified at the top-of-this page. (Refer to INT Functionality Matrix) |
| I-03440 | (SLS Rels-for-Proj) The system shall present a confirmation message when a user either: - Selects a Relationship record to link-to the Project record - Deselects a Relationship record to remove its link-to the Project record |
| I-03450 | (SLS Rels-for-Proj) The system shall log all Select and Deselect actions taken on this page. |
| I-03460 | (SLS Rels-for-Proj) The system shall allow the user to select a listed Relationship to generate a report including information from the Relationship record and all Tip, Note, and Research Item records linked directly-or-indirectly to the selected Relationship. |
| (Internal - Selected Relationship: List and Select Notes, Research, and Tips also refer to SENTRY Requirements (Exhibits).xls / Rel-Notes-Res-Tips (Exhibit - D)) |
|
| I-03470 | (Rel-Notes-Res-Tips) The system shall provide functionality for all users to list and select unassigned Notes and Research Item records to be linked-to the Relationship record the user selected on the Proj-Rel-Notes-Res page (Exhibit - B) and listed near the top of this page. The system shall restrict functionality that deletes or deselects records to Administrator users. (Refer to INT Functionality Matrix) |
| I-03480 | (Rel-Notes-Res-Tips) The system shall restrict functionality to delete the Relationship record the user selected on the Proj-Rel-Notes-Res page (Exhibit - B and is listed near the top of this page. The system shall allow the Administrator to delete the Relationship record when there are no Note, Research Item, or Tip records linked-to the Relationship. (Refer to INT Functionality Matrix) |
| I-03490 | (Rel-Notes-Res-Tips) The system shall provide functionality to unassign (deselect) Note and Research Item records linked to the Relationship record the user selected on the Proj-Rel-Notes-Res page (Exhibit - B) and is listed near the top of this page. The system shall restrict this functionality to Administrator users. (Refer to INT Functionality Matrix) |
| I-03500 | (Rel-Notes-Res-Tips) The system shall provide functionality to remove (deselect) a Tip Information record's link-to the Relationship record the user selected on the Proj-Rel-Notes-Res page (Exhibit - B) and is listed near the top of this page. The system shall restrict this functionality to Administrator users. (Refer to INT Functionality Matrix) |
| I-03510 | (Rel-Notes-Res-Tips) The system shall present the Project's Title, Assigned-To, Created-By, Date Created, Edited-By, Date Edited, Status & Project Record ID near the top of the page. |
| I-03520 | (Rel-Notes-Res-Tips) The system shall present the Relationship's Summary, Created-By, Date-Created, Edited-By, Date Edited, Status & Relationship Record ID fields beneath the Project Information near the top of the page. |
| I-03530 | (Rel-Notes-Res-Tips) The system shall list all Notes and Research Items liked directly to this Relationship or unassigned, prior to any Tips. |
| I-03540 | (Rel-Notes-Res-Tips) The system shall precede each listed Note, Research Item, or Tip with a [ ] checkbox. The checkbox will be checked [x] when the Note or Research Item is linked-to the Relationship. The checkbox will be unchecked [ ] when the Note or Relationship record is unassigned (not linked to any Project, Relationship, or Tip Information record). Each checkbox shall be used to either select an unassigned Note or Research Item record or to deselect (remove its link-to the Relationship record) of a Note, Research Item, or Tip Information record previously linked-to the Relationship. |
| I-03550 | (Rel-Notes-Res-Tips) The system shall not precede Note or Research Item records linked-to a Tip Information record with a checkbox. This page does not provide functionality to maintain Note and Research Item record's link-to Tip Information records. |
| I-03560 | (Rel-Notes-Res-Tips) The system shall list Notes and Research Items in reverse chronological order of Date-Created. |
| I-03570 | (Rel-Notes-Res-Tips) The system shall list Notes and Research Items linked to a listed Tip, following the Tip. |
| I-03580 | (Rel-Notes-Res-Tips) The system shall list the following Notes fields (linked to this Relationship, and any unassigned) from left-to-right: Created-By, Date Created, Edited-By, Date-Edited, Type (Note), Sub-Type (Phone, E-mail), Limited Content (see Exhibit-B), Source of Info (see Exhibit-B) and Note Record ID. |
| I-03590 | (Rel-Notes-Res-Tips) The system shall allow the user to select a Note and access it through the AddViewEditNote page (see Exhibit-I). |
| I-03600 | (Rel-Notes-Res-Tips) The system shall list all unassigned Notes & Research Items along with Notes & Research Items already linked to this Relationship. |
| I-03610 | (Rel-Notes-Res-Tips) The system shall list the following Research Item fields (linked to this Relationship, and any unassigned) from left-to-right: Created-By, Date Created, Edited-By, Date-Edited, Type (Public Awareness), Sub-Type (Legislation), Limited Content (see Exhibit-B), Source of Info (see Exhibit-B), & Research Item Record ID. |
| I-03620 | (Rel-Notes-Res-Tips) The system shall permit users to select a Research Item and access it through an AddViewEditResearchItem page (see Exhibit-J). |
| I-03630 | (Rel-Notes-Res-Tips) The system shall list the Project Title/Relationship Summary of all other relationships the following Tip is linked to (see next requirement). |
| I-03640 | (Rel-Notes-Res-Tips) The system shall list the following Tips fields (linked to this Relationship) from left-to-right: Date Created, Type (Tip), Sub-Type (Tip Number), Limited Content (see Exhibit-B), Source of Info (see Exhibit-B) & Tip Record Id. |
| I-03650 | (Rel-Notes-Res-Tips) The system shall provide functionality for Active-and-Closed (status) Tips only. |
| I-03660 | (Rel-Notes-Res-Tips) The system shall permit users to select a Tip and access it through the AddViewEditTip page (see Exhibit-GH). |
| I-03670 | (Rel-Notes-Res-Tips) The system shall list the following Notes fields (linked to the preceding Tip) from left-to-right: Created-By, Date Created, Edited-By, Date-Edited, Type (Note), Sub-Type (Phone, E-mail), Limited Content (see Exhibit-B), Source of Info (see Exhibit-B) & Notes Record Id. |
| I-03680 | (Rel-Notes-Res-Tips) The system shall list the following Research Item fields (linked to the preceding Tip) from left-to-right: Created-By, Date Created, Edited-By, Date-Edited, Type (Public Awareness), Sub-Type (Legislation), Limited Content (see Exhibit-B), Source of Info (see Exhibit-B) & Research Item Record ID. |
| I-03690 | (Rel-Notes-Res-Tips) The system shall present a confirmation message when a user either: - Deletes a Relationship record - Selects a Note or Research Item record to link-to the Relationship record - Deselects a Note, Research Item, or Tip Information record to remove its link-to the Relationship record |
| I-03700 | (Rel-Notes-Res-Tips) The system shall log the Delete or all Select and Deselect actions taken on this page. |
| (Internal - Search and List Tips for Possible Addition/Deletion to/from This Relationship also refer to SENTRY Requirements (Exhibits).xls / SLS Tips-for-Rel (Exhibit - E)) |
|
| I-03710 | (SLS Tips-for-Rel) The system shall provide functionality for all users to list Tip Information records already linked-to the Relationship record the user selected on the Proj-Rel-Notes-Res-Tips page (Exhibit - B) and listed near the top of this page. Tip Information records already linked-to the Relationship may be deselected (link-to Relationship record removed). The system shall restrict the deselect Tip Information record functionality to Administrator users. (Refer to INT Functionality Matrix) |
| I-03720 | (SLS Tips-for-Rel) The system shall provide functionality for all users to list Tip Information records already linked-to the Relationship record the user selected on the Proj-Rel-Notes-Res-Tips page (Exhibit - B) and listed near the top of this page. Tip Information records already linked-to the Relationship may be deselected (link-to Relationship record removed). The system shall restrict the deselect Tip Information record functionality to Administrator users. (Refer to INT Functionality Matrix) (Duplicate I-03710 Repeated) |
| I-03730 | (SLS Tips-for-Rel) The system shall provide functionality for all users to search for Tip Information records for possible selection to be linked-to the Relationship record the user selected on the Proj-Rel-Notes-Res-Tips page (Exhibit - B). |
| I-03740 | (SLS Tips-for-Rel) The system shall return Tip Information records with a status of "Active" or "Closed." Tip Information records with a status of "New" or "Canceled" shall not be listed. |
| I-03750 | (SLS Tips-for-Rel) The system shall allow the user to enter the Tip Information Submitter's Organization Name as a search parameter. The entered Organization Name shall be used to search against the Tip Submitter's User-Account record or the Source-Identification record of an internally submitted Tip Information record. The Organization Name shall be used as a "contains" search against the Submitter or Source's Organization Name, Org-Level-2, and Org-Level-3 fields. If the name is matched in any of the organization fields the search parameter is satisfied. |
| I-03760 | (SLS Tips-for-Rel) The system shall allow the user to enter the Submitter's Role as a search parameter. |
| I-03770 | (SLS Tips-for-Rel) The system shall support user entry of the Submitter's Role field with a dropdown list. |
| I-03780 | (SLS Tips-for-Rel) The system shall allow the user to enter Tip Number as a search parameter. The system shall reject all other search parameters as unnecessary when the Tip Number is entered. The system shall provide the user with an informative error message when any entered search parameter is invalid or unnecessary. |
| I-03790 | (SLS Tips-for-Rel) The system shall allow the user to enter the Event-or-Incident "Date Range - From/To" Tip Number as a search parameter. |
| I-03800 | (SLS Tips-for-Rel) The system shall compare the Event-or-Incident Date Range (From and To) field parameters against the Tip Information record's Approximate Date of Event-or -Incident. Either or both the "Date From" and "Date To" might be empty. When the user key enters into either date field the system shall require the content to be a valid date format. When the user enters both the "Date From" and "Date To" the system shall compare the dates to each other to ensure the "From Date" is not greater than the "To Date." When the user key enters a valid "From Date" the system shall compare it against the Tip Information record's Approximate Date of Event-or-Incident field. If the Approximate Date is not less than the "From Date" the searched field/parameter comparison is satisfied When the user key enters a valid "To Date" the system shall compare it against the Approximate Date field. If the Approximate Date is not greater than the "To Date" the search field/parameter comparison is satisfied. When the user key enters both the "From Date" and the "To Date" both comparison's against the Approximate Date must be satisfied. |
| I-03810 | (SLS Tips-for-Rel) The system shall allow the user to enter the Zip-or-Postal Code to be searched against the Tip Information record's Event-or-Incident's Zip-or-Postal Code field. A wild card match shall be used starting with the leftmost field positions, such as, 159 equals 159* |
| I-03820 | (SLS Tips-for-Rel) The system shall allow the user to enter City to be searched against the Tip Information record's Event-or-Incident's City field. A wild card match shall be used starting with the leftmost field positions, such as, Pitts equals Pitts* |
| I-03830 | (SLS Tips-for-Rel) The system shall allow the user to enter State to be searched against the Tip Information record's Event-or-Incident's State field. An exact match shall be used to satisfy the search parameter when entered. |
| I-03840 | (SLS Tips-for-Rel) The system shall support user entry of the State with a dropdown list. |
| I-03850 | (SLS Tips-for-Rel) The system shall allow the user to enter the Outcome search parameter to be searched against the Tip Information record's Event-or-Incident Outcome field. A "contains" match search shall be used. |
| I-03860 | (SLS Tips-for-Rel) The system shall allow the user to enter the Drug-or-Chemical Name search parameter to be searched against the Tip Information record's Event-or-Incident Drug-or-Chemical Name field. A "contains" match search shall be used. |
| I-03870 | (SLS Tips-for-Rel) The system shall list Tip Information records that satisfy all entered search parameters or are already linked-to the Relationship listed at the top of the page. |
| I-03880 | (SLS Tips-for-Rel) The system shall present the Project's Title, Assigned-To, Created-By, Date Created, Edited-By, Date Edited, Status & Project Record ID near the top of the page. |
| I-03890 | (SLS Tips-for-Rel) The system shall present the Relationship's Summary, Created-By, Date-Created, Edited-By, Date Edited, Status & Relationship Record ID fields beneath the Project Information near the top of the page. |
| I-03900 | (SLS Tips-for-Rel) The system shall provide functionality listing not only Tips matching search parameters, but Tips link to this Relationship (for potential "deselect"). |
| I-03910 | (SLS Tips-for-Rel) The system shall list Tip Information records in reverse chronological order of date created. |
| I-03920 | (SLS Tips-for-Rel) The system shall list the Project Title/Relationship Summary of each relationship the following Tip is linked to (see next requirement). |
| I-03930 | (SLS Tips-for-Rel) The system shall list the following Tips fields (linked to the preceding Tip) from left-to-right: Date Created, Type (Tip), Sub-Type (Tip Number), Limited Content (see Exhibit-B), Source of Info (see Exhibit-B) & Tip Record Id. |
| I-03940 | (SLS Tips-for-Rel) The system shall permit users to select a Tip and access it through the AddViewEditTip page (see Exhibit-GH). |
| I-03950 | (SLS Tips-for-Rel) The system shall provide functionality for users to select ([x] checkbox) to save or retain this Tip-to-Relationship (id'd in the header), or to de-select ([ ] checkbox) to not create or delete an existing item. All users can select a Tip Information record to be linked-to the Relationship listed near the top of this page. Only Administrator users can deselect a Tip Information record previously linked to the Relationship listed near the top of this page. The system shall support the select/deselect functionality by placing a checkbox in front of each listed Tip Information line. [x] Checked checkbox when initially presented indicates the Tip Information record is already linked-to the Relationship. [ ] An unchecked checkbox when initially presented indicates the Tip Information record is not linked-to the Relationship. |
| I-03960 | (SLS Tips-for-Rel) The system shall present a confirmation message when a user either: - Selects a Tip Information record to link-to the Relationship record - Deselects a Tip Information record to remove its link-to the Relationship record |
| I-03970 | (SLS Tips-for-Rel) The system shall log all Select and Deselect actions taken on this page. |
| (Internal - Search, List, and Select: Tips, Notes, and Research Items also refer to SENTRY Requirements (Exhibits).xls / Search Tips (Exhibit - F)) |
|
| I-03980 | (Search Tips) The system shall provide functionality for all users to enter parameters used to search for and to list Tip Information records. The system shall provide direct access to this Search Tips page without prior selection of a Relationship record. This Search Tips section shall refer back to the preceding "SLS Tips-for-Rel" section to identify search functions already documented. The search functionality shall require all entered search parameters be satisfied to return and list a Tip Information record. The system shall return and list all Tip Information records when no search parameters are entered by the user. The system shall NOT return Tip Information records that have a status of "New" or "Canceled" unless the "New" or "Canceled" unless the Tip Status search parameter entered is either "New" or "Canceled." Comment: Tip Information records with a status of "New" or "Canceled" are not generally available for use. |
| I-03990 | (Search Tips) The system shall conduct a Tip Status search based on the search parameters selected from the dropdown list. |
| I-04000 | (Search Tips) The system shall conduct a search of the Submitted Date Range (From and To) field parameters. Refer to date-range search documentation included in the preceding SLS Tips-for-Rel section . |
| I-04010 | (Search Tips) The system shall conduct a search of the following Submitter's fields: Last Name City State/Province/Territory (State supported by dropdown list) Zip or Postal Code Country (supported by dropdown list) Organization (refer to SLS Tips-for-Rel) Role (refer to SLS Tips-for-Rel) |
| I-04020 | (Search Tips) The system shall conduct a search of the following Event-or-Incident fields: Tip Number (refer to SLS Tips-for-Rel) Date Range (From and To) (refer to SLS Tips-for-Rel) Location's City, State/Province/Territory (State supported by dropdown list), Zip or Postal Code (refer to SLS Tips-for-Rel) Outcome (refer to SLS Tips-for-Rel) Drug or Chemical Name (refer to SLS Tips-for-Rel) Initial Follow-up Contact Made (Yes/No) (supported by dropdown list, unless [ ] checkbox is used) |
| I-04030 | (Search Tips) The system shall list Tip Information records that matched all search parameters entered; beneath each listed Tip list all Notes and Research Items linked-to the Tip Information record. List Notes and Research Items in reverse chronological order by date-created; Notes and Research Items might be interspersed. |
| I-04040 | (Search Tips) When the user enters the Tip Number search parameter, the system shall search for and list the individual Tip Information record (if found) plus Note and Research Item records linked-to the Tip Information record. List Notes and Research Items in reverse chronological order by date-created; Notes and Research Items might be interspersed. In addition, the system shall list all unassigned (not linked-to any Project, Relationship, or Tip Information record) Note and Research Item records. These unassigned Notes and Research Items shall be listed with an unchecked [ ] checkbox preceding the listing. The system shall allow the user to select an unassigned Note or Research Item by checking [x] the checkbox preceding the listing. When the page search results and related user actions are saved, the system shall link each selected/checked Note or Research item to the Tip listed through search by Tip Number. |
| I-04050 | (Search Tips) The system shall list the Project Title/Relationship Summary of each relationship the following Tip is linked to (as well as the Project & Relationship Record ID). |
| I-04060 | (Search Tips) The system shall list the following Tips fields from left-to-right: Date Created, Type (Tip), Sub-Type (Tip Number), Limited Content (see Exhibit-B), Source of Info (see Exhibit-B) & Tip Record Id. |
| I-04070 | (Search Tips) The system shall listing only Tips with a status of "Active" or "Closed" (Except when the user enters Tip Status as a search parameter). |
| I-04080 | (Search Tips) The system shall permit users to select a Tip and access it through the AddViewEditTip page (see Exhibit-GH). |
| I-04090 | (Search Tips) The system shall list the following Notes fields (linked to this Tip) from left-to-right: [ ], Created-By, Date Created, Edited-By, Date-Edited, Type (Note), Sub-Type (Phone, E-mail), Limited Content (see Exhibit-B), Source of Info (see Exhibit-B) & Note Record Id. |
| I-04100 | (Search Tips) The system shall allow the user to select a Note and access it through the AddViewEditNote page (see Exhibit-I). |
| I-04110 | (Search Tips) The system shall list the following Research Item fields (linked to this Tip) from left-to-right: [ ], Created-By, Date Created, Edited-By, Date-Edited, Type (Public Awareness), Sub-Type (Legislation), Limited Content (see Exhibit-B), Source of Info (see Exhibit-B) & Research Item Record Id. |
| I-04120 | (Search Tips) The system shall permit users to select a Research Item and access it through an AddViewEditResearchItem page (see Exhibit-J). |
| I-04130 | (Search Tips) The system shall present a confirmation message when a user either: - Selects a Note or Research Item record to link-to the Tip Information record - Deselects a Note or Research Item to remove its link-to the Tip Information record |
| I-04140 | (Search Tips) The system shall log all Select and Deselect actions taken on this page. |
| I-04150 | (Search Tips) The system shall allow the user to select a listed Tip to generate a report including information from the Tip and all Note and Research Item records linked directly to the selected Tip. |
| (Internal - View Internal Audit-Trail Entries) | |
| I-04160 | (View Audit Trail) The system shall provide functionality for users to view the system audit-trail entries. |
| I-04170 | (View Audit Trail) The system shall restrict which user-function the view audit-trail. (Refer to EXT Functionality Matrix) |
| (Internal - Retention of Original Submitted Information) | |
| I-04180 | (Retention) A determination needs to be made about whether each original submitted information record must be retained as entered. The possibility exists that personally identifiable information (PII), although not requested, may be included within information submitted. The externally submitted information record is passed to the SENTRY internal application where the PII shall be removed through edit of the original record by an Administrator user. Therefore, if the original record needs to be retained it must be captured prior to any editing. |
| (Internal - Initial Script Loading of Tables) | |
| I-04190 | The system shall provide for script loading of the JNS/Username - Name Table. |
| (Internal - Dropdown List - Initial Script Loading) | |
| I-04200 | The system shall provide for script loading of the following dropdown lists: - State - Role - User Function (Analyst/Administrator) - Contact Type (Phone, E-mail, Other) - Tip Status (New, Canceled, Active, Closed) - Project/Relationship Status (Open/Closed) - User-Account and Source-Identification Status (Active/Inactive) - Yes/No (options, if used) - Research Item Record Types (Abuse, Production, Packaging, Distribution, Public Awareness) - Public Awareness Type (Attitudinal Survey/Legislation/Public Service Announcement/Drug Scheduling/Media Report/Comment) - Route of Administration - Gender of Population Involved - Distribution Type - Packaging Type |
| (Internal - Dropdown List - Online Maintenance) | |
| I-04210 | The system shall provide functionality for the Administrator to maintain these dropdown lists: - Substance Category - Role (Previously Career) - Dissemination Restriction - |
| (Internal -Online Maintenance of JNS/Username - Name Table) | |
| I-04220 | The system shall provide online update functionality of the JNS/Username - Name Table. |
| (Internal - Generate Report for Selected Project, Relationship, or Tip) | |
| I-04230 | The system shall provide functionality to select a listed Project and then generate a report including information from the Project record and all Relationship, Tip, Note, and Research Item records linked directly-or-indirectly to the selected Project. (Reference the Internal - Search, List, and Select Projects requirement, and also the SENTRY Requirements (Exhibits).xls / Exhibit {A} SLS Projects) |
| I-04240 | The system shall provide functionality to select a listed Relationship and then generate a report including information from the Relationship record and all Tip Information, Note, and Research Item records linked directly-or-indirectly to the selected Relationship. (Reference the Internal - Search, List, Select, and Deselect: Relationships for Project requirement, and also the SENTRY Requirements (Exhibits).xls / Exhibit {C} SLS Rels-for-Proj) |
| I-04250 | The system shall provide functionality to select a listed Tip and then generate a report including information from the Tip Information record and all Note and Research Item records linked directly to the selected Tip. (Reference the Internal - Search, List, and Select: Tips, Notes, and Research Items requirement, and also the SENTRY Requirements (Exhibits).xls / Exhibit {F} Search Tips) |
| I-04260 | The system shall provide the logged-in user's name(Last, First & Middle) as part of the report's header. |
| I-04270 | When selected, the system shall provide all of the Project record's information on the report: Title, Description, Status, Assigned-To, Created-By, Date/Time Created, Edited-by, and Date/Time Edited The system shall present all Note and Research Item records directly linked-to the Project record followed by a repeat of each Relationship record's information and all Tip, Note, and Research Item records directly-or-indirectly linked to the Relationship. |
| I-04280 | When selected, the system shall provide all of the Relationship record's information on the report: Summary, Description, Status, Created-By, Date/Time Created, Edited-by, and Date/Time Edited Multiple Relationship records might be provided when the report is generated through user selection of a Project. When multiple Relationship records are provided the system shall list the Relationship records in chronological order of Date/Time Created. The system shall present all Note and Research Item records directly linked-to the Relationship record followed by a repeat of each Tip record and its Note and Research Item records directly linked to the Tip. The report shall present the Tip records in chronological order of Date/Time Created. The system shall present the Note and Research Item records in order by the source-of-information then by chronological order of Date/Time Created immediately beneath the Project, Relationship, or Tip the records are directly linked-to.. |
| I-04290 | The system shall provide all Tip Information record fields on the report. The Tip Information record shall be listed in chronological order of Date-Created beneath the Relationship record's information when the Tip is listed through a Project or Relationship selection. |
| I-04300 | The system shall provide all Note and Research Item record fields on the report. Note and Research Item records shall be listed beneath the Project, Relationship, or Tip Information record the Note or Research Item is linked-to, then by their source-of-information, then chronologically by Date/Time Created. |
| Security (SEC) | |
| Req. ID - Rev. | Requirement |
| I-SEC001 | The system shall prevent multiple concurrent active sessions for one user identification. (DOJ Standard 2640.2D - 16b) If this is deemed impossible based on operational need, the system must then provide a user notification to identify that the user session is active in another location. |
| I-SEC002 | The system shall maintain an audit trail of activity sufficient to reconstruct security relevant events. (DOJ Standard 2640.2D – 19a1.) |
| I-SEC003 | The audit trail should include the identification of each entity accessing the system, time and date of the access, time and date the entity terminating access, activities performed using an administrator’s identification, and activities that could modify, bypass, or negate the system security safeguards. (DOJ Standard 2640.2D – 19a2.) |
| I-SEC004 | The system shall protect the audit trail from actions such as unauthorized access, modification, and destruction that would negate its forensic value. (DOJ Standard 2640.2D – 19a3.) |
| I-SEC005 | The system shall retain the audit trail for a period of 90 days at a minimum. (DOJ Standard 2640.2D – 19a4.) |
| I-SEC006 | The system shall require the user to login again anytime the user's session remains idle for 20 minutes or longer. |
| Accessibility (ACC (Section 508)) | |
| Req. ID - Rev. | Requirement |
| I-ACC001 | The system shall provide a text equivalent for every non-text element. |
| I-ACC002 | Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. |
| I-ACC003 | Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup. |
| I-ACC004 | Documents shall be organized so they are readable without requiring an associated style sheet. |
| I-ACC005 | Redundant textlinks shall be provided for each active region of a server-side image map. |
| I-ACC006 | Client-side image maps shall be provided instead of server-side image maps except where the regions cannot be defined with an available geometric shape. |
| I-ACC007 | Row and column headers shall be identified for data tables. |
| I-ACC008 | Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers. |
| I-ACC009 | Frames shall be titled with text that facilitates frame identification and navigation. |
| I-ACC010 | Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz. |
| I-ACC011 | A text-only page, with equivalent information or functionality, shall be provided to make a web site comply with the provisions of this section, when compliance cannot be accomplished in any other way. The content of the text-only page shall be updated whenever the primary page changes. |
| I-ACC012 | When pages utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by assistive technology. |
| I-ACC013 | When electronic forms are designed to be completed on-line, the form shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues. |
| I-ACC014 | A method shall be provided that permits users to skip repetitive navigation links. |
| I-ACC015 | When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. |
| Non Functional (NF) | |
| Req. ID - Rev. | Requirement |
| I-NF001 | The system shall be developed in Microsoft Visual Studio 2005. |
| I-NF002 | The system shall be developed in Microsoft Visual Basic.NET 2005. |
| I-NF003 | The system shall be developed in ASP.NET 2.0. |
| I-NF004 | The system shall use SQL Server 2005. |
| I-NF005 | The system shall use Windows Server 2003. |
| I-NF006 | Each component of the system shall have an install package. |
| Performance (PRF) | |
| Req. ID - Rev. | Requirement |
| I-PRF001 | The system shall be scalable. (scale out) Each tier of the system shall be written to accommodate multiple installations on one or more machines. |
| I-PRF002 | The system should scale linearly when increasing concurrent users and the amount of data. |
| I-PRF003 | The system shall initially be written to support 10-50 concurrent users. |
| I-PRF004 | The response time for a client shall not be more than 2 seconds for a given concurrent load. |
| Functionality | User Function | ||
| No. | Title / Comment | Analyst | Admin |
| 1 | View SENTRY Landing Page (Logged In) (SENTRY Shield) |
x | x |
| 2 | Source of Information Records - Search, List, and Select (Includes Source Identification and External User Account Records) |
x | x |
| 3 | Source Identification Records - Add/View | x | x |
| 4 | Source Identification Records - Edit (Allow Delete when Source ID not Linked-to) | x | |
| 5 | Username-to-Name Table - List and Select | x | |
| 6 | Username-to-Name Table - Add/Edit (Initially script load all JNS/NDIC username/Names) | x | |
| 7 | Project Records - Add/View | x | x |
| 8 | Project Records - Edit | x | |
| 9 | Relationship Records - Add/View | x | x |
| 10 | Relationship Records - Edit | x | |
| 11 | Tip Information Records (Tips) - Add (Requires TSB to Activate Add Function) | x | |
| 12 | Tip Information Records (Tips) - View | x | x |
| 13 | Tip Information Records (Tips) - Edit | x | |
| 14 | Notes - Add/View | x | x |
| 15 | Notes - Edit (Includes Delete) | x | |
| 16 | Research Item (Abuse) - Add/View | x | x |
| 17 | Research Item (Abuse) - Edit (Includes Delete) | x | |
| 18 | Research Item (Production) - Add/View | x | x |
| 19 | Research Item (Production) - Edit (Includes Delete) | x | |
| 20 | Research Item (Packaging) - Add/View | x | x |
| 21 | Research Item (Packaging) - Edit (Includes Delete) | x | |
| 22 | Research Item (Distribution) - Add/View | x | x |
| 23 | Research Item (Distribution) - Edit (Includes Delete) | x | |
| 24 | Research Item (Public Awareness) - Add/View | x | x |
| 25 | Research Item (Public Awareness) - Edit (Includes Delete) | x | |
| 26 | Search, List, and Select Projects (Exhibit {A} - SLS Projects) |
x | x |
| 27 | List and Select Project's: Relationships, Notes, and Research Items (Exhibit {B} - Proj-Rel-Notes-Res) |
x | x |
| 28 | List and Select Project's: Relationships, Notes, and Research Items (Exhibit {B} - Proj-Rel-Notes-Res) (Allow Delete of Project Record when not Linked-to) |
x | |
| 29 | List, Select, and Deselect Project's: Relationships, Notes, and Research Items (Exhibit {B} - Proj-Rel-Notes-Res) (Deselect (remove) Relationships, Notes, and Research Items from this Project) |
x | |
| 30 | Search, List, Select, and Deselect: Relationships for Project (Exhibit {C} - SLS Rels-for-Proj) |
x | x |
| 31 | Search, List, Select, and Deselect: Relationships for Project (Exhibit {C} - SLS Rels-for-Proj) (Deselect (remove) Relationships from this Project) |
x | |
| 32 | Selected Relationship: List and Select/Deselect Notes, Research Items, and Tips, Notes, and Research Items (Exhibit {D} - Rel-Notes-Res-Tips) |
x | x |
| 33 | Selected Relationship: List and Select/Deselect Notes, Research Items, and Tips, Notes, and Research Items (Exhibit {D} - Rel-Notes-Res-Tips) (Allow Delete of Relationship Record when not Linked-to) |
x | |
| 34 | Selected Relationship: List and Select/Deselect Notes, Research Items, and Tips, Notes, and Research Items (Exhibit {D} - Rel-Notes-Res-Tips) (Deselect (remove) Notes, Research Items, and Tips from this Relationship) |
x | |
| 35 | Search, List, Select, and Deselect: Tips for Relationship (Exhibit {E} - SLS Tips-for-Rel) |
x | x |
| 36 | Search, List, Select, and Deselect: Tips for Relationship (Exhibit {E} - SLS Tips-for-Rel) (Deselect (remove) Tips from this Relationship) |
x | |
| 37 | Search, List, Select/Deselect: Tips, Notes, and Research Items (Exhibit {F} Search Tips) |
x | x |
| 38 | Search, List, Select/Deselect: Tips, Notes, and Research Items (Exhibit {F} Search Tips) (Deselect (remove) Notes and Research Items from this Tip) |
x | |
| 39 | Select, Create, Sort, and Print Detailed Report by: Project, Relationship, or Tip | x | x |
| 40 | Maintain Dropdown List Tables (Perform all maintenance on the Internal application; push table to External as necessary) |
x | |
| 41 | View Internal Audit-Trail Entries | x | x |
| 42 | |||
| File Type | application/vnd.ms-excel |
| Author | bifancp |
| Last Modified By | mcculac |
| File Modified | 2007-04-13 |
| File Created | 2006-12-15 |