|
|
20.
|
|
|
If your improvement is validated by the usability team, we will assign a developer and a member of the usability team will improve the guidelines.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/usability_book/1. Introduction/index.rst:52
|
|
|
21.
|
|
|
Introduction to modules
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/usability_book/2. Business Applications/Introduction to modules.rst:3
|
|
|
22.
|
|
|
Menus Organization Rules
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/usability_book/2. Business Applications/Menus Organization Rules.rst:4
|
|
|
23.
|
|
|
All menus have to be suited to one business application. One user has to see all menus linked to his job. He has to be able to make his workflow in one menu only. This is the goal of all the applications. The user should be able to navigate through all his workflow from a single menu to make his work easier, faster and user friendly.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/usability_book/2. Business Applications/Menus Organization Rules.rst:6
|
|
|
24.
|
|
|
Menus are defined in a certain way to make the work of users easier . So, users can see all the menus he has need of and they have to be in a logical order, to facilitate navigation and use. A salesman doesn't need to see the invoices before he has even made the quotation.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/usability_book/2. Business Applications/Menus Organization Rules.rst:8
|
|
|
25.
|
|
|
Main menus are also organized to facilitate the work of a manager. Indeed, in an SME, a manager can have access to a lot of applications, for example, Sales, Projects, Human Resources, Marketing and Accounting. When he opens his instance of OpenERP, he has to see main menus in a logical order, he doesn't want to see the accounting data before the sales information.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/usability_book/2. Business Applications/Menus Organization Rules.rst:10
|
|
|
26.
|
|
|
Business Applications
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/usability_book/2. Business Applications/index.rst:5
../../source/usability_book/7.Guidelines/1business applications.rst:4
|
|
|
27.
|
|
|
Introduction to Business Applications
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/usability_book/2. Business Applications/introduction to business applications.rst:4
|
|
|
28.
|
|
|
The complexity of an ERP is usually due to the high number of available features. Most of the users of the system use only a few features, according to their job position(s) in the company. In order to remain easy to use, the different features are split into business applications.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/usability_book/2. Business Applications/introduction to business applications.rst:7
|
|
|
29.
|
|
|
The main idea is that a user is often working in a particular context (working on a project, recording accounting entries). When he is in such a context, he should directly see all features related to this context (=business application). We try to create business applications according to user's position in the company: salesman, project user, purchasers, accountant, etc.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/usability_book/2. Business Applications/introduction to business applications.rst:9
|
