Lolomboy Attendance Monitoring System With Barcode Scanner

STI COLLEGE BALAGTAS
Mc Arthur Highway, Borol 1st, Balagtas, Bulacan
ATTENDANCE MONITORING SYSTEM FOR

LOLOMBOY ELEMENTARY SCHOOL USING BARCODE SCANNER.
A Project Presented to the faculty of STI College Balagtas

in Partial Fulfilment of the Requirements
for The Degree of
Bachelor of Science in Computer Engineering
By:
Venus, Alexander M.
Bitara, Rassel P
October 2018
TABLE OF CONTENTS
1. Introduction
1.1. Background of the Study ………………………………………………………………………………1-1
1.2. Statement of the Objectives …………………………………………………………………………..1-2
1.2.1.General Objectives ……………………………………………………………………………….1-2
1.2.2.Specific Objectives …………………………………………………………………………….....1-2
1.3. Significance of the Study …………………………………………….………………………………..1-3
1.4. Scope and Limitation of the Study ……………………………………….……………………….…..1-4
2. Methodology
3. Data Gathering Procedures and Output
4. The Existing System
4.1. Company Background …………………………………………………………………………………4-1
4.2. Description of the System ……………………………………………………………………………..4-1
4.3. Data Flow Diagram ……………………………………………………………………………………..4-2
4.4. Data Dictionary ………………………………………………………………………………………….4-2
4.5. Problem Areas ………………………………………………………...………………………………..4-3
5. The Proposed System
5.1. System Overview ………………………………………………………………………………………5-1
5.2. Process Specification ………………………………………………………………………………….5-2
5.2.1.Data Flow Diagram ……………………………………………………………………………….5-2
5.2.2.Data Dictionary ……………………………………………………………………………………5-3
5.3. Data Specification ……………………………………………………………………………………...5-4
5.3.1.Entity Relationship Diagram …………………………………………………………………….5-4
5.3.2.Tables/Files Layout ………………………………………………………………………………5-5
5.4. Screen Layout/Specifications …………………………………………………………………………5-5
5.5. Report/Form Specifications ……………………………………………………………………………5-6
5.6. Program/Module Specifications ……………………………………………………………………..5-10

6. System Coding Prototype
6.1. Programming Language ………………………………………………………………………………6-1
6.2. Special Purpose Language Tools ……………………………………………………………………6-1
7. System Testing Plan
7.1. Testing Stages ………………………………………………………………………………………….7-1
7.2. Testing Schedules ……………………………………………………………………………………...7-2
8. System Implementation Plan
8.1. Resource Requirements
8.1.1.Hardware Requirements …………………………………………………………………………8-1
8.1.2.Software Requirements ………………………………………………………………………….8-1
8.1.3.Human Requirements ………………………………………………………………………...….8-1
8.2. Implementation Plan
8.2.1.Site Preparation …………………………………………………………………………………8-3
8.2.2.Personnel Training ………………………………………………………………………………8-3
8.2.3.System Conversion ……………………………………………………………………………...8-3
8.2.4.Data Conversion …………………………………………………………………………………8-3
8.2.5.Implementation Schedule ………………………………………………………………………8-3
9. System Maintenance Plan
Appendices
BIbliography
CHAPTER I
1. Introduction
“Let’s just do attendance then skip classes today.”
This is an everyday occurrence in our class, giving teachers and parents a good amount
of headache especially in Lolomboy Elementary School. Me and my partner hypothesize and
come up with a solution-the Monitoring System with Barcode.
The main difference between manual and computerized systems is speed. Software
processes data and creates reports much faster than manual systems.
The system of managing attendance is efficient only if it is real-time. It requires quick
access and fixes by the admins, instead of the hassles of having manual laboring every month
end. The automated attendance monitoring system works on all facets with effortlessness and
effectiveness.
In the end of the study, the researchers tend to improve the existing system of the
chosen beneficiary.
1.1 Background of the Study
Our beneficiary is required to take student attendance every school day using log
book/attendance book. For half-day bi-sessional (AM/PM) primary schools, attendance is usually
taken once a day.
As per our investigation we identified specific problems like:
• Loss of records due to storage
-Records can be lost due to negligence of the holder or some other
means.
Attendance Monitoring System for Lolomboy Elementary School using Barcode Scanner
1-1
• Inefficient archiving
- Inefficient archiving due to lots of paperwork accumulated overtime.
• Reporting
-Reporting of records is also lacking in the system of our beneficiary
because of transferring all data from one record to another manually.
• Lack of Maintenance
-Due to the traditional approach of the old system, maintenance is
somewhat lacking and hard to do.
• Easy modification from unauthorized personnel
-Unauthorized personnel can manipulate the record, making it not a
trusty source of information
• Time-consuming
-For a school like our beneficiary, time is an important matter and
additional labor due to this manual labor can make things go awry more so in times where there
are events or occasions.
1.2 Statement of Objectives
To address the problems, we formulate the following objectives to tackle them:
1.2.1 General Objective
• To create a computerized monitoring system with barcode scanner
that will replace the traditional way of monitoring student
1.2.2 Specific Objective
• To make a database for the system to act as a storage of data
1-2
o Storing data to a database will increase all data’s security
and overall durability.
• To create a module that have a search option for easier access of
records
o Having this module will shorten the time needed to search
for a specific record/s.
• To create a module that have the ability to make and print reports
o To grant the ability to create and print reports will lighten the
burden of the authorized personnel to get the data of the
monitoring system.
• To make a module that have an option for easy maintenance
o For the users to apply a quick but effective maintenance for
the system and data.
• To make a module for a login option to prevent data manipulation by
unauthorized personnel
o This is frequent on traditional methods so we are adding a
login option so the data are free from malicious intents.
• To make all operation automatic as much as possible
o So the users can use the system easily and effectively.
1.3 Significance of Study
The study of Computerized Monitoring System using Barcode Scanner will
benefit the following:
Teachers – it will help them reduce their workload making them efficient in other works
Staffs – the guard and janitorial staff in school will no longer do additional labors of
finding the students whenever they are known missing in class
1-3
Students – it will benefit them of having their records safe and intact in times where
additional info maybe needed
Parents – it will allow the parents to access and get feedbacks from teachers about their
son/daughter
Developers – it will benefit the developers because they fulfilled the task and
requirements set by the owner
Future Researchers – because it will serve as a guide and reference in future studies
1.4 Scopes and Limitation
Scopes
• Monitoring – This module serves as a main module of the study. This
serves as the recorder of time in-time out of the students
• Maintenance – This module can add, edit, and archive the data of the
students.
• Records – This module can print the records of the monitoring module
and barcodes of the students
• Help – This module can serve as the guide and reference of the owner
and users
• About – This module provides the description and contact details of the
developer
Limitation
• This system is only for the students of the Lolomboy Elementary School,
not for other school students or its staff.
• This system doesn’t have a module to create another account per
request of the beneficiary
• The system is also an offline application
1-4
CHAPTER II
2. Methodology
Developing a system include several methodologies that will serve as the roadmap of the
researches along the development. In this study, the researchers use the Spiral Model. The selected
model is the best among other methodologies because of its versatility and nature of needing the
developer and beneficiary to further improve the system as it is being developed.
Figure 2.1 Spiral Model
Spiral model includes the following parts, with emphasis on risk analysis:
• Planning – requirements and information are gathered in this phase like Business
Requirement Specifications and System Requirement Specifications. The system analyst
also makes the objectives on this phase and tasks and schedule by the team leader.
2-1
• Risk Analysis – this is the phase where risk and problems are identified and solutions are
formed. The whole team is involve to try solve the problem. A prototype will be created in
this phase.
• Development phase – the system is being developed in this phase and tested at the end
of the phase. This is also the phase where you will start to code the system and test to
identify risks not identified on the second phase. The builder will also base the program
base on the designer’s design.
• Iteration – in this phase, the client will decide if the prototype is acceptable to be
continued or to be rejected and start the project again.
If the project is rejected, the process will be repeated but now based on the previous prototype
until an operational prototype is accepted by the client.
2-2
CHAPTER III
3. Data Gathering Procedures and Output
An efficient Attendance System will do well with thought-out specific requirements and all
possible risks and problems is solved as much as possible. To make that a possibility, there are
procedures to be followed to gather information. For formality and legality, each technique will have step-
to-step procedures. Here are some techniques that researchers may use:
• Brainstorming: This method is used to get a list of all project lists. All ideas are generated
with the help of a facilitator through an open discussion and mass interviewing
techniques. Commonly, the brainstorming technique can be done during a scheduled
meeting with peers, individual brainstorming, or even at an informal meeting.
• Delphi Technique: This technique in project management requires the presence of a
facilitator that gives out questionnaires to solicit different ideas. The responses are
summarized and recirculated to the participants.
• Root cause Analysis: One of the information gathering techniques is the root cause
analysis. It is used in identifying problems and its underlying causes thus developing a
preventive action.
• Interviewing: Stakeholders, participants, and experts are interviewed to identify risks.
Among the techniques, the most appropriate to use for this study to gather information is the
interview. The list below are the step-by-step procedures the researchers taken to gather the specifics
they want to get:
• We observe and studied first the school and how they work on their attendance system.
• We formulate questions that will reveal the problems of the existing system.
• The person to be interviewed is identified.
• We made a scheduled interview with the contact person.
• Before the interview, we give the interviewee some sample questions to get ready.
3-1
• The whole interview is recorded using voice record.
• We informed the contact person if there will be a follow up interview.
The transcript of the interview is included in the study (see the appendices) for validation. The
following details are gathered through interview:
• The old system is paper based.
• Checking the actual records of attendance is hard because old documents are being
superseded by new ones.
• Students are abusing the old system’s flaws.
• The whole process is done manually and takes time to finish.
• The old system is inaccurate and slow in terms of generating reports about the
attendance.
The information gathered are used for analysis and developing sub systems in the main system.
These are also the problems the beneficiary wants us to solve for them
3-2
CHAPTER IV
4.The Existing System
4.1 Company Background
Lolomboy Elementary School is established at year 1921 consisting of only 3 classrooms
with the supervision of Ambrosio Candelaria as its principal. The school only offers Grade I to IV in its early
years. American soldiers serve as the school teachers until the year 1927.
At year 1941, the war broke out and the school is temporarily closed and only reopened
after the war. At year 1948-1950, Teofilo A. Fernando take over as the school’s principal.
As education booms, students also increased in population. Students from different areas
like Bunlo, Bundukan, Igulot and Duhat go to Lolomboy Elementary School just to study. The school is got
Grade V – VI at year 1950-1960 and got planned to build a high school building in year 1970-1974.
Lolomboy Elementary School have 9000 sq.meters in size, composed of 17 buildings and
45 classrooms.
4.2 Description of the System
The current system being used in Lolomboy Elementary School is outdated and paper-
based. A gate guard is the sole responsible for checking the student’s ID and uniform, making the system
unreliable due to the nature of it. The system also doesn’t have a reliable database, just using a logbook
for the holding the records of rule breaking students which is not secured like a database.
4-1
4.3 Dataflow Diagram
Student Peripherals Guards Guard

Traditional
System of LES
Approval of Entry
Guard
Checking
0.1
Students Peripherals Approval of Entry Students

Checking of
Peripherals
Violations
Guard
Violations
Approval of Entry
0.2
Logbook Violations
Record to
Logbook
4.4 Data Dictionary
Name = First Name +(Middle Initial)+ Last Name
First Name = {Legal Character}
4-2
Middle Name = {Legal Character}
Last Name = {Legal Character}
Legal Character = [A-Z|a-z|0-9|’|-]
Student Number = {Legal Character}
4.5 Problem Areas
• Repetitive encoding to create a report
Most of the times, just to produce a good report, the admin of the school
must compile all records from each grade to a single Excel workbook and must
check every record to avoid mistakes. This leads to unnecessary delays or errors
leading to wasted hours of work.
• Manual archiving is exposing the records to hazards and is prone to misplacement
Storing records in this method leads to data loss and sometimes
unauthorized modification from other personnel. This leads to data leaks and hard
to be prevented.
• Hard to access records
Searching for a specific record is hard to do considering the piles of paper
the you must pass through to get that specific record.
4-3
CHAPTER V
5.1 System Overview
The proposed system completely overhauls the current system because its computerized
environment and processes. Some processes are combined to a single working place to increase efficiency.
The application of the proposed system will greatly alleviate the burden of the admin’s work than
the current one. It will also have a security measure that will prevent unauthorized changes in the data.
Maintenance (mainly adding, deleting and archiving) is easier in the proposed system because of
the processes designed specially for it. Every future circumstance is programmed to react to events
regarding user inputs. If ever there is an error after implementation, it is made sure that it is handled and
will not make any bugs in the system.
Reports are also easier to make because of the module made to handle it. Monitoring is also
automated it the proposed system, making the monitoring of the students automated and well handled in
the future.
5.2 Process Specification
5.2.1 Data Flow Diagram
5-1
5-2
5.2.2 Data Dictionary
Student =StudID + FirstName + (MiddleInitial) + LastName + Age + Gender + Address +
Grade + (ContactNumber) + GuardianName + GuardianCN + Status + EncodedId + Name + StudImg
StudID = {Legal Character}
FirstName = {Legal Character}
MiddleInitial = {Legal Character}
LastName = {Legal Character}
Age = {Valid Numerical Character}
Gender = {Legal Character}
Address = {Legal Character}
Grade = {Legal Character}
ContactNumber = {Valid Numerical Character}
GuardianName = {Legal Character}
GuardianCN = {Valid Numerical Character}
Status = {Legal Character}
EncodedId = {Legal Character}
Name = FirstName + MiddleInitial + LastName
StudImg = {Image}
Legal Character = [A-Z|a-z|0-9|’|-]
Valid Numerical Character = [0-9]
Reports = StudId + StudName + Grade + TimeIn + TimeOut + Date + StatusExist
5-3
StudId = {Legal Character}
StudName = {Legal Character}
Grade = {Legal Character}
TimeIn = {Legal Character}
TimeOut = {Legal Character}
Date = {date}
StatusExist = {Valid Numerical Character}
5.3 Data Specification
5.3.1 Entity Relationship Diagram
5-4
5.3.2 Table/Files Layout
Students:
Reports:
5.4 Screen Layout/Specification
Help Module contains:
Labels
5-5
About Module contains:
Labels
5.5 Report/Form Specification
Contains:
Labels, Image Box
5-6
Contains:
Username Field, Password Field, Login Button and Power Button
Dashboard Module contains:
Update Button and Charts
5-7
Add Student Module contains:
Image Box, Textboxes, Add Button, Clear Button, Modify Student Button, and Unique
Barcode Generator
Modify Student module contains:
Textboxes, Combo Boxes, Search Button, Choices in Radio Buttons, Browse Picture
Button, Update Picture Button, Update Button, Clear Button, Data Grid View, Unique Id Viewer
5-8
Print Barcodes module contains:
Textbox, Combo Boxes, Add Buttons, Show All Button, Reset Button and Barcode
Viewer
Archive module contains:
Textbox, Search Button, Choice Radio Buttons, Data Grid View for Search Results,
Enable Button and Disable Button
5-9
Contains:
Date Picker, Power Buttons, Generate Reports Button, Report Viewer with Print Option
5.6 Program/Module Specification
using System;
using System.Collections.Generic;
using System.ComponentModel;
using System.Data;
using System.Drawing;
using System.Linq;
using System.Text;
using System.Threading.Tasks;
using System.Windows.Forms;
5-10
using System.Data.SqlClient;
namespace Dashboard__LSAS
public partial class LogIn : Form
public LogIn()
// userError.Visible = false;
// passError.Visible = false;
InitializeComponent();
static class Globals
public static string ConnectionString ()
return@"DataSource=(LocalDB)\MSSQLLocalDB;AttachDbFilename=|DataDirectory|\App_Data\LES-
AS.mdf;Integrated Security=True";
5-11
private void loginBT_Click(object sender, EventArgs e)
SqlConnection scn = new SqlConnection();
scn.ConnectionString = Globals.ConnectionString();
scn.Open();
string User = userTB.Text;
string Password = passTB.Text;
SqlCommand cmd = new SqlCommand("Select Username,Password From Admin where
Username='" + User + "' and Password='" + Password + "'", scn);
SqlDataAdapter adapter = new SqlDataAdapter(cmd);
DataTable dt = new DataTable();
adapter.Fill(dt);
if (dt.Rows.Count > 0)
MessageBox.Show("Login Successful!");
this.Hide();
DashboardMain mf = new DashboardMain();
mf.Show();
else
5-12
{
MessageBox.Show("Login Failed! Please check credentials.");
scn.Close();
private void exitBT_Click(object sender, EventArgs e)
if (MessageBox.Show("are you sure to exit?", "Warning", MessageBoxButtons.YesNo) ==
DialogResult.Yes)
Environment.Exit(0);
private void userTB_OnValueChanged(object sender, EventArgs e)
private void LogIn_Load(object sender, EventArgs e)
5-13
{
5-14
CHAPTER VI
6. System Coding
6.1 Programming Language
• C#
-dating from 2000, C# (pronounced C-sharp) is a relatively new programming language
designed by Microsoft for a wide range of enterprise applications that run on the .NET
Framework. An evolution of C and C++, the C# language is simple, modern, type safe
and object oriented.
-Microsoft Visual Studio
-is an integrated development environment (IDE) from Microsoft. It is used to
develop computer programs, as well as websites, web apps, web services and mobile
apps. Visual Studio uses Microsoft software development platforms such as Windows
API, Windows Forms, Windows Presentation Foundation, Windows Store and
Microsoft Silverlight. It can produce both native code and managed code.
-the application used to develop the research using C#
6.2 Special Proposed Language Tools
• SQL (Structured Query Language)
-is a standard computer language for relational database management and data
manipulation . SQL is used to query, insert, update and modify data.
-SQL SERVER
-SQL is a special-purpose programming language designed to handle data in a
relational database management system. A database server is a computer program
that provides database services to other programs or computers, as defined by the
client-server model. Therefore, a SQL Server is a database server that implements the
Structured Query Language (SQL).
-the application used to develop the database to be used by the system
6-1
CHAPTER VII
7. System Testing Plan
A test plan is a document detailing the objectives, resources, and processes for a specific test for
a software or hardware product. The plan typically contains a detailed understanding of the eventual
workflow.
7.1 Testing Stage
• Developer Testing
-Developer Testing denotes the aspects of test design and implementation
that it is most appropriate for the team of developers that designed and
implemented the software to do. It is in contrast with the Independent Testing. In
most cases, test execution will occur initially with the developer testing group that
designed and implemented the test, but the developers create their tests so as to
make their tests available to the independent testing groups for execution.
• Independent and Stakeholder Testing
-Independent Testing denotes the test design and implementation that it
is most appropriate for someone independent from the team of developers to do.
This distinction can be considered a superset that includes Independent
Verification & Validation. In most cases, test execution will occur initially with the
independent testing group that designed and implemented the test, but the
independent testers should create their tests so as to make their tests available to
the developer testing groups for execution.
• Unit Tests
-A traditional distinction, unit tests, implemented early in the iteration,
focuses on verifying the smallest testable elements of the software. Unit testing is
typically applied to components in the implementation model to verify that control
7-1
flows and data flows are covered and function as expected. These expectations
are based on how the component participates in executing a use case, which you
find from sequence diagrams for that use case. The Implementer performs unit
test as the unit is developed. The details of unit tests are described in the
Implementation discipline.
• Integration Test
-A traditional distinction, integration testing is performed to ensure that the
components in the implementation model operate properly when combined to
execute a use case. The target-of-test is a package or a set of packages in the
implementation model. Often the packages being combined come from different
development organizations. Integration testing exposes incompleteness or
mistakes in the package's interface specifications.
• System Test
-A traditional distinction, system testing is traditionally done when the
software is functioning as a whole. An iterative lifecycle allows system testing to
occur much earlier, as soon as well-formed subsets of the use case behavior are
implemented. The target is typically end-to-end functioning elements of the
system.
• Acceptance Test
-"User" acceptance testing is typically the final test action prior to
deploying the software. The goal of acceptance testing is to verify that the software
is ready and can be used by the end-users to perform those functions and tasks
the software was built to do. See Concepts: Acceptance Testing for additional
information. There are other notions of "acceptance" testing, which are generally
characterized by a hand-off from one group or team to another. For example a
7-2
build acceptance test is the testing done to accept hand-over of a new software
build from development into independent testing.
7.2 Test Schedule
Type of Testing Module Date Result/ Output
Error in Database but

Unit Testing Login September 29, 2018
resolved later on
Subtle error in
Login, Add Student,
Database synching and
Integration Testing Modify Student, October 14, 2018
queries. Resolved after
Reports, Archive
a week
Subtle synching error
System Testing All Modules October 21, 2018 with each error.
Resolved after 3 days
Error in local database.

Acceptance Testing All Modules November 1, 2018
Not yet resolved
7-3
CHAPTER VIII
8.1. Resource Requirements
8.1.1 Hardware Requirements
To be able for the system to run, the unit shall have or surpass the following:
• A minimum of 200Gb Hard Drive
• Core2Duo microprocessor
• DDR3 4Gb RAM
• Barcode Scanner
8.1.2 Software Requirements
• Microsoft SQL Server
• Windows OS
8.1.3 Human Resource Requirements
• Admin
• Guard
8.2 Implementation Plan
Implementation is the carrying out, execution or practice of a plan, a method or
any design idea, model, specification standard or policy for doing something. As such, implementation is
the action that must follow any preliminary thinking in order for something to actually happen.
Below are the types of implementation plan
● Direct changeover implementation
- There’s a single, fixed point where one system stops being used and the new
one becomes live. This is the cheapest, quickest and easiest form of system
changeover but is also the riskiest if the system is broken or efficient, the
whole organization suffers.
5-1
8-1
● Parallel implementation
- Both the old and the new system run side by side, using live data, so that
project managers can compare the efficiency and reliability of the new
system. Once they’re satisfied, the old system is taken offline and the new
system. once they’re satisfied, the old system is taken offline and the new
system becomes fully active and utilized across the organization.
● Phased implementation
- A staged method whereby one part of the overall system that need changing
is change. If any problems arise, they are limited in scope and therefore
noncritical. Once the system has been successfully changed in one area, the
other areas can follow suit, with any lessons learned during the initial
changeover used to ensure the success of the changeover as a whole.
The developers chose the Direct Changeover Implementation because the
old system needs a complete overhaul and no components of the old can be
transferred in the proposed system. Overall, the proposed system is better
than the old system.
5-2
8-2
8.2.1 Site Preparation
8.2.2 Personnel Training
November 19, 2018
-Onsite Training for the usage of proposed system for effective usage
and general knowledge about it
8.2.3 System Conversion
November 20, 2018
- As discussed with the beneficiary, system conversion will happen at
November 20, 2018
8.2.4 Data Conversion
November 20,2018
- Same with the system conversion, the data conversion will commence
on the same day
8.2.5 Implementation Schedule
November 21, 2018
- A full system implementation will happen. Meaning the old system will
be replaced at the said date.
5-3
8-3
CHAPTER IX
It is the modification of a system to correct faults, to improve performance, or to adapt the system
to a changed environment or changed requirements.
Below are the types of system maintenance plan
● Corrective maintenance
- A type of maintenance used for equipment after equipment breakdown or
malfunction. Often most expensive not only can worn equipment damage other
parts and cause multiple damage, but consequential repair and replacement costs
and loss of revenues due to downtime during overhaul can be significant.
● Predictive maintenance
- More recently, advances in sensing and computing technology have given rise to
predictive maintenance. This maintenance strategy uses sensors to monitor key
parameters within a machine or system, and uses this data in conjunction with
analyzed historical trends to continuously evaluate the system health and predict
a breakdown before it happens.
● Preventive maintenance
- A maintenance performed with the intent of avoiding failures, safety violations,
unnecessary production costs and losses, and to converse original materials of
fabrication. The effectiveness of a preventive maintenance schedule depends on
the RCM analysis which it was based on, and the ground rules used for cost
efficacy.
The developers chose the Preventive Maintenance Plan to prevent the possible
malfunctioning to the system. With this plan, the developers don’t have to go
frequently in the beneficiary’s office to debug the errors that have been occurred.
5-1
9-1
The possible errors have been trapped and solve with unique solutions for every
error. There is going to be a time wherein the error exists without the programmer
knowing it, in this case, the beneficiary shall contact the developer to debug and
repair the errors that occurs.
5-2
9-2
Appendices
Interview
Me: Hello maam goodmorning.
I: Goodmorning
Me: What is your name and how many years are you servicing the school?
Interviewee: I’m Madelliene Villados. I’m 11 years here in Lolomboy.
Me: Regarding the technology of the school, what is your position po regarding this?
I: ICT Coordinator and LIS (Learner Information System) Admin.
Me: What will be the system that you are willing to receive like payroll or something?
I: Hmmmmmmmm. Maybe an Attendance system? Because it’s a problem here in our school.
Many students are skipping classes and many teachers are having a hard time monitoring them.
Me: That’s a good idea maam. Any other suggestions? For us to have options to choose from.
I: Maybe an archiving system. Our formal forms are in shambles because of the ever-growing
piles of paper. It will be an easy task if we can just search for the name of the student and the
forms will appear.
Me: Thank you maam for your suggestions. Can we contact you if ever we need some more
suggestions and help?
I: Of course. Thank you for choosing our humble school as your beneficiary
Me: The honor is ours maam. Thank you for your time
Bibliography
sql server - How to create an exe file with local database attach ? (Visual Studio C#) - Stack Overflow
c# - How to get image path from Resource files - Stack Overflow
How to integrate SAP Crystal Reports in Visual Studio 2015 Enterprise Edition - Stack Overflow
c# - Dynamic File Paths - Stack Overflow
How to set Selectedvalue in Combobox c# - Stack Overflow
How to query DATETIME field using only date in SQL Server? - Stack Overflow
c# - make the Text of Textbox invisible - Stack Overflow
SQL Server Management Studio ZEROFILL - Stack Overflow
c# - Resizing user control that is docked in Panel control does not resize Panel control - better solution? -
Stack Overflow
Icons - Material Design
The color system - Material Design
Components - Bunifu Framework | Empowering software developers craft great user experiences in less
time. Productivity tools for C# & VB.NET UX/UI design

Lolomboy Attendance Monitoring System With Barcode Scanner

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Lolomboy Attendance Monitoring System With Barcode Scanner

Hochgeladen von

Copyright:

Verfügbare Formate

STI COLLEGE BALAGTAS

Mc Arthur Highway, Borol 1st, Balagtas, Bulacan

ATTENDANCE MONITORING SYSTEM FOR

A Project Presented to the faculty of STI College Balagtas

1.1. Background of the Study ………………………………………………………………………………1-1

1.2. Statement of the Objectives …………………………………………………………………………..1-2

1.2.1.General Objectives ……………………………………………………………………………….1-2

1.2.2.Specific Objectives …………………………………………………………………………….....1-2

1.3. Significance of the Study …………………………………………….………………………………..1-3

1.4. Scope and Limitation of the Study ……………………………………….……………………….…..1-4

3. Data Gathering Procedures and Output

4. The Existing System

4.1. Company Background …………………………………………………………………………………4-1

4.2. Description of the System ……………………………………………………………………………..4-1

4.3. Data Flow Diagram ……………………………………………………………………………………..4-2

4.4. Data Dictionary ………………………………………………………………………………………….4-2

4.5. Problem Areas ………………………………………………………...………………………………..4-3

5. The Proposed System

5.1. System Overview ………………………………………………………………………………………5-1

5.2. Process Specification ………………………………………………………………………………….5-2

5.2.1.Data Flow Diagram ……………………………………………………………………………….5-2

5.2.2.Data Dictionary ……………………………………………………………………………………5-3

5.3. Data Specification ……………………………………………………………………………………...5-4

5.3.1.Entity Relationship Diagram …………………………………………………………………….5-4

5.3.2.Tables/Files Layout ………………………………………………………………………………5-5

5.4. Screen Layout/Specifications …………………………………………………………………………5-5

5.5. Report/Form Specifications ……………………………………………………………………………5-6

5.6. Program/Module Specifications ……………………………………………………………………..5-10

6.1. Programming Language ………………………………………………………………………………6-1

6.2. Special Purpose Language Tools ……………………………………………………………………6-1

7. System Testing Plan

7.1. Testing Stages ………………………………………………………………………………………….7-1

7.2. Testing Schedules ……………………………………………………………………………………...7-2

8. System Implementation Plan

8.1. Resource Requirements

8.1.1.Hardware Requirements …………………………………………………………………………8-1

8.1.2.Software Requirements ………………………………………………………………………….8-1

8.1.3.Human Requirements ………………………………………………………………………...….8-1

8.2. Implementation Plan

8.2.1.Site Preparation …………………………………………………………………………………8-3

8.2.2.Personnel Training ………………………………………………………………………………8-3

8.2.3.System Conversion ……………………………………………………………………………...8-3

8.2.4.Data Conversion …………………………………………………………………………………8-3

8.2.5.Implementation Schedule ………………………………………………………………………8-3

9. System Maintenance Plan

“Let’s just do attendance then skip classes today.”

of headache especially in Lolomboy Elementary School. Me and my partner hypothesize and

come up with a solution-the Monitoring System with Barcode.

The system of managing attendance is efficient only if it is real-time. It requires quick

1.1 Background of the Study

taken once a day.

As per our investigation we identified specific problems like:

• Loss of records due to storage

-Records can be lost due to negligence of the holder or some other

- Inefficient archiving due to lots of paperwork accumulated overtime.

-Reporting of records is also lacking in the system of our beneficiary

because of transferring all data from one record to another manually.

-Due to the traditional approach of the old system, maintenance is

somewhat lacking and hard to do.

• Easy modification from unauthorized personnel

-Unauthorized personnel can manipulate the record, making it not a

trusty source of information

-For a school like our beneficiary, time is an important matter and

are events or occasions.