Bid Ethiopia

While functionality is sometimes considered outside the domain of the usability specialist, it’s clear that if users simply can’t do something they need to do, then the system isn’t usable.

As such, much of the work done in user studies during user needs analysis is focused on uncovering the capabilities and functionality that the users will need.

A traditional requirements document in software engineering focuses on functional specifications, or specs. These list each subsystem of the software and all functional requirements within each subsystem.

This document is revised throughout the requirements analysis phase, and additional functional requirements may be added during development as the functionality is understood more intimately or as usability studies reveal that a feature needs to be added or removed.

Later changes are reviewed carefully to understand then impact on schedule and budget. Functional requirements are explicitly prioritized and desired features are scheduled for later releases of the web site.

The functional specs are referenced throughout design and production of the site to verify that the system being produced corresponds to the necessary functionality. In addition, the quality assurance team uses the functional specs as the basis for the majority of its testing.

A large site will have hundreds, thousands, or even more functional requirements specified. Some example functional requirements for the site visitor include the following:

• Site contains a help system that can be brought up from any screen.
• Site contains links to contact information on every screen.
• Error pages include a customer service phone number.
• Searches that return zero matches include suggested products to view.
• Product listings include product name, description, size, and weight.
• Site sends email to buyers when orders are back-ordered, and when back-ordered products are received.
• Site emails a welcome message to users when they register.

Many sites need an administrative interface for those who must update the site content or process orders. Don’t forget to plan the features for these users also. Some example functional requirements for the administrative (or backend) portion of the web site include the following:

• Ability to add, modify, and delete product listings on the site.
• Ability to add, modify, or delete banner ads posted throughout the site.
• Notification system that emails copies of all orders to the shipping department and to the site administrator.
• Nightly transaction reports listing all orders through the site.
• Reports upon request for
• Money made per period – by ads and by order
• User demographics by product category
• Products sold by user category
• Banner ad hit counts by company purchasing banner ads
• Ability to tell f the system is down and send an alert to the system administrator and to the manager responsible for the site.

Report This Post