Professional Documents
Culture Documents
Design Specification
Firm
Billing
Application:
Project:
Status:
Date:
Version:
Author:
Demo
Website
Firm
Billing
Draft
06/12/2013
1.0
DOCUMENT
HISTORY
Revision
Date
Revised
By
Changes/Notes
Corresponding
Document
FUNCTIONAL
DESIGN
FOR
INTERNAL
USE
ONLY
Page
1
of
14
Overview ....................................................................................................................................... 3 1.1 Component Overview ...................................................................................................... 3 1.2 Application Build Requirements ....................................................................................... 3 1.3 Design Assumptions ........................................................................................................ 3 2 Firm Billing Data Model ........................................................................................................... 4 2.1 Data Model....................................................................................................................... 4 3 Firm Billing Features ............................................................................................................... 5 3.1 Firm Billing Summary ....................................................................................................... 5 3.2 Invoice Summary ............................................................................................................. 7 3.3 Invoice Detail ................................................................................................................... 9 3.4 Edit Billing Information ................................................................................................... 12
FUNCTIONAL DESIGN
Page 2 of 14
1.2
The Demo Website uses the following supporting technology. The Firm Billing Feature should be built using the same technology. (WAR file or individual HTML pages can be provided from the existing website for developer to stub pages against) Application should be written in Java Build Manager, Apache Maven-3.05 Webserver, Apache Tomcat-07.0.37 Web framework, Apache Wicket Database, MySQL Charting Tool, HiChart
1.3
Design Assumptions
Firm Billing Invoices should be cached and do not have to be generated on-demand
Feature Elements include Billing Summary Page Invoice Summary Invoice Detail Billing Information Page (edit)
FUNCTIONAL DESIGN
Page 3 of 14
For the Firm Billing Feature of the website, the following list the proposed data elements that may be required. This includes both objects that are available in the current system database and proposed objects that will need to be added. Existing Data FromAccountTable Account Status (Active, Suspended) FirmCost Cost (price per user) New Data Required Invoice InvoiceName (reflects billing for the month of) InvoiceNumber (generated by system) InvoiceDate (reflects the date that the invoice is generated, should be 3 days after month end) InvoiceStatus (outstanding, paid) AmountPaid AmountOustanding (Calculated Field = AmountDue AmountPaid) PaidDate (displays date, only if InvoiceStatus is paid Billing Info Address 1 Address 2 City State Zip Purchase Order Department Contact Name Contact # 1(Phone Number) Contact #2 (Phone Number) Fax (Fax Phone Number) Email Payment Info PayType (ACH or Invoice To Billing Address) PaymentInformation (if PayType = ACH) o BankName o RoutingNumber o AccountNumber
FUNCTIONAL DESIGN
Page 4 of 14
3.1.2
Trigger Description
Extensions or Variations Special Requirements 7. 8. Firm Billing Summary process should be performed at the end of each month Values should be stored so that they can be referenced on an ongoing basis
FUNCTIONAL DESIGN
Page 5 of 14
3.1.4
User Input Reqd? Display Rules (data type, control type, sort order, field length) Field Rule
Error Result
FUNCTIONAL DESIGN
Page 6 of 14
Invoice Summary
Displays a summary page for all current invoices generated for a firm.
3.2.2
Invoice Summary
Use Case Use Case Reference Use Case Goal Actor Pre-Condition Post-Condition Invoice Summary 3.2 Allows Actor to view a list of available invoices for his firm Website user NA Success Actor is able to view a list of available invoices Failure System is unable to generate a list, and actor is unable to view Actor selects Invoice in the navigation 1. 2. 3. 4. 5. Extensions or Variations Special Requirements Actor selects Invoice link within the navigation System retrieves list of available invoices System retrieves payment status of available invoices System displays page End Use Case
Trigger Description
FUNCTIONAL DESIGN
Page 7 of 14
3.2.4
User Input Reqd? Display Rules (data type, control type, sort order, field length) Field Rule
FUNCTIONAL DESIGN
Page 8 of 14
Invoice Detail
Displays the specific invoice that is generated as a billing record for the firm.
3.3.2
Invoice Detail
Use Case Use Case Reference Use Case Goal Actor Pre-Condition Post-Condition Account Invoice Detail 3.3 Allows Actor to view the specific invoice generated for their firm Website User NA Success Actor is able to select Invoice Name and view detailed invoice information Failure Actor is unable to view invoice detail Actor selects Invoice Name (e.g. May 2013) 1. 2. 3. 4. 5. Actor selects Invoice Name System retrieves billing information System calculates Amount Due System generate invoice End Use Case
Trigger Description
Extensions or Variations Special Requirements 6. Invoices should be generated and stored following the end of the month. This reflects the [invoice date], meaning the date that this process was run and the invoice was generated.
FUNCTIONAL DESIGN
Page 9 of 14
3.3.4
FUNCTIONAL DESIGN
Page 10 of 14
Error Result
FUNCTIONAL DESIGN
Page 11 of 14
3.4.2
Trigger Description
FUNCTIONAL DESIGN
Page 12 of 14
3.4.4
FUNCTIONAL DESIGN
Page 13 of 14
Please NOTE that is user selects Payment Method =ACH, this only stores the value. It is not connected to a payments service.
User Input Reqd? Display Rules (data type, control type, sort order, field length) Field Rule Yes Bank Routing Number and Account Number should be obfuscated except for the last 4digits of the numbers Error Result
FUNCTIONAL DESIGN
Page 14 of 14