department of computer science & information technology ......1. in online attendance management...

IT-hub College, Sargodha Version: 1.0

Online Attendance Management System Date: February 20, 2017

© IT-Hub College, Sargodha 1

Department of Computer Science & Information Technology

University of Sargodha

Online Attendance Management System Version 1.0




Table of contents

Chapter 1 : Final Project Proposal.............................................................................................. 5

1.1: Project Title: ....................................................................................................................................... 5

1.2: Project Introduction: .......................................................................................................................... 5

1.3: Project Overview Statement .............................................................................................................. 5

1.4. Goals & Objectives : ........................................................................................................................... 6

1.5. High-level system components: ......................................................................................................... 6

1.6. List of optional functional units: ........................................................................................................ 6

1.7. Exclusions: .......................................................................................................................................... 7

1.8. Application Architecture : .................................................................................................................. 7

1.9. Gantt Chart: ....................................................................................................................................... 7

1.10. Hardware and Software Specifications: ........................................................................................... 7

1.11.Tools and Technologies used with reasoning: .................................................................................. 8

Chapter No 2: First Deliverable .................................................................................................. 9

2.1. Introduction……………………………………………………………………………………………………………………………9

2.2. Project/Product Feasibility Report: .................................................................................................... 9

2.2.1. Technical Feasibility: ................................................................................................................... 9

2.2.2. Operational Feasibility: ............................................................................................................... 9

2.2.3. Economic Feasibility : .................................................................................................................. 9

2.2.4. Schedule Feasibility: .................................................................................................................... 9

2.2.5. Specification Feasibility: .............................................................................................................. 9

2.2.6. Information Feasibility: ............................................................................................................. 10

2.2.7. Motivational Feasibility: ............................................................................................................ 10

2.2.8. Legal & Ethical Feasibility: ......................................................................................................... 10

2.3. Project/Product Scope: .................................................................................................................... 10

2.4. Project/Product Costing: .................................................................................................................. 10

2.4.1. Project Cost Estimation by Function Point Analysis: .................................................................... 10

2.4.2. Project Cost Estimation by using COCOMO’81 (Constructive Cost Model) .................................. 11

2.4.3. Activity Based Costing: .................................................................................................................. 11

2.5. Task Dependency Table: .................................................................................................................. 12

2.6. CPM - Critical Path Method: ............................................................................................................ 12

2.7. Gantt chart: ...................................................................................................................................... 13

2.8. Introduction to Team member and their skill set ............................................................................ 14

2.9. Task and Member Assignment Table: .............................................................................................. 14




2.10. Tools and Technology with reasoning: .......................................................................................... 14

2.11. Vision Document ............................................................................................................................ 15

2.12. Risk List: .......................................................................................................................................... 15

2.13. Product Features / Product Decomposition: ................................................................................. 15

Chapter 3: Second Deliverable For Object Oriented Approach ............................................ 16

3.1. Introduction………………………………………………………………………………………………………………………….16

3.2. Existing System: ............................................................................................................................... 16

3.3 Scope of the System: ......................................................................................................................... 16

3.4 Summary of Requirements: (Initial requirements): .......................................................................... 16

3.5 Identify External Entities: .................................................................................................................. 16

3.6 Capture “shall” Statement: ............................................................................................................... 16

3.7 Allocate Requirements: ..................................................................................................................... 16

3.8 Priorities Requirements: ................................................................................................................... 17

3.9 Requirements Traceability Matrix: ................................................................................................... 17

3.10 High Level Use-case Diagrams: Online Attendance system: ........................................................... 18

3.11. Use-case Diagrams: ........................................................................................................................ 19

3.12.Use case Description: ...................................................................................................................... 20

Chapter 4:Third Deliverable for Object Oriented Approach ................................................ 22

4.1 Introduction: ..................................................................................................................................... 22

4.2 Artifacts which are included in this Chapter: .................................................................................... 22

4.3 Domain Model: ................................................................................................................................. 22

4.4 System Sequence Diagram:............................................................................................................... 23

4.4.1 Admin Sequence Diagram: ......................................................................................................... 23

4.4.2 Teacher Sequence Diagram: ...................................................................................................... 24

4.4.3 Student Sequence Diagram: ...................................................................................................... 25

4.5 Collaboration Diagram: ..................................................................................................................... 26

4.6 Design Class Diagram: ....................................................................................................................... 26

4.7 State machine Diagram: .................................................................................................................... 27

4.8 ER Diagram…………………………………………………………………………………………………………………………….28




TABLE OF FIGURES

Figure 1:3-tier architecture ..................................................................................................................... 7

Figure 2: Gantt Chart............................................................................................................................... 7

Figure 3: Network Diagram ................................................................................................................... 13

Figure 4: Gantt Chart............................................................................................................................. 13

Figure 5: Use case Diagram ................................................................................................................... 18

Figure 6: Use case Diagram ................................................................................................................... 19

Figure 7: Domain Model ....................................................................................................................... 22

Figure 8: Admin Sequence Diagram ...................................................................................................... 23

Figure 9: Teacher Sequence Diagram ................................................................................................... 23

Figure 10: Student Sequence Diagram ................................................................................................. 24

Figure 11: Collaboration Diagram ......................................................................................................... 25

Figure 12: Design Class Diagram ........................................................................................................... 25

Figure 13: State Machine Diagram........................................................................................................ 27

Figure 14: ER Diagram ........................................................................................................................... 28




Chapter No 1: Final Project Proposal

1.1: Project Title

Online Attendance Management System.

1.2: Project Introduction

“ONLINE ATTENDANCEINATION MANAGEMENT SYSTEM” can handle the Online

Attendance record of educational institute. Admin registered the teachers and students. De-

fine the program offered by institute, allocate program and batch to students and categorized

them. Keep result record of all terms online Attendance of all students and generate reports. Also, teachers can manage the grade of each student in an efficient manner. This online system allows

parents to track the progress of their children using the online facility.

1.3: Project Overview Statement

Project Overview:

This Software Requirements Specification provides a complete description of all the func-

tions and specifications of ONLINE ATTENDANCE MANAGEMENT, with the help of this

software admin can easily manage Online Attendance record of students.

Project Overview Statement Template

Project Title: ONLINE ATTENDANCE MANAGEMENT SYSTEM

Project Manager: Sir Muntazir Mehdi

Project Members: Qamar Zeeshan & Imran Farooq

Name Registration # Email Address Signature

Qamar Zeeshan 15MIT120 [email protected]

Imran Farooq 15MIT107 [email protected]

Project Goal: To develop an “ONLINE ATTENDANCEINATION MANAGEMENT SYSTEM” that pro-

vides effective and transparent functionalities for managing Online Attendance record in a small to large

scale progressive educational institutions to automate academic system.

Objectives:

Sr.# Detail

1 It can register teachers and students.

2 Define the programs offered by the institute

3 Teachers assigned to Classes.

4 Manage attendance of students.

Project Success criteria:

The project’s success is based on following criteria:

• Adaptability: The system should be able to adjust to new conditions.

• Availability: The system ensures 24/7 availability.

• Reliability: The system functions according to the stated conditions.

• Response time: The system must have a fast response time.

• Usability: The system provides ease of use, effectiveness, efficiency, learn ability and an overall

users’ satisfaction.




Assumptions, Risks and Obstacles:

• It is assumed that the team members will cooperate and work seriously on this project.

• Non availability of the Internet would be one of the major obstacles.

• It is assumed that the user is familiar with Internet users who are not familiar with these tools

would face difficulty to use the system.

• Users will require special training how to use the functionalities of the system. The level of train-

ing depends on the role of the users. It is also assumed that administrators/managers will require

more training than ordinary users.

• Time, technical expertise & budget constrains may introduce serious obstacles towards the com-

pletion of the project.

Organization Address (if any):

IT-hub, 113/3, Stadium road, Sargodha

Type of project: Research Development

Target End users:

Development Technology: Object Oriented Structured

Platform: Web based Distributed

Desktop based Setup Configurations

Other_____________________

Approved By:

Date:

1.4. Goals & Objectives

Project Goal:

To develop an “ONLINE ATTENDANCEINATION MANAGEMENT SYSTEM” that pro-

vides effective and transparent functionalities for managing Online Attendance record in a

small to large scale progressive educational institutions to automate academic system.

Project Objectives:

To develop an effective and transparent Online Attendance Management System for achiev-

ing following objectives:

1. In Online Attendance management system student may register.

2. In Online Attendance management system teacher may register.

3. In Online Attendance management system admin may register.

4. In this system teacher may generate Online Attendance for w.r.t his subject.

5. Subject wise attendance reports will be managed by the admin

6. Further reports of all Online Attendance may be generated as and when required

1.5. High-level system components

1. Teachers Registration.

2. Students Registration.

3. Management of programs and courses.

4. Management of session.

5. Managing Online Attendance record for complete program.

6. Managing views of Online Attendance.

7. Generate summaries.




Figure 2: Gantt Chart

1.6. List of optional functional units

1. Memory

2. Updating

1.7. Exclusions

It is an Online Attendance management system only, not more.

1.8. Application Architecture

It is 3-tierAapplication Architecture.

Figure 1:3-tier architecture

1.9. Gantt Chart

1.10 Hardware and Software Specifications: Hardware Requirements:

To run the application software of the system in the computer the minimum configuration

required is as below:

1. 233 MHz processor.




2. 512 MB SD-RAM

3. 20 or greater GB Hard-Disk.

4. Monitor: VGA / SVGA

This is the brief introduction of Hardware Configuration for the system. The system can work

in news technology also. It is just telling that system can work with old technology also but, it

consists this minimum configuration of Hardware

Software Requirement

To Handel the system, Administrator requires some software. This software is used for the

development such as coding and testing. Lists are given below:

1. Front End HTML, CSS, Java Script and Bootstrap

2. Back End PHP-MySQL

3. Server Apache Server

4. Design Tool Macromedia Dreamweaver

5. Documentation Tools Microsoft Word -Microsoft PowerPoint

1.11. Tools and Technologies used with reasoning There are following tools and technologies that are used in our system:

Tools:

MS Visio Professional:

We used Visio for use-case diagram, class diagram, domain model, collaboration diagram,

state machine diagram and Sequence diagram.

MS Project Professional;

We used MS Project for Gantt chart.

MS word

For project documentation

Note pad++ (for coding) Web Server – Apache web server or other who concern with PHP codes or scripts. It is basi-

cally used to run the PHP code or file on browser.

Web-browsing Software- Google chrome, Internet Explorer or other

XAMPP- as a virtual server

Technologies:

PHP – It is used for back end tools for the system.

MYSQL - Used to maintain the database. So, you can call it to back-end of system.




HTML & CSS- Both are used for font end because they sport to produce good front end.

Chapter No 2: First Deliverable

2.1. Introduction

First deliverable is all about planning and scheduling of project.

2.2. Project/Product Feasibility Report There are many types of feasibilities:

2.2.1. Technical Feasibility:

The project deals with Online Attendance management. So it is technically feasible.

2.2.2. Operational Feasibility:

The project will facilitate admin to track student’s Attendance and generate reports. So it is

operationally feasible. Each operation will be assigned to specific team member according to

his specialty.

2.2.3. Economic Feasibility:

In economic feasibility we discuss two features. Cost Estimate we define cost estimate with

the help of COCOMO model. We define cost estimate with the help of Function Point Anal-

ysis.

1. Benefit Estimate

2. Tangible benefit:

Those benefit which focus on reduced cost and are responsible for increase in the revenue.

1. Reduced costs

2. Increased revenue

3. Intangible benefit

Information quality and job satisfaction are example of intangible benefits. Cost required in

our project depends upon scope of our project. When scope of project increases, cost also in-

creases. Cost depends upon our hardware configuration, software required in our project and

team member skills cost. According to the budget the cost estimation by using COCOMO

and function point’s analysis is feasible.

2.2.4. Schedule Feasibility:

Schedule feasibility is given below

1. In successful completion of project time schedule plays an important role.

2. All segments of our project are completed within time.

3. We fulfill our requirements easily

2.2.5. Specification Feasibility:

All requirements are completed within time. All requirements are clear. We have no confu-

sion to understand these requirements. New requirements are implemented within time. All




Requirements are the features that our system must have or a constraint that must be accepted

for end users. Specification feasibility also included hardware and software specification re-

quired for completion of our project.

2.2.6. Information Feasibility:

All given information is completing reliable and meaningful. No confusion about require-

ment. Information quality is very good and true information is given. So our software is fea-

sible. Our project is feasible in this context because we collected all related information about

our project.

2.2.7. Motivational Feasibility:

Motivational is also feasible.

2.2.8. Legal & Ethical Feasibility:

We have no legal and ethical issue.

2.3. Project/Product Scope

“ONLINE ATTENDANCEINATION MANAGEMENT SYSTEM” can handle the Online

Attendance record of educational institute. Admin registered the teachers and students. De-

fine the program offered by institute, allocate program and batch to students and categorized

them. Teacher mark attendance of student according to subject. Keep subject wise result rec-

ord of attendance of all students and generate reports.

2.4. Project/Product Costing

2.4.1. Project Cost Estimation by Function Point Analysis:

Type of component Low Average High Total

External Input 0*4=0 4*0=0 4*6=24 24

Internal Output 3*0=0 0*3=0 4*3=12 12

External Inquire 2*5=10 0*5=0 4*0=0 10

Internal logical Files 0*6=0 1*17=17 0*14=0 17

External Interface File 0*2=0 2*8=16 0*12=0 16

Total 79

Compute function points (FP), the following relation;

FPest=79*[0.65+0.01*(32)]

FPest=79*[0.65+0.01*32]

FPest=51.69

Serial # Complex Technology Term Scale

1 Data Communication 5

2 Distributed data processing 0

3 Performance 4

4 Heavily used configuration 2

5 Transact rate 1




6 Online data entry 0

7 End-user Efficiency 4

8 Online update 0

9 Complex Processing 3

10 Reusability 2

11 Installation ease 4

12 Operational ease 4

13 Multiple Sites 0

14 Facilitate change 3

Sum(Fi) 32

2.4.2. Project Cost Estimation by using COCOMO’81 (Constructive Cost Model)

Basic COCOMO

Type Effort Schedule

Organic PM= 2.4 (KLOC)1.05 TD= 2.5(PM)0.38

Semi-Detached PM= 3.0 (KLOC)1.12 TD= 2.5(PM)0.35

Embedded PM= 2.4 (KLOC)1.20=2.4(6)1.05=15.12

TD= 2.5(PM)0.32=2.5(15.12)0.38=14.364

PM= person-month (effort)

KLOC= lines of code, in thousands

TD= number of months estimated for software development (duration)

Intermediate COCOMO

Type Effort Organic PM= 2.4 (KLOC)1.05 x M

Semi-Detached PM= 3.0 (KLOC)1.12 x M

Embedded PM= 2.4 (KLOC)1.20 x M

PM= person-month

KLOC= lines of code, in thousands

M.- reflects 15 predictor variables, called cost drivers

The schedule is determined using the Basic COCOMO schedule equations.

People Required = 15.12/14.364=1.05263

2.4.3. Activity Based Costing:

Activity Cost

Feasibility Report

6000

Cost Estimation by Function Point Analysis 4000

Cost Estimation by COCOMO Model

5000

Activity based Costing

6000




Critical Path Method

5000

Task Dependency and Duration

8000

Vision Document

5000

Risk List

7000

Allocate Requirement

10000

Design Interface

6000

Modeling

10000

Test and Evaluate

12000

Improve Test

10000

Show Result

15000

Total Cost 107000

2.5. Task Dependency Table

Task# Task Dependencies

T1 Proposal None

T2 Feasibility Report T1

T3 Cost Estimation T2

T4 System Specification and Analysis T2

T5 Domain Model T1,T2

T6 Allocate Requirements None

T7 Application Development T4,T5

T8 User T7

T9 Processing T7,T8

T10 Testing T9

T11 Showing T7,T8,T9,T10

2.6. CPM - Critical Path Method

1. Specify the Individual Activities

Individual activities are as follow:

1. Planning

2. Analysis

3. Logical design

4. Physical design

5. Testing

6. Implementation

7. Deployment




Figure 4: Gantt Chart

2. Determine the Sequence of the Activities

All activities are dependent on each other like, first planning and then go to second activity

which is named as Analysis, and then logical designing after it physical designing, then test-

ing it all and then deployment.

3. Draw the Network Diagram

Figure 3: Network Diagram

4. Estimate Activity Completion Time:

Activity Duration ES EF LS LF TS FS

Planning(A) 5 0 5 0 5 0 0

Analysis (B) 3 0 3 3 6 3 2

Logical designing (C) 8 5 13 5 13 0 0

Physical designing (D) 7 5 12 6 13 1 1

Testing (E) 7 0 7 6 13 6 6

Deploy-ment (F) 4 13 17 13 17 0 0

5. Identify the Critical Path:

The critical path is the longest-duration path through the network. The significance of the

critical path is that the activities that lie on it cannot be delayed without delaying the project.

Because of its impact on the entire project, critical path analysis is an important aspect of pro-

ject planning. Critical path is: (A,B,C,D,E,F)

2.7. Gantt chart

B C D E F A




2.8. Introduction to Team member and their skill set

Name Roll No Skill

Qamar Zeeshan 15MIT120 HTML, CSS, PHP, JavaScript

Imran Farooq 15MIT107 HTML, CSS, PHP, MySQL

2.9. Task and Member Assignment Table

Indication of amount of work of each member is expressed in terms of Task and its allocation

by the following given table.

Task# Task Dependencies

T1 Proposal None

T2 Feasibility Report T1

T3 Cost Estimation T2

T4 System Specification and Analysis T2

T5 Domain Model T1,T2

T6 Allocate Requirements None

T7 Application Development T4,T5

T8 User T7

T9 Processing T7,T8

T10 Testing T9

T11 Showing T7,T8,T9,T10

Allocation of People to Activities:

T1 Imran

T2 Imran

T3 Imran

T4 Qamar Zeeshan

T5 Qamar Zeeshan

T6 Imran

T7 Qamar Zeeshan

T8 Qamar Zeeshan

T9 Imran

T10 Qamar Zeeshan

T11 Imran

2.10. Tools and Technology with reasoning

There are following tools and technologies that are used in our system:

Tools:

MS Visio Professional:We used Visio for use-case diagram, class diagram, domain model,

collaboration diagram, state machine diagram and Sequence diagram.




MS Project Professional:We used MS Project for Gantt chart.

MS word: For project documentation

Dream viewer: (for coding) Web Server:Apache web server or other who concern with PHP codes or scripts. It is basi-

cally used to run the PHP code or file on browser.

Web-browsing Software: Google chrome, Internet Explorer or other

XAMPP: As a virtual server

Technologies:

PHP:It is used for back end tools for the system.

MYSQL:Used to maintain the database. So, you can call it to back-end of system.

HTML & CSS: Both are used for font end because they sport to produce good front end.

2.11. Vision Document



software admin can easily manage Online Attendance record of students. Admin registered

the teachers, courses and students. Define the program offered by institute, allocate program

and batch to students and categorized them. Keep subject wise record of Attendance of all

students and generate reports.

2.12. Risk List

We may encounter following risks:

1. Software error risk

2. Progress risk

3. Internet unavailability

4. Content

2.13. Product Features / Product Decomposition

Our product features are as follows:

1. An Online Attendance Management

2. Web based

3. Mobile Accessible

4. User-friendly

5. Easy to use




Chapter No 3: Second Deliverable for Object Oriented Approach

3.1 Introduction

Requirements engineering process provides the appropriate mechanism for understanding

what the customer wants, analyzing need, assessing feasibility, negotiating a reasonable solu-

tion, specifying the solution unambiguously, validating the specification and managing the

requirements as they are transformed into an operational system. In this chapter we discuss

scope of the system, summary of requirements, external entities, shall, will statements, use

case diagram and etc.

3.2. Existing System

No existing system.

3.3 Scope of the System

Admin registered the teachers, courses and students. Define the program offered by institute,

allocate program and batch to students and categorized them. Keep subject wise record of

Attendance of all students and generate reports.

3.4 Summary of Requirements: (Initial requirements)



software admin can easily manage Online Attendance record of students.

3.5 Identify External Entities

The main external entities are following:

1. User

2. Admin

3. Student

4. Teacher

3.6 Capture “shall” Statement

Para# Initial Requirements

1.0 System shall be a website.

1.0 System shall give user interface and log in option too.

1.0 System shall has a form to enter data for registration.

1.0 System shall have a database to save data.

1.0 System shall save the data entered by the user.

1.0 Shall System allow staff to manage attendance record?

1.0 System contain filters to track result as per user requirement.




3.7 Allocate Requirements

Para# Initial Requirements Use case name

1.0 System shall register students and teachers Registration

1.0 System shall manage sessions of students Manage session

1.0 System shall manage programs offered by institute. Manage programs

1.0 System shall manage record of courses. Manage courses

1.0 System shall manage Online Attendance record. Manage Online At-

tendance

1.0 System shall manage records views of students. Manage results

1.0 System shall generate result reports of students. Generate summaries

3.8 Priorities Requirements

Para# Rank Initial Requirements Use case

ID

Use case Name

1.0 Highest System will register students and teachers Uc.1 Registration

1.0 Highest System will manage sessions of students Uc.2 Manage session

1.0 Highest System will manage programs offered by

institute.

Uc.3 Manage pro-

grams

1.0 Highest System will manage record of courses. Uc.4 Manage courses

1.0 Highest System will manage Online Attendance

record w.r.t to subject.

Uc.5 Manage Online

Attendance

1.0 Highest System will manage records of students. Uc.6 Manage results

1.0 Highest System will generate result reports of stu-

dents.

Uc.7 Generate result

card

3.9 Requirements Traceability Matrix

Sr.No Para

no

System specification test Build Use case name

1 1.0 System will register students and

teachers

B1 Registration

2 1.0 System will manage sessions of stu-

dents

B2 Manage Online At-

tendance

3 1.0 System will manage programs offered

by institute.

B3 Manage session

4 1.0 System will manage record of courses. B3 Manage program

5 1.0 System will manage Online Attend-

ance record.

B3 Manage course

6 1.0 System will manage results records of

students.

B3 Manage results

7 1.0 System will generate result reports of

students.

B4 Generate result




3.10 High Level Use-case Diagrams: Online Attendance Management system

Figure 5: Use case Diagram




3.11. Use-case Diagrams

Figure 6: Use case Diagram




3.12. Use case Description

1: Registration:

Use case name: Registration Use case ID: 1

Pre-Conditions: Web page is opened

Basic flow: Enter teacher/student detail.

Alternative flow : Not done.

Post -Conditions: Registered.

2: Manage Session:

Use case name: Manage Session Use case ID: 2

Pre-Conditions: Registered.

Basic flow: Enter session details

Alternative flow : Not done

Post -Conditions: Session details are entered

3: Manage Program:

Use case name: Manage Program Use case ID: 3

Pre-Conditions: Registered

Basic flow: Enter program details.


Post -Conditions: Program details are entered

4: Manage Courses:

Use case name: Manage Courses Use case ID: 4


Basic flow: Enter courses details.


Post -Conditions: Courses details are entered

5: Manage Online Attendance:

Use case name: Manage Online

Attendance

Use case ID: 5


Basic flow: Enter Online Attendance details.





Post -Conditions: Online Attendance details are entered

6: Manage Attendance:

Use case name: Manage Results Use case ID: 6

Pre-Conditions: Online Attendance details are available

Basic flow: Select Online Attendance


Post -Conditions: Online Attendance details are entered

7: Generate View Summaries:

Use case name: Generate result card Use case ID: 7

Pre-Conditions: Result details are available

Basic flow: View result

Alternative flow : Not Available

Post -Conditions: Reports are generated




Chapter No 4: Third Deliverable for Object Oriented Approach

4.1 Introduction

This chapter includes the software design. Till this chapter, analysis of the system is done, the

current situation of the domain is known, we are ready to go ahead for the solution of the

problem in the domain.

4.2 Artifacts which are included in this Chapter

1. Domain Model

2. System Sequence Diagram

3. Collaboration Diagram

4. Design Class Diagram

5. State Transition Diagram

4.3 Domain Model

Figure 7: Domain Model




4.4 System Sequence Diagram

4.4.1 Admin Sequence Diagram:

Figure 8: Admin Sequence Diagram

4.4.2 Teacher Sequence Diagram

Figure 9: Teacher Sequence Diagram




4.4.3Student Sequence Diagram:

Figure 10: Student Sequence Diagram




4.5 Collaboration Diagram

Figure 11: Collaboration Diagram

4.6 Design Class Diagram

Figure 12: Design Class Diagram




4.7 State machine Diagram

State Machine Diagram: Admin:

Teacher:

Student:

Figure 13: State Machine Diagram




4.8 ER Diagram

Figure 14: ER Diagram

department of computer science & information technology ......1. in online attendance management...

Documents