capability maturity model, this shows the company standards
the procedured

1) Initial: The software process is characterized as ad hoc,
and occasionally even chaotic. Few processes are defined,
and success depends on individual effort and heroics.
2) Repeatable: Basic project management processes are
established to track
cost, schedule, and functionality. The necessary process
discipline is in place to repeat earlier successes on
projects with similar applications.
3) Defined :The software process for both management and
engineering activities is documented, standardized, and
integrated into a standard software process for the
organization. All projects use an approved, tailored version
of the organization's standard software process for
developing and maintaining software.
4) Managed :Detailed measures of the software process and
product quality are collected. Both the software process and
products are quantitatively understood and controlled.
5) Optimizing :Continuous process improvement is enabled by
quantitative feedback from the process and from piloting
innovative ideas and technologies.

1.Initial: Initial process
2.Managed:Basic project management
Steps in level2: Requirements Management
                 Project Planning
                 Project Monitoring & Control
                 Measurement & Analysis
                 Process & Product Quality Assurance
                 Configuration Management
3.Defined:Process standardization
Steps in level3:Requirements Development
                Technical Solution
                Product Integration
                verification
                validation
                Organisational Process focus
                Organisational Process definition
                Organisational Training
                Integrated Project Management
                Risk Management
                Integrated Teaming
                Decision analysis and resolution
                Organizational environment for integration
4.Quantitatively Managed:Quantitative management
Steps in level4:Organizational procee performance
                quantitative project management
5.optimising:Continuous process improvement
Steps in level5:organizational innovation and deployment
                analysis and resolution
-----------------------------------------------------------


Requirements Development Process

Templates: SRS
Checklists: RD Process, SRS 
INPUTS:URD
REQUIREMENTS DEVELOPMENT:Develop product requirements
                         Analyze and  Validate requirements
                         Use cases development
OUTPUTS:
                       Develop product requirements
                       Analyze and Validate requirements 
                       Use cases development
METRICS:Time spent on analysis phase 
VERIFICATION:Review of SRS by PM & approved by SDH
             SQA reviews the SRS
------------------------------------------------------------

Product Integration Process

Checklist: PI Checklist
INPUTS:
       HLD
       LLD
       SDP
PRODUCT INTEGRATION:
      Product integration planning
      Product integration testing
OUTPUTS:Integration plan(SDP)
        Integration testing
        Integration test cases
VERIFICATION:PL and PM reviews the Product Integration items
------------------------------------------------------------
Design Process

Templates: Design Change Request, HLD , LLD

Checklists:HLD,LLD, Architectural Design Review Checklist
INPUTS:
      Design constraints
      SRS
      Change requests 
      URD
      SDP
DESIGN PROCESS:
           High Level Design
           Low Level Design
           Use case diagrams
           Sequence diagrams
           Data Flow
            Physical data base design
OUTPUTS:TS plan
        HLD
        LLD
METRICS:SQA audit NC
        Time spent on design Phase
VERIFICATION:PM verifies and approves the HLD, LLD &    
database documents.
             SQA verifies the design items.
------------------------------------------------------------
Coding and Development Process

Templates: Unit Test Case, Unit Test Report, Customer 
Acceptance form

Guidelines: Coding guidelines
INPUTS:
       Project Plan
       SRS
       HLD
       LLD
       Coding standards
       Design updates
CODING/DEVELOPMENT:Development
                   Unit testing
OUTPUTS:Code
        Code review report
        Code peer review reports
        Unit test cases 
        Unit test reports
METRICS:Coding defects
         Time spent on coding
         Unit test results(Bug reports)
         Audit NC
VERIFICATION:PM and SQA  verifies the development items.
------------------------------------------------------------
Validation Process

Templates: Software Test Plan, Test Case form, Defect 
Report, Test Summary Report, 
	   Tester weekly Status Report 
Checklists: Validation Process Checklist
INPUTS:
       Managed Code
       HLD
       LLD
       Test Plan
       Test Cases
       SDP
VALIDATION:
          Integration Testing
          System Testing
          User Acceptance Testing
OUTPUTS: Test cases(UI, functional,
	integration)
        Defect reports
        Test summary report
METRICS:Defect removal Efficiency
        Time spent on validation
        Audit NC’s
       Defect detection rate
       Defect Density
       Defect injection rate
VERIFICATION:PM reviews the test plan and SDH approves the 
test plan
Test Lead and SQA  verifies test items
------------------------------------------------------------

Verification Process, Review Procedure

Templates: Peer review log, SRM Review Report, Peer Review 
Report
Checklists: Verification Process Checklist
INPUTS:
       SDP
       MPP
VERIFICATION:
       Verification of artifacts 
       Verification of code
OUTPUTS:Review report 
        Peer review log
METRICS:
      Time spent on reviews
      Review efficiency
      Audit  NC’s
VERIFICATION:PM and SQA reviews the verification process.
------------------------------------------------------------

Thanks for Answers