C&IT- UOG - Project Coordination Office Version: 1.

0
Final Project Deliverable Guide Date: March 2, 2018

Faculty of Computing and Information Technology

University of Gujrat

Student
Attendance Management System

Submitted By:
Sohaib Qaisar (14-28)
Maira Tooba (12)
Sana Rasheed (20)
Maria Akram (112)

Submitted To:
Miss Qurat-Ul-Ain

© Department of Information Technology.

1
 C&IT- UOG - Project Coordination Office Version: 1.0
Final Project Deliverable Guide Date: March 2, 2018

2.1. Introduction
First deliverable is all about planning and scheduling of project. This
deliverable must contain following artifacts:

a. Project Feasibility
b. Project Scope
c. Project Costing
d. Task Dependency Table
e. Critical Path Method Analysis (CPM Analysis)
f. Gantt Chart
g. Introduction to team members
h. Tasks and member assignment table
i. Tools and Technologies
j. Vision Document
k. Risk List
l. Product Features

2.2. Project/Product Feasibility Report

A Feasibility study is a short, focused study which aims to answer a no of questions.
 Does the system contribute the overall objectives of the organization?
 Can be system be implementing using current technology and within cost and Schedule
Constraints.
 Can a system be integrated with systems which are already in place?
So Our Project is Student Attendance Management System and in this we discuss these type of
feasibility Studies.
There are many types of feasibilities:
 Technical
 Operational
 Economic
 Schedule
 Specification
 Information
 Motivational
 Legal and Ethical

2.2.1. Technical Feasibility

In this we use Visual Studio C# language, Microsoft SQL for Database and Rational Rose
for build UML Diagrams. The technical requirement for the system is economic and it does not use
any other additional Hardware and software. Technical evolution must also access whatever the
can be existing system can be upgraded to use the new technology and whatever the organization
has expertise to use it.
2.2.2. Operational Feasibility
The system working is quite easy to use and learn due to its simple but attractive interface.
User requires no special training for operating the system. Technical performance include issues
such as determining whether the system can provide the right information for the Department
personnel student details, and whether the system can be organized so that it always delivers this
information at the right place and on time using intranet services. Acceptance revolves around the
current system and its personnel.

© Department of Information Technology.

2
 C&IT- UOG - Project Coordination Office Version: 1.0
Final Project Deliverable Guide Date: March 2, 2018

2.2.3. Economic 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 system is also time effective because the calculations are automated which are made at the
end of the month or as per the user requirement. The result obtained contains minimum errors and
are highly accurate as the data is required.
2.2.4. Schedule Feasibility
In this we scheduled our Project Activities. The end of our project is 20 April and we can
easily build our project within in time and time is easily manageable.
2.2.5. Specification Feasibility
Registration
Manage Attendance
Course related Information
Updating/Deleting of User
Generate Reports
In our Attendance System these are the Specification Feasibility Study of the Project.
2.2.6. Information Feasibility
They are almost complete requirements we not need to change this requirements. They are
fulfill the requirements relate to the customer.
2.2.7. Motivational Feasibility
There is a need to motivate our staffs and client. For example if a customer want not delete
the data when they enter in the system but it is not possible because the admin have the right to
delete and modify the data. So we are able to convince the client according to their need.
2.2.8. Legal & Ethical Feasibility
Our Project is pure it’s mean we take care of copyrights of the software. We don’t copy the
software to the other organization. And there is a right when the client use the software then the
client have not the right to sale the project to the other customer without our permission.

2.3. Project/Product Scope

The scope of the project is the system on which the software is installed, i.e. the project is
developed as a desktop application, and it will work for a particular institute. But later on the project
can be modified to operate it online. This document covers the requirements for the Student
Management System. This software will provide a graphical environment in which the users of the
system will be able to perform various operations that are associated with storing, marinating,
updating and retrieving Student information. The purpose of this is to guide developers in selecting
a design that will be able to accommodate the full-scale application. The system will capture
information about student’s personal details lectures and the courses. Storing updating and
retrieving in a fast and accurate way.
This project is limited only on how the students attend the class and each module. This application
will manage each student attendance in class.

2.4. Project/Product Costing

A metric is some measurement we can make of a product or process in the overall development
process. Metrics are split into two broad categories:
 Knowledge oriented metrics: these are oriented to tracking the process to evaluate, predict
or monitor some part of the process.
 Achievement oriented metrics: these are often oriented to measuring some product aspect,
often related to some overall measure of quality of the product.

© Department of Information Technology.

3
 C&IT- UOG - Project Coordination Office Version: 1.0
Final Project Deliverable Guide Date: March 2, 2018

Most of the work in the cost estimation field has focused on algorithmic cost modeling. In this
process costs are analyzed using mathematical formulas linking costs or inputs with metrics to
produce an estimated output. The formulae used in a formal model arise from the analysis of
historical data. The accuracy of the model can be improved by calibrating the model to your specific
development environment, which basically involves adjusting the weightings of the metrics.

2.4.1. Project Cost Estimation by Function Point Analysis

Function Point Analysis can provide a mechanism to track and monitor scope creep. Function
Point counts at the end of requirements; analysis, design, code, testing and implementation can be
compared. The function point count at the end of requirements and/or designs can be compared to
function points actually delivered. If the project has grown, there has been scope creep. The amount
of growth is an indication of how well requirements were gathered by and/or communicated to the
project team. If the amount of growth of projects declines over time it is a natural assumption that
communication with the user has improved.

Function points are computed by completing the table shown in the figure below. Five information
domain characteristics are determined and counts are provided in the appropriate table location.
In Attendance Management System we calculate the Cost with the help of Function Point Analysis.

Information domain values are defined in the following manner:

Number of user inputs:

In this the external input value is 5 and we do their complexity level is low and the value of their
complexity is 3.
Number of user outputs:
In this the external output value is 5 and we do their complexity level is low and the value of their
complexity is 4.
Number of user inquiries:
In this the external inquiries value is 6 and we do their complexity level is low and the value of
their complexity is 3.

Number of files:

© Department of Information Technology.

4
 C&IT- UOG - Project Coordination Office Version: 1.0
Final Project Deliverable Guide Date: March 2, 2018

In this the internal logical file value is 5 and we do their complexity level is Average and the value
of their complexity is 10.
Number of external interfaces:
In this the external interface value is 5 and we do their complexity level is low and the value of
their complexity is 5.

Type of Component & Complexity Type Total Answer

5*3 15
5*4 20
6*3 18
5*10 50
5*5 25
Total 128
Then we calculate the UFP (Unadjusted Function Point)
Then we calculate the VAF (vector Adjustment Factor).So in this purpose we select the General
characteristics of the system.
 Data communications
 Distributed data processing
 Performance
 Heavily used configuration
 Transaction rate
 End-user efficiency
 Complex processing
 Reusability
 Installation ease
 Operational ease
 Multiple sites
 Facilitate change
We take the degree of influence is
Average and their Value is 3 and total
General Characteristics is 12.

Calculate VAF

VAF = (TDI * 0.01) + 0.65

= ((12*3)* 0.01) + 0.65
= 0.36 + 0.65
VAF = 1.01

Then we calculate FP (Function Point)

FP = UFP* VAF
= 128* 1.01
FP = 129.01

© Department of Information Technology.

5
 C&IT- UOG - Project Coordination Office Version: 1.0
Final Project Deliverable Guide Date: March 2, 2018

2.5. Task Dependency Table

Task Dependencies
Requirement
Gathering

Requirement Requirement Gathering

Analysis (M1, documentation)
Develop Design Documentation(M2 , Design)
Develop Unit 1& Design
testing (M3 , Registration)
Develop Unit 2& Design
testing (M4 ,Attendance)
Integrate Units & Develop Unit 1& 2 (M5 , Complete
testing Project)

2.7. Gantt chart

2.8. Introduction to Team member and their skill set

Group Member Name Group Member Skills
Sohaib Qaisar Implementation & Design
Maira Tooba Documentation , Design , Testing Manager
Sana Rasheed Implementation & Documentation
Maria Akram Design & Documentation

© Department of Information Technology.

6
 C&IT- UOG - Project Coordination Office Version: 1.0
Final Project Deliverable Guide Date: March 2, 2018

2.9. Task and Member Assignment Table

Task Duration (days) Dependencies

Requirement 8
Gathering

Requirement 15 Requirement Gathering(M1

Analysis documentation)
Develop Design 10 Documentation(M2 , Design)
Develop Unit 1 and 10 Design, documentation
testing (M3 , Registration)
Develop Unit 2 and 8 Design, documentation
testing (M4 ,Attendance)
Integrate Units 10 Develop Unit 1 & 2
Testing (M5 , Complete Project)

Allocation of People to Activities:

Task Engineer
Requirement Gathering Maira, Sana
Requirement Analysis Sohaib
Develop Design Sohaib
Develop Design Unit 1 Sana
Testing Maira
Develop Design Unit 2 Maria
Testing Maira
Integrate Units Sana
Testing Sohaib

© Department of Information Technology.

7
 C&IT- UOG - Project Coordination Office Version: 1.0
Final Project Deliverable Guide Date: March 2, 2018

Staff Allocation:

2.10. Tools and Technology with reasoning

We use different types of Tools for develop our project.
ASP.Net
ASP.Net is a programming language and development that allows you to create programs that
run under the windows operating system. It enables you to develop many different type of applications, itis
a programming language used to create window-based application. It makes it very easy to get the
user interface of the application and running it. It is very easy and it provides a very user-friendly
environment while programming inASP.Net. It provides a vital link to graphical environment and allows
you to develop applications based on standard windows, features: dialog boxes, command buttons, pull-
down menus, scroll bars and selection lists etc. It also allows creating robust applications that fully make
sure of the graphical user interface. It is use for front end design.
MY SQL
It is use for back end design to store the data. RDBMS is the basis for SQL, and for all modern
database systems such as MS SQL Server, IBM DB2, Oracle, MySQL, and Microsoft Access. The data in
RDBMS is stored in database objects called tables. A table is a collection of related data entries and it
consists of columns and rows.
Rational Rose
For Making UML Diagrams we use rational rose because it’s a official software for build
diagrams that’s the reason we use this.

2.12. Risk List

 Family and community factors such as poverty, parental unemployment and/or low
educational attainment, homelessness, transience or living in out-of-home care, Aboriginal or
Torres Strait Islander status, refugee background, family breakdown/relationship issues and
domestic violence.

© Department of Information Technology.

8
 C&IT- UOG - Project Coordination Office Version: 1.0
Final Project Deliverable Guide Date: March 2, 2018

 Personal factors such as physical or mental health issues, disability, behavioral issues, offending
behavior and/or contact with police or justice system, substance misuse or dependency, pregnancy
or parenting, caring responsibilities, and learning difficulties.

 School-related factors such as negative relationships with teachers or peers, unsupportive school
culture, limited subject options and lack of student participation in decision making.

 School factors include issues related to the overall climate, such as a school's size and the attitudes
of administrators, teachers, and other students, as well as the degree to which a school is flexible
in meeting the diverse cultural and learning styles of students. Another important factor is the
manner in which a school deals with truancy among students: Are clear procedures in place and
consistently enforced? Do such procedures have meaningful consequences for students?

 Family factors include lack of parent supervision and/or guidance, poverty, substance abuse in
the home, domestic violence, lack of familiarity with school attendance laws, and varied education
priorities.

 Economic factors include employment among students as well as students who live in single
parent households, have parents with multiple jobs, and whose families lack affordable
transportation and/or childcare.

2.13. Product Features/ Product Decomposition

2.13.1 Registration
2.13.1.1 Description and priority:
Only administration allow to register a student in the data base .Students only see the data stored in the data
base. Administer can update and modify the data in case of any error. Administrator(admin) to log into his
account and has the privileges to do multiple things some of the include adding new student, modifying
student information and modifying student information, deleting of student also there is a provision to
change login password. The priority of this function is very high.
2.13.1.2 Stimulus Response Sequence:
Administer First enter the user name ,Father name ,Address, city, Email address, Phone number, password,
Educational Data ,Past Experience in the form and then this data stored in the database and a message show
that the data is successfully stored in the database.
2.13.1.3 Functional Requirements:
REQ-1: Only administration allow to register a student in the data base.
REQ-2: one student cannot enroll in more than one degree program.
REQ-3: Student’s personal family and Educational data must be entered in the form.
2.13.2 Create Account:
2.13.2.1 Description and priority:
Only the Administrator can be create the account of the users. Users Will be handover their passwords and
user names. Students can only view their attendance. Priority of create account is high. There are two types
of users

© Department of Information Technology.

9
 C&IT- UOG - Project Coordination Office Version: 1.0
Final Project Deliverable Guide Date: March 2, 2018

1: Student
2.13.2.2 Stimulus Response Sequence:
First the account form display on the screen. User enter the name and the password and other require data
in the form.
2.13.2.3 Functional Requirements:
REQ-1: User name and password must be entered in the form.
REQ-2: User name and password must be individually assigned.
REQ-3: User must be registered in the data base.

2: Teacher
2.13.2.4 Stimulus Response Sequence:
Firstly, user account display on screen. User enter name, other personal details and password in account.
User now mark the attendance of student who is present in class.
2.13.2.5 Functional Requirements:
REQ-1: User name and password must be entered in the form.
REQ-2: User name and password must be create separately.
REQ-3: User must be registered in the database.
2.13.3 Login Account:
2.13.3.1 Description and priority:
Login must be necessary for interact to the system .Its priority is high.
2.13.3.2 Stimulus Response Sequence:
User enter the name and password. If the user name and password wrong then notification will be appear
on screen. If the name and password is correct the data will be appear.
2.13.3.3 Functional Requirements:
REQ-1: User name and password must be create separately.
REQ-2: User must be registered in the database.
2.13.4 Take Attendance:
2.13.4.1 Description and priority:
Only the teachers take the attendance. Its priority is high.
2.13.4.2 Stimulus Response Sequence:
Teacher first login the account and then take the attendance .Then save in the database.
2.13.4.3 Functional Requirements:
REQ-1: Teacher must have an account.
REQ-2: Attendance sheet must be provided by System.
2.13.5 Update Attendance:
2.13.5.1 Description and priority:
Only the administrator can be update the attendance. If any student have any query about their attendance
then administrate update this query.
\2.13.5.2 Stimulus Response Sequence:
Student give the application for updating of attendance to administrator. The administrator verify the
attendance through the teacher and then update the attendance.
2.13.5.3 Functional Requirements:
REQ-1: only the administrator can update the query related to attendance.
2.13.6 View Attendance:
2.13.6.1 Description and priority:
The user can view the attendance but they cannot change it. Its priority is low.
2.13.6.2 Stimulus Response Sequence:
Firstly, allow the user log into the system. After log in user only view the current attendance statistics. User
cannot update/modify your status.
2.13.6.3 Functional Requirements:

© Department of Information Technology.

10
 C&IT- UOG - Project Coordination Office Version: 1.0
Final Project Deliverable Guide Date: March 2, 2018

REQ-1: No other privileges are given to the student.

2.13.7 Generate Report:
2.13.7.1 Description and priority:
This attendance report show the percentage of student or by classes. This features offer a variety of search
query option for the report like total no of attendance, no of absent etc. this report generate by administrator.
This priority is average.
2.13.7.2 Stimulus Response Sequence:
Administrator gather the all information of users. After gathering admin making report using attendance
record of students.
2.13.7.3 Functional Requirements:
REQ-1: The detailed of student attendance must be given to the system.

© Department of Information Technology.

11