DjAccount v0.2 Requirements

From ArgeoWiki

Contents 1 Main Features 2 Local Currency Handling 2.1 Requirements 2.2 Interface 3 Stock Management 3.1 Real life usecases 4 XML import/export 4.1 Use cases 4.2 Systems identification 5 Client preferences

Main Features

Version 0.2 is local and single user. It uses an internal database (HSQLDB).

• Basic new/edit/delete on all business objects
• Fast entry form for Movement
• Local currency, exchanges rates and exchange issues addressing
• Income statement and Balance sheet views
• English and French localization

Main features and tricky parts of this version are illustrated there : DjAccount Functional Usecases

Local Currency Handling

Requirements

• The user choose if we take or not the rate to compute default currency amount when an entry is entered.
• Once you choose that you use the exchange rate, the calculation is done with the rate of the day

In other Word :

• Either you enter both local and default currency amount
• Either you enter a date, then choose the local currency and book ONLY the local cur. amount

• Constraints on exchange rate booking:

A) It is NOT possible to book a NEW rate on a currency that already has :

  * Either a rate with a date that is same or after 
  * Either an entry that has a date same or after AND that is linked to a rate with a date before 

  (in french just to be sure that the rule is clear, sorry)
  on ne pas pas entrer de taux sur une devise qui a 
  soit déjà un taux de date postérieure ou égale 
  soit une entrée utilisant un taux de date antérieure et ayant une date postérieure ou égale
  

B) An existing rate on a currency can be modified

  only if NO entry is linked to this rate

Interface

• The list of all rates can be seen in the exchange rate list

• The user can choose beetween the three type of entries (once the account is chosen) :
  • Entry in default currency => user books date and the def cur amount
  • Entry in local currency not using the rate => user books date, cur., def. cur. & loc. cur. amount
  • Entry in local currency using the rate => user books date, cur., loc. cur. amount

Stock Management

Real life usecases

XML import/export

Use cases

• backup / restore
  • export complete model
  • reload it
    • has to come from the same model, with consistent revisions
    • overwrite changes done after the backup

• incremental history / merge
  • record each revision
  • apply a sequence of revisions
    • has to come from the same model, with consistent revisions

• import of arbitrary data
  • import arbitrary data, considered as new objects
    • no revisions or tids
    • fail if constraints not respected (like unique fields)
  • import arbitrary data, searching for matching business objects
    • no revisions or tids
    • functional ids are declared per object, and the import search for matching objects to update before creating new ones

Systems identification

• model identifier: unique identifier for a given model (1..1 with the master database)
• client identifier: unique identifier for a given client installation

Client preferences

• language / locale