|
|
 |
|
|
|
|
|
|
User Requirements :- An Assets Maintenance database. Functional Requirements. Authorized Users (Five sales people) should have access to the database to enter a new complaint or to edit already opened complaint. Those five sales persons can login each time to the diferent computer ( 3 computers). Because I should track who opened complaint ( or edited already opened), there is a login problem. Each sales person should write to the system ( probably into customers details column), details about complaint. When another sales person some other day open the already opened complaint to add some aditonal information, new date should be entered and it should be recognized who added aditional info about complaint..., when the complaint is resolved, some kind of new box is shown on the form, in which person can put amount of money we pay back to the customer to resolve a complaint. In summary: The System should track who, when (date, time) has anything to do with new complain or has edited already opened, and what information was put into system. Design Notes :- This Page defines the Requirements for a Database for physical Assets. It contains four Sections : 1. Things of Interest 2. How these Things are related 3. Characteristics of these Things 4. User Scenarios
Barry Williams
|