Cosc 3p94 Course Project
Stage 2

(Due date for assignment is March 25th 16:00 est No Lates Accepted)

Introduction:

By now you should have the following information from your discovery of a Video Editing application and the associated tasks which are important to users. As well as any interviews that you "may" of done and personas to attain an understanding of what the users expect and need from such a system. You should have:

  1. An idea of how some of the existing systems are structured based on the HTA. 
  2. A realization of goals from the perspective of the personas.
  3. How efficient existing interfaces are in terms of navigation hence the KLM 
  4. What goal and actions are important to the user.
  5. Areas of difficulty.
  6. The information which the system must manage.
  7. A storyboard of how a new system might look.

Goals of the Assignment:

This assignment will focus on the design and implementation of a mock application, you may presume any platform, Browser, Application, or mobile app although it is not a requirement. The goal is to create a fully functional interface but devoid of any of the misgivings of previous systems and based on the research you conducted in stage 1. The idea of a mock interface it to be able to show what a functional system would or could look and act like without getting bogged down in technical issues. Thus, creating a fully functional application with database an network connectivity is not part of the scope of this course. However, past experience has shown that putting a database in the back end to manage some of the interaction is beneficial, but not necessary, and certainly no marks are awarded for such a system.

The Assignment:

Create an implementation which supports the concept of a "Video Editor" application. Insure all primary personas are taken care of.

So how functional should it be? If you can click on it or type in information then that is what should be implemented. At times you will need to simulate information reception. You can use static messages for this. In the end, what is important is that the idea gets across. One technique you might find useful, is to implement a small database in the background, PHP and MySQL. This can be used to drive some of the dialog boxes and messages, such as selection of information. Not a requirement.

Your solution should be run-able on any desktop or laptop. In the end the implementation platform is immaterial, but we need to constrain the project for practical reasons. The purpose is to show an application which is designed for use. Novel ideas can be implemented and are encouraged.

For assignment (Stage 2) completion you will have a new application. Use the knowledge from Stage 1 to drive your design. As the course progresses you will find that your implementation will be modified. B.T.W. Stage 3 will consist of testing and evaluating implementations from other groups, as well as they evaluating yours. The feedback should then drive changes and improvements of your own interface.

Consider the following scenario. You have finished Stage 2 and must now give a presentation. A contract is at stake. Your interface should demonstrate fully what your system can do from an interface perspective. Interaction between application and the user is paramount. The audience might want to sit down in front of your application and play to evaluate your design. Does your interface sell your expertise and guarantee a contract?

The Submission:

For submission you will be required to package your project into a zip file OR submit 1 page with site access information. If your application relies on some library or installation, you must include sufficient information that some person may install and run your application. Ensure that you test the installation process or provide the required permissions prior to submission.

Stage 3 is a mutual evaluation. Each group will be given two other group projects. The groups will test and evaluate these projects. It is therefore required, that each group submit 3 copies of everything at the conclusion of stage 2. 1 copy to the markers, 2 for the mutual evaluation. Each copy should be self contained and labelled, if you have a web site then a single page of access info is needed. Label 1: "For MarkerGroupXX" and Label 2:  "For EvaluationGroupXX". Include installation instruction in both. The XX is your group number.


In summary:
  1. 3 copies of the installation, 1 for the marker "For MarkerGroupXX", the other 2 will be distributed for mutual evaluation "For EvaluationGroupXX".
  2. The "For Marker" distribution should have Full Names and Student numbers of all group members.
  3. The "For Evaluation" distribution does not need to contain the names and student number.
  4. Ensure the group number is part of the distribution name.
  5. Written instructions for installation or access to your project in the case of a website, contained in each distribution.
  6. Verify it does install (if a website, then ensure access) and work from an independent account.
End!