Attendance Monitoring System Thesis Documentation | Chapter 4
In this article, you will learn how to write the Attendance Monitoring System Existing System Chapter 4. Chapter 4 is about the existing system your target client. This Chapter of your Attendance Monitoring System is similar to Chapter 1 but is focused on the manual system. Here are the steps in creating Chapter 4.
Steps in writing Chapter 4 – The Existing System
How to write Attendance Monitoring System Existing System Chapter 4
- The Existing System
The researcher need to describe the current manual system of the client.
- General Objectives of the Manual System
The researcher must state the general objective of the current system.
- Specific Objectives of the Manual System
Breakdown the general objective into smaller parts. Specific objectives give a clearer vision of what the study is trying to achieve.
- Scope of the Existing System
The scope explains the nature and coverage of the manual system.
- Concept of the Operation
In this part, the researcher will discuss the over-all process of the existing system.
- Activity Diagram
The activity diagram will illustrate the actions done by the users of the existing system.
- Data Flow Diagram
The Data Flow Diagram will illustrate the flow of information through the system. In this case, we only used level 0 of the DFD.
Sample Chapter 4 – Existing System
The Existing System
The existing system is a manual entry for the students and teachers’ information. Here, the attendance will be carried out in handwritten registers. It will be a tedious job to maintain the record for the user. The system requires more human effort.
The retrieval of the information is not easy because records are maintained in hand written registers. This application requires correct feed in the respective input field. Supposed there were wrong inputs entered, the application resists requiring the user to input correct data.
General Objectives
This study aims to monitor the students’ and teachers’ attendance and to evaluate their performance according to their attendance.
Specific Objectives
- To
record daily time record of the teachers - To check the daily
attendance of the students - To maintain the
security of the students and teachers within the school
Scope of the Existing System
The system covers all the students and teachers of RTTNHS Su-ay Ext. The system is applicable for teachers because it can be used to compute for their payroll. It is limited only to students who have been monitored from time to time and who are officially enrolled and to the teachers who are employed in RTTNHS.
Concept of Operation
Having a manual operation in a school or in a company brings a lot of work and sometimes this method causes errors in inputting data like basic student information that results to another set of work. In other words, the manual operation takes also a lot of time and effort.
In manual attendance monitoring, the teachers are using time sheet in their attendance, attendance log and attendance sheets. These are all paper works and these can easily get damaged and worst is that these can be tampered or modified. Security is also involved in this system.
Activity Diagram
Figure 3 shows the existing systems activity diagram. This figure shows two processes in monitoring the attendance. Process one is from students’ and teachers’ entities wherein their identification cards are required for them to enter the school. Process two records the details of attendance from the staff or employee to the administrators.
Data Flow Diagram of the Existing System
Figure 4 shows how the manual operation works in the system and who are involved in the operation. In order for a student to enter the school, he or she must have the school ID. Then the employee will verify the ID and so, the student can now enter the school. This type of system is not much observed in some schools.
Conclusion
Now that you have read through the sample the existing system of attendance monitoring system, you are now ready to take the last Attendance Monitoring System Documentation chapter!
This attendance monitoring system documentation chapter 4 is free to modify. Surely, this guide will help you finish your own attendance monitoring system documentation.
Related Capstone Resources
- Chapter 3 Methodology Attendance Monitoring System 2019 Doc
- Proposed Solution Chapter 5 Attendance Monitoring System Doc 2019
- Attendance Monitoring System Thesis
- Attendance Monitoring System Thesis Chapter 1 Guide
- Attendance Monitoring System Thesis Documentation Chapter 2 Rrl Doc
- 2019 Chapter 4 Existing System Library Borrowing System Doc
Capstone chapter writing checklist
Structuring a BSIT capstone chapter correctly saves rework and eases the defense. Follow this checklist for consistent quality across all 5 chapters.
- Draft the outline first. Every section header first, then fill in the content.
- Write the methodology before the introduction. Chapter 3 (methodology) forces you to think through the system; Chapter 1 becomes easier after.
- Include diagrams early. UML diagrams in Chapter 3 clarify what you’re building.
- Cite sources as you write. Do not defer citations. Use Zotero or Mendeley to track sources.
- Get adviser feedback per chapter. Do not write all 5 chapters then ask for review.
- Number figures and tables. Figure 3.1, Table 4.2, etc. Panels reference these numbers.
- Follow the school template exactly. Font, margins, spacing — do not deviate.
Common capstone mistakes to avoid
- Copying without attribution. Panels use Turnitin. Cite everything you did not write yourself.
- Over-scoping the project. A well-executed simple system beats a poorly-executed ambitious one.
- Deferring documentation. Documentation quality is a big part of the grade.
- Skipping user testing. Panels ask about user feedback. Have real data.
- Ignoring adviser feedback. Advisers know what the panel will ask.
Recommended free tools for capstone projects
- draw.io / diagrams.net. UML diagrams for Chapter 3.
- Google Docs. Collaboration + version history + adviser comments.
- Zotero or Mendeley. Reference management + auto-formatted citations.
- GitHub. Version control for the source code (also earns E-E-A-T signal on your CV).
- Grammarly. Language + tone check on the documentation.
- Turnitin. Plagiarism check before submission (some schools provide access).
- ChatGPT or Claude. For outline scaffolding — not for writing the actual content.
Where to get more capstone resources
- Capstone project ideas. Browse itsourcecode.com/topics/fyp/ for 140+ tested capstone concepts.
- Working source code. itsourcecode.com/topics/free-projects/ has 1,000+ downloadable projects.
- UML diagrams. itsourcecode.com/uml/ has 300+ free UML examples for Chapter 3.
- ER diagrams. itsourcecode.com/topics/uml/erd/ for database schemas.
Official references
Frequently asked questions
How many pages should a BSIT capstone chapter be?
Chapter 1 (Introduction) is typically 8-12 pages. Chapter 2 (RRL) is 15-25 pages. Chapter 3 (Methodology and System Design) is 15-30 pages depending on diagram count. Chapter 4 (Results) is 10-20 pages. Chapter 5 (Conclusions) is 5-10 pages. Total: 60-100 pages for the whole capstone.
What order should I write the chapters in?
Recommended order: Chapter 3 first (system design and methodology — most concrete), then Chapter 1 (introduction with the problem statement), then Chapter 2 (RRL to justify Chapter 1), then Chapter 4 (results — after implementation), then Chapter 5 (conclusions). This avoids rewrites and speeds up defense readiness.
What formatting style should I use for the capstone documentation?
Most Philippine BSIT programs require IEEE or APA 7th edition. Confirm with your adviser first. Use Times New Roman 12pt, double-spaced, 1-inch margins, and page numbers. Reference all sources properly and use consistent citation style throughout.
How many references do I need per chapter?
Chapter 1: 5-10 references. Chapter 2 (RRL): 20-40 references. Chapter 3: 10-15 references. Chapter 4-5: minimal, mostly self-referential. Recent sources (last 5 years) are strongly preferred over older ones.
What tools help write the capstone chapters?
Zotero or Mendeley for reference management, Grammarly for language check, Turnitin for plagiarism scan, Google Docs for collaboration with adviser, LaTeX (Overleaf) for advanced formatting, and ChatGPT or Claude for outline scaffolding (not for writing the actual content).
Adones Evangelista
Programmer & Technical Writer at PIES IT Solution
Adones Evangelista is a programmer and writer at PIES IT Solution, author of over 900 tutorials and error-fix guides at itsourcecode.com. Specializes in JavaScript, Django, Laravel, and Python error debugging covering ValueError, TypeError, AttributeError, ModuleNotFoundError, and RuntimeError, plus C/C++ and PHP capstone projects for BSIT students.
Expertise: JavaScript · Python · Django · Laravel · Error Debugging · C/C++
· View all posts by Adones Evangelista →