Beruflich Dokumente
Kultur Dokumente
Project Paper Submitted in Partial Fulfillment of the Requirement for the Degree of
Bachelor of Information Technology with Software Engineering (Hons)
ii
ABSTRACT
Hence we are now in the high technology year, some of the institution are engaged in the
high technology gadgets to exist in traditional style of recording using manual
transactions. Invoice Tracking System proposed to solve the problem encountered by
many organizations. It is a big help for the organization, most especially to the
administrator and financial workers, in managing the invoice records. The financial
workers can track the process of invoice payment.
Through this Invoice Tracking System they can now easily locate the certain
invoices record from the number of records. They can easily update the invoices record
if there are some changes and added informations. This system designed to give the
quality of service of the organization.
iii
ABSTRAK
Kinidalamtahunteknologitinggi,
beberapainstitusiterlibatdalamalatteknologitinggiuntukwujuddalamgayatradisionalrakam
anmenggunakantransaksisecara
manual.
SistemPenjejakanInvoisdicadangkanuntukmenyelesaikanmasalah
dihadapiolehbanyakorganisasi.Iaadalahbantuan
terutamakepadapentadbirdanpekerjakewangan,
yang
yang
besarbagiorganisasi,
dalammenguruskanrekodinvois.
Para
MelaluiiniSistemPenjejakanInvoismerekakinibolehdenganmudahmencarirekodinvoistert
entudaripadabilanganrekod.Merekabolehmengemaskinirekodinvoisjikaterdapatbeberapa
perubahandanmaklumattambahanini.Sisteminidirekauntukmemberikualitiperkhidmatano
rganisasi.
iv
ACKNOWLEDGEMENTS
I take this opportunity to express my profound gratitude and deep regards to my project
advisor Mrs Noor Harnidda Khalid for his exemplary guidance, monitoring and constant
encouragement throughout the course of this project. The blessing, help and guidance
given by him time to time shall carry me a long way in the journey of life on which I am
about to embark.
Lastly, I thank almighty, my family, parents, brother, sisters and friends for their
constant encouragement without which this assignment would not be possible.
DECLARATION
Name
Metric. Number:
I hereby declare that this project paper is the result if my own work, except for
quotations and summaries which have duly acknowledged.
Signature :
Date :______________________________
vi
TABLE OF CONTENTS
ABSTRACT..........................................................................................III
ABSTRAK............................................................................................IV
ACKNOWLEDGEMENTS......................................................................V
DECLARATION....................................................................................VI
CHAPTER 1..........................................................................................1
INTRODUCTION...................................................................................1
1.0
Introduction........................................................................................................ 1
1.1.
Background Studies.............................................................................................. 2
1.2.
1.3.
Objective............................................................................................................ 5
1.4.
Scope of Project................................................................................................... 6
1.5.
Limitation of Project.............................................................................................7
1.6.
Problem Statement...............................................................................................9
1.7.
Definition of Abbreviations..................................................................................12
CHAPTER 2........................................................................................13
LITERATURE REVIEW........................................................................13
2.0
Introduction...................................................................................................... 13
2.1
2.2
2.3
vii
2.4
Solution to Problems........................................................................................... 19
2.5
Databases......................................................................................................... 23
2.6
2.7
2.8
2.9
Project timeline.................................................................................................. 29
CHAPTER 3........................................................................................32
ANALYSIS & DESIGN........................................................................32
3.0
Introduction...................................................................................................... 32
3.1
Research Methodology........................................................................................32
3.2
3.3
3.4
User Requirements............................................................................................. 42
3.5
System Requirements.......................................................................................... 45
3.6
Use Case........................................................................................................... 47
3.7
Class Diagram................................................................................................... 66
CHAPTER 4........................................................................................68
IMPLEMENTATION AND TESTING...................................................68
4.0
Introduction...................................................................................................... 68
4.1
Implementation................................................................................................. 69
4.2
Programming.................................................................................................... 70
4.3
4.4
Overall Plan...................................................................................................... 81
viii
4.5
Testing Requirements.......................................................................................... 84
4.6
Procedure Control.............................................................................................. 86
4.7
4.8
Evaluation...................................................................................................... 115
4.9
Installation..................................................................................................... 118
4.10
4.11
Troubleshooting Plan........................................................................................122
4.12
CHAPTER 5......................................................................................126
CONCLUSION...................................................................................126
5.0
Introduction.................................................................................................... 126
5.1
5.2
5.3
REFERENCES...................................................................................129
ix
LIST OF FIGURE
Figure 1: Checklist documentation for invoices..............................................................17
Figure 2: Use Case Diagram for Clerk and Head of Department....................................64
Figure 3: Use Case Diagram for Officer and Project Manager........................................65
Figure 4: Use Case Diagram for Administrator...............................................................65
CHAPTER 1
INTRODUCTION
1.0Introduction
The project system documentation is one of requirement for subject
CBBR4108 Project. This subject is one of the subjects for the final year
student to full fill an important component of the first degree curriculum.
Search invoices
Register invoices
Payment recommendations
Invoice review
Invoice approval
Report
System administrator
1.1.Background Studies
The Invoice Tracking system is design for the University Malaya Medical Centre
(UMMC). UMMC is a government-funded medical institution located in
LembahPantai, a southwest corner of Kuala Lumpur. It also knows as Hospital
University by local citizen. It was founded in 1962.
Malaya in 1963. Instruction started in 1964 with the first batch of students.
(UMMC)
DipertuanAgung,
was
Duli
officially
Yang
opened
MahaMulia
by
His
Seri
Majesty
the Yang
PadukaBaginda
Yang
UMMC strive to provide the best services and treatment. Efforts that are
ongoing are to provide medical services, learning and research with the best
efficiency to their customer.
After the head of department have approved the invoice, the clerk will
submit the invoice to the finance department. All related documents will
submitted to the finance department for the next process which is the
payment process by the finance department.
Sometimes the invoice was missing during the processing of the invoice
payment. This is because of the no backup, no security and the appropriate
filling. There was a case where there was a water leaking on filling room, all
the original invoice is wet and destroyed. Therefore, the UMMC need to
contact the supplier and ask the supplier to re-issue the invoice.
It is hard for UMMC if they keep using manual filling method to handle
all the invoice payment processes. Therefore the UMMC especially the
finance department needs an appropriate system to handle this problem so
that all the process of invoice payment can be done smoothly.
1.3.Objective
The main objective of the project is to produce a web based system with
database called Invoice Tracking System which provides faster and
systematic data or information management site for invoices fully owned by
the UMMC finance department.
This system will be put at UMMC Portal (my.ummc.edu.my) under the eservices in management group. This system is one of the sub-system that is
can be access via my UMMC portal system that only the UMMC staff have
the authorization.
1.4.Scope of Project
Tracking suppliers invoices is important for the UMMC is one of the
important things that the UMMC take serious note, this is because by
tracking the invoices it could facilitate the payment of invoices to suppliers.
Therefore, the organization decides to implement a computerized system for
this invoice tracking.
1.5.Limitation of Project
Based on analysis and fact finding there are several limitations toward the
proposed project. Below are the limitations of proposed Invoice Tracking
System:
1.6.Problem Statement
According to fact finding and analysis, there are several problems that have
been identified. The problems that UMMC finance department having is:-
Managing in manual filing base system is very difficult for the many
data that need to be handling. There are a lot of problem occurred when
doing many tasks with manually such as error writing for the customer
details, difficult to read some writing by many person, unclear word to be
read and need more time to done tasks.
supplier or vendor to reissue the invoice due there is no backup for the
invoices and related document.
1.7.Definition of Abbreviations
10
No. PO Refers to the registered purchase order number that has been
registered under UMMC finance system database.
No. GRN Refers to the guarantee refer note number that has been
registered under UMMC finance system database.
CHAPTER 2
LITERATURE REVIEW
11
2.0Introduction
12
With the purposed system, the problems that UMMC finance department
face could be solve. Firstly with the purposed computerized system, the
finance department does not have to use manual filling anymore. This is
because all the information and data will be store into database that located at
IT department data centre.
With the Invoice Tracking System, the report can be generating from the
system. When the reports are generated from the system, the data and
information from the report are more accurate than manual report.
13
The testing stage is the pilot test. The pilot test will be implementing on
IT department and finance department first. The duration for this phase is for
one week. The clerk at the IT department needs to use the system under
supervision of programmer in charge of the system. If there are some errors
or bugs that occur during this phase, the programmer in charge will fix the
error immediately. On the finance department side, the clerk in charge for the
system will review the data and invoices via the system. Then they will
manually key-in the invoice data into the Century System which is the
current UMMC finance system.
After the pilot test is done, user training for each clerk in charge for this
system from each department in UMMC will be implementing. The user
training will involve the entire sub module in the system. Then, the system
will go for sign off procedure on the purposed date.
After the sign off procedure the system developers will work on support
basis to handle system bugs and errors reported by the end user. The
application support team from IT department will be responsible for first
14
level support and to work close with helpdesk team for hardware
maintenances.
15
2.3.2 Questionnaire
16
2.4Solution to Problems
As for the solution for UMMC, there are three possible solutions that can be
implemented in the organization to help its daily business in invoice tracking
system. The possible solution is:
17
The first solution that could be used by the development team to help
UMMC face the problem which occur which is using manual system is
by developing a computerized database system to the company. The
developed system will be working as a standalone system. The system
will be installed in the department clerk computer and department clerk is
the only user of the system. The standalone system means that the system
will working on task without need to depend on other sources or link to
other computer or network for the system to be able to run. The system
also store data in the database and made all process for the user is easy as
the user does not have to master other system in order to use the system.
This is because, stand standalone system do the entire task without any
effect from other system.
18
19
20
2.5Databases
Database is a structured set of data or information held in a computer,
especially one that is accessible in various ways. A database could be as
simple as an alphabetical arrangement of names in an address book or as
complex as a database that provides information in a combination of formats.
In this project, database is used to store and keep all information that is
related to invoices. Therefore they can remove the traditional way of keep all
21
22
crashes, or the network hiccups, this will not affect the underlying tables;
instead the data manager realises that the transaction has not been completed
and does not commit the partially transmitted data to the database. The
database therefore continues to run without problem.
A file server system such as Access is designed for small workgroups and
is scalable to perhaps 10 concurrent clients. Above this level performance
starts to degrade rapidly as more users are added. With the SQL Server
client/server architecture many hundreds or even thousands with the
appropriate infrastructure, of concurrent users can be supported without
significant performance degradation.
23
The benefits of SQL Server over Access are improved reliability, better
performance, reduced network traffic and increased scalability
As a web editor, DreamWeaver can hide the details of pages' HTML code
from the user, making it possible for non-coders to create web pages and
sites. DreamWeaver also allows users to preview websites in many browsers,
provided that they are installed on their computer. It also has some site
24
management tools, such as the ability to find and replace lines of text or code
by whatever parameters specified across the entire site, and a templatization
feature for creating multiple pages with similar structures. The behaviors
panel also enables use of basic JavaScript without any coding knowledge.
Classic ASP pages have the extension .asp instead of .htm, when a page
with the extension .asp is requested by a browser the web server knows to
interpret any ASP contained within the web page before sending the HTML
25
produced to the browser. This way all the ASP is run on the web server and
no ASP will ever be passed to the web browser.
Any web pages containing ASP cannot be run by just simply opening the
page in a web browser. The page must be requested through a web server that
supports ASP, this is why ASP stands for Active Server Pages, no server, no
active pages.
26
2.9Project timeline.
Project timelines are used to help team members to know what milestones
need to be achieved and under what time schedule. Project timeline is one of
several horizontal lines in a job chart (each drawn at specific points in time)
to relate the completion of two or more jobs to the start of one or more other
jobs. First timeline is the start line and the last one is the finish line.
For UMMC Invoice Tracking System project, a Gantt chart will be used
as project timeline. For UMMC Invoice Tracking System project time line
please refer on page 29 and 30.
27
28
29
CHAPTER 3
ANALYSIS & DESIGN
3.0Introduction
Analysis and design chapter explain the research methodology for the
purposed system project development. Furthermore, in this chapter the
program design, database design and interface design also will be discussed.
3.1Research Methodology
A guideline system for solving the problem statement that has been identified
is known as research methodology. This guideline is using specific
component such as phase, tasks, and methods, tools and techniques. There
are many methods used in different types of research. The properly
30
conducted research will a reliable research with proper testing conducted and
come comes with not extraneous variables.
Project planning
Requirement definition
Design
Development
Testing
Installation and implementation
The intent of a software development life cycle process it to help
3.1.2 Prototyping
31
The first element, prototyping, is the construction of a featurelight, reduced-scalability application in a short amount of time. The
objective is to create a working application to help a user flesh out
requirements.
analysis,
designing,
testing,
implement,
and
system
3.1.3 Structured
Systems
Analysis
and
Design
(SSADM)
32
2.
3.
4.
33
5.
by many
commercial
businesses,
consultants,
educational
Prototyping
SSADM
model is time
prototyping method as
consuming as it is
development step by
phase.
Model
Time
every development
time.
phase.
Project
Context
prototype which
depends on customer
requirements and
to do different task at
details implementation
same phase
Cost
As prototyping method
Structured Analysis
more cost in
completing the
development. The
implementation but it
implementation as the
depends on the
prototype build.
SDLC it is resource
intensive.
system is reduce
36
37
This method concentrate the developer to what the system has to do and
how the system will be developed. Using this method, the developer can
interact with user in developing this system from time to time as this method
is including user involvement.
By using this method, the developer can produce the output of the system
by stage. This also means that developer can do the physical design while
doing the logical design of the system. The development of the system will
become easier and faster. The developer also can identify the error and also
any enhancement of the system on time.
3.4User Requirements
The user requirement of the system for the UMMCs Invoice Tracking
system data management, data acquisition, invoice review by project
manager, invoice approval by head of department and report features.
All data will be stored in the database for user retrieval. The future data
will be stored in the same storage. This data will also be kept in the
portable hard disk as a backup file.
39
40
The system administrator is the other module that the user request. This
module is required because it easier for the admin to maintained the
system and controls the user access for the system.
3.5System Requirements
The system requirement below explains of processes and its functions for the
Invoice Tracking System software. The requirement will divided into 4
requirements which are clerk or data entry staff requirement, officer
requirement, project manager requirement and head of department
requirement.
i.
ii.
iii.
iv.
v.
vi.
vii.
viii.
ix.
x.
Search invoices
Key in invoices
Upload attachment
Download attachment
Delete attachment
Select officer in charge for recommendations
Select project manager in charge for review
Select head of department in charge for approval
Key in activities log
Generate report
Search invoices
View invoice
Download attachment
Key in invoice recommendations
Key in activities log
Search invoices
View invoice
Download attachment
Key in invoice review
Key in activities log
Search invoices
View invoice
Download attachment
Key in invoice approval
Key in activities log
3.5.5 Administrator
i.
42
ii.
iii.
iv.
v.
Search invoice
View invoice
Download attachment
Key in activities log
3.6Use Case
A graphic depiction of the interactions among the elements of a system is a
use case diagram. A use case is a methodology used in system analysis to
identify, clarify, and organize system requirements. In this context, the term
"system" refers to something being developed or operated, such as a mailorder product sales and service Web site. Use case diagrams are employed in
UML (Unified Modelling Language), a standard notation for the modelling
of real-world objects and systems.
System objectives can include planning overall requirements, validating a
hardware design, testing and debugging a software product under
development, creating an online help reference, or performing a consumerservice-oriented task.
A use case diagram contains four components.
43
3.6.1 Use
Case
Diagram
for
UMMC
Invoice
Tracking System
Search invoices
Actor/Actors
Entry Condition
Action Performed
Exit condition
invoice information
Selected invoice information will appear on
invoice page
Exceptions
None
Special
None
requirements
44
Key in invoices
Actor/Actors
Clerk
Entry Condition
Action Performed
Exit condition
Exceptions
Special
None
requirements
Upload attachment
Actor/Actors
Clerk
45
Entry Condition
Action Performed
Exit condition
redundancy.
Selected invoice information will appear on
invoice page with uploaded document information.
Exceptions
Special
None
requirements
Download attachment
Actor/Actors
Entry Condition
46
Action Performed
Exit condition
Exceptions
None
Special
None
requirements
Delete attachment
Actor/Actors
Clerk
Entry Condition
Action Performed
Exit condition
Exceptions
None
Special
None
requirements
Actor/Actors
Clerk
Entry Condition
Action Performed
48
Exceptions
Special
None
requirements
Actor/Actors
Clerk
Entry Condition
Action Performed
redundancy of data.
Selected project manager name for review will
appear.
Exceptions
Special
None
requirements
Actor/Actors
Clerk
Entry Condition
Action Performed
Exit condition
Exceptions
Special
None
requirements
Actor/Actors
Clerk
Entry Condition
Action Performed
Exit condition
recommendations
System will navigate user back to the invoice
page.
Exceptions
Special
None
requirements
51
Actor/Actors
Entry Condition
Action Performed
Exit condition
Exceptions
None
Special
None
52
requirements
View invoices
Actor/Actors
Entry Condition
Action Performed
Exit condition
information
Selected invoice information will appear on
invoice page
Exceptions
None
Special
None
requirements
53
Actor/Actors
Officer
Entry Condition
Action Performed
Exit condition
invoice review
Pending invoice recommendation list page will
appear.
Exceptions
None
Special
None
requirements
54
Actor/Actors
Project manager
Entry Condition
Action Performed
Exit condition
Exceptions
None
Special
None
requirements
55
Actor/Actors
Head of department
Entry Condition
Action Performed
Exceptions
None
Special
None
requirements
56
Generate report
Actor/Actors
Clerk
Entry Condition
Action Performed
Exit condition
Exceptions
None
Special
None
requirements
57
Actor/Actors
Administrator
Entry Condition
Action Performed
Exceptions
None
Special
None
requirements
58
59
60
3.7Class Diagram
Class diagrams are the mainstay of object-oriented analysis and design. Class
diagrams show the classes of the system, their interrelationships (including
inheritance, aggregation, and association), and the operations and attributes
of the classes. Class diagrams are used for a wide variety of purposes,
including both conceptual/domain modelling and detailed design modelling.
61
62
CHAPTER 4
IMPLEMENTATION AND TESTING
4.0Introduction
In this chapter, implementation on application will be discussed. It will focus
on how to execute the implementation plan for this project. Other than that, a
testing plan and procedure also will be discussed in this chapter. Furthermore
the backup strategy for this project also will be discussed.
63
4.1Implementation
Implementation is the realization of an application, or execution of a plan,
idea,
model,
design,
specification,
standard,
and
algorithm.
An
software
component,
or
other
computer
system.
Many
4.2Programming
64
For this project, an Active Server Page or called as ASP classic will be
used as programming language. For completed system programming
codes please refer on the CD that has been attached.
Close Connection
setconnfinance=nothing
aktivitiRS.addnew
aktivitiRS("tarikhaktiviti") = now
aktivitiRS("idinbois") = idinbois
aktivitiRS("idkodproses") = 1
aktivitiRS("aktif") = "Y"
aktivitiRS("datecreated")
= now
4.2.2 Insert into
database
aktivitiRS("createdby") = gl_nokplpengguna
aktivitiRS("lastupdate") = now
aktivitiRS("lastupdateby") = gl_nokplpengguna
aktivitiRS.update
aktivitiRS.close
setaktivitiRS=nothing
65
setSimpanKemaskini=server.CreateObject("adodb.recordset")
SimpanKemaskini("idinbois")
= idinbois
SimpanKemaskini("kodpembekal")
= kodpembekal
SimpanKemaskini("namapembekal")
SimpanKemaskini("jenisinbois")
SimpanKemaskini("nopo")
SimpanKemaskini("nogrn")
= namapembekal
= jenisinbois
= nomborpo
= nomborgrn
SimpanKemaskini.update
SimpanKemaskini.close
setSimpanKemaskini=nothing
66
setSimpanKemaskini=server.CreateObject("adodb.recordset")
sql= "select * from inv_fail where idfail='"&idfail&"' "
SimpanKemaskini.open sql,connfinance,3,3
SimpanKemaskini("aktif") = "N"
SimpanKemaskini.update
SimpanKemaskini.close
setSimpanKemaskini = nothing
With UMMC IT Department Policies, the data must not deleted from
database but must be mark as archive so that the data can be retrieve back
if the user accidently delete the data from the system.
67
= request("idinbois")
setsemak_inboisRS = server.CreateObject("adodb.recordset")
sql = "select * from inv_inbois where idinbois ='"&idinbois&"'
and aktif = 'Y'"
semak_inboisRS.open sql,connfinance,3,3
68
4.3.1 Introduction
The project is to develop and replace the current manual system used by
UMMC. The system is Invoice Tracking system which are consist of
database that storing details about the suppliers invoices. It also can
produce the report about the invoices.
By using this invoice tracking system, the activities that can be handled
by this system are like:
69
This system is the way to provide easy and fast report details for
the invoices details and invoice processes tracking details.
70
This is the Master Test Plan for the Invoice Tracking System project. This
plan will address only those items and elements that are related to the
Invoice Tracking System process, both directly and indirectly affected
elements will be addressed. The primary focus of this plan is to ensure
that the new Invoice Tracking System application provides the same level
of information and detail as the current system while allowing for
improvements and increases in data acquisition and level of details
available. Specified objectives for this test plan:
Ensure the flow of system run smoothly include user interface control
o The test is based on flow of Invoice Tracking System which
consists of various types of tasks. The test runs for invoice
details, recommendation details, invoice review details and
approval details. Which the flow must be smoothly to ensure
user of system did not feel lost from browsing the system
which may result in misconduct of system.
71
73
At the end of test, this UAT form are very usable for the
programmer in order to make any amendment or maintenance in order to
make this system more functional and especially, the website is meet the
user requirement and satisfaction
74
4.4Overall Plan
Task
10/11/2013
User authentication
11/11/2013
75
76
Invoice documents
o The numbers of invoice document for each type of invoice are
correct
The flow of system run smoothly include user interface control and
test covers all forms/pages of system
o The flow run smoothly and user of system did not feel lost
from browsing the system which may result in misconduct of
system.
o The button runs well, so do the link references as it does not
contains error.
77
4.5Testing Requirements
Processor
Intel
Pentium/Celeron
family,
AMD
Pentium
IV
2.0
GHz
or
higher
recommended.
Memory
Hard Disk
VGA
applications
from
start
to
finish
with
Adobe
78
Google chrome
o Google Chrome is used for interface to interact with the
database (MS SQL Server) and also server (ISS). Google
Chrome can be downloading from google chrome website.
4.5.3 Personnel
The personnel that will be conducting the testing are the system analyst,
programmer and project manager. The system analyst will test the input
and output of data, flow of the system and user interface control. The
programmer will test the code wrote as to assure it run line by line and
execute perfectly. The project manager will test the overall of system
such as the interface, links, header and consistencies of elements used.
4.6Procedure Control
79
80
For the next test case, it will be the document that required
uploading based on the type of invoice. If the required document is not
complete uploaded, the system will display error message and will not let
the user to proceed to the next step.
For the final test case, all links, buttons, text box and combo box of
all forms/pages will be tested by insert data and execute by click the
button and link. The data inserted supposed to match with database data
type while all links run smoothly as to prevent lost in navigation.
81
For the final test case, all links, buttons, text box and combo box of
all forms/pages will be tested by insert data. If the data inserted does not
to match with database data type, the page will display error in Microsoft
SQL Server data type syntax. As for the links, if it did not run smoothly, it
will cause failure to browse the selected page and may also result to be
lost in navigation.
82
UMMC IT DEPARTMENT
TEST CASE DESCRIPTION
Test Case Number: 1
Date:10/11/2013
Test Case Description: User authorization
Program Name: Invoice Tracking System
Test Case Prepared By: Nor Zainan Ashraf Bin Manan
Test Administrator: Yamin Bin Ahmad
Description of Test Data:
Tester will click on the invoice tracking system icon
Expected Result:
For the correct authentication, the system will display the welcome form with menus
button. If the user dont have authorization, the system will display the error page that
prompt user to get authorization from IT department
Actual Result:
For the correct SSO id and password inserted, the system will display the welcome
form with menus button. If the user dont have authorization, the system will display
the error page that prompt user to get authorization from IT department
84
UMMC IT DEPARTMENT
TEST CASE RESULTS
Test Case Number:1
Date:10/11/2013
Program Name: Invoice Tracking System
Module Under Test: User authorization
Explanation on difference between actual and expected output:
There is no difference between the actual and expected output. The function on the
system work as expected.
Suggestions for next steps:
No any suggestions
85
UMMC IT DEPARTMENT
TEST CASE DESCRIPTION
Test Case Number: 2
Date:10/11/2013
Test Case Description: Test all the button and links contains in button side frame
Program Name: Invoice Tracking System
Test Case Prepared By: Nor Zainan Ashraf Bin Manan
Test Administrator: Yamin Bin Ahmad
Description of Test Data:
All links and buttons are click and executes.
Expected Result:
All links and buttons are functioning same as the name button. Button home link to
home page, button search invoice link to search invoice page, button new invoice link to
new invoice page, button report link to report type page, button invoice
recommendations link to invoice recommendations page, button invoice review link to
invoice review page, button invoice approval link to invoice approval page and button
administrator link to administrator page.
Actual Result:
The links and button runs smoothly and correct, user browses the selected page and also
does not feel lost in navigation.
86
UMMC IT DEPARTMENT
TEST CASE RESULTS
Test Case Number:2
Date:10/11/2013
Program Name: Invoice Tracking System
Module Under Test: Test all the button and links contains side button frame
Explanation on difference between actual and expected output:
There is no difference between the actual and expected output. The function on the
system work as expected.
Suggestions for next steps:
No suggestion.
87
UMMC IT DEPARTMENT
TEST CASE DESCRIPTION
Test Case Number: 3
Date:10/11/2013
Test Case Description: Test all the button and links contains in new invoice page
Program Name: Invoice Tracking System
Test Case Prepared By: Nor Zainan Ashraf Bin Manan
Test Administrator: Yamin Bin Ahmad
Description of Test Data:
All links and buttons are click and executes.
Expected Result:
All links and buttons are functional.
Actual Result:
The links and button runs smoothly and correctly, user browses the selected page and
also does not feel lost in navigation.
88
UMMC IT DEPARTMENT
TEST CASE RESULTS
Test Case Number:3
Date:10/11/2013
Program Name: Invoice Tracking System
Module Under Test: Test all the button and links contains in new invoice page
Explanation on difference between actual and expected output:
There is no difference between the actual and expected output. The function on the
system work as expected.
Suggestions for next steps:
No suggestion.
89
UMMC IT DEPARTMENT
TEST CASE DESCRIPTION
Test Case Number: 4
Date:10/11/2013
Test Case Description: Test all the button and links contains in upload attachment
Program Name: Invoice Tracking System
Test Case Prepared By: Nor Zainan Ashraf Bin Manan
Test Administrator: Yamin Bin Ahmad
Description of Test Data:
All links and buttons are click and executes. All attachment can upload and store into the
server.
Expected Result:
All links and buttons are functional. All attachment can upload.
Actual Result:
The links and button runs smoothly and correctly, user browses the selected page and
also does not feel lost in navigation.
90
UMMC IT DEPARTMENT
TEST CASE RESULTS
Test Case Number:4
Date:10/11/2013
Program Name: Invoice Tracking System
Module Under Test: Test all the button and links contains in upload attachment
Explanation on difference between actual and expected output:
There is no difference between the actual and expected output. The function on the
system work as expected.
Suggestions for next steps:
No suggestion.
91
UMMC IT DEPARTMENT
TEST CASE DESCRIPTION
Test Case Number: 5
Date:10/11/2013
Test Case Description: Test all the button and links contains in download attachment
Program Name: Invoice Tracking System
Test Case Prepared By: Nor Zainan Ashraf Bin Manan
Test Administrator: Yamin Bin Ahmad
Description of Test Data:
All links and buttons are click and executes. All attachment can download and view.
Expected Result:
All links and buttons are functional. All attachment can download.
Actual Result:
The links and button runs smoothly and correctly, user browses the selected page and
also does not feel lost in navigation.
92
UMMC IT DEPARTMENT
TEST CASE RESULTS
Test Case Number:5
Date:10/11/2013
Program Name: Invoice Tracking System
Module Under Test: Test all the button and links contains in download attachment
Explanation on difference between actual and expected output:
There is no difference between the actual and expected output. The function on the
system work as expected.
Suggestions for next steps:
No suggestion.
93
UMMC IT DEPARTMENT
TEST CASE DESCRIPTION
Test Case Number: 6
Date:10/11/2013
Test Case Description: Test all the button and links contains in officer, project manager
and head of department name selection
Program Name: Invoice Tracking System
Test Case Prepared By: Nor Zainan Ashraf Bin Manan
Test Administrator: Yamin Bin Ahmad
Description of Test Data:
All links and buttons are click and executes.
Expected Result:
All links and buttons are functional.
Actual Result:
The links and button runs smoothly and correctly, user browses the selected page and
also does not feel lost in navigation.
94
UMMC IT DEPARTMENT
TEST CASE RESULTS
Test Case Number:6
Date:10/11/2013
Program Name: Invoice Tracking System
Module Under Test: Test all the button and links contains in officer, project manager and
head of department name selection
Explanation on difference between actual and expected output:
There is no difference between the actual and expected output. The function on the
system work as expected.
Suggestions for next steps:
No suggestion.
95
UMMC IT DEPARTMENT
TEST CASE DESCRIPTION
Test Case Number: 7
Date:10/11/2013
Test Case Description: Test all the button and links contains in payment recommendation
page
Program Name: Invoice Tracking System
Test Case Prepared By: Nor Zainan Ashraf Bin Manan
Test Administrator: Yamin Bin Ahmad
Description of Test Data:
All links and buttons are click and executes.
Expected Result:
All links and buttons are functional.
Actual Result:
The links and button runs smoothly and correctly, user browses the selected page and
also does not feel lost in navigation.
96
UMMC IT DEPARTMENT
TEST CASE RESULTS
Test Case Number:7
Date:10/11/2013
Program Name: Invoice Tracking System
Module Under Test: Test all the button and links contains in payment recommendation
page
Explanation on difference between actual and expected output:
There is no difference between the actual and expected output. The function on the
system work as expected.
Suggestions for next steps:
No suggestion.
97
UMMC IT DEPARTMENT
TEST CASE DESCRIPTION
Test Case Number: 8
Date:10/11/2013
Test Case Description: Test all the button and links contains in invoice reviews page
Program Name: Invoice Tracking System
Test Case Prepared By: Nor Zainan Ashraf Bin Manan
Test Administrator: Yamin Bin Ahmad
Description of Test Data:
All links and buttons are click and executes.
Expected Result:
All links and buttons are functional.
Actual Result:
The links and button runs smoothly and correctly, user browses the selected page and
also does not feel lost in navigation.
98
UMMC IT DEPARTMENT
TEST CASE RESULTS
Test Case Number:8
Date:10/11/2013
Program Name: Invoice Tracking System
Module Under Test: Test all the button and links contains in invoice reviews page
Explanation on difference between actual and expected output:
There is no difference between the actual and expected output. The function on the
system work as expected.
Suggestions for next steps:
No suggestion.
99
UMMC IT DEPARTMENT
TEST CASE DESCRIPTION
Test Case Number: 9
Date:10/11/2013
Test Case Description: Test all the button and links contains in invoice approval page
Program Name: Invoice Tracking System
Test Case Prepared By: Nor Zainan Ashraf Bin Manan
Test Administrator: Yamin Bin Ahmad
Description of Test Data:
All links and buttons are click and executes.
Expected Result:
All links and buttons are functional.
Actual Result:
The links and button runs smoothly and correctly, user browses the selected page and
also does not feel lost in navigation.
100
UMMC IT DEPARTMENT
TEST CASE RESULTS
Test Case Number:9
Date:10/11/2013
Program Name: Invoice Tracking System
Module Under Test: Test all the button and links contains in invoice approval page
Explanation on difference between actual and expected output:
There is no difference between the actual and expected output. The function on the
system work as expected.
Suggestions for next steps:
No suggestion.
101
UMMC IT DEPARTMENT
TEST CASE DESCRIPTION
Test Case Number: 10
Date:10/11/2013
Test Case Description: Test all the button and links contains in activities log page
Program Name: Invoice Tracking System
Test Case Prepared By: Nor Zainan Ashraf Bin Manan
Test Administrator: Yamin Bin Ahmad
Description of Test Data:
All links and buttons are click and executes.
Expected Result:
All links and buttons are functional.
Actual Result:
The links and button runs smoothly and correctly, user browses the selected page and
also does not feel lost in navigation.
102
UMMC IT DEPARTMENT
TEST CASE RESULTS
Test Case Number:10
Date:10/11/2013
Program Name: Invoice Tracking System
Module Under Test: Test all the button and links contains in activities log page
Explanation on difference between actual and expected output:
There is no difference between the actual and expected output. The function on the
system work as expected.
Suggestions for next steps:
No suggestion.
103
UMMC IT DEPARTMENT
TEST CASE DESCRIPTION
Test Case Number: 10
Date:10/11/2013
Test Case Description: Test all the button and links contains in report page
Program Name: Invoice Tracking System
Test Case Prepared By: Nor Zainan Ashraf Bin Manan
Test Administrator: Yamin Bin Ahmad
Description of Test Data:
All links and buttons are click and executes.
Expected Result:
All links and buttons are functional.
Actual Result:
The links and button runs smoothly and correctly, user browses the selected page and
also does not feel lost in navigation.
104
UMMC IT DEPARTMENT
TEST CASE RESULTS
Test Case Number:10
Date:10/11/2013
Program Name: Invoice Tracking System
Module Under Test: Test all the button and links contains in report page
Explanation on difference between actual and expected output:
There is no difference between the actual and expected output. The function on the
system work as expected.
Suggestions for next steps:
No suggestion.
105
User Acceptance Testing (UAT) is the last phase of the software testing
process. During UAT, actual software users test the software to make
sure it can handle required tasks in real world scenarios, according to
specifications.
UAT is one of the final and critical software project procedures
that must occur before newly developed software is rolled out to the
market.UAT is also known as beta testing, application testing or end user
testing.
UAT directly involves the intended users of the software. UAT
can be implemented by making software available for a free beta trial on
the Internet or through an in-house testing team comprised of actual
software users.
Following are the steps involved in in-house UAT:
Designing test cases: Test cases are designed to cover all the
functional scenarios of the software in real-world usage. They are
designed in a simple language and manner to make the test
process easier for the testers.
relevant comments.
Bug fixing: Responding to the bugs found by the testing team,
the software development team makes final adjustments to the
code to make the software bug-free.
106
Sign-off: When all bugs have been fixed, the testing team
indicates acceptance of the software application. This shows that
the application meets user requirements and is ready to be rolled
out in the market.
DATE:
1-BAD
1. Usability
Easy
User manual
107
All buttons
meaningful
and
icons
2. Reliability
Web Information run as
required
3. Security
Data information are
secured by authorization
4. Suggested Hardware
Specification
5. Suggested Software
Specification
Signed on behalf of the IT department
Name:
Signature:
Signature:
4.8Evaluation
Evaluation is systematic determination of merit, worth, and significance of
something or someone using criteria against a set of standards. Evaluation
often is used to characterize and appraise subjects of interest in a wide range
of human enterprises, including the arts, criminal justice, foundations and
non-profit organizations, government, health care, and other human services.
For this Invoice Tracking System project, the evaluation is done with the
form named evaluation form. This form will be full filled by the user that
using this system for the first time. This evaluation is usually will be
completed in site presentation session.
108
NO
2. How about the performance of the button and the linkage of the site?
EXCELLENT
GOOD
AVERAGE
POOR
3. Do the button and the linkage refer to the correct path or page?
YES
NO
NO
NO
NO
NO
8. Do you recognize the usage of the buttons easily according to the words?
YES
NO
User Satisfaction
9. Does this Site can fulfil your requirements?
YES
NO
110
10. Do you have any suggestion to improve this UMMC Invoice Tracking
System?
_________________________________________________________________
_________________________________________________________________
__________________________________________________
4.9Installation
The implementation involves installing approved applications into production
environments as this case, the website that has been maintained is re-installed
in client computer. Primary tasks include announcing the implementation
schedule, training end users, and installing the product. Additionally, UMMC
should input and verify data, configure and test system and security
parameters, and conduct post-implementation reviews. Management should
circulate implementation schedules to all affected parties and should notify
users of any implementation responsibilities.
111
remove some parts of original test case and check if the problem still exists.
When debugging the problem in GUI, the programmer will try to skip some
user interaction from the original problem description and check if remaining
actions are sufficient for bug to appear. To automate test case simplification,
delta debugging methods can be used.
There are many ASP debugging techniques that can save countless hours
when coding. An effective but basic debugging technique is to simply turn on
error reporting. Another slightly more advanced technique involves using
print statements, which can help pinpoint more elusive bugs by displaying
what is actually going onto the screen. Debugging technique for ASP can be
dividing into three main techniques which are using software to debug the
code, another technique is by error message which a basic debugging
techniques and using a print statement.
113
As for this system testing, the debugging techniques are using the error
message. Error messages are the first line of defence as a developer. The
developer doesnt want to be developing code in ASP on a server that is not
configured to display error messages. However, remind that when code is
debugged and ready to go live, make sure error reporting is turned off
because don't want user of system seeing error messages that may give them
enough knowledge to exploit a weakness and hack the system.
Error messages can also use as advantage because it display the exact line
of code that threw or generated an error. This makes debugging a matter of
looking at the line number shown on the browser by the generated error and
checking that line number in the code.
114
115
116
Since a backup system contains at least one copy of all data worth saving,
the data storage requirements are considerable. Organizing this storage space
and managing the backup process is a complicated undertaking. A data
repository model can be used to provide structure to the storage. In the
modern era of computing there are many different types of data storage
devices that are useful for making backups. There are also many different
ways in which these devices can be arranged to provide geographic
redundancy, data security, and portability.
because it takes up less time and space than a full backup and provides for
more efficient restoration than incremental backups. The backup are done
using a 250GB hard disk drive where weekly (incremental backup) backup is
done and full backup done by burn into optical storage media such as
CD/DVD.
118
CHAPTER 5
CONCLUSION
5.0Introduction
With proper planning and analysis that have been done for this project, the
UMMC Invoice Tracking System was completed successfully.
A complete invoice tracking system hasbeenbuild to cover all the
problems that UMMC finance department have. With this system almost 90
percent of the problem has been solved.
Thus with this system successfully completed, there are still few
limitation that this system have, therefore this system still need to improved so
that those limitation can be solved on the next version of the system.
Now the UMMC have used the system to store and tracking all the invoices.
One week was allocated for pilot test to conduct project review by the system
owner which is head of department of UMMC finance department.
Based on the review and feedback from head of department of UMMC
finance department, there are still need few enhancement on the system need to
be add. Thus, from the feedback the system will still go on sign off. All the
manual filling not used anymore and unknown tracking of invoice processes
now can be track.
5.3Future enhancement
For the future enhancement on the system all limitation that this system have
must be solve. On the next version of this system the integration with the century
system must have. With this integration feature it easier for finance department to
make payment processes for the invoice and the payment can be making during
14 days of working.
The Data Centre Unit of UMMC IT Department have ordered new server
to replace the current database server. This is to ensure a stable connectivity
between file server and database server.
Furthermore on future enhancement there are other features that the head
of department request. All the features will be handling on the next version of the
system.
REFERENCES
121
122