Informatics OperationsExams Management and Student E-Support System

PJ330 G IMSS B.Sc.
(Honors) in Computing (UOP)
University of Portsmouth
Technology Extended Campus
Honor‟s project undertaken in partial fulfillment of

the requirements for the
BSc (Hons) Computing
“Informatics Operations/Exams Management and Student e-

Support System”
by
Prakash Shrestha
Hemis No.
472124
Supervisor: Mr. Laxman Shimoga
Project unit: PJ 3330G
1 Prakash Shrestha | Hemis: 472124

PJ330 G IMSS B.Sc. (Honors) in Computing (UOP)
Abstract
Today‟s cyber world demands technological innovations in the least trivial areas of human
undertakings, let alone the error-sensitive and critical ones. Computers have revolutionized
the today‟s world and it will continue to do so. Without the aid of computers, small and
small jobs are near to impossible; the culmination of the ICT has had an inseparable bond
with the activities carried out lately. Surely Education Sector is never an alternative. With
the advent of computerized system, Informatics College has had a handful of benefits and
to add up to which, it has turned itself into the threshold of a new system with added
advantages.
This new project is aimed to provide Informatics College a complete set of tools to see off
entire problems it had pertaining to academics, operations, exams and student support.
The old system (ISMS) had also been real helpful but the demand has far increased,
seeking an enhanced new system. The proliferation of this project is due to the same.
The new system is expected to be dissimilar from the old system with respect to three
specific domains: User-friendliness, Added Functionalities and Addition of Student
Support. Data entry and Report Generation must also be fast, seamless and simple.
Keyword List
Informatics Operations/Exams Management and Student e-Support System

Acknowledgements
I am grateful to Informatics Academy for providing me this opportunity to prove my
academic capabilities in something more professional and practical. This honors project
carried out in crunch time has taught me utterly necessary lessons as to how a
professional project should be managed and handled. I cannot also thank more to my
project supervisor Mr. Laxman Shimoga for enduring my steep mistakes and shortcomings
and finally accepting my project on his behalf.
Plagiarism Declaration
I confirm that the enclosed written work (including application code) is entirely in my own
words except where explicitly stated otherwise. I further declare that wherever I used
copying, paraphrasing, summarizations or other appropriate mechanism related to another
author's work it has been properly acknowledged in accordance with normal scholarly
conventions. I further understand that wherever 6 or more consecutive words are extracted
from a source they must be acknowledged and 10 consecutive words that are
unacknowledged will be regarded as proof of plagiarism.
Signed Student Name Prakash Shrestha


Chapter 1 – Systems Introduction
1.1 Objective of this Chapter:
The objective of the chapter is to provide the overview of the IMSS idea and to introduce
the problem domain being studied. This chapter aims to initiate the project by introducing
various project aspects:
 Motivational Factors
 Project Background
 Problem Domain
 Scope of the project
 Approaches undertaken
 Aims and Objectives
 Project Time Plan.
This chapter helps grasp as to how the context of constructing this project is set off.
1.2 Introduction:
The proposed system IMSS (Informatics Operations/Exam Management and Student e-

Support System) is a web-centric comprehensive system which will manage most of all
tasks being carried out in Informatics College.
Informatics College Kathmandu is a regular and one of the largest franchises of

Informatics Academy Singapore. Informatics College Kathmandu conducts various
Diploma, advanced diploma and Bachelors Degree program in association and
collaboration with Informatics Singapore, NCC Education UK and various universities
around the world. Informatics College Kathmandu was formally established in the year
1997 and is successfully running thereafter.
IMSS is intended to replace an already running Student Management System operational

in Informatics College currently. The proposed system will redefine the requirements and

functionalities of the current system and add up some new like student e-support and
advanced MISs, which has been a bigger demand in the current circumstances.
1.3 Motivational Factors:
The motivational factor of initializing this project is the speed of the growth of Informatics
College. The demand of the courses must cope with fluency and efficiency of management
procedures, which is not possible without an automated system. The proposed system
would not only ease the task and make them less time-consuming, but also apply the
concept of IT implementation in an IT College.
 Where did the project suggestion come from? What were the motivations?
The project suggestion obviously came from the complaints made by students, operational
staffs and Management members during the usage of problematic current system. The
procedures are complicated and least organized there, making the overall academic tasks
hectic and redundant. The growth in the number of students, the raise in popularity and
introduction of some new interesting courses has motivated the management in bigger
prospects, and an efficient and smart automated system would simply add a cherry on the
cake.
“Prakash, I am unable to open the software. This software is so irritating. Can we

have a more user friendly software?”
All these questions were aimed at me. This was one of the main reason and motivation for
me to initiate this project.

1.4 Problem Domain:
The system currently being operational in Informatics was developed as per the nearly half
a decade old requirements. The new context of academic, financial and students‟ growth
has resulted in some new requirements. The current system hasn‟t been able to address
those new requirements; hence, a new system has been a real need for Informatics. The
limitations of current system with regards to Exams, Operations and Student E-Support
have to be well addressed by the new system.
 Why the problems are so interesting? Why has management been

motivated to initiate this project?
As already told, the management is already very enthusiastic about solving the current
operational problem. The exciting growth of the college has motivated management to
solve the current problems in best possible ways. The only problem there in the college
has been operational and some of them being students related. But the problems if not
addressed properly can cause some drastic effect in the coming future as it would result
some unsatisfied graduates. The product of the college is really important for the
management as the word-of-mouth is the best advertisement ever, which would attract
other prospective students.
Some of the most remarkable problems in the current system are briefly listed below:
o Planning and managing classes:

 Any number of classes, up-to 4, can be taken by a student in a
trimester.
 Except mandatory modules, they can opt for the modules to study on
their own.
 Planning and management of the new classes is dependent on the
choice of specific group of students. The class-timings, lecturers‟
allocations and class rooms have to be managed accordingly.
 The allocated class can be cancelled and postponed by the students.
 There is no facility in the current system as to know the number of
classes a student is studying, the modules s/he has completed and
also the number of trimesters s/he is going to take in order to

graduate. The current manual tracking system is hard to manage and

report, as the number of students is exponentially in its way up.
o Student Management task is also problematic in the current system. The

current system lacks quick and efficient retrieval of the students‟ information
as and when needed. The student records can only be plainly listed.
o Managing Exams is also problematic in the current system. The exam

registration records of the students in the college has grown in considerable
numbers and the functionality of tracking, managing and reporting the exam
registrations hasn‟t been simplified in the current system. Some of the most
important features the current system lacks are:
 Generation of Internal Exam schedules, Registration summary
consisting of number of registered modules of each students, number
and total amount of collected Demand Drafts, a report of students not
registering for any examinations etc.
 Confirmed listings of exam registration to be sent to IA Singapore.
 Generation of Exam-Entry-Card for each registered students, used to
allow them to sit in the examinations. The Exam-Entry Card would
consist of the exam schedules, exam dates and times.
 Students‟ Result Slips and Progress Reports.
o While Student Support is so important for Informatics College, the current
system has no any features relating to it. Except for the attendance purposes,
Students cannot use the current system. All the tasks pertaining to the student
support such as submission of assignments, interaction with course facilitator
and lecturers, placing queries feedbacks and comments are all done manually
by the students. This is the reason why the student support has been found
quite unpopular in the college.
o The existing MySQL database has also caused little more problems in terms
of efficiency and transaction handling, as the number of records has risen
quite substantially.

1.5 Approaches Taken:
The following systematic approach will be adopted during the construction of the proposed
system:
 A detailed study will be carried out on the problem domain.

 The figured out problems will be verified.
 Various other college management systems will be taken into considerations and
a thorough study will be conducted
 Detailed requirements will be gathered and modeled.
 Based on the requirements, various prototypes will be designed-developed and
submitted to the management for a review/feedback.
1.6 Project Aims and Objectives:
1.6.1 Aim:
“To strengthen the management of operations, exams and student support of Informatics
College, thereby cultivating a high performance academic unit operating in a highly
systematic and student-friendly manner.”
1.6.2 Objectives:
1. To be able to manage Student Administration tasks with an optimum ease.

2. To facilitate the College Administration with a systematic process to operate.
3. To automate and abridge the Examination Conduction procedures.
4. To enhance the student support of the college so as to enable the students to
interact and make use of the system to its fullest.
5. To automate the student support in order to minimize the dependency on the staffs
for student support, by doing which, improvisation of the so-far unpopular student
support could be ensured and would make the students feel that their issues
haven‟t been turned deaf ears.
6. To facilitate staffs and College Administration by reducing the hassles making use
of the application there by reducing the consumption of time and effort. This would
help them contribute more time in strategic matters rather than in day-to-day
routine tasks.

1.6.3 Scope of the Project:
Scope is the boundary in which a system resides and operates on. Before the
initiation of the development of any project, scope of the project must be specified.
The Scope of the new system has been defined in the following major
perspectives:
Technical Definition:
Components Description
Manage Operations Will be developed to handle all the
academic operational tasks of
Informatics College.
Student e-Support Student Support tasks are carried out.
Manage Exams Will be developed to handle all the
examination related tasks in
Table 1.1 Technical Definition
1.7 Project Deliverables:
 System Documentation consisting of Project Proposal, Systems Requirements

Specification, Design Spec, Test Reports etc.
 A working model of the project consisting of:
 Data entry Modules
 Data transportation Modules
 Report Generation Modules
 Management/MIS Modules
 User Manual and Training Manual.

1.8 Outline of the Proposed System:
Fig 1.1: Outline of the proposed system
The above outlined new system would solve almost all problems being figured out in the
current system. The requirements would be redefined and they would be put into real
consideration while designing and developing the new system.
The most exaggerated problem in informatics i.e. Class Planning will be incorporated in
the new system much to the relief of the management.
Another problematic aspect i.e. Exams Management will also be fully automated in the
new system, with almost all procedures incorporated.
Student e-Support will also be included, eliminating the long discussed unpopular student
support problem.

1.9 Project Time Plan:
Fig 1.2: Gantt Chart (Project Timeline) for the project development
1.10 Summary of this Chapter:
This chapter gave the brief explanation as to how the idea of the project was initiated, the
motivation factors behind the project, the problem domain, approach to be adopted, some
basic aims and objectives of the proposed system, and finally the project time plans and
tenures.

Chapter 2 – Literature Review
2.1 Objectives of this Chapter:
The objective of the chapter is to provide a detailed literature review on the scope dealt
with. This chapter also intends to give a detailed background as to how and why the
proposed system is appropriate for the Informatics College.
2.2 Introduction:
Academic, administrative and day-to-day routine tasks are piled up as the growth of the
College and a simplified system is paramount. A College Management System is the
system which would carry out daily routine tasks as well as simplify the managerial tasks
with adequate ease and optimum efficiency. Automated systems are a basic necessity in
every place and domain in today‟s IT savvy world. Informatics College is certainly not an
exception.
2.3 Importance of ICT in Informatics College:
Informatics College Kathmandu is one of the leading IT Colleges in Kathmandu, with more
than 600 current students. Being so, it has its reputation on implementing something
extraordinary. Also, one of the main problems has been the student dissatisfaction over
the inefficiency of administration. Also, the problems have arisen in an adequate number
over the administrative tasks carried out daily.
ICT stands for Information and Communication Technology. ICT development has been
considered as one of the basic infrastructural development in any sectors. Nepal has been
constantly on her way up towards a holistic development of ICT, even in her governance.
ICT is considered as one of the most attractive, imperative and key areas, given enough
priority on which, can help in all-round development of the country. Informatics College
Kathmandu has been producing some quality software engineers, network engineers,

mobile engineers and various other IT professionals. Being an IT professional producing

institution, ICT implementation in the college itself is something of ultimate essence.
2.4 Introduction to Web Centric System and it’s suitability in Informatics

College:
Web-centric systems, also knows as web-based or web applications are the systems
developed and programmed using server-side scripts or similar programming language,
and which are supposed to be run in a web environment such as internet or intranet. The
popularity of web based systems has really taken rise in the recent times, due to various
advantages. Some of them include:
 They are easy to develop and implement, since most of all computer systems
have inbuilt web (internet) environment.
 They have common platform i.e. browsers, to run and operate on.
 Since most users are familiar with internet and surfing websites, web based
systems tend to be user friendly and easy to use.
 The feature of client-server architecture, makes web based systems strong,
secure and effective. Also, the implementation is easier than most other systems.
 Integration with external systems is also very easy and convenient.
2.5 Suitability of Web-based System in Informatics College:
The old system, which has been operational in Informatics College and which is being
used for almost a decade now, is also a web based system. The operators and other staffs
in Informatics College are quite familiar with the pros of web based systems. The client-
server architecture has to be implemented very vigorously, since the departments are in
wider geographical proximity and also the centralization is the main issue. The
management of Informatics College has also made quite clear that they may end up with a
crap, but that has to be web-based.

2.6 Various aspects and areas in which the proposed system would make its
effect in Informatics College:
 Overall Operations/Exams Management:
Operations in Informatics College include class management, lecturers management,

course management, Student management and exams matters. Since these areas have
already been automated, an update is all that is necessary.
 Student e-Support:
Student e-Support stands for a system which would dedicatedly carry out student support
related tasks. Students are the all that matter to a college, as in Informatics College, the
ultimate goal has been the student satisfaction. Unfortunately, the current manual system
in Informatics College hasn‟t contributed much towards achieving the goal. So an
automated system to handle that is an utmost necessity.
 Staffs/Lecturers E-Appraisal:
Introduction to Appraisal:
Appraisal is a decision method which includes the formulation and evaluation of

staffs in any organization. The ultimate goal of Appraisal is to motivate a staff to perform to
his utmost and ensure he isn‟t just bluffing around. An e-Appraisal is the process which
takes care of staff performances by formulating a decision making model and thereby
evaluating in point-based method to give managers a hawk-eye view over what has been
happening in the human resource department.
e-Appraisal of Staffs/ Lecturers in Informatics College:
There are currently around 30 operational staffs and around 60 active lecturers in
Informatics College. Their performance needs to kept track of, in order to ensure the high
standard of academic quality in Informatics College.

2.7 Selection of Development Tools and Justification:
The following development tools are proposed to be used for the development of the new
system:
 Object-Oriented PHP as the Front-end Programming Language

 Oracle as Back-end DBMS.
 Apache Web Server.
 PDO (PHP Data Objects) OCI to bridge PHP and Oracle.
PHP, parsed in apache web server, is chosen along with oracle as DBMS. PHP and
Oracle can be incorporated by various ways i.e. Oracle, OCI8, PDO, ODBC extension etc.
These extensions are written in C and linked with PHP binary. The most common
extension is OCI8. It is included in almost all versions of PHP. OCI8 is a open source
extension, constantly maintained and debugged by PHP community consisting of Oracle
as well. Following diagram illustrates the underlying model of PHP and oracle link:
Fig 2.1: PHP and Oracle client library link

Apache Web Server is chosen as a web-server to host the program files due to the
following reasons:
 Apache is a powerful, free and open source web server with strong PHP support.
 It is one of the most popular and most used web-server worldwide. More than 90%
web servers throughout the world uses Apache as web hosting server.
Object Oriented PHP is chosen mainly due to the following reasons:

 PHP (Hypertext Pre-Processor) is one of the most popular server side scripts.
 It is platform independent and most of the web-servers support it.
 Its availability is wide and free.
 It is open source and is hence customizable.
 It has its support for most DBMSs.
 Object Oriented Features in PHP is more standardized in the recent versions of
PHP. In PHP 5, the new Object Model introduced, has object handling features
completely rewritten allowing better performance.
Oracle (Oracle 10g Express Edition) is chosen as backend database due to the following
reasons:
 Oracle Databases are popular for its high scalability, reliability, efficiency and other
nifty features.
 The facility of sessions, user-oriented (schema) databases and enhanced
committing and roll backing options make Oracle one of the most safest and
reliable DBMS in the world.
 Oracle 10g Express Edition is a free edition of Oracle, with its distribution free and
most features of Oracle included.
PDO OCI driver is chosen to bridge PHP with Oracle because PDO is a lightweight, handy
and consistent extension of PHP used to access most of the databases.
 All one needs to supply is a database specific PDO driver in order to access
database whatsoever.
 Also, PDO uses a data-access abstraction layer, which facilitates the developers
to use same functions and methods to fetch data, regardless of whatever DBMS
used.
 PDO in recent versions of PHP has full Object Oriented Features intact.

Adobe Dreamweaver CS4 is chosen as an IDE for the development as:

 Dreamweaver is one of the most popular and easy tool for web development.
 Supports programming and debugging PHP in a more consistent manner.
 Has a design view, live view and code view so as to make it easy for the
programmer.
 Fully supports RAD (Rapid Application Development) with Drag-n-Drop
functionality.

2.8 Development Methodology to be used:
Waterfall methodology is proposed to be used as a development methodology. Waterfall

methodology consists of the following steps:
Fig 2.2: SDLC (Software Development Lifecycle)

SDLC has been proposed to be adopted due to the following reasons:
 Since, the requirements should only be reengineered, SDLC (waterfall) would

be safe to use.
 Waterfall method is easy-to-use and easy-to-adopt. As per the requirements of
this dissertation, Waterfall methodology would be better.
 It would be unfeasible and expensive to adopt other development
methodologies like Spiral and Prototyping approach.
2.9 Summary of this Chapter
This chapter gave the overview of the foundation of the development of the project. The
importance of ICT in Informatics College was discussed along with the importance,
benefits and suitability of web-centric software in the college. Various aspects in which the
system would affect the operations in Informatics College were also discussed. Finally the
development tools and methodology were analyzed and justified; the software
development methodology was also discussed and put forth.

Chapter 3 – Requirements Analysis
The main objective of this chapter is to figure out and capture unambiguous set of
requirements of the new system. This chapter hence puts forward the Requirements
Analysis being carried out in Informatics College in order to reengineer the current system.
The gathered requirements will be formulated in the SRS (System Requirements
Specification) document. In order to collect the data and requirements various fact-finding
techniques have been used, which will be discussed in appropriate details in this chapter.
The SRS document will consist of the list of requirements categorized under Functional,
Non-Functional and usability requirements.
3.2 Introduction:
Requirements Analysis is the most important and critical phase of any

development procedure, most dominantly in software engineering. Right after the
preliminary investigation/initial study, this step of software engineering takes place. It also
acts as a transition phase for another crucial step i.e. Systems Design where the actual
system shapes up. In order to be a system successful and effective, correct, unambiguous
and complete set of requirements must be generated which is not possible if this phase
isn‟t taken into serious considerations.
Analysis involves transforming a problem definition out of a problem
domain which is an unclear set of facts, data and even misconceptions, into a collective
and coherent statement of the system‟s requirements. Since it involves transformation,
which always is a difficult task, Software Engineers take this step as one of the most
critical and time consuming step.

3.3 Organizational Structure of Informatics College:
Before the initiation of Requirements Analysis via different fact finding techniques,
a detailed organizational structure of Informatics College should be taken into
consideration. The organizational structure will certainly help the analyst to grasp ideas as
to who needs to be asked, questioned and observed as a part of fact-finding. Most
members might be clear of their requirements, as they have been using the already-
described problematic current system. Following is the organizational structure of
Fig 3.1: Organizational Structure of Informatics College

3.4 Plan of Action for Requirements Analysis:
Since requirements Analysis is a critical task, the analyst has planned it

accordingly, giving adequate time and resources to it. In this section, the same plan is put
forth. The plan consists of the major fact finding techniques embraced and the set of
requirements generated out of it.
The requirements analysis phase started from 8th December 2009, when the
requirements gathering process was initiated. The process ran for 9 days and eventually
concluded on 17th of December the same year. For the requirements gathering purpose,
various fact finding techniques were used such as:
Objective Fact Finding Resources/Subjects Duration Category of Data

Technique
Grasp the overview of Background study -Website, 0.5 days Secondary Data
the organizational -Annual College Magazine,
structure and academic -Journals,
background of -Pamphlets and Brochures
Informatics College
Countercheck the roles Interview/Observ -Department Heads, 1 day-5 hrs Secondary Data
of operations/exams ation/Questionnai -User Roles in the current
departments as they res system ISMS.
were in the current
system.
Analyze how the classes Interview/Docume -Principal 1 day Primary Data
are planned manually nt Sampling - Coordinator
and how the students are - Existing Manual Class-
allocated classes in a Planning Registers
term.
Get the information as to Interview/Observa -Principal 1 day Primary Data
how lecturers are tion -Coordinator
assigned to a class.
Figure out the most Observation -Operations staffs 2 hrs Primary Data
sought after information
of a student.
Analyze the examination Observation/Doc -Board of Examiners 2days 1 hour Primary Data
conduction procedure uments Sampling -Exam Manager and each
and counter check them operational staffs

with the current system.

Analyze the Questionnaire -Students 2 days 2 Primary Data
requirements of students hours each
and figure out their
involvements.
Establish additional Interview -All Operational staffs. 1 day Primary Data
requirements if any
whatsoever.
Examine other scopes Interview -All Operational staffs 1 hr Tertiary Data
and constraints that the
new system can take
care of.
Finding out the Interview/Survey -All Operational Staffs 1 day Tertiary Data
positive/negative impact -Board of Directors, Managers
that the new system may
cause.
Table 3.1 Requirements Collection Plan Table
P.S.:
The actual time span of the above mentioned Plan Table is 11 days, 2 days more than what
planned. The extra 2 days were managed out form the time planned for the design, as the
analysis and design could go shoulder to shoulder.

3.5 Fact-Finding Techniques Embraced:
Various Fact-Finding Techniques were applied to collect data and information for
requirements spec.
While using various fact finding techniques, various ethical considerations were made such
as:
 Made sure that Hawthorne effect were highly tried to minimize during the observation
of the staffs‟ activities:
 Made sure that no personal questions were asked/investigated.
 Made sure that no staffs were compelled to answer the questions against their
personal liking.
 Made sure that the information given by them, were taken care with total confidentiality
and sensitivity.
 Made sure that all the information collected were taken into serious consideration and
later reported.
Some of the most vigorously used fact finding techniques are listed, explained and
reported below:
3.5.1 Background Study:
Background study was done in various areas in order to get fundamental ideas about the
project. Mostly, the current system was studied and various assumptions were also
generated. The current system currently operational in Informatics College was a good
source, studying the background of which, a number of good and clear new requirements
were figured out.

Fig 3.2: Current system in which background study was done

3.5.2 Interviews:
Interviews were also conducted on several occasions with a number of organizational

members of the College so as to grasp information pertaining to the problems being
figured out in the current system and what they require in the new system.
Two kinds of questions were asked:

o Quantitative Questions
o Qualitative Questions
Quantitative Questions are the questions which require definite answers. Such questions
are generally objective and the answerer is just required to select an option out of multiple.
While there were some interviews conducted based on quantitative questions, majority of
them were that of qualitative questions as answerers prefer descriptive answers.
Quantitative questions were asked in another fact-finding technique i.e. Questionnaires.
Qualitative questions mostly expect descriptive answers, the sort of questions most
appropriate for Interviews.
After the completion of a number of interview sessions, reports based on the answers of
the interviewee were drafted. Following is an interview report as of the interview conducted
against CEO/Chairman of Informatics College, Mr. Sulav Budhathoki.
Other interview reports are listed in Appendix E.

Table 3.2 Sample Interview Report

Name: Mr. Sulav Budhathoki Date of Interview: 9th December 2009
Designation: Chairman/CEO Place: Informatics Premises-CEO Cabin
Q 1. Why would you like to have a new system replacing the current system?
Ans:- Informatics College has advanced in leaps and bounds in the recent years in terms
of academics and number of students. As the number of students is constantly on its way
up, the academic overheads and operational tasks have also increased, leaving us starved
as the current system hasn’t been too helpful. That’s why I sensed it is high time we need
an update.
Q 2. Do you want to completely replace the current system or just some parts of it?
Ans:- For the time being, I have recommended to replace just certain parts of the current
system. Some modules of existing system like library management and attendance
management seem to be fine and working. Successful implementation of the proposed
system would ensure the replacement of those modules as well, in the near future.
Q 4. How much budget has been allocated for the proposed system by you?
Ans:- Well, I haven’t fixed it for the time being. As the proposed system has been
proposed for the fulfillment of an academic project, the cost is certainly marginal. All
other extra costs, apart from the core development, will be covered by the college.

3.5.3 Questionnaire:
Questionnaires are one of the fact-finding techniques used to gather information from
mass. As the main personnel have already been interviewed and important data have
already been collected. Two different types of questionnaires were created and distributed
amongst the different level of staffs:
The format of those two different types questionnaires are given below:
Table 3.3 Questionnaire Sample 1
Questionnaire to assess the existing ISMS

(Please tick  the appropriate, information revealed would be kept confidential)
Name -.......................................................................................................................................................................
Position -..................................................................................................................................................................
Department - Exam  Operations  Student support 
In the current ISMS software that you have been using in Informatics, What are your opinions in terms of:
Usability (User friendliness):

- Very Satisfied  Satisfied  Dissatisfied  Very Dissatisfied 
Functionalities (How often do you find the current ISMS helpful in your job):
- Very helpful  Helpful  OK  Hectic 
How often do you use this ISMS system:

- Very much  Used to  Not used to  want to get rid of
Do you need a replacement to the current ISMS:

- Very much  high time  yes  its working just about fine
Overall satisfaction:
- Very Satisfied  Satisfied  Dissatisfied  Very Dissatisfied 

Your Comments:
 What are your suggestions for a replacement for the current ISMS?
 _____________________________________________________________________
 _____________________________________________________________________
 _____________________________________________________________________
 _____________________________________________________________________
 _____________________________________________________________________
_________________________
Your Signature
Thank you. We appreciate you offering your valuable time and co-operation.

Table 3.2 Questionnaire Sample 2
PLEASE FILL IN THE FOLLOWING IN BLOCK LETTERS:


Your Name : ________________________________________________
 Your Designation : ________________________________________________
As you may have come to know that we are commencing on new software replacing the
problematic current ISMS system. The proliferation of the new software requires your invaluable
help and suggestion in order to make it a success and easy for you in future. You are therefore
requested to manage your time and give us the following information. The information you
provide herein will be kept and dealt with high confidentiality.
 Do you think a new system replacing the current ISMS is necessary? Will
you accept it?
Yes No
 Why?

Please write in the box below, your day-to-day routine tasks:
 _____________________________________________________________________
 _____________________________________________________________________
 _____________________________________________________________________
 _____________________________________________________________________
 _____________________________________________________________________
 _____________________________________________________________________
 _____________________________________________________________________
 _____________________________________________________________________
 _____________________________________________________________________
What are your suggestions pertaining to your day-to-day tasks? What are the things
you want to add and/or change?
 _____________________________________________________________________
 _____________________________________________________________________
 _____________________________________________________________________
 _____________________________________________________________________
 _____________________________________________________________________
 _____________________________________________________________________
 _____________________________________________________________________
 _____________________________________________________________________
 _____________________________________________________________________
_________________________
Your Signature
 Thank you. We appreciate you offering your valuable time and co-operation.

The samples of the questionnaires filled by the employees are included in APPENDIX F,
attached to this document.
Outcome of the Questionnaire:
The outcome of the questionnaires being distributed and collected is depicted in the
following diagrams:
As per the answers of questionnaires collected from all the staffs, a summary was
generated in terms of various indicators.
For instance, with regards to the acceptance of the old ISMS system in Informatics, three
indicators were used:
 Workable:
Means, the current ISMS is fine and workable, no need of new system replacing
the same.
 Acceptable:
Means, the current ISMS is OK and acceptable, the new upgraded and
improved system would be great.
 Useless:
Means, the current ISMS is a trash and a new system replacing it is a
paramount.

Fig 3.3 Old ISMS Acceptability Graph
Useless
Exams
Acceptable
Operations
Workable
0 20 40 60
Workable Acceptable Useless

Exams 20 50 20
Operations 10 50 40
As per this finding, majority of staffs in Informatics has been taking the current ISMS as
acceptable, with a significant number of them pressing for a new one. The proliferation of
new system, hence, was considered necessary.
Fig 3.4 New System Necessity Graph
Utterly Necessary
Would be great
No need
Waste of time
and resource

The above depiction also tells us that the proliferation of new system would be
beneficiary for the operations and overall whatnots of Informatics College.

3.5.4 Observation:
It is another important fact finding technique used to analyze the requirements for the new
system. Observation was made in various occasions during the operations. Observation
was only done in order to check and verify the validity of the routine tasks/operations and if
they were as it is in the current ISMS system.
As it was observed, the day-to-day activities currently done by the existing ISMS
system and other manual tasks are depicted in the following Use Case Diagram and
Activity Diagram:
Fig 3.5 Use case Diagram for

current system

 Use Case Description:
Use Case Description

Admit Student The procedure in which a new student is
admitted to the college.
Assign Course The procedure in which the new student is
enrolled in a course.
Assign Class The procedure in which the new student is
registered for a class in the particular trimester.
Other Academic Operations Other Academic tasks carried out upon a
student, such as assignment collection,
punctuality/attendance management, SPR
(Student Performance Review) Report
generations etc.
Conduct Examination This use case consists of all the examination
related tasks such as Exam Registration,
Confirmed Listing generation, Entry Card
Generation, Report Card Generation etc.
Notify The procedure in which students and staffs of
Informatics College is notified on a number of
occasions.
Provide Feedback The procedure in which students provide
feedback pertaining to various issues.
Submit Assignment The procedure in which students submit their
assignment and other academic materials to the
administration or the respective lecturers.

 Actor Description:
Actor Description
Operations Dept. All the working staffs related to Operations
Dept. Operations Dept is primarily responsible
for Academic Administrations. Operations Dept
is headed by the Principal.
Exams Dept. All the working staffs related to Exams Dept.
Exams Dept look after all the examinations held
in the college.
Students As the name suggest.

Fig 3.6 Activity Diagram for the

Current ISMS
3.6 Qualitative Data Analysis:
3.6.1 Operations Management:
Overview of the current system:

When a student is first admitted in the college, s/he is first assigned to a course.
Then s/he is assigned a class that has to be planned and managed. For the class
management, a team of administrative staff plans the number of classes to be undertaken,
the lecturer to be assigned and the module of the corresponding class. Besides Operations
is also responsible of attendance reports, progress reports, results slip and other reports
generation.
Problem:
As already been described, a number of problems still persist. The class management
and planning has been the most problematic by far. As the students have full right to
postpone, cancel or skip any classes they are to undertake, a class can be dismissed at any
instance and can also be postponed. As the student wishes to shift classes, the
management has to commit considerable amount of time and extra effort managing those all.
3.6.2 Exam Management:

As the student continues his/her studies for one full year, s/he has to register for
the respective examinations. Exam Fees are payable to IA Singapore and has to be done
that with the help of bank drafts. The manually verified registrations are summarized in a
prefixed Confirmed Listing Report and sent to Singapore. An Exam Entry Card is issued to
each registered students and the exams are taken. Later the generated result slips from IA
Singapore are distributed to the students.
Problem:
There is also considerable number of problems in the exams management. As the
number of students have grown par limit, it is difficult to generate confirmed listing report
manually one by one. Also, manual generation of Exam Entry Card is tedious and time
consuming. There is no any feature of planning seats for the exams conduction, which would
be great if incorporated in the new system.

3.6.3 Student Support:

Student Support includes different services provided by the college that the
student is entitled for. Printing of their assignments, distribution of Case studies papers, other
academic materials, Collection of Assignments, facilitating their studies, making sure that
their voices are heard and collecting their feedbacks etc. are some regular tasks there to be
done with regards to Student Support.
Problem:
As there is no any features pertaining to student support in the current ISMS, all the
problematic procedures need to be automated.

3.7 Requirements List Table:
Following Requirements List Table is generated so as to summarize the overall findings of the
requirements analysis.
No. Requirements Use Case(s)

1 To plan new classes for each new trimesters. Plan Class
2 To manage Students and their related academic operations. Adding, ID Manage Student
Generation, modifying, listing, viewing, searching of the records of students
shall be done.
3 To manage the course and assign students in it. Changing, modifying, Manage Course
promoting, demoting courses etc should be included.
4 To manage exams, add/update/delete exam registrations made in a Manage Exams
particular trimester, generate confirmed listing, generate registration
summaries, generate exam entry card, Exam seat plans etc should be
incorporated.
5 To carry out student support related tasks such as Discussion Forum, Online Support Students
Assignment Submission, Academic Corners, Email Notification etc.

3.8 General Requirements (Non-functional):
 The whole new system should be web-based with interfaces having both offline and
online capabilities.
 A separate Control Centre should be incorporated in the system. The Control
Mechanism should be able to create user roles, impose access rights and limit/extend
user privileges.
 The new system should embrace client-server based architecture.
 The reports generated by the system should be graphical, tabular, indicator-driven and
exportable to different popular formats like excel sheets.
 The navigational consistency should be maintained; not more than 3 clicks to be made
by the user in order to reach the destination.
 The response times of the system should be optimum. The new system shouldn‟t
consume much bandwidth even though most of the features are running offline. In
order to achieve this, optimum usage of AJAX/XML should be enforced.
3.9 Usability Requirements:
As the current ISMS system had quite a number of usability issues, new system replacing
it, is expected to have quite a few usability optimization. Almost all the expected users of
the new system have a great deal of experience using current system, hence the usability
requirements of the new system are not that sophisticated.
Some of the most important usability requirements for the proposed system are:
 As most exaggerated, the new system should be literally “User Friendly”. No. of
clicks required to reach a destination must be extremely minimal (not more than
3).

 Most sought after and most performed tasks of a particular user must be
incorporated in the front-end interface of that user.
 The interface must adapt with the most frequently done tasks of a user. A user
must not feel difficult to find the modules which he frequently has to deal with.
 The design must be as much graphical as possible. One of the most complained
drawback of current ISMS is that the most interface is textual, giving the command
line interface feeling to the user.
 As it is web-based, the web-page refreshes must be as less as possible.
3.10 Summary of this chapter:
In this chapter, System Requirements Specification (SRS) has been tried to summarize
and present. First, all the Fact-Finding Techniques used in order to gather requirements and
information from various resources are explained. The detailed reports as of the outcome of such
techniques are also formulated. Later a System Requirements List is presented; extra
requirements (Non Functional Requirements and Usability Requirements) are also presented. A
Use Case Diagram and an Activity Diagram is also used, in order to model the current system.

Chapter 4 – Systems Design
The main objective of this chapter is to design and model the new proposed
system. All the requirements being pointed out in the SRS and formulated in the previous
chapter are to be designed with the best possible way. The following contents will disclose
various object oriented methodologies used to design the new system.
4.2. Design Overview:
Object Oriented Methodology is used to design the new system. This chapter will
consist of a list of different UML diagrams. UML stands for Unified Modeling Language,
which is one of the most popular designing methodologies ever used.
As the first step, a use case diagram is designed so as to model the procedures of new
system. The whole system is broken down into three major modules in order to ease and
simplify the use case diagram. Following are the modules.
1. Manage Operations (Academics)
2. Manage Examinations
3. Student E-Support

4.2.1 Manage Operations
Fig 4.1 Use Case Diagram – Manage Operations

Detailed Use Case Description for Manage Operations:

Apply New Prospective students apply for the admission in the
college.
Enroll New Student The Academic Staff enrolls the new student if s/he satisfies all
the entry criterions. All the required information of the student
are tracked and stored. A new StudentId is also generated.
Administer Courses Add/Modify Courses being undertaken in the college
Assign Courses Assign new Course to each new student and those who
graduate and proceed into a new course.
Administer Academics Track each student‟s performance, provide interface to the
existing Attendance System, track the change of their
migrations etc.
Plan Class Track the students who are remained to undertake a particular
module and plan classes for them with regards to the number of
such students, class room and lecturer. Group student as per
their yet-to-undertake modules.
Assign Lecturer Assign a lecturer to a new planned class.
Administer Lecturer Add/Modify/Delete the lecturer‟s information
Administer running classes Update/Delete currently running classes.
Table 4.1: Detailed Use Case Description for Manage Operations

4.2.2 Manage Exams
Fig 4.2 Use Case Diagram – Manage Examinations

Detailed Use Case Description for Manage Examinations:

Fill up Registration Form The student fill up a registration form specifying the modules
they want to be examined and the registration status i.e.
fresh/reunit etc. Draft Details (Exams fees Payment Demand
Draft payable to IA Singapore) are also to be included.
Generate/Validate As each exam registration are tracked and stored into the
Confirmed Listing system, the academic staff will now generate the confirmed
listing report which consists of the exam registration details of
all the registered students. Later the report is validated in order
to be sent to Singapore.
Schedule Internal Plan, manage and record Internal Examination schedule
Examinations
Generate Exam Entry Card Based on the exam registration records and confirmed listing,
exam entry card shall be generated for each registered
students.
Generate Other Reports Other reports such as reports pertaining to Unregistered
Student of that particular term, Registration Summary consisting
of total monetary transaction, total registered students in a
particular module, total number of exam registrations etc. are
also to be generated.
Display/Distribute Results Generate Result slip as and when the results are disclosed by
Slip IA Singapore to the students.
Table 4.2: Detailed Use Case Description for Manage Exams

4.2.3 Student E-Support
Fig 4.3 Use Case Diagram – Student E-Support

Detailed Use Case Description for Student E-Support:

Interact with Facilitators Interact with facilitators and ask questions to them pertaining to
their academics. Facilitators (Lecturers) also interact with
students using same use case.
Interact with fellow Students shall interact with each other for various purposes.
classmates
Submit Assignments Students shall now submit their assignments, case studies
paper and all other academic write-ups and reports online in the
proposed system. The system will track their submissions and
forward to the respective stakeholders.
Download/Upload Course Students shall download course materials such as assignment
Materials question papers, lecturer notes etc. using the proposed system.
Provide Student shall now provide feedbacks/complaints/grievances to
Feedback/Grievances the targeted administrative members directly using the
proposed system.
View Attendance Students shall now be able to view different reports of theirs
Report/Progress such as attendance reports, progress reports, performance
Report/Result Slips reports and result slips, using the proposed system.
Issue/Broadcast Different notifications and information to be broadcasted to
Notifications all/groups of students shall be done by the proposed system.
Email notifications will be given priority for the time being.
Table 4.1: Detailed Use Case Description for Student E-Support.

4.3 System Module Design:
In this section, detailed system modules are designed using different UML diagrams.
Activity Diagrams and Sequence Diagrams are given more priority as they can depict
procedures more efficiently and accurately.
Basically, the system is broken down into three major Modules, whose basic Use Case
Diagrams have already been presented.
 Operations Management
 Exams Management
 Student E-Support
4.3.1 Activity Diagrams:
Following Sections will display Sub Activity Diagrams for various important sub-
modules with regards to above-mentioned three major Modules.
 Operations Management:
 Plan Class
 Promote/Update Course
 Exams Management:
 Exam Registration
 Seat Planning
 Confirmed Listing Generation
 Student E-Support:
 Notification
 Interact with facilitators
 Submit Assignments

Fig 4.4: Sub Activity Diagram of Operations Management: PLAN CLASS

Fig 4.5 Sub Activity Diagram of Operations Management: Modify/Update Course

Fig 4.6 Sub Activity Diagram of Exams Management: Exam Registration

Fig 4.7 Sub Activity Diagram of Exams Management: Seat Planning

Fig 4.8 Sub Activity Diagram of Exams Management: Confirmed Listing Generation

Fig 4.8 Sub Activity Diagram of Student E-Support: Notification

Fig 4.9 Sub Activity Diagram of Student E-Support: Submit Assignment

Fig 4.10 Sub Activity Diagram of Student E-Support: Notification

Fig 4.11 Sub Activity Diagram of Student E-Support: Interact with Lecturers/Facilitators

4.3.2 System Static Structure (Class Diagram):
As a part of the Systems Architecture Design, Class Diagram is to be modeled so as to

identify classes/objects and to find out relationship between the classes. The Class Diagram
(System Static Structure) modeled would, hence, act as a high level basis for the system
architecture with its significant low-level basis in the static structure of the data.
In order to model class diagram, a Textual Analysis was carried out on the Requirements
Specification produced in the Chapter 1 of this very documentation.
Textual Analysis:
Identified possible Classes, Attributes, and Methods:
Nouns:  Notification
 Informatics  Assignment
 Exam  Staff
 Module  Draft
 Class  Bank
 Student
 Operational Staff
 Exam Staff Verbs:
 Lecturer
 Principal  Register
 CEO  Enroll
 MD  Pay
 ClassTiming  Take Class
 ClassRoom  Submit Assignment
 Examination  Interact with lecturer
 Examination Schedule  Collect Assignment
 Coursework  Mark Assignment
 ExamDate Etc.
 Course

Based on the above Textual Analysis, Following Class Diagram (System Static Structure) was
created:
Fig 4.12 : Class Diagram

4.3.3 Sequence Diagrams:
The following sections will display Sequence Diagrams as of the above sub-activity
Diagrams. Sequence Diagrams will help clarify the actual sequence of processes going to
be embraced in the new system.
Fig 4.13Sequence Diagram for Operations Management: PLAN CLASS

Fig 4.14 Sequence Diagram for Operations Management: Student Course Management

Fig 4.15 Sequence Diagram for Exams Management: Exam Registration

Fig 4.16 Sequence Diagram for Exams Management: Seat Plan

Fig 4.17 Sequence Diagram for Exams Management: Generate Confirmed Listing

Sequence Diagrams pertaining to Students E-Support are listing in Appendix F of this

documentation.

4.4 Data Design:
4.4.1 Design Overview:
Data design is another most important consideration to be made. Data design

involves the design and management of the all the kinds of data going to be used,
manipulated and stored by the program.
As the project stands as a reengineering venture, data design is rather simplified.

The database, being currently used by the old system, is to be migrated and
optimized. Following is the ER Diagrams that of New System
(Optimized/Modified).
The schema design of the database being used currently is included in Appendix
G. The whole design for the proposed system was based on the same schema
design. Unnecessary Entities were removed and the others were optimized based
on the requirements analysis done.
Following is the detailed Entity Relationship Diagram (E-R Diagram) put forth for
the New Proposed system:

Fig 4.18 Entity Relationship Design for New System

4.5 Architecture Design
Architecture Design of the proposed system is done so as to design and manage the
hardware peripherals, network and resources sharing.
The entire project (new system) is web-based, hence a central web-server,
configured with Apache Web Server System, will host it. The central web server shall also
host the oracle database, for which Oracle 10g Express Edition is installed into it.
Separate collision domains are created for each department i.e. Operations
Department, Exams Department, Student Support Services and Top Mgmt. So is done
with the help of a router. The router connects to the internet with a firewall. The students
who are to use the system, does so with the help of internet. Hence the Student Panel will
be kept online. Rest of all the modules of the proposed system will be kept and to be used
offline.
Following is the architecture design diagram which gives the overview as to how
the hardware and resources are shared.
Fig 4.18 Entity Relationship

72 Prakash Shrestha | Hemis: 472124Design for New System
4.6 Interface Design:
Interface Design is another of the most crucial consideration to be made as it is the front-
end design. The most problematic part of the current system (ISMS) was its usability issue.
The design of the proposed system is hence expected to be put forward so as to address
all the issues pertaining to the user-friendliness.
The new Interface Design is completely based upon the usability requirements given in the
previous Chapter-Requirements Analysis.
The new Interface Design is more focused on the user rather than the functionality. While
the object oriented development will aid a lot in maintaining the user approach, the
interface front-end design is also proposed to be done in the same way. The users i.e.
Informatics Staffs and Students should find the front-end interface extremely:
 Simple
 Less time Consuming (Not more than 3 clicks to be made for any tasks to be
done)
 Functionalities-easy to find.
 Artificially intelligent to some extent (most used icons, functionalities must appear
in the front) etc.
In order to verify the usability requirements, some wireframe prototypes of the front-
end user interface were designed which are as follows:

Fig 4.19 Login Screen Interface

 A spacious dashboard would be designed, which would contain the links to almost all the
activities performed by a specific Staff of a specific department.
 A Box which would contain all the frequent (most done) activities by the staff would also be
incorporated.
Fig 4.19 Dashboard

 Ajax powered Modal Boxes would be used for data-entry purposes in order to reduce the
number of clicks and page refreshes.
 The Modal Boxes would also enhance the overall design and look of the front-end, with its
efficiency and effectiveness in terms of functionalities intact.
Fig 4.20 Modal Boxes For easy-to-use data entry Forms

4.7 Summary of this Chapter
This Chapter dealt with the overall system design of the proposed system. All the
front-end and back-end processes were designed so as to make it easy for the
development phase. The design specifications put forth were submitted to the
management. The following chapter will deal with testing once the development
is completed thereafter.

Chapter 5 – Systems Testing and Implementation
5.1. Objectives of this Chapter:
The main objective of this chapter is to test and implement the new system. The
new system has already been developed based on the Design Specification, but is
yet to be tested for any problems. This chapter hence, aims to introduce different
testing strategies so as to ensure the new system to be fully operational.
5.2. Testing Overview:
All the information systems inevitably need to be tested thoroughly for any
programming bugs and errors. As the proposed system has already been
developed, it should now be tested to be deemed acceptable and implantable in
Informatics College. However, it is taken with full awareness that no system can
be practically 100% error free. The bugs encountered whatsoever during the
operation of the system would be countered and rectified against, as and when
pinpointed.
Various testing methods/techniques were used and adopted in order to test the
developed new system. Some of them are:
 Unit Testing
 Dataflow Testing
 Boundary Analysis
 Integration testing
 Condition/Loop Testing
 Data Testing
 Equivalence Testing etc

However, the detailed tests like condition/loop test; Unit Tests etc. were not
preferably adopted as it would eat up considerable amount of time.

5.3. Testing Strategy:
With regards to the Testing Strategy, a detailed Test Plan is created, consisting of
a number of Test Cases. Those Test Cases are to be materialized realistically and
a detailed Test Log consisting of the results that of each Test Cases is also to be
documented. Following sections disclose such Test Plan, Test Cases and Test
Logs.
P.S
Separate lists of Test Plans are created for three different types of end-users i.e.
 Operational Staff
 Exams Staff
 Students
5.4. Test Plan:
Following is the Test Plan formulated for the comprehensive Testing of the new
developed system. As mentioned somewhere above, the test plan shall consist of
the Test Cases with regards to the expected End Users and Use Cases pertaining
to them. Following is the table which gives an overview as to how the Test Cases
are to be organized:

5.4.1. Use Case Test Plan:
Table 5.1 Test Plan

Actor Test case Use Case Objective
Operational/Academic 1 Enroll New Student To Check if the new student can be
Staff registered or not and if so, new
StudentId is generated or not.
2 Promote/Update To Check if the course of a particular
Course student can be promoted/updated.
3 Administer To Check if the operation Term Break
Academics is applicable or not.
4 Plan Class To Check if the students can be

grouped and assigned a class or not
5 Administer Running To Check if any of the running
Classes classes can be terminated or not.
Exams Staff 6 Generate Validate To Check if all the registered students
Confirmed Listing along with their registered modules
are displayed in the confirmed listing.
7 Generate Exam To Check if all the registered students

Entry Card are generated an exam entry card or
not.
8 Progress Report To check if clicking on the Generate
Generation Progress Report link, a detailed
progress report of a student is
generated or not.
9 Fill up Registration To Check if only the yet-to-study
Form modules get appeared while
registering them for a student’s Exam
Registration.
10 Fill up Registration To Check if only the draft created in
Form the current term get appeared while
Exam Registration.
11 Schedule Internal To check if the error message is
Exam displayed if two exams commencing
on same time are put in the same
time.

Student 12 Interact with To check if the messages by the

Facilitators students are sent or not.
13 Download/upload To find out whether the share

Course Materials resources/Course Materials can be
downloaded or not.
14 Provide Feedback To check if the entered
Feedback/grievances were received
or not.
Table 5.2 Validation Test Plan
5.4.2. Validation Test Plan:
Table 5.2 Validation Test Plan
Input Key Test Objective

Case
Login Information 1 To check if the incorrect login
information leads to an error
message display or not.
Auto Complete 2 To check if the auto complete text
boxes display a list of suggested
values or not.
Validating Input 3 To check if the invalid data entry
leads to the generation of error
message or not.

5.5. Test Log:
5.5.1. Use Case Test Log
5.5.1.1. Actor: Operational Staff
Test Case: 1
Objective: To Check if the new student can be registered or not and if so, new
StudentId is generated or not.
Test Data: A new student‟s name and other details
Expected Test A StudentId should be generated and a success message should get
Result displayed
Actual Test StudentId was generated and Success Message was also displayed.
Result:
Conclusion: Successfully done
Test Case: 2
Objective: To Check if the course of a particular student can be

promoted/updated.
Test Data: An existing Student‟s information and a click to the update button
Expected Test The Current Course Status of the student should be displayed upon
Result the click on the update, the course should be updated and get
displayed.
Actual Test Course was updated.
Result:

Test Case: 3
Objective: To Check if the operation- Term Break is applicable or not.
Test Data: An existing Student‟s information and a click to the Term Break
button
Expected Test The Current Course Status of the student should be set to halt. The
Result student must also be removed from all the running classes and
temporarily be hidden from the Running Student list
Actual Test Course status was halted, removed from the classes and hidden from
Result: the active student list.
Test Case: 4
Objective: To Check if the students can be grouped and assigned a class or not
Test Data: Selection of a module
Expected Test The students who are yet to undertake the entered module should be
Result listed and grouped in equal proportions. The group should be able to
assign an already created class.
Actual Test The students were grouped in equal proportions and listed
Result: successfully. They could also be assigned a class

Test Case: 5
Objective: To Check if any of the running classes can be terminated or not.

Test Data: A Running Class
Expected Test The Class‟s status should be set to „t‟ and should disappear from the
Result Running Classes list.
Actual Test The Class Info disappeared from the list
Result:
5.5.1.2. Actor: Exam Staff
Test Case: 6
Objective: To Check if all the registered students along with their registered
modules are displayed in the confirmed listing.
Test Data: A Course selection

Expected Test All the exam registration pertaining to the selected course must be
Result displayed in the specified format.
Actual Test The report was displayed
Result:

Test Case: 7
Objective: To Check if all the registered students are generated an exam entry
card or not.
Test Data: A Course selection
Expected Test All the registered students studying the selected course must be
Result generated a exam entry card
Actual Test Each Student was generated an exam entry card.
Result:
Test Case: 8
Objective: To check if clicking on the Generate Progress Report link, a detailed

progress report of a student is generated or not.
Test Data: A Student Selection
Expected Test Progress Report of the selected student should be generated,
Result containing the grades s/he had scored and his/her class statuses.
Actual Test Progress report for the student was generated
Result:

Test Case: 9
Objective: To Check if only the yet-to-study modules get appeared while

registering them for a student‟s Exam Registration.
Test Data: A Student and course Selection
Expected Test Only the modules that of the selected course and that the selected
Result student is yet to study must be listed in the form..
Actual Test Only the yet-to-study modules were listed
Result:
Test Case: 10
Objective: To Check if only the draft created in the current term get appeared
while Exam Registration.
Test Data: An exam registration
Expected Test Only the drafts created in the current term must be listed
Result
Actual Test Only the drafts created in the current term were listed.
Result:

Test Case: 11
Objective: To check if the error message is displayed if two exams commencing

on same time are put in the same time.
Test Data: An already entered exam info
Expected Test An error message specifying the room/module/exam timing conflict
Result must be displayed.
Actual Test The error message was displayed.
Result:
5.5.1.3. Actor: Student
Test Case: 12
Objective: To check if the messages by the students are sent or not.

Test Data: A message as of a student
Expected Test The message must be stored in the database and a success
Result message must be displayed
Actual Test The message was stored in the database and a success message
Result: was also displayed.

Test Case: 13
Objective: To find out whether the share resources/Course Materials can be

downloaded or not.
Test Data: A case study uploaded a lecturer
Expected Test The case study must be downloadable by the students dealt by the
Result lecturer.
Actual Test The case study document was downloaded upon verification.
Result:
Test Case: 14
Objective: To check if the entered Feedback/grievances were received or not.

Test Data: A feedback by a student
Expected Test The feedback must be stored in the database and downloadable
Result whenever the staff logs in.
Actual Test The feedback was stored and downloadable.
Result:

5.5.2. Validation Test Log:
Test Case: 1
Objective: To check if the incorrect login information leads to an error

message display or not.
Test Data: Incorrect Username/password
Expected Test Result An error message must be displayed.
Actual Test Result: An error message was displayed

Test Case: 2
Objective: To check if the auto complete text boxes display a list of

suggested values or not.
Test Data: Initials of Id i.e. “1801..”
Expected Test Result A list of suggestive Ids must be listed automatically.
Actual Test Result: The list was displayed

Test Case: 3
Objective: To check if the invalid data entry leads to the generation

of error message or not.
Test Data: Invalid Class Information “abcd..”
Expected Test Result An error message should be displayed by the side of
the textbox where the wrong data has been input.
Actual Test Result: The list was displayed

5.6. Test Results:
5.6.1. Test Result for Use Case Test Plan:
Test Case Objective Status

1 To Check if the new student can be registered or not Successful
and if so, new StudentId is generated or not.
2 To Check if the course of a particular student can be Successful
promoted/updated.
3 To Check if the operation Term Break is applicable or Successful
not.
4 To Check if the students can be grouped and assigned Successful

a class or not
5 To Check if any of the running classes can be Successful
terminated or not.
6 To Check if all the registered students along with their Successful
registered modules are displayed in the confirmed
listing.
7 To Check if all the registered students are generated Successful
an exam entry card or not.
8 To check if clicking on the Generate Progress Report Successful
link, a detailed progress report of a student is
generated or not.
9 To Check if only the yet-to-study modules get appeared Successful
while registering them for a student‟s Exam
Registration.
10 To Check if only the draft created in the current term Successful
get appeared while Exam Registration.
11 To check if the error message is displayed if two exams Successful
commencing on same time are put in the same time.
12 To check if the messages by the students are sent or Successful
not.
13 To find out whether the share resources/Course Successful
Materials can be downloaded or not.
14 To check if the entered Feedback/grievances were Successful
received or not.

5.6.2. Validation Test Result:
Test Case Objective Status

1 To check if the incorrect login information leads to an Successful
error message display or not.
2 To check if the auto complete text boxes display a Successful
list of suggested values or not.
5.7. Implementation Plan:
As the developed system has been thoroughly tested for any bugs and errors and as they
have been rectified as encountered, now it is there to be implemented. The implementation
plan is a bit important as the current old system (ISMS) has there been operational for so
long and without which the day-to-day operations are seriously hampered.
Following is the Implementation Plan poised after a series of serious talks and
consultations with the management of Informatics College.
Fig 5.1 Systems Implementation Plan

At the end of the Implementation Plan, the Developed System will be deployed as
specified in the Architectural Design Section, introduced and documented in Chapter 4
of this very documentation.
5.7.1. Required Tools for Implementation:
Following are the tools required for implementation of this newly developed project:
5.7.1.1. Development Language Adopted:
 PHP
Adopted because:
 Of its popularity.
 Of its rich Object-Oriented Features.
 Of its simplicity and extreme popularity.
 The old system is also developed in PHP; hence the migration
and optimization would be easy.
5.7.1.2. Development Tool Adopted:
 Adobe Dreamweaver CS3
Adopted because:
 Of its brilliant user-friendliness.
 Supports MVC (Model, View and Controller) which works
faultlessly with web development.
 Supports Design view as well which makes it easy for the physical
interface designs.
5.7.1.3. Web Server Adopted:
 Apache Web Server
Adopted because:
 Of its growing popularity.
 Prompt and easy integration.

 High efficiency and performance.

 Works seamlessly with PHP.
5.7.1.4. Database Adopted:
 Oracle 10g Express Client
Adopted because:
 Of its popularity.
 User oriented high performance databases.
 Efficient Session Management
 Free Distribution.

5.7.1.5. Hardware Specification:

5.7.2. Installation of the system:
The system will be installed based on the different components of the system. The
installation would be straightforward as it‟s a web-based system and all it should be done
is copy the program files into the root directory of the web server.
The detailed step-by-step guide to install the system has been provided in the User
Manual, which is included in Appendix H of this very documentation.
5.7.3. Training End Users/Stakeholders:
As almost all staffs, except students, have been using the older current system (ISMS),
thorough training on the day-to-day routine tasks is not needed. However, it‟s imperative to
make them understand the differences between the nature of operations carried out in the
older and newer version of the system. Hence, user training is to be provided to all the
stakeholders and end-users, to whom the system would have made direct effect on.
Following is the plan for the detailed user training:

 A Presentation pertaining to the objectives and operations of the new system, to
all the academic, exams and Student Services staffs would be given.
 Separate workshops to the staffs relating to Academics, Exams and Student
Support would be carried out, where definite individuals will be trained and taken
care of.
 As of students, an online demo to use the new system is proposed to be provided
in the official website of the college.
 A high level seminar will also be organized to introduce the new system to the top
level management personnel. A brief training session cum presentation would also
be carried out.
A User Manual of the new system would also be distributed to all the stakeholders. The
User Manual has been included in Appendix G of this very documentation.

5.7.4. System Changeover:
The System Changeover is the process at the end of which new system would
wholly/partially replace the old system.
There are four major System Changeover Techniques/Concepts used universally, which
are:
 Direct Changeover
 Parallel Changeover
 Pilot Changeover
 Phased Changeover
Fig 5.2 Different Changeover Techniques

Figure Citation:
http://chelet.files.wordpress.com/2009/05/week9.jpg
Retrieved on: 2nd July, 2010

As the old system (ISMS) has been operational in Informatics College, the direct changeover of the
new system would not be appropriate. Hence it is recommended to use Parallel Changeover
where:
 Each department will implement the new system along with the old system.
 More priority will be given to the new system but if the tasks have to be done urgently old
ISMS system will be used.
 After a period of time, when all the end-users are properly trained and made familiar with
the new system, the new system will be directly prevailed.
5.8. Summary of this Chapter:
This Chapter overall discussed about the Testing and Implementation plan of the new
system. Different Testing Strategies were put forth and introduced. Those Strategies were
analyzed and implemented through different Test cases and the results out of those test
cases were also documented. A detailed Implementation plan of action was also
introduced in the later part of this chapter.

Chapter 6 – Systems Evaluation
6.1. Introduction to this Chapter:
This chapter describes the system evaluation segments of the project. The main
mission of this chapter is to carry out an overview of the evaluation which was
necessary during the development of the system which will in turn present the
importance of the implemented solutions which encloses many types of strategies
for the project. The discussion on the evaluation of the project, its outcome and the
practices carried out has been carefully elaborated in this chapter.
6.2. Evaluation Overview:
The evaluation of the project is done against the initial aim and objectives. The main
aim of the project was to maintain the operations, exams management and student
e-support systems for Informatics College. The study on the implementation of the
new system will provide us with the techniques used to deal with the problems and
evaluate the information got from this practice.
In general, system evaluation can be defined as the process of systematically

collecting data that informs us about what it is like for a particular user or a group of
users to use a product for a particular task in a certain type of environment, Preece,
Rogers, Sharpe (2002, p.317).

6.3. Evaluation of Project Deliverables:
The main purpose of the implementation of the new system of operations, exams
management and student e-support systems for Informatics was to overcome the
current system which was only made for limited amounts of users or students and
without exams management and student e-support.
The motive behind the proposed system is to address the entire necessary
problem is current educational scenario in which all the portions are included from
student perspectives to college management views. The solution that is produced
needs to overcome all the problems that the current system has been facing.
6.4. System Evaluation:
The system evaluation is done on the basis of all the working functions within the
system. In the process of system evaluation, the functional evaluation of the project
is carried out which will calculate the functional requirements of the system and its
implementation accuracy during the development which in return should fulfill the
while set of requirements of the system.
6.5. Criteria:
The criteria‟s set for the evaluation of the system would determine all the working
aspects and the strong points of the system.

6.6. Evaluation of the Project Practice:
The project has been made with the support of detail documentation of the system
properties. The measurement of each stage from beginning till end on how they
were done has been specified, their success rate, changes in the middle of the
system and their outcome has also been studied. This will help the system in near
future to be prepared with any type of changes that may occur. This has been
possible because during the evaluation every option on system design or functioning
pattern changes would be studied.
Besides these benefits the main result from the evaluation of the project would be
that we would get the chance to learn about the project management process and its
practices which is very important in future system development projects.
6.7. Chapter Summary:
The main issues that this chapter has discussed are about the implementation of the
system. So for the implementation of the project, the evaluations of different
methods and practice of the current proposed system has been presented with cited
results as a supporting verification.

Chapter 7 – Project Conclusion
7.1 Introduction
Project Conclusion
This chapter concludes the system process of the project. It presents the achievement
within the project boundaries, its future augmentations, resources aspects of the project
and the lessons learnt during the development period of the project.
7.2 Conclusion Outline
The conclusion chapter brings the project into is main conclusion regarding its different
features and development procedures. Here, the main objective of this explanation is to
bring an ample amount of finale conclusion of the project with the aid of its features of the
outcome of the project and the method used in its development procedures. The main
summarization of the achievement of the system are discussed in this chapter to
remember the basic thoughtful information in the project development and the goal
achieved during the development of all the phases of project development from initial to
the final stages.
The understanding of the current student management system of Informatics College has
been done in order to start the project initials. With the collection of these information, we
have come to know about future service that can be added along with the proposed
system which will be beneficial for the institution. Besides the previous system information,
this chapter will focus on the future advantages also. Therefore, the inclusive knowledge

about project development was acquired from this chapter and hence the lessons learned
from this experience were also put forward for the future plan of the system itself.
7.3 Project Achievements
The main target of the project was to fulfill the current system for Informatics by including
student support features along with examinations record keeping and evaluation. The
project development phase was started with the main focus in finding out the problem
domain. The problem domain was meant to be overcome through series of research,
development, testing and implementation phase. This would help me to understand the
project scope as a whole and imply on the solutions to the problems as the development of
the system carries on.
There were lots of challenges on bringing the new features such as student support and
exam management which would replace the current system. The challenges included in
several forms which included both logistically and management point of view which were to
be addressed in their own terms in order to shape the proposed system. The system was
tested with its flexibility which in turn was narrowed down according to its feature and onto
its targeted students, lecturers and staffs.
Therefore, during the completion of the project, there were lots of achievements with their
respective importance which were accomplished through detail study on the system
properties and focus on the ideas. The learning from this experienced has helped my skill
on solving future problems in this current system or any other system that we can come
across.

7.4 Future Escalation
The system that has been proposed for this project has been done for Informatics College
in order to replace their current system which contained limited features has itself been a
remarkable footstep in case of the college‟s management system. With current proposed
system there can be some amount of changes in the future as the institutions has frequent
changes on their management system which may include examinations rules, total number
of students and their courses offered or taken by the students.
In aspects of the current system used in Informatics with its features, the proposed idea for
the new applicable system is efficient and appropriate. However with the use of new
system for the college, there might also be some drawbacks related to the working
structure or management of the system. The previous working environment may change in
the organization relating to exam management and student support which will take some
time for the staff and the student to get used to. While, the proposed system will all in all
better the efficiency of the activities in the college, it will require a getting used to system
requirements which can be fulfilled through providing the staff as well as the students with
training and manuals regarding the proposed system working properties.
The current proposed will include exam management and student e-support as an added
features, whereas in the future the support section of the system can be enhanced with
added features like chat rooms, discussion boards, forums etc. This will be put in future
plans so as to make a clearer vision on the proposed system.
7.5 Resources Aspects
This section of the chapter presents a brief idea about the resources used while making
this project along with its documentation which includes learning related item, literature
reviews and the requirements gathering.
The collection of objects related to the system was studied extensively through
researching about the subject through different universities and college‟s websites, student
forums and e-books books related with programming. Apart from resources gathering,

actual real data of current scenario in the college was done which was carried out through
sequence of questionnaires and interviews with the current working teachers and students
of the college.
During the making of the system, there were plenty of practical works done which included
the collection of raw data along with its implementation on the system. Such information
were to be studied deeply in order to imply them into their own functionality in areas like
database management systems, advanced network architecture, web architecture and
user interface.
7.6 Lessons Learnt
There are lots of lessons that I have learnt during the development of the project. It has
provided me with stern ideas and knowledge on obstacles that we face during the process
of project development.
After all, the project has been completed with sincere dedication in all aspects which
includes study related or work related, planning, researching and requirements gathering
for the related topic. It has taught me to put this all methods into practice. These sections
are very important in making of the project and I have tried my best to implement all of it in
a proper manner. In spite of my sincerity, I have fell behind in some parts and planning and
time management being one of them. Due to increasing load shedding and power outages
in the country, I was not able to complete all of my works on time and the project in all did
not go according to the plan that was submitted with the project proposal. This created
problem in areas regarding coding of the project and documentation presentation. The
interviews along with the questionnaires were done according to the plan, but due to my
lack of experience in data gathering and its studies some of the presentation of collected
data done in this documentation can lack in some of its aspects.
Since the project was based on the educational sector, I had to go through a lot of
counseling from the teachers whom I would like to thank a lot for being helpful and always
available for me. My inexperience in project development was a weak point for me but with
the help of my teachers, I overcame the problems to get along with my system

The main lesson learnt from my project development course was to undertake the project
development periods and its stage on time with accurate results and credibility.
7.7 Critical Appraisal
My main early stages of project development came after receiving the project guidelines
from the college. I chose my project title for my own Informatics College and I am very
thankful for Mr. Lakshman Shimoga who is our project supervisor for accepting my project.
I had made my project plan according to our given guidelines but due to political turmoil
and frequent power outages in the country, the project time period did not go according to
plan. However, with endless time dedication I was able to complete my project with
complete results even after some days of the deadline.
7.8 Summary of this Chapter:
This chapter has presented about the report for the project through simple understanding
and presentation of the project results, its aim and objectives, future development, project
achievements, resource aspects and above all the lessons learnt and decisive judgments.

APPENDIX E – Interview Reports
Name: Mrs. Prabina Rajbhandari Date of Interview: 10th December 2009

Designation: Principal Place: Informatics Premises-Meeting Hall
Q 1. What are your opinions on the initiative taken by the CEO to embark upon a
new system?
Ans:- I’m very happy since it was my recommendation to implement a new system here,
as everybody has been feeling a need of one. I’m happy that the decision has been
materialized this soon.
Q 2. How actually have you been planning the new classes in each new semester so
far?
Ans:- Its all manual currently, because of which we are enduring much problems. Since
we don’t have anything but some pieces of information of the class history of a student,
we all have to maintain a record as to whom student has completed what. It has been
much time consuming and hectic as the number of students has increased and their
choices varied.
Q 4. How many staffs do you currently require for the class planning task?
Ans:- Two or three, but it’s not really the number of staffs’ concern. No matter how many
staffs are there, it has really been time-consuming as the class history of all students has
to be monitored individually.
Q 5. Who are involved in your class planning team?
Ans:- Mr. Sachin Thapa, Accounts Officer, who recognizes quite a number of students
here, heads the team. He can tell a student’s history without having to look into the
registers. Others consist of Mr. Ashok Dhungana, Coordinator, Mr. Govinda Thapa,
Coordinator and Mr. Surendra Phuyal, Administrator.
Q 6. Do you have definite policies with regards to which, you and your team select
and assign lecturers to a class?
Ans:- We have currently a manual system in which we gather student’s feedback and
evaluate a lecturer’s percentage. Lecturers with high ranking are only allowed to continue
the next term. New Lecturers are recruited based on a series of HRM policies. All in all
we try and ensure a team of dedicated most experienced and knowledgeable lecturers. To
assign them into a class, We discuss class timings with them and assign classes according
to their preference as they are only part-timers.
Q 7. How many days does it normally take to plan classes for a particular trimester?
Ans:- Normally it would take a week or so. But, it has been taking at most a month in

recent days as the number of classes has increased drastically.
Name: Mr. Ashok Dhungana Date of Interview: 12th December 2009

Designation: Coordinator-Faculty of IT Place: Informatics Premises-Meeting Hall
Q 1. What are your opinions on the initiative taken by the CEO to embark upon a
new system?
Ans:- Nobody in this college would be happier and satisfied than me upon the threshold
of this new system. There is nobody other than me in this college who needed new and
user-friendly software to manage academic whatnots.
Q 2. By what means, do you think the new system would help you as a manager in
your routine tasks?
Ans:- There are two major domains where I expect the new system to have a magic wand
effect on. First Class Management and the other: Exams Management.
Q 4. What are your opinions on the possible effect of new system in the student
support?
Ans:- Like so much exaggerated, student support has been much unpopular in this
college. As the number of students has increased, the quality of expected student support
has unfortunately, not been proportionate. We had actually tried out managing student
supports much effectively, but I had already realized personally that without an
automated system, it would end up nowhere.
Q5 . What do you think the specific problems are, pertaining to student supports
here?
Ans:- The major setback is again, the number of students. In order to provide an effective
student support, we at least need a working staff to every 10 or 12 students, which is
impossible now. Also, in Informatics, students are involved in quite a lot of activities.
Keeping track of them and fulfilling their needs is virtually impossible in absence of an
automated system. Every time we try our guts out to listen to them, we can’t help their
voices going straight to deaf ears.
Q5 . What about Examinations matters?
Ans:- Examination matters have comparatively fewer problems than the rest. But a new
system would certainly aid to what we have in our current software. We are really
looking forward for it.

Name: Ms. Ranjita Rana Date of Interview: 12th December 2009

Designation: Operations Officer/Student Place: Informatics Cafeteria
Support Officer
Q 1. Have you heard about a new system going to be implemented here, replacing
the current ISMS?
Ans:- Yes I have, and I am desperately looking forward to it.
Q 2. What are your specific problems in the current system i.e. ISMS?
Ans:- mm.. It is working good and has been much helpful but the main problem that I
have faced is the lack of user-friendliness. I gotta’ make a number of clicks to do tasks,
sometimes it’s really hectic when I have to open multiple windows and get confused to
what actually I have been trying to find. Also, somewhere, I am sick of the same
interface; a good graphical interface would add cherry on the cake.
Q 4. What are the student’s complains? I mean, there must be quite a number of
them, but which ones are more specific?
Ans:- Yes, you got it right. I and my colleagues actually get overwhelmed by the
complaints made by students. The more specifics complaints are the lack of quality of
service provided to them and their voices being not heard.
Q 5. What do you think the specific problems are, pertaining to student supports
here?
Ans:- The major setback is again, the number of students. In order to provide an effective
student support, we at least need a working staff to every 10 or 12 students, which is
impossible now. Also, in Informatics, students are involved in quite a lot of activities.
Keeping track of them and fulfilling their needs is virtually impossible in absence of an
automated system. Every time we try our guts out to listen to them, we can’t help their
voices going straight to deaf ears.
Q5 . What about Examinations matters?
Ans:- Examination matters have comparatively fewer problems than the rest. But a new
system would certainly aid to what we have in our current software. We are really
looking forward for it.

Appendix F: Sequence Diagrams
 Sequence Diagrams for Module: Student E-Support
Sequence Diagram for Student E-support: Notification

Sequence Diagram for Student E-support: Submit Assignment


Appendix G: Schema Design-Old System (ISMS)
Following is the schema Design of the database used by the old system. The design was
used in order to design an optimized new database. Some of the entities are kept intact,
some of which unnecessary attributes are removed and added wherever necessary.
Unnecessary and out-domain entities are also removed.









Appendix H – User Manual
Following is the consecutive steps that would help install this new system into a computer.
Installing Server:
1. Install XAMPP utility included in the CD.
Fig 8: XAMPP installation Screen
2. Inside the XAMPP folder, execute xampp-control.exe and install apache (Apache)
as service. MySQL and Filezilla are not needed.

Fig 9 - Xampp Control with Apache set as service
3. Install the Oracle 10g Express Edition using recommended configuration, the
installation package of which is included in the CD (OracleXEUniv.exe).
4. Go to http://localhost:8080/apex and login using the System User set during
installation, in order to check and ensure if the oracle has been installed
successfully.
5. Create a new user with the following credentials as shown in the following
diagram:
Username: isms
Password: donotopen

Fig 10 – Creating new user in Oracle Express 10g
6. Copy the file php_oci8.dll included in the CD into the ext path of the php
installation which normally happens to be <drive>:/xampp/php/ext/. Overwrite if
necessary.
7. Double Click on php.ini file located in <drive>:/xampp/apache/bin/.
8. Uncomment the following lines inside php.ini:
;extension=php_oci8.dll
;extension=php_pdo_oci.dll
;extension=php_pdo_oci8.dll
9. Restart apache service using xampp-control.exe utility. Alternatively you can issue
the following command line in cmd.
net stop apache2.2 <enter>
net start apache2.2 <enter> (this will restart the apache server).
10. Copy the folder new_isms included inside the CD into the <drive>:/xampp/htdocs
folder .

11. Install Google Chrome, the installation package of which is included in the CD.
(Google Chrome is highly recommended browser to be used for this
system).
12. Open Chrome and go to http://localhost/new_isms/ . The system should now be

opened.
Fig 11: Front Interface of New System.

Using the system:
Following Screenshots and diagrams, with the aid of adequate labels, explains the front-
end which is expected to be useful for the end-users to operate on the new system. Since
the old ISMS had been operational and most end-users know the detailed steps, so is not
included.
Fig 12: Login Screen

Invalid Username and Password leads to an error message like above.
Fig 13 Dashboard (different dashboards are there for specific users like Exam officers,
Admins, Academic Officers, student Support Officers etc.)

Fig 14. Dashboard illustrated.
Fig 15. A pop menu containing

all the specific activities
pertaining to the listings.

Fig 16: All the forms, reports, displays etc. pop up in an Ajax dialog box so as to make it
easy for the operators to handle. This also saves time and less hectic for the users.

Appendix I: Source Code

Db.inc.php:
<?php
session_cache_limiter();
@session_start();
include_once("misc.inc.php");
class DbConnect
{
public $dbh;
public function DbConnect()
{
try{
$this->dbh = new PDO('oci:dbname=localhost/XE', 'isms',
'donotopen');
$this->dbh->setAttribute(PDO::ATTR_ERRMODE,
PDO::ERRMODE_EXCEPTION);
}
catch (Exception $e) {
echo "Failed: " . $e->getMessage();
}
}
public function returnCon()

{
return $this->dbh;
}
//This function returns the result set array

public function executeQuery($sql)
{
try{
$stmt=$this->dbh->prepare($sql);
$stmt->execute();
$result=$stmt->fetch(PDO::FETCH_ASSOC);
return $result;
}
catch (Exception $e){
echo "Failed in ExecuteQuery: " . $e->getMessage();
}
}

//This function returns the pure resultset, there to be fetched.

public function executeSql($sql)
{
try{
$stmt=$this->dbh->prepare($sql);
$stmt->execute();
return $stmt;
}
echo "Failed in ExecuteQuery: " . $e->getMessage();
}
}
public function selectRows($attributes, $tbl, $condition)

{
$sql="select $attributes from $tbl where $condition";
$result=$this->executeQuery($sql);
return $result;
}
public function selectRowsMultiple($attributes, $tbl, $condition)

{
$sql="select $attributes from $tbl where $condition";
$result=$this->executeSql($sql);
return $result;
}
public function getNumRows($sql)

{
$num=0;
$result=$this->executeSql($sql);
while($row=$result->fetch(PDO::FETCH_ASSOC))
{
$num++;
}
return $num;
}
}
?>

student.inc.php:
<?php
require_once('db.inc.php');
include_once("course.inc.php");
class Student
{
public $StudentId;
public $db;
public function Student($studentid)

{
$this->StudentId=$studentid;
$this->db=new DbConnect();
}
//The following method can be used without having to make an object of this class.
public static function listStudents()
{
?>
<div class="content-box">
<div class="content-box-header">
<h3>Listing Students</h3>
</div>
<div class="content-box-content">
<table class="pagination">
<thead>
<tr>
<td colspan="6">
Search: <input type="text">
<a href="#" onmouseout="hideTooltip()" onmouseover="showTooltip(event,'Search
students using advanced credentials!');return true">Detailed Search</a>
</td>
</tr>
<tr>
<th><input
type="checkbox" /></th>
<th>StudentId</th>
<th>Full
Name</th>
<th>Course</th>

<th>Phone</th>
<th>Actions</th>
</tr>
</thead>
<tfoot>
<tr>
<td colspan="6">
<div
class="bulk-actions">
<a href="#" class="graybutton">Apply to selected</a>

</div>
</td>
</tr>
</tfoot>
<tbody>
<?php
$db=new DbConnect();
$dbm=$db->returnCon();
try{
$sql="select StudentId from student";
$stmt=$dbm->prepare($sql);
$stmt->execute();
while($row = $stmt->fetch(PDO::FETCH_ASSOC))
{
$std=new Student($row['STUDENTID']);
//display records of each student as a row
$std->displayRecord();
}
}
echo "Failed in checking username and password: " . $e->getMessage();
}
?>
</tbody>
</table>
</div>
</div>

<?php
}
public function displayRecord()
{
?>
<tr>
<td><input type="checkbox" /></td>
<td><?=$this->StudentId?></td>
<?php
$pic="<img src=images/studpics/".$this->StudentId.".jpg
width=130 align=texttop>";
?>
<td><a href="#" onMouseover="showTooltip(event,'<?=$pic?>');return false;"
onmouseout="hideTooltip()"><?=$this->getStudentNameById(1,1,1)?></a></td>
<td><?php $this->displayRunningCourse();?></td>
<td><?=$this->getCellPhone()?></td>
<td>
<a href="#modal<?=$this->StudentId?>" rel="modal" title="More Actions">More
Actions</a>
<a href="#" title='View Details of this student'
onclick="displayMessage('includes/manage_stud/view_stud.php?id=<?=$this->StudentId?>',900,600);return
false;"><img src="images/icons/binocular.png" alt="Edit" /></a>
<a href="#" title="Modify"
onclick="displayMessage('includes/manage_stud/mod_stud.php?id=<?=$this->StudentId?>',900,600);return
false;"><img src="images/icons/pencil.png" alt="Edit" /></a>
<a href="#" title='Term Break' class="confirmation"><img src="images/icons/termbreak.png"
alt="Delete" /></a>
<a href='#' title='Add/Modify Class Status'><img src="images/icons/acs.png" alt="Add/Modify
Class Status" /></a>
</td>
</tr>
<div id="modal<?=$this->StudentId?>">
<div class="modalbox">
<div class="modalhead">
<img src="images/modaltop.png" alt="Modal arrow"/>
More Actions for <?=$this->getStudentNameById(1,1,1)?>:
</div>
<div class="modalcontent">
<ul>
<li><a href="#">View Class Status</a></li>
<li><a href="#">View Results</a></li>
<li><a href="#">View Progress Report</a></li>

<li><a href="#">Enter Grades of</a></li>

<li><a href="#">View Registration</a></li>
</ul>
</div>
<div class="modalfoot">
<img src="images/icons/newmessage.png" alt="New message" /> New message
</div>
</div>
</div>
<?php
}
public function getStudentNameById($first, $middle, $last)
{
$result=$this->db->selectRows("Fname,Mname,Lname","student",
"StudentId='".$this->StudentId."'");
//$data=$result->fetch(PDO::FETCH_ASSOC);
if($first==1)
$name.=$result['FNAME']." ";
if($middle==1)
if(!is_null($result['MNAME']))
$name.=$result['MNAME']." ";
if($last==1)
$name.=$result['LNAME']." ";
$name=trim(ucwords($name));
return $name;
}
public function getCellPhone()

{
$result=$this->db->selectRows("CellPhone","student", "StudentId='".$this-
>StudentId."'");
return $result['CELLPHONE'];
}
public function displayRunningCourse()

{
$i=0;
$course=array();
$sql="select CourseId from studentcourse where StudentId='".$this-
>StudentId."' and Status='r'";
//Misc::displayMsg($sql);

$result=$this->db->executeSql($sql);
while($row=$result->fetch(PDO::FETCH_ASSOC))
{
$course[$i++]=$row['COURSEID'];
}
foreach($course as $val)
{
echo Course::getCourseNameAbb($val)." ";
}
}
public function displayAllCourse()
{
$i=0;
$course=array();
$sql="select CourseId,status from studentcourse where StudentId='".$this-
>StudentId."'";
$num=$this->db->getNumRows($sql);
if($num>0){
$result=$this->db->executeSql($sql);
while($row_c=$result->fetch(PDO::FETCH_ASSOC))
{
if($row_c['STATUS']=='r' or $row_c['STATUS']=='R')
$status="<span
style='color:green'>Running</span>";
else if($row_c['STATUS']=='g' or $row_c['STATUS']=='G')
$status="<span
style='color:red'>Graduated</span>";
else if($row_c['STATUS']=='c' or $row_c['STATUS']=='C')
$status="<span
style='color:red'>Completed</span>";
else if($row_c['STATUS']=='w' or $row_c['STATUS']=='W')
$status="<span style='color:red'>Walked
Away</span>";
echo Course::getCourseNameAbb($row_c['COURSEID']) .
" - " . $status."<br>";
}
}else{
echo "<span style='color:red'>Not enrolled in any courses</span>";
}
}
}
?>

Informatics OperationsExams Management and Student E-Support System

Uploaded by

Document Information

Copyright

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Informatics OperationsExams Management and Student E-Support System

Uploaded by

Copyright:

PJ330 G IMSS B.Sc.

(Honors) in Computing (UOP)

Technology Extended Campus

Honor‟s project undertaken in partial fulfillment of

BSc (Hons) Computing

“Informatics Operations/Exams Management and Student e-

1 Prakash Shrestha | Hemis: 472124

2 Prakash Shrestha | Hemis: 472124

Signed Student Name Prakash Shrestha

3 Prakash Shrestha | Hemis: 472124

4 Prakash Shrestha | Hemis: 472124

Chapter 1 – Systems Introduction

1.1 Objective of this Chapter:

The proposed system IMSS (Informatics Operations/Exam Management and Student e-

Informatics College Kathmandu is a regular and one of the largest franchises of

IMSS is intended to replace an already running Student Management System operational

5 Prakash Shrestha | Hemis: 472124

1.3 Motivational Factors:

“Prakash, I am unable to open the software. This software is so irritating. Can we

6 Prakash Shrestha | Hemis: 472124

1.4 Problem Domain:

 Why the problems are so interesting? Why has management been

o Planning and managing classes:

7 Prakash Shrestha | Hemis: 472124

graduate. The current manual tracking system is hard to manage and

o Student Management task is also problematic in the current system. The

o Managing Exams is also problematic in the current system. The exam

8 Prakash Shrestha | Hemis: 472124

1.5 Approaches Taken:

 A detailed study will be carried out on the problem domain.

1.6 Project Aims and Objectives:

1. To be able to manage Student Administration tasks with an optimum ease.

9 Prakash Shrestha | Hemis: 472124

1.6.3 Scope of the Project:

1.7 Project Deliverables:

 System Documentation consisting of Project Proposal, Systems Requirements

10 Prakash Shrestha | Hemis: 472124

1.8 Outline of the Proposed System:

Fig 1.1: Outline of the proposed system

11 Prakash Shrestha | Hemis: 472124

1.9 Project Time Plan:

1.10 Summary of this Chapter:

12 Prakash Shrestha | Hemis: 472124

Chapter 2 – Literature Review

2.1 Objectives of this Chapter:

2.3 Importance of ICT in Informatics College:

13 Prakash Shrestha | Hemis: 472124

mobile engineers and various other IT professionals. Being an IT professional producing

2.4 Introduction to Web Centric System and it’s suitability in Informatics

2.5 Suitability of Web-based System in Informatics College:

14 Prakash Shrestha | Hemis: 472124

 Overall Operations/Exams Management:

Operations in Informatics College include class management, lecturers management,

Appraisal is a decision method which includes the formulation and evaluation of

e-Appraisal of Staffs/ Lecturers in Informatics College:

15 Prakash Shrestha | Hemis: 472124

2.7 Selection of Development Tools and Justification:

 Object-Oriented PHP as the Front-end Programming Language

Fig 2.1: PHP and Oracle client library link

16 Prakash Shrestha | Hemis: 472124

Object Oriented PHP is chosen mainly due to the following reasons:

17 Prakash Shrestha | Hemis: 472124

Adobe Dreamweaver CS4 is chosen as an IDE for the development as:

18 Prakash Shrestha | Hemis: 472124

2.8 Development Methodology to be used:

Waterfall methodology is proposed to be used as a development methodology. Waterfall

Fig 2.2: SDLC (Software Development Lifecycle)