Open Accounting System, Use Case Description

Description

An accounting system application.


Any accounting system consists of a series of business transactions, a journal (which records the transactions), ledger (chart of accounts) (which group transactions by account) and a collection of standard accounting reports (which retrieve transactions, group them by account, or summarize the activities by account or account type showing the relationships of the totality of the activities over an accounting period) eg. "trial balances”. Also other free-form, ad hoc or optional (special) reports may be included.


All system activities fall into a general set of function:


Ultimate implementation, MySQL database and an interface and utility application programmed in Java.


Trigger

  1. Posting to account (account transaction)
  2. View transactions History Request
  3. Retrieve transaction Request
  4. Reports Request


Actors

  1. Bookkeeper
  2. Accountant
  3. Office Manager
  4. System Manager


Preconditions

  1. User valid
  2. database access
  3. report formats


Goals (Successful Conclusions)

  1. secure system, assured integrity
  2. robust / failsafe (wrt. Interruption or system failure)
  3. balanced accounts
  4. whole system (complete and consistent data)
  5. easy transaction handling
  6. clear audit trail
  7. easy and accurate reports generation
  8. automated routine processing


Failed Conclusions

  1. unauthorized activity
  2. transaction interruption
  3. Database read/write failure
  4. Unbalanced accounts
  5. Unclosed book (failed end of period handling)
  6. Missing data
  7. bad debts and write-offs


Extensions (Alternatives) “extend work”


Steps of Execution (Requirements)

  1. User logon and verification
    • success
    • failure
  2. Choose activity
    • Journal entry (transaction creation an d completion)
    • Create account(s) and system setup
    • Ledger summary review or output
    • Balance sheet review (“trial balance”) or output
    • Integrity checks and audit trail review
    • Start of term activities(start fiscal year)
    • End of term activities (end-fiscal year)
  3. Input required data for activity
  4. Execute routine(s) specific to activity
  5. Receive result / transaction completion



See Use Case Diagram