Attendance Management System m423w

1. INTRODUCTION Channel-I is a website designed to manage students in a campus. Using this both students and teachers can manage their attendances as well as manage the schedule of classes, various subjects they are enrolled in. can add various teachers and students to the system and once they are added teachers can add students to their courses. Moreover it provides blogging facility to the so that they can submit thei r articles and once it is approved by then it is ready to be published. Earlier systems developed for this lack online , i.e. they can be used only on the machine on which it is installed. Whereas this system running over the internet can be used from any location.

Logo

1|P a g e

2. PURPOSE The purpose to develop such a system is to computerize the traditional way of taking attendance which if often cumbersome to manage and if record is misplaced then there is nothing a person can do about it. The information is sorted by the operators, which will be provided by the teacher for a particular class. This system will also help in evaluating attendance eligibility criteria of a student. The purpose of developing attendance management system is to computerized the tradition way of taking attendance. Another purpose for developing this software is to generate the report automatically at the end of the session or in the between of the session.

2|P a g e

3. CURRENTLY IMPLEMENTED FEATURES - for profile based management: , Teacher and Student - Online teacher and student registration - Allow to add courses - Allow to add students and enrol them to one or more courses - Allow to edit students already entered into database - Allow to edit courses already entered into database - Allow teachers to manage student attendance - Allow teachers to display graphically course attendance and - Allow students to check their enrolment and provide for a course - Blog - Main website can be viewed in multiple colours

3|P a g e

4. SCOPE The scope of this project is restricted to a particular institute and this website will work over the entire internet or it can be made to work on the college intranet.

4.1 LIFE TIME: This product works until the software used is in existence.

4.2 SUCCESS CRITERIA: As we are using current trends of website, the product runs successfully.

4.3 REQUIREMENTS Hardware Requirements  Pentium III or above  256MB RAM  Internet Connection Software Requirements  Web Browser with Java Script and FLASH  WAMP Server(if testing website locally)

4|P a g e

5. FUNCTIONAL REQUIREMENTS: This system requires the following information to maintain attendance of each student. 1. 2. 3. 4. 5. 6. 7.

Teachers and students themselves to the website. adds teachers to the system and assign them respective courses and classes. then adds students to the system Teachers then add student to the courses and then their attendance is marked Students can to view their course details along with some other details can by using the page. Blog posts are added by by using the for the blog.

5|P a g e

6. NON-FUNCTIONAL REQUIREMENTS: USABILITY: The product could be used by two categories of people: faculty and students. Apart from them also could use it.

RELIABILITY: s can perform the operations without any constraints regarding the outcome of operation. The product as a whole is highly reliable.

PERFORMANCE: It provides s with access to information based on the type of s i.e. , student, faculty and to which department they belong. It provides fast access to all the data and transactions requested thereby providing a high degree of performance and throughput.

ABILITY: All kinds of information which can be ed in the database are ed by the system and the application s the utilities of the system over which it is deployed.

6|P a g e

7. TECHNOLOGY USED DEG LANGUAGES: HTML, CSS3, jQuery, Flash PROGRAMMING LANGUAGE: PHP DATABASE: SQL

FIGURE: HOW A DYNAMIC WEBSITE WORKS

7|P a g e

8. FEASIBLITY

8.1 ECONOMICALLY FEASIBILITY: The system being developed is economic with respect to School or Collage’s point of view. It is cost effective in the sense that has eliminated the paper work completely. The result obtained contains minimum errors and are highly accurate as the data is required.

8.2 TECHNICAL FEASIBILITY: The technical requirement for the system is economic and it does not use any other additional Hardware and software.

8.3 BEHAVIOURAL FEASIBILITY: The system working is quite easy to use and learn due to its simple but attractive interface. requires no special training for operating the system.

8|P a g e

9. WORKING OF PRESENT SYSTEM In the present system all work is done on paper. The whole session attendance is stored in and at the end of the session the reports are generated.

9.1 DISADVANTAGES OF PRESENT WORKING SYSTEM      

Not Friendly: The existing system is not friendly because the retrieval of data is very slow and data is not maintained efficiently. Difficulty in report generating: We require more calculations to generate the report so it is generated at the end of the session. And the student not get a single chance to improve their Attendance Manual control: All calculations to generate report is done manually so there is greater chance of errors. Lots of paperwork: Existing system requires lot of paper work. Loss of even a single /record led to difficult situation because all the papers are needed to generate the reports. Time consuming: Every work is done manually so we cannot generate report in the middle of the session or as per the requirement because it is very time consuming. Most systems are desktop based so they cannot be used to view details by other s easily.

9|P a g e

10. CHARECTERISTIC OF THE PROPOSED SYSTEM • Friendly: The proposed system is friendly because the retrieval and storing of data is fast and data is maintained efficiently. Moreover the graphical interface is provided in the proposed system, which provides to deal with the system very easily. • Very less paper work: The proposed system requires very less paper work. All the data is feted into the computer immediately and reports can be generated through computers. Moreover work become very easy because there is no need to keep data on papers. • Computer operator control: Computer operator control will be there so no chance of errors. Moreover storing and retrieving of information is easy. So work can be done speedily and in time.

10 | P a g e

11. SOFTWARE PROCESS MODEL: To solve actual problems in an industry, software developer or a team of developers must incorporate a development strategy that encomes the process, methods and tools layers and generic phases. This strategy is often referred to as process model or a software developing paradigm. A process model for software developing is chosen based on the nature of project and application, the methods and tools to be used, and the controls and deliverables that are required. All software development can be characterized as a problem solving loop in which four distinct stages are encountered: Status quo, Problem definition, technical development and solution integration. Regardless of the process model that is chosen for a software project all of the stages coexist simultaneously at some level of detail.

Our Project Follows the Waterfall Model:

 The Waterfall Model: The steps of the typical Waterfall Model are: 1. Requirement Definition. 2. System & Software Design. 3. Implementation. 4. Integration & System Testing. 5. Operation and Maintenance. There have been some variations from the typical waterfall model for this project lifecycle. They are: 1. Maintenance has been omitted from the current project. 2. Not all testing methods which are present in theoretical model are implemented.

11 | P a g e

12 | P a g e

12. ENTITY RELATIONSHIP MODEL It is an abstract and conceptual representation of data. Entity relationship modelling is a database modelling method, used to produce a type of conceptual schema or semantic data model of a system, often a relational database, and its requirements in a down fashion. Diagrams created by this process are called entity-relationship diagrams, ER diagrams, or ERDs. COMPONENTS: ENTITY: An entity may be defined as a thing which is recognized as being capable of an independent existence and which can be uniquely identified. An entity is an abstraction from the complexities of some domain. When we speak of an entity we normally speak of some aspect of the real world which can be distinguished from other aspects of the real world. An entity may be a physical object such as a house or a car, an event such as a house sale or a car service, or a concept such as a customer transaction or order. Although the term entity is the one most commonly used, following Chen we should really distinguish between an entity and an entity-type. An entity-type is a category. An entity, strictly speaking, is an instance of a given entity-type. There are usually many instances of an entity-type. Because the term entity-type is somewhat cumbersome, most people tend to use the term entity as a synonym for this term. Entities can be thought of as nouns. Examples: a computer, an employee, a song, a mathematical theorem. REPRESENTATION: Entities are drawn as rectangles EXAMPLE: COMPANY

JOB

Or ATTRIBUTES: An entity is described using a set of attributes. All entities in a given entity set have the same attributes; this is known as similar type. Our choice of attributes reflects the level of detail at which we wish to represent information about entities. For example, company entity set could use company_id, company_name for each company. For each attribute associated with an entity set, we must identify a domain of possible values. For example domain associated with attribute company_name of company might be a set of 20-characterstrings similarly company_id might be integer. Further, for each entity set, we choose a key. A key is a minimal set of attributes whose values uniquely identify an entity in the set, generally called as candidate key, there could be more than one candidate key, if so we designate one of them as primary key. A primary key is key with which we can identify a tuple uniquely. TYPES: Simple Attribute: A normal attribute defining a entity Representation: Name Multivalued attribute: 13 | P a g e

Attribute consisting of multiple values. Example: Address Derived attribute: An attribute which is derived from other attribute. RELATIONS: A relationship captures how two or more entities are related to one another. Relationships can be thought of as verbs, linking two or more nouns. Examples: a owns relationship between a company and a computer, a supervises relationship between an employee and a department, a performs relationship between an artist and a song, a proved relationship between a mathematician and a theorem. Entity-relationship diagrams don't show single entities or single instances of relations. Rather, they show entity sets and relationship sets. Example: a particular song is an entity. The collection of all songs in a database is an entity set. The eaten relationship between a child and her lunch is a single relationship. The set of all such child-lunch relationships in a database is a relationship set. In other words, a relationship set corresponds to a relation in mathematics, while a relationship corresponds to a member of the relation. EXAMPLE: COMPANY

OFFERS

JOB

CARDINALITY: In the relational model, tables can be related as any of: many-to-many, many-t oone (rev. one-to-many), or one-to-one. This is said to be the cardinality of a given table in relation to another. For example, considering a database designed to keep track of hospital records. Suc h a database could have many tables like: A Doctor table full of doctor information A Patient table with patient information And a Department table with an entry for each department of the hospital. In that model: There is a many-to-many relationship between the records in the doctor table and records in the patient table (Doctors have man y patients, and a patient could have several doctors); A one-to-many relation between the department table and the doctor table (each doctor works for one department, but one department could have many doctors). One-to-one relationship is mostly used to split a table in two in order to optimize access or limit the visibility of some information. In the hospital example, such a relationship could be used to keep apart doctor's personal or istrative information.

14 | P a g e

13 SQL DATABASE STRUCTURE The SQL Database consists of following tables  crc_attendance  crc_courses  crc_date  crc_  crc__answers  crc__questions  crc_profiles  crc_roles  crc_rooms  crc_schedules  crc_sessions  crc_states  crc_student_schedule  crc_teacher_schedule  crc_venue  s  news 

13.1 DETAILS OF DATABASE TABLES 

crc_attendance Column attendance_id attendance_student_schedule_id attendance_date_id attendance_check



Type int(11) int(11) int(11) Char(1)

Null No No No No

Default 0 0 A

crc_courses

Column course_id course_name course_desc course_active course_fee

15 | P a g e

Type Int(11) Varchar(100) Varchar(255) Tinyint(1) Int(11)

Null No No Yes No No

Default

0 0



crc_date

Column date_id date_day date_month date_year 

Type Int(11) Int(11) Int(11) Timestamp Tinyint(1)

Default

Null No No No No No

Default 0 0 CURRENT_TIMESTAMP 0

crc__answers

Column _answers_id _answers__id _answers_questions_id _answers_answer _answers_active _answers_comments 

Null No No No no

crc_

Column _id _profile_id _schedule_id _date _active 

Type Int(11) Char(2) Char(2) Varchar(4)

Type Int(11) Int(11) Int(11) Text Tinyint(4) Text

Null No No No No No No

Default 0 0 0

crc__questions

Column _questions_id _questions_question _questions_active _questions_type _questions_category _questions_sequence

16 | P a g e

Type Int(11) Text Tinyint(1) Varchar(100) Varchar(100) Int(11)

Null No No No No No No

Default

0 COMMENT COMMENTS 0



crc_profiles

Column profile_id profile_uid profile_pwd profile_firstname profile_lastname profile_email profile_dob profile_gender profile_employed profile_employed_title profile_employed_compa ny profile_address_one profile_address_two profile_city profile_province_state profile_postal_code profile_country profile_phone_land profile_phone_cell profile_phone_fax profile_role_id profile_active profile_rdn profile_date

17 | P a g e

Type

Nul l Int(11) No Varchar(100 No ) Varchar(40) No Varchar(100 No ) Varchar(100 No ) Varchar(100 No ) Date No Varchar(6) No Tinyint(1) Yes Varchar(100 Yes ) Varchar(100 Yes ) Varchar(100 Yes ) Varchar(100 Yes ) Varchar(100 Yes ) Varchar(100 Yes ) Varchar(100 Yes ) Varchar(100 Yes ) Varchar(14) Yes Varchar(14) Yes Varchar(14) Yes Int(11) No Tinyint(1) No Varchar(100 Yes )

Default

Timestamp

CURRENT_TIMESTAMP

No

2010-01-01 M 0

0 0 ou=don mills,ou=toronto,ou=ontario,ou=canada,o=c rc world



crc_roles

Column role_id role_name role_desc role_active

Type Int(11) Varchar(100) Varchar(255) Tinyint(10

Null No No No No

Default

Type Int(11) Varchar(100) Varchar(255)

Null No No No

Default

Column schedule_id schedule_course_id schedule_start_date schedule_end_date schedule_day_time

Type Int(11) Int(11) Date Date Varchar(30)

Null No No No No No

Default

schedule_status schedule_room_id schedule_active schedule_venue_id

Varchar(100) Int(11) Tinyint(1) Int(11)

No No No No

Tentative 2 0 1

Type Int(11) Varchar(255) Varchar(15) Varchar(15) Varchar(255) Timestamp

Null No No No No No No



crc_rooms

Column room_id room_name room_desc 



0

crc_schedule

0 2010-01-01 2010-01-01 M,W [8:00PM 10:00PM]

crc_sessions

Column sessions_oid sessions_id sessions_uid sessions_pwd sessions_dn sessions_time

18 | P a g e

Default

CURRENT_TIMESTAMP



crc_states

Column state_id state_name state_desc 

Type Int(11) Varchar(50) Text

Null No No No

Default

crc_student_schedule

Column student_schedule_id student_schedule_profile_id student_schedule_schedule_id student_schedule_paid student_schedule_amount

Type Int(11) Int(11) Int(11) Char(1) Int(11)

Null No No No No No

Default

student_schedule_questions

Tinyint(1)

No

0

Type Int(11) Int(11) Int(11) Int(11)

Null No No No No

Default



0 0 0

crc_venue

Column venue_id venue_name venue_desc Venue_shortname 

0

crc_teacher_schedule

Column teacher_schedule_id teacher_schedule_profile_id teacher_schedule_schedule_id teacher_schedule_evaluation 

0 0 U

Type Int(11) Varchar(50) Text Varchar(8)

Null No No No No

Default

Type Int(11) Text Text

Null No No No

Default

news

Column post_id title blog_entry

19 | P a g e



s

Column id name 

Type Int(11) Text Text

Null No No No

Default



Column Id name emailid telephone message date

20 | P a g e

Type Int(6) Varchar(50) Text Int(15) Text Timestamp

Null No No No No No No

Default

CURRENT_TIMESTAMP

13.2 SQL CODE FOR GENERATING REQUIRED DATABASE -- phpMy SQL Dump -- version 3.4.10.1 -- http://www.phpmy.net --- Host: localhost -- Generation Time: Jun 03, 2013 at 06:14 AM -- Server version: 5.5.20 -- PHP Version: 5.3.10 SET SQL_MODE="NO_AUTO_VALUE_ON_ZERO"; SET time_zone = "+00:00";

/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */; /*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */; /*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */; /*!40101 SET NAMES utf8 */; --- Database: `crcdb` --- ---------------------------------------------------------- Table structure for table `campus_news` -CREATE TABLE IF NOT EXISTS `campus_news` ( `id` int(6) unsigned NOT NULL AUTO_INCREMENT, `date` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP, `news` text NOT NULL, `title` varchar(100) NOT NULL, PRIMARY KEY (`id`) ) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ; -- ---------------------------------------------------------- Table structure for table `` --

21 | P a g e

CREATE TABLE IF NOT EXISTS `` ( `id` int(6) unsigned NOT NULL AUTO_INCREMENT, `name` varchar(50) NOT NULL, `emailid` text NOT NULL, `telephone` int(15) NOT NULL, `message` text NOT NULL, `date` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP, PRIMARY KEY (`id`) ) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=2 ; -- ---------------------------------------------------------- Table structure for table `crc_attendance` -CREATE TABLE IF NOT EXISTS `crc_attendance` ( `attendance_id` int(11) NOT NULL AUTO_INCREMENT, `attendance_student_schedule_id` int(11) NOT NULL DEFAULT '0', `attendance_date_id` int(11) NOT NULL DEFAULT '0', `attendance_check` char(1) NOT NULL DEFAULT 'A', PRIMARY KEY (`attendance_id`) ) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=75 ; -- ---------------------------------------------------------- Table structure for table `crc_courses` -CREATE TABLE IF NOT EXISTS `crc_courses` ( `course_id` int(11) NOT NULL AUTO_INCREMENT, `course_name` varchar(100) NOT NULL DEFAULT '', `course_desc` varchar(255) DEFAULT '', `course_active` tinyint(1) NOT NULL DEFAULT '0', `course_fee` int(11) NOT NULL DEFAULT '0', PRIMARY KEY (`course_id`,`course_name`) ) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=14 ; --- Dumping data for table `crc_courses` -INSERT INTO `crc_courses` (`course_id`, `course_name`, `course_desc`, `course_active`, `course_fee`) VALUES (13, 'EE223', '', 0, 0); 22 | P a g e

-- ---------------------------------------------------------- Table structure for table `crc_date` -CREATE TABLE IF NOT EXISTS `crc_date` ( `date_id` int(11) NOT NULL AUTO_INCREMENT, `date_day` char(2) NOT NULL DEFAULT '', `date_month` char(2) NOT NULL DEFAULT '', `date_year` varchar(4) NOT NULL DEFAULT '', PRIMARY KEY (`date_id`) ) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=14 ; -- ---------------------------------------------------------- Table structure for table `crc_` -CREATE TABLE IF NOT EXISTS `crc_` ( `_id` int(11) NOT NULL AUTO_INCREMENT, `_profile_id` int(11) NOT NULL DEFAULT '0', `_schedule_id` int(11) NOT NULL DEFAULT '0', `_date` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP, `_active` tinyint(1) NOT NULL DEFAULT '0', PRIMARY KEY (`_id`), KEY `_profile_id` (`_profile_id`,`_schedule_id`) ) ENGINE=MyISAM DEFAULT CHARSET=latin1 COMMENT='This table is facility to store feddback information from st' AUTO_INCREMENT=20 ; -- ---------------------------------------------------------- Table structure for table `crc__answers` -CREATE TABLE IF NOT EXISTS `crc__answers` ( `_answers_id` int(11) NOT NULL AUTO_INCREMENT, `_answers__id` int(11) NOT NULL DEFAULT '0', `_answers_questions_id` int(11) NOT NULL DEFAULT '0', `_answers_answer` text NOT NULL, `_answers_active` tinyint(4) NOT NULL DEFAULT '0', `_answers_comments` text NOT NULL, PRIMARY KEY (`_answers_id`) 23 | P a g e

) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=449 ; -- ---------------------------------------------------------- Table structure for table `crc__questions` -CREATE TABLE IF NOT EXISTS `crc__questions` ( `_questions_id` int(11) NOT NULL AUTO_INCREMENT, `_questions_question` text NOT NULL, `_questions_active` tinyint(1) NOT NULL DEFAULT '0', `_questions_type` varchar(100) NOT NULL DEFAULT 'COMMENT', `_questions_category` varchar(100) NOT NULL DEFAULT 'COMMENTS', `_questions_sequence` int(11) NOT NULL DEFAULT '0', PRIMARY KEY (`_questions_id`), KEY `SEQUENCE` (`_questions_sequence`) ) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=29 ; --- Dumping data for table `crc__questions` -INSERT INTO `crc__questions` (`_questions_id`, `_questions_question`, `_questions_active`, `_questions_type`, `_questions_category`, `_questions_sequence`) VALUES (1, 'I feel that I have gained new skills and knowledge.', 0, 'OPTION', 'GENERAL', 1), (2, 'I will recommend the course to other member(s).', 0, 'OPTION', 'GENERAL', 2), (3, 'I believe the skills that I have learned will help.', 0, 'OPTION', 'GENERAL', 3), (4, 'The course material was easy to read.', 0, 'OPTION', 'GENERAL', 4), (5, 'I will be able to use the course materials as a reference.', 0, 'OPTION', 'GENERAL', 5), (6, 'I felt totally comfortable during the course.', 0, 'OPTION', 'GENERAL', 6), (7, 'The lesson time frame was appropriate for the course.', 0, 'OPTION', 'GENERAL', 7), (8, 'My expectations for the course were met.', 0, 'OPTION', 'GENERAL', 8), (9, 'I understood the course objectives clearly.', 0, 'OPTION', 'OBJECTIVE', 9), (10, 'I did achieve the course objectives.', 0, 'OPTION', 'OBJECTIVE', 10), (11, 'The topics presented in the course were relevant to my work.', 0, 'OPTION', 'OBJECTIVE', 11), (12, 'The course was structured in a logical way.', 0, 'OPTION', 'OBJECTIVE', 12), (13, 'The course was easy to follow.', 0, 'OPTION', 'OBJECTIVE', 13), (14, 'The course was interesting and enjoyable.', 0, 'OPTION', 'OBJECTIVE', 14), (15, 'The concepts and techniques used were explained clearly.', 0, 'OPTION', 'PRESENTATION', 15), (16, 'I was encouraged to actively participate during the course.', 0, 'OPTION', 'PRESENTATION', 16), (17, 'My individual questions/problems discussed were satisfactorily answered.', 0, 'OPTION', 'PRESENTATION', 17), 24 | P a g e

(18, 'The presentation style of the instructor was satisfactory.', 0, 'OPTION', 'PRESENTATION', 18), (19, 'The instructor''s knowledge of the subject was satisfactory.', 0, 'OPTION', 'PRESENTATION', 19), (20, 'The course was well paced.', 0, 'OPTION', 'PRESENTATION', 20), (21, 'Please comment on what you liked about the course.', 0, 'COMMENT', 'COMMENTS', 21), (22, 'What improvements would you suggest for this course.', 0, 'COMMENT', 'COMMENTS', 22), (23, 'Please provide any additional comments not covered.', 0, 'COMMENT', 'COMMENTS', 23); -- ---------------------------------------------------------- Table structure for table `crc_profiles` -CREATE TABLE IF NOT EXISTS `crc_profiles` ( `profile_id` int(11) NOT NULL AUTO_INCREMENT, `profile_uid` varchar(100) NOT NULL DEFAULT '', `profile_pwd` varchar(40) NOT NULL DEFAULT '', `profile_firstname` varchar(100) NOT NULL DEFAULT '', `profile_lastname` varchar(100) NOT NULL DEFAULT '', `profile_email` varchar(100) NOT NULL DEFAULT '', `profile_dob` date NOT NULL DEFAULT '2010-01-01', `profile_gender` varchar(6) NOT NULL DEFAULT 'M', `profile_employed` tinyint(1) DEFAULT '0', `profile_employed_title` varchar(100) DEFAULT '', `profile_employed_company` varchar(100) DEFAULT '', `profile_address_one` varchar(100) DEFAULT '', `profile_address_two` varchar(100) DEFAULT '', `profile_city` varchar(100) DEFAULT '', `profile_province_state` varchar(100) DEFAULT '', `profile_postal_code` varchar(100) DEFAULT '', `profile_country` varchar(100) DEFAULT '', `profile_phone_land` varchar(14) DEFAULT '00400000000000', `profile_phone_cell` varchar(14) DEFAULT '00400000000000', `profile_phone_fax` varchar(14) DEFAULT '00400000000000', `profile_role_id` int(11) NOT NULL DEFAULT '0', `profile_active` tinyint(1) NOT NULL DEFAULT '0', `profile_rdn` varchar(100) DEFAULT 'ou=don mills,ou=toronto,ou=ontario,ou=canada,o=crc world', `profile_date` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP, PRIMARY KEY (`profile_id`,`profile_uid`,`profile_email`) ) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=25 ; 25 | P a g e

--- Dumping data for table `crc_profiles` -INSERT INTO `crc_profiles` (`profile_id`, `profile_uid`, `profile_pwd`, `profile_firstname`, `profile_lastname`, `profile_email`, `profile_dob`, `profile_gender`, `profile_employed`, `profile_employed_title`, `profile_employed_company`, `profile_address_one`, `profile_address_two`, `profile_city`, `profile_province_state`, `profile_postal_code`, `profile_country`, `profile_phone_land`, `profile_phone_cell`, `profile_phone_fax`, `profile_role_id`, `profile_active`, `profile_rdn`, `profile_date`) VALUES (1, '', 'd033e22ae348aeb5660fc2140aec35850c4da997', 'Firstname', 'Lastname', '[email protected]', '1993-12-02', 'M', 0, '', '', 'weqweqewiqweqiwe', '', 'Toronto', 'ON', '222222', 'Canada', '00400000000000', '00400000000000', '00400000000000', 2, 0, 'ou=don mills,ou=toronto,ou=ontario,ou=canada,o=crc world', '2013-05-18 19:58:10'); -- ---------------------------------------------------------- Table structure for table `crc_roles` -CREATE TABLE IF NOT EXISTS `crc_roles` ( `role_id` int(11) NOT NULL AUTO_INCREMENT, `role_name` varchar(100) NOT NULL DEFAULT '', `role_desc` varchar(255) NOT NULL DEFAULT '', `role_active` tinyint(1) NOT NULL DEFAULT '0', PRIMARY KEY (`role_id`,`role_name`) ) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=4 ; --- Dumping data for table `crc_roles` -INSERT INTO `crc_roles` (`role_id`, `role_name`, `role_desc`, `role_active`) VALUES (1, '', 'CRC role', 1), (2, 'Teacher', 'CRC Teacher role', 1), (3, 'Student', 'CRC Student role', 1); -- ---------------------------------------------------------- Table structure for table `crc_rooms` 26 | P a g e

-CREATE TABLE IF NOT EXISTS `crc_rooms` ( `room_id` int(11) NOT NULL AUTO_INCREMENT, `room_name` varchar(100) NOT NULL DEFAULT '', `room_desc` varchar(100) NOT NULL DEFAULT '', PRIMARY KEY (`room_id`) ) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=4 ; --- Dumping data for table `crc_rooms` -INSERT INTO `crc_rooms` (`room_id`, `room_name`, `room_desc`) VALUES (3, '122', 'N/A'); -- ---------------------------------------------------------- Table structure for table `crc_schedule` -CREATE TABLE IF NOT EXISTS `crc_schedule` ( `schedule_id` int(11) NOT NULL AUTO_INCREMENT, `schedule_course_id` int(11) NOT NULL DEFAULT '0', `schedule_start_date` date NOT NULL DEFAULT '2010-01-01', `schedule_end_date` date NOT NULL DEFAULT '2010-01-01', `schedule_day_time` varchar(30) NOT NULL DEFAULT 'M,W [8:00PM - 10:00PM]', `schedule_status` varchar(100) NOT NULL DEFAULT 'Tentative', `schedule_room_id` int(11) NOT NULL DEFAULT '2', `schedule_active` tinyint(1) NOT NULL DEFAULT '0', `schedule_venue_id` int(11) NOT NULL DEFAULT '1', PRIMARY KEY (`schedule_id`) ) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=16 ; --- Dumping data for table `crc_schedule` -INSERT INTO `crc_schedule` (`schedule_id`, `schedule_course_id`, `schedule_start_date`, `schedule_end_date`, `schedule_day_time`, `schedule_status`, `schedule_room_id`, `schedule_active`, `schedule_venue_id`) VALUES (15, 13, '1993-12-12', '1994-12-12', 'wed', 'In progress', 3, 0, 1); -- --------------------------------------------------------27 | P a g e

-- Table structure for table `crc_sessions` -CREATE TABLE IF NOT EXISTS `crc_sessions` ( `session_oid` int(11) NOT NULL AUTO_INCREMENT, `session_id` varchar(255) NOT NULL DEFAULT '', `session_uid` varchar(15) NOT NULL DEFAULT '', `session_pwd` varchar(15) NOT NULL DEFAULT '', `session_dn` varchar(255) NOT NULL DEFAULT '', `session_time` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP, PRIMARY KEY (`session_oid`) ) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=496 ; --- Dumping data for table `crc_sessions` -INSERT INTO `crc_sessions` (`session_oid`, `session_id`, `session_uid`, `session_pwd`, `session_dn`, `session_time`) VALUES (460, 'ge9g5h6dgr6sf3mg0robkkn1p2', '', '', 'ou=Don Mills,ou=Toronto,ou=Ontario,ou=Canada,o=CRC World', '2013-05-18 19:51:29'), (461, 'ge9g5h6dgr6sf3mg0robkkn1p2', '', '', 'ou=Don Mills,ou=Toronto,ou=Ontario,ou=Canada,o=CRC World', '2013-05-18 19:51:29'), (462, 'ge9g5h6dgr6sf3mg0robkkn1p2', 'maths', 'maths', 'ou=Don Mills,ou=Toronto,ou=Ontario,ou=Canada,o=CRC World', '2013-05-18 19:58:13'), (463, 'ge9g5h6dgr6sf3mg0robkkn1p2', 'maths', 'maths', 'ou=Don Mills,ou=Toronto,ou=Ontario,ou=Canada,o=CRC World', '2013-05-18 19:58:13'), (464, 'ge9g5h6dgr6sf3mg0robkkn1p2', '', '', 'ou=Don Mills,ou=Toronto,ou=Ontario,ou=Canada,o=CRC World', '2013-05-18 19:58:34'), (465, 'ge9g5h6dgr6sf3mg0robkkn1p2', '', '', 'ou=Don Mills,ou=Toronto,ou=Ontario,ou=Canada,o=CRC World', '2013-05-18 19:58:34'), (466, 'ge9g5h6dgr6sf3mg0robkkn1p2', 'maths', 'maths', 'ou=Don Mills,ou=Toronto,ou=Ontario,ou=Canada,o=CRC World', '2013-05-18 19:59:13'), (467, 'ge9g5h6dgr6sf3mg0robkkn1p2', 'maths', 'maths', 'ou=Don Mills,ou=Toronto,ou=Ontario,ou=Canada,o=CRC World', '2013-05-18 19:59:13'), (468, 'btok23o2jcrvfdvtpfvab77kc7', '', '', 'ou=Don Mills,ou=Toronto,ou=Ontario,ou=Canada,o=CRC World', '2013-05-19 14:13:05'), (469, 'btok23o2jcrvfdvtpfvab77kc7', '', '', 'ou=Don Mills,ou=Toronto,ou=Ontario,ou=Canada,o=CRC World', '2013-05-19 14:13:05'), (470, 'vh3roqd5m4be2m1o8551vkrvv6', '', '', 'ou=Don Mills,ou=Toronto,ou=Ontario,ou=Canada,o=CRC World', '2013-05-20 08:42:40'), (471, 'vh3roqd5m4be2m1o8551vkrvv6', '', '', 'ou=Don Mills,ou=Toronto,ou=Ontario,ou=Canada,o=CRC World', '2013-05-20 08:42:40'), (472, '6jj8bqmprdr6ogcjn3sv8m5su0', '', '', 'ou=Don Mills,ou=Toronto,ou=Ontario,ou=Canada,o=CRC World', '2013-05-21 18:00:36'),

28 | P a g e

(473, '6jj8bqmprdr6ogcjn3sv8m5su0', '', '', 'ou=Don Mills,ou=Toronto,ou=Ontario,ou=Canada,o=CRC World', '2013-05-21 18:00:36'), (474, '7r338ouvjsjsi1onk3dal6elv1', '', '', 'ou=Don Mills,ou=Toronto,ou=Ontario,ou=Canada,o=CRC World', '2013-05-21 20:25:44'), (475, '7r338ouvjsjsi1onk3dal6elv1', '', '', 'ou=Don Mills,ou=Toronto,ou=Ontario,ou=Canada,o=CRC World', '2013-05-21 20:25:45'), (476, 'veoqskb2t4hu3gcgmsgoorf5', '', '', 'ou=Don Mills,ou=Toronto,ou=Ontario,ou=Canada,o=CRC World', '2013-05-24 02:52:01'), (477, 'veoqskb2t4hu3gcgmsgoorf5', '', '', 'ou=Don Mills,ou=Toronto,ou=Ontario,ou=Canada,o=CRC World', '2013-05-24 02:52:01'), (478, 'veoqskb2t4hu3gcgmsgoorf5', 'pramruch', 'qwertyuiop', 'ou=Don Mills,ou=Toronto,ou=Ontario,ou=Canada,o=CRC World', '2013-05-24 02:57:42'), (479, 'veoqskb2t4hu3gcgmsgoorf5', 'pramruch', 'qwertyuiop12345', 'ou=Don Mills,ou=Toronto,ou=Ontario,ou=Canada,o=CRC World', '2013-05-24 02:58:02'), (480, 'veoqskb2t4hu3gcgmsgoorf5', 'maths', 'maths', 'ou=Don Mills,ou=Toronto,ou=Ontario,ou=Canada,o=CRC World', '2013-05-24 02:59:01'), (481, 'veoqskb2t4hu3gcgmsgoorf5', 'maths', 'maths', 'ou=Don Mills,ou=Toronto,ou=Ontario,ou=Canada,o=CRC World', '2013-05-24 02:59:01'), (482, 'mp4n1bnm2tf7psckrkmmm0c6o0', '', '', 'ou=Don Mills,ou=Toronto,ou=Ontario,ou=Canada,o=CRC World', '2013-05-31 20:50:59'), (483, 'mp4n1bnm2tf7psckrkmmm0c6o0', '', '', 'ou=Don Mills,ou=Toronto,ou=Ontario,ou=Canada,o=CRC World', '2013-05-31 20:51:00'), (484, '1rlpt6ktsutadk1m2g4chjfkc4', '', '', 'ou=Don Mills,ou=Toronto,ou=Ontario,ou=Canada,o=CRC World', '2013-06-02 05:05:26'), (485, '1rlpt6ktsutadk1m2g4chjfkc4', '', '', 'ou=Don Mills,ou=Toronto,ou=Ontario,ou=Canada,o=CRC World', '2013-06-02 05:05:26'), (486, '1rlpt6ktsutadk1m2g4chjfkc4', 'maths', 'maths', 'ou=Don Mills,ou=Toronto,ou=Ontario,ou=Canada,o=CRC World', '2013-06-02 05:05:42'), (487, '1rlpt6ktsutadk1m2g4chjfkc4', 'maths', 'maths', 'ou=Don Mills,ou=Toronto,ou=Ontario,ou=Canada,o=CRC World', '2013-06-02 05:05:42'), (488, '1rlpt6ktsutadk1m2g4chjfkc4', '', '', 'ou=Don Mills,ou=Toronto,ou=Ontario,ou=Canada,o=CRC World', '2013-06-02 05:05:57'), (489, '1rlpt6ktsutadk1m2g4chjfkc4', '', '', 'ou=Don Mills,ou=Toronto,ou=Ontario,ou=Canada,o=CRC World', '2013-06-02 05:05:57'), (490, 'd25bdv9js1b4rf9pljujuih1b3', '', '', 'ou=Don Mills,ou=Toronto,ou=Ontario,ou=Canada,o=CRC World', '2013-06-02 16:54:50'), (491, 'd25bdv9js1b4rf9pljujuih1b3', '', '', 'ou=Don Mills,ou=Toronto,ou=Ontario,ou=Canada,o=CRC World', '2013-06-02 16:54:50'), (492, 'd25bdv9js1b4rf9pljujuih1b3', 'maths', 'maths', 'ou=Don Mills,ou=Toronto,ou=Ontario,ou=Canada,o=CRC World', '2013-06-02 16:55:10'), (493, 'd25bdv9js1b4rf9pljujuih1b3', 'maths', 'maths', 'ou=Don Mills,ou=Toronto,ou=Ontario,ou=Canada,o=CRC World', '2013-06-02 16:55:10'), (494, 'd25bdv9js1b4rf9pljujuih1b3', 'maths', 'maths', 'ou=Don Mills,ou=Toronto,ou=Ontario,ou=Canada,o=CRC World', '2013-06-02 16:56:56'), (495, 'd25bdv9js1b4rf9pljujuih1b3', 'maths', 'maths', 'ou=Don Mills,ou=Toronto,ou=Ontario,ou=Canada,o=CRC World', '2013-06-02 16:56:56');

29 | P a g e

-- ---------------------------------------------------------- Table structure for table `crc_states` -CREATE TABLE IF NOT EXISTS `crc_states` ( `state_id` int(11) NOT NULL AUTO_INCREMENT, `state_name` varchar(50) NOT NULL DEFAULT '', `state_desc` text NOT NULL, PRIMARY KEY (`state_id`) ) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=6 ; -- ---------------------------------------------------------- Table structure for table `crc_student_schedule` -CREATE TABLE IF NOT EXISTS `crc_student_schedule` ( `student_schedule_id` int(11) NOT NULL AUTO_INCREMENT, `student_schedule_profile_id` int(11) NOT NULL DEFAULT '0', `student_schedule_schedule_id` int(11) NOT NULL DEFAULT '0', `student_schedule_paid` char(1) NOT NULL DEFAULT 'U', `student_schedule_amount` int(11) NOT NULL DEFAULT '0', `student_schedule_questions` tinyint(1) NOT NULL DEFAULT '0', PRIMARY KEY (`student_schedule_id`) ) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=37 ; -- ---------------------------------------------------------- Table structure for table `crc_teacher_schedule` -CREATE TABLE IF NOT EXISTS `crc_teacher_schedule` ( `teacher_schedule_id` int(11) NOT NULL AUTO_INCREMENT, `teacher_schedule_profile_id` int(11) NOT NULL DEFAULT '0', `teacher_schedule_schedule_id` int(11) NOT NULL DEFAULT '0', `teacher_schedule_evaluation` int(11) NOT NULL DEFAULT '0', PRIMARY KEY (`teacher_schedule_id`) ) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=9 ; --- Dumping data for table `crc_teacher_schedule` --

30 | P a g e

INSERT INTO `crc_teacher_schedule` (`teacher_schedule_id`, `teacher_schedule_profile_id`, `teacher_schedule_schedule_id`, `teacher_schedule_evaluation`) VALUES (8, 24, 15, 10); -- ---------------------------------------------------------- Table structure for table `crc_venue` -CREATE TABLE IF NOT EXISTS `crc_venue` ( `venue_id` int(11) NOT NULL AUTO_INCREMENT, `venue_name` varchar(100) NOT NULL DEFAULT '', `venue_desc` varchar(100) NOT NULL DEFAULT '', `venue_shortname` varchar(8) NOT NULL DEFAULT '', PRIMARY KEY (`venue_id`) ) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=2 ; -- ---------------------------------------------------------- Table structure for table `news` -CREATE TABLE IF NOT EXISTS `news` ( `post_id` int(11) NOT NULL AUTO_INCREMENT, `title` text NOT NULL, `blog_entry` text NOT NULL, `updated` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP, PRIMARY KEY (`post_id`) ) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=9 ; --- Dumping data for table `news` -INSERT INTO `news` (`post_id`, `title`, `blog_entry`, `updated`) VALUES (4, 'q', 'qasxcvabcadvbav avg aeiv aeiuvg av av auev aev auv av aiuf aiufga evuia gvauiev agev aiuegv aiuev gaeuiv gaeiuv aeuigv aeugvf aeuf gaeuif caeiuv gaeuigv aeuiv aeiuv auiev aiuev auiv aeiuv aiuev iuaev aiuev iaue viuaev iuae vavqasxcvabcadvbav avg aeiv aeiuvg av av auev aev auv av aiuf aiufga evuia gvauiev agev aiuegv aiuev gaeuiv gaeiuv aeuigv aeugvf aeuf gaeuif caeiuv gaeuigv aeuiv aeiuv auiev aiuev auiv aeiuv aiuev iuaev aiuev iaue viuaev iuae vav', '2013-06-02 04:46:08'), (5, 'w', 'qasxcvabcadvbav avg aeiv aeiuvg av av auev aev auv av aiuf aiufga evuia gvauiev agev aiuegv aiuev gaeuiv gaeiuv aeuigv aeugvf aeuf gaeuif caeiuv gaeuigv aeuiv aeiuv auiev aiuev auiv aeiuv aiuev iuaev aiuev iaue viuaev iuae vavqasxcvabcadvbav avg aeiv aeiuvg av av auev 31 | P a g e

aev auv av aiuf aiufga evuia gvauiev agev aiuegv aiuev gaeuiv gaeiuv aeuigv aeugvf aeuf gaeuif caeiuv gaeuigv aeuiv aeiuv auiev aiuev auiv aeiuv aiuev iuaev aiuev iaue viuaev iuae vav', '2013-06-02 04:46:14'), (6, 'e', 'qasxcvabcadvbav avg aeiv aeiuvg av av auev aev auv av aiuf aiufga evuia gvauiev agev aiuegv aiuev gaeuiv gaeiuv aeuigv aeugvf aeuf gaeuif caeiuv gaeuigv aeuiv aeiuv auiev aiuev auiv aeiuv aiuev iuaev aiuev iaue viuaev iuae vavqasxcvabcadvbav avg aeiv aeiuvg av av auev aev auv av aiuf aiufga evuia gvauiev agev aiuegv aiuev gaeuiv gaeiuv aeuigv aeugvf aeuf gaeuif caeiuv gaeuigv aeuiv aeiuv auiev aiuev auiv aeiuv aiuev iuaev aiuev iaue viuaev iuae vavqasxcvabcadvbav avg aeiv aeiuvg av av auev aev auv av aiuf aiufga evuia gvauiev agev aiuegv aiuev gaeuiv gaeiuv aeuigv aeugvf aeuf gaeuif caeiuv gaeuigv aeuiv aeiuv auiev aiuev auiv aeiuv aiuev iuaev aiuev iaue viuaev iuae vav', '2013-06-02 04:46:19'), (7, 'r', 'qasxcvabcadvbav avg aeiv aeiuvg av av auev aev auv av aiuf aiufga evuia gvauiev agev aiuegv aiuev gaeuiv gaeiuv aeuigv aeugvf aeuf gaeuif caeiuv gaeuigv aeuiv aeiuv auiev aiuev auiv aeiuv aiuev iuaev aiuev iaue viuaev iuae vavqasxcvabcadvbav avg aeiv aeiuvg av av auev aev auv av aiuf aiufga evuia gvauiev agev aiuegv aiuev gaeuiv gaeiuv aeuigv aeugvf aeuf gaeuif caeiuv gaeuigv aeuiv aeiuv auiev aiuev auiv aeiuv aiuev iuaev aiuev iaue viuaev iuae vavqasxcvabcadvbav avg aeiv aeiuvg av av auev aev auv av aiuf aiufga evuia gvauiev agev aiuegv aiuev gaeuiv gaeiuv aeuigv aeugvf aeuf gaeuif caeiuv gaeuigv aeuiv aeiuv auiev aiuev auiv aeiuv aiuev iuaev aiuev iaue viuaev iuae vav', '2013-06-02 04:46:23'); -- ---------------------------------------------------------- Table structure for table `s` -CREATE TABLE IF NOT EXISTS `s` ( `id` int(11) NOT NULL AUTO_INCREMENT, `name` text NOT NULL, `` text NOT NULL, PRIMARY KEY (`id`) ) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=2 ; --- Dumping data for table `s` -INSERT INTO `s` (`id`, `name`, ``) VALUES (1, '', ''); /*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */; /*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */; /*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */;

32 | P a g e

This table structure can be generated by running an automated script file which contains the following code #!/bin/bash # This script is used to initialize an empty MySQL database suitable to be used by Channel-I # The mysql script file, 'crc_database_setup.sql', should be located in the same folder as this script # The default name is '' with '' DB_NAME=crcdb E_SUCCESS=0 33 | P a g e

E_FAILURE=1

read -s -p " for root of MySQL server: " MYSQL_PWD echo echo -n "Creating database $DB_NAME" mysql -u root --=$MYSQL_PWD -e "create database $DB_NAME" if [ $? -eq $E_SUCCESS ] then echo -e "\tdone" else echo "Using existing database ..." fi echo "Granting all privileges on $DB_NAME ..." echo "!!! Make sure that the name and match those found in crc_constants.mod.php !!!" read -p " name: " _NAME read -s -p " : " _PWD echo read -s -p "Confirm : " PWD_CONFIRM echo if [ $_PWD != $PWD_CONFIRM ] then echo "s don't match" exit $E_FAILURE fi mysql -u root --=$MYSQL_PWD -e "grant all privileges on $DB_NAME.* to $_NAME@localhost identified by '$_PWD'" if [ $? -ne $E_SUCCESS ] then exit $E_FAILURE 34 | P a g e

fi echo -n "Creating tables inside database $DB_NAME" mysql -u $_NAME --=$_PWD -D $DB_NAME < crc_database_setup.sql if [ $? -eq $E_SUCCESS ] then echo -e "\tdone" else exit $E_FAILURE fi

echo -e "\n\t*********************************************************************** **********************" echo -e "\t* The default Channel-I name is '' with '' *" echo -e "\t* Please change the default values once logged in from 'Edit profile' menu *" echo -e "\t* Make sure that the MySQL name and match those found in crc_constants.mod.php *" echo -e "\t************************************************************************* ********************\n" exit $E_SUCCESS

35 | P a g e

14. DATA FLOW DIAGRAMS It is a graphical representation of the data. It identifies the path the data will take, what process will take place to it from one from to another. A DFD is a graphical representation of the flow of data through an information system. It can be used to provide a clear representation of any function. It doesn’t provide information about the timing of processes or about whether processes will operate in sequence. Therefore it is different from a flowchart. Data Flow Diagrams are composed of the four basic symbols shown below.     

The External Entity symbol represents sources of data to the system or destinations of data from the system. The Data Flow symbol represents movement of data. The Data Store symbol represents data that is not moving (delayed data at rest). The Process symbol represents an activity that transforms or manipulates the data (combines, reorders, converts, etc.). Any system can be represented at any level of detail by these four symbols.

Data Flow: It is represented by a line arrowhead showing the direction of flow. It shows the flow of information from source to its destination. Information always flows to or from process and may be written, verbal or electronic. Symbol:

Process: A circle represents a process. It shows the procedures those use the data in the system. Symbol:

External Entities : A Rectangle represents an external entity. They either supply data or receive data. They do not process data. Symbol:

36 | P a g e

Data Store: A process references the data store in the system.The data flow is shown by the opened ended rectangles. Symbol:

CONTEXT DIAGRAM: The context diagram is a top-level view of an information system that shows the boundaries and scope. It describes the main objective of the system and the entities involved.

37 | P a g e

38 | P a g e

39 | P a g e

40 | P a g e

15. SCREENSHOTS 15.1 HOME PAGE The home page consists of a flash image at centre which changes by a swirling kind of effect breaking the image in number of parts which can be specified by modifying a XML file associated with it. It consists of all the links details of certain features as provided by the website.

41 | P a g e

XML FILE FOR CONFIGURING FLASH



<Settings>

1000 300 <segments>16 1.2 0.1 easeInOutBack 0 <expand>20 0x111111 0x0064C8 <shadowDarkness>100 25 12 Description Text Ӂ <paragraph>Here you can add a description text for every single image. Ӂ Ӂhyperlinks

42 | P a g e

<paragraph> Description Text Ӂ <paragraph>Here you can add a description text for every single image. Ӂ Ӂhyperlinks <paragraph>. Description Text Ӂ <paragraph>Here you can add a description text for every single image. Ӂ Ӂhyperlinks <paragraph> Description Text Ӂ

43 | P a g e

<paragraph>Here you can add a description text for every single image. Ӂ Ӂhyperlinks <paragraph> Description Text Ӂ <paragraph>Here you can add a description text for every single image. Ӂ Ӂhyperlinks <paragraph> Description Text Ӂ <paragraph>Here you can add a description text for every single image. Ӂ Ӂhyperlinks <paragraph>

44 | P a g e



45 | P a g e

15.2 HOME PAGE IN DIFFERENT COLORS The website can also be accessed in different colour styles. There are 8 colour to choose from which can be chosen as the website is on-line. It is done by linking 8 different CSS files to the webpages.

46 | P a g e

47 | P a g e

15.3 It consists of details about the creator of this website. Along with details it consists of image of the creator which when clicked shows up on the screen enlarged. It is done using an open source package known as lightbox.

48 | P a g e

15.4 US This page consists of a form which is to be filled by the to the s. It asks for name, email, telephone and the message from the . All the details entered are validated by using libraries from Zend Framework. If any detail is not specified it shows up an error message. If the form is successfully submitted, the details are added to table in the database which is then shown up in the .

49 | P a g e

15.5 THANK YOU FOR ING It is a simple page which only shows up when a query is successfully submitted to the server.

50 | P a g e

15.6 PAGE This is the page for the main student teacher management system. s are required to using their name and . Currently lost feature was not implemented in this but it can be added easily at a later stage and doesn’t requires much work. It is a common page for students, teachers and to . Different functionalities will be shown for different levels.

51 | P a g e

15.7 This page is used to a teacher or a student to start using this website. It asks for some simple details from the which are all validated using PHP code.

52 | P a g e

15.8 PAGE This is the page for the . It consists of features like:    

Add a course Add a student Add a student to a course Change the schedule of a class

53 | P a g e

15.9 STUDENT MAIN PAGE This is the main page for the student after logging in. It provides various functionality to students.    

Edit their profile View courses they are ed for. View their attendance View schedule for the class

54 | P a g e

15.10 TEACHER MAIN PAGE This is the main page for teachers after logging in. In this page they can:    

Add a course Add a student to a course Change the schedule of a class Change their profile

55 | P a g e

15.11 MENU FOR BLOG AND It shows up the following functionality:     

Adding new blog post. Modifying an existing blog post Deleting an existing blog post Viewing queries submitted by s Deleting queries This page requires and cannot be accessed without .

56 | P a g e

15.12 ADD NEW POST It requires adding and title and the post. As soon as it is added here, the post appears on the main blog page (blog.php).

57 | P a g e

15.13 MANAGE POSTS Here, s can view existing blog posts, and can update them or delete them.

58 | P a g e

15.14 QUERIES It shows queries submitted at the .php page. can delete the query when it is completed.

59 | P a g e

15.15 BLOG PAGE The blog page is a dynamic page written using PHP code which automatically groups the posts by month and also shows up recent posts in a sidebar. The posts are also displayed in detail in the main centre. The blog page can directly be updated by using the for the blog page. The blog posts can be added, modified and deleted using the .

60 | P a g e

15.16 OTHER SCREENSHOTS

Edi

EDIT COURSE PAGE FI

F

61 | P a g e

Add Student Page

62 | P a g e

Add Course Page

63 | P a g e

View Course Stats Page

64 | P a g e

Enrolment Page

65 | P a g e

Page

66 | P a g e

16. FUTURE WORK    

Addition of lecture and facility Student registration for semester can be done on this It can also be made a portal for alumni interactions It can be developed to be used as a complete college intranet website

67 | P a g e

17. CONCLUSION This website fully meets the objectives of the system which it has been developed. The system has reached a steady state where all bugs have been eliminated. The system is operated at a high level of efficiency and all the teachers and associated with the system understands its advantage. The system solves the problem. It was intended to solve as requirement specification.

68 | P a g e

BIBLIOGRAPHY   

http://www.w3schools.org MySQL Documentation Head First PHP and SQL

69 | P a g e