title: Online Job Portal System Use Case Diagrams
body: <p>I want to have a correct use case diagram for an online job portal system. Here is my attemp:</p>
  
  <p><img src="https://i.stack.imgur.com/6miAI.jpg" alt="onlinejobportalsystem"></p>
  
  <p>I have some doubts:</p>
  
  <ol>
  <li><p>I can't see where making "Login" use case witch is an important use case for this system.</p></li>
  <li><p>This use case diagram is not showing the difference between a simple visitor and a registered one. The former could view vacancies, view advice without the obligation for having an account. The latter could view vacancies, view advice, upload CV (after be logged), apply for a job (after be logged) ... Is having two actors "Simple visitor" and "Registred Visitor" in my diagram will be correct? Or is there a way to differentiate these two actors without the need to add a second?</p></li>
  </ol>
  
  <p><strong>Edit1:</strong></p>
  
  <p>Taking into account your remarks, here is my modified version:
  <img src="https://i.stack.imgur.com/vr3eW.jpg" alt="onlinejobportalsystemversionmodified"></p>
  
  <p><strong>Edit2:</strong></p>
  
  <p>I feel unsatisfied with my use case diagram. Here is my new version. use Cases added  are:</p>
  
  <ol>
  <li>Moderator: Notify JobSeeker/Employer, Disapprove Vacancy/Application, Manage Payment.</li>
  <li>JobSeeker: View  CV, Download CV, View Application Status, View Employer Details, Search Employer.</li>
  <li>Employer: View  CV, Search CV, Download CV, Edit Vacancy, Delete Vacancy, View JobSeeker Details, Search JobSeeker.</li>
  </ol>
  
  <p>And for the development part, I want to partition the work into three modules: one for the moderator, one for the JobSeeker and one for the Employer.</p>
  
  <p><img src="https://i.stack.imgur.com/PwQax.jpg" alt="onlinejobportalsystem3"></p>
  
  <p>Any remark?</p>