Air University, Islamabad

Faculty Computing & of Artificial Intelligence

Department of Creative Technologies
BS Software Engineeirng

Assignment 02

Semester: Spring 2023 Max Marks: 10

Instructors: Hafiz Anas Bilal Section: A & B
Assigned Date: 16-03-2023 Due Date: 23-03-2022

Please carefully read and follow the instructions before creating/submitting your assignment.

Instructions:

1. Please submit a pdf file with the name format: SDA-YourRegistrationNumer-A2-SP23 .pdf.
Note: Only the placeholders in red will be replaced with your respective ones.
2. Sample file Naming: If your registration number is BSE193001, then your file name will be:
SDA-BSE193001-A2-SP23 .pdf.
3. Formatting styles: Font size (text) is 12 and 14 for headings, all the text is justified.
4. Make sure your names, registration numbers and the assignment number are clearly
mentioned on the title page of the deliverable that you submit.
5. Submit PDF of your milestone on the GCR and bring its hardcopy along with you in the next
lecture after the deadline.
6. If your submission is late or doesn’t follow the naming scheme/instructions, it will not be
graded.

1
Question No.1 [10]
Understand the following scenario and prepare a Class Diagram for it.

Scenario: Recruitment Management Software (RMS)

Recruitment Management Agency (RMA) is a specialist recruitment agency which
provides temporary staff to its clients. They need a software system, Recruitment
Management Software (RMS), to manage the employment contracts with their clients –
various organisations in need of temporary staff.
Each client would have an agreement with RMA for the provision of personnel on short
term contracts. An agreement is drawn up between RMA and the respective client
defining the categories of personnel, which RMA will be providing to the client and the
range of monthly salaries for each category. Each agreement is recorded in RMS and
may be subsequently amended by the Office Manager at RMA. The amendments may
involve adding or removing categories of staff to the agreement or amending the range of
monthly salaries for the existing categories of personnel. The Agreement is valid until it is
terminated by the Office Manager.
A client with an agreement with RMA would submit a staffing request for a particular type
of employee, a job description, key skills (KS) needed for the job, the starting date and
the duration of employment together with the salary for the vacant position. The request
can be submitted by an ordinary post, e-mail or verbally over the phone. The staffing
requests fall in one of the following two categories: regular and urgent. The staffing request
is validated by a Contract Manager against the Agreement (the validation consists of checks if
the required staff category is listed in the Agreement and if the salary offered in the staffing
request is within the salary range defined in the Agreement). If the validation is passed
successfully the Contract Manager approves the staffing request. Approved requests are
recorded in RMS with the details provided by the client in the staffing request; requests
which fail the validation checks are discarded. Once a staffing request is recorded, the RMS
will query the Candidates Management System (CMS), a legacy software system, which RMA
currently use, to manage all employment candidates registered with RMA, to establish if
candidates with suitable skills are available in CMS. The RMS is expected to query CMS
using the KS provided in the staffing request. In response to the query made by RMS,
CMS will return a list of candidates who match the supplied KS. The list will be ordered by
how the candidates are ranked (i.e., how well they meet the KS). RMS will then take up to
three (3) candidates for regular staffing requests and up to 5 candidates for the urgent
requests, which best match the KS specified in the staffing request. If the list of candidates is
not empty, the RMS will proceed and send e-mails to the selected candidates informing
them about the employment opportunity specified in the staffing request suggesting that they
get in touch with RMA if the candidates are interested. In case of urgent requests, the
selected candidates shall also be sent SMS messages on their mobile phones. A deadline
shall be set in the email/SMS for the candidate to confirm their interest. Candidates will be
given a deadline of 7 days to respond to regular staffing requests and 3 days to respond to
urgent staffing requests.
If the CMS query returns an empty list of suitable candidates, then the request is marked
as failed and the client is informed by email that RMA cannot meet the staffing request.
When a candidate confirms their availability for the job (by email or phoning back the
RMA office) the Contract Manager records with RMS that the particular candidate has
accepted the offer. An email is then sent to the client with the details of the successful
candidate. An email is also sent to the successful candidate with a draft contract and the
client details. At this point RMS marks the staffing request as completed. Any
subsequent confirmations from other candidates interested in the opportunity will be
declined. If no confirmation is received by the

2
set deadline (i.e., if none of the invited candidates confirms their availability for the offered
position), the RMS marks the staffing request as failed and emails the client accordingly.
The users of RMS should login before they can access the RMS functionality. Login accounts
(username, password and role) will be maintained by a system Administrator. There are 3 roles
envisaged in RMS:
- Contract Manager – can use the functionality related to the staffing requests but cannot
create/amend/remove client Agreements. The Contract Manager can only search and
read existing client Agreements;
- Office Manager has access to the entire functionality of RMS except dealing with login
accounts;
- System Administrator – deals with login accounts only – creates and deletes them – but
cannot use the core functionality of RMS (i.e., cannot deal with client agreements and
staffing requests).
In the analysis you can assume that any email and SMS attempted by RMS will be delivered
reliably. In other words, there is no need to consider in your models failures of the
communication channels (e.g., email delivery failures and failures of the SMS service).