TOP
3.2.1 Component Parent
3.2.1.1 Processing narrative of component Parent
The component parent contains the class Parent. It contains the attributes,
which are the basic data of the parent of a child. It contains the
functions, which sets all the related data into and out of the database. The
class parent contains the data members and functions, which are unique to
the parent of a child. The responsibilities of this component is to
declaring variables of the basic data of the parent and implementing
functions which set data in the database and retrieve from the database.
3.2.1.2 Interface description of the component Parent
The component parent has an interface with the class person from which it
inherits attributes and functions. The person class has attributes, which
are the basic data common to parent class and employee class and functions
to set this data into the database and retrieve from the database. The
attributes common for parent and employee are declared in this interface and
the functions related to these attributes to set and get from the database
are defined in this class. The attributes and operations which are unique to
the parent are declared and defined in the component class, for example
spouse, list children, authorized pickup, appointment date, contract renewal
date, register date etc.
3.2.1.3 Algorithmic description of component Parent
Component Parent;
The intent of this component is to set basic parent data into the database
and get data from the database
Start
Declare variables of the basic data
Set the basic data of the parent in the database
Get the data from the database
End
3.2.1.3.1 Design class hierarchy
TOP
3.2.2 Component Employee
3.2.2.1 Processing narrative of component Employee
The component Employee consists of the class Employee. It contains the
attributes, which are the basic data of the employee of the childcare
center. It contains the functions, which sets all the related data into and
out of the database. The class Employee contains the data members and
functions, which are unique to the employee. The responsibilities of this
component is to declare variables of basic data of the employee and
implementing functions which set data in the database and retrieve from the
database.
TOP
3.2.2.2 Interface description of component Employee
The component Employee has an interface with the class person from which it
inherits attributes and functions. The person class has attributes, which
are the basic data common to parent class and employee class and functions
to set this data into the database and retrieve from the database. The
attributes common for parent and employee are declared in this interface and
the functions related to these attributes to set and get from the database
are defined in this class. The attributes and operations which are unique to
the employee are declared and defined in the component class, for example
punchin time, punchouttime, noofhrs, pay etc.
3.2.2.3 Algorithmic description of component Employee
Component Employee;
The intent of the component Employee is to set basic data of Employee into
database and get the data from the database
Start
Declare variables of the basic data of the employee
Set values into the database
Calculate the pay of the employee
Get the data from the database
End
TOP
3.2.2.3.1 Design class hierarchy
TOP
3.2.2.3.2 Restrictions/limitations
This component can only be called when the user requires the data of the
child and parent.
3.2.3 Component Child
3.3.3.1 Processing narrative of component Child
The component child consists of the class Child. It contains the attributes,
which are the unique basic data of the child. It contains the functions,
which sets all the related data into and out of the database. The class
child contains the data members and functions, which are unique to the
employee. The responsibilities of this component is to declare variables of
basic data of the employee and implementing functions which set data in the
database and retrieve from the database.
3.3.3.2 Interface description of component Child
The component Child has an interface with the class Parent from which it
inherits attributes and functions. The parent class has attributes, which
are the basic data common to parent class and child and functions to set
this data into the database and retrieve from the database. The attributes
common for parent and child are declared in this interface and the functions
related to these attributes to set and get from the database are defined in
this class. The attributes and operations which are unique to the child are
declared and defined in the component class, for example photo, class,
special needs etc.
3.3.3.3 Algorithmic description of component Child
Component Child;
The intent of the component Child is to set basic data of Child into
database and get the data from the database
Start
Declare variables of the basic data of the Child
Set values into the database
Get the data from the database
End
3.3.3.3.1 Design class Hierarchy
3.2.3.3.2 Restrictions/Limitations
This component can only be called when the user requires the data of the
child.
3.2.4 Component Teacher
3.2.4.1 Processing narrative of the component Teacher
The component Teacher consists of the class Teacher. It contains the
attributes, which are the basic responsibilities of the teacher in the
childcare care center. Itcontains the functions to set the related data into
and out of the database. It contains the data members and functions to set
the student activities, set the classroom schedules. Since teacher is also
an employee of the childcare center, the component would have access to the
basic data of the employee. The responsibilities of this component is to set
and get the basic data of the teacher and set the and get the student
activities and classroom schedules.
3.2.4.2 Interface description of component Teacher
The component Teacher has an interface with the class Classroom and the
class Employee. As the Teacher is an Employee it has access to the Employee
class and inherits the attributes and functions of that class through the
interface. Using this interface the basic data of the teacher can be set
into the database and get from the database in this interface and the
functions related to these attributes to set and get from the database are
defined in this class. Using the interface Classroom the schedules and
programs of the classrooms can be set into the database and get from the
database.
3.2.4.3 Algorithmic description of component Teacher
Component Teacher;
The intent of the component Teacher is to set basic data of Teacher,
classroom schedules, and student activities into the database and get the
data from the database.
Start
Declare variables of the student activities
Set the data into the database
Get the data from the database
End
3.2.4.3.1 Design class hierarchy
TOP
3.2.4.3.2 Restrictions/Limitations
This component can only be called when the user wants to manipulate the
teacher data, classroom schedules, and student activities.
3.2.5 Component Adminstaff
3.2.5.1 Processing narrative of the component Adminstaff
Component Adminstaff consists of the class Adminstaff. It contains the
attributes, which are the basic responsibilities of the staff regarding
schedules of classrooms, student activities, immunization information,
employee information, child billing information,
It contains the operations to set related data to the database and get from
the database. I also compute the paybills of the child.
3.2.5.2 Interface description of the component Adminstaff
The component Adminstaff has the interface with the classes Teacher, Child,
Employee, Immunization, classroom. Since the Aminstaff are the employee of
the childcare center, it inherits the attributes and functions from the
class Employee. The Adminstaff has the responsibility of setting the
classroom schedules, student activities, so it inherits the related
attributes and members from the classes Classroom and Teacher. They have the
responsibility of manipulating the data regarding the immunization
information of the child, so it inherits the related data from the class
Immunization. Using these interfaces the data can be set into the database
and get the data from the database.
3.2.5.3 Algorithmic description of the component Adminstaff
Component Adminstaff;
The intent of this component is to set the data of the adminstaff, classroom
schedules, student activities, and immunization into the database and get
the same from the database.
Start
Set the data of adminstaff into the database
Set the data of classrooms into the database
Set the data of the child immunization
Set the data of the student activities
Get the data of the billing hrs of the child
Get the data of adminstaff into the database
Get the data of classrooms into the database
Get the data of the child immunization
Get the data of the student activities
Get the data of the billing hrs of the child
Calculate the pay bill of the child
End
TOP
3.2.5.3.1 Design Hierarchy of the component Adminstaff
TOP
3.2.5.3.2 Restrictions/Limitations
This component can only be called when the user wants to manipulate the
Adminstaff data, classroom schedules, student activities, Immunization
information, child data.
3.2.6 Component Manager
3.2.6.1 Processing narrative of the component Manager
The component Manager consists of the class Manager. The responsibility of
this component is to manipulate the data of the child, Employee, set
schedules, activities, print reports, and immunization.etc. This component
sets related data into the database and performs on the data to print the
reports.
3.2.6.2 Interface Description of the component Manager
The component manager has the interface with the classes Child, Adminstaff,
Employee, Reports, and Classroom. As the manager is the employee, it
inherits the data members and functions from the class Employee to set and
get the data of the manager into the database and from the database. It
inherits the functions from the class Report to print the reports. It
inherits the data members and functions from the class classroom to set the
classroom schedules.
3.2.6.3 Algorithmic description of the component manager
Component Manager;
The intent of the component manager is to manipulate the data of the child,
Employee, set schedules, activities, print reports, Immunization.
Start
Set manager data into the database
Get manager data from the database
View the child data, Employee data, and classroom data
Set the classroom data
Get the classroom data
Print the reports
End
TOP
3.2.6.3.1 Design Hierarchy of component Manager
3.2.7 Component Reports
3.2.7.1 Processing narrative of the component Reports
The component Reports consists of the class Reports. The responsibilities of
this component are to print the reports of the sign in, sign out,
Immunization, customer info, child info, employee info, employee pay,
receipts, pay bills, register receipt etc. This component gets the data
through various interfaces described in the next section to print on the
reports. TOP
3.2.7.2 Interface description of the component Reports
The component Reports has the interface with the classes Child, Employee,
Customer, Classroom, Account, Timesheet. It inherits the data members and
functions from the class child to print the child data report. It inherits
data members and functions from the class Employee to print the Employee
data, from the class Account to print the child billing report, Employee pay
report, from the class Classroom to print the classroom schedules, from the
class Timesheets to print the sign in sign out reports.
TOP
3.2.7.3 Algorithmic description of the component Reports
Component Reports;
The intent of this component is to print the reports
Start
Get the child data
Print the child data report
Get the employee data
Print the Employee report
Get the classroom schedules
Print the Classroom schedule report
Get the Employee pay data
Print the Employee pay report
Get the child billing data
Print the child billing report
End
TOP
3.2.7.3.1 Design class hierarchy
3.3 Dynamic behavior for component n
3.3.1 Interaction Diagrams
A sequence diagram, for each use case the component realizes, is presented
TOP
This is a sequence diagram where the use case component is a Manager .The
first event, system ready, is derived from the external environment and
channels behavior to a Manager object. The manager enters a password. A
request lookup event is passed to system that looks up the password in the
software system and returns a result (found or not found) to Monitor. A
valid password results in a password= correct event to software system which
then gives access to the manager and the manager can add/update/delete the
data of all other employees. And this data can be displayed on the monitor
or printed from the printer up on request.
TOP
This is a sequence diagram where the use case component is Administrative
staff .The first event, system ready, is derived from the external
environment and channels behavior to a Admin staff object. The Admin staff
enters a password. A request lookup event is passed to system that looks up
the password in the software system and returns a result (found or not
found) to Monitor. A valid password results in a password= correct event to
software system which then gives access to the admin staff and the admin
staff can add/update/delete the data of all other employees depending upon
his access levels. And this data can be displayed on the monitor or printed
from the printer up on request. TOP
This is a sequence diagram where the use case component is a Teacher .The
first event, system ready, is derived from the external environment and
channels behavior to a Teacher object. The teacher enters a password. A
request lookup event is passed to system that looks up the password in the
software system and returns a result (found or not found) to Monitor. A
valid password results in a password= correct event to software system which
then gives access to the teacher and the teacher can add/update/delete the
data of child. And this data can be displayed on the monitor or printed from
the printer up on request. TOP
