Cybersecurity program
Running Head: SYSTEM DESIGN 1
SYSTEM DESIGN 2
Student Name
School NAME
Date
TABLE OF CONTENT
1.0 Introduction……………………………………………………………………………………3
2.0 Goals and Considerations…………………………………………………...………………...3
3.0 Overview of the system design document…………………...……………………………...3-4
4.0 How is data design associated with system design document?.................................................4
5.0 Describe the human-machine interface and operational scenarios………………………….4-5
6.0 System architecture design……………………………………………………………………5
7.0 Hardware security diagram………………………………………………………………….5-6
8.0 Security software design………………………………………………………………………6
9.0 Reference……………………………………………………………………………………...7
The system design document discusses the system design aspects, how the non-functional and functional requirements are recorded in the requirement document, and the preliminary data design documented in the local data. System design documents the high-level system design and the low-level detailed design specifications. An example of system design is the architectural design which is a concept that focuses on components of a structure (QIU & OMURA, 2016). This system consists of multiple volumes of individual design documents. This document is important because it helps individuals to understand what is possible, not possible, and the system that will be favorable for that scenario.
Goals and Considerations
The goal of this design is to track any required data to effectively define the system architecture and system design to ensure the development team has attained guidance on the architecture of the system to be developed (QIU & OMURA, 2016). Given that the system will integrate data from various sources and conduct a systematic correlation of real-time information, its architecture is based on enterprise application integration (EAI) The considerations of the system design document include a description of the purpose of the output such as identification of the primary users, report distribution requirements if any (include frequency for periodic reports) description of any access restrictions or security considerations. Other goals include ease of use. The system will be easy to use and provide a strong user experience.
Overview of the system design document
In this section, the system is described in a more narrative form using non-technical terms. The system design document is a concept that focuses on components of a structure. It’s guided by certain principles such as high coupling, good modularity, and low cohesion (QIU & OMURA, 2016). Design concepts such as architectural patterns, reference architectures, externally developed components, and tactics are the building blocks of the system architecture and they form the basis of the architectural design. This system has three layers. The first layer covers the software and the hardware needed to have a secure computer system. The second layer entails the logical techniques needed to keep the system secure and the third layer covers the evaluation techniques that quantify how the system is secured. System design documents are developed to ensure efforts of a large team are coordinated, to give them a stable reference point, and to expound all parts of the system software and how they will operate. The system design document ensures products are created to meet the needs and is per what was agreed upon before the inception of the software.
How is data design associated with system design document?
Data design can be described as the first design activity which leads to fewer complexes, modular, and efficient program structure. The system views how information security controls and safeguards are implemented in the IT system to protect the confidentiality, integrity, and availability of information. Data design is associated with system design documents in various ways.
Describe the human-machine interface and operational scenarios
A human-machine interface (HMI) is an interface used by organizations to connect a person to a machine, server, device, or system (Afrianto et al., 2019). It enables the operators to manage their industrial and process control machinery through a computer-based graphical user interface (GIU). The human-machine interface provides a visual presentation of the control system and provides real-time data acquisition. Operational scenarios are the description of an imagined Sequence of events that include the interaction of the services and products with its users and the environment as well as the interaction among its products or service components (Afrianto et al., 2019).
System Architecture Diagrams
Systems and subsystems architectures for the organization are expounded in this section.
External system design
Hardware security diagram
This part describes the system hardware and the organization. Under this section, hardware components and the connectivity between the components are presented in form of a diagram.
Security software design
Overall system software and the organization are explained in this section. It includes a list of software techniques, computer languages, and computer-aided software engineering tools.
References
Afrianto, I., Heryandi, A., Finadhita, A., & Atin, S. (2019). Design Of E-Document System with Digital Signature Using User-Centered Design Method. Conference SENATIK STT Adisutjipto Yogyakarta, 5.
Jang, S. (2017). Design of Access Control System for Hangul document System. Journal of Digital Information Management, 15(4), 170.
Qiu, Q., & Omura, K. (2016). Developing a Document Creating System for Affective Design: A Case Study in Card Design. International Journal of Affective Engineering, 15(2), 91-99.