+ <h3>Accelerated Cure Paths</h3><br /><br />Name one cure from the past decade. EXACTLY ZERO. The system is broken. Let's do better together. Registration is free, fast and easy just click the tab above and join with peers who know there is a better way and want to get there NOW. Cybermedica is dedicated to operating as a meritocracy for the betterment of mankind big-pharma can therefore stay away.<br />

+ <strong>Program/Project Management</strong> – This document will provide an overview of the project management infrastructure, reporting relationships and project management activities that exist within <a title="CyberMedica’s vision is to revolutionize the life-sciences industry by accelerating the open drug and device discovery process." href="tiki-index.php?page=CyberMedica&amp;bl=y" class="wiki ">CyberMedica</a>. This SOP defines the <a title="CyberMedica’s vision is to revolutionize the life-sciences industry by accelerating the open drug and device discovery process." href="tiki-index.php?page=CyberMedica&amp;bl=y" class="wiki ">CyberMedica</a> project management process including structure, relationships and activities associated with recognition, definition, management, design, implementation, testing, release, operation and management of a project. <a class="wiki external" target="_blank" href="http://sdlc.cybermedica.org" rel="external nofollow">more...</a><br />

- <strong>Document Governance</strong> – This document 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. <a class="wiki external" target="_blank" href="http://sdlc.cybermedica.com" rel="external nofollow">more...</a><br />

+ <strong>Document Governance</strong> – This document 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. <a class="wiki external" target="_blank" href="http://sdlc.cybermedica.org" rel="external nofollow">more...</a><br />

- <strong>Capacity Management</strong> – This document 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 CyberMedica’s<a href="tiki-editpage.php?page=CyberMedica%E2%8%99s" title="Create page: CyberMedica%E2%8%99s" class="wiki wikinew">?</a> service standards and contractual obligations. <a class="wiki external" target="_blank" href="http://sdlc.cybermedica.com" rel="external nofollow">more...</a><br />

+ <strong>Capacity Management</strong> – This document 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 CyberMedica’s<a href="tiki-editpage.php?page=CyberMedica%C3%A2%E2%82%AC%E2%84%A2s" title="Create page: CyberMedica%C3%A2%E2%82%AC%E2%84%A2s" class="wiki wikinew">?</a> service standards and contractual obligations. <a class="wiki external" target="_blank" href="http://sdlc.cybermedica.org" rel="external nofollow">more...</a><br />

- <strong>Configuration Management</strong> – This document 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. <a class="wiki external" target="_blank" href="http://sdlc.cybermedica.com" rel="external nofollow">more...</a><br />

+ <strong>Configuration Management</strong> – This document defines the procedures for the set-up of platform, network and software.orgponents for a release. The SOP addresses the controlled change and update of the development, QA, FOA/Beta, staging and production environments. <a class="wiki external" target="_blank" href="http://sdlc.cybermedica.org" rel="external nofollow">more...</a><br />

- <strong>Procurement and Purchasing</strong> – This document defines the procedures used to provide an efficient and consistent way of purchasing assets needed to support the operation of CyberMedica’s<a href="tiki-editpage.php?page=CyberMedica%E2%8%99s" title="Create page: CyberMedica%E2%8%99s" class="wiki wikinew">?</a> 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. <a class="wiki external" target="_blank" href="http://sdlc.cybermedica.com" rel="external nofollow">more...</a><br />

+ <strong>Procurement and Purchasing</strong> – This document defines the procedures used to provide an efficient and consistent way of purchasing assets needed to support the operation of CyberMedica’s<a href="tiki-editpage.php?page=CyberMedica%C3%A2%E2%82%AC%E2%84%A2s" title="Create page: CyberMedica%C3%A2%E2%82%AC%E2%84%A2s" class="wiki wikinew">?</a> 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. <a class="wiki external" target="_blank" href="http://sdlc.cybermedica.org" rel="external nofollow">more...</a><br />

- <strong>Release Planning</strong> – This document 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. <a class="wiki external" target="_blank" href="http://sdlc.cybermedica.com" rel="external nofollow">more...</a><br />

+ <strong>Release Planning</strong> – This document provides an overview of the first phase of the System Development Life Cycle (SDLC). This SOP identifies the business areas of the.orgpany for which the business strategy, priorities and scope of the release/project will be determined. <a class="wiki external" target="_blank" href="http://sdlc.cybermedica.org" rel="external nofollow">more...</a><br />

- <strong>IT Strategic Planning</strong> – This document will provide an overview of the iterative strategic planning process of IT. Information Technology Strategic planning in an 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. <a class="wiki external" target="_blank" href="http://sdlc.cybermedica.com" rel="external nofollow">more...</a><br />

+ <strong>IT Strategic Planning</strong> – This document will provide an overview of the iterative strategic planning process of IT. Information Technology Strategic planning in an 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.orgpany. <a class="wiki external" target="_blank" href="http://sdlc.cybermedica.org" rel="external nofollow">more...</a><br />

- <strong>Asset Management </strong> – This document provides an overview of an efficient and consistent way of tracking and managing its 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 can be 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 <a title="CyberMedica’s vision is to revolutionize the life-sciences industry by accelerating the open drug and device discovery process." href="tiki-index.php?page=CyberMedica&amp;bl=y" class="wiki ">CyberMedica</a> with an efficient and consistent way of tracking and managing its assets. <a class="wiki external" target="_blank" href="http://sdlc.cybermedica.com" rel="external nofollow">more...</a><br />

+ <strong>Asset Management </strong> – This document provides an overview of an efficient and consistent way of tracking and managing its 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 can be 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 <a title="CyberMedica’s vision is to revolutionize the life-sciences industry by accelerating the open drug and device discovery process." href="tiki-index.php?page=CyberMedica&amp;bl=y" class="wiki ">CyberMedica</a> with an efficient and consistent way of tracking and managing its assets. <a class="wiki external" target="_blank" href="http://sdlc.cybermedica.org" rel="external nofollow">more...</a><br />

- <strong>Site Monitoring and Problem Management</strong> – This document 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. <a class="wiki external" target="_blank" href="http://sdlc.cybermedica.com" rel="external nofollow">more...</a><br />

+ <strong>Site Monitoring and Problem Management</strong> – This document 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. <a class="wiki external" target="_blank" href="http://sdlc.cybermedica.org" rel="external nofollow">more...</a><br />

- <strong>MIS Reporting</strong> – This document 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 <a title="CyberMedica’s vision is to revolutionize the life-sciences industry by accelerating the open drug and device discovery process." href="tiki-index.php?page=CyberMedica&amp;bl=y" class="wiki ">CyberMedica</a> and client databases. The procedures employed are identical for standard or Ad Hoc report requests. <a class="wiki external" target="_blank" href="http://sdlc.cybermedica.com" rel="external nofollow">more...</a><br />

+ <strong>MIS Reporting</strong> – This document 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 <a title="CyberMedica’s vision is to revolutionize the life-sciences industry by accelerating the open drug and device discovery process." href="tiki-index.php?page=CyberMedica&amp;bl=y" class="wiki ">CyberMedica</a> and client databases. The procedures employed are identical for standard or Ad Hoc report requests. <a class="wiki external" target="_blank" href="http://sdlc.cybermedica.org" rel="external nofollow">more...</a><br />

- <strong>Requirements Definition</strong> – This document provides an overview for the creation, review and approval of a requirements definition for a project. This procedure refers to the second phase of the System Development Life Cycle (SDLC). The primary purpose of the document is to outline the process used to obtain commitment between the Performing and Contracting organizations for a project scope, cost and schedule. <a class="wiki external" target="_blank" href="http://sdlc.cybermedica.com" rel="external nofollow">more...</a><br />

+ <strong>Requirements Definition</strong> – This document provides an overview for the creation, review and approval of a requirements definition for a project. This procedure refers to the second phase of the System Development Life Cycle (SDLC). The primary purpose of the document is to outline the process used to obtain.orgmitment between the Performing and Contracting organizations for a project scope, cost and schedule. <a class="wiki external" target="_blank" href="http://sdlc.cybermedica.org" rel="external nofollow">more...</a><br />

- <strong>Detail Design</strong> – This document provides an overview for the creation, review and approval of detailed technical specifications for the project. Technical specification incorporated 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. <a class="wiki external" target="_blank" href="http://sdlc.cybermedica.com" rel="external nofollow">more...</a><br />

+ <strong>Detail Design</strong> – This document provides an overview for the creation, review and approval of detailed technical specifications for the project. Technical specification incorporated detailed analysis and design information for project.orgponents 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.orgpliance with sales processes and corporate strategy. <a class="wiki external" target="_blank" href="http://sdlc.cybermedica.org" rel="external nofollow">more...</a><br />

- <strong>System Security</strong> – This document provides an overview of CyberMedica’s<a href="tiki-editpage.php?page=CyberMedica%E2%8%99s" title="Create page: CyberMedica%E2%8%99s" class="wiki wikinew">?</a> 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 document provides a blueprint for the definition, design, implementation, testing, refinement and deployment of system security solutions. <a class="wiki external" target="_blank" href="http://sdlc.cybermedica.com" rel="external nofollow">more...</a><br />

+ <strong>System Security</strong> – This document provides an overview of CyberMedica’s<a href="tiki-editpage.php?page=CyberMedica%C3%A2%E2%82%AC%E2%84%A2s" title="Create page: CyberMedica%C3%A2%E2%82%AC%E2%84%A2s" class="wiki wikinew">?</a> 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 document provides a blueprint for the definition, design, implementation, testing, refinement and deployment of system security solutions. <a class="wiki external" target="_blank" href="http://sdlc.cybermedica.org" rel="external nofollow">more...</a><br />

- <strong>Security Administration</strong> – This document provides an overview of CyberMedica’s<a href="tiki-editpage.php?page=CyberMedica%E2%8%99s" title="Create page: CyberMedica%E2%8%99s" class="wiki wikinew">?</a> 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. <a class="wiki external" target="_blank" href="http://sdlc.cybermedica.com" rel="external nofollow">more...</a><br />

+ <strong>Security Administration</strong> – This document provides an overview of CyberMedica’s<a href="tiki-editpage.php?page=CyberMedica%C3%A2%E2%82%AC%E2%84%A2s" title="Create page: CyberMedica%C3%A2%E2%82%AC%E2%84%A2s" class="wiki wikinew">?</a> 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. <a class="wiki external" target="_blank" href="http://sdlc.cybermedica.org" rel="external nofollow">more...</a><br />

- <strong>Service Level Agreement</strong> - This document provides an overview of the Service Level Agreement (SLA) design process. The SLA 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 (24x7x365) and the methods by which the efficiency of the delivery of these services is monitored and reported. <a class="wiki external" target="_blank" href="http://sdlc.cybermedica.com" rel="external nofollow">more...</a><br />

+ <strong>Service Level Agreement</strong> - This document provides an overview of the Service Level Agreement (SLA) design process. The SLA 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 (24x7x365) and the methods by which the efficiency of the delivery of these services is monitored and reported. <a class="wiki external" target="_blank" href="http://sdlc.cybermedica.org" rel="external nofollow">more...</a><br />

- <strong>Incident Tracking</strong> – The objective of this document is 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 is not intended to manage system environment problems such as hardware and environment problems. <a class="wiki external" target="_blank" href="http://sdlc.cybermedica.com" rel="external nofollow">more...</a><br />

+ <strong>Incident Tracking</strong> – The objective of this document is to provide a consistent methodology to ensure that “defects” or “bugs” identified in the production environment are reported, tracked,.orgmunicated, 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 is not intended to manage system environment problems such as hardware and environment problems. <a class="wiki external" target="_blank" href="http://sdlc.cybermedica.org" rel="external nofollow">more...</a><br />

- <strong>Documentation of Training</strong> – This document describes the methods used to document job related training received by <a title="CyberMedica’s vision is to revolutionize the life-sciences industry by accelerating the open drug and device discovery process." href="tiki-index.php?page=CyberMedica&amp;bl=y" class="wiki ">CyberMedica</a> personnel. <a class="wiki external" target="_blank" href="http://sdlc.cybermedica.com" rel="external nofollow">more...</a><br />

+ <strong>Documentation of Training</strong> – This document describes the methods used to document job related training received by <a title="CyberMedica’s vision is to revolutionize the life-sciences industry by accelerating the open drug and device discovery process." href="tiki-index.php?page=CyberMedica&amp;bl=y" class="wiki ">CyberMedica</a> personnel. <a class="wiki external" target="_blank" href="http://sdlc.cybermedica.org" rel="external nofollow">more...</a><br />

- <strong>Training and Documentation</strong> – This document 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. <a class="wiki external" target="_blank" href="http://sdlc.cybermedica.com" rel="external nofollow">more...</a><br />

+ <strong>Training and Documentation</strong> – This document 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 e.orgpasses the training roles and responsibilities to effectively perform the knowledge transfer that must occur with any product/service deployment. <a class="wiki external" target="_blank" href="http://sdlc.cybermedica.org" rel="external nofollow">more...</a><br />

- <strong>Development</strong> – The purpose of this document is to provide for consistent the design and implementation of projects. This document 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. <a class="wiki external" target="_blank" href="http://sdlc.cybermedica.com" rel="external nofollow">more...</a><br />

+ <strong>Development</strong> – The purpose of this document is to provide for consistent the design and implementation of projects. This document focuses on activities performed during the design of technical design, implementation and testing of project deliverables after project detail design is.orgplete. The goal of development is to produce a deliverable as close to production-quality as possible. <a class="wiki external" target="_blank" href="http://sdlc.cybermedica.org" rel="external nofollow">more...</a><br />

- <strong>Quality Function</strong> – The objective of this document 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. <a class="wiki external" target="_blank" href="http://sdlc.cybermedica.com" rel="external nofollow">more...</a><br />

+ <strong>Quality Function</strong> – The objective of this document 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. <a class="wiki external" target="_blank" href="http://sdlc.cybermedica.org" rel="external nofollow">more...</a><br />

- <strong>Deployment</strong> – The objective of this document is to provide an overview of 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 planning details for the design, implementation and operation of monitoring processes and roadmaps for the deployed system. <a class="wiki external" target="_blank" href="http://sdlc.cybermedica.com" rel="external nofollow">more...</a><br />

+ <strong>Deployment</strong> – The objective of this document is to provide an overview of 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.orgbination with the methods described in the Site Monitoring and Problem Management procedure provide planning details for the design, implementation and operation of monitoring processes and roadmaps for the deployed system. <a class="wiki external" target="_blank" href="http://sdlc.cybermedica.org" rel="external nofollow">more...</a><br />