Professional Documents
Culture Documents
TESTING
Software testing is an investigation conducted to provide information about the
quality of service under test of system.
Test Scenario:
Log in
Input/Action/
Condition:
Fill-out the Username and Password fields, and then click the Log-in
button. If the username and password are correct, Homepage will be
displayed. And, if the username and password didnt match, a message
dialog box will appear Invalid combination of username and
Remarks:
password.
No errors found
Date Tested:
No.:
Test Scenario:
Database Setting
Input/Action/
Condition:
The user needs to fill up the text box with the correct Username and
Password. If the user input incorrect data for three attempts, message
box will appear failed to connect to the database.
Remarks:
Errors found
Date Tested:
Page 1
No.:
Test Scenario:
Input/Action/
Condition:
Get the overall reports from other departments. The IIO can view the
given reports and analyze it. If the reports are not available then the
IIO have nothing to view and analyze and need to wait for the reports
from the other departments.
Remarks:
Errors found
Date Tested:
No.:
Test Scenario:
Table Name
Input/Action/C
ondition:
Table name must have a unique ID and Password. If the table name
has a same ID and Password from other department it is hard to
identify what kind of table is that.
Remarks:
Errors Found
Date Tested:
Page 2
INTEGRATED SYSTEM
No.:
Test Scenario:
Log in
Input/Action/C
ondition:
The log in of Standalone system is the same with the log in, in
integrated system. The Username and Password fields and then click
the Log-in button. If the username and password are correct,
Homepage will be displayed. And, if the username and password
didnt match, a message dialog box will appear Invalid combination
of username and password.
Remarks:
No errors found
Date Tested:
No.:
Test Scenario:
Input/Action/
Condition:
Remarks:
Errors Found
Date Tested:
Page 3
No.:
Test Scenario:
Executive Officer
Input/Action/C
ondition:
Remarks:
Errors Found
Date Tested:
No.:
Test Scenario:
One Database
Input/Action/C
ondition:
Remarks:
Date Tested:
Errors Found
August 15, 2014
CHAPTER-5 EVALUATION
5.1 Findings
Inventory Deployment System
Page 4
Base in the observation we are doing in chapter 4 which is the testing part,
were found that the system is not currently fully done, or functioning nicely that
the number one reason why the group decided to focus on main system which
encountered so much problems and errors. And in that way the decision that
already made to solve those errors through doing the best to create a unique and
user friendly interface even the old times people can use it. Sometimes the system
is not totally perfect and have an errors encountered, the results of testing is failed
to connect to the system and to another system especially in integrated system.
And if the top five issues of every department did not match in other department,
the inventory deployment system has a conflict to do the integrated database. The
inventory deployment has no back end but currently have a tendency that the
main back end of the system is the reports of every department given. And
whatever the reports they had received that are the main reports will be manages
and put it, in the dashboard.
5.2 Analysis
The Inventory Deployment System has a goal to reach the client needs
through checking a system step by step to minimize the errors of every
department connected to the system. If all of the departments did not give their
integrated reports, may dont have a report to represents through dashboard
because the main system is connected to other departments by viewing their
reports in real time. The Inventory Deployment is often analyzed during
processing to ensure that the process is operating in an efficient manner. Thus if a
problem develops during processing it can be quickly detected and the process
adjusted so that the other departments has always given the reports and not
adversely affected. Techniques used to monitor process control must be capable of
producing precise results in a short time. Customer Relationship Management can
either use analytical techniques that measure the order processing of foods online. And the Logistics warehouse is the one who managing the ordering process,
managing the supplies of raw materials and their stocks, and the bad orders given
to them.
Inventory Deployment System
Page 5
5.4 Recommendations
The suggestions of my groups are to improve and enjoy to do the system in
real-time, detailed by doing this system because you can manage and control the
time whatever kind of system you have like the Inventory Deployment System
by changing the errors or solve the problems automatically. And eliminate the
inefficiencies throughout the convenient online system and connected also to all
departments like purchasing system. Teach how to purchase order online that
track costs of every products, thats why were create a dashboard that shows the
overall issues of every departments and shows the recommends also to do it in
Page 6
advance, doing the assign task that given the instructor by working it together
with all groups, updating, communicating all times.
CHAPTER-6 CONCLUSIONS
6.1 Conclusions of the findings
Page 7
Inventory Deployment System has fully aimed and done the system by
testing the successes and failures of the system at different points of the lifecycle
of Inventory, which we solve the top five issue of every department by viewing
their reports in real time through dashboard. And updating always the integrated
groups to minimize the hassle and errors of every departments.
Ask some advice to the adviser given and think first the moves
before doing the assign task.
Page 8