Introduction
The current industry standards in Information Technology projects management require the use of structured plans, in order to allow one carry out an implementation processes. These plans need to follow the systems development life cycle, to ensure that certain implementation paradigms are observed in the deployment process. The systems development life cycle is a framework that outlines the various phases of information systems development (Schwalbe, 2010). The systems development life cycle consists of the five stages, namely requirements definition, systems design, implementation, testing, and evaluation. Purpose of the plan The goal of a systems implementation plan is to help move the implementation process to an ideal state, using some strategies (Dostal et al, 2012). It also ensures that each phase is completed as per the project requirements. The goals and objectives of this implementation plan is to ensure compliance with regulatory standards, by ensuring that the systems implementation process is well managed.This is also to ensure that the right infrastructure is laid down, based on the requirements analysis, and to protect the enterprise-wide computing platform from infiltration attempts. To improve network security by implementing the best standard practices in intrusion prevention and detection.
To enhance access control though implementing industry best standards of access control techniques. Business goals and objectives To reduce network based maintenance expenses that occur as a result of network attack, as well as improve network performance. By implementing this, the organization will record a decrease in the prevalence rates due to inappropriate access and use of business sensitive data. Project Goals and Objectives To develop systems with access privileges, in order to control access to sensitive business information and data. The organization will have an elaborate system that protects its data, as well as its network against intrusion. Scope definition The scope definition communicates the project scope in order to drive the main project activities (Dow & Taylor, 2010). The scope of this plan will be to develop a structured methodology of implementing the network systems, to ensure that the steps are efficient in order to give room for vulnerabilities that may exploit the system The implementation plan will guide the project managers and team members in deploying the network solution, by implementing security technologies to help mitigate against network threats. Items beyond scope Performing software upgrades on sensitive access control devices, as well as the main intrusion prevention systems such as a firewall. Re-configuring the parameters on security devices that have been sourced from vendors.
Projected ExpensesItem Cost ($)Printing expenses $80Consultancy expenses $2,500Courier expenses $300Overheads $500Transport charges $1,000Administration $2,000Utilities i.e. telephone calls $800Total projected expenses $7,180System development life cycle Requirements definition The purpose of the requirements definition is to define the requirements needed for the implementation process, and to ensure that the system to be implemented fulfils the needs of the organization (Luzeaux & Ruault, 2010). In requirements definition, the requirements needed must meet the goals and objective of implementing the security systems, which will be verified in this stage through studying the outlined requirements. System design This phase will involve the actual design of the security solution. It will involve establishing various positions where the devices will be placed, to help safeguard the organizational resources. Implementation This stage of the implementation process, will involve deploying the security technologies implemented, in order to measure their effectiveness as regards to network protection. Testing This phase will involve testing to establish how the security devices are responding to intrusion attempts, in order to make recommendations as pertains to the configured parameters to ensure full deterrence of threats from compromising the organizational resources. Evaluation This phase will involve ascertaining how the security controls and devices that have been deployed are working, and reporting to the management in case the implementation is successful. Milestones
Assumptions: Project assumptions The total cost needed in implementing the plan will be available to prevent any hitch during the implementation process.The items beyond our scope will not occur.The implementation phases will progress as usual per the set timelines.There will be no malfunctions of the security devices sourced from external vendors. Constraints Constraints are limitations that the organization can get involved in, which may be technical or business related (Kemp, 2005).The implementation timeline may be a constraint due to interdependencies between the phases. Critical Project Barriers Lack of commitment from the management Lack of support from the staff members during project implementation Inadequate funds as per the established budget (expenses) The project implementation plan will be a guide in the implementation process. It highlights different items that need to be prevented, as well as the organizational effort required in terms of resources in order to ensure success during the project implementation.
References
Dostal, E., Cloete, A., & Járos, G. G. (2012). Biomatrix: A systems theory in graphics. Stellenbosch: BiomatrixWeb.
Dow, W., & Taylor, B. (2010). Project Management Communications Bible. New York, NY: John Wiley & Sons.
Kemp, S. (2005). Ultimate Guide to Project Management for Small Business: Get It Done Right!. Irvine: Entrepreneur Press.
Luzeaux, D., & Ruault, J.-R. (2010). Systems of systems. London: ISTE.
Schwalbe, K. (2010). Information technology Project Management. Boston, MA: Course Technology/Cengage Learning.
