Docstoc

whitepaper_tech_Health_Index

Document Sample
whitepaper_tech_Health_Index Powered By Docstoc
					                           TECHNICAL HEALTH INDEX - <PROJECT NAME>


Document Name:       ASP-QA-PHI- <Month> <Year>
Date:                <month> <dd>, <yyyy>




                                         Modification History


           Date
May 10, 2007         Aparna Venkateshwaran
July 9, 2007         Krishna Sivaramakrishnan
August 20, 2007      Thanuja Noogala
September 11, 2007   Elango Kanakaraji
September 14, 2007   Benita Michael



September 19, 2007   Krishna Sivaramakrishnan


October 11, 2007     Ganesan Ellappan




January 8, 2008      Ganesan Ellappan
Januaru 9, 2008      Krishna Sivaramakrishnan
March 23,2008        Elango Kanakaraji
INDEX - <PROJECT NAME>


>




cation History


                   Change Description        Version
            Initial draft                    0.1
            Review on criteria               0.5
            Enhanced the existing criteria   0.6
            Added Technical Health Index     0.7
            Review and formatting            0.8

            Project Health Index computed
            based on Process and technical
            inputs.Review and Approval       1.0
            Auto formatted the formule
            columns                           1.3
            Following changes were made:
            1. LLD and HLD Criteria is split
            into two different criteria
            2. Auditor and Auditee' names are
            added for reference.
            3. Overall Comments and
            Recommendations are added for     1.4
            Reviewed and Approved            2.0
            Updated lin eitems               2.1
                                                            TECHNICAL HEALTH INDEX - Zeta Nov 2010


   0 - 0.5                               0.51 - 0.74                            0.75 - 0.95

  TECHNICAL
   SYSTEM
                                          CRITERIA                                  Description
CHARACTERISTI
   CS(TSC)
                                                                   D E V E      L    O P M E N T
                     Development Environment                       Developers workspace should be
    ENVIRONMENT
    DEVELOPMENT




                                                                   configured according to design, source
                                                                   code branch, server setup etc
                     QA environment                                QA system configuration details including
                                                                   size of the database etc
                     UAT Environment                               UAT system configuration details
                                                                   inclduing clustering, load balancing etc
                     Code Synchronization with target repository   Code be synced with target repository



                     Requirments Analysis                          Requirments should be captured in detail
      REQUIREMENTS




                                                                   which includes implicit requirments, data
                                                                   flow analysis etc


                     Technical and Non functional Requirements     Requirements like working on
                                                                   windows/linux paltform, jboss
                                                                   architecture, response time, etc


                     High level Design                             This can be architecture, framework ,
                                                                   component etc
                     Low level Design                              This design is at requirment spec level,
                                                                   use case based design
      DESIGN




                     Sequence Diagram / Class Diagram              Classes for the new enhancements or
                                                                   developments
                     Impact Analysis                               Files or methods affected due to a
                                                                   change in code
                     Database Design                               DB schema design



                     Code/DB Scritps Quality                       Coding guideline compliance,
                                                                   architecture compliance, code coverage,
                                                                   SQL queries
      CODING
                    Unit test classes                                  Unit test cases should be created for

 TESTING
   UNIT                                                                required and delivered source code


                    Functional Unit test case for the implemented      The test cases should be at developer
                    feature                                            like data oriented test cases



                                             Unit Testing and Coding
                    Code Release                                       Code released in the target repository
AS
RE
LE

 E




                                                                       should be the tested source code


                    Deployment procedure for all environments
 YMENT
 DEPLO




                    Build procedure



                                             Deployment and Release

                                                      T E S T I N G
                    Automated Test Scripts
AUTOMATI

 TESTING




                    Regression Testing
   ON




                    Automation Test Bed



                    Test Cases
 FUNCTIONAL
   TESTING




                    Implicit functional Test Cases

                    Regression Testing

                    Functional Test Report



                    Communication Test Cases
   SYSTEM TESTING




                    Performance Test Cases

                    Usability Test Cases

                    Environment Test Cases

                    Security Compliance Test Cases

                    Volume and Stress Testing



                                                 Testing Overall


                           TECHNICAL HEALTH INDEX : <PROJECT NAME><MONTH><YEAR>

                                                                                         Copy Case & Copy Documents fuctionalit
                       OVERALL COMMENTS
                                  Design review seems to
RECOMMENDATIONS FOR THE PROJECT

                                          Muthu Velappa
         AUDITOR' NAME
                                            Sendil Sekki
         AUDITEE' NAME
eta Nov 2010


                          0.96 - 1


            SCALE
           1/ 0/ NA   TSC AVERAGE          REMARKS


 N T

                1

                1

                NA

                NA

               1.00      1.00
                                     Proper Req's available
                                     for both Copy Case t&
                1                    Copy documents to
                                     Alfresco functionality

                                     Hasn't checked
                NA


               1.00      1.00
                NA
                                     I'm not so sure
                1                    whether the detail
                                     specified in UML is
                                     required..
                NA

                1

                NA

               1.00      1.00
                                     1. Variable scoping
                                     should be as specific
                                     as possible..
                                     2. Usage of "continue"
                                     is not required in one
                0
                                     for loop.
                                     3. Catch specific
                                     exceptions rather than
                                     Generic base class…


               0.00      0.00
                                                  1. Basic Initialization
                   0                              Testcase itself is not
                                                  available for Copy
                                                  Case functionality
                  NA

                 0.00               0.00
                 0.00
                   1

                       1.00         1.00
                  NA

                  NA

            NA                       NA
                 1.00


                  NA

                  NA

                  NA

            NA                       NA
                  NA

                  NA

                  NA

                  NA

            NA                       NA
                  NA

                  NA

                  NA

                  NA

                  NA

                  NA

                  NA                 NA
                  NA

>                                   0.67

& Copy Documents fuctionality has been taken for review.
Design review seems to be missing

        Muthu Velappan

          Sendil Sekki

				
DOCUMENT INFO
Categories:
Tags:
Stats:
views:2
posted:3/4/2012
language:
pages:8