Aveneu Park, Starling, Australia

1. Existing Attendance Management Applications are less efficient, secure

1.     
INTRODUCTION

1.1. Problem Statement

We Will Write a Custom Essay Specifically
For You For Only $13.90/page!


order now

The existing manual Attendance
Management Application has many lacks. In existing manual Attendance management
application all the Data is handled physically in the catalogs or in other
documents. The process of the work is mainly divided into two parts, first is
to take attendance on sheet & enter details into the catalogs. And then at
the end of the month attendance is intended manually & reports are
generated.

Existing Attendance Management Applications are less
efficient, secure and are time consuming. There are no leave management portal
in biometric application and If Biometric machine is out of order there is no
alternate feature to mark Attendance and these applications have no feature
which can manage reports of attendees on daily, Weekly and on Monthly Basis.

 

There are some limitations of Manual Attendance application
like

·        
Wastage of time

·        
Wastage of the human resources

·        
Data is less secure

·        
Searching of a record from the manual application
is very difficult

·        
Possibility of error occurrence means
accuracy is less

1.2. Objectives

Objective of the
project was to develop an attendance management application which will be able
to register an attendee by getting necessary personal information and Thumb
impression. The application will be able to create user accounts of different
access levels. Application will be able to recognize a person by examining his
thumb impression and then the application will store the time of person’s entry
in the attached data base. Then Organization will be able to manage the record
of attendance and can also check the unauthorized access in an organization.
The organization also will be able to generate different types of periodic
reports.

1.3. Motivation

It was observed
that Most of organizations were using manual attendance management application.
There were many flaws in that application. In market the space and demand for
an attendance application which have accuracy and authenticity was
observed.

A desktop based Attendance management application can fulfill
these requirements therefor this application was designed.

2.     
LITERATURE REVIEW

 

3.     
ANALYSIS

3.1. Vision

Time Click (Attendance Management Application)
is a desktop application which contains software, runs on the application on
which it has been installed under the user control and it will work for any
organization. It can be add user and attendees by an admin and attendees can
mark their attendance by using Thumb impression reader. If the thumb impression
reader is not available then attendance can make with alternate application by
using CNIC number and auto generated password.

Attendees can apply for leaves
which are assigned to them by Admin. Then Admin can approve or reject the leave
application and an email will sent to the applicant about application status. Periodic
reports about on time, late, absent and short attendance can be generated,
printed and save in pdf, docx formats.

 

      In sum Time
Click (Attendance Management Application) include following benefits:

·        
100 percent accuracy in attendance

·        
Daily, monthly, yearly absentee/attendance
report

·        
Reduce use of paper – a green initiative

·        
Save time, money & focus on other core
competencies

·        
Less administration work, fewer workforce

·        
Improves Employees attendance ratios

·        
Eliminate duplicate data entry and errors in
attendance

·        
Real-time status tracking of attendance/leave
requests

·        
Automatic calculation of attendance and leave

 

3.2. Use Case Model

                        Two
main actors are involved to run this application. Application is designed for
two types of users; both users have distinct role and access in this
application.

1.     
Admin

2.     
User

3.2.2. Use case
Essential diagram

3.2.3.
Use case Elaborated diagram

 

Admin

 

           

 

3.3 Software
Architecture

Three layer
architecture is used to developed the application

1.     
Data Access Layer

2.     
Business Layer

3.     
Front End Layer

 

3.4  .
Screen Shots

3.4.1. Login

 

3.4.2. Main Form
Admin

 

 

 

3.4.3. Attendee
Registration Form

 

3.4.4. Attendee Thumb
Impression Capture Form

 

3.4.5. Edit Attendees
Personal Form

 

 

3.4.6. Re Capture
Attendee Thumb Impression Form

 

3.4.7. User Registration Form

3.4.8. Edit User Info
Form

 

 

 

3.4.9. Attendees
Tagging With User Form 

 

3.4.10. Assign Leaves
Form

 

3.4.11. Leave Request
Form

 

 

3.4.12. Mark
Attendance Form

 

 

3.4.13. Reports View
Form

 

3.4.14. Attendance
Settings

 

3.4.15. User Main
Form

 

3.4.16. Mark
Attendance Form

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

3.5. Supplementary
Specification

 

3.5.1.
Purpose

 Purpose of the Supplementary Specification is
to internment the application requirements that are not willingly captured in
the use cases of the use-case model. It comprises necessities such as legal and
regulatory requirements, application standards and quality features of the application
to be built (usability, reliability, performance, and supportability
requirements) and other necessities such as operating applications and
environment compatibility requirements and design constraint.

3.5.2. Scope

This
Supplementary Specification developed by the development team and Active Participant.
The development team and Active participants developed a customizable, decentralized
application that allowed individuals or organizations; to easily, efficiently,
and precisely use of the application. The scope of this paper comprised
describing fully what the software structure will do, but on how it will do, by
recounting nonfunctional requirements such as security, reliability,
extensibility, and performance by using SIG.

3.5.3
Definitions, Acronyms, and Abbreviations

 

Active participant: A user who was also an attendee, whose role was
to perform an action during demo. This user may also be asked to provide
requirements for equipment.

Admin: is an advantaged
user who is responsible for managing user accounts, and managing resources (adding,
removing and editing users, Attendees, Leaves, etc.).

Attendee: is a
user, who marks his attendance by using thumb impression capture function. An
attendee can be furthermore classified as active or inactive participant.

Confirmation: A
notification sent to attendees by the initiator confirming registration as
attendee.

Date conflict: occurs when no available date can be found in
the stated date range.

Date range: time
interval specified by the initiator in which the meeting should take place,
this also serves as the boundaries for the exclusion and preference sets.

Equipment: Any
type of resource (e.g. projector, microphone, etc) that can be used in a
meeting or event. They are further classified as movable or fixed. Movable
equipment refers to equipment that can be transported from one location to
another without requiring technician (hardware technician, electrician,
handyman, etc) intervention. Fixed equipment refers to equipment that is
assigned to a location (overhead projector, podium microphone, etc) wherein
moving it to another location involves an installation that requires technician
intervention.

Exclusion set: a set of dates on which the attendees are not
present in organization

GUI:
Graphical User Interface.

Internationalization
(I18N): The
process of designing a software application so that it can be adapted to
various languages and regions without engineering changes.

Initiator: is a
user who calls for the meeting. The initiator is responsible for performing the
meeting scheduling activities, or to envoy an initiator representative to
perform this on their behalf.

Initiator representative: is a user who is delegated to act on behalf
of the initiator.

Invite: A
meeting request sent by an initiator or representative to the prospective
attendees, which includes meeting area, date range and requires attendees to
respond with their partialities regarding date. For active participants the
invite will require the attendee to provide tools requirements. For important
participants the invite will require the attendee to provide location
preferences. 

Localization: The procedure of adapting software for an explicit
region or language by adding locale-specific constituents and translating text.

Meeting scheduling activities: The tasks required in order to schedule a
meeting. These usually involve the following tasks: planning the meeting,
sending the invites, monitoring the responses, resolving conflicts, and
confirming the final arrangements.

Strong date conflict: This happens when no date can be found within
the date range and outside all barring sets.

UML:
Unified Modeling Language

User: A
person who interacts directly with the application. A user can have different
roles with esteem to the application (e.g. admin, user).

3.6.
Overview

The supplementary specification
document is poised of different section comprising Functionality, Security,
Reliability, Performance, Supportability, Design Constraints, Online User
Documentation and Help Application Requirements, Purchased Components,
Licensing Requirements, Legal, Copyright, and Other Notices, Applicable
Standards.

The Functionality Requirements: defines requirements of the applications
which are stated in the natural language style. This section will be organized
by structures or by users or organization by sub application.

Security section: includes all of the requirements
that affect security.

Reliability section: describes about availability
(percentage of time available, hours of use, and maintenance access), mean time
between failures, how long is the application allowed to be out of operation
after it has failed, accuracy, maximum bugs, and blemish rate.

Performance section: uses figures to describe the
performance characteristics of the application.

Extensibility section: indicates any requirements such as
scalability and customizability.

Design Constraints: directs any design constraints
on the application being built. Such as software languages, software process
requirements, prescribed use of developmental tools, architectural and design
constraints,

Purchased Components: describes any purchased components
to be used with the application any applicable licensing or usage limits, and
any associated compatibility or interoperability or interface standards.

Licensing Requirements,
Legal, Copyright, and Other Notices section defines any basic legal repudiations,
warranties, copyright notices, patent notice, word mark, trademark, or logo
compliance issues for the software.

Applicable Standards section
describes by reference any applicable standards and the specific sections of
any such standards that apply to the application being described.

3.7. Functionality

a.                 
Admin

·        
The application shall allow the admin
to add users.

·        
The application shall allow the admin
to edit user information.

·        
The application shall allow the admin
to remove users.

·        
The application shall allow the admin to change
user status from active to inactive

·        
The application shall allow the admin
to add attendees.

·        
The application shall allow the admin
to edit attendee’s information.

·        
The application shall allow the admin
to remove attendees.

·        
The application shall allow the admin to change attendee’s
status from active to inactive.

·        
The application shall allow the admin to tag a
user with an attendee.

·        
The application shall allow the admin to assign
leaves to attendees.

·        
The application shall allow the admin to take
action on attendees leave requests.

·        
The application shall allow the admin to mark
attendance.

·        
The application shall allow the admin to view
periodic reports of attendees regarding their attendance.

·        
The application shall allow the admin to change
attendance setting from thumb impression to password.  

b.                 
User

·        
The application shall
authenticate users at the beginning each session.

·        
The application shall allow the
user to view leaves assigned to them.

·        
The application shall allow the
user to request for a leave.

·        
The application shall allow user
to mark his attendance on daily basis.

·        
The application shall allow user to mark short
attendance.

·        
The application shall allow the
user to change the password.

·        
The application shall provide auto
generated password to the user at the time of their registration. Later user
can use this password to mark attendance.

 

The security goal is divided into
confidentially, integrity, and availability.

3.8.1.
Confidentiality

To ensure confidentiality it’s essential
to achieve authentication, it is mandatory for users to log into the application
by providing username and with strong password, it also provides auto generated
password to the user at the time of their registration.

3.8.2.
Integrity

 Integrity ensures completeness such as data
validation, accuracy, and consistency. And availability provides protection
against DOS attack relays on the firewall, see figure below.

 

 

3.8.3. Reliability

The reliability of application
divided into accuracy, integrity, and availability. Accuracy consist
consistency and availability provides protection against DOS attack relays on
the firewall. Integrity shelters completeness such as data validation,
efficiency, and consistency. And availability provides protection against DOS
attack relays on the firewall.

3.9.
Performance

The most significant
nonfunctional requirement is that customer wants an application with good and
fast performance level. Consequently, the performance goal is divided into
three parts: time, space, and response. Time is divided into throughput time
and response time (when using indexing). In this application performance is
most important feature. High level performance is ensured by using indexing. A privilege
of response time is that indexing improves responses time when interacting with
Data base. Responsive sub goal deals on how fast the application responds to
queries, and space sub goal with storage space. Storage saved and prevents to
be wasted in order to achieve a good performance.

3.10. Design Constraints

 

a.      Hardware Limitations

To install this application a computer must have the following
minimum hardware capabilities.

32-bit (x86) or 64-bit (x64) processors
Dual-core, 2.66-GHz or faster processor
USB 2.0 bus
2 GB of RAM

b.     
Software
Limitations

To install this application a computer must have the following
minimum software capabilities.

 

·        
Microsoft windows XP or latest
version.

·        
Microsoft visual studio

·        
ASP.NET 2.0 and web standards.

 

3.11. Software Quality Assurance Plan

 

The Software Quality Assurance Plan describes the process,
methods, standards, and procedures that were used to perform the Software
Quality Assurance function for the Time Click (Attendance Management System).
The Software quality assurance plan follows the Agile unified Software
Engineering Methodology (SEM), modified to accommodate the project model
adapted for Time Click (Attendance Management System).

 

 

3.11.1. Application checkpoints

Every stage of application development has one formal
checkpoint called stage exit.

When an application successfully reached at that stage it
indicates that a module has been completed successfully. At every stage exit
Software quality assurance plan executed.

3.11.2. Roles and responsibilities

Roles and responsibilities in Time Click quality
assurance plan were following:

 

Role

Name

SQA Responsibility

 
QA Consultant

 
Haseeb Ghaffar

Managed the quality assurance functions

 

 

Helps define product quality expectations

 
QA Consultant

 
Haseeb Ghaffar

Audit and approved application’s delieverables

QA Consultant

 
Haseeb Ghaffar

Ensure implementation of quality activities

 

3.11.3. Required Skills

The QA Analyst must be able to review iterations in
the project plan and SDLC to determine industry standards. QA Consultant pays role
independently to ensure the work quality at every stage exit.

 

3.11.4. Audits and Reviews

Time
Click QAP followed the Software engineering Method (SEM) standards. They are
Following.

 

·        
IEEE Guide to
software Design Descriptions.

·        
IEEE Standard
for Software User Documentations.

 

 

3.11.5. Problems Level

 

QA Problems are classified in three categories
described under:

Level

Description

Low

Low Potential or existing problems must be addressed
to avoid an impact on current project plan
This should also apply if no issues
identified

Medium

Medium problems exist that have a high
probability of impacting the project plan

High

High problems exist that have a high
probability of impacting user acceptance

 

x

Hi!
I'm Darlene!

Would you like to get a custom essay? How about receiving a customized one?

Check it out