Description of the Problem
The Raju Corporation maintains a chain of hotels world-wide and wants to introduce a new computer system to capture feedback from hotel guests. Information will be sought on comments made on various aspects of each hotel's operations (such as compliments about service received, and suggestions for improving services), and, more importantly, complaints about service received. Collectively, comments and complaints will be known as 'submissions' to the system.
Hotel guests will be able to enter comments and complaints via the hotel's website. The system will allocate a unique identifier for the submission, and record the nature of the submission, the guest who entered it and the date. Both comments and complaints are logged by the system, and may be archived at a later date, but complaints require specific action to resolve them.
Handling Complaints
A manager will be able to access the system and list all new complaints in date order. A new complaint is defined to be one that has not had a 'resolver' assigned to it (see below).
A manager will be able to view a list of all staff, and to designate a member of staff responsible for resolving a complaint, with a deadline date for its resolution. A manager may subsequently change the resolver assigned to a complaint and the associated deadline.
A resolver will be able to use the system to record an action taken in response to a complaint. An action will record what has been done, and the date of the action. A resolver will be able to record that a complaint has been resolved. Such complaints will then be inspected by a manager, who may confirm that the complaint has been resolved, or request that further action be taken.
A manager will be able to list the details of all resolved complaints that have not been confirmed, and list all unresolved complaints in deadline date order.
Recorded Data
Staff and guest details are already recorded in the hotel database which is used for other applications. Each guest has an id number, name, address, email address and a telephone number. Every hotel employee has an id number, a name, department and their role within the department. An example of a role and a department might be "waiter" and "catering" respectively. Managers are hotel employees with privileged access to the system.
Archiving Submissions
Periodically, all submissions that meet certain criteria will be archived and purged from the system. Complaints will only be archived when they are marked as resolved, and confirmed by a manager. Comments can always be archived
----------------------------
i have create the Use case diagram in (Posidon for UML) and attach it with this thread.
can any body tell me that em goin in right direction.
any help will be appricated.
Thanks
i
[IMG]file:///D:/DOCUME%7E1/Yasar/LOCALS%7E1/Temp/moz-screenshot.jpg[/IMG]