CHAPTER 4 : DESIGN PHASE

Use case Diagram for Manager/Employee(sub-ordinate)

SEQUENCE DIAGRAM: USERLOGIN

user

Login Page :
Login

Insert Usr name &

pwd

Login Db

User MainScreen

Validate info
Success
Login successful

SEQUENCE DIAGRAM: Manage projects

Manager:
user

Create project:
projects
Insert Usr name &
pwd

Warning screen

Validate info
Error

Project not added

SEQUENCE DIAGRAM: ADD TASKS

Manager :
user

Task add: tasks

Insert Usr name &

pwd

tasks

User MainScreen

Validate info
success

Insert task in Db
Task added successfully

SEQUENCE DIAGRAM: UPDATE TASKS

Manager :
user

Task add: tasks

Insert Usr name &

pwd

tasks

User MainScreen

Validate info
Insert task in Db

success

Task status successfully

SEQUENCE DIAGRAM: UPDATE TASKS

Manager :
user

Create login
page

Login Db

Success screen

Fill in form
Validate info
Insert log
Login Created

ENTITY RELATIONSHIP DIAGRAM

success

Employee tasks

project
s

tasks

Task time

Employee

Employee tasks
Task ID
EMPLOYEE ID
Task assign date

Project
.
Project
Project
Project
date
Project

ID
name
descptn
start
end date

Task ID
.
Task name
Task
description
Task start
date
Task end

Task time
Task ID
.
Employee ID
Task- work start
date
Task-work end

Employee ID
.
Employee: Name
Employee: phone
Employee:
address

Database design tables were designed during systems design. In the following
diagram different data is stored and retrieved ideally.

INTERFACE DESIGN
To be fully satisfactory the interface of a system should be designed to match the
functionality, experience and expectations of its users as suggested by (Somerville, 2007).
Interface refers to the Graphical controls that the user is going to interact with in order to get
the proposed system to process data as desired. This shows the highest levels of Data
abstraction and hides the complexity of the system.
Input Design

These are used to capture data and should have a user friendly interface which accepts the correct
data types and rejects the wrong data types avoiding (GIGO) GABBAGE IN GABBAGE OUT
bringing the concept of data consistence, data integrity and timeless entry.

The input of data will be through forms and these are easy to use and they are accurate. Upon
logging into the system the end user is prompted to enter the password so that access into the
system can be granted. The input and output design forms are described below:
Guidelines for Input Forms

The proposed system will make use of graphical 3D input format. All these forms are going to be
characterized by:
i

Appropriate captions/titles to be used.

ii

Consistent use of controls and colors. Therefore a single color theme is to be used
throughout the system and a selected range of input controls (Text Boxes, Command
Buttons, Data Combos, and Data Grids) are to be consistently used.

iii

To ensure appropriate guide to user inputs , an extensive and exclusive use of tool tips is
to be used in the system.

iv

Where input is constant and categorized for example, users are not to input the data from
scratch, but to select from drop down lists.

To reduce input errors (thus improving data quality) data validations are to be taken care
of during the input process disabling some textboxes with Auto fill.

vi

To ensure easy use of system, simple and self-explanatory, constructive, consistent and
guide message dialogs are to be used throughout the processing of input.

As each Manager inputs data ensure that only valid data is input, where possible, for example
letters only for names or digits for phone numbers and enforce data uniformity (lower or upper
cases).

The new proposed system will contain input forms that will allow user to capture tasks and
generate reports after.
Taps intro

Interface screen shots

bn

CHAPTER FIVE: IMPLEMENTATION PHASE

5.0 INTRODUCTION

Delivering of the working system to the user is done on the implementation phase.
The new working system has to be tested for all the possible bugs and exceptions
before handing it to the client checking if the system is functional considering the

laid out specifications and requirements. A question comes on to saying IS THE

SYSTEM PROBLEM SOLVING The product moves from the theoretical
environment of development to the practical environment of the users. Users of the
system are trained on how to use the system before system starts to operate and
security measures are put in place to guard system against attacks and unauthorized
access. This phase involves the coding, installation of software, testing, and
training of users by the developer. The system is tested to discover any errors so
that corrections can be made before it can be installed.
5.1 CODING (Pseudo Code)

It is the turning of program logic into specific instructions that are to be executed
by the computer system. As highlighted in the development process, ASP.net(2010)
has been used for coding and construction and SQL Server database was used. All
the elements in the data dictionary conceptualized during the database design were
mapped into the relevant tables and its assigned attributes were aligned into the
appropriate field. The system functionality was developed as modules which were
finally integrated into one working system. Queries were also constructed to help
on gathering specific information using criterias. Such operations generally
included data retrieval (SELECT) operations and data manipulation (INSERT,
UPDATE, and DELETE) operations.

5.2 SYSTEM TESTING

This is where the system is searched through to figure out if it meets the
requirements and specifications.
5.2.1 Unit testing

Unit testing is when individual components are tested to ensure that they operate
correctly .It focuses on verification effort. On small unit software design, each
component is tested independently without user components. After the designing
of each form and its related code, it was being tested so as to examine whether the
unit is coded correctly before it is integrated with other code. For example the

login form was tested to find out if the system validates passwords and logs in user
according to access levels.
5.2.2 Module Testing

Module testing is the testing of a collection of dependant components. A single

module can be tested without the other system modules. For example tests were
carried out on reports to check if the user could get reports on sales that occurred at
a given time.
5.3 INSTALLATION

This is where the system is prepared for final use on the clients computer and is
installed for the practical work of the Employee task management system. On this
installation phase the executable files of the system are configured on the clients
machine.
5.3.1 User training

These user groups listed below will be trained on their relative use of the system.
Outlined below are the generalized areas where they will be trained:
i

System administrators- will be trained mainly on how to use the system

when adding tasks and updating tasks to their database. Their training
will include on how to set up and maintain parameters as well as to
manage the system security issues when others try to beat the system on
allocating lighter tasks.

ii

Employees - They will be trained mainly on how to view tasks allocated

to them and review progress and changes associated to them and

updating. Administrator to approve R-W-E (READ-WRITE-EXECUTE

rights) rights if mistakes occur.
iii

Manager- They will be oriented on how to access reports for the daily
projects and tasks as well as to view progress.

5.4 System conversion

This is a technical process whereby the new system replaces the old system and
will take effect after the establishment of the operational environment and training
has been established. This means that new data may have to be gathered, old data
re-analyzed and reformatted.

The following changeover strategies include:

Pilot Conversion
Direct Conversion
Phased Conversion
Parallel Conversion

5.4.1 Pilot conversion

It involves running the new system for one group of users. For example an
organization may first install the new system at one of its branches.

5.4.2 Direct conversion

It involves stopping the old system and starting the new system on a given date.
It is the least desirable approach because of its potential for problems and errors
when the old system is shut off and the new system is turned on instantly.

5.4.3 Phased conversion

Components of the new system are slowly phased in whereas components of the
old system are slowly faced out. This gradual replacement is repeated for each
application until the new system is running every application.
5.4.4 Parallel conversion

This conversion involves running both the old system and the new system for a
period of time. The output of the new system is compared closely with that of the
old system and any differences are reconciled. When users are comfortable that the
new system works correctly, the old system is eliminated.

5.4.5 Evaluation

After comparing the possible conversion methods the best option is to use parallel
conversion to introduce the new system, this will be used check if the system is
performing its entire functional requirement as specified. The new system is going
to run parallel with the old so as to compare functionality.
Data will be input on both systems and results will be compared and verified.
Errors will be identified and corrected without having to disrupt the daily
operations.
5.4.5.1 MAIN ADVANTAGES

Risk is relatively low

Gives end user enough time to verify the efficiency and effectiveness of the
new system
5.4.5.2 DISADVANTAGES

Costs are high since both systems will be operating for a certain period of time and
it is monotonous as the same work will be done twice.

DIAGRAM TO SHOW THE CONVERSION

NEW SYSTEM
FAVOURABLE

OLD SYSTEM

COMPARISON
OF RESULTS

NEW SYSTEM
OLD SYSTEM SHOWING
DEMERITS

5.5 Conclusion
I have managed to come up with a problem solving system that is acceptable.