SATA TECHNOLOGY AND BUSINESS COLLEGE

HARDWARE AND NETWORK SERVICING LEVEL-IV

Developing System Infrastructure Design Plan

Learning objectives:

At the end of this session, you will able to:

 Define the principles, functions and framework of System
 Organize business requirement functions
 Identify operational environment of hardware, software and Network
 Refining system topology model, templates and standards
 Utilizing project architecture development

By TW
 Chapter One:
Plan and design internet infrastructure

1.1 Identifying critical principles, functions and framework of System

 Definition of System
 The term system is derived from the Greek word systema, which means an organized
relationship among functioning units or components. A system exists because it is
designed to achieve one or more objectives.
 It is a group of interrelated components working together towards a common goal, by
accepting inputs and producing outputs in an organized transformation process.
 It is an organized collection of parts (or subsystems) that are highly integrated to
accomplish an overall goal.
 Types of systems :
 Systems have been classified in different ways. Common classifications are:
1. Physical or abstract,
2. Open or closed
Physical or abstract systems :
• Physical systems are tangible entities that may be static or dynamic in operation.
• They can be seen and counted; they are static.
• In contrast, abstract systems are conceptual or non-physical entities.
Open or Closed Systems :
• An open system has many interfaces with its environment.
• It permits interaction across its boundary; it receives inputs from and delivers outputs to
the outside.
• In contrast, a closed system is isolated from environmental influences.
  Systems Models
What is model?
 Model is a representation of a real or a planned system.
 It’s objective is to point out the significant elements and the key interrelationships of a
complex system.
 A system topology model is a graphical representation of the components and
connections that make up a system.
 It is used to illustrate the structure of a system and how its components interact with
each other.
 In the context of a system infrastructure design plan, a topology model can be used to
show the physical and logical layout of the system’s hardware, network, and software
components.
 Characteristics of a System
Some characteristics those are present in all systems:
Organization
o Organization implies structure and order.
o It is the arrangement of components that helps to achieve objectives.
o In the design of a business system, for example, the hierarchical relationships starting
with the president on top and leading downward to the blue collar workers represents
the organization structure.
Interaction
o It refers to the manner in which each component functions with other components of
the system.
o In a computer system, the central processing unit must interact with the input device to
solve a problem.
Interdependence
o It means that parts of the organization or system depend on one another.
 o They are coordinated and linked together according to a plan.
o It also means that the output of one subsystem is the required input for another
subsystem.

Integration
o It refers to the holism of systems.
o It is concerned with how a system is tied together.
o It means that parts of the system work together within the system even though each
part performs a unique function.
Central objective
o The important point is that users must know the central objective of a computer
application early in the analysis for a successful design and conversion.
 Elements of a System
The environment may be a business firm, a business application, or a computer system. To
reconstruct a system, the following key elements must be considered:
 Outputs and inputs.
 Processor(s).
 Control.
 Feedback.
 Environment.
 Boundaries and interface

Input Process Output

Fig 1.1 General Model of system

1.2 Organizing business requirement functions

Requirement
 Requirements are the foundation of an IT project. Failure to understand the
requirements in the beginning results in an incorrect system and probably delays in
delivery.
 Requirements play a vital role in the systems development and maintenance processes.
System requirements consist of hardware requirements, software requirements, and
operational requirements.
 The IT project manager establishes a process to identify, define, elicit, and understand
system requirements.
 The purpose is to establish a common understanding between the customers, users,
stakeholders, and project manager of the requirements that will be completely
addressed in the systems development.
 The primary function of defining requirements is to draw blueprints and document them
to eliminate potential confusion and misinterpretation.
 Thus the requirement definition document that the customer produces will ensure that
the system developers understand the customers’ requirements, needs, and objectives.
 A requirement is simply a statement of what the system must do or what characteristic
it must have.
Types of Requirement

 User requirements

 Statements in natural language plus diagrams of the services that the systems
provide and its operational constraints.
 Written for customers
 Should describe functional and non-functional requirements
Functional requirements
 It relates directly to process a system has to perform or information it needs to
contain.
  Describe functionality or system services
 Depend on the type of software, expected users and the type of system where the
software is used.
Non-functional requirement

 It refers to behavioral properties that the system must have, such as performance
and usability.
 The ability to access the system using a Web browser is considered a non-functional
requirement.
 It can influence the rest of analysis (functional, structural, and behavioral models)
but often do so only indirectly.
 System requirements
 A structured document setting out detailed descriptions of the system services.
 Written as a contract between client and contractor
System Requirement Identification

 Is important to help the customer and developers define and understand what will be
involved in the system.

 The customer creates requirements for a specific purpose.

 Requirements can be totally new for an IT systems development project, or

requirements can be for improving an existing IT system.

 The customer and developers must understand the requirements before making a
costly decision of what to build.

 This process involves determining, defining, and specifying requirements before

analyzing them.

Requirement Determination

 Requirement determination is a process that determines what is desired.

  Determining what is desired involves sub processes, such as the customer defining the
requirements and the system developer learning those requirements.

 The customer must state requirements clearly, rigorously, and precisely before
proceeding to other system development phases.
Importance of a Good Requirement
 A good requirement is an agreement among the customers, users, stakeholders, and
system developers.
The Requirements Document
 Official statement of what is required of the system developers
 Should include both a definition and a specification of requirements
 Should:
 specify external system behavior
 specify implementation constraints
 be easy to change (but changes must be managed)
 serve as a reference tool for maintenance
 It is not a design document
 it should state what the system should do rather than how it should do it

1.3 Identifying operational environment support

Overview of operating environment
 The operating environment for home control is in several aspects much less demanding
than, for example, the environments in which industrial controls are deployed.
 This is, for example, true for operating temperature ranges, dust and dirt, chemicals in
the environment, electromagnetic interferers, or vibration.
Hardware
 Hardware infrastructure refers to the physical components and devices that form the
foundation of an information technology (IT) system.
 These components work together to support the processing, storage, and
communication of data within an organization or a network.
  Key elements of hardware infrastructure include:
 Servers: Powerful computers designed to process requests and serve applications or
resources to other computers on the network. Servers can include web servers,
database servers, file servers, and more.
 Storage Systems: Devices or systems that store and manage data. This includes hard
disk drives (HDDs), solid-state drives (SSDs) and more.
 Networking Equipment: Devices that facilitate communication and data transfer
within a network. This includes routers, switches, hubs, modems, and access points.
 Power Infrastructure: Systems that provide electrical power to IT equipment. This
includes uninterruptible power supplies (UPS) to protect against power outages.
 Client Devices: Devices used by end-users to access and interact with the IT system.
This includes desktop computers, laptops, tablets, and smartphones.
Network Infrastructure
 Refers to the hardware and software resources that enable the connectivity,
communication, and management of computer networks.
 It is the foundation on which network services, applications, and data are transmitted
and accessed within an organization or between different entities.
 Key components of network infrastructure include:
 Hardware: Routers, switches, firewalls, servers, cabling, and connectivity components.
 Network Services: DNS (Domain Name System), DHCP (Dynamic Host Configuration
Protocol), LAN and WAN services.
 Security Measures: Firewalls, Intrusion Detection and Prevention Systems (IDPS).
 Internet Connectivity: Gateways.
 Network infrastructure, which is the foundation of network services, applications, and
data transmission.

Software

 Software infrastructure, also known as software architecture or application infrastructure

refers to the collection of software components, frameworks, tools, and services that
 support the development, deployment, operation, and maintenance of software
applications.
 It provides the foundation for building and running software systems efficiently and reliably.
 Operating Systems: An operating system is fundamental software that manages hardware
resources and provides essential services for other software applications.
 Database Systems: Database management systems (DBMS) store, organize, and manage
data. Common types include MySQL, PostgreSQL, Oracle, and Microsoft SQL Server.
 Development Tools: Integrated Development Environments (IDEs), code editors, compilers,
and debugging tools facilitate the creation of software applications.
 Programming Languages: Various programming languages (e.g., Java, Python, C++, and
JavaScript) are used to write code and develop applications.
System topology model
 System topology in computer networks refers to the physical or logical layout of
network devices and the interconnection between them.
 The physical topology refers to the actual layout of the devices and cables, while the
logical topology refers to how data flows in the network.
 Logical topologies include point-to-point, point-to-multipoint, client-server, and peer-to-
peer topologies.
 Each topology has its own strengths and weaknesses.
 For example, a bus topology is simple and inexpensive, but it can be slow and
unreliable. A mesh topology is highly reliable, but it can be complex to manage.
1.5. Project architecture development
Identifying project gaps
 Gap analysis is a formal study of how a business or project is currently progressing and
where it plans to go in the future.
Some common types of architecture requirements:
 Functional Requirements: Descriptions of the system’s functions and capabilities.
Define input and output expectations.
  Non-Functional Requirements: Performance, reliability, security, scalability,
usability.
 Technical Requirements: Hardware specifications, software specifications, network
requirements.
 Architectural Patterns: Specify the architectural style to be followed (e.g., client-
server, micro services, monolithic).
 Data Management Requirements: Database requirements, data integrity and
consistency requirements.

Chapter Two
Specify hardware and software

2.1. Architecture Requirements

 Architecture has emerged as a crucial part of the design process.

 Software architecture is developed as the first step toward designing a system that has a
collection of desired properties.
Good Architecture Rules
 Use information hiding to hide computing infrastructure
 Use well-known architecture tactics to achieve quality attributes
 Minimize and isolate dependence on a particular version of a commercial product or
tool.
2.2. Requirement Capacity against Client Requirements
 Understanding client requirements:
 This involves analyzing the specific needs and expectations of your clients, such as
quality, cost, time, scope, etc.
  You should communicate with your clients regularly to understand their goals,
preferences, and feedback.
 You can use tools such as surveys, interviews, focus groups, or questionnaires to
gather client information.
 Documenting internal capabilities:
 This involves assessing your organization’s resources, such as human capital,
technology, infrastructure, processes, etc.
 You should identify the strengths and weaknesses of your organization, as well as
the opportunities and threats in the external environment.
 Conducting a gap analysis:
 This involves comparing your current state with your desired state, and identifying
the gaps or discrepancies between them.
 You should measure the performance of your organization against the client
requirements, and determine the root causes of the gaps.
 You can use tools such as fishbone diagram, Pareto chart, or root cause analysis to
conduct a gap analysis.

2.3. System and application requirement

System requirements
 These are the specifications and criteria that define the design and functionality
of a system, such as a computer, a network, or a device.
 System requirements describe the conditions necessary for the product to run,
such as hardware, software, network, and performance expectations.
 System requirements often indicate the minimum and the recommended
configuration for optimal product functionality.
Application requirements
 These are the specifications and criteria that define the design and functionality
of a software application, such as a web app, a mobile app, or a desktop app.
 Application requirements describe the features and capabilities of the product,
such as user interface, user experience, data management, security, compliance,
and scenarios.
  Application requirements help guide the development and ensure that the final
product meets the desired objectives and user needs.
Relationship between system and application requirements
 System and application requirements are interrelated and interdependent.
Application software needs system software to operate effectively.
 These programs require the support and functions of the system software to install
them selves onto the hardware.
 System software also provides services and resources for application software to
run smoothly and efficiently.
Importance of system and application requirements:
 System and application requirements are crucial for the success of any software
project.
 They provide a clear and detailed description of what the software will do and
how it will be expected to perform.
 They also serve as a communication point between all the stakeholders involved
in the software development process, such as developers, testers, customers, and
users.