Order Management System UI Report

This report details the user interface of an order management system, outlining the process from user order placement to product shipment. It identifies security concerns such as hacking and internal vulnerabilities, as well as risks like inventory miscalculations and location verification failures. The report suggests security measures, including pilot testing and data encryption, to mitigate these issues. It also references relevant research on software engineering and mobile e-commerce security.

Week 4: User Interface
Given below is the order management feedback rating storyboard created for the system under
development:

The order management within the system will be managed in the manner depicted in the
storyboard above. The users will be opening the application to access the interface from where
they will place the order for their product. The order will be pinged to the administrator and it
will be automatically forwarded to the backend system where the products to be picked will be
identified. The system will match the order from the users and the availability of that product in
the inventory. In this case, two same orders have been considered coming from the two different
users. Even there will be different for the different users the system will complete the task in the
similar manner. The orders received from the users will be matched with the available inventory,
and location where they are need to be sent. The checkout requisition will be generated for both
the locations. After that, the system will automatically create the purchase order lines for the
products and will be combined with one po line as the order are for the same product and the
product will be shipped to the specified location. After the receipt of the order the users will be
auto-confirmed of the same and will be prompted to give feedback which will be collected for
future study and analysis.
There are some security concerns with this process that are mentioned below:
- The system can be hacked by some external parties for competitive interest or personal
interest.
- The failure of the staffs to effectively handle the internal security of the system and
allowing intervention of third party.
- Intervention of external software system that disrupts the mechanism of the system.
Apart from the security concerns, there are some risks that are to be taken into consideration
while moving ahead with the development:

- The failure of the system to assess whether there exist enough products in the warehouse
to fulfill the order.
- The failure of the system to display correct availability of the products to the users.
- The failure to verify the locations entered by the users.
The security concerns and the risks can be handled effectively by considering the security
measures before the occurrence of these fatal situations. Some of the security measures that can
be taken regarding this system are that the system must be kept on pilot test for at least two to
three months with fake user entry and assessment. A continuous report should be prepared to
assess the variations and then right system development should be development. Apart from that
the data entered by the users should be encrypted. The encryption should be able to protect the
data transfer during the movement and at the server where it is more vulnerable to threats as
external threats are knows where they can find enough data.
References
Wasserman, A. I. (2010, November). Software engineering issues for mobile application
development. In Proceedings of the FSE/SDP workshop on Future of software engineering
research (pp. 397-400). ACM.
Ghosh, A. K., & Swaminatha, T. M. (2001). Software security and privacy risks in mobile e-
commerce. Communications of the ACM, 44(2), 51-57.