Home

      Hosting      Domains       Support       Contacts

Back to main project description

User Interface Design
For
Nenios Child Care Software System


1. Introduction

2. Data Design

3. Architectural and Component level Design

4. User Interface Design

4.1 Description of the User Interface
4.2 Interface Design rules
4.3 Components available
4.4 UIDS Description

5. Restrictions, Limitations and Constraints

6. Testing Issues



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
         


  
 TOP
 

Leather Bags: IMedici Leather

| Home | Hosting | Domains | Support |  Contacts |
|
Terms & Condition | Privacy Policy |


 

Copyright © 2005 by HostItWise.com Read our Copyright. All rights reserved.

RushRash Inc |