[fromTheSprawl]

here are the statements where I based the use case
Hiring process

HR manager may post vacancy

An applicant may submit his/her requirements online

the system will give applicant unique id for application

Applicant may view the status of application based on Application id

An applicant may revise CV while status is pending

Applicant may delete application anytimg

HR manager may retrieve all submitted application

HR may approve/reject application

Application status will be updated upon approval/rejection

Results automatically be sent to applicant email

here is the use case:



what do you think? Is it good enough? thanks.

[MentalFloss]

This almost seems like a real project.

I think you might be better off creating two use cases diagrams. Create one where the applicant is the star and another where the HR manager is. Then describe their roles against their target agent.

As it is, this diagram is trying to explain the conversations between both of them on the same diagram.

Also, your include and extends tags do not seem to explain much and in fact, seem incorrect.

Anyway, let me see if I can explain this properly

|             +- Submit requirements ----------+
|             |                                |
|             +- View app status     ----------+
|             |                                |
Applicant ----+- Edit CV             ----------+--------> System
|             |                                |
|             +- Delete application  ----------+

After all, everything an applicant does will end up going to the system to be processed in some way.

Then you would have your HR manager with their behaviors:

|              +- Post vacancy            -----+
|              |                               |
|              +- Retrieve submitted apps -----+
|              |                               |
HR Manager ----+- Approve app             -----+---------> System
|              |                               |
|              +- Reject app              -----+

These things are not really important to know inside a use case diagram:

- the system will give applicant unique id for application
- Application status will be updated upon approval/rejection
- Results automatically be sent to applicant email

Those are all implementation details of the system or server as it were.

Hope this helps. Sorry if my drawings are too crude. Just try to remember what you're conveying.


PS: Use case diagrams are overrated and project manager candy...

Have fun.