|
|
 |
|
Viewing report
|
|
|
|
The Open Systems Engineering and Software Development Life Cycle Framework
Open SDLC, Jan 2011, Pages: 1,000
OpenSDLC binds the business drivers to the systems development process ensuring that projects get the proper resource allocation and prioritization to ensure success. The Open SDLC will fast track your projects and your career. IT professionals of every caliber adapt and present the relevant peer-reviewed portions of the included policy, process, procedure, roles and responsibilities documents. We grant you the rights to not merely edit and enhance but to label it as your own! From enterprise-class to start-up the peer-developed, industry reviewed OpenSDLC will prevent you, your team and company from making costly mistakes. Furthermore the OpenSDLC marries the warring tribes of Engineering and Development in a holistic systems approach which eliminates finger pointing and unifies organizations toward harmonious delivery of pragmatic expectations.
Open SDLC provides a consistent peer-reviewed framework for the planning, definition, design, implementation, testing and operational deployment of hardware, software and management systems supporting enterprise class technology products, services, programs and projects. OpenSDLC is a Rational Unified Process (RUP) integrated, Capabilities Maturity Model Integrated (CMMI) International Standards Organization (ISO) quality, systems Development Life Cycle (SDLC) for Platform as a Service (PaaS) Service Oriented Architecture (SOA) Software as a Service (SaaS) on Infrastructure as a Service (IaaS) systems.
The Program/Project Management section provides an overview of the project management infrastructure, reporting relationships and project management activities that exist for the SDLC. This SOP defines the SDLC project management process including structure, relationships and activities associated with recognition, definition, management, design, implementation, testing, release, operation and management of a project.
The Document Governance section provides and overview of the review, modification and approval process for standard operating procedures. This SOP establishes the criteria and activities to be performed in the creation and maintenance of each policy and/or procedure document.
The Capacity Management section defines the procedures and methodology to employ in proactive and operational capacity planning. This SOP defines the activities to perform to ensure that enhancements and new products have an environment that will meet your company's service standards and contractual obligations.
The Configuration Management section defines the procedures for the set-up of platform, network and software components for a release. The SOP addresses the controlled change and update of the Development, QA, FOA/Beta, Staging and Production environments.
The Procurement and Purchasing section defines the procedures used to provide an efficient and consistent way of purchasing assets needed to support the operation of SDLCs business. The SOP establishes the criteria and procedures for requesting, approving, ordering and receiving assets, as well as tracking orders throughout the entire purchasing cycle.
The Release Planning section provides an overview of the first phase of the System Development Life Cycle (SDLC). This SOP identifies the business areas of the company for which the business strategy, priorities and scope of the release/project will be determined.
The IT Strategic Planning section provides an overview of the iterative strategic planning process of IT. Information Technology Strategic planning is a continuous process managed through a project management methodology. Major changes in the business environment (internal and/or external) will lead to a re-assessment of the IT Strategy to ensure it is fully aligned with the business strategy for the company.
The Asset Management section provides an overview of an efficient and consistent way of tracking and managing assets. Assets are defined as those that are needed to support the operation of the business and are considered to be assets of the shared nature. This procedure establishes the criteria to determine which assets need to be managed, the information that needs to be captured and the process for which assets are tracked and reported on. The Asset Management Procedure is initiated upon procuring assets, when assets are reconfigured, when leases or warranties expire and when assets are broken or fixed. The objective of this Standard Operating Procedure (SOP) is to provide the company with an efficient and consistent way of tracking and managing its assets.
The Site Monitoring and Problem Management section provides an overview of the monitoring and problem resolution methodology. This SOP describes the procedures used to define system monitoring, maintenance, evaluation, escalation and resolution procedures for operation of systems.
The MIS Reporting section provides an overview of the standard and Ad Hoc reporting process. This SOP establishes the criteria for accepting, approving, tracking and developing report requests. The procedure is used for all requests for information in company and client databases. The procedures employed are identical for standard or Ad Hoc report requests.
The Requirements Definition section provides an overview for the creation, review and approval of a requirements definition for a project. The primary purpose of the section is to outline the process used to obtain commitment between the Performing and Contracting organizations for a project scope, cost and schedule.
The Detail Design section provides an overview for the creation, review and approval of detailed technical specifications for the project. Technical specifications incorporate detailed analysis and design information for project components for the development, quality and support functions. In addition, sales, marketing, product management and product development are included in the review and approval process to ensure compliance with sales processes and corporate strategy.
The System Security section provides an overview of the processes and procedures for the developing, implementing and enforcing system security. Procedures are outlined through flow charts and descriptions of potential risks and actions to take to eliminate them. This section further provides a blue print for the definition, design, implementation, testing, refinement and deployment of system security solutions.
The Security Administration section provides an overview of the processes and procedures for the administering security. Procedures are outlined through flow charts and descriptions of tasks to perform for granting access, processing requests for information and providing input to development and configuration standards.
The Protection of Proprietary Information (POPI) section establishes the procedures used to identify and label proprietary information and protect it from inadvertent or unauthorized disclosure, modification or destruction.
The Service Level Agreement section provides an overview of the Service Level Agreement (SLA) design process. The SLA then provides a description of the services available to clients (internal and external) for a product/project. The final SLA includes a description of all services, their availability during (e.g. 24x7, Mon-Fri) and the methods by which the efficiency of the delivery of these services is monitored and reported.
The Incident Tracking section is designed to provide a consistent methodology to ensure that defects or bugs identified in the production environment are reported, tracked, communicated, and resolved in an efficient manner. A defect occurs when the production system functionality is not performing in accordance with the Business/Users needs. This procedure is used to manage production source code defects and system problems such as hardware and environment problems.
The Documentation of Training section describes the methods used to document job related training received by associated personnel.
The Training and Documentation section describes the methods used to identify, analyze and prepare documentation and training materials, in order to effectively deploy service enhancements and products to functional units and end-users. The documentation summarized in this procedure is limited to training related materials and product release documentation as outlined in the Scope of Work (SOW) for a specific project. This procedure also encompasses the training roles and responsibilities to effectively perform the knowledge transfer that must occur with any product/service deployment.
The Development section is methodology agnostic and designed to provide for adaptable yet consistent design and implementation of projects. This section further focuses on activities performed during the design of technical design, implementation and testing of project deliverables after project detail design is complete. The goal of development is to produce a deliverable as close to production-quality as possible.
The Quality Function section is to provide an overview of the methods used to design and implement quality monitoring for product/project management. These activities include contributions to business plans, development of an overall quality plan, test strategy, integration and system test plans, preparation and verification of test plans, definition of version control procedures, execution of test plans and validation, user acceptance and performance testing, system deployment and quality monitoring for deployed systems.
The Deployment section provides the methods used to design and implement deployment plans for product/project management. This includes the development of planned tasks for the purpose of rolling out a new system for FOA, BETA or General Availability as dictated by the requirements for a product/project. The contents of this procedure in combination with the methods described in the Site Monitoring and Problem Management procedure provide details for the design, implementation and operation of monitoring processes for the deployed system.
The Control of Quality Records section details the methods used to control records relating to the effective operation of the Quality System. This documentation includes all Quality records that are established and maintained to provide evidence of conformity to requirements and of the effective operation of the quality management system. This includes the Quality Systems Manual, all Standard Operating Procedures (SOP), Work Instructions, Templates and Forms. The intent is to provide requirements for legibility, identification, storage and retrieval.
In summary, the OpenSDLC integrates peer-reviewed best practices and patterns and comprised of hundreds of pages of policies, processes, standard operating procedures, swim lane diagrams, operational forms, work instructions, defined roles and responsibilities. It includes ALL of the original non-watermarked source-editable Word, Visio and Project files and forms with FULL COMMERCIAL RIGHTS to adapt, edit, modify and label and present as your own.
Leverage IT Today!
Product samples
A sample for this product is available. Please Login/Register to download this sample.
|
|
|
|
