Table of Contents
Step of developing a prototype.
When designing a prototype the following steps are followed: The first step is to identify basic requirements or problems: this level the objective is to determine basic requirements including the input and output information desired. At this level details, such as security information can typically be ignored.
The second step is to develop an initial Prototype: at this level the initial prototype is developed that includes only user interfaces. The third step in prototype design is to review the initial prototype: At this level a mechanism is developed to allow the customers, including end-users, examine the prototype and provide feedback on additions or changes. The last step in design a prototype is to revise and enhance the prototype: At this level developers use a feedback to consider all the specifications and improve the prototype. Negotiation about what is within the scope of the product being developed is done. If new changes are suggested then a repeat of steps 3 and 4 may repeated.
Consideration for the system Student
Who will use the output? Registered students and members of staff in the department. What is the purpose of the output? The purpose is to process informatimation related to students learning i.e. course registration, fees payment, assignment and lecture notes download, accommodation, class timetable, and calendars
Where does the output need to be delivered? The output will de delivered in student respective accounts upon logging into the system. How many people need to view the output? Only one student logged in, will be able to view the information from one particular access point. This will be done to enhance security.
The worst that can happen
The worst thing that can happen is system failure or access denial i.e. Users can not access information. To correct this systems approach to prototype design must ensure that a variety of aspects, from technologies to be used to target user psychology and physiology, are taken into consideration. In relation to the users aspects an interface designer should not forget about disparate groups of users whose preferences might vary greatly. Often spend a lot of time to perform a simple operation. When you students struggle with a poor quality interface, they waste a lot of time and make numerous mistakes. In this case, interface is not only inefficient, but also a major principle of usability is forgotten that an interface should be subjectively pleasant.
Things to consider when redesigning
Average operation time. Using a poor quality interface, students and members of staff can spend up to twice more time to perform an operation compared to a well-designed interface. When investing in a friendly and efficient interface you reduce time needed to work with software.
Number of errors. How many mistakes occur when administering a site per month, such as incorrect prices, items missing form price lists, links that do not work etc.? How many users report such mistakes? All this is caused by poor design of software interface and can seriously endanger the health of your business.