ec-g2
- accounting
- OpenACS
- Accounts Desk
- Accounts Finance
- Accounts Ledger (General Ledger)
- Accounts Payables
- Accounts Payroll
- Accounts Receivables
- Application Neutral Audit (ANA) Logs
- Bulk Upload
- Customer Service
- ECKS Forms
- ECKS templates
- Ecommerce-2
- Ecommerce-g2
- Ecommerce-g2 development guidelines
- Ecommerce-g2 package list
- Ecommerce-g2 requirements
- Fabrication
- Field Service
- Glossary
- Human Resources
- Inventory Control
- Manufacturing Design
- Online Catalog
- Production
- Reference Data - GIFI
- Reference Data - UNSPSC
- Shipping Tracking
- Spreadsheet
- Supply Chain
- Systems simulator package
- Task: add locales (done)
- ec-g2 contributors
- other non-OpenACS software
No registered users in community XoWiki
in last 20 minutes
in last 20 minutes
Ecommerce-g2 requirements
The requirements are split up into general web application and business logic, so that we can match the web-app features to a web application (OpenACS).
Web application features:
- internationalized
- include a way to import common references, such as from project-manager, logger, categories, etc when adding rows.
- customizable (using tcl api),must be flexible with implementation
- use groupware functionality of OpenACS subsites (DAVEB says dotLRN doesn't have any benefits here)
- See OpenACS end-user and developer features
business logic
- use UBL ( http://docs.oasis-open.org/ubl/ ) and related standards, or at least build with the goal of meeting open standards.. Also see WSRP's CSS standards discussion in context of OpenACSzen
- where no open standards exist, standardize on common patterns, or uncommon patterns that are easily normalized but also provide additional long-term value (These are web 2.0 principles, see Jakob Nielsen's web 2.0 caveats)
- scalable
- practical permissions defaults, flexibly customizable
- able to import from other systems without significant hassles (xml,CSV,tab delimited tables etc)
- able to integrate with other aps, such as xml/soap services
- output to screen or paper(pdf)
- plug-able to other systems for maintenance etc, such as POS, data publishing/sharing etc.
- reports generation with different views for different levels of access
- adhere to GAAP (see http://en.wikipedia.org/wiki/GAAP) and International Financial Reporting Standards (IFRS) and extendable to other sociological/environmental accounting techniques
- templated for "quick" start, modifiable
- allow for cases where users may not have an email address, such as when making an order in a shopping basket. ecommerce package shows users a message history from the ecommerce/www/account page. Consider moving these to a system-wide messaging center where email is optional (such as private-message package. (This request moved from Bug number 2315 on openacs.org)
- accounting packages need to be able to export/import tables for 1 package instance, in the event that an entity needs to move to another openacs website or subsite
- refactor any part of the ratings function in ecommerce that is not in the Ratings package
- Provide users with a way to converts page output to PDFs, PS etc. ( extend acs-templating or create a separate package? )
- Develop some ecommerce b2b functionality that uses the oacs-open.org business transaction and saml open standards (using OpenACS' soap and xml-rpc features).
- follow guidelines established by dotWork project (without dotLRN)
- see also http://www.basecamphq.com/ and http://www.sitening.com/
- package that sets up common roles and departments, alternate packages that setup for vertical uses
- simple ledger functionality (account, itemref, original date, to/from, for/exp-code, credit/debit, project/clientref, their ref, statement date, papers filed, tax ref and a few customizable columns(other1, other2) included so experts do not need to get involved for everything
- See http://openacs.org/projects/dotwrk/project_management/requirements
- and use cases: http://openacs.org/projects/dotwrk/project_management/use_case
Technical development guidelines
See Development guidelines. Processes should be consistent with Extreme Programming