Answer Happy

Task 1: Class Diagram 1.1.Client's Description Hi my name is Ahmad and I work at the Talent Acquisition (TA) department at xyzSoft company. In the TA department, we are responsible for hiring people to serve in the various departments. However, we need to automate a lot of our daily procedures since most of them are repeated. Anyway, xyzSoft has a hierarchy composed of multiple divisions; each division is composed of many departments. Whenever we hire someone, he/she should be linked to one of the divisions or departments. Each unit (division or department) is different in its nature and thus has different jobs. We call these “Job Bands”. For example, if a unit has a “Project Management” band, then it should include several jobs such as “Program Manager” and “Product Manager”. Similarly, if a unit has an “Engineering Band”, then it should include several jobs such as “Lead Engineer”, “Senior Engineer" and "Engineer". Nothing prevent a unit from having multiple bands if applicable. The company goes in a hierarchy review every 6 months or year. For this reason, we would like to have a way to generate the proper jobs for each unit based on the bands associated to it. Another issue, we need a system that takes care of the candidates that we process in our system. Each candidate has а name, national id (10 digits), and gender. Also, we need to capture more info such as years of experience and the candidate's CV. As part of our usual recruitment process, each new candidate should go through a clear process or set of recruitment stages. We would like to keep a clear record of all candidates and the results of their interviews. Some candidates go through a single interview while some go through 3 interviews. Each interview logs the basic info such date and time and the people who were interviewing the candidate. I hope you can build a system that reflect my needs. 1.2. What is required? Create a class diagram that reflects the above description. You should distinguish between what should be considered a class and what should be considered an attribute. Also, clearly specify the relation between classes. If the relation is an association, specify the multiplicity, label and direction of the relationship.