IT302-Unit4-
Kaplan University

Part 1: Dashboard Design. For the dashboard that I anticipated is required to meet the needs of the task that I discussed in Unit 3, I believe that the best approaches are either a Semantic Network or the use of Scenarios, Flowcharts and Cognitive walkthroughs, and more specifically Scenarios. Although this may be the most productive approach, it is likely that in the process of creating the dashboard that parts of a number of the conceptual designs could contribute to the finished product. While the Semantic Network is comprised of elements that would be useful and productive, particularly by providing ease in exploring the problem space and graphical views, it does not offer us all the information that would be constructive. To accomplish that, I believe the use of Scenarios, Flowcharts and Cognitive walkthroughs would provide us with the most useful means to develop a dashboard adequate to provide the functionality we are seeking. Of these, the use of Scenarios would provide the easiest means to develop a dashboard with the desired functionality initially along with the ability to modify easily as required to accomplish what is needed. By creating scenarios and including them in the early development of the dashboard we will provide ourselves with a means to develop a versatile form that can be easily amended as needed to provide a finished console that provides the full functionality that is required. This approach would also be likely to provide the users with the ability to modify the dashboard if needed to keep pace with any updating or restructuring that is considered necessary to keep up with changes in required to meet varying needs. Since the primary function of the dashboard is ultimately going to be a means to help update and track the needs of the clients and to provide them with enhanced service. By providing a broad variety of approaches and techniques to help develop the dashboard the conceptual design tool provided a clear-cut means of the various ways to approach the development of a dashboard that would meet the our needs and help to clarify the approaches that are available. Without it would have been far more demanding to determine the needs and solutions to creating the dashboard. Part 2: Wireframe Design.

[pic] Part 3: Nielsen’s Heuristics • Visibility of system status. The dashboard provides clear visibility of system status by selection of current or previous actions or issues. • Match between system and the real world. The dashboard is designed to be compatible with actual issues and provide the technician the information required to perform the proper actions. • Consistency and standards. The dashboard controls are designed to be easily understood and standard in their usage. • Recognition rather than recall. The controls are clearly marked and separated to prevent incorrect selection. • Help and documentation. Provisions will be added to provide a help page. • While not all of Nielsen’s choices are presently shown, as the dashboard is developed any additional items required will have provisions made for them.

Reference Nielsen, J. (1995). 10 usability heuristics for user interface design. Freemont: Nielsen Norman Group. Retrieved from http://www.nngroup.com/ (October 2009 ). A guide to creating dashboards people love to use . (pp. 2-24). Juice Analytics. DOI: info@juiceanalytics.com (2013, 02). Guide to Design Usable Dashboard. StudyMode.com. Retrieved 02, 2013, from http://www.studymode.com/essays/Guide-To-Design-Usable-Dashboard-1401751.html

-----------------------
Client

Contact

Phone

Date

Initial Contact - Description of problem.

Previous Issues or Continuation of Previous Issues - Description of problem.

`