Business Requirements
Business Requirements
An online user survey was held from 27th Feb 2015 to 11th March 2015 to gather responses to a series of questions aimed at deciphering what aspects of the user interface are being used and what could be improved on.
Detailed Requirements are captured in the following sections:
Search Options
The existing criteria fields in the Visitor Search page will be expanded to include the following options:
- Org unit
- Originator
- Visit start date
- Visit end date
- Current visits
- Past visits
- Future visits
- All of the search criteria are optional, and there will be a “Select All” and “Clear” option for the checkboxes.
- Current visits, past visits and future visits search options will be grouped together.
- If there are no checkboxes ticked, then the application will assume “Return everything”.
- If some are selected, then the application will return results dependant on the selection criteria.
- If all are selected, the application will return all results.
- None of the above search options should be mandatory.
Search Results
When you perform a search using the criteria above, the existing columns of data will be expanded to include the following information in the returned search results:
- Date of Birth
- Org unit (‘Owning Department’)
- Max (Start Date) and max (End Date) of all visits to be displayed in initial results
- Record count of number of visits
The search results will be sortable by column heading – ie click on a column to sort on that column by ascending order, then click again to sort by descending order. An icon will be displayed showing sort order next to the field. The default sort order will be by Start Date, with the latest date being displayed first.
There is a requirement not to show the “Add Visitor” button if any of the filters have been applied. When the button is not displayed, a message will be shown in place of the button to inform users what to do to enable the Add Visitor button. The text will read "Remove filters to enable Add Visitor option".
Fields
When you click on one of the returned results, you are taken to the Visitor Details data entry page. There are some minor updates required to aid usability.
- Initials: this should be made clear that it is only forename initials to be entered and not forename and surname. This could be a label change to read “This will be printed before the surname on the card”.
- On the Add Visit page, wording is to be inserted on the page next to the Visit Type select option to encourage users (other than OLL) not to select the Visitor Student option unless the student is registered with EUCLID. This could read “Visiting students need to be registered with EUCLID” next to the option.
If the text of these messages is too long to show on the screen, it could be displayed by using a "?" or information icon that the user could click on to show the message.
PURE
PURE is to be a selectable 'Service' for visitors, rather than an option on the entry screen. Staff-Id entry is required for PURE, so field will be kept in the visitor details section.
Service
The Service page will be made more dynamic and easier to use. When someone selects a service, any depending services are automatically selected, and any that are not applicable are greyed out. This is for the visitor’s page only, and not for the Identity Services tab. See the Service Dependencies Matrix document for dependencies. The benefits are of this method will be a greater degree of validation and ease of use in service selection.
Services are to be grouped by category to make the list easier to follow. Eg, “Network access”, then (wireless / VPN / LapLAN), or “Web Services” then (MyEd / Learn / Wiki). See the Matrix grouping services document.
If any service is selected, then EASE, Unidesk and Central Auth are automatically added.
It should be possible to create a visitor without any services, e.g a visiting plumbing contractor doesn't' need any.
If Staffmail is selected, then Exchange is automatically added to provide a calendar.
Next to each service will be a service description, accessed by clicking on a "?" or and information icon next to the service name.
Service names will be pulled from a database table, so that any future updates are easily made.
The data contained in the Service Dependancy Matrix and the Matrix Grouping Services Excel spreadsheets will be translated into a database driven system for ease of maintenance. This means that dependancies and groupings have a parent - child relationship with none hard coded.
System Description Document
The System Description Document (SDD) will be updated with the Service Selection and User Service changes that have been made to the application. This will allow Applications Management and Service Management to make future updates.
Matrix documents