Organizations’ utilization of IT infrastructure is fundamental in supporting various business operations and operational objectives. There is the need for organizations to install these infrastructures to support their objectives and facilitate the operations between organizations to enable it meet customers’ needs. However, this must be put into plan to for easy implementation.
These plans need to follow a structured approach of the system development life cycle, consisting of various phases of a system being implemented. The system development life cycle is the structured set of methods, which are used in developing and implementing information systems applications (Grenci, 2004). The various phases here include the functional requirements definition; systems design specification, development and implementation, testing and evaluation of controls, and deployment. In these stages, there are deliverables that need to be reached to enable the systems’ development process to be implemented fully.
Purpose of the Plan
The main goal of the implementation plan is to ensure that each phase is completed to ensure that the information systems between the merging firms are working, while the goal and objective of the plan is to ensure that the process adheres to standards of systems development. It also ensures that the whole process is well managed to prevent variances that may distract the project implementation process.
Overview of the network diagram and security solution for the intended project
This will ensure that the implementation of the information systems infrastructure between the two companies is guided by sets of standards, to facilitate the proper functioning of the computing infrastructures being put into place. By following the laid down structured process, the two infrastructures will be merged together to sustain the network, system and to ensure continued operations between the two firms. The structured approach will also ensure that security appliances designed are put into place to prevent network and system breaches.
Business goals and objectives
The objective is to protect the network from intrusions and attacks that compromise the effectiveness of the organization’s development. The organization will reduce the prevalence rates and attempts of gaining access to organizational through implementing the security plan within the IT infrastructure of the two companies.
Project Goals and Objectives
The project objective is to merge the two company’s information system infrastructures and to implement a secure and tamper-proof network to protect the company from attacks.
This statement is used to define what the project will accomplish (Kless, 2010). It gives the vision needed that guides the project until it is completed.
It will also help in steering the project management process to ensure that the IT project is completed according to the project management guidelines.
The plan will give the project management office an elaborate way of managing the team members to complete the project. The project management office is a unit dedicated in handling a variety of tasks related to an organizational management of projects (Muller, 2013).
Items beyond scope
Carrying out systems upgrades
Hardware and software fault detection
Project Plan Expenses
Unit Cost ($)
Printing services $1000
Logistics services $9000
Utilities i.e. telephone bills $2000
Total Expenses $25000
System development life cycle
Functional requirements definition
This phase defines the requirements for implementing the project systems development process. In this stage, the user requirements are defined in detail, with the main aim being to ensure that the system being defined in mind meets all technical requirements. This is through determining the nature of the outputs that will meet the needs of potential users.
System design specification
This stage includes all elements relating to the actual design, involves designing critical elements that support the system. This may include the database, interfaces, and supporting architecture, while carrying out consensus between users and the IT department (Tiwana, 2012) in order to model the system according to user needs.
Development and Implementation
This phase involves the actual coding and generation of various cases and scenarios to ensure that the project is implemented as per the user needs. It also involves integrating the various units of the system.
Testing and evaluation of controls
This stage involves testing the system to ascertain that it is working and responding according to the needs of users. It also involves checking on the controls effectiveness.
The deployment phase is the last stage of the lifecycle in which the developed system is configured to operate in a live environment. This may include installing the newly built system into the organization’s infrastructure.
Training users on the new security system Wed 1st – Friday 3rd
Deploying the security system in the company Fri 12th – Sat 13th (3 P.M)
Actual delivery of the system Wednesday, 23rd (12:00pm)
The total budget of implementing the project plan will be sufficient to reduce delays that may occur during the project plan implementation process. It is however an assumption that the total budget will be sufficient to cater for the whole project, with the phases expected to progress as usual. The company also expects that all external project supplies will be made on time.
These are attributes imposed internally or externally and control the project in some way (Gohary et al, 2010).
- Rigid timeline for completion
Critical Project Barrier
- Shortage of funds due to inflation on prices due to the lengthy duration of completing the project
The plan shall be used as a guideline to steer the company in implementing and delivering its system.
El-Gohary, N. M., & El-Diraby, T. E. (2010). Domain Ontology for Processes in Infrastructure and Construction. Journal of Construction Engineering & Management, 136(7), 730-744. doi:10.1061/(ASCE)CO.1943-7862.0000178
Grenci, R. T., & Hull, B. Z. (2004). New Dog, Old Tricks: ERP and the Systems Development Life Cycle. Journal of Information Systems Education, 15(3), 277-286.
Kless, E. (2010). Project Management for Accountants. Journal of Accountancy, 209(4), 38-42.
Müller, R., Glückler, J., Aubry, M., & Shao, J. (2013). Project Management Knowledge Flows in Networks of Project Managers and Project Management Offices: A Case Study in the Pharmaceutical Industry. Project Management Journal, 44(2), 4-19. doi:10.1002/pmj.21326
Tiwana, A. (2012). Novelty-Knowledge Alignment: A Theory of Design Convergence in Systems Development. Journal of Management Information Systems, 29(1), 15-52.