Overall system architecture
The paper shows an insight into the Cumberland Farm’s system design. An open architecture built to make it simple to smoothly join, upgrade, and/or switch modules used on the Cumberland Farm system. The platform also guarantees optimization, accessibility (possibilities to ensure that users have access to both systems and data), and safety (protection of both data and systems against threats or unauthorized users).
Cumberland Farm’s goals are to:
• Improve accurate and workable information accessibility without compromising security
• Enable increased trust through defined data management of the inventory
• Allow people to improve the quality of Cumberland Farm’s Platform data analysis, reports, feedback, and decisions based on inventory information on the database
• Effortlessly absorb, incorporate, and maintain comprehensive information and surveillance data from the inventory database.
• Automatic processes to retrieve, clean, validate, transform and compile knowledge from a range of sources based on predetermined analyst rules and controls in multiple formats
• Store documentation and link known entities and fields to source information
• To provide scalable and data storage, while processing, and analyzing infrastructures and to update data continuously from the source data.
Scope and purpose of the document
This document describes the technical design of the Cumberland Farm’s network web portal. This document primarily aims to establish a technological vision for fulfilling business requirements. This paper provides an architectural overview of the system to illustrate various aspects. This paper is also the base of developers’ reference.
This paper targets system designers but not limited to:
· Development group
· IT staff
· Personnel Support
It bases the design method used here on Data Flow Architecture. The Cumberland Farm system’s data flow is internet-based. This will be used to extract MYSQL data and cache it to the web portal user interface. It will also allow the data modification where necessary.
This platform is developed by factoring application classes into the current layer as an object-oriented system for an Internet-based architecture using four-layer architecture:
The Layer of Presentation
This is the layer on which objects with physical windows, and apps. It also includes controller classes. Any new apps of the user interface developed for this implementation is put into this layer.
The Domain Model
Most of the objects recognized will live in the analysis and the design. The objects in this layer can be app-independent, to a large extent. Common objects may reap the benefits of Object-Oriented programming in this application.
The Hibernate layer
We have identified the database model using Hibernate. This maps domain classes into a greater range of legacy systems and makes the database more adaptable.
The Data layer- MySQL meant for management of the data
To organize the website Cumberland Farm: User Site Folders: Root Directory—all web pages relate to user features, it uses them up on the internet directories. Directory Pictures–Contains system images.
Reports: includes local reporting for exporting to CSV format. Reports.
General Search Search
The overall search involved the retrieval of documents from the database using the search criteria is done by the user. Unless, further data collections are required such as including on-screen data included during the search.
The layered structure of Cumberland Farm’s inventory and departments is managed by this module. Change the Cumberland Farm structure relationship. The module will add, delete, and change user permission for this module. There are four different levels of user permission: level 1- general users, who can request and see their applications only; levels 2-department administrators able in their departments to manage applications; levels 2-departmental administrators, who can view audit logs and search assets in their department; levels 3- faculties, who can manage applications; Level 4- IT stuff, inventory items and administrators from Cumberland Farm who can handle requests, view audit logs and scan assets throughout the organization.
It is a collection of functions that limit access here between protected internet connection or other network sets. Cumberland Farm uses IP packets based on source and destination IP, and source and destination port for packet filters. The rules of packet filtering studied sequentially, and placed careful attention and given to input rules.
Human interface design
Cumberland Farm shows details based on service areas in a hierarchy. The hierarchy aims to allow an administrator to easily access the display, and to take necessary measures. The content of the display at each level defined by the function of the operator. The overview display, for example, is the number of items in the stock and the abstracts level. It would only include the operator’s information needed to determine if the product is right within a few seconds.
The entire structure of information needed is more often outside the server room and on devices other than an administrator workstation, to meet changing user expectations. The interface responds to the needs of employees who are used to accessing inventory information almost anywhere on desktops, laptops, and mobile devices.
Jacinto, H., Kéchichian, R., Desvignes, M., Prost, R., & Valette, S. (2012, August). A web interface for 3D visualization and interactive segmentation of medical images. In Proceedings of the 17th International Conference on 3D Web Technology (pp. 51-58).
Ali, K., Zulkernine, M., & Hassanein, H. (2007, October). Packet filtering based on source router marking and hop-count. In 32nd IEEE Conference on Local Computer Networks (LCN 2007) (pp. 1061-1068). IEEE.