SOFTWARE REQUIREMENTS SPECIFICATION (SRS)

AYESA Web Based Test Generation and Execution Software (TESTMATIC) TEAM 2

Team Members: Emre Altay Fatma Nur olakolu Deniz Glsoy Kenan Gngr

Acquirer: Dr. zlem Albayrak Consultant: Dr. Cneyt Sevgi Customer: Mert Sungur (AYESA)

Change History Table

Version Number 1.0 Date 06.11.2010 File Name SRS_Team2.docx Status Created Description Preparation and revision of SRS is completed. Updated according to check list. Functional and non functional requirements, constraints are updated. Use case diagram and descriptions are updated.

1.1 1.2

10.11.2010 05.12.2010

SRS_Team2.docx SRS_Team2.docx

Updated Updated

1.3

22.12.2010

SRS_Team2.docx

Updated

Table of Contents

Introduction ........................................................................................................................ 6 1.1 Purpose ........................................................................................................................ 6 1.2 Scope ........................................................................................................................... 6 1.3 References ................................................................................................................... 7 1.4 Definitions and Acronyms ........................................................................................... 8 2 Overall Description ............................................................................................................ 8 2.1 Objectives of the Project.............................................................................................. 8 2.2 Functional Requirements of the Product ..................................................................... 8 2.2.1 Use Case Model/Context Diagram ....................................................................... 9 2.2.2 System Features.................................................................................................. 11 2.2.3 Use Cases Specifications .................................................................................... 14 2.3 Non-Functional Requirements and Constraints of the Product ................................. 29 3 System Models of the Product ......................................................................................... 31 3.1 Activity Diagrams for the main scenario of the use cases ......................................... 31 3.2 System Sequence Diagrams for the main scenario of the use cases .......................... 39 3.3 Graphical User Interface mock-up screens ................................................................ 45 3.4 Analysis Object Model .............................................................................................. 48 3.5 Analysis Sequence Diagrams .................................................................................... 49

List of Figures
Figure 1: Use Case/Context Diagram.............................................................................................. 9 Figure 2: Use Case/Context Diagram............................................................................................ 10 Figure 3: Use Case/Context Diagram............................................................................................ 10 Figure 4: Activity Diagram for Manage Tool Settings ................................................................. 31 Figure 5: Activity Diagram for Create Question ........................................................................... 32 Figure 6: Activity Diagram for Update/Delete Question .............................................................. 33 Figure 7: Activity Diagram for Filter Created Questions ............................................................. 34 Figure 8: Activity Diagram for Create\Assign Test ...................................................................... 35 Figure 9: Activity Diagram for Update/Delete Test...................................................................... 36 Figure 10: Activity Diagram for Print Test ................................................................................... 37 Figure 11: Activity Diagram for Take / Submit / ViewOwnTestResult ....................................... 38 Figure 12: System Sequence Diagram for Manage Tool Settings ................................................ 39 Figure 13: System Sequence Diagram for Create Question .......................................................... 39 Figure 14: System Sequence Diagram for List Questions ............................................................ 40 Figure 15: System Sequence Diagram for Update/Delete Question ............................................. 40 Figure 16: System Sequence Diagram for Filter Created Questions ............................................ 41 Figure 17: System Sequence Diagram for Create Test ................................................................. 41 Figure 18: System Sequence Diagram for Update/Delete Test..................................................... 42 Figure 19: System Sequence Diagram for Assign Test/Print Test/View Test Results ................. 43 Figure 20: System Sequence Diagram for Employee to Take/Submit/ViewOwnTestResult ....... 44 Figure 21: System Sequence Diagram for Applicant to Take/Submit/ViewOwnTestResult ....... 44 Figure 22: Analysis Object Model ................................................................................................ 48 Figure 23: Analysis Sequence Diagram for Manage Tool Settings .............................................. 49 Figure 24: Analysis Sequence Diagram for Create Question ....................................................... 49 Figure 25: Analysis Sequence Diagram for Update/Delete Question ........................................... 50 Figure 26: Analysis Sequence Diagram for Filter Created Questions .......................................... 51 Figure 27: Analysis Sequence Diagram for Create Test ............................................................... 52 Figure 28: Analysis Sequence Diagram for Update/Delete Test .................................................. 53 Figure 29: Analysis Sequence Diagram for Assign/Print/View Test Result ................................ 54 Figure 30: Analysis Sequence Diagram for Employee to Take/Submit/View Own Test Result .. 55

List of Tables
Table 1: Manage Tool Settings ..................................................................................................... 14 Table 2: Create Questions ............................................................................................................. 15 Table 3: List Questions ................................................................................................................. 16 Table 4 : Show The Content of Questions .................................................................................... 17 Table 5: Update Questions ............................................................................................................ 18 Table 6: Delete Question ............................................................................................................... 19 Table 7: Filter Created Questions.................................................................................................. 20 Table 8: Create Test ...................................................................................................................... 21 Table 9: Update Test ..................................................................................................................... 22 Table 10: Delete Test .................................................................................................................... 23 Table 11: Assign Test .................................................................................................................... 24 Table 12: Print Test ....................................................................................................................... 25 Table 13: View Test Results ......................................................................................................... 26 Table 14: Take Test ....................................................................................................................... 27 Table 15: Submit Test ................................................................................................................... 28 Table 16: ViewOwnTestResult ..................................................................................................... 29

List of Images
Image 1: Login Screen .................................................................................................................. 45 Image 2: Main Screen ................................................................................................................... 45 Image 3: Create Question .............................................................................................................. 46 Image 4: Create Test Set Information Part .................................................................................... 46 Image 5: Create Test Settings Part ................................................................................................ 47 Image 6: Create Test Publish Part ................................................................................................. 47 Image 7: Question Bank ................................................................................................................ 48

1 Introduction
1.1 Purpose
This SW provides a usable platform to the AYESA in order to evaluate the skills and knowledge of the applicants and it also evaluates current employees performance which participated in the trainings. The purpose of this Web Based Test Generation and Execution SW is to help selecting the qualified employees by creating the random tests. Furthermore, it also measures the understandings of the given trainings about specific topics. Before the opinion of this SW was created, there were any interview and training evaluation program in AYESA. They were using the MS Word documents to create questions and then they were asking these questions to the candidates. Moreover, tests were printed and there was no system to enter and see the results of these tests. By the helping of this SW, administrator, question bank manager and test creator will choose the questions manually or automatically, ask these questions to the applicants and employees. Candidates will answer questions in a limited time period. Also, tests results will be shared with test administrators online. It will be designed for the specific need of the company. This web based SW answering question part will be used by person below: 1) For job candidates: Before selecting the qualified person for a job, AYESA wants to measure appropriate skills for specific job or general applications. Therefore, Admin groups will prepare the tests for candidates and candidates will show their skills by using the web based platform. After that, system will calculate points of candidates and AYESA will decide whether this person is suitable for this job or not. 2) For Employees (After Training): After giving training to the workers such as SW Process Model or SW Design Patterns, AYESA also wants to measure the current employees adequacy and trained person will be tested. AYESA also wants to see whether these trainings are helpful for their work performance or not. If trainings are beneficial for employees, AYESA will continue to give these trainings to their current employees; vice versa necessary precautions will be taken.

1.2 Scope
There are 4 types of main users which are the general users of this SW. Administrator: This person may create the questions. Also, he creates tests by choosing questions from question bank manually or randomly. He may update, delete questions and tests which are created by all of the authors. He may manage tool settings like giving authorization, adding new difficulty level, adding new category. Question Bank Manager: This person may create questions and tests. Moreover, he has an authorization for filtering the questions which is created by administrator or test creator. If he thinks that question is suitable for evaluation, he publishes the question at the question bank for creating test. He may update, delete questions which are created by all of the authors. He may update, delete tests which are created by him. Test Creator: This person may create questions and tests. He may update, delete his own questions or tests.

Test Taker: Test taker can be employee or an applicant. Test taker may take and submit tests. If test taker is employee, he may view his own grade and true answers of the test. The employees who work in AYESA will be evaluated after the training programs. Applicants will be examined at interviews before selecting for the job. For taking training evaluations, username and password will be defined. For taking interviews, applicants will enter the name and surname at the beginning of the test, no need for user defined entrance. When he enters his name and surname to the textboxes, this information will save into DB automatically. It will be possible to print the non answered test to be executed. Admin groups add questions to the DB. Tests will be created either by manually selecting among the question pool or by an automatic selection of question pool on the criteria of category, difficulty level, author, created date and time. It will be possible to define fill-in-the-blanks, true-false type of questions as multiple choices. It means we can identify the number of choice. For example, if there is two blank for filling in the blank type question, test creator will put only 2 choices into answers. A)/ To make understandable, some images will be seen near the questions. Difficulty level will be categorized as easy, medium, difficult and not applicable. Applicants may take the interview questions in short time. (In 1 hour, it has to finish.) Employees may take the tests in the identified but long time period.(For 7 days, it has to finish) The questions will be able to reply non - orderly. In the case of change to answers, DB will keep the last one. After training, Administrator will be able to decide who will take the evaluation tests. Results of the tests will be prepared automatically. If test is taken on the printed documents from the system, results of the tests will be entered to the system manually. Test executions and grading will be logged in the DB. Statistical evaluations will be possible to obtain.

1.3 References
AYESA, <http://www.ayesas.com/tr/>, 1.11.2010. Albayrak, Dr. zlem, < http://www.bilkent.edu.tr/~ozlemal/>4.11.2010. CTIS359 Lecture Notes ProProfs Quiz Maker, <http://www.proprofs.com/quiz-school/>, 15.10.2010.

UML Sequence Diagrams, <http://www.agilemodeling.com/artifacts/sequenceDiagram.htm>, 4.11.2010. Use-case, < http://www.usecase.org/>, 3.11.2010. UML 2 Activity Diagram, <http://www.agilemodeling.com/artifacts/activityDiagram.htm>, 4.11.2010.

1.4 Definitions and Acronyms

AYESA CTIS DB GUI LDAP QBM SRS SW UML : Aydin Software and Electronic Industry A.. : Computer Technology and Information System : Database : Graphical User Interface : Lightweight Directory Access Protocol : Question Bank Manager : Software Requirements Specification : Software : Unified Modeling Language

Mock-Up Screen: Tentative screen shots from system. It will help the managers and the developers to visualize the system.

2 Overall Description
2.1 Objectives of the Project
Objectives of the project are as follows: - To prepare and apply tests for interviews and in firm training evaluation to measure the efficiency of those processes. - To test applicants about psychological and capability about the job. So, the most skilled and qualified persons will be selected for the appropriate job positions. - To test employees, after infirm trainings. Therefore, effect of the training on the trainee will be measured successfully. - To prepare a question bank. - To decrease time consuming for preparing test. Preparing test by using Testmatic system will take less time instead of preparing it on the MS word. - To prepare statistical results for interviews and training tests for analyzing the success of the tests.

2.2 Functional Requirements of the Product

In this part, functional requirements of the project will be highlighted by the help of use case model and its specifications, features of the system.

2.2.1 Use Case Model/Context Diagram

Admin groups consist of Administrator, Question Bank Manager and Test Creator.

Figure 1: Use Case/Context Diagram

Figure 2: Use Case/Context Diagram

Figure 3: Use Case/Context Diagram

10

2.2.2 System Features

Requirements 1. Admin groups shall be able to create new questions to question bank. 2. Questions shall have specifications like: - Category, - Difficulty level, - Author Name, - Created date and time. 3. Question type shall be multiple choices with requested number of choice. 4. If necessary, new category shall be able to identify by administrator. 5. Difficulty level of the questions shall be categorized as: - Difficult, - Medium, - Easy, - Not applicable. 6. If necessary, new difficulty level shall be able to identify by administrator. 7. Admin groups shall be able to add images to questions. 8. Administrator and QBM shall be able to delete the questions added by any of the authors. 9. Test creator shall be able to delete the added questions by himself only. 10. Administrator and QBM shall be able to update the questions added by any of the authors. 11. Test creator shall be able to update the added questions by himself. 12. Admin groups shall be able to create new test. 13. Test shall have specifications like: - Test Title, - Author Name, - Test Description. 14. Admin groups shall be able to set a time limit for test execution. 15. Admin groups shall be able to set start and finish day for a test. 16. Admin groups shall be able to set start and finish hour for a test. 17. If admin groups enables the randomization part of the test settings, questions shall be selected from the question bank randomly according to the determined Importance (1: min, 3: average, 5: max) 3 3

5 3 1

1 1 3 3 3 3 3 3

5 3 3 5

11

criteria of the question like: - Category, - Difficulty level, - Number of questions. 18. If admin groups disable the randomization part of the test settings, questions of the test shall be expected to select manually. 19. If admin groups prepare the test by manually, they shall create the test by selecting questions from the list. 20. Testmatic shall be able to list the questions according to determined criteria: - Category, - Difficulty level, - Author Name, - Created date and time. 20.1. Admin groups shall be able to list the created questions. 20.2. By clicking on the specific question, content of the question will be shown by admin groups including; - Author Name, - Category, - Difficulty level, - Image, - Created date/time - Question, - Answer Choices, - Correct answer. 21. Testmatic shall be able to sort listed questions according to determined criteria: - Category, - Difficulty level, - Author Name, - Created date and time. 22. Admin groups shall be able to see the preview of prepared test. 23. Admin groups shall be able to print prepared tests. 24. If employee or applicant takes exam via web browser, admin groups shall decide to publish the prepared test at the interview or training part. 25. If test published to training part, admin groups shall determine that which employees will take this test. 26. Testmatic shall be able to save created test in the DB. 27. Administrator shall be able to delete the tests created by any of the authors. 28. Test creator and QBM shall be able to delete created tests by him. 29. Administrator shall be able to update the tests created by the any of the authors. 30. Test creator and QBM shall be able to update tests

5 3 3

1 3

5 3 3 5 5 3 3 3 3 12

created by him. 31. Testmatic shall list the created tests according to determined criteria like: - Category, - Author name, - Time dependency, - Randomization availability. 32. Testmatic shall be able to sort created tests according to determined criteria like: - Category, - Author name, - Created date and time. 33. Applicant shall enter the name and surname at the beginning of the test. 34. Employees shall get the test by entering username and password. 35. Applicant and employee shall be able to answer questions in any order. 36. If employee logout from the system without completing the test, marked questions shall enable to keep in DB. 37. If employee or applicant changes the answer of the question, answer of this question shall be able to update in DB. 38. Submitted tests by employee and applicant shall save in DB. 39. Admin groups shall be able to see the selected list of submitted test according to criteria like: - Category, - Test Title, - Author Name, - Employee or applicant name. 40. Admin groups shall be able to see the sorted list of submitted test according to criteria like: - Category, - Test Title, - Author Name, - Employee or applicant name. - Submitted date and time. 41. If training and interview test is taken via web browser, testmatic shall execute the tests automatically. 42. If test is taken on the printed documents, grade of the each test takers will be entered to the system manually. 43. Testmatic shall display the number of true, false and blank answers of the each employee or applicants test to admin groups. 44. Testmatic shall display the rank of each employee or applicant test to admin groups. 45. Testmatic shall display the answered sheet of each employee and applicant to admin groups. 46. Employee shall view the grade of submitted test.

3 3 5 5 5 5 3

5 1 5 5 5 3 13

47. Employee shall view the correct answers of the test. 48. If test is time dependent, after the time out employee shall view his grade. 49. If test is time dependent after the life time of the test out, employee shall view the true answers of the test. 50. Testmatic shall display mean value of test. 51. Testmatic shall display standard deviation of test.

3 5 5 3 3

2.2.3 Use Cases Specifications

Use Case Name: Use Case ID: Source: Primary System Actor: Other Participating Actors: Description: Preconditions: manageToolSettings Use Case Type 1 System Requirement Administrator N/A Actor may able to change all tool settings of the system. Internet connection must be provided. The actors must login the testmatic. If actor thinks that there must be some changes into system features, this process will occur. This use case is initiated after the actor clicks on the settings tab on the manage tool settings page. Actor Action Step 1: The actor clicks the setting tab. Step 2: The actor makes changes on features of the system. Step 3: The actor clicks the make changes button. System Response Step 4: The system will save the modifications.

Trigger: Typical Course of Events:

Alternate Courses: Post condition:

New category and difficulty level will be added. Authorization will be given to some employees. SpecialRequirements/Implementation Use-case must be available to the member 7x24 Constraints: Table 1: Manage Tool Settings

14

Use Case Name: Use Case ID: Source: Primary System Actor: Other Participating Actors: Description: Preconditions: Trigger:

createQuestions Use Case Type 2 System Requirement Admin groups N/A Actors will create the questions. The actors must login the testmatic. Internet connection must be provided. This use case is initiated after the actor clicks the create question part on the menu at the top of the page. System Response Step 3: The system will respond by displaying the confirmation message. Step 5: The system will save the features of the created question into the DB. Step 6: The system will send confirmation message again. Alt -Step1: If actor enter missing information or doesnt select the time or difficulty level etc., the system will send a warning message. Actor Action Step 1: The actor selects time limit, content, difficulty level, type, number of questions and true answers. Step 2: The actor clicks on the add button. Step 4: The actor clicks on the add test button.

Typical Course of Events:

Alternate Courses:

New question will be created. Post condition: SpecialRequirements/Implementation Use-case must be available to the member 7x24 Constraints: Table 2: Create Questions

15

Use Case Name: Use Case ID: Source: Primary System Actor: Other Participating Actors: Description: Preconditions: Trigger: Typical Course of Events:

List Questions Use Case Type 3 System Requirement Administrator N/A Admin Groups will be able to view created questions. Internet connection must be provided. The question must be created. This use case is initiated after the actor clicks on the Question Bank sub menu in the Questions tab menu. Actor Action System Response Step 1: The actor will click on Step 2: The system will the Question Bank sub menu in get the created the Questions tab menu. questions from the database. Step 3: The system will show the question list to the admin groups. If there is no question in the database, the system will give warning message to the admin groups. The listed questions will be displayed. Use-case must be available to the member 7x24.

Alternate Courses: Post condition: Special Requirements/Implementation Constraints:

Table 3: List Questions

16

Use Case Name: Use Case ID: Source: Primary System Actor: Other Participating Actors: Description: Preconditions: Trigger: Typical Course of Events:

Show The Content of Questions

Use Case Type

Alternate Courses: Post condition: Special Requirements/Implementation Constraints:

System 4 Requirement Administrator N/A Admin Groups will be able to see the content of the questions. Internet connection must be provided. The question must be created. The question must be selected. This use case is initiated after the actor double clicks on the specific question. Actor Action System Response Step 1: The actor will double Step 2: The system click on the specific question. will get the details about question from the database. Step 3: The system will show the content of the selected question including ; Category, Difficulty Level, Author Name, Image, Created Date/Time, Question, Answer Choices, Correct Answers. The details of selected question will be displayed. Use-case must be available to the member 7x24

Table 4 : Show The Content of Questions

17

Use Case Name: Use Case ID: Source: Primary System Actor: Other Participating Actors: Description: Preconditions:

updateQuestions Use Case Type 5 System Requirement Admin groups N/A Actors will update the questions. The actors must login the testmatic. Internet connection must be provided. This use case is initiated after the actor clicks the edit button at the update question page. System Response Step 2: The system will respond by displaying the questions. Step 5: The system will save the features of the created question into the DB. Step 6: The system will send confirmation message again. Alt -Step1: If actor enter missing information or doesnt select the time or difficulty level, the system will send a warning message. Actor Action Step 1: The actor clicks on the edit button of question that he wants to change. Step 3: The actor makes changes any part like content, difficulty level, author of question and Step4: The actor clicks the update button.

Trigger: Typical Course of Events:

Alternate Courses:

Updated question will take place in DB. Post condition: SpecialRequirements/Implementation Use-case must be available to the member 7x24. Constraints: Table 5: Update Questions

18

Use Case Name: Use Case ID: Source: Primary System Actor: Other Participating Actors: Description: Preconditions: Trigger: Typical Course of Events:

deleteQuestions Use Case Type 6 System Requirement Admin groups N/A Actors will delete the questions. The actors must login the testmatic. Internet connection must be provided. This use case is initiated after the actor clicks the delete button. System Response Step 2: The system will send warning message. Step 4: The system will delete this question from the DB. Alt -Step1: If actor clicks the more than one item at the right part and click the delete selected items button, the system will delete the all selected items. Actor Action Step 1: The actor clicks on the delete button of specific question. Step 3: If the actor clicks the OK button.

Alternate Courses:

Deleted question will take place in DB. Post condition: SpecialRequirements/Implementation Use-case must be available to the member 7x24 Constraints: Table 6: Delete Question

19

filterCreatedQuestions Use Case Type 7 System Requirement QBM N/A Actor may able to filter the question which was entered by admin groups. He/she may decide which question is appropriate for evaluation of employee or applicant. Internet connection must be provided. Preconditions: The actors must login the testmatic. If QBM sees fit to filter some questions, he will decide to filter. This case is initiated after the actor clicks on the Trigger: created question list. Typical Course of Events: Actor Action System Response Step 1: The actor reviews the Step 3: The system content of questions. will save the Step 2: The actor clicks the information into button for adding the the DB. question to the question bank. Step 4: The system will give the confirmation message. Altstep 2: If question is not appropriate for Alternate Courses: publishing questions into the question bank, actor will delete or update created question. Filtered and accepted questions will be open to Post condition: create test. SpecialRequirements/Implementation Use-case must be available to the member 7x24 Constraints: Use Case Name: Use Case ID: Source: Primary System Actor: Other Participating Actors: Description:

Table 7: Filter Created Questions

20

createTest Use Case Type 8 System Requirement Admin groups N/A Actors select questions randomly or manually from Question Bank and Create Test. The users must login the testmatic. Preconditions: Internet connection must be provided. This use case is initiated after the actor clicks the Trigger: create test part on the menu at the top of the page. Typical Course of Events: Actor Action System Response Step 1: The actor clicks the Step 2: The system Create Test menu item. responds by displaying create Step 3: The actor selects test menu screen. questions and sets test Step 4: The system properties and click Add responds by Test Button. displaying Create Test Form. Step 5: The system will list the test to the user and save into the DB. Alternate Courses: Created Test will take place in DB. Test is ready to Post condition: assign. SpecialRequirements/Implementation Use-case must be available to the member 7x24 Constraints: Use Case Name: Use Case ID: Source: Primary System Actor: Other Participating Actors: Description: Table 8: Create Test

21

Use Case Name: Use Case ID: Source: Primary System Actor: Other Participating Actors: Description: Preconditions: Trigger: Typical Course of Events:

updateTest Use Case Type 9 System Requirement Admin groups N/A The actor will update the test. The users must login the testmatic. Internet connection must be provided. This use case is initiated after the actor clicks the edit button at the update test page. Actor Action System Response Step 1: The actor gets test Step 2: The system according to selected will respond by categories. displaying the test list. Step 3: The actor selects a Step 4: The System test and clicks Update will send Button. confirmation message and save changes in DB.

Alt-Step 3: If actor is administrator, the system will allow the user to update created test by all of the authors. Alt Step 3: If actor is test creator, the system will allow the user to update test by created himself. Updated Test will take place in DB. Post condition: SpecialRequirements/Implementation Use-case must be available to the member 7x24 Constraints: Alternate Courses: Table 9: Update Test

22

Use Case Name: Use Case ID: Source: Primary System Actor: Other Participating Actors: Description: Preconditions: Trigger: Typical Course of Events:

delete Test Use Case Type 10 System Requirement Admin groups N/A The actor will delete the test. The users must login the testmatic. Internet connection must be provided. This use case is initiated after the actor clicks the edit button at the delete test page. Actor Action System Response Step 1: The actor gets test Step 2: The system according to selected will respond by categories. displaying the test list. Step 3: The actor selects a Step 4: The System test and clicks Delete will send Button. confirmation message and save changes in DB.

Alt-Step 3: If actor is administrator, the system will allow the user to delete created test by all of the authors. Alt Step 3: If actor is test creator, the system will allow the user to delete test by created himself. Alt Step 3: If user selects the many items from the list, the system will be able to delete selected tests. Deleted Test will take place in DB. Post condition: SpecialRequirements/Implementation Use-case must be available to the member 7x24 Constraints: Alternate Courses: Table 10: Delete Test

23

Use Case Name: Use Case ID: Source: Primary System Actor: Other Participating Actors: Description: Preconditions: Trigger: Typical Course of Events:

assignTest Use Case Type 11 System Requirement Admin groups N/A The actor will assign the test. The users must login the testmatic. Internet connection must be provided. This use case is initiated after the actor clicks the assign test button. Actor Action System Response Step 1: The actor assign Step 2: The System test under the interview or will send training test. confirmation message.

Alternate Courses:

Alt-Step 1: If test taker is employee which takes test via web browser, admin groups will assign test to employees.

Test is open to use of employee and applicant. Post condition: SpecialRequirements/Implementation Use-case must be available to the member 7x24 Constraints: Table 11: Assign Test

24

Use Case Name: Use Case ID: Source: Primary System Actor: Other Participating Actors: Description: Preconditions: Trigger: Typical Course of Events:

printTest Use Case Type 12 System Requirement Admin groups N/A The actor will print the test. The users must login the testmatic. Internet connection must be provided. This use case is initiated after the actor clicks the print test button. Actor Action System Response Step 1: The actor prints the Step 2: The System selected tests. will send nonanswered test sheet.

Alternate Courses:

Printed test in hand. Post condition: SpecialRequirements/Implementation Use-case must be available to the member 7x24 Constraints: Table 12: Print Test

25

Use Case Name: Use Case ID: Source: Primary System Actor: Other Participating Actors: Description: Preconditions:

Trigger: Typical Course of Events:

viewTestResults Use Case Type 13 System Requirement Admin groups N/A Actors may able to see test results for every employee or applicant. Internet connection must be provided. The actors must login the testmatic. The questions had to submit by employee or applicant. This use case is initiated after the actor clicks on the view test result button. Actor Action Step 1: The actor clicks the get test result list button. Step 3: The actor clicks the view button to see the selected test results.

System Response Step 2: The System will display the resulted test list. Step 4: The system will send the grade and true answers of the test. Alt-Step 1: If actor wants to see specific persons Alternate Courses: result, he/she clicks the check box and selects a specific person. Test results are obtained Post condition: SpecialRequirements/Implementation Use-case must be available to the member 7x24 Constraints: Table 13: View Test Results

26

Use Case Name: Use Case ID: Source: Primary System Actor: Other Participating Actors: Description: Preconditions: Trigger:

Typical Course of Events:

Alternate Courses:

takeTest Use Case Type 14 System Requirement Employee, Applicant N/A Actors will get assigned test and answer it. The users must login the Testmatic. Internet connection must be provided. As employee, This use case is initiated after the employee enters his current username and password. As applicant, This use case is initiated after the applicant enters her/his name and surname to the textboxes and clicks the login button. Actor Action System Response Step 1: The actor enters Step 2: The system her/his own username and will respond by password. displaying the test Step 3: The actor clicks the screen. answers of the questions. Step 5: The system Step 4: The actor will click will save the the submit button. answers into the DB. Alt-Step 1: If actor is employee, the system will send the test screen to the user. Alt-Step 1: If actor is applicant, the system will get the information from textboxes and save it to the DB. After that, it will send the test screen. Alt-Step 6: If actor is applicant, system may not send the answers to the user.

Test is taken. Post condition: SpecialRequirements/Implementation Use-case must be available to the member 7x24 Constraints: Table 14: Take Test

27

Use Case Name: Use Case ID: Source: Primary System Actor: Other Participating Actors: Description: Preconditions: Trigger: Typical Course of Events:

submitTest Use Case Type 15 System Requirement Employee, Applicant N/A Actors will submit his/her answered questions. The users must login the testmatic. Internet connection must be provided. This use case is initiated after the actor clicks on the submit button. Actor Action Step 1: The actor selects the answers of the questions. Step 2: The actor enters the submit button.

System Response Step 3: The system will keep selected answers. Step 4: The system will send the answers to the user. Alt-Step 4: If actor is applicant, system may not Alternate Courses: send the answers to the user. Test is submitted into test DB. Post condition: SpecialRequirements/Implementation Use-case must be available to the member 7x24 Constraints: Table 15: Submit Test

28

Use Case Name: Use Case ID: Source: Primary System Actor: Other Participating Actors: Description: Preconditions: Trigger: Typical Course of Events:

viewOwnTestResult Use Case Type 16 System Requirement Employee N/A The actor will view the result of the test. The users must login the testmatic. Internet connection must be provided. This use case is initiated after the actor clicks the view own test result button. Actor Action System Response Step 1: The actor clicks Step 2: The System will the get test result list display the resulted test button. list. Step 3: The actor clicks Step 4: The system will the view button to see send the grade and true the selected test results. answers of the test.

Employee will analyze his grade and true answers of the test. SpecialRequirements/Implementation Use-case must be available to the member 7x24 Constraints: Alternate Courses: Post condition: Table 16: ViewOwnTestResult

2.3 Non-Functional Requirements and Constraints of the Product

Usability There will be a help menu which helps the usage of this system. Users of the system must be able to use the system 24 hours a day, seven days a week. Performance If approximately 120 users use the system at the same time, there must be no impact on the system performance. Portability This system may not cause any problem while it is used by different operating systems such as XP or LINUX. Implementation Testmatic must be a web based application.

29

Security Each employee must have the username and password for taking the test. Availability The system must be available whenever users have intranet connection and proper worked hardware. Maintainability If there is need for defect correcting and determining new requirements, system will be changed. Constraints Testmatic must be a web based application. User authentication shall be performed in a separate method in the design for future LDAP adaptation. Tortoise SVN will be used as SCM tool, due to the requirement of customer. For the deployment of the software in another server, license costs must be zero except operational system cost.

30

3 System Models of the Product

3.1 Activity Diagrams for the main scenario of the use cases

Figure 4: Activity Diagram for Manage Tool Settings

31

Figure 5: Activity Diagram for Create Question 32

Figure 6: Activity Diagram for Update/Delete Question

33

Figure 7: Activity Diagram for Filter Created Questions 34

Figure 8: Activity Diagram for Create\Assign Test

35

Figure 9: Activity Diagram for Update/Delete Test

36

Figure 10: Activity Diagram for Print Test

37

Figure 11: Activity Diagram for Take / Submit / ViewOwnTestResult

38

3.2 System Sequence Diagrams for the main scenario of the use cases

Figure 12: System Sequence Diagram for Manage Tool Settings

Figure 13: System Sequence Diagram for Create Question

39

Figure 14: System Sequence Diagram for List Questions

Figure 15: System Sequence Diagram for Update/Delete Question

40

Figure 16: System Sequence Diagram for Filter Created Questions

Figure 17: System Sequence Diagram for Create Test

41

Figure 18: System Sequence Diagram for Update/Delete Test

42

Figure 19: System Sequence Diagram for Assign Test/Print Test/View Test Results

43

Figure 20: System Sequence Diagram for Employee to Take/Submit/ViewOwnTestResult

Figure 21: System Sequence Diagram for Applicant to Take/Submit/ViewOwnTestResult

44

3.3 Graphical User Interface mock-up screens

Image 1: Login Screen

Image 2: Main Screen

45

Image 3: Create Question By clicking the Next Question button, a new screen for creating a new question will appear. By clicking the Previous Question button, the previous created question will appear. By clicking the Save button; the existing created question will be saved.

Image 4: Create Test Set Information Part

46

Image 5: Create Test Settings Part

Image 6: Create Test Publish Part

47

Image 7: Question Bank

3.4 Analysis Object Model

Test User -userTypeId : int -userName : string -userPassword : string +LogIn() Question -questionId : int -description : string -category : string -d_level : string -author : string +getQuestionList() +CreateQuestion() +DeleteQuestion() +UpdateQuestion() -testId : int -title : string -description : string -timeLimit : int -dateLimit : string -author : string +getTestList() +CreateTest() +DeleteTest() +UpdateTest() +CreateTestInfo() +SaveTest()

1 1 UserType -userTypeId : int -userTypeName : string *

Category -categoryId : int -categoryName : string

DifficultyLevel -level_Id : int -levelName : string TestResult -userTypeId : int +ViewTestResult() +ViewOwnTestResult()

0..1

Figure 22: Analysis Object Model

48

3.5 Analysis Sequence Diagrams

Figure 23: Analysis Sequence Diagram for Manage Tool Settings

Figure 24: Analysis Sequence Diagram for Create Question

49

Figure 25: Analysis Sequence Diagram for Update/Delete Question

50

Figure 26: Analysis Sequence Diagram for Filter Created Questions

51

Figure 27: Analysis Sequence Diagram for Create Test

52

Figure 28: Analysis Sequence Diagram for Update/Delete Test

53

Figure 29: Analysis Sequence Diagram for Assign/Print/View Test Result

54

Figure 30: Analysis Sequence Diagram for Employee to Take/Submit/View Own Test Result

55