The convent we chose to make our
system is in Hambantota.One of major reasons why we chose it was because my
friend live that area. If any technical issue found or if there is any fault in
the system he can easily reach to that place and help them.
Before we make our system the
technical knowledge of people who interact with the system was low. So we
carried out some sessions to improve their computer knowledge and how to work
with our system. Not even we just made the system we took the responsibility to
teach them what they didn’t know. So as software engineers we accepted full
responsibility for our work and still we work on it even after delivering.
1.01 Accept full responsibility for their own work
Software Engineers should be able to accept the full responsibility for
their own work. Even
after delivery of the product Software Engineer should take the
responsibility of the product. As
an example if they have a bug after delivering the product Software Engineer
should take the responsibility to fix it immediately.
Since our project is a student administration system we have to
make sure whether our product works properly.
If there are any crashes in our product it can affect to all
student details. As an example
if in our system show wrongs about student it will generate all wrong report
and information about that student. Therefore we have to make sure our system
work properly and if any bug found to fix it immediately.
So, we make proper test plane and did several stages of testing for preventing
bugs.
Following example is one of our test scenarios.
Tester: G.K.L.U Madhushan Reg. No: 2012CS082
Use case
C001: Admin may be add user to the system and
register user can be log in to the successfully.
Test
scenarios:
Use case
ID
Scenario
ID
Test
Scenario
No: of
test cases
C001
S001
Register customer in to the system
3
S002
Validate the login functionality of
the application and ensure only the registered person only allowed to login.
3
Test Cases&Procedure:
1)T001 – (
Enter valid data and check out put)
Scenario ID
S001
Test case
ID
T001
Test Case
Description
Check add user functionality is working correctly and
after add details, check detail in the system.
We check different input and check out put.
Pre-condition
Navigatesystem
setting menupage and system is stable to test
Step No
Step desc
Test Data
Expected Result
status
Step 1
Click user button
Load add user window successfully. This page should show add user
button. All fields deactivate.
Pass
Step 2
Click Add button
Active four fields to input data
Deactivate add button and active save button and back button.
