Software Engineering Project: Dry Cleaner Management System

Desklib provides solved assignments and past papers to help students succeed.

Table of Contents
UML Diagram............................................................................................................................2
Test Cases...................................................................................................................................3
Problems.....................................................................................................................................7
References..................................................................................................................................8
List of Figures
Figure 1: UML Diagram............................................................................................................2
Figure 2: Test Case 1..................................................................................................................4
Figure 3: Test Case 2..................................................................................................................4
Figure 4: Test Case 3..................................................................................................................5
Figure 5: Test Case 4..................................................................................................................5
Figure 6: Test Case 5..................................................................................................................6
Figure 7: Test Case 6..................................................................................................................6

UML Diagram
Figure 1: UML Diagram
The above made UML Diagram explain the scenario of the entire program is made. Two of
the classes are explained here named as Order and RockyDryCleanerGUI(Torre et al., 2018).
Many of the functions are mentioned in the both the classes like in the Order class

setCustomerName, setGarments, getCustomerName, getGarments and calculateCharges
whereas in the next class that is named as RockyDryCleanerGUI also contains the functions
or the methods named as enter, displayHeading, displayOrder, appendLine, displayAll,
search, exit and showDialog. A multiplicity is also shown in the diagram that is 0..* from
Order to RockyDryCleanerGUI.
Test Cases
Test Case Expected Result Actual Result Status
Null Value test. Not Entering the
entire data would
provide the result.
Error occurred. Fail
Data not found. The appropriate
result would not be
found.
Required data
doesn’t exist.
Pass
Garment Value
condition check
The required result
would be received.
An error occurred
showing the message
that Garment value
must be greater than
zero.
Fail
Final Message The final thankyou
would pop out.
The thank you
window is popped
up.
Pass
Null Value test. Not Entering the
entire data would
provide the result.
The error is received
that the orders are not
entered.
Pass
Searching The data that has to
be searched must be
entered.
The message is
popped up.
Pass
Screenshots

Figure 2: Test Case 1
Figure 3: Test Case 2

Figure 4: Test Case 3
Figure 5: Test Case 4

Figure 6: Test Case 5
Figure 7: Test Case 6
The entire project was built within five days (Laakso et al., 2016). The project took much
time in the starting while designing the interfaces and preparing the entire code but on the
later stage, the work went smoothly and completed within 5 days.

Problems
Some of the problems were also encountered while preparing this project was:
 During the development of the interface, some of the difficulties were faced as it took a
long time and for designing work proper implementation was also required. Therefore,
the design has to be correct to make the project a bit catchy and efficient as well.
 While working with the defined classes named as the Order and RockyDryCleanerGUI,
the interaction between both the classes has to be properly shown and that too was found
a bit difficult in the starting but on the later stage, the work went smoothly and both the
classes properly interacted according to the code.
 Also, one more issue occurred in designing the UML diagram for the created code as
what functions are to be shown and how the classes must be represented in the diagram
was to be properly shown in the diagram.
 One another issue that was faced in the implementation of this project was of showing the
various test cases and proper results of the test cases and few of the test cases were failed
as well.

References
 Laakso, K.P., Husu, T., Romppainen, M., Fagerlund, J., Kettunen, M. and Standell,
T., 2016, May. User Interface Design In Agile Projects. In Proceedings of the 2016
CHI Conference Extended Abstracts on Human Factors in Computing Systems (pp.
1007-1010). ACM.
 Torre, D., Labiche, Y., Genero, M., Baldassarre, M.T. and Elaasar, M., 2018, May.
UML diagram synthesis techniques: a systematic mapping study. In 2018 IEEE/ACM
10th International Workshop on Modelling in Software Engineering (MiSE) (pp. 33-
40). IEEE.