Asset Books
| ID: | AB001 |
| Description: | The assets book allows the recording of the assets of a company. |
| Rationale: | The main purpose of assets book is the calculation of the depreciation for wear and tear of the assets of a company. The assets book stores the assets and provides the calculation functionality. |
| Fit Criterion: | The ea-Geier provides an interface to assets. [pA2] |
Assets Data
| ID: | AB002 |
| Description: | Each record has a unique id provided by the system. |
| Rationale: | The system will give each asset an unique id in the order of entering the assets. |
| Fit Criterion: | Each asset has a unique id provided by the system. [pA2] |
| ID: | AB003 |
| Description: | Each record has name field describing the asset. |
| Rationale: | To name an asset the user needs a text field. |
| Fit Criterion: | Each assets holds a not-empty text field describing the transaction. [pA2] |
| ID: | AB004 |
| Description: | Each record stores the purchase date of the asset 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 asset stores the date given by the user, the first generation and the last manipulation of the record. [pA2] |
| ID: | AB005 |
| Description: | Each record has text field holding the data of the vendor of the asset. |
| Rationale: | To the data of the vendor of the asset the user needs a text field. |
| Fit Criterion: | Each assets holds a not-empty text field describing the vendor of the asset. [pA2] |
| ID: | AB006 |
| Description: | The acquisition costs the lifetime and the calculation method of the asset are stored by the system. |
| Rationale: | To calculate the depreciation of asset the system needs to know the acquisition costs, the life time and the depreciation method. |
| Fit Criterion: | Each record stores the data needed to calculation the depreciation. [pA2] |
| ID: | AB007 |
| Description: | The system will support different kinds of depreciation. |
| Rationale: | Depending on the country the user might to use different depreciation methods. e.g. Austria: linear depreciation on a half-year basis, Germany: linear depreciation on a monthly-basis and digressive depreciation. |
| Fit Criterion: | The system supports different kinds of depreciation with automatic calculation or user-given values. [pA2] |
| ID: | AB008 |
| 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. [pA2] |
Display
| ID: | AB009 |
| 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. [pA2] |
| ID: | AB010 |
| 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. [pA2] |
| ID: | AB011 |
| 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. [pA2] |
| ID: | AB012 |
| Description: | The user can print single records, parts, or the complete assets book. |
| Rationale: | The user will want to print the assets books. |
| Fit Criterion: | A print function allows to print single records, parts as well as the complete assets book. [pA4] |
Additional Functionality
| ID: | AB013 |
| 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] |