Choice of the application was to develop an work order syste
Choice of the application was to develop an work order system for customers and manager.
Prepare a report that describes the domain, users, goals, and usability aspects as listed below. At the beginning of the report, briefly describe your application selection that was approved. Next, identify the following HCI components for your application. Clearly identify each component section and be thorough.
Domain of knowledge for the designer (what do you as the developer need to know to develop the application)
Users for the application (primary, secondary, stakeholder)
Environment where the system is expected to typically be used in
Qualitative and quantitative usability aspects and goals (Ch 1)
User Experience goals (Ch 1)
Constraints and tradeoffs to be considered for the new design (this should include issues relating to the user, platform, environment, etc.)
Solution
Please find some useful points here so that you can build upon the same
in your report.
1. Work order system for customers and manager.
Having a system for better management of work is always better.
Work order is an order received by organization from customer for the products developed by organization or the
services offered.
\"Work Order\" is used in place of \"invoice\" or \"statement\".
With a software it becomes easy for the manager to manage the customer requests/orders.
A proper work order system should help in
- Tracking the requests raised by customer.
- Generate invoices for the customer and track the payment.
- Track the delivery made to the customer.
- Have a check on the stocks available.
and many more..
Domain of knowledge for the designer:
Having a good understanding of the domain for which the software is developed is very helpful.
If the product is developed for say Manufacturing domain, the work order is converted from sales
order to show that work is about to begin on the product requested by customer.
if the product is for service industry, the work order records the location, date and the service provided
and the nature of work done..
SO the same \"Work Order\" would mean different in different domains, having a proper knowledge is required.
Users for the application:
A single application can serve many functionalities.
All of the functionalities may not be required for everyone.. For example, the customer need not have
access to the billing system which generates invoice, track the products etc..
Primary owner OR the admin (here its manager) should have the access to the entire application.
Secondary owner, may be the one who works under the manager should have limited access as decided by the manager.
Stake holders are the customers who should have very limited access as against the earlier two.
Environment where the system is expected to typically be used in:
This depends on the domain where the product is deployed.

