BN314 System Architecture Assignment: Network Inventory Report

This report presents a detailed analysis of a Network Equipment Inventory Information System, designed for network engineers to efficiently access device information and configuration details. The system's architecture, encompassing a server, platform controller, and user interface application, is thoroughly examined. The report outlines the system's functional requirements, demonstrated through a use case diagram, and provides a comprehensive system architecture diagram. User interface design, based on principles of user-centered design, is highlighted with mock-ups. Furthermore, the report explores a cloud-based architecture for the system, elucidating its components and benefits. The report concludes by emphasizing professional work practices and providing relevant references. The report also includes system test plans to ensure the accuracy of the system's working. The report also includes a sequence diagram to explain the flow of the system. The cloud-based architecture explains how the system can be shifted to the cloud environment and the benefits of doing so.

Running head: SYSTEM ARCHITECTURE
SYSTEM ARCHITECTURE
Name of the Student:
Name of the University:
Author Note:

1
SYSTEM ARCHITECTURE
Executive Summary
The report is presented on the Network Equipment Inventory Information System which is used by network
engineers to quickly search a device’s information and configuration detail. The system uses a server, a
platform controller and a user interface based application to operate between the users and the main
server. The report also states the functional requirements of the system and demonstrates them by
showing a use case diagram of the same. The report also describes the system architecture of the system
with a diagram. The user interface design has been highlighted with the help of interface design mock-ups.
The report also illustrates the cloud architecture for the same system and explains it. The report ends with
the professional work practices that should be adopted and references.

2
SYSTEM ARCHITECTURE
Table of Contents
Introduction...........................................................................................................................................3
Architecture of the system....................................................................................................................3
Conceptual design of user interface......................................................................................................4
Sequence diagram.................................................................................................................................7
System Test plans..................................................................................................................................7
Cloud based architecture.......................................................................................................................8
Functional Solutions..............................................................................................................................8
System Processes and Work Practices.................................................................................................10
References...........................................................................................................................................11

3
SYSTEM ARCHITECTURE
Introduction
The Network Equipment Inventory Information System is mainly developed to keep the record of the
thousands of network devices around the world. This system provides easy access to the network device
database for the network engineers or operators. The system is maintained by a group of admins who are
tasked of updating the system database to keep it up to date. The Network Equipment Information
inventory system should be operable on a range of devices. A network engineer should be able to access
the system while working from his smartphone or computer.
Architecture of the system
Figure 1 System architecture diagram
The architecture of the system shows the data flow and major components of the system. The three main
components are the main inventory information system server, the web server for authentication purposes
and the web browser or application interface to access the system and view the data. The main server is
used for both storing, retrieval and collecting of the data. The data includes the network device information
on geometric locations as well as the updated configuration of each of these devices. The web server is
totally dedicated to create a secure link between the user and the main server and its primary function is to
authenticate the users for access. The web browsers or the system interface is the primary user interface
via which a user retrieves the information it needs.

4
SYSTEM ARCHITECTURE
Conceptual design of user interface
The user interface can be designed based on Don Norman’s Principles of user cantered design. The main
aspect of the design can be highlighted by focusing of six main points of interface design:
1. Visibility: The main aspects of the system should be more visible to the user. For example, the
search bar should be highlighted in the interface for easy searching of the network design.
2. Feedback: The feedback from the system to the user is an important part of knowing whether an
action has been performed or not. For example, when a user completes a search he should get a
response from the system to know whether his search is successful or not.
3. Affordance: The system should be easily understandable for even a layman. The simpler the
application design, more the affordance.
4. Mapping: It is the relation between the amount of control given to the user and the proportional
effect due to control on the system. For example, if a user searches for devices with names starting
with H, then he should only get devices starting with H.
5. Constraints: The constraints can be size limitation on different devices. The smaller device
interfaces are harder to design due to limited space.
6. Consistency: The application designed should have a consistent design over the years as it becomes
easier for the users to identify with the application later on by just seeing the interface design.

5
SYSTEM ARCHITECTURE
Figure 2 User interface login page

6
SYSTEM ARCHITECTURE
Figure 3 User interface search page
Sequence diagram

7
SYSTEM ARCHITECTURE
Figure 4 Sequence diagram
System Test plans
The network equipment inventory information system can many important functional requirements that
are needed to be tested for checking the accuracy of the system’s working. The main requirements
expected from the system are:
1. The system should be able to look up a specific device on the database. To check this feature the
tester must search for a specific tool or configuration from the user interface and check if the
correct results are provided. The tester should perform this test for multiple different devices with
different configuration to test the system accuracy.
2. The system should work on different devices with different operating systems. To check this aspect
the tester should be able to successfully install the system application on multiple different devices
with different operating system and run the application to see if it is running smoothly.
3. The system should be able to auto update itself or have a manual update option to keep the
records updated. The tester can check this feature by running the auto update feature from the
admin panel and check whether the device information have been updated or not. The tester can
also try to update a single network device manually to see if the system accepts the updated
information.
Cloud based architecture
The software, platform and infrastructure are the main elements needed to develop the system. The
software handles the user interface of the system and acts as the medium between the main server, the
database and the user. The web server which hosts the authentication and access functions act as the
platform for the system. The main information server which stores, collects and retrieves information for

8
SYSTEM ARCHITECTURE
the system acts as the infrastructure. The whole system can be shifted to the cloud environment by making
the system cloud accessible. The infrastructure like the mainframe controllers and the database servers can
be shifted to cloud using the IaaS or Infrastructure as a Service solution. The web server dedicated to the
authentication and communication purposes can be shifted to the cloud using the PaaS or Platform as a
Service solution. Finally the software system that is used by the user can be streamlined and made faster by
shifting it to the cloud using SaaS or Software as a Service. Thus shifting to the cloud will not only save
space and money but will also increase the performance of the system.
Functional Solutions
The user using the system should be able to access the login page of the system to use his credentials to
access the system. The system should revert to the user and grant him access if the login is successful or
send a message if it is unsuccessful. The user should be able to search for a specific device and use filters to
narrow down his search. The device should be able to retrieve and show both device information and
configuration details. The user should be able to logout from the system after the use. The admin should be
able to update and maintain the system and also view the users accessing the system.

9
SYSTEM ARCHITECTURE
Figure 5 Use case diagram
System Processes and Work Practices
The work practices are:

10
SYSTEM ARCHITECTURE
1. Design and document key processes.
2. Control and monitor the processes to make sure the service standard is of expected quality.
3. The administration must take action to correct the problems.
4. Use benchmarking data to compare the systems performance with other similar tools.

11
SYSTEM ARCHITECTURE
References
[1] Kenneth C. Laudon and Jane P. Laudon. Management information system. Pearson Education India,
2016.
[2] Stefano. Puliti et al. "Inventory of small forest areas using an unmanned aerial system." Remote
Sensing 7.8, pp.9632-9654. 2015.
[3] Haiyan. Guan et al. "Use of mobile LiDAR in road information inventory: A review." International Journal
of Image and Data Fusion 7.3, pp.219-242. 2016.
[4] Eirini. Spiliotopoulou et al. "Managing and reallocating inventory across two markets with local
information." European Journal of Operational Research 266.2, pp.531-542. 2018.
[5] Max. Muller Essentials of inventory management. HarperCollins Leadership, 2019.
[6] Manita. Timilsina et al. "Large-Scale Landslide Inventory Mapping in Lesser Himalaya of Nepal Using
Geographic Information System." GIS Landslide. Springer, Tokyo, Pp.97-112. 2017.
[7] Maike. Kuhnert et al. "Next generation, secure cloud-based Pan-European information system for
enhanced disaster awareness.” 2015.
[8] Lu. Hou et al. "Internet of things cloud: Architecture and implementation." IEEE Communications
Magazine 54.12, pp32-39.2016.
[9] John W. Rittinghouse and F. Ransome. James Cloud computing: implementation, management, and
security. CRC press, 2017.
[10] Edward. Tenner "The Design of Everyday Things by Donald Norman." Technology and Culture 56.3,
pp785-787.2015.