CS504 Software Engineering – I Assignment 6 Ide Solution Fall 2012 On February 2013
In this assignment, we will develop test cases to test certain parts of the system. Please read the template file (template.doc) given with this assignment as helping guide. You will have to develop two test cases.
First test case will test “Add Department” functionality within “Administrative Control Module” of Online Budget Control System (OBCS).
Second test case will test “Budget Requisition” functionality within “Budget Submission/Allocation Module” of Online Budget Control System (OBCS).
Questions [Marks 10+10]:
1) Develop a test case to test the functional requirement “Add Department”.
In order to add a new department in the system, the user must have appropriate administrative rights. To add a new department, the details of the department including the department name, address, department id and phone is entered into a form. The system checks if the department is already registered or not. If not already registered, the system adds the department into database and gives success message.
2) Develop a test case to test the functional requirement “Budget Requisition”.
Only the authorized person can make the request for budget allocation. To make a budget request, user opens a request form and fills it with all the information about the items along with their estimated cost for which budget is required to allocate. After filling the form, it is submitted to the finance department. The system saves the information regarding budget allocation request and gives the message that request is submitted.
Note:
We will assume that the test cases will be tested in future, so you can skip certain details e.g. Tested By, Result etc.
Important:
You will have to develop a separate test case for each of the above use case. Also, make sure to strictly follow the given test case template provided in template.doc file which is uploaded with the assignment file.
Test Case Template
Test Case #:
Test Case Name:
System:
Subsystem:
Designed by:
Design Date:
Executed by:
Execution Date:
Short Description:
Write a short detail of the test e.g. the functionality to be tested
Pre-Conditions :
Describe the preconditions for the test case. A precondition is the state of the system that must exist before a test case can be performed.
Step
Action
Expected System Response
Pass/ Fail
Comments
1
Describe the flow of events that would be expected in normal eeexecution conditions
System response after each action/event performed by tester
2
3
4
5
6
Post Conditions:
Describe the post conditions for the use case. A post condition is a list of possible states the system can be in immediately after a test case has finished.
Test Case Example
Test Case #: 2.2
Test Case Name: Change PIN
System: ATM
Subsystem: PIN
Designed by: ABC
Design Date: 9/14/2012
Executed by: N/A
Execution Date: N/A
Short Description:
Test the ATM Change PIN service
Pre-Conditions :
The user has a valid ATM card – The user has accessed the ATM by placing his ATM card in the machine.
The current PIN is 1234.
The system displays the main menu.
Step
Action
Expected System Response
Pass/ Fail
Comments
1
Click the ‘Change PIN’ button
The system displays a message asking the user to enter the new PIN
2
Enter ’5555′
The system displays a message asking the user to confirm (re-enter) the new PIN
3
Re-enter ’5555′
The system displays a message of successful operation
The system asks the user if he wants to perform other operations
4
Click ‘YES’ button
The system displays the main menu
5
Check post-condition 1
In this assignment, we will develop test cases to test certain parts of the system. Please read the template file (template.doc) given with this assignment as helping guide. You will have to develop two test cases.
First test case will test “Add Department” functionality within “Administrative Control Module” of Online Budget Control System (OBCS).
Second test case will test “Budget Requisition” functionality within “Budget Submission/Allocation Module” of Online Budget Control System (OBCS).
Questions [Marks 10+10]:
1) Develop a test case to test the functional requirement “Add Department”.
In order to add a new department in the system, the user must have appropriate administrative rights. To add a new department, the details of the department including the department name, address, department id and phone is entered into a form. The system checks if the department is already registered or not. If not already registered, the system adds the department into database and gives success message.
2) Develop a test case to test the functional requirement “Budget Requisition”.
Only the authorized person can make the request for budget allocation. To make a budget request, user opens a request form and fills it with all the information about the items along with their estimated cost for which budget is required to allocate. After filling the form, it is submitted to the finance department. The system saves the information regarding budget allocation request and gives the message that request is submitted.
Note:
We will assume that the test cases will be tested in future, so you can skip certain details e.g. Tested By, Result etc.
Important:
You will have to develop a separate test case for each of the above use case. Also, make sure to strictly follow the given test case template provided in template.doc file which is uploaded with the assignment file.
Test Case Template
Test Case #:
Test Case Name:
System:
Subsystem:
Designed by:
Design Date:
Executed by:
Execution Date:
Short Description:
Write a short detail of the test e.g. the functionality to be tested
Pre-Conditions :
Describe the preconditions for the test case. A precondition is the state of the system that must exist before a test case can be performed.
Step
Action
Expected System Response
Pass/ Fail
Comments
1
Describe the flow of events that would be expected in normal eeexecution conditions
System response after each action/event performed by tester
2
3
4
5
6
Post Conditions:
Describe the post conditions for the use case. A post condition is a list of possible states the system can be in immediately after a test case has finished.
Test Case Example
Test Case #: 2.2
Test Case Name: Change PIN
System: ATM
Subsystem: PIN
Designed by: ABC
Design Date: 9/14/2012
Executed by: N/A
Execution Date: N/A
Short Description:
Test the ATM Change PIN service
Pre-Conditions :
The user has a valid ATM card – The user has accessed the ATM by placing his ATM card in the machine.
The current PIN is 1234.
The system displays the main menu.
Step
Action
Expected System Response
Pass/ Fail
Comments
1
Click the ‘Change PIN’ button
The system displays a message asking the user to enter the new PIN
2
Enter ’5555′
The system displays a message asking the user to confirm (re-enter) the new PIN
3
Re-enter ’5555′
The system displays a message of successful operation
The system asks the user if he wants to perform other operations
4
Click ‘YES’ button
The system displays the main menu
5
Check post-condition 1
