Design and prototype, Database Management System

This assignment is worth 45% of your final grade for this module.  Marks will be awarded as follows:

  • Prototypes (wireframe and web based prototype)
    • You are expected to design the main screens of the system and represent these using wireframes. Your choice of screens should show a representative subset (2 or 3 wireframes) of the system. You are advised to select screens that relate to the purchase of a product from your web site. The wireframes provide the basis for the web pages that will show the interface in more detail. (5%)
    • Based on the work you have done in creating the wireframes, you need to create the web pages that illustrate the core functionality of the system. You are advised to select a scenario that sets out the process of a purchase being made as the basis for your work (ideally this would be based on a scenario you developed for the first coursework).

This is a relatively low fidelity prototype in terms of the levels of interaction (i.e. there is no back-end to the system, we are looking at the front-end) and you may include data that is 'hard-coded' rather than generated by the system. An example of this may be a list of products that is hard-coded in the page and not generated by a call to the back-end. (10%)

  • Evaluation and critical account of usability of system based on the criteria set out in CW1
  • You will need to conduct a heuristic evaluation of your web pages to test that your web page interface design conforms to the criteria that you have set down for your system.

You would be expected to submit both the raw data of your heuristic evaluation and a report summarising the main findings in an appropriate format.

Your report should include a section in which you critique the usability of the system and reflect upon the efficacy of your criteria for identifying usability issues.

  • You are expected to outline your design for a formative usability test as part of the overall usability study. You may choose to identify one iteration of the formative testing and describe how this would be conducted.
  • You are also required to detail a summative usability study that tests the extent to which your system supports users in getting through the purchasing process. Your success criteria are that users are able to make a purchase of a given product within a specified period of time and at a minimum level of errors.
Posted Date: 2/21/2013 6:13:50 AM | Location : United States







Related Discussions:- Design and prototype, Assignment Help, Ask Question on Design and prototype, Get Answer, Expert's Help, Design and prototype Discussions

Write discussion on Design and prototype
Your posts are moderated
Related Questions
Explain the dependency relationship of object oriented A dependency is a relationship which states that a change in specification of one thing can affect another thing, but n

4. Describe three ways to handle missing field values

Prove that a relation which is 4NF must be BCNF.   Ans Let R be in 4NF.  Suppose it is not in BCNF.  Hence, there exists an FD X→Y in R such that x is not a super key. Although

how many types of data model in DBMS? explain data abstraction with its different level

Explain the terms primary key, candidate key, alternate key and secondary key. In the given table identify every key? STUDENT(SID,Regno, Name, City) Primary Key: The prim

You want to implement following relationships when designing tables. How would you do it? a.) One-to-one b.) One-to-many c.) Many-to-many a.) One-to-One relationship -

Define the Traditional System Analysis and Design Traditional System Analysis and Design (SAD) have three basic life cycle models. A typical software lifecycle consists of the

What is a shadow copy scheme? It is simple, but efficient, scheme known as the shadow copy schemes. It is based on making copies of the database called shadow copies that singl

Having clause This clause is used for producing conditions on grouped information. Example: Find maximum salary and department number of those departments where maxim

Association as a cache This association must be updated when any new element is added to it, but testing for overlap using association is more efficient.    Figure: