applicant by alendar

VIEWS: 20 PAGES: 11

									                                                                                      ATTACHMENT C


       CRITERIA FOR CERTIFICATION OF FUNCTION POINT SOFTWARE TYPE 2


Applicant _______________________________________________________________________

                                           (Company Name)

This document provides the critical items that should be covered using software for function point
counting.

Type 2 software provides Function Point data collection and calculation functionality, where the
user and the system/software determine the Function Point count interactively; the user answers
to the questions made to him by the system/software and the system/software makes decisions
about the count, records it and performs the appropriate calculations.

The software and its associated documentation must conform to the Counting Practices Manual. Each
mandatory (not optional) item must be covered in detail in the software and also in the documentation.
Each optional item should be covered in detail in the software and in the documentation.

The items required to be automatically identified by the system/software are represented in the
appropriates check-lists by (AI) (AI = Automate Identification).

The items that may be entered in the system manually by the user are represented in the appropriates
check-lists by (MI) (MI = Manual Input).

The items that may be either automatically identified by the system/software or entered/refined
manually by the user are represented by (AI/MI).

In the table below, please note the page number(s) in the space provided to identify the location of that
criterion in your printed software documentation. Also, please note the menu number(s) or alpha(s) in
the space provided to identify the location of that criterion in your software. Make sure all items in the
checklist are covered. Failure to do so will result in your material being classified as “incomplete”.




                                                 Page 1
Revised October, 1999
                                                                         ATTACHMENT C


      CRITERIA FOR CERTIFICATION OF FUNCTION POINT SOFTWARE TYPE 2

Documentation Software                         Criteria                    Reviewer’s
Page Number Menu Number                                                    Comments
                          A. DESCRIPTIVE INFORMATION
                          1. ID of application/project (MI)
                          2. Name of application/project (MI)
                          3. Description of application/project (MI)
                          4. Type of count (MI)
                          5. Link between the Enhancement Projects and
                             the modified application(s) (MI)
                          B. FUNCTION TYPES




                                      Page 2
Revised October, 1999
                                                                       ATTACHMENT C


     CRITERIA FOR CERTIFICATION OF FUNCTION POINT SOFTWARE TYPE 2
Documentation Software                        Criteria                     Reviewer’s
Page Number Menu Number                                                    Comments
                        1. Each user identifiable group of logically
                            related data or control information referenced
                            by the application/project being counted, but
                            maintained within the boundary of another
                            application and having as primary intent to
                            hold data referenced through one or more
                            elementary processes within the boundary of
                            the application/project being counted is
                            identified as an External Interface File
                            (EIF) (AI)
                           a) ID, or number, or name (AI/MI)
                           b) Description (MI)
                           c) If it represents Conversion Functionality
                               (optional, MI)
                           d) Each unique user recognizable, non-
                               repeated field retrieved from the EIF
                               through the execution of an elementary
                               process is counted as a DET (AI/MI)
                           e) Name of DETs (optional, MI)
                           f) Each user recognizable subgroup of data
                               elements within the EIF is counted as a
                               RET (AI/MI)
                        2. Each user identifiable group of logically
                            related data or control information
                            maintained within the boundary of the
                            application/project being counted and having
                            as primary intent to hold data maintained
                            through one or more elementary processes of
                            the application/project being counted is
                            identified as an Internal Logical File (ILF)
                            (AI)
                            a) ID, or number, or name (AI/MI)




                                        Page 3
Revised October, 1999
                                                         ATTACHMENT C


      CRITERIA FOR CERTIFICATION OF FUNCTION POINT SOFTWARE TYPE 2

Documentation Software                    Criteria           Reviewer’s
Page Number Menu Number                                      Comments




                                 Page 4
Revised October, 1999
                                                                          ATTACHMENT C


     CRITERIA FOR CERTIFICATION OF FUNCTION POINT SOFTWARE TYPE 2
Documentation Software                         Criteria                       Reviewer’s
Page Number Menu Number                                                       Comments
                           a) Description (MI)
                           b) If it represents Conversion Functionality
                               (optional, MI)
                           c) Each unique user recognizable, non-
                               repeated field maintained in the ILF through
                               the execution of an elementary process is
                               counted as a DET (AI/MI)
                           d) Name of DETs (optional, MI)
                           e) Each user recognizable subgroup of data
                               elements within the ILF is counted as a
                               RET (AI/MI)
                        3. Elementary process that processes data or
                            control information that comes from outside
                            the application/project’s boundary being
                            counted and having as primary intent to
                            maintain one or more ILFs and/or to alter the
                            behavior of the system, is identified as an
                            External Input (EI) (AI)
                           a) ID, or number, or name (AI/MI)
                           b) Description (MI)
                           c) If it represents Conversion Functionality
                               (optional, MI)
                           d) Each user recognizable, non-repeated field
                               that enters or exits the application/project’s
                               boundary being counted and is required to
                               complete the EI is counted as a DET
                               (AI/MI)
                           e) The capability of the application/project
                               being counted to send a system response
                               message outside it’s boundary to indicate
                               an error occurred during processing,
                               confirm that processing is complete or
                               verify that processing should continue is
                               counted as one DET (AI)
                           f) The ability of the application/project being
                               counted to specify an action to be taken is
                               counted as one DET, even if there are
                               multiple methods for invoking the same
                               logical process (AI)
                           g) Name of DETs (optional, MI)

                                          Page 5
Revised October, 1999
                                                         ATTACHMENT C


      CRITERIA FOR CERTIFICATION OF FUNCTION POINT SOFTWARE TYPE 2




                                 Page 6
Revised October, 1999
                                                                             ATTACHMENT C


      CRITERIA FOR CERTIFICATION OF FUNCTION POINT SOFTWARE TYPE 2

Documentation Software                          Criteria                         Reviewer’s
Page Number Menu Number                                                          Comments
                             h) Capability to select the logical file
                                 maintained/read by the EI from the ILFs
                                 and/or EIFs (MI)
                             i) Each different ILF/EIF maintained/read by
                                 the EI is counted as an FTR (AI)
                          4. Elementary process that sends data or control
                              information outside the application/project’s
                              boundary being counted and having as primary
                              intent to present information to a user through
                              processing logic (that contains at least one
                              mathematical formula or calculation, or create
                              derived data) other than, or in addition to, the
                              retrieval of data or control information is
                              identified as an External Output (EO) (AI)
                             a) ID, or number, or name (AI/MI)
                             b) Description (MI)
                             c) If it represents Conversion Functionality
                                 (optional, MI)
                             d) Each user recognizable, non-repeated field
                                 that enters the application/project’s
                                 boundary being counted and is required to
                                 specify when, what and/or how the data is
                                 to be retrieved or generated is counted as a
                                 DET (AI/MI)
                             e) Each user recognizable, non-repeated field
                                 that exits the application/project’s boundary
                                 being counted is counted as a DET (AI/MI)
                             f) If a DET both enters and exits the
                                 boundary, it is counted only once for the EO
                                 (AI)
                             g) The capability of the application/project
                                 being counted to send a system response
                                 message outside it’s boundary to indicate an
                                 error occurred during processing, confirm
                                 that processing is complete or verify that
                                 processing should continue is counted as
                                 one DET (AI)




                                       Page 7
Revised October, 1999
                                                                             ATTACHMENT C


      CRITERIA FOR CERTIFICATION OF FUNCTION POINT SOFTWARE TYPE 2

Documentation Software                          Criteria                         Reviewer’s
Page Number Menu Number                                                          Comments
                             h) The ability of the application/project being
                                 counted to specify an action to be taken is
                                 counted as one DET, even if there are
                                 multiple methods for invoking the same
                                 logical process (AI)
                             i) Name of DETs (optional, MI)
                             j) Capability to select the logical file
                                 maintained/read by the EO from the ILFs
                                 and/or EIFs (MI)
                             k) Each different ILF/EIF maintained/read by
                                 the EO is counted as an FTR (AI)
                          5. Elementary process that sends data or control
                              information outside the application/project’s
                              boundary being counted and having as primary
                              intent to present information to a user through
                              processing logic (that contains no
                              mathematical formula or calculation, and
                              creates no derived data) of retrieval of data or
                              control information from an ILF or EIF is
                              identified as an External Inquiry (EQ) (AI)
                             a) ID, or number, or name (AI/MI)
                             b) Description (MI)
                             c) If it represents Conversion Functionality
                                 (optional, MI)
                             d) Each user recognizable, non-repeated field
                                 that enters the application/project’s
                                 boundary being counted and is required to
                                 specify when, what and/or how the data is
                                 to be retrieved is counted as a DET (AI/MI)
                             e) Each user recognizable, non-repeated field
                                 that exits the application/project’s boundary
                                 being counted is counted as a DET (AI/MI)
                             f) If a DET both enters and exits the
                                 boundary, it is counted only once for the EQ
                                 (AI)




                                       Page 8
Revised October, 1999
                                                                               ATTACHMENT C


      CRITERIA FOR CERTIFICATION OF FUNCTION POINT SOFTWARE TYPE 2

Documentation Software                          Criteria                         Reviewer’s
Page Number Menu Number                                                          Comments
                             g) The capability of the application/project
                                being counted to send a system response
                                message outside it’s boundary to indicate an
                                error occurred during processing, confirm
                                that processing is complete or verify that
                                processing should continue is counted as
                                one DET (AI)
                             h) The ability of the application/project being
                                counted to specify an action to be taken is
                                counted as one DET, even if there are
                                multiple methods for invoking the same
                                logical process (AI)
                             i) Name of DETs (optional, MI)
                             l) Capability to select the logical file read by
                                the EQ from the ILFs and/or EIFs (MI)
                             m) Each different ILF/EIF read by the EQ is
                                counted as an FTR (AI)
                          C. GENERAL SYSTEM CHARACTERISTICS
                          1. Listing of GSCs (AI/MI)
                          2. Degree of Influence (0-5 only) (AI/MI)
                          D. UPDATE CAPABILITY FOR
                          DEVELOPMENT PROJECT (full optional)
                          1. Created application
                            a) Function types of the Development Project
                               are included as Function types of the created
                               application (AI)
                            b) Function types defined as Conversion
                               Functionality of the Development project are
                               not included as Function types of the created
                               application (AI)
                          2. General System Characteristics
                            a) Degrees of influence of the GSCs of the
                               created application are initialized (AI)




                                       Page 9
Revised October, 1999
                                                                           ATTACHMENT C


      CRITERIA FOR CERTIFICATION OF FUNCTION POINT SOFTWARE TYPE 2

Documentation Software                          Criteria                       Reviewer’s
Page Number Menu Number                                                        Comments
                          E. UPDATE CAPABILITY FOR
                          ENHANCEMENT PROJECT (full optional)
                          1. Modified application
                            a) Function types of the modified application
                               include the Function types ADDED by the
                               Enhancement project (AI)
                            b) Function types of the modified application
                               are replaced with the Function types
                               CHANGED by the Enhancement project (AI)
                            c) Function types of the modified application no
                               longer include the Function types DELETED
                               by the Enhancement project (AI)
                            d) Function types defined as Conversion
                               Functionality of the Enhancement project are
                               not included as Function types of the
                               modified application (AI)
                          2. General System Characteristics
                            a) Degrees of influence of the GSC of the
                               modified application are updated (AI/MI)
                          F. AUTOMATED CALCULATIONS
                          1. Complexity for Function Types (L, A, H)
                            a) EIF
                            b) ILF
                            c) EI
                            d) EO
                            e) EQ
                          2. Total for GSCs
                          3. Project Adjusted Function Point Count
                          4. Application Initial Function Point Count
                             (optional)
                          5. Application Function Point Count after the
                              enhancement project (optional)
                          G. DISPLAY/REPORTS (no special format)
                          1. Ability to display/print items input
                          2. Ability to display/print calculations
                          H. IFPUG REFERENCE
                          1. Counting Practices Manual

                                      Page 10
Revised October, 1999
                                                          ATTACHMENT C


     CRITERIA FOR CERTIFICATION OF FUNCTION POINT SOFTWARE TYPE 2
Documentation Software                     Criteria         Reviewer’s
Page Number Menu Number                                     Comments
                        2. Release/Version




                                 Page 11
Revised October, 1999

								
To top