C3
Use the demo time to assess the system and the
(possibly revised) user manual. Everyone from the
customer group must attend and take part. You
should assess the demo to determine how closely
it
relates to what has been negotiated and agreed in
previous documents. Check that your acceptance
tests are performed during the demo. Please note
that this document will be, by definition, relatively
short. It is only concerned with the demo.
Comment on their manual and demo.
1. VIKRAAAAAAM! How closely does it relate to the
negotiated design documents?
2. DAVIDZORD! Does acceptance testing meet our
requirements in functionality?
For our web based flier system to maintain a competitive edge and
sustainable business model several key requirements must be met. These
requirements include a dynamic and robust product search, extensive
corporate statistics resources and an intuitive accessible design. From
Webonomics product demonstration, the key functionality requirements were
met and further expanded on the initial product vision. More specifically,
Webonomics demo encompassed demonstration of an intuitive analytic tool
for corporations, a dynamic search engine with product filtering, and
intuitive
upload system for products and a pleasing easy on the eyes aesthetic.
Furthermore, Webonomics also demonstrated a well designed product
tracking
system and product cart systems. These systems have met our original
vision for an intuitive product management system. Webonomics demo
clearly met all key functionality requirements.
3. NOPOWERMAN! TEBEGO Does the demo meet
usability requirements?
The demo covered all of the use cases which were layed out in the previous
documents. The interaction of the corporate users and other users in general
with frugal flier was demonstrated well and the usability requirements which
we expected were carried out in detail. The demo also showed us that the
product was easy to use since most usabilities like adding items to the
tracked products or shopping list seemed to be easy to complete by any user
regardless of age. Also it showed us that it is easy navigate in the frugal flier
which will benefit BigSplash marketing to acquire enough revenues to
request more features from Webonomics. In conclusion, the demo was a
sucess.
4. PROTOSOMETHING MOFFAT! Comments,
suggestions, concerns relating to graphical
presentation?
The graphical interface of the E-flier system is simple, elegant and user
friendly. It is possible, and without much effort, to perform most of the core
system functions with just a few clicks. The system also, for the logged-in
user, requires less interaction from the user as users continue to use the
system to buy similar products repeatedly. The E-flier system graphical
interface is one that is recommended for systems by most expert
practitioners. The system performs its functions with very little interaction
from its user.
The view of analytical information for the user is also simple and presents
the data in a way that makes it easy for the user to process it. This part of
the graphical interface demonstrates the amount of thought and creativity
put into producing the system user interface.
Using the IP address of the user to determine their location and presenting
the user with a choice to use a different address for their search radius
would help to increase the usability of the system.
5. CALEBENAUT! Does the final system solve the
original problem and needs?
What is specified in their Functional Specification and Management Plan
document:
- Will allow customers to compare prices between competing grocery
stores in the area
- Will keep track of customer's settings
- Will provide trends to the retailers
- Will have 3 types of access:
- Customer account
- Retailer account
- One-time customer
- There are 5 major components to the system:
1. Login (Logged in users can save products to a 'tracked products'
list)
2. Searching (Search for product using keywords; filter based on
location)
3. Shopping List (Calculates a list of lowest priced goods selected)
4. Tracked Products ()
5. Retailer Accounts (Data collected and displayed for retailers to
analyze)
- Retailers would have the ability to upload XML files as fliers
What is given in technical design document and demo:
- A useful and comprehensive interface for comparing prices is provided
to the users (as per the requirements
specified in the Functional Specifications and Management Plan
document)
- The capability of a customer to log in and save a tracked items list and
save other settings (like location) has been implemented.
- Data is compiled and displayed in an easy-to-use interface for the
retailers to view and analyze it; this satisfies the specified requirements
- The technical design document and the demo provided examples of all
three access types in progress (retailer side, customer account side,
and one-time customer side)
- There is a login option on their system for both customers and retailers
(satisfying the login requirement specified in the functional specifications
document)
- There is a comprehensive search capability that is easy to use and
powerful (satisfies the requirements specified)
- A shopping list is implemented that satisfies the requirements specified
in both our discussions with the group and the functional specifications
- A tracked product list is implemented that satisfies our requirements
specified in both discussions and in documentation
- A full-functional retailer account is available and was demonstrated. This
demo satisfies our requirement for the retailer to
have some feedback and analytics displayed. Satisfies the
requirements specified in the functional specifications document and in
discussions.
In conclusion, all of the five main functional specifications described were
fully satisfied in the demonstration given. Therefore, with the original
problem in mind, I believe that this system fully solves the original problem
described and also fully satisfies our (the customer's) needs.