 |
|||||||
 |
 |
||||||
|
 |
||||||
 |
|||||||
 |
|||||||
 |
|||||||
DESIGN SPECIFICATION DOCUMENT
|
|
Presented By: |
|
 |
Bhaskara R. Mudunuru Aman Passi Pavan Daggumatti Omair Naeem |
1. Introduction1.1 Goals and Objectives
1.2 Statement of Scope
1.3 Software context
1.4 Major constraints2.1 Internal Data Structure
2.2 Global Data Structure
2.3 Temporary Data Structure
2.4 Database Description3. Architectural and Component level Design
3.1 Architectural Diagram
3.2 Description of Components3.2.1 Component Parent
3.2.2 Component Employee
3.2.3 Component Child
3.2.4 Component Teacher
3.2.5 Component Adminstaff
3.2.6 Component Manager
3.2.7 Component Reports3.3 Dynamic behavior for component
4.1 Description of the User Interface
4.2 Interface Design rules
4.3 Components available
4.4 UIDS Description5. Restrictions, Limitations and Constraints
6. Testing Issues
TABLE OF FIGURES
Figure 1. Architecture Context Diagram
Figure 2. Call and Return Architecture Diagram
Figure 3. Object Oriented Architecture Diagram
Figure 4. Sequential Diagram
1. INTRODUCTION
1.1 Goals and objectives
Developing the software for childcare is an attempt to make the things (current process) simpler, easier and efficient. There are many goals for which the software is developed such as:1) Reduces complexity
2) Costs Less
3) EfficientThe software can store information for unlimited number of children. It maintains a database of Family, Child, and Payroll information All that requires is just a computer with the software loaded that can perform many operations like generating bill statements, recording of payments and adjustments and financial reports, tracking and updating the children activities, immunization records, managing class schedules etc. So it reduces complexity, as there is no need of any paper and pencil work. Moreover it costs less to have a computer instead of having large number of people for various works like one for managing accounts and other for storing records of child and so on. It can track the child, parent and family information in very efficient way .So it’s really fast.
TOP
1.2 Statement of Scope
The software allows handling the child’s, parents and employees records. The child is identified by unique id (SS#). Further the software allows to generate billing records of child also. Not only for child, it stores information about the employees .So it can be used to generate paychecks, store in and out time etc.
Major inputsParents name, address, phone numbers and email address
Child name, birth date, class, photo
Immunization dates
Classroom schedules
Visitors’ information
Employee name, group
Billing period
Attendance
Overtime and late pickups
Employee pay period
Overtime
Tax rates
Processing Functionalities
Function Priority Child information entry Essential Parent information entry Essential Immunization tracking and alerting Essential Classroom scheduling Essential Attendance tracking Essential Billing Essential Overtime and late pickup billing Essential Receipt printing Essential Pay checks generating Essential Calculating pay hours and billing Essential Contract renewals Desirable Recording of correspondence with parents Desirable Programs and activities scheduling Desirable Customer account tracking Desirable Potential customer tracking Future Requirements Child progress tracking Future Requirements
Outputs
Parent information reports, Child information reports, Immunization reports, Classroom schedules, Attendance reports, Sign-in and sign-out sheets, Call sheets, Child enrollment and withdrawal reports, Billing reports, Receipts, Late fee and balance due reports, Employee payment report, Paychecks, Child progress reports, Programs and activities schedule reports, etc.
TOP
1.3 Software context
This childcare software is a very efficient one, which maintains database of parents, children and their short term and long-term activities. And this software is less expensive and also reduces complexity. In this software we use Java and Oracle and JDBC for the database connectivity. The database search is very fast such that the system responds to all requests with in 20 seconds.
TOP
1.4 Major constraints
The software is to run on a system, with SQL Therefore the systems should be properly connected to the server to access database. The Systems should be good enough to perform all the actions fast for example it is recommended that system should be no older than PII .The RAM should be no less than 128 MB. Detail constraints are described in subsequent sections.
TOP
2.0 DATA DESIGN
To understand the data design for the child care system its important to have a look at the overall design of the application.
As the application is being build in java, Microsoft Access, and JDBC the overall application design can be categorized into three parts based on the above mentioned application developing languages.
1. Front End Graphical User Interface
2. Back End Data
3. Internal Functional Procedures1. Graphical User Interface (GUI):
Java is being used for the development of the front end GUI. The GUI components temporarily stores the keyboard input by the users till its being used by the functional procedures. More explanation of the overall GUI and it components is available in the section 4 of the document.
2. Back End Data:
We are using Microsoft Access database management system at the back end for storing all information in the form of tables. These tables will be globally available to all the internal procedures. JDBC/ODC bridge is being used to establish connectivity to the database from the application. The DBMS system will be locally available on the machine where the application is running. However the same database can be accessed remotely as well.
For adding, deleting, accessing, and updating the data we are using SQL queries built in the internal procedures. Rest all the file and data management functionality is being provided by the DBMS.
3. Internal Functional Procedures:
The internal functional procedures are the logical entities that carry out different tasks of adding, updating, deleting, viewing, or printing the database. These procedures have been written in JDBC and provide a link between the GUI and the database. There are no data structure defined in any of these procedures and they utilize local variables to store intermediate information.
After describing the above view of the overall system we can discuss the rest of the topics related to the data design.
TOP2.1 Internal software data structure
There are no data structures available to the internal software architecture.
The intermediate information while updating or adding to any table is stored in the java swing component JTextField of the GUI. When the add or update button is pressed the information in those text fields is directly sent to the database for add or update.
For accessing or viewing any table the data is fetched directly from the DBMS to the java database object is displayed directly on the screen.
For report printing temporary local variables have been defined in the procedures with meaningful names to store different values and then print the report. After finishing those variables are discarded.
2.2 Global data structure
The only kind of data available globally to the whole system is the database itself stored in Microsoft Access. After the JDBS connection any data stored can be fetched, updated, or deleted. For more information regarding the database stored refer to section 2.4 of the document.
2.3 Temporary data structure
The Child Care application does not use any intermediate temporary files of its own. As data is being stored in a DBM system all the intermediate data it being stored by the DBMS until the command “commit” is being executed in the SQL query by the application. Hence no intermediate files or data structures are used.
2.4 Database description
Below are mentioned all tables, their corresponding attributes and a small description of each.
Table Name: Employee
Attributes: SSN, First Name, Last Name, Date of Birth, Email Address, Contact No., Address
Description: It holds all the general information of all the employees of childcare facility. Primary key of this table is employee SSN.
Table Name: Customer
Attributes: SSN, First Name, Last Name, Date of Birth, Email Address, Contact No., Address
Description: It holds all the general information of all the parent/customers of childcare facility. Primary key of this table is customer SSN.
Table Name: Child
Attributes: Parent SSN, First Name, Last Name, Date of Birth, Email Address (optional), Contact No., Address
Description: It holds all the general information of all the children admitted in the child care facility. Primary key of this table is parent SSN and the first name of the child. Parent SSN is also the foreign key of the table Customer.
Table Name: Appointment
Attributes: Parent SSN, First Name, Last Name, Time, Date, Comments
Description: Appointment table holds all the current appointments of customer or parent with the manager. It holds the date of the appointment, time of the appointment, and any special comments or reason for that particular appointment. Time and Date are the primary keys for the table to avoid duplication of appointments on a particular time of the day.
Table Name: Immunization
Attributes: Parent SSN, Chile First Name, Child Last Name, Medicine Name, Time, Date, and Comments
Description: The purpose of this table is to keep the record of any particular medication requires for a particular child. Parent SSN and First Name of Child specifically identify a child. Medicine name is the medicine to be given at certain time on a certain date. And comment can also be recorded if any required.
Table Name: Class Room
Attributes: Class Room No., Class Activity, and Date
Description: This table holds the classroom activities of all classrooms on a particular day. Class Room No is the primary key for this table.
Table Name: Waiting List
Attributes: Waiting List No., Parent SSN, First Name, Last Name, Date
Description: If on a particular day no more appointments can be scheduled then the name of the customer and SSN is stored in this table. The waiting list number acts as a primary key and is automatically generated in sequential order. And the customer is being served on the basis of waiting list no.
Table Name: Login
Attributes: Login ID, Password, Type
Description: This table will hold the login name and password for all the employees. The type filed identifies different access levels. ‘M’ mean managers, ‘A’ mean Admin Staff, and ‘T’ mean Teachers. Only manager can update this table.
Table Name: Punch In Punch Out
Attributes: Employee SSN, Punch In Time, Punch Out Time, Date, Hours
Description: This table holds the number of hours worked by each employee.
Table Name: Payroll
Attributes: Employee SSN, Rate, Overtime Rate
Description: This table holds, for each employee, the per hour amount to be paid and the overtime rate for that particular employee.
Table Name: Time In Time Out
Attributes: Parent SSN, Child First Name, Time In, Time Out, Hours
Description: This table holds the total number of hours spent by each child in the day care facility for the current session.
Table Name: General Information
Attributes: State Tax, Federal Tax, Other Tax, Hourly rate for Employee, Hourly Late for Children, Overtime Rate for Employee, Overtime Rate for Children.
Description: This table holds all the general information as the attributes name indicate that are going to be used for billing and payrolls.
TOP
3.0 ARCHITECTURAL AND COMPONENT LEVEL DESIGN3.1 Architectural Diagram
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.
TOP
Architectural Context Diagram
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
TOP
The 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 reports
And 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 admin 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:
Object Oriented Architecture (contd.to next Page)
TOP
3.2 Description of Components
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
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
TOP3.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
End3.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
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
TOP3.2.5.3.1 Design Hierarchy of the component Adminstaff
TOP3.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 TOP3.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. TOP3.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. TOP3.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 TOP3.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
4.0 User interface design
The application has a Graphical User Interface, which is build completely in java. Among the variety of libraries available in java we have chosen java swing library for development as more variety of component are available in it and more sophisticated techniques are available to change to appearances of those components if required in future.
4.1 Description of the user interface
4.1.1 Screen images
The GUI for the childcare system has been kept quite simple and follows a conventional style. Its very user friendly and do not require any training what so ever to work on.
Below is a detailed images and description of the GUI. The object and actions performed when you click them are also identified.
The first image is of the login screen. The user is supposed to have a login and password in order to login. User name and password can only be created by the manager of the company when he hires a new employee. TOP
After entering username and password you click on login and the program verifies the information entered. Upon verification the program either allows you to log in or a message will be displayed that the login was not verified.
The program also checks whether the user is a manager, administration staff, or teaching staff. Depending upon this information the program gives the respective interfaces hence there by restricting user to perform any other task except that can be performed by him/her.
Below is the manager interface. This interface has only those options that are only accessible to a manager. TOP
This above GUI is also self explanatory. The manager is supposed to click on any of the available options to add, update, or access them. Once clicked another GUI will appear that will have further option in any of the above category clicked.
Now the respective admin staff and the teacher interfaces are shown below.
As shown that all three interfaces for manager, administrator, or teacher differ in options. That way access levels are restricted. Also all three GUI follow the same convention. Logout and exit command buttons are also provided in each interface.
Now when you click on any of the available options another window appears and has sub options for that particular option. For instance, for employee option in the manager interface above is the sub option window that opens up. The choices are either to add, update, or delete a particular employee. TOP
The back command button takes you back to the previous screen. And the exit command button quits the application.
Exactly same window appears when clicked on customers or children and are shown below. TOP
Now when you click on add button the follow form appears that ask you to type in the information in the respective text fields.
After entering the information you click the add button to add it to the database. Or click the back button to go back.TOP
Otherwise if you click either the update or delete button in the previous window another window shown below appears that ask you to search for the particular
employee, parent, or child you are looking for to update or delete. You can either search the corresponding entry by first and last name or by SSN. If no entry in the database is found then a message is being displayed. Otherwise the same window as for adding is appeared with the person information in it. You can either edit the information or can delete it.
Same kind of options window appears when you click on reports and then in the sub options if a report is clicked to be printed it is sent to the printer. TOP
4.1.2 Objects and actions
The above shown GUI window consists of java swing components. A frame of size 800 * 500 is being used as a container for other components. The frame consists of label for displaying text. Text fields for entering or editing text. And command buttons are used for execution of procedures.
4.2 Interface design rules
To improve the usability of an application it is important to have a well designed interface. These “Eight Golden Rules of Interface Design" are a guide to good interaction design.
1) Strive for consistency.
Consistent sequences of actions should be required in similar situations; identical terminology should be used in prompts, menus, and help screens; and consistent commands should be employed throughout.
2) Enable frequent users to use shortcuts.
As the frequency of use increases, so do the user's desires to reduce the number of interactions and to increase the pace of interaction. Abbreviations function keys, hidden commands, and macro facilities are very helpful to an expert user.
3) Offer informative feedback.
For every operator action, there should be some system feedback. For frequent and minor actions, the response can be modest, while for infrequent and major actions, the response should be more substantial.
4) Design dialog to yield closure.
Sequences of actions should be organized into groups with a beginning, middle, and end. The informative feedback at the completion of a group of actions gives the operators the satisfaction of accomplishment, a sense of relief, the signal to drop contingency plans and options from their minds, and an indication that the way is clear to prepare for the next group of actions.
5) Offer simple error handling.
As much as possible, design the system so the user cannot make a serious error. If an error is made, the system should be able to detect the error and offer simple, comprehensible mechanisms for handling the error.
6) Permit easy reversal of actions.
This feature relieves anxiety, since the user knows that errors can be undone; it thus encourages exploration of unfamiliar options. The units of reversibility may be a single action, a data entry, or a complete group of actions.
7) Support internal locus of control.
Experienced operators strongly desire the sense that they are in charge of the system and that the system responds to their actions. Design the system to make users the initiators of actions rather than the responders.
8) Reduce short-term memory load.
The limitation of human information processing in short-term memory requires that displays be kept simple, multiple page displays be consolidated, window-motion frequency be reduced, and sufficient training time be allotted for codes, mnemonics, and sequences of actions.
4.3 Components available
Java swing library have many components available but for now only JFrame, JTextLabel, JTextField, and JButton are being used in the GUI. Among them only JButton have been added to the mouse action listener. Rests have no action listener attached to them. More components may be added in future if necessary.
TOP
4.4 UIDS description
No user interface development system has been used in the development of the childcare system.
5. Restrictions, Limitations and constraint
a. Only the manager can update or delete the information
b. Every employee should have ID and password to access the information.
c. The functions and data members of the component are called only when the user requires to manipulate the data of the component
d. The software is to run on a system, with SQL Therefore the systems should be properly connected to the server to access database.
e. The Software should be designed in such a way that the processing speed of the operations should be high
6.0 Testing Issues
Test strategy and preliminary test case specification are presented in this section. The various tests to be conducted to validate the software developed are login test, Child information report testing, Parent information report test, Employee information report test, employee pay check test, child billing report test.
There are two types of testing techniques. Black Box and White (Clear Box).
In Black Box we consider the domain of inputs to the system and without considering details in the software. In white box, we consider each and every path, branch for the testing.
TOP
Classes of testing
Description
Expected software response
Performance bounds
Components to be identified
Log in This test class is defined to validate whether the user is able to login with his ID and password. The user will be able to login when he enters the ID and password The user should not login if enters a wrong ID or password TestChild This test class is defined to validate whether all the child information is being displayed or not All the functions related to the child data are called in this test class This test will print the child information No Child, Parent, Classroom, Reports Test Parent This test class is defined to validate whether all the parent information is being displayed or not. All the functions related to the parent data are called in this test class
This test will print the parent information Parent, Reports TestEmployee
This test class is defined to validate whether all the employee information is being displayed or not. All the functions related to the employee data are called in this test class
This test will print the employee information Employee, Reports TestBill This test class is defined to validate whether the child monthly bills is being calculated correctly or not. All the functions related to the child data, child billing data are called in this test class.
This test class will display the child billing information Child, Parent, Reports, TestPay This test class is defined to validate whether the pay of the employee is being calculated and printed correctly or not. All the functions related to the employee data, pay data are called in this test class
This test class will display the employee pay information
Employee, Reports | Home | Hosting | Domains | Support | Contacts |
| Terms & Condition | Privacy Policy |
Copyright © 2005 by HostItWise.com Read our Copyright. All rights reserved.
