Description of system to be modeled:

Tackleforce Management System for a Small Company.

A small company, with one location and less than 500 employees, has a culture of using 'tackleforces' to address issues facing it, thereby increasing empowerment of its employees, and harnessing the knowledge of its workers in a coordinated fashion. These tackleforces can address anything from customer satisfaction, to a competitive analysis of employee benefits, to improvements in inventory control. The final reports from these tackleforces contain recommendations, for consideration by senior management. The recommendations can propose anything from company performance metrics, to solutions to inefficiencies. It is also the culture of this company for senior management to issue a response, with explanations, as to why or why not the recommendations will be adopted by the company.

The company would like to have system to manage these tackleforces so it can leverage its employees' input as efficiently as possible. The company has multiple departments. Employees belong to departments. Employees can serve on on one or more tackleforces as tackleforce members, with the approval of their department heads. Sometimes the tackleforce members are appointed by their department heads or can volunteer. The new system is required to support a schedule of tackleforces being formed, the issue they will be addressing, and the target date of their initial meeting. This schedule is visible only to the department or departments from which the tackleforce is formed. (Tackleforces can be part of one department or be cross-departmental.) Once the tackleforce has been approved by a company vice-president, an administrative assistant from the CEOs office creates the tackleforce in the system and, as they are approved to participate, assigns employees into the tackleforces. One employee from each tackleforce is assigned as a tackleforce chair. A recording secretary is also assigned, who will generate minutes for each meeting, with next steps and member responsibilities etc., and these will be stored in the system, visible only to the tackleforce members themselves. Tackleforce members meet to produce recommendations to address the issues for which their tackleforce was formed. Specific recommendations are discussed and voted on by tackleforce members during tackleforce meetings, and the tackleforce concludes its work with a final report of its recommendations. Here are examples of the pieces of data that the system needs to capture Employee name, email address, department they belong to, tackleforce title, and description, recommendation report ID, date on which final report was submitted, meeting dates, attendance of each meeting (online, offline), and a summary of comments that employees make on the report (showing the degree to which they agree/support the recommendations in the report), and eventually the senior management response.

Questions

What diagrams are expected?

Use Case diagram

Use case description/specification for at least two use cases.

Class diagram