7.3.3 (INFRASTRUCTURE DEVELOPMENT/ACQUISITION PRACTICES (The physical…
The physical architecture analysis
Project Phases of Physical Architecture Analysis
Review of Existing Architecture (1st workshop)
Operational constraints of physical requirement
• Ground issues
• Size limits
• Weight limits
• Current power supply
• Environmental operating limitations (temperature and humidity minimum
• Physical security issues
Analysis and Design
adhering to good practices and
meeting business requirements
Draft Functional Requirements
is the input for the next step and the vendor selection process.
Vendor and Product Selection
parallel witj drafting of functional requirement
Writing Functional Requirements (2nd workshop)
functional requirements document is written and will be introduced
results will be discussed and a list of the requirements that need
to be refined or added will be composed.
Proof of Concept
to prove that the selected hardware, software and data are able to meet all expectations, including security requirements.
deliverable of the POC should be a running prototype, including the associated document and test protocols describing the tests and their results.
POC should be based on the results of the procurement phase described below in this section
prototype should demonstrate the following features
• Basic but
functional implementation of security measures as defined
• Secured transactions
Characterization in terms of installation constraints
and limits (server size, server current consumption, server weight, server room physical security)
• Resiliency to include basic fail-over to a trusted operational state
• Funding and costing model
• Data and algorithm
• The basic setup of the
core security infrastructure
Related implementation projects that prepare for deployment should also be part of the POC
For example, if the enterprise operates in a highly regulated industry or an industry that demands high levels of availability, adequate redundancy and safeguards for ensuring data privacy and confidentiality may have to be factored in while testing the POC.
Planning Implementation of Infrastructure
requirements analysis is not part of this process
but constantly feeds results into the process.
the procurement process begins
the service-level management process.
communication between the business and the analysis project is established
and determine the quantity structure of the deliverables
to provide an overview of the chosen solution
the preferred partners are invited to the negotiations process and the deliverables, contracts and SLAs are signed
delivery plan should include topics such as
goals and nongoals
key facts, principles, communication strategies
and progress on key tasks and responsibilities.
Installation Test Plan
The test plan includes
basic requirements’ specifications
definition of the processes, and
measurement information for the applications and the infrastructure.
impact is not only economic but also technological because it decides many other choices downstream, such as
and TCO (total cost of ownership)
Information and communication technologies (ICT) departments are often tasked with making these decisions.
Solutions must accomplish the following
• Ensure alignment of the ICT with corporate standards.
• Provide appropriate levels of security.
• Integrate with current IT systems.
• Consider IT industry trends.
• Provide future operational flexibility to support business processes.
• Allow for projected growth in infrastructure without major upgrades.
• Include technical architecture considerations for information security, secure storage, etc.
• Ensure cost-effective, day-to-day operational support.
• Foster the usage of standardized hardware and software.
• Maximize ROI, cost transparency and operational efficiency.
The physical architecture analysis, the definition of a new one and the necessary road map to move from one to the other are critical tasks for an IT department