CHAPTER FOUR

SYSTEM IMPLEMENTATION AND EVALUATION

4.0 Preamble
The purpose of system implementation is to produce a fully developed,
functional, and integrated system, in accordance with the functional
specification and ready for acceptance and testing. Normally program
implementation starts only when the design stage is completed. System
implementation does not actually mean stopping the old system and starting
the new one, but it has much more explanations to qualify the meaning,
because it is in the implementation stage that the following activities are
required by the company
i.Training of the staff to use the system
ii. Equipment conversion
iii. Evaluation and maintenance

4.1 Testing and Evaluation

Testing is the process of executing a program or system with the intent of

finding errors (Michelle & E., 2006). Simply testing involves the processes of
verifying and validating
the
program or application. The primary purpose of testing is to ensure that the
system
meets the requirements and satisfies the user's needs and it's also working as
expected. Verification is the process of making sure the product satisfied the
conditions imposed at the start of the development phase. In other words, to
make sure that the products behaves the way we want it to. While, Validation
is the process of inaking sure the product satisfies the specified requirement
at the end of the development phase.
Scopes of software testing often include examination of codes, execution of
codes in various environment and conditions. The following are the strategies
adopted at the testing phase of the system:
i. Unit testing: -Unit testing is a procedure use to validate those individual
units of source codes are working properly. A unit is a smallest part of an
application that can be tested. In this application, the individual unit is the web
page.
ii. Integration Testing: - is a systematic testing technique for constructing the
software architecture while at the same time conducting test to unveil errors
associating with interfacing. The reason for integration testing is to verify
functional performance and reliability requirements placed on major design
items. These groups of units are exercised through their interfaces. Using
black box testing, success and error cases are being stimulated through
appropriate parameter and data input. Simulated usage of shared data area
and inter process communication is tested and individual subsystem are
exercised via their input interface. Test cases are constructed to test that all
components within assemblages interact correctly, across procedure calls of
process activations. The unit tested components are integrated to build a
program structure that has been ditched by design. The strategy adopted here
is the incremental integration testing, a combination top-down and bottom-up
testing.

4.2 System Conversion Plan

This is the part of the research work that defines how to convert from the
existing system (manual method) to the new system, after training the
user/staff.
4.2.2 Parallel Approach
Due to the suitability of parallel method, the changeover of this program
should be parallel changeover as parallel changeover simply means the use
of both old and new system side by side until the new system satisfy the user
then the old one can be
eliminated,
42.3 Direct Change Over
Direct conversion is an implementation process that involves essentially
"switching off" the current system entirely and "switching on" the new system
to take its place all at once. The old system is no longer available for use from
that point onward.
4.3 System Documentation
Finally, documentation is necessary, since poor documentation available from
earlier stages has resulted into excessive and time consuming maintenance.
There are examples of abandoned computer based systems due to lack of
documentation. So, if a system analyst neglects documentation at earlier
stage in a project, the error will be sadly apparent when system maintenance
is attempted at a sample of a system.
4.4.1 Installing the Program Folder/Files
1. Open the CD containg the file "Student Information Management System"
2. Copy the entire folder to the Destination Drive(destination drive can be
described as a process of resolving issues and creating backups).
3. Close
44.2 Running the Software System
1. Open the folder or Directory
2. Select the Exe file name "Student Information Management System"
3. Enter Username and Password as contained in the README file The
programming language used is PHP (Hypertext Pre-processor), CSS
(Cascading Style Sheet), and MySQL (My Structure Query Language). To run
the program;
1. Put your XAMPP server online
2. Open your browser
3. On the address bar, type localhost/program/index.php
4. The program is ready for use
4.5 Sample Outputs
 CHAPTER FIVE

SUMMARY, CONCLUSION AND RECOMMENDATIONS

Preamble
This chapter presents the summary, conclusions and recommendations of the
whole report in general. It briefly summarize the report, gives conclusion to the
report, and also recommends ways which the project can be further enhanced
to maintain and perform optimally better functions.

5.2 Summary

Project titled "Student Information Management System" provides a

computerized student information management to Kaduna Polytechnic,
Kaduna. It provides easy, friendly, transparent and up-to-date record of all
registered students. It also creates an integrated information technology
environment for students; head of department, staff, and administrators, and
to have a proper and well manage student information system for Kaduna
Polytechnic.
This project work is limited in its functionalities due to time constraint,
acquisition, and screening of information. The application is not an end in
itself. However there is no doubt that the application will really help in solving
problems of student information management in Kaduna Polytechnic, Kaduna
State. The system was developed with programs written in PHP, HTML, CSS
and MySQL database.

5.4 Conclusion

The need for a computerized student information management system in any

college cannot be over emphasized; it is against this backdrop that this study
was undertaken to minimize the problem associated with the manual method
of student information management system in Kaduna Polytechnic, Kaduna.
To be abreast of time, a robust and efficient tool is no doubt required, that is
the reason why the choice of PHP was made to develop this work because of
its ability to produce simple and dynamic application, efficiently support
database, its portability, its functionality and it speed of execution. During the
course of this research work, it was observed that the existing system is
obsolete, which incapacitated it from not being able to meet up with the
demanded performance with respect to the increasing population of students.
The new system will eliminate the problems of delay, missing files, etc
associated with the manual method due to its user-friendly interface.

5.4 Recommendations

The software developed for the implementation of Student Information

Management System can be used by any institution of higher learning to
manage student records and history appropriately. The following
recommendations are proposed:
1. The college should provide an efficient internet network by incorporating its
existing
computers into an enterprise local network. Staff and students should be
sensitized to leverage its resources such as chart and voice messaging,
classroom conferencing, catalogues, library and other academic information
ranging from registration, lectures
to result requires.
2. Management should develop an intensive in-house training for academic
and non academic staff. This will help eliminate the dependence on manual
process and also increase staff competence on world class office automation.
3. Student Information Management System should be adopted by Kaduna
Polytechnic to ensure effective and efficient student record management.

REFERENCES

Abraham, S., Henry, F. & Korth, S. (2013). Database System Concepts.

Books New York. Pp.45-67.
Brendan, P. K. (2005):Zen and the Art of the Internet (1" ed.) A Beginner's
Guide. New York: Prentice Hall Publishing.
Communications, Computers and Signal Processing, 1991 (Institute of
Electrics Engineers).
Jay, G. S. &Brad B. (2001), MYSQL/PHP Database Application. M&T
Lahman, R. (1998): Multiple Computer Network and Inter Computer
Communication;
ACM Gattlinburg Conference, June.
Luk, A. (9 May 1991). "Fujikama Goes Unix". IEEE Pacific Rim Conference on
Ndukwe, C.M (2010); Handbook on Research Project and Thesis Writing,
Aba; Cheeda Prints. Ojo A. I. (2015). Guideline to a Successful Project Work
and Seminal Presentation.
Retrieved from www.en.wikipedia.com/SIMS
Retrieved from www.tutorials point.com Simply Easy Learning Copyright 2014
by Tutorials Point (1) Pvt. Ltd. Tutorials Point (2014). Management Information
System (M.I.S). Wikipedia, the Free Encyclopedia (2016). Student Information
Management System.
www.howstuffworks.com
http://www.google.com
http://www.html-form-guide.com/php-form/php-form-validation.html
http://php.about.com/od/phpbasics/ss/mysql_files.htm
http://php.about.com/od/phpwithmysql/ss/od/phpwithmysql/ss/mysql_files.htm
http://php.about.com/od/finishedphp1/ss/php_login_code.htm
http://en.wikipedia.org/wiki/Automation
http://www.engineersgarage.com/invention-stories/computer-history
www.howstuffworks.com

Appendix:

Sample Code
Code for Login Page
public class Login extends JFrame implements ActionListener {
Container c = getContentPane();
private JButton btnLogin, btnCancel;
private JLabel lblUName, lblPasswd;
private JTextField txtUName;
private JPasswordField txtPasswd;
public Login() {
super("Login ...");
this.setSize(350, 200);
this.setLayout(null);
this.setResizable(false);
this.setLocation((Settings.getScreenSize().width / 2)
- 175, (Settings.getScreenSize().height / 2) - 150);
this.setDefaultCloseOperation(EXIT_ON_CLOSE);
lblUName = new JLabel("Username");
lblPasswd = new JLabel("Password");
txtUName = new JTextField();
txtPasswd = new JPasswordField();
btnLogin = new JButton("Login", new
ImageIcon(ClassLoader.getSystemResource("Images/login.png")));
btnCancel = new JButton("Cancel",new
ImageIcon(ClassLoader.getSystemResource("Images/cancel.png")))
;
lblUName.setBounds(50, 40, 140, 25);
txtUName.setBounds(150, 40, 130, 25);
lblPasswd.setBounds(50, 80, 140, 25);
62 | P a g e
txtPasswd.setBounds(150, 80, 130, 25);
btnLogin.setBounds(50, 120, 100, 25);
btnCancel.setBounds(180, 120, 100, 25);
btnLogin.addActionListener(this);
btnCancel.addActionListener(this);
this.add(lblUName);
this.add(lblPasswd);
this.add(txtUName);
this.add(txtPasswd);
this.add(btnLogin);
this.add(btnCancel);
}//constructor closed
public void actionPerformed(ActionEvent e) {
if (e.getSource() == btnLogin) {
try {
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
Connection con =
DriverManager.getConnection("jdbc:odbc:student");
try {
Statement st = con.createStatement();
ResultSet rs = st.executeQuery("SELECT *
FROM UAD WHERE Username='" + txtUName.getText() +
"' and Password='" +
txtPasswd.getText() + "'");
if (rs.next()) {
if (rs.getString(3).equals("Student"))
{
userMDI frm = new userMDI();
frm.setVisible(true);
} else {
new
frmAdminMDI().setVisible(true);
}
this.dispose();
}else{
JOptionPane.showMessageDialog(null,"Invalid username or
password","Invalid",JOptionPane.ERROR_MESSAGE);
}
con.close();
} catch (Exception ex) {
JOptionPane.showMessageDialog(null,
"Invalid username or password", "Invalid",
JOptionPane.ERROR_MESSAGE);
txtUName.setText("");
txtPasswd.setText("");
}
} catch (Exception x) {
JOptionPane.showMessageDialog(null, "Unable to
connect to the database", "Connection error",
JOptionPane.ERROR_MESSAGE);
}
}
if (e.getSource() == btnCancel) {
System.exit(0);
}
}actionPerformed() closed
public static void main(String args[]) {
new Login().setVisible(true);
}
}