Week 1 Thread
Imagine you are managing a design project that will create an interface for automobile mechanics. The interface would be used by the mechanics to look up various fixes and parts for any number of makes or models of automobiles that may come through their garage. Decide what usability measures would be most motivating when designing this interface and describe the unique challenges you would have to plan for when designing an interface for an automotive repair shop. Use supporting evidence to support your response.
First step for any design project would be to gather the requirements. As developer and project managers would not know what the end user needs and what their technical skills are, it would be essential to collect information on what the client needs. I would think that the interface has to be as simple as possible. So that the end user would have no problems searching through the interface for different parts and makes of cars. I can imagine a mechanic just looking at the screen trying to figure out where is he at or what is he looking at. So the title of the search performed and the result should be bold and large font on top to ensure they know what the information is. Also to simplify the problem of how to fix a certain problem or a part in an automobile, the interface can be linked to Auto Repair Reference Centre. The new Auto Repair Reference Center interface provides for an increased amount of content with access to repair information for more than 37,000 vehicles. In-depth repair coverage—representing the most comprehensive collection of automobile repair reference information in the market—is provided for each vehicle. In addition to repair manual information, library patrons will find technical service bulletins, recall information, electrical wiring diagrams, maintenance intervals, specifications and labor times. Advanced do-it-yourselfers can take advantage of the diagnostics information collection, which provides the ability to troubleshoot
First step for any design project would be to gather the requirements. As developer and project managers would not know what the end user needs and what their technical skills are, it would be essential to collect information on what the client needs. I would think that the interface has to be as simple as possible. So that the end user would have no problems searching through the interface for different parts and makes of cars. I can imagine a mechanic just looking at the screen trying to figure out where is he at or what is he looking at. So the title of the search performed and the result should be bold and large font on top to ensure they know what the information is. Also to simplify the problem of how to fix a certain problem or a part in an automobile, the interface can be linked to Auto Repair Reference Centre. The new Auto Repair Reference Center interface provides for an increased amount of content with access to repair information for more than 37,000 vehicles. In-depth repair coverage—representing the most comprehensive collection of automobile repair reference information in the market—is provided for each vehicle. In addition to repair manual information, library patrons will find technical service bulletins, recall information, electrical wiring diagrams, maintenance intervals, specifications and labor times. Advanced do-it-yourselfers can take advantage of the diagnostics information collection, which provides the ability to troubleshoot