The Architectural Context diagram for the software is shown below. As it
is clear from the diagram, various actors are manager, adminn staff and
teacher, which use the system. The subordinate systems that will be used
by the software are the database (MS ACCESS) and Java. Also JDBC, ODBC
driver is required to connect java to database. Maintainence system is
super ordinate, which needs the software for testing and maintenance
purposes.

There are various types of architectures to represent the context. Basically
the architectures can be divided as system architecture and application
architectures. The system architecture is one we described above as
Architecture Context digram. There are many ways to represent application
architectures such as call and return, pipes and filters ,Object oriented
architecture etc.In our case call and return architecture and Object
oriented architecture are shown.However,the main emphasis is on object
oriented architecture. Firstly, Call and Return architecture is drawn .In
this, there is a main which calls the controller functions and these
functions further call the application functions. These functions then
return the required data.The call an return architecture for the child care software system is shown
below(using UML Component diagram):

**Basic info means name, address, tel no,DOB etc.

The Call and return architecture

TOPThe Call and return architecture has a main program, which controls all
others. Basically it selects the functions described in components below it.
The main program calls External communication management, which further
calls GUI implemented in project. Now depending on the access levels, it
calls the various functions. And these functions return some values that are
data. For example: when main calls add/modify/delete parent /child info,
this function further calls one of the functions shown below depending upon
the user wish. And this function then returns some data or simply performs
the specified function. Furthermore the user can call print reports, which
will generate various reportsAnd similar case is with the employees. One most important thing is that
some functions may be restricted for the use of actors for e.g. Employee
info can be accessed by the manager only and restricted to use by employee
and teacher.Next we are going to describe the object-oriented architecture. Since this
architecture is derived from Analysis classes, so first refer to the
analysis classes drawn in requirement specification. From those classes, the
design classes are made and component level designing is done. Now each
class is a component. And has some interface, which is described in the
component level designing. As we can see from the architecture drawn on next
page, we have elaborated each data field. For ex: consider the person class
in which address data field is elaborated which now contains four strings
Line1 address, line2 address, city and zip code. Similarly, other fields are
elaborated. Each class becomes a component and it interacts (interfaces)
with each other. This notation is represented by two lollipops at each
class. The interfaces are described in more detail in the next section
(Component level designing).The architecture describes the details about the classes we are going to use
and the variables and their types. The type of relationship is also shown
for example adminn staff access teacher class and manager access almost all
classes. As we can see it gives more details than call and return
architecture. The only difference in call and return architecture and object
oriented is that call and return architecture considers each function as
module where as object oriented considers each class as module. So it is
better to represent object-oriented view when using object oriented
programming, and it is better to represent using call and return
architecture when we use procedural programming. The object-oriented
architecture is follows on next page:

3.2.1.1 Processing narrative of component ParentThe 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.

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.

Component Parent;The intent of this component is to set basic parent data into the database
and get data from the databaseStartDeclare variables of the basic dataSet the basic data of the parent in the databaseGet the data from the databaseEnd

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.

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.

Component Employee;The intent of the component Employee is to set basic data of Employee into
database and get the data from the databaseStartDeclare variables of the basic data of the employeeSet values into the databaseCalculate the pay of the employeeGet the data from the databaseEnd

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.

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.

Component Child;The intent of the component Child is to set basic data of Child into
database and get the data from the databaseStartDeclare variables of the basic data of the ChildSet values into the databaseGet the data from the databaseEnd

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.

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.

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.StartDeclare variables of the student activitiesSet the data into the databaseGet the data from the database
End

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.

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.

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.StartSet the data of adminstaff into the databaseSet the data of classrooms into the databaseSet the data of the child immunizationSet the data of the student activitiesGet the data of the billing hrs of the child
Get the data of adminstaff into the databaseGet the data of classrooms into the databaseGet the data of the child immunizationGet the data of the student activitiesGet the data of the billing hrs of the childCalculate the pay bill of the childEndTOP

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.

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.

Component Manager;The intent of the component manager is to manipulate the data of the child,
Employee, set schedules, activities, print reports, Immunization.StartSet manager data into the databaseGet manager data from the databaseView the child data, Employee data, and classroom dataSet the classroom dataGet the classroom dataPrint the reportsEnd
TOP

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

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

Component Reports;The intent of this component is to print the reportsStartGet the child dataPrint the child data reportGet the employee dataPrint the Employee reportGet the classroom schedulesPrint the Classroom schedule reportGet the Employee pay dataPrint the Employee pay reportGet the child billing dataPrint the child billing reportEnd
TOP

3.3.1 Interaction DiagramsA 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