DISTRIBUTED MANAGEMENT SYSTEM
HSL
COMPANY PROFILE
Page 1
DISTRIBUTED MANAGEMENT SYSTEM
HSL
1. COMPANY PROFILE
Page 2
DISTRIBUTED MANAGEMENT SYSTEM
HSL
System Study
2. SYSTEM
2.1 EXISTING SYSTEM:
Page 3
STUDY
DISTRIBUTED MANAGEMENT SYSTEM
HSL
The existing system is the manual system. The manual system is prone to
error. It is time consuming.
It is very difficult for a person to produce report. There are chances for
changing the sales report and do malpractising. This system involves a lot of
manual entries with the applications to perform the desire task.
Limitations of system:
Data maintenance adopted by the present system is not accurate
Inaccurate result in case of duplicating, delay and inconsistency in reporting.
Generating consolidated reports is more difficult in manual system and it may
not be consistent.
The transactions are very time consuming.
There is no facility for the users to know weather the data is entered is valid or
not.
This disadvantage is the major cause of errors in transaction
It is not user friendly.
2.2 Proposed system:
The proposed system is designed to eliminate the drawbacks of the
existing system. It is designed by
Page 4
DISTRIBUTED MANAGEMENT SYSTEM
HSL
keeping in mind all the drawbacks of the present system in order to
provide a permanent solution to the problems. The primary aim of the new system
is to speed up transaction. The report is prepared for the sales done by the
representative and the distributor. The graphs are drawn for showing the pictorial
representation of sales done by the representative and distributor for a month and
year.
The bill is calculated at the time of sales and the information of sales is
entered into the rep and distributor table simultaneously. The representative code
and distributor code is validated and the process is proceeded. Accuracy for all the
date entered is maintained in the proposed system through validation and
verification from all the files. Verification of representative code, distributor code,
validation of records, etc.are performed with maximum accuracy. In short
efficiency is established.
The advantages of this system are
User friendliness is the key word for all the new software in the market.
The proposed system incorporates this concept into itself to guide the user.
At every stage of data entry necessary comments and validatory messages
are provided to the user.
The comments and validatory messages provide a way to get away with the
redundant data.
The proposed system is also expected to reduce 5the amount of paper work
involved.
2.3 Need For New System:
Page 5
DISTRIBUTED MANAGEMENT SYSTEM
HSL
Our system is developed to overcome the problems faced by the developers
in raising the issues and manual recording of data.
2.4 SYSTEM CONFIGURATION
Page 6
DISTRIBUTED MANAGEMENT SYSTEM
HSL
2.4.1 HARDWARE REQUIREMENTS:
Processor
: Intel pentium III (minimum)
Processor speed
: 800HZ
Hard disk capacity : 8GB
CD drive capacity : 32 * CD drive
Floppy disk
: 1.44MB
Ram capacity
: 256 MB
Keyboard
: 101 keys
2.4.2 SOFTWARE REQUIREMENTS:
Front End
Middle Ware
Back End
Servlet Runner
Page 7
DISTRIBUTED MANAGEMENT SYSTEM
HSL
Database connectivity
SYSTEM ANALYSIS
AND
DESIGN
Page 8
DISTRIBUTED MANAGEMENT SYSTEM
HSL
3. SYSTEM ANALYSIS & DESIGN
Introduction to System Analysis
System analysis is a process of gathering interpreting facts,
diagnosing problems, and using facts to improve the system. The objective of
the system analysis is to understand the important facts of current system by
studying it in detail. To accomplish this objective the following have to be
done.
Learn the details of the system as well as procedures currently in practice.
Develop insight into future demands of the organization on its growth, hike
in Competition, evolving new financial structures, introduction of new
technology, and changes in the customer needs.
Documentation details of the current system for discussion and review by
others.
Evaluate effectiveness and efficiency of the current system and procedure
taking into account the impact of anticipating future demands.
Recommend any revisions and enhancements to the current system,
indicating how they are justified. If appropriate, an entire new system may
be purposed.
Page 9
DISTRIBUTED MANAGEMENT SYSTEM
HSL
Document the new system features at a level of details that allows others to
understand its components and manage the new system developed.
SYSTEM
DESIGN
Page 10
DISTRIBUTED MANAGEMENT SYSTEM
HSL
SYSTEM DESIGN
Requirement analysis in a software engineering task , which bridges the gap
between the computer system engineering and software design. Requirement
analysis enables the system engineer to specify software function and performance
, indicate softwares interface with other system elements and establish constraints
that software must meet.
Requirement analysis provides the software designer with models that can
be translated into data, architectural, interface and procedural design. The design
of a system produces the details that state how a system meet the requirements
identified during system analysis. System specialists often refer to this stage as
logical design, in contrast to the process of developing program software, which is
referred to as physical design.
Data Flow Diagrams have been used in the design of the system. Data Flow
Diagram is a graphical tool used to describe and analyze the movement of data.
Page 11
DISTRIBUTED MANAGEMENT SYSTEM
HSL
The transformation of data from input to output, through processes may be
described logically using these Data Flow Diagrams.
The DFD shown to the user must represent only the major functions being
performed by the system. This is called Top Level DFD. If this process is complex
enough, it can be broken further into different levels. This process can be
continued till the process is simple. This is called the leveling of DFDs.
MODULAR DESCRIPTION
Page 12
DISTRIBUTED MANAGEMENT SYSTEM
HSL
3.1 MODULE DESIGN
PROBLEM DEFINATION
It focuses on specifying what the system or application required to
do.It allows individuals to see logical elements(What the system should do)apart
from the physical components it uses (computers,terminals and storage system).It
is the process of gathering and interpreting facts ,diagnosing problem and using
the information to recommend improvements to the system.
PROJECT DESCRIPTION
Page 13
DISTRIBUTED MANAGEMENT SYSTEM
HSL
DATA COLLECTION METHODOLOGY:
TIME SCHEDULE:
Analysis and Design: Approximately 15 days
Implementation
: Approximately 15 days
Post Implementation: Approximately 25 days
Testing
: Approximately 10 days
MODULES OF THE PROJECT
The project consists of the main home page which is divided into five
modules.Each module has several options which perform different operations.The
five modules are :
Page 14
DISTRIBUTED MANAGEMENT SYSTEM
HSL
1. Administrator module
2. Manager module
3. Distributor module
4. Sales manager module
5. Representative module
Administrator module
It consists of several options like:
1. Addition of sales representative
2. Sales representative sales details
3. Distributor sales details
4. Address modification
5. Product details
6. Feedback
Manager module
It consists of several options like:
1. Product view
2. Change own password
3. Sales representative sales report
4. Distributor sales report
5. Feedback
Page 15
DISTRIBUTED MANAGEMENT SYSTEM
HSL
Distributor module
It consists of several options like:
1. Registering new distributors
2. Sales details
3. Product view
4. Sales report
5. Mail options
Sales manager module
It consists of several options like:
1. Product view
2. Change own password
3. Sales representative sales report
4. Distributor sales report
Representative module
It consists of several options like:
1. Product view
2. Sales details
3. Areawise report
4. Sales report
5. Mail options.
Page 16
DISTRIBUTED MANAGEMENT SYSTEM
HSL
DATABASE DESIGN
Page 17
DISTRIBUTED MANAGEMENT SYSTEM
HSL
3.2 DATABASE DESIGN
ADDRESS CHANGE
FIELD NAME
Code
Add1
Add2
City
State
Pincode
Flag
TYPE
DESCRIPTION
Text
Code of rep. or
Text
distributor
Address of rep. or
Text
Text
Text
Number
Text
distributor
-do-do-do-doThis field will be set by
the admin
Page 18
DISTRIBUTED MANAGEMENT SYSTEM
HSL
LOGIN TABLE
FIELD NAME
Userid
Password
Code
Pos
TYPE
Text
Text
Text
Text
DESCRIPTION
User name
Users password
Code of the user
This field will be set as
per the users position
PRODUCT TABLE
FIELD NAME
Pcode
Pname
Price
TYPE
Text
Text
Number
DESCRIPTION
Product code
Product name
Price of a product
DISTRIBUTOR DETAILS
FIELD NAME
Dcode
Userid
Password
Name
Add1
Add2
City
State
Pincode
Email
Rphone
TYPE
Text
Text
Text
Text
Text
Text
Text
Text
Number
Text
Number
DESCRIPTION
Distributor code
User name
User password
Name
Address
-do-do-do-doEmail-id
Residence phone number
Page 19
DISTRIBUTED MANAGEMENT SYSTEM
HSL
Ophone
Dstate
Ddistrict
Dcity
Area
Amount
Number
Text
Text
Text
Text
Number
Office phone number
Distributors state
Distributors district
Distributors city
Distributors area
Deposit
REPRESENTATIVE DETAILS
FIELD NAME
Scode
Userid
Password
Rname
Dob
Qualif
Add1
Add2
City
State
Pincode
Phone
Emailid
Dcode
TYPE
Text
Text
Text
Text
Text
Text
Text
Text
Text
Text
Number
Number
Text
Text
DESCRIPTION
Representative code
Rep-id
Rep. password
Rep. name
Rep. dob
Rep. Qualification
Rep. address
-do-do-do-do-do-doDistributor code
DISTRIBUTORS SALES DETAILS
FIELD NAME
TYPE
Page 20
DESCRIPTION
DISTRIBUTED MANAGEMENT SYSTEM
HSL
Dscode
Ddate
Dcode
Pcode
Quantity
District
Text
Date/Time
Text
Text
Number
Text
Sales code
Sales date
Distributor code
Product code
Quantity
District
FEEDBACK DETAILS
FIELD NAME
Fno
Name
Phone
Fdate
Email
Sub
Enquiry
Code
TYPE
Text
Text
Number
Text
Text
Text
Memo
Text
DESCRIPTION
Feedback number
User name
Phone number
Feedback date
Users email
Subject
Feedback message
Type of enquiry
REPRESENTATIVE SALES DETAILS
FIELD NAME
Rscode
Rsdate
Rcode
Dcode
Pcode
Quantity
TYPE
Text
Date/Time
Text
Text
Text
Number
Page 21
DESCRIPTION
Sales code
Sales date
Representative code
Distributor code
Product code
Quantity
DISTRIBUTED MANAGEMENT SYSTEM
HSL
Reason
Text
Reason
CREDIT CARD DETAILS
FIELD NAME
Credit no
Bank
Amount
TYPE
DESCRIPTION
Text
Distributors credit card
Text
Number
number
Bank name
Amount
3.4 Output Design
Outputs from computer are required primarily to communicate the result of
processing to the user.They are almost to provide a paranent copy of these results
for later consulation.
There are various types of outputs required by most systems.they are
External outputs whose desitination is ouside the organization and which
requires the special attention because they project the image of
theorganization.
Intractive ouput,Which involve the user in communicating directly with the
computer
Page 22
DISTRIBUTED MANAGEMENT SYSTEM
HSL
DATAFLOW DAIGRAM
3.5 DATAFLOW DIAGRAM
L
LOGIN
ADMINISTATOR
MANAGERR
DISTRIBUTOR
SALES
MANAGER
REPRENSENTATIVE
YES
IF NEW
DISTRI-BUTOR
Page 23
GET THE
DETAILS
DISTRIBUTED MANAGEMENT SYSTEM
HSL
NO
OPTIONS
SALES
DETAILS
ENTER
SALES
DETAILS
PRODUCT
VIEW
REPORT
SALES
REPORT
MAIL
OPTIONS
ENTER
PRODUCT
DETAILS
CHANGE
PASSWORD
DISTRIBUTOR
REPORT
Level 0:
Page 24
CHANGE
ADDRESS
DISTRIBUTED MANAGEMENT SYSTEM
HSL
Page 25
DISTRIBUTED MANAGEMENT SYSTEM
HSL
Page 26
DISTRIBUTED MANAGEMENT SYSTEM
HSL
Page 27
DISTRIBUTED MANAGEMENT SYSTEM
HSL
Page 28
DISTRIBUTED MANAGEMENT SYSTEM
HSL
Page 29
DISTRIBUTED MANAGEMENT SYSTEM
HSL
Page 30
DISTRIBUTED MANAGEMENT SYSTEM
HSL
Page 31
DISTRIBUTED MANAGEMENT SYSTEM
HSL
Page 32
DISTRIBUTED MANAGEMENT SYSTEM
HSL
Page 33
DISTRIBUTED MANAGEMENT SYSTEM
HSL
Page 34
DISTRIBUTED MANAGEMENT SYSTEM
HSL
Page 35
DISTRIBUTED MANAGEMENT SYSTEM
HSL
SALES MANAGER MODULE:
Page 36
DISTRIBUTED MANAGEMENT SYSTEM
HSL
S
M
OPTIONS
PRODUCT VIEW
SALES REP.
SALES REPORT
CHANGE PASSWORD
DISTRIBUTOR SALES
REPORT
Sales Analysis
Representative
Page 37
DISTRIBUTED MANAGEMENT SYSTEM
HSL
Sales
Analysis
and
Reporting
Reports
Distributor
System
Graphs
Product
Level I:
Entry Details:
Representative Entry:
rscode
Rgi
Representat
ive code
validation
process
Error
rgi
Insert
Distributor Entry:
distributorc
ode
validation
discode
process
dsgi
Error
dsgi
Page 38
DISTRIBUTED MANAGEMENT SYSTEM
HSL
Insert
Product Information:
pcode
psgi
product
code
validation
process
Error
psgi
insert
SALES:
Qty, Price
Quantity & price
rscode
rscode
/discode
validation
rssales
rssales/dissales
discode
Sales
process
dissales
Page 39
DISTRIBUTED MANAGEMENT SYSTEM
HSL
pcode
pcode
validation
bill/master sales
pdt
Report:
Rep. date-wise report:
Rscode
Report
rep.
wise
corresp.Rep. date wise
report
rgi
details
Page 40
DISTRIBUTED MANAGEMENT SYSTEM
HSL
Rep. weekly report:
report
Report
rep.
wise
weekly
representative report
rgi
corresp.
detail
Rep. monthly report:
report
Report
rep.
wise
monthly representative
report
rgi
corresp.
detail
Rep. yearly report:
report
Report
rep.
wise
yearly representative
report
rgi
corresp.
detail
Distributors Yearly report:
discode
Report
distribut
or
Wise
dsgi
Page 41
corresp
Individual
Distributors
Yearly report
DISTRIBUTED MANAGEMENT SYSTEM
HSL
details
Product wise report:
pcode
pdt
Report
Product
wise
pdt.
Product Individual
report
details
Zone wise Report:
zcode
Report
zone
wise
Entire zone
Zone wise report
zgi
details
Page 42
DISTRIBUTED MANAGEMENT SYSTEM
HSL
REQUIRMENTS
SPECIFICATION
3.6 REQUIRMENT SECIFICATION
Page 43
DISTRIBUTED MANAGEMENT SYSTEM
HSL
System Testing
SYSTEM TESTING
Page 44
DISTRIBUTED MANAGEMENT SYSTEM
HSL
Theoretically, a new designed system should have all the pieces in
working order, but in reality, each piece works independently. Now is the time
to put all pieces into one system and test it to determine whether it meets the
users requirements. The purpose of the system is to consider all the likely
variations to which it will be subjected and then push the system to its limits. It
is tedious but necessary step in system development. One needs to be familiar
with the following basic terms.
4.1 UNIT TESTING:
Is testing changes made in an existing or a new program.
SEQUENTIAL OR SERIES TESTING: is checking the logic of one or
more programs in the candidate system, where the output of one program
will affect the processing done by another program.
SYSTEM TESTING: is executing a program to check logic changes made
in it and with the intention of finding errors making the program fail.
ACCEPTANCE TESTING: is running the system with live data by the
actual user of the system.
Testing is vital to the success of the system. System testing
makes a logical assumption that if all the parts of the system are correct, the
goal will be successfully achieved. In adequate testing or non-testing leads to
errors that may not appear until months later. Another reason for system testing
is its utility as a user-oriented vehicle before implementation. The best program
and the user have communication barriers due to different backgrounds. The
system tester (designer, programmer, or user) who has developed some
computer mastery can bridge this barrier.
(i)
Unit Testing:
This focuses on the smallest unit of software design. The
module using the details design description as a guide; important control paths
are tested to uncover errors within the boundary of the module.
Page 45
DISTRIBUTED MANAGEMENT SYSTEM
HSL
Unit test consideration:
The module interface id tested to ensure that information
properly flows into and out of the program unit under test. The local data
structures are examined to ensure that the data stored temporarily maintains it
integrity during all steps in an algorithm execution. Boundary conditions are
tested to ensure that the module operates properly at boundaries established to
limit or restrict processing. The test of data flow across a module interface is
required before any other test. If data do not enter and exit properly, all other
tests are moot.
Unit Procedure:
Unit test is normally considered adjunct to the coding style.
After source level code has been developed, reviewed and verified
for correct syntax, unit test case design begins. Each test case should
be coupled with a set of expected results.
Normally, a driver is a main program that accepts test case data,
passes such data to the module to be tested and prints the relevant
results. Stubs serve to replace modules that are subroutines called by
the module to be tested. A Stub or dummy stub program uses the
subroutine modules interface to do minimal data manipulation and
returns.
Unit testing is simplified when a module with high
cohesion is designed. When a module addresses only one function, the number
of test cases is reduced and errors can be more easily predicted and uncovered.
4.2 INTEGRATION TESTING:
Integration is a systematic technique for constructing the
program structure, while at the same time conducting tests to uncover errors
associated with interfacing. The objective is to make unit-tested modules and
build a program structure that has been dictated by design. Incremental
Page 46
DISTRIBUTED MANAGEMENT SYSTEM
HSL
integration is the program that is the program that is constructed and tested in
small segments where errors are easier to isolate and correct.
Top down Integration:
Top-down integration is an incremental approach to the
construction of program structure. Modules are integrated by moving
downward through the control hierarchy, beginning with the main control
module. Module subroutine to the main control module is incorporated into the
structure either in a depth-first manner is engaged for this system. Breadth-first
incorporates all modules directly subroutine at each level, moving across the
structure horizontally.
The integration process is performed in a series of five steps:
a. The main control module is used as a test driver and stubs are substituted
for all modules directly subroutine to the main control module.
b. Depending on the integration approach selected (depth or breadth first)
subroutine stub are replaced one at a time with actual modules.
c. Tests are conducted as each module is integrated.
d. On the completion of each set of test, another stub is replaced with the real
module.
e. Registration testing is conducted to ensure that new errors have not been
introduced.
4.3 VALIDATION TESTING:
Page 47
DISTRIBUTED MANAGEMENT SYSTEM
HSL
At the end of integration testing, the system is completely assembled
as a package with interfacing errors corrected after which a final series of
software tests namely validation testing begins. Validation succeeds when the
software functions in a manner that can be reasonably expected by the user.
Criteria:
Software validation is achieved through black box tests that
demonstrates conformity with requirements.
System Testing:
System testing is actually a series of different tests whose primary
purpose is to fully exercise the computer-based system. Although each test has
a different purpose, all work should verify that all system elements have been
properly integrated and perform allocated functions. Being the most important
test, the performance test is covered briefly below:
a. Performance Testing: For real-time systems, software that provides
required function but does not conform to performance requirement is
unacceptable. Performance testing is designed to test the run-time
performance of software within the context of an integrated system.
Performance testing occurs throughout all steps in the testing process. Even
at the unit level, the performance of an individual module may be accessed
as tests are conducted. However, it is not until all system elements are fully
integrated that the true performance of a system can be ascertained.
4.4 DEBUGGING:
Debugging is not testing not occurs as a consequence of testing, that
is when a test case uncovers an error, debugging is the process that results in
the removal of the error.
Normally three categories for debugging approaches are
proposed:
a. Brute force
b. Back-tracking
Page 48
DISTRIBUTED MANAGEMENT SYSTEM
HSL
c. Cause-elimination
a. Brute force:
This is the most common and least efficient method for isolating
the cost of a software error. Brute-force debugging method is usually applied
when all else fails. Using a let the computer finding the error philosophy,
memory-dumps are taken, runtime traces are invoked and the program is
loaded with WRITE (in this case message box) statements. In the information
that is produced, a clue is found leading to the cause of the error.
b. Back-tracking:
This is fairly common debugging approach that can be used
successfully in small programs. Beginning at the site where a symptom has
been uncovered, the source code is traced backwards (manually) until the site
of the cost is found.
c. Cause-Elimination:
This approach is manifested by induction/deduction and
introduces the concept of binary partition. A cause hypothesis is devised and
the error related data are used to prove or disprove the hypothesis.
Alternatively, a list of all possible causes is developed, and tests are conducted
to eliminate each. If initial tests indicate that a particular cause hypothesis
shows promise, that data are refined in an attempt to isolate the path.
Each of the debugging approaches can be supplemented with
debugging tools. A wide variety of debugging compilers, dynamic debugging
aids (tracers), automatic test case generators, memory dumps and crossreference maps can be applied. However, tools are not a substitute for careful
evaluation, based on a complete software design document and clear source
code.
Page 49
DISTRIBUTED MANAGEMENT SYSTEM
HSL
System Implementation
5 SYSTEM IMPLEMENTATION
System implementation is the stage of the project when the
theoretical design is turned into an operational and reliable working system.
Page 50
DISTRIBUTED MANAGEMENT SYSTEM
HSL
Implementation is the process of having system personnel check out
and new equipment into use ,train users ,install new application and construct any
files of data needed to use it.
It includes activities that take place to convert from the old to new
system.The new system may be totally new ,replacing an existing manual system.
This stage is crucial in achieving a successful new system and in
giving users confidence that the new system will work and be effective.
It involves careful planning, investigation of current system and its
constraints on implementation, design of methods to achieve the changeover
procedures,training of staff in changeover procedures,evaluation.
A parallel run between the manual system and proposed system was
made.
The results and reports generated were compared with maual results and it was
certified as an error free system.
Page 51
DISTRIBUTED MANAGEMENT SYSTEM
HSL
MAINTAINENCE
AND
ENHANCEMENT
MAINTAINENCE AND ENHANCEMENT
Page 52
DISTRIBUTED MANAGEMENT SYSTEM
HSL
The term Software Maintenance is used to describe the software
engineering activities that occur following delivery of a software product to the
customer. The maintenance phase of the software life cycle is the time period in
which a software product performs a useful work.
Maintenance activities involve making enhancement to software
products, adapting to new environments and correcting problems. software
product enhancement involves providing new functional capabilities, improving
user display and modes of interaction and upgrading external documents. Adapting
of software to new environments may involve moving to a different machine.
Problem correction involves modification and revalidation of software to correct
errors.
The enhancement of this project can be accomplished easily. That is,
any new functional capabilities can be added to the project by simply including the
new module in the homepage and giving a hyperlink to that module. Adaptation of
this project to a new environment is also performed easily. The further
enhancement is to make the project available online so that several branches of a
particular company can access from their own places.
Page 53
DISTRIBUTED MANAGEMENT SYSTEM
HSL
Conclusion
6. CONCLUSION
Page 54
DISTRIBUTED MANAGEMENT SYSTEM
HSL
The system is developed for automating the activities involved in the sales
done by the company. The data maintenance and reports generated are compatible
with the daily activities of the department.
The main advantage of the system over the existing system is the increase
in the speed of information retrieval since that data is maintained systematically
and any type of information required for the end user of the system can be
generated easily.
This system is of vital use to the sales incharge, to the distributor and to the
representative also. They can very well know about the sales done by them on a
particular day or a month, between dates, in an area,
Though Distributor Information System is so designed that not
much amendment is required. This system has provisions for adopting to future
enhancements.
The Timesheet Maintenance module allows the developers to enter their
work time and the effort put on their projects, their percent of completion of the
project and their work description.
This allows the organization to know the work productivity and the effort of
developers for that project. This system is fully developed using jsp and MySql.
The screen designing is developed in Macromedia Dreamweaver 4.0 and Abode
Photoshop 7.0 which are very efficient tools for front end designing. The java
script is used for the validations in the source code. Information outputs required
are made available in the required format. This project has given us immense
pleasure and has boosted our confidence level.
Limitations
Page 55
DISTRIBUTED MANAGEMENT SYSTEM
HSL
The Process Monitoring System is optimistic for the present requirements
of the organization.
The timesheet developed can be based only to some extent and has to
enhance like a spherical timesheet. Spherical Timesheet, which makes timesheet
creation fast, accurate and easy. The Issue Maintenance module cannot analyze the
work productivity of the organization.
Enhancements
Application software system has been developed to case out the problems
faced in the present system. The system described in this book have been
designed, tested and documented to a great extent.
This package is expected to be very useful to HCL Peripherals Ltd.
Goals
The goals that are expected to be achieved by the PMS are:
Track of time spent on tracking and resolving the issues.
Tracing the entire issue life cycle.
The timesheet works together with any current payroll packages
being used, as a tool for the capture, retrieval and storage of
organization man-hours and cost via a simple-to-use menu driver
user interface.
Its valuable tool for management and also it can be an added
advantage for the payroll department.
Page 56
DISTRIBUTED MANAGEMENT SYSTEM
HSL
Data Entry Screen
Page 57
DISTRIBUTED MANAGEMENT SYSTEM
HSL
7.1 SCREEN DESIGN
Bibliography
Page 58
DISTRIBUTED MANAGEMENT SYSTEM
HSL
BIBLIOGRAPHY
BOOKS
WEBSITES
Page 59
