DECLARATION We “MAKAME, Makame H, STEPHEN, Hilda, HARITH, Fadhil N, CLINUS, Rehema, KHAMIS, Juma H, SAID, Munira, NJAU, Roger P, HAMAD, Asha ALLY, MTAMBUU, Hassan” hereby declare that the project report entitled “ONLINE ASSIGNMENT SUBMISSION SYSTEM” submitted in partial fulfillment of the requirements for the course of “Industrial Training” to the College of Informatics and Virtual Education, is our original work, except for source material explicitly acknowledged, the same or closely related material has not been previously submitted for the same or different courses, and that the submitted soft copy is identical to the submitted hard copy, if both of them are going to be submitted. I also acknowledge that I am aware of University policy and regulations on honesty in academic work, and of the disciplinary guidelines and procedures applicable to breaches of such policy and regulations, as contained in the UDOM website.
I
SUPERVISOR’S CERTIFICATION ONLINE ASSIGNMENT SUBMISSION SYSTEM submitted in partial fulfillment of the requirements for the Industrial Training Project of the College of Informatics and Virtual Education by MAKAME, Makame H, STEPHEN, Hilda, HARITH, Fadhil N, CLINUS, Rehema, KHAMIS, Juma H, SAID, Munira, NJAU, Roger P, HAMAD, Asha ALLY, MTAMBUU, Hassan has worked under my supervision and guidance. Signature………………………………. Name…………………………………… Date………………………………………
II
Contents DECLARATION ................................................................................................................................... I SUPERVISOR’S CERTIFICATION .............................................................................................. II LIST OF FIGURES AND TABLES .......................................................................................................... V ABSTRACT........................................................................................................................................ VI List of symbols and abbreviations.............................................................................................. VII Symbols .................................................................................................................................. VII Abbreviations ........................................................................................................................ VIII ACKNOWLEDGEMENT ..................................................................................................................... IX CHAPTER ONE .................................................................................................................................. 1 INTRODUCTION ................................................................................................................................ 1 1.
OVERVIEW: ................................................................................................................... 1
OBJECTIVES: ................................................................................................................................. 1 Specific objective: .................................................................................................................... 1 SCOPE OF PROJECT ...................................................................................................................... 2 CHAPTER TWO: ................................................................................................................................ 3 LITERATURE SURVEY: ........................................................................................................... 3 CHAPTER THREE ............................................................................................................................... 4 SYSTEM ANALYSIS AND DESIGN ....................................................................................................... 4 REQUIREMENTS SPECIFICATIONS. ............................................................................................... 4 FUNCTIONAL REQUIREMENTS ................................................................................................. 4 NON FUNCTIONAL REQUIREMENTS............................................................................... 5 SYSTEM SPECIFICATION: ...................................................................................................... 5 DEVELOPING AND OPERATING ENVIRONMENT. ..................................................................... 5 Development Environment. ..................................................................................................... 5 System design: ............................................................................................................................. 6 Database design: ...................................................................................................................... 6 Physical design: ....................................................................................................................... 7 Use case scenario: ........................................................................................................................ 7 Use case table: ............................................................................................................................. 8 Use case diagram: .................................................................................................................... 9 Entity relationship table: ............................................................................................................ 10 III
Entity relationship diagram: ....................................................................................................... 13 Database dictionary: .................................................................................................................. 14 DATABASE SCHEMA............................................................................................................. 20 CHAPTER FOUR.......................................................................................................................... 21 SYSTEM IMPLEMENTATION ............................................................................................... 21 APPLICATION DEVELOPMENT: ...................................................................................... 21 P ................................................................................................................................................. 31 SYSTEM TESTING ...................................................................................................................... 39 CHAPTER SEVEN ............................................................................................................................. 40 EVALUATION .................................................................................................................................. 40 Measure of performance: .......................................................................................................... 41 Speed. .................................................................................................................................... 41 Reliability................................................................................................................................ 41 Security: ................................................................................................................................. 41 Comparison: ............................................................................................................................... 41 CHAPTER FIVE ................................................................................................................................ 42 CONCLUSION AND RECOMMENDATION ....................................................................................... 42 Conclusion:................................................................................................................................. 42 RECOMMENDATION ............................................................................................................. 43
IV
LIST OF FIGURES AND TABLES Figure 1: use case diagram ............................................................................................................... 9 Figure 2: Entity relation table ........................................................................................................ 13 Figure 3: login interface ................................................................................................................. 21 Figure 4: Instructor home interface ............................................................................................... 22 Figure 5: Assignment interface ...................................................................................................... 23 Figure 6: Posted assignment interface .......................................................................................... 23 Figure 7: Notes upload interface .................................................................................................. 24 Figure 8: Submits interface ............................................................................................................ 24 Figure 9: Student home interface .................................................................................................. 25 Figure 10: Assignment interface .................................................................................................... 25 Figure 11: Groups creation interface ............................................................................................. 26 Figure 12: Groups interface ........................................................................................................... 26 Figure 13: Notes interface ............................................................................................................. 27 Figure 14: Results interface ........................................................................................................... 27 Figure 15: Archives interface ......................................................................................................... 28 Figure 16: Head of department Home interface ........................................................................... 28 Figure 17: Student Interface .......................................................................................................... 29 Figure 18: Course interface ............................................................................................................ 30 Figure 19: Program interface ......................................................................................................... 31 Figure 20: Administrator home interface ...................................................................................... 31 Figure 21: View Log interface ........................................................................................................ 32 Figure 22: Department interface ................................................................................................... 32 Figure 23: tbl_user ......................................................................................................................... 34 Figure 24: tbl_employee ................................................................................................................ 34 Figure 25: tbl_department ............................................................................................................. 35 Figure 26: tbl_h_department......................................................................................................... 35 Figure 27: tbl_program .................................................................................................................. 35 Figure 28: tbl_course ..................................................................................................................... 36 Figure 29: tbl_course_program ..................................................................................................... 36 Figure 30: tbl_employee_course ................................................................................................... 37 Figure 31: tbl_student.................................................................................................................... 37 Figure 32: tbl_events ..................................................................................................................... 38 Figure 33: tbl_member .................................................................................................................. 38 Figure 34: tbl_question .................................................................................................................. 38
V
ABSTRACT This project focuses on the development of Online Assignment Submission System; the project provides information on things that were acquired during industrial training and how does system help us for our future life. Because in order to award bachelors of degree to the students as the partial fulfillment of the requirements, the CIVE curriculum tends to require students in their each final year of study to work on project report. The main aim of our project is to make sure that we create a system that will provide easy handling of assignment and notes. Also other specific objectives to develop our system include: i.
Assignment submission on time helps to reduce laziness of students on accomplishing several task provided by instructors in class.
ii.
Easy the processing of forming Assignment Groups because student are willing to select themselves to do assignment posted by the instructor in required order of members needed by instructor.
iii.
To increase the confidential of scholar information such as scholar assignment result.
iv.
Provision and distribution of academic material such as notes in better ways. Make the system to be able to keep track of what materials are to be offered in each academic year and the current year of studies.
v.
Digital marking of Assignment simplify work since the manual system is tiresome and time consuming.
vi.
Reduce paper work.
vii.
Increase efficiency of assignment submission and result due to deadline provided at required time.
VI
List of symbols and abbreviations Symbols
Entity
Weak Entity
Attribute
Primary Key
Actor
Arrow show event flow
…………………..
Foreign key
VII
Abbreviations
UDOM
university of Dodoma
CIVE College of informatics and virtual education DBMS
database management system
DB
database
SDLC
system development life cycle
ID
Identification
PK
primary key
FK
foreign key
ER
entity relationship
OASS
Online Assignment Submission System
ARIS
Academic Registration Information System
VIII
ACKNOWLEDGEMENT This was not simply task as it might seems to be; a number of individuals have dedicated time, money, knowledge, social and spiritual support in making this work be. We are very happy and concerned taking this very precious moment to give our sincerely gratitude to those whom have been our great support in doing this tasks. We would like to thanks Mr. Jabera Matogoro who was our supervisor during the industrial training because due to his willingness on using his time to assist us in different issues concerning our project. Also we would like to take this opportunity to appreciate the work done by Mr. Khamis Fereji and other staffs of CIVE for their attention, direction, encouragement and timely intervention and valuable help in the industrial training, data collection analysis and summarization and paper up to this moment. Also our special acknowledgements should go to our fellow students of the college of informatics and virtual education for their full time support starting from requirements gathering up to this moment of preparing this report. Lastly, we take this chance to thank ourselves respectively for support we gave to each other, though working in group is something difficult that can make the core problem of the project. Since working together made us to manage the fullest of this work; and also make us to be great friends that has a great reason for us to thank each other for sacrifices made in fulfilling this tasks, because each of us had sacrificed enough to make this project be.
IX
CHAPTER ONE INTRODUCTION 1. OVERVIEW: Online Assignment Submission System (OASS) is a web based module that allows Teachers and Students to communicate with each other about the assignments and other academic matter easily and rapidly. Students can submit assignments; receive academic material and the result of the assignment anywhere at any time. Teachers can check assignments and not only mark them but also leave their marks about the assignment with some online clicks, and also they will be able to post assignment and notes and other materials to students at anyplace at any time. Many Universities and Colleges are adopting this method to increase Teacher-Student interaction with each other.
OBJECTIVES: The main objective of this project is to create a system that will help in easy interaction between teacher and students in term of academic matter such as assignment. Specific objective:
i.
Submission of assignment on time
ii.
Easy the process of forming Assignment Groups
iii.
To increase the confidentiality of student information such as student assignment result.
iv.
Provision and distribution of academic material such as notes in better ways.
v.
Digital marking of Assignment
vi.
Reduce paper work.
vii.
Increase efficiency of assignment submission and result.
1
SCOPE OF PROJECT OAS will be a web based system for lecturer and scholar in a university. The system will be designed to maximize the performance activities of lecturer and scholar in academic issues by providing tools for submitting assignment, posting assignment results and keep assignment record which would otherwise have to be performed manually with the use of hardcopy such as papers. The OAS designed to allow lecturers to manage and communicate with scholar about academic matters like posting notes, assignment advertisement and its deadline.
2
CHAPTER TWO:
LITERATURE SURVEY: The assessment for many University courses includes some form of assignment which students complete, individually or as groups, and submit for marking. Assignment management involves collection, date stamping, redistribution to tutors for marking, collation of results, and return of assignments to students (Derbyshire, 2000). Tregobov (1998) breaks the process down into four stages: submission, recording, marking, and return. Online assignment submission and management (OASM) involves the use of the World-Wide Web, the Internet and computers to aid this process. The most obvious advantage offered by online assignment management is that it offers faster transportation of assignments than traditional, physical methods. In a study focusing on the use of online assignment management in a programming course Price and Peter (1997) found that students reported a decrease in assignment turnaround time from 2 weeks down to 5 to 7 days Chi-Sang et al (1999) report a reduction in the assignment submission cycle from 2-3 weeks to 1-2 hours. The best result achieved through OASM at CQU resulted in the return of 72 assignments from students throughout Australia and South-East Asia within just over 3 days (1 working day). Also Oliver and Mitchell, 1996 said� resource intensive nature of assessment can often decrease the quality of the feedback provided to student�. Providing timely, meaningful feedback on student progress is essential and can influence student results. Problems associated with traditional assignment management approaches contribute significantly to assignment turnaround time while much of the process of performing assessment is mechanical, repetitious and a perfect candidate for the application of information technology. It is the combination of these factors that is driving interest in online assignment management systems by many educators and institutions throughout the world.
3
CHAPTER THREE SYSTEM ANALYSIS AND DESIGN On the basis of the online assignment system (OASS):
Behavioral: The system operation is quite easy to use and learn due to its simple but attractive interface. But User requires some special training for operating the system.
Technically: The technical requirement for the system is economic also it requires other few software’s in its effective application.
Economically: The developed system is in consideration to College’s and university point of view. It is cost effective in the sense that has eliminated the paper work completely.
REQUIREMENTS SPECIFICATIONS. From the detailed analysis we conduct, several requirements was obtained which we Categorize them into functional and non-functional requirements. FUNCTIONAL REQUIREMENTS
i.
The system should support uploading and downloading of assignment.
ii.
OAS should provide visibility and improve accessibility to publication of assignment information.
iii.
The system should allow scholars to view assignment result.
iv.
The system should be able to reject out-dated assignments if the scholars send assignment after deadline.
v.
The system should allow lecturers to update assignment information.
vi.
The system should be able to provide archive of past assignments information’s for any user of the system who need them.
vii.
The system should allow administrator to give privilege to other users.
viii.
The system should allow head of department to add courses and lecturers.
ix.
The system should allow scholars to view groups arranged by lecturer.
x.
The system should allow users to login and logout.
4
NON FUNCTIONAL REQUIREMENTS i.
Performance: The system is expected to have reasonable short time response. Users should be able to login and be able to get response for their requests in 2-3 seconds.
ii.
Security: All passwords that are generated or accepted must be stored in a database in an encrypted form e.g. in database we use SHA1 because it is more secured and it use a hash code which is 20 bytes long.
iii.
Usability: The system will have the good user interface with more interactive forms and menus that make the system usable to system users.
iv.
Reliability: The system will operate 24 hrs. a day, 7 days a week, while ensuring that information is delivered on time as required.
v.
Accessibility: Users can access their results from any location (as long as they are within a network service reception area).
SYSTEM SPECIFICATION: DEVELOPING AND OPERATING ENVIRONMENT.
Development Environment. In online assignment submission, several hardware and software ware needed for designing, implementing and testing the system. These are: i.
Macromedia Dreamweaver: for development and testing purpose
ii.
MYSQL DBMS for the designing and implementation of database.
iii.
WAMP Server as the server for connecting PHP and MySQL.
iv.
Web browser for testing the functionality of the code developed.
5
Operating Environment: Hardware and software requirement for online assignment submission system are: Minimum hardware requirements: Client side i.
Processor, Pentium II at 500MHZ
ii.
RAM 256MB.
iii.
Free disk space 100MB
Server side i.
Web sphere application server.
ii.
Pentium III at 1GHZ, 256MB, 120MB.
System design: Database design: Logic design: The logical design will base on the conceptual model as follows: i.
Develop a logical data model for each known user interface for the application using normalization principles.
ii.
Combine normalized data requirements from all user interfaces into one consolidated logical database model.
iii.
Translate the conceptual E-R data model for the application into normalized data requirements.
iv.
Compare the consolidated logical database design with the translated E-R model and produce one final logical database model for the application.
6
Physical design: Based on the above logical design the physical design will be performed as follows: i.
Choosing storage format for each attribute from the logical database model.
ii.
Grouping attributes from the logical database model into physical records.
iii. Arranging related records in secondary memory (hard disks and magnetic tapes) so that records can be stored, retrieved and updated rapidly. iv. Selecting media and structures for storing data to make access more efficient.
Use case scenario: a) Publishing of assignment: Lecturer should login into the system by using his/her username and password then he/she click upload button and he/she will browse the document he/she want to post then he/she will click post button. b) Update assignment information: After lecturer has login into the system he/she can update assignment by adding, modify or deleting assignment. c) Adding course: In this case, head of department has privilege to add courses with their attributes by clicking add button, the system automatically insert data to the database. d) Assign lecturers with course: In this case, head of department has privilege to assign lecturers with their respective courses and their attributes by clicking add button, the system automatically insert data to the database. e) Record scholar information Head of the department will have ability to insert and edit scholar information such as program and course the scholar study. f) Downloading of assignment/notes After scholar login into the system, he/she can click assignment or notes button and select the document that he/she want to download.
7
g) Uploading assignment result After a lecturer login to the system, he/she can post assignment results for scholars; on their individual account by just click the post button. h) View assignment result After scholar login to the system, the scholar can view result of assignment through his/her account.
Use case table: USE CASE NAME
ACTORS
DESCRIPTION
Head of department
System will allow lecturer to
System administrator
assign courses and its attribute.
Lecturer
System will allow lecturer to post
System administrator
assignment.
Lecturer
Lecturer should be able to update
information.
System administrator
assignment information.
Downloading assignment
scholar
Scholar
System administrator
download assignment.
administrator
System
Assign courses
Publishing assignment
Update
assignment
Adding users
should
should
be
able
enable
to
the
administrator to add users such as scholar/lecturer to the system. View result
Record
lecturer/scholar
information.
scholar
System should enable lecturer to
lecturer
view all scholar result but scholar
System administrator
will view only his/her result.
Head of department
System should enable head of
System administrator
department
to
insert
or
scholar/lecturer information. Table 1: use case table
8
edit
Use case diagram:
Figure 1: use case diagram
9
Entity relationship table:
ENTITY
RELATIONSHIP
CARDINALITY
tbl_student
1->M
ATTRIBUTES
Sn username
tbl_eventlog
Status
tbl_users
1->M tbl_employee
user_type password
1->M
tbl_student
tbl_user
1->M
studentID
tbl_program
1->M
lname
tbl_course
M->M
fname dateID sn
tbl_employee
tbl_user
1->M
Sn
tbl_course
M->M
Lname
tbl_department
M->1
employeeID deptID
tbl_department
tbl_program
tbl_course
1->M
deptID
tbl_program
1->M
deptName
tbl_employee
1->M
tbl_department
M->1
programID
tbl_student
M->1
deptID
tbl_course
M->M
programName
10
tbl_course
tbl_hdepartment
tbl_department
M->1
courseID
tbl_program
M->M
courseName
tbl_employee
M->M
deptID
tbl_department
1->1
Deptno
tbl_employee
1->1
deptID employeeID
QuestionID tbl_questions
tbl_course
M->1
Deadline Mode coursed posted date question_path
tbl_answer
tbl_course
M->1
answerID
tbl_student
1->M
questionID courseID studentID mark answer_path
tbl_user
1->M
Sn userID
tbl_eventlog
Date Time Event
11
User_type
tbl_group
tbl_student
1->M
studentID
tbl_question
1->M
group_ID questionID mark answer_path
tbl_member
tbl_group
1->1
Sn
tbl_student
1->1
studentID questionID group_ID mark student_contact
Table 2: Entity Relation Table
12
Entity relationship diagram:
Figure 2: Entity relation table 13
Database dictionary: DATABAS E NAME: OASS1 TABLE
FIELD/
DATA
NAME
ATTRIBUTE
TYPE
SIZE NULL
KEY
DESCRIPTION
EXAMPLE
/
NAME
NOT NULL
Sn
Int
-
Primary Student key
User_name
Varchar
25
tbl_user
1
identification
NOT
User
T/UDOM/200
NULL
identification
8/00005
name status
User_type
password
Varchar
Varchar
Varchar
20
15
100
NOT
Whether user
NULL
exist or note
NOT
Previllege of
NULL
user to system
NOT
Secret
NULL
identification of
Active/disable
teacher
Teacher4%
system user
DeptID
Varchar
10
NOT
Primary Identificaton
NULL
key
tbl_departme nt
Cs
number of department
Deptname
Varchar
40
14
NOT
Name of
NULL
department
Computer Science
Fname
Varchar
40
NOT
mwalim
NULL DeptID
Sn
ProgramID
program_name
Varchar
10
Int
Varchar
Varchar
10
10
tbl_program deptID
StudentID
Lname
Varchar
10
Int
Varchar
40
NOT
Foreign
CS
NULL
key
NOT
Foreign
NULL
key
NOT
Primary Program
NULL
key
1
Bsc CS
identification
NOT
Name of the
Bsc Computer
NULL
program
science CS
NOT
Foreign
Department
NULL
key
identification
NOT
Primary Student
NULL
key
NOT
3
identifiaction Name of student
juma
Name of student
Mtaho
NULL fname
Varchar
40
tbl_student
NULL ProgramID
Sn
Deptno
tbl_hdepartm
NOT
deptID
Varchar
10
Int
Int
Varchar
10
ent 15
NOT
Foreign
Program
Bsc Computer
NULL
key
identification
science
NOT
Foreign
Identification w
16
NULL
key
NOT
Primary D identification
NULL
key
NOT
Foreign
Department
NULL
key
identification
4
CS
employeeID
CourseID
Int
Varchar
10
tbl_course course_name
deptID
tbl_course_pr
CourseID
Varchar
Varchar
Varchar
40
10
10
ogram ProgramID
tbl_employee
EmployeeID
Varchar
Int
10
-
_course courseID
QuestionID
Varchar
Int
10
_
tbl_question CourseID
question_name
Mode
Posted_date
Varchar
Varchar
Varchar
10
50
15
Date
NOT
Foreign
employeeidentif
NULL
key
ication
NOT
Primary Course
NULL
key
8
CS205
identification
NOT
Name of the
NULL
course
Visual basic
NOT
Foreign
Department
CS
NULL
key
idenfication
NOT
Foreign
NULL
key
NOT
Foreign
NULL
key
NOT
Foreign
NULL
key
NOT
Foreign
NULL
key
NOT
Primary Assignment
NULL
key
number
NOT
Foreign
Course code
CS205
NULL
key
NOT
Assignment
Assignment
NULL
name
Number4
NOT
Individual/
individual
NULL
Group
NOT
Posted date
8/15/2012
Deadline for
8/18/2012
CS205
Bsc CS
2
CS205
3
NULL deadline
Date
NOT
16
question_path
Varchar
100
NULL
submition
NOT
Storage path
NULL
AnswerID
QuestionID
Int
Int
NOT
Primary Assignment
NULL
key
answer number
NOT
Foreign
Assignment
NULL
key
Question
4
4
number CourseID
Varchar
10
tbl_answer StudentID
Marks
answer_path
Int
Int
Varchar
100
NOT
Foreign
Course code
CS205
NULL
key
NOT
Foreign
Student
176
NULL
key
number
NOT
Assignment
NULL
Marks
NOT
Storage path
10
NULL NotesID
notes_name
Int
Varchar
15
NOT
Primary Note
NULL
key
identification #
NOT
Notes
NULL
identification
tbl_notes
7
Lecture 2a
name CourseID
notes_path
Varchar
Varchar
10
100
NOT
Foreign
NULL
key
NOT
Course code
IS320
Storage path
NULL posted_date
Date
NOT NULL
17
Posted date
8/15/2012
Sn
userID
Int
Int
tbl_events Date
Date
NOT
Primary Serial number
NULL
key
NOT
Foreign
User
NULL
key
identification#
NOT
3
6
Event date
8/15/2012
Event time
11:54:40 AM
NOT
Event
Loggin
NULL
description
NOT
Type of user
NULL Time
Time
NOT NULL
event
usertype
Varchar
Varchar
100
15
student
NULL
group_ID
QuestionsID
Int
int
tbl_Group
NOT
Primary
Group
NULL
key
identification#
NOT
Foreign
Question
NULL
key
identification number
answer_path
varchar
100
NOT NULL
18
storage path
1
2
Sn
int
StudentID int
NOT
Primary
Serial
NULL
key
number
NOT
Foreign
Student
NULL
key
Identificati
tbl_member
5
3
on number
questionID
int
NOT
Foreign
Question
NULL
key
Identificati
8
on number
Mark
float
Null
Mark of
2.3
assignment
varchar
30
student_contact
Table 3: Date Base Dictionary
19
NOT
Contact
NULL
information
089674
DATABASE SCHEMA i.
Tbl_user(sn, user_name, status, user_type, password)
ii.
Tbl_department(deptID, deptname,)
iii. Tbl_employee(employeeID, lname, fname, depatID) iv. Tbl_progrm(programID, progaram_name, deaptID) v.
Tbl_student(studentID, lname, fname, programID,sn)
vi. Tbl_h_department(depyno, depyID, employeeID) vii. Tbl_course(courseID, course_name, deptID) viii. Tbl_course_program(courseID, programID) ix. Tbl_employee_course(employeeID, courseID) x.
Tbl_question(questionID, courseID, question_name, posted_date, deas_line,mode question_path)
xi. Tbl_answer(answerID, questionID, courseID, studentID, mark, answer_path ) xii. Tbl_notes(notesID, note_name, courseID, notes_path, posted_date) xiii. Tbl_event(sn, userID, Date, time, user_type ) xiv. Tbl_group(groupID,questionID,mark,answer_path,studentID) xv. Tbl_member(sn,studentID,questionID,student_contact)
20
CHAPTER FOUR SYSTEM IMPLEMENTATION APPLICATION DEVELOPMENT: In implementing online assignment submission system, we develop user interface and write PHP codes for performing different functionalities required in assignment submission system. The designed interfaces are as the following:Login Form: Figure 13 below is the snapshot of login form where the user of the system must login in order to interact with the system. We have categorized the users of the system into four access levels; these are; i.
Administrator.
ii.
Instructor
iii. Head of department iv. Student User required to enter his/her username and password inorder to get the access to interact with the system.
Figure 3: login interface
21
Home Page Form: Once the user has logged in to the system, he/she first sees the home page form where he/she can be able to view all links that are corresponding to him/her according to his/her privileges.
Figure 4: Instructor home interface
22
Assignment interface : This form will enable instructor to upload assignment to students with deadline of assignment.
Figure 5: Assignment interface
View posted assignment: This form enable instructor to view all posted assignment to student and enable to change deadline of assignment or remove assignment.
Figure 6: Posted assignment interface
23
Notes: This form enable instructor to upload notes and view uploaded notes for specified course.
Figure 7: Notes upload interface
Submit: This enable instructor to view and mark the submitted assignment of students.
Figure 8: Submits interface
24
Student Home form pages:
Figure 9: Student home interface
View assignment: This form enable student to view the assignment posted by instructor from different course that he/she has been register to.
Figure 10: Assignment interface
25
Groups: This enable student to create and join the group if the assignment posted is group assignment.
Figure 11: Groups creation interface
Figure 12: Groups interface
26
Notes: This form enable student to view the posted notes by the teacher of a corresponding course, download the assignment if the student wishes.
Figure 13: Notes interface
Results: This form enable student to view assignment result of all marked assignment.
Figure 14: Results interface
27
Archives: This form enable students to view and download the past course material.
Figure 15: Archives interface
Head of department home page:
Figure 16: Head of department Home interface
28
Staff Form: Head of department is the one who have the ability to add the new staff to the Corresponding department, and he/she is able to view all staff recorded to the system. Figure 23 below is the details on staff of the department:
Student Interface: Head of department is the one who has the ability to add student to the program and he/she is able to view student information to the corresponding department.
Figure 17: Student Interface
29
Course Interface: Head of department is the one who has the ability to add course to the program and he/she is able to view course information to the corresponding department..
Figure 18: Course interface
30
Program Interface: Head of department is the one who has the ability to add program to the corresponding department and he/she is able to view program information to the corresponding department.
Figure 19: Program interface
ADMISTRATOR FORM
Figure 20: Administrator home interface
31
View log interface: This form will enable administrator to view events that was performed by user once they logged in to the system.
Figure 21: View Log interface
Department form: This form will enable administrator to view the existing department and enable him/her add new department and its corresponding head of department.
Figure 22: Department interface
32
User interface: This form will enable administrator to view the information of the existing of the system.
Database Development: In this phase we implement the designed database using MySQL as our relation database Management system. First we create a database in MYSQL known as OASS1 where all objects needed by our database will be stored in this schema. Then we create different kind of objects needed by online assignment submission system such as tables. During creation of those objects we ensure that all constraints are implemented properly and we perform several unit tests to ensure that.
33
OASS1 TABLES: Different tables were created to store and organize data. Each data entered or retrieved from. Online assignment submission system is stored from the database. Below are some of snapshot OASS1 tables:-
Tbl_user: This table stores the data information of all user of the system
Figure 23: tbl_user
Tbl_employee: This tables store the information about the employee of the organization which includes both instructor and administrator of the system.
Figure 24: tbl_employee
34
Tbl_department:This table store all information of the department existing in the system
Figure 25: tbl_department
Tbl_h_department:This table store all information about the head of department that exist in our system. Head of department come from the existing employee of the system.
Figure 26: tbl_h_department
Tbl_program:This table store all information about the program that were existing in the system.Head of department has the responsibility to add and remove program to the corresponding department.
Figure 27: tbl_program
35
Tbl_course:This table store the information about the course that were available in the corresponding department.Head of department has the roles to assign course to the correspong program.
Figure 28: tbl_course
Tbl_course_program:This table were the result of breaking many to many relationship between tbl_course and tbl_program.It store the information of the assigned course to the corresponding program.
Figure 29: tbl_course_program
36
Tbl_employee_course:Also this This table were the result of breaking many to many relationship between tbl_employee and tbl_course.It store the information of the assigned instructor to the corresponding course.
Figure 30: tbl_employee_course
Tbl_student: This table store all information about the student in the corresponding department. The student must first exist to the table of user.
Figure 31: tbl_student
37
Tbl_event:This table store all events of the users done when entering the system
Figure 32: tbl_events
Tbl_member:This table store the information about the student details who form a certain group to the corresponding course.
Figure 33: tbl_member
Tbl_question: This table store the information of the assignment question posted by the instructor and its detail such as deadline of assignment and mode of assignment.
Figure 34: tbl_question
38
SYSTEM TESTING We perform two kinds of test for our system, unit testing and integration testing. In Unit testing each module was tested independently in order to make sure that each module is working properly. This part was always performed soon after the completion of the respective module. The following are some modules of online assignment submission system: i.
Home page creation
ii.
User creation in the system
iii. Connection and authentication of the system iv. Assignment and notes uploaded v.
Assignment and notes downloaded
vi. Group creation vii. Assignment making viii. Setting assignment deadline ix. Integrate different modules to the main page based on user accounts types After developing and testing of the individual modules, all of the above modules were integrated and then tested to identify if there is any malfunctioning of the integrated units as well as any errors that could have been generated. After all the tests carried above, there is no any serious error which has been detected, since the system has conformed to all the requirements mentioned in the analysis stage. At this point the system is ready for deployment.
39
CHAPTER SEVEN EVALUATION The Online assignment submission system will be evaluated to see if it met the system expectations and if it fulfills all requirements as proposed at the early stage of system. Also support and maintenance will be planned due to evaluation feedback and drawbacks will be collected for the second version of the system in order to improve the system efficiency. The result obtained in this system shows that the objectives has been reached, hence the system can help colleges and university instructor and student to have a better way of communicate about assignment and other academic material through different modules, it meets the expectations and it fulfills all requirements as planned . The following are some function that user of online assignment submission system can perform:
i.
Teacher can post assignment to student.
ii.
Student can submit and download assignment through there account.
iii. Instructor can mark assignment and reward marks to student assignment. iv. System allows head of department to add course, program, instructor and student to the corresponding department. v.
System enable users to changes there password
vi. Also system allow student to join and create the assignment group online.
40
Measure of performance: Speed.
Online assignment submission system works at the normal speed with more accuracy and efficiency. Reliability.
The system was developed to be operated with different system’s hardware’s and software.Eg it works through different window and web browser.
Security:
The system is much secured, this is due to the fact that it allow only user who have the access right to interact with the system. Also it uses SHA1 function to encrypt the password of the users.
Comparison: Online assignment submission system is the first system to be developed in our environment but we may compare it by system like ARIS. We created a system that may work as a subsystem to ARIS. Our system can be connected with part of ARIS database and automate assignment result management.
41
CHAPTER FIVE CONCLUSION AND RECOMMENDATION Conclusion: This project has successfully developed a new way of assignment submission system which will help the user to obtain assistance from support when they encounter technical problems and perform other functions such as to enable them communicate with each other within an organization. Although we have successfully completed this project, but we have failed to meet some of the objectives such as automatic asset recoding and file sharing among users. Because we didn’t have enough time to fulfill those objectives; then we failed to look other optional cases of our scope because of fearful to meet the deadline. Hence we believe that we have successfully develop a systematic way for assisting CIVE staff to report their problems request and obtain technical solutions when performing their daily activities. Because when this online assignment submission system will be implemented in ARIS system at UDOM, it will increase work throughput. Due to ICT professionals who are now capable on thinking several ways that helps people working together with their system despite of the distance that is between them.
42
RECOMMENDATION We honestly attracted, enjoyed learned and acquired skills in this practical training because instructors were giving choice students to learn computer language such as vb.net or Php that was interested due to experts effort of teaching. Because they make sure that all students understood well what they were being taught. Practical training is very important to students as it adds not only knowledge and experience to them but also builds skills, confidence and self-trust in making decisions. Again it exposes students to the working environment by preparing them to be hard working and self -disciplined workers. Also student should try to be patient and understandable people, even though we differ in capacity and treatment level in the IPT environment. Students should work hard and keep learning so as to acquire the new challenges and striving for more knowledge. We also recommend that, CIVE administration should train IT staff and increase their number so that they can provide better technical services and all required resource that could be needed for IPT. Not only that CIVE administration should find enough experts and ensure that they are available full time during working hours. Finally, we recommend that our Online Assignment Submission System should be deployed and used in ARIS at UDOM so as to assist staff in fulfilling their daily activities which will lead to the increase of work throughput as much current process have been automated and simplified by our system.
43
44