You are on page 1of 1

Functional Requirements Non-Functional Requirements

1. Inputs 1. Resources and Physical Environment


• Search bar • Equipment: Compatibility with desktop PCs as well as mobile devices
• Drop-down menus (e.g., smartphones)
• Hyperlinks that provide access to a registration form and a • Locations: Accessible from desktop pc environments like homes and
log-in option afterwards. workplaces as well as on-the-go via mobile devices.
• Widgets which embed related content and services (e.g., • Physical space: Τhe structure of the website makes it responsive to
participation slot booking form) various screen sizes and through resizing of the browser window no
• A selection of hyperlinks in different font sizes and colours part of the functionality is lost.
which provide access to related content (e.g., a “Contact Us”
link permits immediate access to the relevant webpage form) 2. Interfaces (including interaction with the user and other applications)
• Smartly designed interface in terms of structure, layout and
• Distinguishable and marginally interactive navigational menu,
formatting.
at the top of the page and in a large font.
• User-friendly and aesthetically pleasant interface, achieved by careful
• Textual and numerical fields where users input required data
colour scheme and font selections.
(e.g., booking form)
• Distinct and interactive navigational menu in a large font at the top of
• Links to external website (e.g., product pages of possible
the page. Constant appearance of this menu.
tournament prizes)
• Well placed media like photographs, to offer users an instant and
• Social media icons (e.g., Facebook, Twitter, YouTube) that
engaging depiction of our services.
provide access to third-party web-based platforms.
• Embedded widgets which provide interaction with selected webpage
2. Processing content, such as updated tournament schedules and booking forms,
• A secure membership registration webpage so that the user as well as interaction with third-party platforms like YouTube and
can book his participation slot after creating an account. google maps.
• Online and interactive forms (e.g., booking form)
3. User and Human Factors
3. Outputs • The site aims to reach a fairly heterogeneous group of people, with
• Information icons and spot-on hints embedded within an emphasis on those who love sports and running.
registration and booking forms (e.g., calendar icon next to • The website aims to reach a large and quite heterogeneous group of
event date field) people, so the economic, social or educational background does not
• Embedded widget list to update and present upcoming matter much. To achieve this, α clutter-free simple interface along
tournaments. with easily understandable texts written in understandable English are
• Downloadable pdf document that presents the tournament provided.
format and locations, states participation requirements and • Regarding the required skill level, fairly minimum computer literacy is
advertises featured prizes. needed so most individuals familiar with using the internet for daily
• Embedded and interactive Google Map where all current tasks should have no problem.
tournament locations are pinned
4. Performance
• Embedded YouTube player for the users to view advertising
• Unproblematic overall performance
video from our webpage’s YouTube channel.
• Fast load times and responses on web browsers.
4. Error Handling • Smooth scrolling through provided content
• A “Help” button which provides the user with a hyperlink to • Not excessively mobile data consuming, with on-the-go users in mind.
“contact us” online form where he can describe his problem
and expect an answer as well as a “FAQ” hyperlink which 5. Documentation
leads him to a section that covers most common issues. • Informative pdf document available for download.
• Greying out invalid options (e.g., a date when all available 6. Security considerations
slots are booked so it’s not selectable) • Secure registration and booking webpage to protect sensitive user
• Pop-up notification in case a user error is detected. data.
• Hint messages when a user inputs invalid data (e.g., “invalid
email format” message when no “@” character is used at 7. Quality Assurance
email field) so as to help user come back with the correct • Low downtime during days before the tournaments when users want
data. to book their slots
• Use of asterisks to indicate mandatory form fields.

You might also like