Networking Design And Development

Net fashioning Design And DevelopmentE real body developed or task that had been carried out necessitate a framework or method to follow as guideline in erect to make sure of succeeder implementation. Guideline of structured framework potty encourage to manage and intend rolls, to swerve the difficulties like failure to gain requirements, low quality, high operation cost, non meeting the estimated time, inefficient work, and expensive maintenance. In interlocking, the entire concept of visualiseing a net profit is simplified through the use of inventned or structured protrude methodologies. Structured initiation methodological analysis is a set of distinct steps that help to guarantee that every(prenominal) of the essential tasks in the interlocking public figure operation atomic number 18 accomplished. In this applyation notify, we were concentrating on three major topics on victimization and implementation framework System victimisation Life unit of amm unition (SDLC), PDIOO (acronym of Planning, Design, implementation, Operation and Optimization) and PPDIOO (enhanced version of PDIOO).System Development Life musical rhythm (SDLC)The Systems Development Life Cycle (SDLC) is framework that describes the activities executed at each stage of a software development project. It is also a theoretical model used in project administration that describes the builds involved in an information system development project from an initial possibility study through maintenance of the completed drill.System screwliness cycle models describe human bodys of the system cycle, signifier 1 and the order in which those phases are executed. There are different phases for SDLC and the following are the main phases of it.Figure SDLC CyclePhases of SDLC modelProject supplying phaseDuring this phase, resources ordain be acknowledged and cost will be estimated in order to succeed project objectives. Project inventning is process of defining methods , scope, length and work for completion of a project.Requirements Definition phaseUnder this phase, the projects goal is checkerd and the functions are brought to focus. Gathering of information and analysis of the users requirement is also done in this phase.Design phaseA sample structure of the entire project is created in this phase and all necessary data are ga on that pointd. This is where e verything is put in concert and the actual design of the system is done. This is also where documentation such as the Maintenance Manual, Operations Manual, and Training Manual begin. This is also where some(prenominal) of the flaws in the master devisening may appear and require some adjustment. Again, there is documentation and approval.Development phaseThe system is built. The software, hardware, and trying occur during the Development Stage. This is also the phase where the bugs are worked out of the system. integrating and Test phaseThis is the formal integration and testing of t he system. Testing has been done on the development phase, but in the Integration and Testing Phase it is a formal, documented testing procedure, not only to assure that the system performs as designed, but testing the roll-out of the system.Installation and Acceptance phaseAfter completing the testing phase, the completed system should be installed at the end user sites. Users will accept the system after all errors and bugs captured during the old phases have been modified and repaired.SDLC ModelsThere are various SDLC methodologies, Figure 2, have been developed to guide the processes involved including the waterfall model (the original SDLC method), rapid application development (RAD), prototype model, spiral model and m all other models. Some models work better for precise types of projects, but in the final analysis, the about primary(prenominal) factor for the success of a project may be how closely particular plan was followed. The image down shows some of SDLC modelsFig ure SDLC discussed in this reportWaterfall ModelWaterfall Model is the most common and classic of life cycle models, also referred to as a linear-sequential life cycle model. It is very simple to understand and use. In a waterfall model, Figure 3, each phase must be completed in its entirety before the undermentioned phase tummy begin. At the end of each phase, a review takes place to determine if the project is on the right path and whether or not to continue or discard the project. (Priya, 2008)Figure SDLC, Waterfall ModelPhases of ProcessRequirements defines needed information, function, behaviour, performance and interfaces.Design data structures, software architecture, interface representations, algorithmic details. executing source code, database, user documentation, testing.Verification (testing) Brings all the pieces together into a special testing environment, then checks for errors and bugs.Maintenance System changed to reflect changing conditions.AdvantagesThis mode l is very simple and easy to use and easy to manage due to the rigidity of the model each phase has specific deliverables and a review process. Phases are treat and completed one at a time. It works well for smaller projects where requirements are very well understood. (Priya, 2008)DisadvantagesIf there any adjustment scope during the life cycle can kill a project progress. No working software/ growth is produced until late during the life cycle. It has high amounts of essay and uncertainty. As far as the development concern, it is a poor model for complex and object-oriented projects. It is not suitable for long and on-going projects where requirements are at a moderate to high insecurity of changing.When to use the Waterfall ModelIt is going to be used when project requests are very well known and understandable. The product definition is stable and the engineering is understoodFigure SDLC, Prototype ModelPrototypeFigure 4 shows a Prototype Model. In this model, once the requi rement analysis is done and the design for a prototype is made, the development process gets started. Once the prototype is created, it is given to the user for evaluation. The customer tests the package and gives his feed back to the developer who refines the product according to the customers require expectation.Advantagesclients can see the system requirements as they are being gathered. The developers can learn from the customers. It proper to a to a greater extent accurate end product and there will no unexpect requirements accommodated where it abandons for flexible design and development.DisadvantagesIt has bad status for quick-and-dirty methods. The customer may want the prototype delivered. At the end of it, the process may continue forever.When to use the prototype ModelWhen requirements are unstable or have to be clarified. And other thing, where project has to deal with development of user interfaces when it needs a short-lived demonstrations with information for the a nalysis and design portions of object-oriented development involve to be presented.Spiral Cycle ModelIn the spiral cycle model, Figure 5, the concept is more(prenominal) on risk of infection analysis. The spiral model has four phases which are Planning, Risk Analysis, Engineering and Evaluation. Requirements are gathered during the planning phase. In the risk analysis phase, a process is undertaken to identify risk and alternate dissolvers. A prototype is produced at the end of the risk analysis phase.Figure SDLC, Spiral Cycle ModelAdvantagesIt has a high amount of risk analysis which that kind of information is very useful to the project. Good for huge and mission-critical projects. Lastly, in software development, the product will be created early in the software life cycle.DisadvantagesIt can be an overpriced model to use and risk analysis requires highly specific expertise. The Projects success is highly hooked on on the risk analysis phase and it doesnt work well for smalle r projects.When to use the Spiral ModelWhen cost and risk evaluation is most-valuable and it is good for medium to high-risk projects. Spiral model is the best when users are unsure of their needs and requirements are complex. If dealing with a new product line, it significant changes are expected and the model ready to deal with it.Incremental ModelThe incremental model is a natural attempt to the waterfall model. Figure 6 shows multiple development cycles take place, fashioning the life cycle a multi-waterfall cycle. Cycles are divided up into smaller, more easy managed iterations. Each iteration passes through the requirements, design, implementation and testing phases.Figure SDLC, Incremental ModelAdvantagesIt generates working software quickly and early during the software life cycle. It provides more flexible less costly to change scope and requirements. And it is easier to test and debug during a smaller iteration. Furthermore, it is easier to manage risk because risky pi eces are determine and handled during its iteration.Customer can respond to each build with lowers initial delivery cost. Initial product delivery is faster but the customers will get important functionality early.At last the risk of changing requirements is reduced.DisadvantagesIt requires a good planning and design and early definition of a complete and fully functional system to allow for the definition of increments. Sometimes, well-defined module interfaces are required (some will be developed long before others). Not forgotten, total cost of the complete system is not lower.When to use the Incremental ModelRisk, funding, schedule, program complexity, or need for early realization of benefits. Most of the requirements are known up-front but are expected to evolve over time. This model needs to get basic functionality to the market early. It suitable on projects which have lengthy development schedules or a project with a new engineering sciencePDIOO internet Life CycleCisco uses a methodological analysis known as PDIOO as part of designing webs ( Lamml Barkl, 2003). PDIOO is an acronym that describes some of the major elements in a profits design process, namelyPlanningDesignImplementationOperationOptimizationFigure PDIOO (Oppenheimer, 2004)But then cisco come out with a new enhanced concept called PPDIOO where the first P refers to PREPARE. In this paper, part of the phases in PDIOO is going to be explained in PPDIOO phases.PPDIOO Network Life CyclePPDIOO is the correctd PDIOO methodology composed by six (6) phases closely related to PDIOO rather than has one additional phase that is required by real life byplay of a company. formulatePlanningDesignImplementationOperationOptimizationFigure PDIOO (Oppenheimer, 2004)PPDIOO religious service lifecycle allows earnings design engineers and network planners to better manage large network installations. Cisco created this methodology to allow network engineers to better plan and meet disdain objectiv es.Why PPDIOO Model?The methodology created to reduce the total cost of network ownership while the company or organization adds some new technologies or upgrade the be network (Semperboni, 2009).Increasing availability, Downtime can badly affect income and can reduce profitability through cost associated with the network staff having to troubleshoot and function in a excited mode (Semperboni, 2009). To surge availability request to carefully planned redundancy, sound security, and scalability and also requires carefulness throughout the network lifecycle.To Improving air agility can be described as an organizations ability to respond rapidly to changing art or market conditions and adapt to the changing demands of its customers and the business environment introduction hie Speeding access to applications and services helps enable business agility.Availability targets are influenced by business goals. Targets are established early in the network lifecycle and achieved throughou t it a smooth, well-planned deployment helps minimize risk of downtime, and sound planning for day-to-day operations helps speed problem re solving. (Semperboni, 2009)Life Cycle PhasesThe network design methodology composed by six phases (Cisco, 2008), Figure 9, closely related prepare, plan, design, implement, operate, optimize. In this section we give you more details of each of the phases.Figure PPDIOO phasesPrepare descent agility starts with preparation. The preparation phase is the discovery process to understand the business requirements gathering to build a business case and financial motivation to certify the implementation of new applied science (CiscoSystem, 2004). By expecting future needs and developing both a applied science strategy and a high-level architecture to meet those needs (Cisco, 2008).In this phase we should know aboutBusiness requirement developmentConsider and document the business requirements for end-user service delivery that support the engineering investment.Business requirements development can help toMake sound financial decisions by developing a business case that establishes the financial justification for making a technology changeEstablish a basis for developing a technology strategyTechnology strategy developmentAnalyse your business and service requirements and identify the Cisco advanced technologies that support them. Document a technology strategy.Technology strategy development can help to improve susceptibility throughout the solution lifecycle by aligning your technology strategy to your business goalsMeet end-user service-delivery requirements by identifying which advanced technologies can create a solution that can support themOperation Technology strategy developmentCreate an operational strategy that defines the people, processes, and tools required to support the operations and focus of the technology solution.Operations technology development can help toAchieve business goals by aligning your operati ons strategy with your business and technical requirements garnish on-going network operations costs by identifying the operational requirements for supporting the operation and management of the technology solutionHigh Level Design DevelopmentCreate a high-level conceptual architecture of your proposed system that talking toes business and technical requirements and creates the foundation for system deployment. Include specifications for availability, capacity, and security to meet service requirements. High-level design development can help you to reduce rework during the design phase by identifying and validating required technologies and sports early in the solution lifecycle.Business Case DevelopmentPrepare and present an executive-level business case that details the business and financial justification for migrating to the new technology solution. Include a precise financial analysis, including capital and operational expenses, cost-to-benefit analysis, and intercommunica te return on investment. Business case development can help in make sound financial decisions by demonstratingThat the technology investment supports your business goals and high-level designThe cost-to-benefit ratios of both adopting and not adopting the proposed solutionReturn on investment based on multiple investment criteria such as net payback period and internal rate of returnProof ConceptDevelop and conduct a proof-of-concept test to validate the high-level design. Identify design enhancements necessary to meet business and technical requirements. Proof of concept testing can help you reduce costly rework and project delays by identifying design enhancements necessary to meet your business and technical requirements before proceeding to detailed designPlanThe network requirements are what you need to identify in the planning phase. (CiscoSystem, 2004). Important considerations for this phase include determining exactly where you plan to install the network, its objectives, a nd the types of services it will provide and to whom, etc. in this phase the brisk network tests its network for security implementation or security vulnerability to visit it will be able to assist with intruders and outside networks . In this phase the most important things is to ensure that the existing environment is carefully analysed before going to design phase.Development Project ManagementProvide for one or more project managers or program managers to manage the planning, design, and implementation of your deployment project. Develop and implement a project management plan, manage information and resources, and control change.Deployment project management can help to get down risks by using proven project management methodologies and risk mitigation strategiesResolve problems quickly by managing information, facilitating collaboration, and escalating issues promptly and efficaciouslyKeep the project on track by managing and controlling change throughout the project lifecy cle.System Readiness AssessmentPrepare for your technology solution deployment by assessing the readiness of your existing system infrastructure to support a new technology. Analyse the physical and logical configuration of the network, systems availability, and systems capacity, quality of service, systems resiliency, security, and integration with existing platforms. Identify network and application modifications that should be made precedent to implementation.Systems readiness assessment can help toImprove the return on investment and speed migration by identifying and planning for necessary infrastructure changes as well as resourcesReduce deployment costs by analysing gaps early in the planning process to determine what is needed to support the systemImprove productivity by identifying and decide gaps in service-level requirements associated with availability, capacity, and security specifications.Site Readiness AssessmentPrepare for your technology solution deployment with a comprehensive site assessment that evaluates the readiness of your current facilities infrastructure to support the new technology. Identify any physical, environmental, and electrical modifications that should be made prior to implementation.Site readiness assessment can help toReduce deployment costs and delays by identifying facilities preparation requirements early in the planning processReduce the risk of downtime caused by facilities-related problems.Operation Readiness AssessmentPrepare for your technology solution deployment with a comprehensive operations assessment that evaluates the readiness of your current operations and network management infrastructure to support the new technology. Identify any changes to people, processes, and tools that should be made prior to implementation.Operations readiness assessment can help inEffectively plan and budget for technology expenditures by gauging operational preparedness and ability to support current and planned network techno logies and servicesAvoid downtime by enhancing readiness to operate and manage technologies and servicesReduce network operations costs by identifying the operational changes required to support the operation and management of the technology solutionImprove IT staff productivity by identifying high-demand repeatable tasks that can be automated.Security VulnerabilityProtect your network from inside and outside intruders by assessing system, application, and network device vulnerabilities. Safely simulate activities typical of attacks on your network, without affecting your network. Recommend changes that should be made to the network to help prevent security breaches and reduce risk of attack.Security vulnerability assessment can help toMitigate network security threats by limiting their ability to do damageReduce the downtime, business disruption, and costs associated with viruses and worms, information theft, application abuse, and denial-of-service attacksImprove the overall secur ity state of the corporate trusted network and the systems and information within it by identifying changes to address vulnerabilitiesPrevent attacks from external sources and mistakes made by trusted insiders from resulting in security breachesSupport regulatory compliance by demonstrating that adequate security measures are in place to protect sensitive information assets.DesignIn this phase, the network designers should make a design aligned with business goals and technical requirements can improve network performance while supporting high availability, reliability, security, and scalability, according to requirements gathered during the Plan phase (CiscoSystem, 2004). Also by developing detailed design is important to reduce the risk, delay and the total cost of network operation. The design phase can also guide and accelerate successful implementation with a plan to stage, configure, test, and validate network operations.Application DevelopmentPrepare for a new technology depl oyment by planning and developing custom applications for the technology to support feature and functionality requirements, and to enable the applications to integrate with your existing network infrastructure.Applications development can help toReduce risk when integrating a new technology system into your existing infrastructure by using a proven applications development methodologySpeed migration by providing a detailed development, integration, and test plan that addresses such elements as customized scripts, reporting, and database design slender design developmentDevelop an in-depth, implementation-ready detailed design for your new system. Derive the design from availability, capacity, reliability, security, scalability, and performance specifications that align with your business and technical requirements.Detailed design development can help toReduce expensive, time-consuming network redesign by creating a well-engineered design early in the network lifecycle adjoin system or solution performance, resiliency, and availability by specifying the correct set of hardware, software releases, and hardware and software features and functionalityImprove deployment team and operations staff attainment by providing continuous knowledge exchange throughout design developmentAccelerate adoption of new technologies and improve return on investment by integrating your technical requirements and business goals into a detailed design.Staging plan developmentDevelop a step-by-step plan for staging the configuration, implementation, and connectivity testing of the technology system or solution in a controlled environment that emulates, but does not affect, your production network.Staging plan development can help toReduce delays and other problems during staging with a detailed plan that addresses staging requirements including physical, electrical, and environmental conditions on the site network hardware and software and third-party devicesAccelerate staging plan cr eation by using industry prima(p) practices and staging expertiseOperation Implement Plan DevelopmentDevelop an operations implementation plan detailing the tasks needed to deploy and commission the operations and network management system for the technology to be deployed. Include scheduling of priorities, resources, and responsibilities.Operations implementation plan development can help toReduce delays, disruption, and other problems by accurately estimating the time and resources required to implement new operations and network management systemsImprove efficiency during the operations implementation phase by creating a plan that covers staging, tools, processes, task owners, configuration, testing, documentation, system user acceptance, and success criteria lag Plan developmentPrepare your staff for a new technology deployment by using conventional instructional design methodologies to create a staff plan. Determine the technical activities and tasks required to support the sy stem, measure the ability of functional groups to perform those tasks, and develop a curriculum plan to address skill and knowledge gaps.Staff plan development can help toReduce on-going direct costs by identifying proficiency issues that could affect staff productivity and performanceImprove training effectiveness by comparing staff performance to industry leading practices and your standard operating procedures and defining a role-based curriculum to close any gaps in skill or knowledgeImplementThis phase begins, after the Design phase has been approved. In this phase activities are performed to ensure that the network is designed according to the design specifications without any difficulties or weakness. This phase the network will be implemented to ensure that the new infrastructure meet all the business requirements by installing, configuring, integrating, testing, and commissioning all systemsStagingIn this staging process, it will stage and test your new technology system i n a controlled environment that does not affect your live network, as outlined in your predefined staging plan. Staging can help to improve efficiency and reduce costly delays and rework during implementation by identifying and resolving issues.ImplementationInstall, configure, and integrate the new technology system as specified in your implementation plan. Complete predefined test cases. And need to document all the components, devices, and applications used.Implementation can help toSuccessfully deploy the new technology system by following an in-depth, detailed implementation process based on leading practicesRealize business and technical goals of the new system by implementing it in accordance with recommendations made in the earlier phases of the lifecycle.Operation ImplementationInstall, configure, test, and commission the operations and network management system for the technology and deploying in accordance with operations implementation plan. Operations implementation can help to reduce network operating expenses by improving the efficiency of operations processes and tools.MigrationMigration can help you to reduce risks such as downtime, delays, and the need for rework by following a thorough, detailed implementation process based on leading practices.System Acceptance testingPerform systems-level acceptance testing objectively measure operability and functionality of the system you are deploying to verify that it meets your business and technical requirements and is ready for production. Document the test results. Systems acceptance testing can help you to speed migration accelerate return on investment and reduce unnecessary risk, including disruption, delays, rework, and other problems. These benefits are achieved by demonstrating that your newly deployed system or solution meets the operational, functional, and interface requirements defined in the system acceptance test plan.Business Readiness testingTest the readiness of existing network to s upport end-to-end business processes, including operations, management, and security processes, as outlined in business readiness test plan. Business readiness testing can help to reduce risk of downtime by testing your production networks operations and management business processes.Staff TrainingStaff training concerning managing or implementing development plan for workers skill and competency in the organisation. It is includes scheduling classes, creating the enrolment process, providing course materials, and managing training vendors.Staff training can help toIncrease overall productivity and reduce on-going operating costs through training designed to close the skill gaps that were identified in developing your staff plan Reduce downtime through expedited case handling and reduced mean time to resolution through training targeted to improve operational knowledgeImprove training efficiency and effectiveness by applying the ideal combination of training methods and tools as nee ded to close skill gaps. travelThis phase is the last test of the effectiveness of the design before going to last phase. During this phase the operation team monitors the health of the network to improve service quality reduce disruptions mitigate outages and maintain high availability, reliability, and security. This phase could be the longest phase in the network development life cycle to ensure that the infrastructure is well designed during all previous phases.System monitoringIn this task, it will monitor, manage, and report on service-level metrics and abnormal events or trends that might adversely affect the availability, capacity, performance, and security of your system.Systems monitoring can help toImprove service quality and reduce disruptions and outages by proactively monitoring system health regenerate system availability issues by tracking and assessing capacity, performance, utilization, and other service-level metrics.Incident managementManage and resolve real-time incidents with system components using an incident management process that creates and maintains a report of the status of an incident from isolation to closure.Incident management can help toRestore normal service operation quickly by providing an in-depth incident management process that includes case management, investigation, and diagnosis hardware and software replacement or updates and service restoration, testing, and verificationReduce incident rates and step-up network and/or application availability, reliability, and stability by providing software updates and upgrades as an on-going part of your network operationsProblem managementManage and resolve recurring incidents using an in-depth problem management process that analyses incident trends to identify patterns and systemic conditions.Problem management can help you to reduce the risk of downtime and increase network and/or application availability, reliability, and stability. It delivers these benefits by analysing t he root cause of recurring incidents and