Initial Client Setup
From ADempiere
This Wiki is read-only for reference purposes to avoid broken links.
Contents
- 1 Status
- 2 Contributors
- 3 Overview
- 4 Purpose
- 5 References
- 6 Design Considerations
- 7 Glossary
- 8 Functional Requirements
- 9 Functional team
- 10 Acceptance criteria
- 11 QA and test cases
- 12 Development infrastructure
- 13 Technical Requirements
- 14 Technical team
- 15 Data Requirements
- 16 Non-Functional Requirements
- 17 Open Discussion Items
- 18 Closed Discussion Items
Status
Suman: this page should be pointing here http://www.adempiere.com/Initial_Client_setup_improvements but I dot know how to change. Can you assist please.
Contributors
Adaxa Pty Ltd (Paul Bowden)
Overview
Purpose
References
Design Considerations
Assumptions
Dependencies
Constraints
Glossary
Functional Requirements
Functional team
- Volunteers for reviewing:
- Mario Calderon 14:00, 22 June 2013 (UTC) - Functional Review
Result of review by Mario Calderon, June 22nd, 2013
- Process Initial Client Setup done as SystemAdministrator (Application Dictionary)
- Only difficulty: the Chart of Accounts file must contain at least the default accounts
- This has to be created/edited correctly by a person who knows the matter; otherwise, the process fails here.
- When Process fails (mostly because of error in COA): it would be desirable to keep the entries already done, instead of having to type in everything
- Automatic generation of data
- Creation of Client with logo
- Creation of 2 roles: Admin and User
- Creation of 1 Product, including accounting: standard
- Creation of 1 Product category, including accounting: standard
- Creation of 1 BPartner (as specified in process), including accounting
- Creation of 1 Tax Category: standard
- Creation of 1 Tax, including accounting: standard
- Creation of 1 Calendar from 2014-2018, for company
- Creation of Chart of Accounts
- Creation of 1 Product, including accounting: standard
- Creation of 1 Cost element: Standard Costing
- Access to all system defined objects (UOM, Cost element types, document types, etc.)
- Summary: the Client is created and it is possible to immediately work with it.
- Conclusion: accepted
User roles & profiles
Business process definition
User stories
Functional requirements based on business processes
User Interface Mockups
Acceptance criteria
QA and test cases
Development infrastructure
Technical Requirements
Technical team
- Volunteers for reviewing:
- Mario Calderon 23:30, 18th August 2013 (UTC) - Technical Review
Result of review by Mario Calderon, 18th August 2013
- class, method and variable nomenclature:OK
- license: OK
- code well-commented
- code well-structured: it is easy to read
- methods with javadoc
- good example for reusing Adempiere objects
Data Requirements
Non-Functional Requirements
Open Discussion Items
the tax setup will only suit AU and NZ ... may need tax to be deleted for general usage.
