SOP
ID |
Title
and Description |
1000
|
Program/Project
Management – This document provides an overview of the project management infrastructure, reporting relationships and project management activities that exist 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.
|
1001
|
Document
Governance –
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.
|
1002
|
Capacity
Management – 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 SDLC’s service standards and contractual obligations.
|
1003
|
Configuration
Management
– 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.
|
1004
|
Procurement
and Purchasing – This document defines the procedures used to provide an efficient and consistent way of purchasing asses needed to support the operation of SDLC’s 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.
|
1005
|
Release
Planning
– 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.
|
1006
|
IT
Strategic Planning
– This document provides 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.
|
1007
|
Asset
Management
– 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 SDLC with an efficient and consistent way of tracking and managing its assets.
|
1010
|
Site
Monitoring and Problem Management
– 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.
|
1030
|
MIS
Reporting – 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 SDLC and client databases. The procedures employed are identical for standard or Ad Hoc report requests.
|
1040
|
Requirements
Definition
– 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.
|
1041
|
Detail
Design
– 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.
|
1050
|
System
Security – This document provides an overview of SDLC’s 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 blue print for the definition, design, implementation, testing, refinement and deployment of system security solutions.
|
1051
|
Security
Administration – This document provides an overview of SDLC’s 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.
|
1060
|
Service
Level Agreement -
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 (24x7,
Mon-Fri) and the methods by which the efficiency of the delivery of
these services is monitored and reported.
|
1061
|
Incident
Tracking – 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.
|
1100
|
Documentation
of Training–
This document describes the methods used to document job related training received by SDLC personnel.
|
1101
|
Training
and Documentation
– 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.
|
1200
|
Development
– 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.
|
1210
|
Quality
Function
– 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.
|
1220
|
Deployment
– 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
(SOP 1010) procedure provide details for the design, implementation and
operation of monitoring processes for the deployed system.
|