ABSTRACT

child daycare system is the care of a child during the day by a person other than the child’s

legal guardian, basically performed by someone outside the child’s immediate family. it is

typically ongoing for a specific period, such as parents work time. the system will be used to

register a child, monitor and verify who drops and picks the child, log of child’s activity,

parents/guardian details, parents will be able to update a child’s details (e.g. record allergy,

drug administration time if any etc.). it can also take a formal structure with education, child

development and discipline.

viii

TABLE OF CONTENTS

Title Page - - - - - - - - - - i

Cover Page - - - - - - - - - - ii

Declaration - - - - - - - - - - iii

Certification - - - - - - - - - - iv

Approval - - - - - - - - - - v

Dedication - - - - - - - - - - vi

ABSTRACT - - - - - - - - - - VII

CHAPTER ONE: INTRODUCTION

1.1 Overview - - - - - - - - - 1

1.2 Background and Motivation - - - - - - - 1

1.3 Statement of Problem - - - - - - - - 2

1.4 Aim and Objective - - - - - - - - 2

1.5 Significance of the Project - - - - - - - 2

1.6 Risk Assessment - - - - - - - - 3

1.7 Scope/Project Organization - - - - - - - 3

CHAPTER TWO: LITERATURE REVIEW

2.0 Overview - - - - - - - - - 4

2.1 Introduction - - - - - - - - - 4

2.2 Types of day care - - - - - - - - 5

2.3 Related Work - - - - - - - - - 5

2.3.1 EZcare childcare management software - - - - - 6

2.3.2 The Pre School Partner - - - - - - - 6

2.3.3 Power School Kindergarten System - - - - - - 6

2.3.4 Proposed solution - - - - - - - - 7

ix

2.4 Summary - - - - - - - - - 7

CHAPTER THREE: REQUIREMENTS ANALYSIS AND DESIGN

3.1 Overview - - - - - - - - - 8

3.2 Proposed Methodology - - - - - - - 8

3.3 Approach to chosen Methodology - - - - - - 10

3.4 Tool and Techniques - - - - - - - - 10

3.5 Requirement Analysis - - - - - - - 10

3.6 Requirement specifications - - - - - - - 11

3.6.1 Functional Requirements Specification - - - - - - 11

3.6.2 Non-functional Requirement specifications - - - - - 12

3.7. Application Architecture - - - - - - - 12

3.7.1 Use Case Diagram - - - - - - - - 14

3.7.2 Class Diagram- - - - - - - - - 17

3.7.3 Database Design - - - - - - - - 18

3.7.4 Dataflow Diagram (DFD) - - - - - - - 19

3.7.5 Activity Diagram - - - - - - - - 21

3.6 Summary - - - - - - - - - 22

CHAPTER FOUR: IMPLEMENTATION AND TESTING

4.1 Overview - - - - - - - - - 23

4.2 Development tools and technologies - - - - - - 23

4.3 Implementation Problems - - - - - - - 23

4.4 Overcoming Implementation Problems - - - - - 24

4.5 Testing - - - - - - - - - 25

4.5.1 Test Plans - - - - - - - - - 25

4.5.2 Test Traceability Matrix - - - - - - - 26

4.6 Test Report Summary - - - - - - - - 28

4.7 User Guide - - - - - - - - - 28

4.8 Summary- - - - - - - - - - 28

x

CHAPTER FIVE: DISCUSSION, CONCLUSION, AND RECOMMENDATIONS

5.1 Overview - - - - - - - - - 29

5.2 Evaluation - - - - - - - - - 29

5.2.1 Objective Assessment- - - - - - - 29

5.3 Limitations and challenges - - - - - - - 29

5.4 Future Enhancements - - - - - - - - 30

5.5 Recommendation - - - - - - - - 30

5.6 Conclusion - - - - - - - - - 30

REFERENCES - - - - - - - - - 31

APPENDICES - - - - - - - - - 32