The number of New Source Lines of Code that were not adapted from prior projects.

The percentage of the adapted software’s design which is modified in order to adapt it to the new objectives and environment.

The percentage of the adapted software’s code which is modified in order to adapt it to the new objectives and environment.

The percentage of effort required to integrate the adapted software into an overall product and to test the resulting product as compared to the normal amount of integration and test effort for software of comparable size.

The degree of Assessment and Assimilation needed to determine whether a reused software module is appropriate to the application, and to integrate its description into the overall product description.

Enter 0 For none

Enter 2 For basic module search and documentation

Enter 4 For some module Test and Evaluation (T&E), documentation

Enter 6 For considerable module T&E, documentation

Enter 8 For extensive module T&E, documentation

The percentage that the software is understood.

Enter 50:

    If structure has very low cohesion, high coupling, spaghetti code.

    If application clarity has no match between program and application world-views.

    If self descriptiveness has Obscure code; documentation missing, obscure or obsolete.

Enter 40:

    If structure has moderately low cohesion, high coupling.

    If application clarity has some correlation between program and application.

    If self descriptiveness has some code commentary and headers; some useful documentation.

Enter 30:

    If structure has reasonably well-structured; some weak areas.

    If application clarity has moderate correlation between program and application.

    If self descriptiveness moderate level of code commentary, headers, documentation.

Enter 20:

    If stucture has high cohesion, low coupling.

    If application clarity has good correlation between program and application.

    If self descriptiveness good code commenty and headers; useful documentation; some weak areas.

Enter 10:

    If structure has strong modularity, information hiding in data / control structures.

    If application clarity has clear match between program and application world-views.

    If self descriptiveness self-descriptive code; documentation up-to-date, well-organized, with design rationale.

The amount that one software developer is paid per hour.

RELY depends on the required reliability under which the product was developed.

Select VERY LOW if it will require more effort to fix latent faults.

Select LOW if there is low reliability, but easily recoverable losses.

Select NOMINAL if there is moderate reliability, but easily recoverable losses.

Select HIGH if failures to reliability result in high financial losses.

Select VERY HIGH if failures to reliability result in risk to human life.

Select LOW if testing database bytes per program SLOC is less than 10.

Select NOMINAL if testing database bytes per program SLOC is inclusively between 10 and 99.

Select HIGH if testing database bytes per program SLOC is inclusively between 101 and 999.

Select VERY HIGH if if testing database bytes per program SLOC is greater than 1000

Ultimately, decide whether the project will have almost no documentation, documenation just to get people off your back, adequate documentation, excessive documentation, or extremely excessive documentation

Select VERY LOW if the documentation for the project leaves many lifecycle needs uncovered

Select LOW if the documentation for the project leaves some lifecycle needs uncovered

Select NOMINAL if the documentation for the project has adequate lifecycle needs

Select HIGH if the documentation for the project has somewhat excessive details on lifecycle needs

Select VERY HIGH if the documentation for the project has overly-excessive details on lifecycle needs

Select LOW if no effort will be made to reuse any of the software modules on other projects

Select NOMINAL if components will be reused in the project itself

Select HIGH if components are to be reused across multiple applications from the same organization

Select VERY HIGH if components are to be reused across the product line, such as across multiple organizations

Select EXTRA HIGH if components are to be reused across multiple product lines

TIME is the measure of the storage constraint imposed upon a software system.

Select NOMINAL if less than 50% of available storage is expected to be used.

Select HIGH if 50% to 70% of available storage is expected to be used.

Select VERY HIGH if 70% to 85% of available storage is expected to be used.

Select EXTRA HIGH if more than 85% of availble storage is expected to be used.

PVOL is the volatility of the hardware and software the product calls on to perform its tasks.

Select LOW if there is a major change in the platform every 12 months or a minor change every 1 month.

Select NOMINAL if there is a major change in the platform every 6 months or a minor change every 2 weeks.

Select HIGH if there is a major change in the platform every 2 months or a minor change every 1 week.

Select VERY HIGH if there is a major change in the platform every 2 weeks or a minor change every 2 days.

STOR represents the degree of main storage constraint imposed on a software system.

Select NOMINAL if less than 50% of available storage is expected to be used.

Select HIGH if 50% to 70% of available storage is expected to be used.

Select VERY HIGH if 70% to 85% of available storage is expected to be used.

Select EXTRA HIGH if more than 85% of availble storage is expected to be used.

ACAP signifies the expected capability of the analyst TEAM working on the requirements, high-level design, and detailed design of the project

Select VERY LOW if the analysts are in the 15th percentile.

Select LOW if the analysts are in the 35th percentile.

Select NOMINAL if the analysts are in the 55th percentile.

Select HIGH if the analysts are in the 75th percentile.

Select VERY HIGH if the analysts are in the 90th percentile

PCON rating scale is in terms of the project's annual personnel turnover.

Select VERY LOW if there is expected to be a 48% annual personnel turnover.

Select LOW if there is expected to be a 24% annual personnel turnover.

Select NOMINAL if there is expected to be a 12% annual personnel turnover.

Select HIGH if there is expected to be a 6% personnel turnover.

Select VERY HIGH if there is expected to be a 3% personnel turnover.

PLEX rating scale is in terms of the TEAM's experience using the platform on which they are developing the software.

Select VERY LOW if the team has less than 2 months of experience using the platform.

Select LOW if the team has between 2 months and 6 months of experience using the platform.

Select NOMINAL if the team has between 6 months and 1 year of experience using the platform.

Select HIGH if the team has between 1 year and 3 years of experience using the platform.

Select VERY HIGH if the team has between 3 years and 6 or more years of experience using the platform.

PCAP signifies the expected capability of the programmer TEAM working on the requirements, high-level design, and detailed design of the project

Select VERY LOW if the programmers are in the 15th percentile.

Select LOW if the programmers are in the 35th percentile.

Select NOMINAL if the programmers are in the 55th percentile.

Select HIGH if the programmers are in the 75th percentile.

Select VERY HIGH if the programmers are in the 90th percentile

APEX signifies the level of applications experience of the project TEAM developing the software.

Select VERY LOW if the TEAM has less than 2 months of similar applications experience.

Select LOW if the TEAM has between 2 months and 6 months of similar applications experience.

Select NOMINAL if the TEAM has between 6 months and 1 year of similar applications experience.

Select HIGH if the TEAM has between 1 year and 3 years of similar applications experience.

Select VERY HIGH if the TEAM has 3 or more years of similar applications experience.

LTEX is the measure of the level of experience in the programming language and software tools that the project TEAM has.

Select VERY LOW if the TEAM has less than 2 months of programming language and software tools experience.

Select LOW if the TEAM has between 2 months and 6 months of programming language and software tools experience.

Select NOMINAL if the TEAM has between 6 months and 1 year of programming language and software tools experience.

Select HIGH if the TEAM has between 1 year and 3 years of programming language and software tools experience.

Select VERY HIGH if the TEAM has 3 or more years of programming language and software tools experience.

TOOL measures the capability of the various IDEs or text editors or other software tools used when creating this software.

Select VERY LOW if the software tools have only simple edit, coede, and debug capabilities.

Select LOW if the software tools have simple, frontend, backend, CASE, with little integration.

Select NOMINAL if the software tools have basic lifecycle tools, moderately integrated.

Select HIGH if the software tools are strong, mature lifecycle tools, moderately integrated.

Select VERY HIGH if the software tools are strong, mature, proactive lifecycle tools, well-integrated with processes, methods, and reuse.

SITE is the measure of whether this project has indications that multisite development effects are significants.

Select VERY LOW if team is international and uses some phone, but mostly mail to communicate.

Select LOW if the team is multi-city and/or multi-company and uses individual phones and faxing to communicate.

Select NOMINAL if the team is multi-city and/or multi-company and uses narrow-band email to communicate.

Select HIGH if the team is in the same city or metro area and uses wideband electronic communication.

Select VERY HIGH if the team is in the same building or complex and uses wideband electronic communication with occasional video conferencing.

Select EXTRA HIGH if the team is fully collocated and uses interactive multimedia.

SCED is the cost driver which is used to describe the effect of schedule compression/expansion FOR THE ENTIRE PROJECT

Select VERY LOW if the project is expected to be completed in 75% of the given time.

Select LOW if the project is expected to be complete in 85% of the given time.

Select NOMINAL if the project is expected to be complete in 100% of the given time.

Select HIGH if the project is expected to be complete in 130% of the given time.

Select VERY HIGH if the project is expected to be complete in 160% of the given time..

Precedentedness measures how similar a product is similar to previously developed products. If it is, precedentedness is high.

The flexibility of the software requirements and environment.

This measures whether the tools and resources needed for the project architecture are available, and whether the risk management plan identifies critical risk items and plans for resolving them.

The team scale factor takes into account difficulties in team cohesion.

The procedure for determining PMAT is organized around the Software Engineering Institute’s Capability Maturity Model (CMM).