Ready Report Att
Ready Report Att
CHAPTER1
INTRODUCTION
INTRODUCTION
OBJECTIVES:
Design the system with a user-friendly interface to facilitate easy navigation for
staff members, ensuring efficient data input and report retrieval.
DELIVERABLES:
Enhanced data security with separate usernames and passwords for staff
members, and an authentication mechanism restricting access to authorized
personnel.
Detailed weekly reports providing insights into individual student attendance and
overall class trends, empowering staff with actionable insights for decision-
making.
Intuitively designed interface for effortless input of attendance data and access to
reports, ensuring efficiency and accessibility for staff members.
CONSTRAINTS:
The system assumes that the hardware infrastructure (servers, network devices) is
robust enough to handle real-time attendance tracking, automated calculations,
and report generation without significant performance issues.
The system relies on stable internet connectivity for real-time monitoring and
data access. Any disruptions in internet services may impact the system's
functionality.
Assumes that staff members are adequately trained to use the system. Inadequate
training may lead to errors in data input and report interpretation.
The implementation is subject to budget limitations, which may impact the extent
of technological features and security measures that can be integrated into the
system.
ASSUMPTIONS:
Assumes timely updates and maintenance of the system to address any potential
security vulnerabilities, ensure optimal performance, and incorporate new
features or improvements.
The accuracy of real-time attendance tracking assumes that devices used for
marking attendance have synchronized and accurate time settings.
Assumes that the system adheres to data privacy regulations and policies. Any
changes in regulations may require updates to the system to maintain compliance.
CHAPTER2
This structured breakdown provides a clear outline of the tasks and activities required
for the successful development, implementation, and maintenance of the Student
Attendance Management System. Each phase is designed to ensure systematic
progress and effective project management.
System Design: Gather requirements, design the database schema, create the user
interface, define system architecture, and plan for security measures.
Testing: Conduct unit testing, perform integration testing, carry out system
testing, conduct security testing, and verify user interface usability.
Project Closure: Evaluate project success criteria, obtain user feedback, document
lessons learned, handover project deliverables, and conduct a final project review.
Time-line Schedule
Project 1 Week
management
02 06/03/2024 11/03/2024
Analysis 1 Week
03 13/03/2024 03/04/2024
Design 3 Week
04 04/04/2024 02/05/2024
Developing 4 Week
05 03/05/2024 25/05/2024
Testing Costs:Includes testing tools and software, potential external testing services,
and expenses for user interface usability testing.
Implementation Costs:Covers deployment services and user support during the initial
rollout.
Phase4: Coding 7k
Phase7: Deployment 7k
Risk Analysis
Department of CSE, SET POLYTECHNIC, MELUKOTE Page 8
Student Attendance Management System
Risk Identification
Control Risks
Selecting a seller
Receiving seller responses
Awarding a contract
SYSTEMDESIGN
Data Store:A data store is a holding place for information within the system. It is
represented by an open ended narrow rectangle. Data stores may be long-term files
such as sales ledgers, or may be short-term accumulations: for example batches of
documents that are waiting to be processed. Each data store should be given a
reference followed by an arbitrary number.
Level 1:
DETAILED DESIGN
Use cases:
A use case describes a sequence of actions that provide something of
measurable value to an actor and is drawn as a horizontal ellipse.
Actors:
An actor is a person, organization, or external system that plays a role in
one or more interactions with your system. Actors are drawn as stick figures.
Associations:
Associations between actors and use cases are indicated in use case
diagrams by solid lines. An association exists whenever an actor is involved
with an interaction described by a use case.
Literature survey
Observation survey:
Operates on a daily basis for systematic tracking of attendance for each student.
Ensures only authorized personnel can access and modify attendance records.
Marks students as present only if physically present during the designated class
period.
CHAPTER3
APPROACH AND METHODOLOGY
Database: MySQL
MySQL: MySQL is an open-source relational database management
system (RDBMS) known for its reliability, performance, and scalability. It
provides features for creating, querying, updating, and managing relational
databases. In this app, MySQL is used as the database management system to
store user data, posts, chat messages, course registrations, and other relevant
information. The schema design ensures efficient storage and retrieval of data,
maintaining data integrity and consistency.
Processor:
Pentium 4 or higher: The Pentium 4 processor is a central processing unit
(CPU) manufactured by Intel. It offers capabilities suitable for running basic
to moderate computing tasks. Emphasizing the Pentium 4 or a higher
processor indicates the minimum processing power required for the system.
Speed: 1.2 GHz or higher: The specified speed denotes the clock frequency
of the processor, measured in gigahertz (GHz). A speed of 1.2 GHz or higher
ensures adequate processing power to handle computational tasks efficiently.
Hard Disk:
20GB: The hard disk is a non-volatile storage device used to store data
permanently. The specified capacity of 20GB denotes the minimum storage
space required for installing the operating system, applications, and storing
user data. While 20GB may seem small by modern standards, it is sufficient
for basic computing needs.
Programming language
CHAPTER4
TEST AND VALIDATION
PURPOSES OF TESTING
knowledge of the code's internal workings. Testers delve into the source code
to identify specific units or sections of code that may exhibit inappropriate
behavior.
Different levels of testing play distinct roles in ensuring the quality and
functionality of software:
UNIT TESTING
isolate and demonstrate that individual program parts meet the requirements
and function correctly.
Limitations:
Unit testing cannot detect every bug in an application.
Evaluating every execution path in complex software is not feasible.
There's a constraint on the number of scenarios and test data developers
can use to validate the source code, necessitating the eventual merging of
code segments with other units.
INTEGRATION TESTING
SYSTEM TESTING
ACCEPTANCE TESTING
Acceptance testing, also known as User Acceptance Testing (UAT), is a
crucial phase in the software testing process where a system is evaluated
for acceptability. The primary purpose of this testing level is to assess
whether the system aligns with the business requirements and determine if
it's suitable for delivery. User Acceptance Testing (UAT) is carried out
either by end-users or on behalf of them to ensure that the software
functions in accordance with the Business Requirement Document. UAT
focuses on several key aspects:
Ensuring that all functional requirements are met.
Department of CSE, SET POLYTECHNIC, MELUKOTE Page 28
Student Attendance Management System
Arguably, UAT is one of the most critical types of testing because it's
conducted by the Quality Assurance Team, responsible for gauging
whether the application aligns with the intended specifications and meets
the client's requirements. The QA team typically uses predefined scenarios
and test cases to evaluate the application thoroughly.
Additionally, acceptance tests serve as a means to gather insights about
the application's performance, accuracy, and the reasons behind the
project's initiation. These tests aim not only to identify simple issues like
spelling mistakes or cosmetic errors but also to pinpoint any critical bugs
that could lead to system crashes or major errors in the application. By
conducting acceptance tests, the testing team can gain a better
understanding of how the application will perform in a production
environment.
REGRESSION TESTING
CHAPTER5
CONCLUSION
FUTURE ENHANCEMENT
REFERENCES