Implementation of SAIMS-HND

0
10

Introduction

This chapter discusses about the implementation procedure of the system. This chapter is based on chapter 5 (Design of SAIMS-HND). Further it explains the methodologies and algorithms which are used to implement the design of the system. All the data that have analyzed are used in this chapter to implement the system. As stated, the implementation can be divided based on the modules and to implement these four modules PHP (CodeIgniter Framework) is used as the server site scripting and java script to write client functions and MySQL is used as the database engine. HTML, CSS and JQuery are also used to create web forms and attractive user interface and user experience. In addition to that, phpDesigner 7 is used as an IDE (integrated development environment) to implement the system.

Software

PHP and MySQL are the main software used to implement SAIMS-HND. PHP Version 5.3.1 and MySQL Version 5.1.41 are used to implement the system. In additional to that Apache version 2.2.14 on windows xp (service pack 2) machine is used as a server to test the PHP codes.

Hardware

This implementation doesn’t need a high processing hardware and is implemented using an Intel 2.2GHz processor and Pentium IV version computer having 512MB memory module installed. In addition to that a modem is required to connect internet since this is a web base system.

Implementation of user authentication

This is mainly based on Forms Authentication. Forms authentication, on the other hand, is ideal for Internet web applications. Recall that forms authentication identifies the user by prompting them to enter their credentials through a web form. Consequently, when a user attempts to access an unauthorized resource, they are automatically redirected to the login page where they can enter their credentials. The submitted credentials are then validated against the database.

After verifying the submitted credentials, a forms authentication is created for the user. This ticket indicates that the user has been authenticated and includes identifying information, such as the username. The forms authentication ticket (Session) is typically stored as a cookie on the client computer. Therefore, subsequent visits to the website include the forms authentication ticket in the HTTP request, thereby enabling the web application to identify the user once they have logged in.

Implementation of the identified modules

This section is about implementation details of the four modules discussed in chapter 5.

Payment Manager

From the administrator perspective once he logs in successfully he registers students and other (if any) administrators to the system. After the successful registration of students along with password and username the students can log in to the system. One the students are registered to the system the administrator needs to register the student for a particular semester along with the payment information for the semester. As long as the payments are not made from students, it is displayed that the payment is pending. When a student makes payment the administrator needs to update the semester payment for the particular student. There available a text box to search the corresponding student whose payment is received. Then the administrator updates the payment detail as paid or received.

Module Manager

Once the administrator registers a student for a particular semester the students are able to enter the module selection area. Once they visit, there will have the option to tick the course modules they want to offer based on their payment made and will be submitted by students. This will be entered in the database. Once the results are entered to the database by admin, it will be decided whether the student has passed or need to repeat. If identified as needed to repeat, it will be added to payment manager as a pending payment for the repeat exam and whenever the student wants to repeat the subject the student will need to make the payment. After that particular module will be added to the module manager and where the student will be able to select the module to do the exam at that semester.

Credit and GPA Manager

Once the student selects the modules to offer in a semester those modules will be added to credit and GPA Manager by system. Until the administrator enters the result it will have null values or empty values. Once the admin enters the results for the subjects offered by the students, they will be transferred to Credits and GPA, then they will be calculated as semester GPA and overall GPA.

PDF Result Generator

Implementation of PDF result generator has been integrated with all the queries. PDF result generator will have many options (buttons) to enter the other modules. For instance once the administrator has entered into payment manager option, he will be prompted many sub options such as total payment paid by students for the semester, by batch, and many more.

Summary

In this chapter implementation details have been discussed in a simplified form while rests of the codes are included in the Appendix. The next chapter is about how the system is evaluated against the requirement and objectives that were expected to achieve with the system.

LEAVE A REPLY

Please enter your comment!
Please enter your name here