PWS Appendix 3_Ticketing System RVTM_FINAL.xlsx

Title Page

NATIONAL ARCHIVES AND RECORDS ADMINISTRATION (NARA)

NARA Ticketing System

&F Page &P of

Requirements

<type of requirement> <Business | Stakeholder | System | Business Rule> <required> <category of requirement> <Functional | Non-functional | Constraint | N/A> <N/A is to be used only when Type=Business> <required> <sub-category of requirement for Non-Functional requirements only>

<requirement priority> <stakeholder-assigned priority MoSCoW:

Must | Should | Could | Would> <optional> <identifier of release in which the requirement will be / is developed> <do not delete this column, it should be populated during the appropriate phase of the project> <required when process descriptions are defined for the project> <mapping to the process descriptions that are appropriate to the requirement> <If process descriptions will not be developed for the project, delete this column; if process descriptions will be developed but have not yet been defined, use the value "TBD"> <required when use cases are defined for the project> <mapping to the business or system use cases that are appropriate to the requirement> <If use cases will not be developed for the project, delete this column; if use cases will be developed but have not yet been defined, use the value "TBD"> <optional> <additional pertinent information which does not fit into one of the other columns> <do not delete this column, just leave it empty if notes are not needed> <required> <indication of design elements (e.g., subsystem or class) that are relevant to the requirement> <may map to more than one design element, in which case abbreviations or IDs are preferred over names> <use "N/A" for business requirements> < at least one column (tracing) is required> <when appropriate to the project, you may use multiple columns, one per type of design entity (e.g., subsystem)> <required when iterations are used for the project> <identifier of iteration in which the requirement will be / is developed> <"N/A" for business requirements> <when the column is not needed, delete it> <required> <inspection, analysis, test, demonstration, or certification> <use "N/A" for business requirements> <required> <identification of the test cases to be used by NARA to verify the requirement> <use "N/A" for business requirements> <required> <Pass, Fail> <use "N/A" for business requirements> <optional> <attributes to be verified to determine if the system element meets the requirement and satisfies the design.> <use "N/A" for business requirements> <when the column is not needed, delete it> <required> <identification of the test cases to be used by NARA to validate the requirement> <use "N/A" for business requirements> <required> <Pass, Fail> <use "N/A" for business requirements>

1.0 The solution shall provide the capability to manage events. Business Event Management Manage means to create, retrieve, edit and delete events.

Authorized users will be able to promote events online, customize event types including free events and paid events, seating charts, RSVP management etc. L

PL

PL

1.3 The solution shall provide the capability to manage the number of attendees for events. Business Event Management Manage means to create, retrieve, edit and delete the minimum and maximum number of attendees for events. L

PL

PL

2.1 The solution shall provide the capability for an authorized user to customize tickets for an event. Business Ticket Management System Administrators will be able to create different ticket categories (e.g., general admission, guided tour, special exhibition), pricing tiers including free tickets, offer add-ons, discounts, promo codes, and group rates to accommodate various visitor preferences and promotions. L

PL

2.2 The solution shall provide the capability to assign a Barcode with a unique identifier number to each event ticket. Business Ticket Management L

PL

3.0 The solution shall provide the capability for onsite self-service kiosks. Business Kiosk Attendees will be able to buy or reserve tickets, look up their prior online ticket purchases and print tickets using the barcode at the kiosk. L

PL

PL

PL

6.1 The solution shall provide the capability to support timed ticket entry for access to specific areas. Business Admissions L

PL

PL

PL

PL

14.0 The solution shall provide the capability to search for transactions, orders and events. Business Order Management This includes the ability to perform a keyword search and partial keyword search for orders and events using order/transaction number, event name, event date, customer information, or credit card information (last four digits), group reservations information etc. L

PL

15.0 The solution shall provide the capability for an authorized user to manage standard and ad hoc reports. Business Reporting Manage means to create, retrieve, update, and delete reports. This also includes exporting reports in various formats, e.g., .csv, .pdf, .xls, and .xlsx formats. L

PL

Associating records schedules with electronic records provides an inherent link between the NARA records schedule and an electronic records object. The records schedule item is 'associated' with the managed record objects as a rule, which determines the retention of the object. L

PL

PL

21.0 The solution user interface shall be responsive for use of the system on mobile devices.

Business Supportability This means the system has been designed to be responsive to the devices it’s viewed on, adjusting and resizing elements in order to optimally display across a broad range of devices, including desktop computers, laptops, tablets, and smartphones. Responsive design provides the best viewing experience independent of a user’s device. L

PL

22.0 The solution shall be accessible to a user via the web. Business Supportability The solution shall be accessible to a user using Mozilla Firefox, MS Edge, Google Chrome.

The browser versions to be supported will be dependent upon when the system is deployed into production and the browser versions supported in the NARA baseline at that time. L

PL

22.1 The system shall provide NARA the ability to incorporate their own subdomain name and URL for the ticketing system. Business Supportability L

PL

23.0 The solution shall be in compliance with NARA IT Security Requirements. Business Security L

PL

24.0 The solution shall comply with NARA's Privacy Policy. Business Compliance L

PL

25.0 The solution shall be in compliance with Section 508 Standards for Electronic and Information Technology. Business System Accessibility L

PL

26.0 The solution shall be 99% available, 24 hours a day, 7 days a week, with the exception of scheduled downtime. Business Availability The scheduled downtime shall be no more than four (4) consecutive hours of downtime in a 24 hour period. L

PL

27.0 The solution shall be compatible with NARA's Enterprise Architecture. Business System Architecture L

PL

28.0 The solution shall integrate with internal and external systems. Business System Interoperability L

PL

28.1 The solution shall integrate with Microsoft Dynamics Great Plains (GP) for the submission of sales transaction. Business System Interoperability Microsoft Dynamics Great Plains (GP) is the back office financial accounting system.

PL

32.0 The solution shall support Internet Protocol version 6 (IPv6). Business Hosting L

PL

33.0 The solution shall scale to handle increase in the number of concurrent users during customer activity peaks. Business Performance L

PL

34.0 The solution shall scale to handle future data growth without major design or architectural changes. Business Elasticity L

PL

PL

PL

40 The solution shall allow all users to make group reservations. Business Order Management The ticketing system shall provide a barcode and its associated unique sequence of numbers for each individual within the group. L

&F Page &P of

Standard Values

<Project Name> Requirements Verification Traceability Matrix (RVTM) / &A

&F Page &P of

WARNING! Some of the information in this worksheet is used to implement cascading drop-down lists in the 'Requirements' worksheet, be aware of this when modifying it, and especially when deleting columns! Refer to the 'Notes' worksheet for more information.

Column Descriptions

Values: Functional | NonFunctional | Constraint | NA

Values: Must | Should | Could | Would

at least one column (tracing) is required.

Iteration The iteration in which the requirements will be/is developed.

Yes, when iterations are used for the project. "N/A" for business requirements when the column is not needed, delete it.

Verification Method The method used to verify the requirement.

Values: inspection, analysis, test, demonstration, or certification

Values: Pass, Fail

Values: Pass, Fail, NA

No

<Project Name> Requirements Verification Traceability Matrix (RVTM) / &A

&F Page &P of

Notes

1A The 'Category' and 'Sub-Category' columns of the 'Requirements' worksheet are implemented as cascading drop-down lists, which means that the items in the 'Category' and 'Sub-Category' drop-down lists depend upon the value in another column. Simple drop-down lists (such as that implemented for the 'Type' column) and cascading drop-down lists have been implemented in the 'Requirements' worksheet to help ensure that consistent values are used for important information. The values used in columns with drop-down lists are restricted to the values in the list.

The implementation of the cascading drop-down lists utilizes three components: (1) The text values for the items in the drop-down lists of the 'Standard Values' worksheet, (2) A named range that defines each drop-down list, and (3) Data Validation for the 'Requirements' cells to which a drop-down list is applied.

1B A drop-down list is defined in the 'Standard Values' worksheet as a set of consecutive cells in a column. The uppermost cell (in row 1) is a label / header; the values in the cells below it are the values that will appear in the drop-down list. When sub-lists cascade from the values in the drop-down list, a drop-down list must also be defined for each of the values in the drop-down list.

For example, the 'Type' column in the 'Requirements' worksheet has a drop-down list; this drop-down list is defined in column A of the 'Standard Values' worksheet and has the values {Business, Stakeholder, System, BusinessRule}. The valid values in the 'Category' column cascade from the 'Type' value in the same row, so drop-down lists for {Business, Stakeholder, System, BusinessRule} are defined in the 'Standard Values' worksheet. When a drop-down list is displayed for a cell in the 'Category' column, Excel finds the drop-down list for the 'Type' value in the same row and displays it.

Note that it is possible for a 'Type' cell to be empty: in this case, Excel will not display a drop-down list for 'Category'. It is also possible to have an invalid value for 'Type' - although Excel will prevent one from being directly entered - in which case Excel will again not display a drop-down list for 'Category'. This behavior holds for all cascading drop-down lists, e.g., for 'Category and 'Sub-Category' also.

1C Defined names are used as part of the drop-down list implementation. A defined name is a text string that has a specific value (which can be an address range). In the RVTM, a name is defined for each drop-down list; it is the same as the list's label / header in the 'Standard Values' worksheet. For example, the name 'Type' is defined as 'Standard Values'!$A$2:$A$5. The names used in the RVTM are defined as global, i.e., they are accessible from any worksheet in the workbook.

When you have selected a cell range that has a name, the name appears in the Name Box in the upper left below the Ribbon and above the column designators. However, a possibly easier way to see all of the names in the workbook is to select Formulas > Name Manager from the Ribbon. The Name Manager dialog is displayed. From the Name Manager dialog, you can see the defined values of each name; you can also modify or delete a name.

1D A drop-down list is implemented for a cell by defining a data validation for the cell. To do this, click on a cell (or range of cells) and select Data > Data Tools > Data Validation > Data Validation... from the Ribbon. The Data Validation dialog is displayed. To implement a static (i.e., non-cascading) drop-down list, enter Allow=List, Source="=listname", Ignore blanks=checked and In-cell dropdown=checked (where listname is a defined name) in the Settings tab of the dialog under Validation criteria. Click OK to implement the data validation. This causes / enables the values indicated by the Source to be displayed as a drop-down list. For example, in the 'Requirements' worksheet for the 'Type' column, the data validation specifies Source="=Type" and the name Type is defined as 'Standard Values'!$A$2:$A$5 so the values {Business, Stakeholder, System, BusinessRule} are displayed in the drop-down list. (Note that Source="= 'Standard Values'!$A$2:$A$5" also works for a static drop-down list: the defined name Type is used in the RVTM template to be consistent with the defined names that are used for the cascading drop-down lists, and it provides a more obvious tie to the values.)

1E Columns with cascading drop-down lists are implemented a bit differently: Excel's INDIRECT function is used in conjunction with the defined names for the parent (or triggering) drop-down list values. A Data Validation for a cascading drop-down list is defined in the same way as for a simple drop-down list, except that Source=INDIRECT(refcell) is used, where refcell is the address of the cell whose value will indicate the drop-down list that will be displayed. For example, to cause the 'Category' drop-down list that is displayed in the 'Requirements' worksheet to depend upon the value of the 'Type' drop-down list in the same row, Source=INDIRECT($Cn) is used, where n is the row number. 'Type' is in column C, so this construct tells Excel to use the value in $Cn as the address range where the drop-down list values to display are found. Since the value in 'Type' is text, a way to translate the text into an address range is needed. This is done by defining a name for each value in the 'Type' drop-down list that points to the address range in the 'Standard Values' worksheet which contains the drop-down list that is to be displayed ("cascaded") for that 'Type' value. When Excel performs the INDIRECT function and finds the 'Type' value in refcell, it recognizes that the refcell value is a defined name and displays the values indicated by the defined name as the 'Category' drop-down list.

For example, if a 'Type' cell in the 'Requirements' worksheet contains the value "Stakeholder", when Excel displays the drop-down list for the 'Category' cell in the same row it will find that the name 'Stakeholder' is defined as 'Standard Values'!$E$2:$E$4. The text in 'Standard Values'!$E$2:$E$4 is {Functional, NonFunctional, Constraint}, so these are the values that Excel displays in the 'Category' drop-down list.

Note that the same defined name cannot indicate two different drop-down lists. There is a need in the 'Requirements' worksheet for two different drop-down lists which are associated with the value "Constraint"; thus, the values and names "Constraint" and "Constraint." are used. The trailing period in "Constraint." is not a defect but is used to distinguish between the two lists.

1F Note that Excel has some limitations on a defined name (i.e., the name itself, not its value):

1. Must begin with a letter or underscore character

2. Remaining characters in the name can be letters, numbers, periods, and underscore characters

3. Spaces are not allowed

4. Can contain uppercase and lowercase letters, but Excel does not distinguish between uppercase and lowercase characters

5. May contain no more than 255 characters

1G In the 'Requirements' worksheet, a custom warning message is displayed when a cell with a drop-down list is selected (i.e., clicked). It is displayed in a pop-up with a yellow background. This is accomplished via the Input Message tab of the Data Validation dialog. Show input message when cell is selected=checked and the custom message text is entered in the Input message box.

The 'Requirements' worksheet also prevents invalid values from being entered into a cell with a drop-down list. This is accomplished via the Error Text tab of the Data Validation dialog. Show error alert after invalid data is entered=checked and Style=Stop are specified, which causes an Excel-generated error message to be displayed and the data entry action to be terminated.

1H To easily determine which cells in a worksheet have data validation defined, select Home > Find & Select > Data Validation from the Ribbon. This causes the cells with a defined Data Validation to be shaded. To remove a data validation, select a cell or cells, select Data > Data Tools > Data Validation > Data Validation... from the Ribbon, and click Clear All in the Data Validation dialog.

In the 'Requirements' worksheet, data validation is typically defined for an entire column - except for the cells in the top three rows, which are header and information rows. One way to do this is to select the entire column, define the desired Data Validation, then select the top three cells and clear the Data Validation.

<Project Name> Requirements Verification Traceability Matrix (RVTM) / &A

&F Page &P of image1.png