Company Universal Consulting is a large consulting firm that specializes in IT consulting services for the Healthcare industry. The company employs over 2,000 dedicated IT professionals who design, develop, and implement tailored IT salutations for their clients. In order to instill the sense of community into its employees and to improve employee collaboration and innovativeness, Universal Consulting is planning to develop an Event Management Information System (EMIS) through which employees could further improve/expand their skills/knowledge useful for their own professions, collaborate on new ideas and initiatives, and socially connect with other members of the company and clients. The detailed requirements for EMIS are described in the following.
Events are classified into three categories-learning events, social events, and collaboration events. Learning events are for job-related trainings and seminars, social events are for social networking among employees and potential/existing clients, and collaboration events are for internal collaboration on the new idea/product development. Every year, an employee must attend at least one learning event, one social event, and one collaboration event.
An event manager creates and manages all events. The manager uses the EMIS to create an event and detail the event information including objectives, time, date, location, capacity, brief description, instructor/facilitator information. Once an event is created, the event manager invites senior managers to view, comment, and approve/reject the new event. The event manager may need to revise event details based on suggestions from the senior managers. Once an event is finally approved, the event manager publishes the event so that the event is available for public view and a notification of the event is sent out via email to all employees.
Upon receiving the notification, employees could log into the event management information system to review the event details, and register themselves to the event. Employees could also cancel the registered events, but they must provide reasons for the cancellation. Once registered, all participants will receive a reminder three days before the event. Participant could not cancel an event after the event reminder.
If it is considered necessary to involve existing/potential clients in some events, the event notification will be sent to the clients as well. In that case, the clients need to register themselves first, and create their own login ID and password to be able to register themselves to the events.
For any event to take place, a minimum of ten people is required. Therefore, the event manager could cancel an event if it attracts insufficient interests or an emergent situation happens. During the event, the event manager will keep track of event attendance, and record each participant's attendance on EMIS. Once an event is completed, the event manager will send out an online survey (created using EMIS) to the participants to gather their opinions and suggestions, which will be used for evaluating the event and for developing future events. The completed events will be archived and taken out from the EMIS web site.
In the year end, each department manager could access the EMIS to generate reports on his or her subordinate's event registration, cancelation, and attendance. The information will be used for each employee's annual assessment.
Content Requirements
Your individual project is developed based on the case description on project management system. In the individual project, you are required to compile all individual assignments together using Visio. Copy all Visio diagrams to the MS Word, arrange these diagrams in the following order.
Detailed Content of individual project
Requirement analysis and modeling
Event Table
Identify all events in the case and create an event table, and also build a noun table
Class Diagram
Draw a domain class diagram for the PMS system based on the noun table you have developed
Use Case Diagram
Draw a use case diagram for the system
Use Case
Write a detailed use case description for each use case of the system.
Activity Diagrams
Build activity diagrams for each use case description
System Sequence Diagram
Draw a sequence diagram for each use case.
Statechart Diagram
Draw a state chart diagram for any objects with dynamic behaviors in the system
- First, name each state chart diagram based on the name of the class for which the diagram is developed.
- Second, make sure that the states in the state chart diagram are the states of the class.
- Third, the class(es) should be in your class diagram.
- Fourth, when you have a composite state, Visio automatically opens another window allowing you to specify transitions of states within the state. Include both in your diagrams
Design Specifications
Detailed class diagram
Build a design class diagram based on the class diagram you have developed.
Note the following important things....
- First, you need to indicate navigation visibility in the design class diagram.
- Second, you need to include attributes and methods for each class, and specify attribute and method visibility.
- Third, no more multiplicities in the design class diagram.
- Forth, you could add handlers to your diagram as well as method(s) for each handler.
Detailed system sequence diagrams
Draw a detailed sequence diagram for each use case, based on the system sequence diagrams you developed and the design class diagram.