1. PowerJobs Website

2. Company name: Softwear Suit, Ltd. Students: Shiri Semo semos@cs.bgu.ac.il Tomer Mansur mansurt@cs.bgu.ac.il Technical advisor: Itzik Katzav itzik.katzav@softwear.co.il Academic advisor: Dr. Goldberg Mayer gmayer@cs.bgu.ac.il

3. Our Solution Provides all information transfer needs between candidates and man power companies. Makes the process of adding a candidate to a candidate pool efficient.

4. Problem Domain

5. System Architecture

6. Two main modules: DM – the candidates' module - The web application will be written using ASP.NET technologies. - The DM will access the DMDB using SQL queries. PM – the companies’ module - The PM will be written in C#. - The PM will access the PMDB using SQL queries. - The PM will access the DMDB using web services.

7. Requirements

8. Functional Requirements DM – Candidates’ module Creating a candidate card Logging in to an existing card Performing a candidate card update Viewing published positions Performing a position search Managing a position cart Applying for a position

9. Functional Requirements PM – Companies’ module: Publishing a position Modifying published positions Removing a published position Synchronizing modules

10. Functional Requirements Administrative: Adding new company

11. Non-Functional Requirements Response Time The user should receive a response within no more than 3 seconds, for the following actions: Creating a new candidate card. Performing a candidate card update. Logging in to an existing card. Performing a position search. Operations performed on shopping cart.

12. Non-Functional Requirements Safety & Security Candidate details will be transferred over the internet encrypted. Candidate’s password should be stored encrypted. Validating the identity of the synchronization initiator will be required.

13. Use Cases

14. Use-cases Creating a candidate card

15. Use-cases Logging in to an existing card

16. Use-cases Performing a candidate card update

17. Use-cases Performing a position search

18. Use-cases Adding a position to a position cart

19. Use-cases Viewing the content of a position cart

20. Use-cases Removing a position from a position cart

21. Use-cases Applying for a position

22. Use-cases Publishing a position

23. Use-cases Publishing a position immediately

24. Use-cases Removing a published position immediately

25. Use-cases Synchronizing modules – Candidates

26. Use-cases Synchronizing modules – Positions

27. Use-cases Adding a new company

28. Risks Supporting a large number of candidates accessing the DM simultaneously.

29. Thanks.