assignment

Objective To allow you to take the role of an HCI designer in producing a prototype interface to a database using Visual Basic. Submission You should submit all the required work on a floppy disc (that has been checked for viruses, please!). The Visual basic project should NOT be compiled - submit it in an editable form (ie separate project and form files). The full submission should include the following (all on disc): VB project and form files. Documentation in MSWord format Standard coursework cover sheet Problem Statement Use Visual basic to produce an easy-to-use interface to a database that will allow students to display: (a) Their marks in three modules taken in one semester, including their overall average across the three modules, after entering either their Reg No or their surname. (b) For a given module code, the class average for that module, and the full module name. (c) For a given course code, the averages in each module for that course, and the full course name. The 'average' student, with a reasonable level of computer experience, should be able to operate the interface without any special training. Where possible, error prevention design features should be used. When errors do occur the system should allow the user to recover from the error without having to restart the application. Display The interface may comprise a single 'form' or, if you think it is appropriate, multiple forms may be used. When an individual is searching for their own set of marks, the screen should display: Reg No, Name, Initials, Mark1, Mark2, Mark3, Average When requesting a module average, the screen should display: ModuleCode, ModuleName, Average When requesting a course average, the screen should display : CourseCode, Coursename, Average1, Average2, Average3 Documentation The documentation (in a single MSWord file) on disc should include the following: A Task Analysis for the prototype, including a Task Hierarchy Diagram. Analytical Evaluation (by you) of the interface - explain how you think it conforms to the main HCI guidelines for interface design. Detail any features which you tried to implement, but didn't/couldn't. Briefly, explain how you think the interface might be developed further to improve its 'Usability'. Database You will probably need to set up a MSAccess database with four tables in order to st ## Deliverables Database You will probably need to set up a MSAccess database with four tables in order to store the necessary information effectively. I suggest the following structures for the tables, though it is up to you to choose your own field names, and you may want to include additional fields if you think you need them. A sample of about 15 records in the STUDENT table should be enough for testing purposes. Three course codes/titles should be enough in the COURSE table. Table1 : STUDENT RegNo, Surname, Initials, CourseCode Table2 : MARKS RegNo, Mark1, Mark2, Mark3 Table3 : MODULE ModCode, ModTitle Table4 : COURSE CourseCode, CourseTitle I suggest you use the following three modules: COM350M2 Human Computer Interaction COM340M2 Knowledge Based Systems COM326M2 Object Oriented programming Examples of course codes are E185UM BSc Interactive Multimedia Design E410UM BSc Computer Science E155UM BSc Maths, Statistics, Computing Criteria 1. Task analysis [10] Shows main tasks/subtasks - looks realistic Database looks 'reasonable' for the problem. 3. Prototype [60] Works properly - related to the tasks. Conforms to HCI guidelines, especially:- Consistency User expectations Text Legibility Visual clarity/structure of interface eg obvious what should be done. shows only what is needed for task in hand Appropriate Use of colour Provision ## Platform none required ## Deadline information none