Maintainability and future of product

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.

Software Deployment and Testing

Demo Video of the our product

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		Navigate  system setting  menu  page 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.	Pass
Step 3	Enter valid data to input test field	User ID : <Admin> Name : <kamal> Password : <admin> Capacity: 1	Active again Add Button. Deactivate save button and other test fields.	Pass
Step 4	Ok massage box massage		Shows massage box message “add details successfully”. Clear test fields.	Pass
Post–Condition		System stable and user can search enter details successfully.

Software Implementation

This is most valuable stage of our product. We highly care about product quality. We used java as our programming language and MySQL as our database. We are getting considered about ACM principal about Management and Profession resolve problems during implementation stage.

 We understand our software risk before it development. We take some rough idea about performance and effect level should be in software. Other things we are see our interesting and most talented areas before divided work among us. We make some time frame to end our work. 

When end some component develop we are double check it work properly. Take responsibility for detecting, correcting, and reporting errors in software and associated documents on which they work.

Example:

5.11 Not ask a software engineer to do anything inconsistent with this code.

All software engineers are responsible for follow code of ethics and professional Practice. Therefore other software engineers should be ethical not asked to do anything against to this code. So, software engineers are responsible to promote an ethical approach to the management of software development and maintenance.

When implementing this system gave our attention on code of ethics and follow the principle in every step. All team members got the responsibility of that.

In the developing process once client requested from us to use some plugins that are available on internet. 

But we were not agreed with that because it not ethical according to code of ethics and if someone has copy right it will be illegal.

Other than that nobody asked to do anything inconsistent with code of ethics.  Developing team always tied with the code of ethics because all the members have knowledge on principles of code of ethics.

6.08 Take responsibility for detecting, correcting and reporting errors in software and associated documents on which they work.

Software engineers are responsible to their own code and documents. In any case if some problem occurs due to error in these two software engineers should detect, correct or report that error.

In this stage when we build some module we found some performance and availability troubles. We always record this and discuss each other and come some agreement.