Requirement Id | Description | Category | Module | Validation Test ID |
FR-1 | The system shall accept users’ text input of region names to search for walking tours.
FR-1.1
The system shall search region (text input) in the cloud database and return the walking tours in the region.
FR-1.2
The system shall list the walking tours for users to view. | Management | AW | VT-1 |
FR-2 | The system shall support the ability for users to save/download walking tours. | Management | AW, MA | VT-2 |
FR-3 | The system shall support the ability for users to select a walking tour from the search list or saved/downloaded walking tours to view its details. | Functional | MA | VT-1 |
FR-4 | The system shall direct users to go from one location to the next in the walking tour. | Functional | MA | VT-3 |
FR-5 | The system shall convert location coordinates to pixels on walking tour maps.
FR-5.1
The system shall show the locations of a walking tour on a map.
FR-5.2
The system shall show the location of the user on the walking tour map using GPS updated when map updates are available. | Operational | MF | VT-3 |
FR-6 | The system shall support the ability for users to select a location of a walking tour to view the location information (address, description, images). | Functional | MA | VT-1 |
FR-7 | The system shall display location information (address, description, images) when the user is at a location of the walking tour.
FR-7.1
The system shall play the location description audio files automatically. | Functional | MA | VT-3 |
FR-8 | The system shall convert the location description text file to an audio file.
FR-8.1
The system shall support the ability for users to listen to location descriptions. | Operational | MA | VT-4, VT-3 |
FR-9 | The system shall support the ability for users to delete walking tours from their device’s local memory/saved walking tours. | Functional | MA | VT-2 |
FR-10 | The system shall port locations from Google Maps to the cloud database. | Operational | MF | VT-3 |
FR-11 | The system shall port map tiles and directions of approved walking tours from Google Maps to the cloud database | Operational | MF | VT-3 |
FR-12 | The system shall require/accept developer users to log in with a username and a password. | Management | AW | VT-6 |
FR-13 | The system shall accept developer users’ text input of location names to search for locations.
FR-13.1
The system shall search locations (text input) in the cloud database and return the locations. | Management | AW | VT-5 |
FR-14 | The system shall support the ability for developer users to create/edit locations.
FR-14.1
The system shall require developer users’ input of location address, name, and description, and pictures.
FR-14.2
The system shall store/update locations in the cloud database. | Management | AW | VT-5 |
FR-15 | The system shall support the ability for developer users to create/edit walking tours (ordered locations).
FR-15.1
The system shall store/update the walking tours in the cloud database once they are approved by system administrators. | Management | AW | VT-5 |
FR-16 | The system shall support the ability for developer users to delete walking tours/ locations.
FR-16.1
The system shall delete walking tours/locations in the cloud database. | Management | AW | VT-5 |
FR-17 | The system shall support developer users to register for an account. | Management | AW | VT-6 |
FR-18 | The system shall store developer users’ account information in the cloud database. | Management | AW | VT-6 |
FR-19 | The system shall grant developer users access to their accounts when login is successful. | Management | AW | VT-6 |
FR-20 | The system shall support the ability for developer users to retrieve/reset passwords. | Management | AW | VT-6 |
FR-21 | The system shall support the ability for developer users to deactivate/delete their accounts.
FR-21.1
The system shall delete user accounts from the cloud database. | Management | AW | VT-6 |
NFR-1 | The system shall operate on iOS and Android smart phone operating systems. | Operational | MA | VT-1 |
NFR-2 | The system shall run on web browsers. | Operational | AW | VT-2 |
NFR-3 | The system shall require walking tours be approved by system administrators. | Operational | MA, AW | VT-5 |
NFR-4 | The system shall be in English. | Operational | Ma, AW | VT-1 |
NFR-5 | The system shall store user accounts, walking tours, and locations data using relational data structure in the cloud database.
Customer ID First Name Last Name Email Address Password Tour ID Location1 ID Location2 ID Location3 ID LocationX ID Key Words Location ID Name Address Description Images Coordinates | Operational | MF, AW, MA | VT-2 |
NFR-6 | The system shall provide a tutorial for new users and after users log in for the first time. | Operational | MA | VT-2 |
NFR-7 | The system shall provide a FAQ page. | Operational | AW | VT-7 |
NFR-8 | The system shall provide an email address for all users to send feedback or seek technical help.
NFR-8.1
The system shall provide technical help to developer users in less than two business days.
NFR-8.2
The system shall provide technical help to users in less than five businesses days. | Operational | MA, AW | VT-7 |
VT-1 - Search ValidationSearching is the primary way users discover walking tours and is a key feature of the system (FR-1). Typing in a location should return tours within the search region (FR-1.1). These locations should be displayed as a list (FR-1.2). Each item in the returned list should be interactable and display more information about the specific walking tour (FR-3). Part of the information displayed should show location information including address, description, and images from the location (FR-6). Text should be displayed in English (NFR-4).
VT-2 - User Account Validation
WalkingStick users are capable of creating personal accounts for tracking and storing their data. User accounts should be stored in the cloud (NFR-5). Users should be able to access their accounts using a web browser (NFR-2). Users should be prompted with a tutorial of how to use the system once their account is created and they log in for the first time (NFR-6). Users should be able to view a list of saved/downloaded walking tours as part of their account (FR-2). Users should be able to delete walking tours from their saved/downloaded list (FR-9).
VT-3 - Map Data Validation
Users are guided on their walking tour by location and map data. The system should display location information while they are at a tour location (FR-7). Users should be directed from their current location to the next location on the tour (FR-4). The system should play audio files about the location automatically (FR-7.1). The location coordinates should be displayed as pixels on the tour map (FR-5, FR-5.1). The user’s current location should be displayed on the map (FR-5.2). Location coordinates and map tiles for approved walking tours should be stored in the cloud database (FR-10, FR-11).
VT-4 - Text to Audio Validation
Text about a specific location on an approved walking tour can be read aloud to the user by the system. The system should convert location description text to an audio file (FR-8). The user should have the option to play the audio file from the location information (FR-8.1).
VT-5 - Walking Tour Development Validation
Walking Tours are created, modified, and removed by developers. The content creation process is a key design feature. Developers should be able to search for locations using the search bar (FR-13). Search results should be pulled from the cloud database and displayed to the developer (FR-13.1). Developers should be able to create/modify locations (FR-14) Locations should require the input of address, name, description, and images before being saved (FR-14.1). Locations should be stored/updated in the cloud database when changes are made (FR-14.2). Walking tours should be able to be created/edited by developers (FR-15). Walking tour creation and modification should require system administration approval (NFR-3). Walking tours should be stored/updated in the cloud database once approved. Developers should be able to delete walking tours and locations (FR-16). Walking tours and locations should be removed from the cloud database once deleted (FR-16.1).
VT-6 - Developer Account Validation
Developer accounts are used for content creation and modification. Developers should be able to register for an account with elevated privileges (FR-17). Developer accounts should be stored in the cloud database (FR-18). Developers should be able to log in with their username and password (FR-12). Developers should be able to access their accounts and elevated privileges once login is successful (FR-19). Developers should be able to retrieve or reset their passwords (FR-20). Developers should be presented with an option to delete their accounts(FR-21). Deleted developer accounts should be removed from the cloud database (FR-21.1).
VT-7 - Documentation/Contact Validation
Documentation for common questions and a way to contact the system support staff should be made available. A FAQ page should be presented to the user in an obvious but unobtrusive manner (NFR-7). A contact form should be available to the user to provide an email account and a text description of their feedback/needs (NFR-8). The technical support team should receive notification of developer requests for technical support and should respond within two business days (NFR-8.1). The technical support team should receive notification of user requests for technical support and should respond within five business days (NFR-8.2).