Purchase Books
| ID: | PB001 |
| Description: | The purchase book allows the recording of purchased goods of a company intended for resale. |
| Rationale: | The main purpose of a purchase book is to keep records of all purchased goods intended for resale. |
| Fit Criterion: | The ea-Geier provides an interface to enter and maintain purchases. [pA3] |
Purchase Data
| ID: | PB002 |
| Description: | Each record has a unique id provided by the system and a voucher id defined by the user. |
| Rationale: | The user may define a voucher id for each transaction e.g. K1, K2, etc. for cash transaction and B1, B2, etc for bank transactions which should be identical to the one used in the cash book for the referring voucher. In addition the system will give each transaction an unique id in the order of entering the transactions. |
| Fit Criterion: | Each transaction has two ids – one provided by the system, one by the user. [pA3] |
| ID: | PB003 |
| Description: | Each record has name field describing the purchase. |
| Rationale: | To name an purchase the user needs a text field. |
| Fit Criterion: | Each purchase-book form holds a not-empty text field describing the purchase. [pA3] |
| ID: | PB004 |
| Description: | Each record stores the purchase date of the goods given by the user, and the dates for the generation and last manipulation of the record. |
| Rationale: | The user has to define the date of the purchase. In addition the system will store the date of the generation and manipulation of the record. |
| Fit Criterion: | Each purchase record stores the date given by the user, the first generation and the last manipulation. [pA3] |
| ID: | PB005 |
| Description: | Each record has text field holding the data of the vendor of the purchased goods. |
| Rationale: | To enter the data of the vendor of the purchased goods the user needs a text field. |
| Fit Criterion: | Each record holds a not-empty text field describing the vendor of the purchased goods. [pA3] |
| ID: | PB006 |
| Description: | The acquisition costs of the purchased goods are stored by the system. |
| Rationale: | To enter the price of the purchased goods the user needs a text field. |
| Fit Criterion: | Each record stores the price of the purchased goods. [pA3] |
| ID: | PB007 |
| Description: | The number format is configurable on a client basis. |
| Rationale: | The number format may be different depending on the country of the user. e.g. 123,45 EUR compared to 123.45 USD. |
| Fit Criterion: | The owner of a client can define the number format in which the data will be entered and displayed. [pA3] |
Display
| ID: | PB008 |
| Description: | The system shows sortable tables of a certain amount of records. |
| Rationale: | To provide an overview of the entries the system has provide a list of the entries. To navigate inside this list it needs to be sortable and paginated. |
| Fit Criterion: | The system is able to show the data as sortable tables with pages limited to a user-specific number of entries. [pA3] |
| ID: | PB009 |
| Description: | The system shows a detailed data of single records. |
| Rationale: | To see all available data for a record a list would be too complex. |
| Fit Criterion: | The system is able to show the detailed data of a single record. [pA3] |
| ID: | PB010 |
| Description: | The user can search for specific records. |
| Rationale: | The user might also want to search for a specific record. |
| Fit Criterion: | A search function provides means to find specific records defined by date, records, etc. [pA3] |
| ID: | PB011 |
| Description: | The user can print single records, parts, or the complete purchase book. |
| Rationale: | The user will want to print the purchase books. |
| Fit Criterion: | A print function allows to print single records, parts as well as the complete purchase book. [pA4] |
Additional Functionality
| ID: | PB012 |
| Description: | A history log stores all data changes. |
| Rationale: | To provide the complete history of a transaction, the system has to log all changes. |
| Fit Criterion: | The system stores each manipulation of a record. [future feature – depends on used database] |