Difference between revisions of "New Dunning Functionality"
From ADempiere
This Wiki is read-only for reference purposes to avoid broken links.
(→Functional Requirements) |
m (→Functional team) |
||
Line 25: | Line 25: | ||
==Functional Requirements== | ==Functional Requirements== | ||
== Functional team == | == Functional team == | ||
− | *Volunteers for analyzing: | + | *Volunteers for analyzing: [[User:Kthiemann|Kthiemann]] |
*Result of analysis: | *Result of analysis: | ||
===User roles & profiles=== | ===User roles & profiles=== |
Revision as of 02:44, 13 June 2013
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
In Production use
Contributors
Overview
Possibility to define Pluggable Dunning Sources and create Dunning Candidates. Works with existing Dunning Grace Functionality. Dunning candidates can be processed to Dunning Documents. New Windows:
- Dunning candidates
- Dunning Documents
New Process:
- Create Dunning candidates
- Create Dunning documents
- Mass Writeoff/ Dismissal
Purpose
References
Design Considerations
Assumptions
Dependencies
Constraints
Glossary
Functional Requirements
Functional team
- Volunteers for analyzing: Kthiemann
- Result of analysis:
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 analyzing:
- Result of analysis: