Rapid Deployment of BMC Remedy Solutions
•Transferir como PPT, PDF•
1 gostou•388 visualizações
The document discusses a rapid deployment methodology for BMC Remedy solutions developed by generationE Technologies. It outlines the issues affecting traditional BMC Remedy deployments like developer productivity and time to market. It then describes the benefits of a rapid application development approach and generationE's BMC Remedy rapid deployment methodology which uses iterative development, prototyping, and timeboxing to compress project timelines. A case study example is also provided.
![Agenda ,[object Object],[object Object],[object Object],[object Object],01/21/12 ©2006 BMC Software](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recomendados
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (19)
Semelhante a Rapid Deployment of BMC Remedy Solutions
Semelhante a Rapid Deployment of BMC Remedy Solutions (20)
Último
Último (20)
Rapid Deployment of BMC Remedy Solutions
- 1. Rapid Deployment of BMC Remedy Solutions Antonio Rolle VP of Professional Services generationE Technologies 01/21/12
- 26. What is Meant by “Out-of-the-box”? 01/21/12 ©2006 BMC Software Industry Standards/Best Practices ITIL, Six Sigma, BS 15000, ISO 9000 Plus 13,000 pieces of pre-configured workflow Customer Requested Functionality More than 10 years of industry experience and over 10,000 customers using Remedy Market-Leading Innovations Remedy recognized as the Thought Leader within the IT Service Management market
Notas do Editor
- The RAD methodology is not as popular today as agile methodologies such as eXtreme Programming (XP), but it is still a valuable methodology in the right circumstances. Today RAD has been embodied in a number of methodologies including Agile development, extreme programming, and test-driven development. While these have different names, they all share a common theme: Deliver software into the hands of users as soon as possible.
- RAD is a manifestation of Vilfred Pareto's law known as the 80 - 20 Rule. It states that 80% of XX is caused by 20% of YY. More specifically, 80% of the costs of a complete system are due to 20% of the features included in the system. Conversely, 20% of the system costs are due to 80% of the system features. RAD methodology allows the most important 80% of the system features to rise to the top of the list and be integrated into the system - at a cost of 20% of the complete system. The RAD methodology is not as popular today as agile methodologies such as eXtreme Programming (XP), but it is still a valuable methodology in the right circumstances. RAD is more applicable to organizations because World market place is competitive, need right system at the right time to get competitive edge Organizations are dynamic and evolving, requirements change as a system is built, a frozen specifications become outdated IT now viewed as a cost centre not a resource, once system delivered it starts earning money Systems are used by users, if jointly developed by users then more likely to be accepted
- Prototyping takes place during any activity where clients and developers review and refine systems by use of working software Prototyping is viewed to be used for one of 2 scenarios where interfaces are built, evaluated and thrown away or to be part of an iterative or evolutionary building of software with user collaboration
- As with any project it is vital to identify the details of the project up front in some form of document such as a Project Management Plan (PMP). All parties should agree up front on details such as potential risks and mitigation strategies, a development schedule including resources, milestones and deliverables such as a completed data model or types of documentation to deliver, an approach including standards, tools, and technologies to be used, a desired end result, terms and constraints and financial considerations including budget and cost of tools.
- Develop a problem statement A narrative of the management perspective
- The Design Document will contain: Process Flow Charts/Swim Diagrams/Activity Diagrams Use Cases Collaboration Diagram Sequence Diagram GUI Mock Ups
- Develop the prototype(s) Release/Iteration Plan Release Plan Test Plan ITIL Release Management The goals of Release Management are: to plan and oversee the successful rollout of software and related hardware to design and implement efficient procedures for the distribution and installation of Changes to IT systems to ensure that hardware and software being changed is traceable, secure and that only correct, authorized and tested versions are installed to communicate and manage expectations of the Customer during the planning and rollout of new Releases to agree the exact content and rollout plan for the Release, through liaison with Change management to implement new software Releases or hardware into the operational environment using the controlling processes of Configuration management and Change Management – a Release should be under Change Management and may consist of any combination of hardware, software, firmware and document CIs to ensure that master copies of all software are secured in the Definitive software library (DSL) and that the Configuration management database (CMDB) is updated to ensure that all hardware being rolled out or changed is secure and traceable, using the services of Configuration Management. The focus of Release Management is the protection of the live environment and its services through the use of formal procedures and checks. The goals of Release Management are: to plan and oversee the successful rollout of software and related hardware to design and implement efficient procedures for the distribution and installation of Changes to IT systems to ensure that hardware and software being changed is traceable, secure and that only correct, authorized and tested versions are installed to communicate and manage expectations of the Customer during the planning and rollout of new Releases to agree the exact content and rollout plan for the Release, through liaison with Change management to implement new software Releases or hardware into the operational environment using the controlling processes of Configuration management and Change Management – a Release should be under Change Management and may consist of any combination of hardware, software, firmware and document CIs to ensure that master copies of all software are secured in the Definitive software library (DSL) and that the Configuration management database (CMDB) is updated to ensure that all hardware being rolled out or changed is secure and traceable, using the services of Configuration Management. The focus of Release Management is the protection of the live environment and its services through the use of formal procedures and checks.
- Remedy’s offers a comprehensive solution of best-practice out of box solution. But, let us tell you more what goes into the “box”: BMC Remedy® solutions incorporate industry standards like ITIL. We have over 10 years of experience of serving over 7500 customers and we listen to them. We continue to incorporate new functionality into our product suites – based upon our customer input. BMC continues to innovate by offering the right technology at the right time – Web Services is a part of the AR System platform, so all of the Remedy applications benefit from it. In addition, the BMC workflow definitions, the functional modules and configuration interface all make it easy for our customers to make the Remedy solution meet their unique needs today and into the future.
- Components of an Accepted Business System Remedy® with configuration and customization changes Production Data System Test Results System Test Library System Technical Documentation User/Administrator Operations Manual User Documentation
- As with any project final deliverables should be handed over to the client and such activities should be performed that will benefit future projects. Specifically it is a best practice for a Project Manager to review and document project metrics, organize and store project assets such as reusable code components, Project Plan, Project Management Plan (PMP), and Test Plan. It is also a good practice to prepare a short lessons learned document.