Design of System Components and User Interfaces

1
Name
University
Course
Instructor

2
Table of Contents
Design of the system components....................................................................................... 3
Design of the user interfaces............................................................................................. 4
Storyboard 1.............................................................................................................. 4
Story board 2............................................................................................................. 7
Best-practice user interface design concepts...................................................................10
Security concerns and the approaches to mitigating them.....................................................10
SQL injections and cross-scripting attacks.....................................................................11
Worm and virus attacks............................................................................................. 11
Confidentiality attacks on files sent over a network..........................................................12
Authentication and authorization attacks.......................................................................12
Deployment of the solution............................................................................................. 12
Converting and initializing data...................................................................................12
Training users.......................................................................................................... 13
Configuration of the product environment.....................................................................13
Packaging, installation, and deployment of the components...............................................13
Change and version control......................................................................................... 14
References.................................................................................................................. 15

3
Design of the system components
Australian post Enterprise Resource Planning information system operates within a networked
environment. The system is composed of servers, databases, routers, and the internet. A customer
can access his or her account via the internet by entering his or her valid login credentials. If he
or she is not a member he or she can register for an account using a mobile phone, a laptop, a
desktop or a tablet as long as there is internet connection. Through their created accounts
customers are allowed to access their personal information, modify, add, or delete them. They
are also able to send letters within Australia and oversees, receive letters, calculate the postage,
and delivery times, track an item he or she sent or is receiving, book an appointment, and shop
online through the Australian post website. The Employees of Australian post on the other hand,
access the system through their work stations by authenticating their log in credentials. These
employees communicate to each other through the local area network in the Australian post
offices. The employees’ accounts are assigned more privileges as compared to the customers.
They can be able to view all the information on every customer of the Australian post. They are
allowed to add more customers by assigning them usernames and passwords, and delete or
terminate these customers from the system. These privileges assigned to the employees come
with the responsibility of ensuring the security of the customers’ information. As per the
Australian post regulation, the employees are not supposed to disclose information on any
customer to another company or any other person. All the information on the customers are
stored in the web servers where they can be accessed from anywhere at any time as long as there
is internet connection. Employee information is stored on the databases at the Australian post.

4
Design of the user interfaces
Storyboard 1
The following story board show the manage customer details use case. The employee or the
administrator has to login to the system first. After successful authentication the system displays
the administration homepage where the administrator chooses the manage users button from the
navigation bar in the homepage. When the administrator chooses the manage users button a
screen where a user can add and delete customer details is displayed.