|
CATEGORY TEMPLATES

Download hard copy
of Category Templates
In each of the categories below, a minimum of 40 credits must be attained for the category to qualify for submission.
| Work
Experience (WE) 40% |
|
Plan |
Design |
Implement |
Sustain |
Administer |
Evaluate |
Analyze |
Report |
Mentor |
| Tools |
20 |
20 |
20 |
20 |
20 |
20 |
|
|
1 pch |
| Process |
20 |
20 |
20 |
20 |
20 |
20 |
|
|
1 pch |
| Software Measurements |
|
|
|
|
|
20 |
80 |
40 |
1 pch |
Education
(ED)
25% |
|
Attend |
Complete |
Obtain |
| IFPUG Conference |
16 |
|
|
| Eligible Non-IFPUG Conference |
8 |
|
|
| IFPUG Software Measurement Course |
|
16 |
|
| Eligible Non-IFPUG Software Measurement Course
|
|
8 |
|
| Industry Certification |
|
|
50 |
| Professional
Participation (PP) 15% |
|
Attend / Serve |
| Software Measurement Related Group Meetings
– IFPUG |
16 |
| Software Measurement Related Group Meetings
– Non-IFPUG |
8 |
| Software
Measurement Related Publishing (MP) 10% |
|
Author / Co-Author
|
Contributing Author
|
Expert Review
|
Expert Edit |
Translate |
| Book |
80 |
40 |
30 |
20 |
80 |
| Refereed Article |
40 |
|
20 |
10 |
20 |
| Non-Refereed Article |
20 |
|
|
|
20 |
| Software Measurement Exam |
20 |
20 |
20 |
20 |
40 |
| Teaching
(TE) 10% |
|
Author / Co-Author |
Teach |
Present (at IFPUG)
|
Present (not at
IFPUG) |
| Software Measurement Course |
8 |
24 |
|
|
| Software Measurement Poster |
|
|
5 |
|
| Software Measurement Presentation |
|
|
10 |
5 |
Category Name: Work Experience
(WE) (40%)
Description:
This category awards applicants for providing life
cycle support for the tools and processes that constitute a software
measurement program. The credits for mentoring are awarded on a
per contact hour (pch). A minimum of 40 credits must be attained
for this category to qualify for submission.
| Work
Experience (WE) 40% |
|
Plan |
Design |
Implement |
Sustain |
Administer |
Evaluate |
Analyze |
Report |
Mentor |
| Tools |
20 |
20 |
20 |
20 |
20 |
20 |
|
|
1 pch |
| Process |
20 |
20 |
20 |
20 |
20 |
20 |
|
|
1 pch |
| Software Measurements |
|
|
|
|
|
20 |
80 |
40 |
1 pch |
Example inclusion:
 |
The applicant has created two unique and significant software
measurement programs for two different projects (could be in
a single organization or across organizations). (In this case,
created means planned and designed.) Award 80 credits
(40 for each project). |
 |
The applicant is asked to review and make recommendations
regarding a metrics program process. Award 20 credits
for evaluate. |
 |
The applicant performs statistical, comparative, and cause
and effect analysis on defects for a project. The applicant
performs analysis every other month over the past six months.
Award 20 credits. (award a max of one-fourth of the credits
due to duration / maturity (compare to a quarterly-based 2-year
“practice”; also see analysis definition
below)) |
 |
The applicant performs statistical, comparative, and cause
and effect analysis on defects for two projects over
the past 10 years. Award 240 credits. (Years 4 – 10 are
likely irrelevant for purposes of this certification.) |
 |
Over the past year, the applicant evidences the mentoring
of a peer about the organization’s measurement process.
The applicant meets with the peer every week for an hour. Award
52 credits. |
Example exclusion:
 |
Nothing included in other Categories. |
 |
The applicant purchased a tool for use in a measurement
program. Award no credits. Credits may be awarded if this was
part of a planning or some other activity on the matrix. |
 |
The applicant purchased a tool that the applicant
used during planning, designing, and implementing of a measurement
program. Award credits based on a relevant description of how
the tool was used in various stages of the measurement program. |
 |
The applicant developed a report on the status
of the metrics process and presented it to senior management.
Award no credits. Credits may be awarded if the activity included
an evaluation of the process with recommendations for improvement. |
Definitions
 |
Administer: to demonstrate
the benefit of the tool, process, or measure; providing guidance
for the program and its practitioners; a “help desk”
like service for the software measurements |
 |
Analyze: to utilize
collected data to meet business needs and requirements identified
during Planning, Design, Implementing and Sustaining a Software
Measurement Program. Activities include (but are not limited
to) statistical analysis, comparative trending, root cause analysis,
cause and effect analysis and other tasks to assist with ever
changing user and management questions and expectations. This
activity is performed for two years on a quarterly basis, or
an equivalent level of activity (monthly for one year). |
 |
Design: to define software
measurement architecture, database, access controls, data integration,
and “drill down” capability, as well as the tools,
techniques, processes and/or procedures to optimize value based
on a software measurement plan. |
 |
Evaluate: to assess
the state and value of an organization’s measurement program.
Making specific recommendations relevant to the improvement
of the measurement process. |
 |
Implement: to carry
out and fulfill the Software Measurement Plan. Actions include
at least three of the following: |
| |
~ |
identifying benefits and risks, |
| |
~ |
training staff through direct or contracted training programs,
(cannot be claimed for credit as part of TE) |
| |
~ |
defining and writing processes and/or procedures, |
| |
~ |
collecting data, |
| |
~ |
determining reliability and consistency of data, |
| |
~ |
reporting results, and |
| |
~ |
providing guidance for all levels of an organization. |
 |
(IT) Measurements:
(From Guidelines to Software Measurement Glossary, GSMG) assigning
relative value. Usually, in the improvement process, measures
gained from this activity are combined to form Metrics. |
 |
Measure: (from GSMG)
as a noun, a number that assigns relative value; as a verb,
to ascertain or appraise by comparing to a standard. |
 |
Mentor: (verb form)
to perform a documented process and establish a formal relationship
in which one party (mentee) is the primary recipient of measurement
knowledge and experience, often in place of or as a supplement
to other forms of training. |
 |
Metric: (from GSMG)
no single universal definition exists for metrics.
In the context of this document, a metric is a combination of
two or more measures or attributes. |
 |
Plan: to meet with
Executives and / or Sponsors to identify the steps and actions
necessary to establish a Software Measurement Program. Variables
here can include, but are not limited to: number of people involved,
knowledge and/or previous experience of the organization, organizational
issues, sponsor needs and requirements, time constraints, budget
constraints, physical proximity of staff, availability, reliability
and consistency of other measurement data. Planning also means
defining a strategy for deploying a software measurement program
such as pilots and incremental improvements, releases, or deployments. |
 |
Process: The steps,
procedures, forms, training, monitoring and reporting to ensure
measures are carried out in an objective, consistent, auditable
fashion. |
 |
Report: not the act
of generating reports; rather, to interface with middle and
upper level customers and IT Management. This activity is “listening,
selling and leading” through oral and written communications
that demonstrate comprehensive understanding of software metrics,
their uses and value added in Business Processes; in other words
“board room presence.” The full number of credits
is based on a two-year duration with a minimal of quarterly
reporting contact with Management, or an equivalent level of
activity (monthly for one year). |
 |
Senior Management:
Program or director level management as opposed to line management,
project management, or project leaders. Senior management is
not typically involved in the day-to-day operations of the organization. |
 |
Sustain: to analyze
and to act to evaluate and enhance the efficiency and effectiveness
of the Measurement Program. This includes maintaining and/or
increasing “momentum” in an “inherited”
Measurement Program. Key topics include flexibility, relevance,
alignment, sponsorship, communications and/or training. Moving
a Program to “critical mass,” where it survives
even after the departure of key individuals. |
 |
Tools: Automated software,
including Excel spreadsheets, for capturing, collecting and/or
reporting Measurement data such as (but not limited to) Function
Points, time, defects, cost, and customer satisfaction. |
Category Name: Education (ED)
(25%)
Description:
This category awards applicants for attending classes, conferences and completing other forms of
software measurement education using industry recognized prescribed
techniques or processes. Areas of education include, but are not
limited to project management, measurement, defects, estimation,
quality, etc. The credits below are based on a daily accrual in
½ day increments. A minimum of 40 credits must be attained
for this category to qualify for submission.
Education
(ED)
25% |
|
Attend |
Complete |
Obtain |
| IFPUG Conference |
16 |
|
|
| Eligible Non-IFPUG Conference |
8 |
|
|
| IFPUG Software Measurement Course |
|
16 |
|
| Eligible Non-IFPUG Software Measurement Course |
|
8 |
|
| Industry Certification |
|
|
50 |
Example inclusion:
 |
The applicant attends the Annual IFPUG Conference over 2
½ days. Award 40 credits. |
 |
The applicant attends an eligible non-IFPUG software measurement
conference which lasts four days. Award 32 credits. |
 |
The applicant attends an IFPUG-sponsored one day CFPS preparation
course. Award 16 credits. |
 |
The applicant attends a week long CMMI® course taught
by a Software Engineering Institute certified instructor. Award
40 credits. |
 |
The applicant completes a three-week course and project for
an organizational internal six sigma course which carries a
certification. (If training is conducted eight hours per day)
award the applicant 120 credits. If the course completion alone
is the sole requirement for certification, no additional credits
are awarded for the certification even if it is recognized by
industry. However, the completion of the project may be a candidate
for additional credit under WE. |
 |
The applicant completes a one-week internal course and associated
project on six sigma, which includes a certification. The certification
is recognized outside the hosting organization. Award 50 credits.
In this case, no additional credits are awarded for the training.
The completion of the project may be a candidate for additional
credit under WE. |
 |
The applicant completes a one-week internal course and associated
project on six sigma, which includes a certification. The certification
is not recognized external to the hosting institution. Award
40 credits. In this case, no additional credits are awarded
for the certification. The completion of the project may be
a candidate for additional credit under WE. |
 |
The applicant receives a certificate of completion for attending
a 2-day IT project management course with a focus on measurement
/ management by data. Award 32 credits. (The focus on measurement
/ management by data qualifies this class as a Software Measurement
Course.) |
 |
The applicant is re-certified as a Certified Software Test
Engineer. Award 50 credits. |
 |
The applicant is certified as a Project Management Professional.
Award 50 credits. Other industry certifications may include
certifications from PMI, SEI, IEEE, and QAI. Note that this
certification is the culmination of many courses for which the
applicant may receive additional credit, not the completion
of a single course that results in a certification (in which
case credit is awarded for either the course or the certification).
Any certification submission must include the certification
requirements. |
 |
The applicant receives a teaching certificate relevant to
software measurement. Award 50 points with stipulations described
above for the Project Management Professional. Any certification
submission must include the certification requirements. |
 |
The applicant obtains a teaching certification for Practical
Software Management (or for teaching the CMMI©, or as a
CMMI® lead assessor). Award 50 credits. Additional credits
are awarded for courses that are taken as part (or not as part)
of the certification. Note that the credits for Certification
are intended for those who complete a certification program
(series of courses, tests, demonstrated capabilities, not merely
a course). |
Example exclusion:
 |
Nothing included in other Categories. |
 |
The applicant attends a one-hour non-IFPUG presentation on
measurement. Award no credits. (Does not meet the ½ day
accrual test.) |
 |
The applicant is in the process of receiving a Project Management
Professional certification. Award no credits. |
 |
The applicant attends, but was unable to complete, a 2-day
Software measurement course. Award no credits for completion.
Applicant could submit for credit as attending an “Eligible
non-IFPUG Presentation and Training.” |
Definitions
 |
Attend: Be present at a qualifying
event. |
 |
Complete: Finish, with evidence
of completion, a qualifying event. |
 |
Obtain: To be awarded (or re-awarded)
an industry-recognized certification. |
Category Name: Professional Participation
/ Contribution to the Software Measurement Industry (PP) (15%)
Description:
This category awards applicants for participating
and contributing to the Software measurement industry. The credits
below are based on a daily accrual in ½ day increments. A
minimum of 40 credits must be attained for this category to qualify
for submission.
| Professional
Participation (PP) 15% |
|
Attend / Serve |
| Software Measurement Related Group Meetings – IFPUG |
16 |
| Software Measurement Related Group Meetings – Non-IFPUG |
8 |
Example inclusion:
 |
The applicant attends a local IFPUG chapter meeting once a
quarter for two hours. Attending four meetings in one year,
the applicant is awarded 16 credits (on an equivalency basis). |
 |
The applicant serves on or in behalf of an IFPUG committee
and attends meetings once a year for two full days. Award 32
credits. In addition, the applicant participates in 10 one-hour
long teleconferences during the reporting period for the same
committee. Award 16 credits, which are treated as a one-day
equivalent. |
 |
The applicant attends one one-hour SPIN (Software Process
Improvement Network) meeting. Award 0 credits. However, if the
applicant attends four one-hour meetings over the application
period, award 4 credits on a ½ day equivalency basis. |
 |
The applicant serves on an IFPUG committee. The documented
(and verified by a letter of reference) application indicates
10 days of work related to coordinating, writing, editing, and
reviewing IFPUG materials (books and exams). Award 160 credits.
No credit may be claimed for writing as part of the MP category. |
Example exclusion:
 |
Nothing included in other Categories. |
 |
The applicant is appointed (or elected) “chair”
for a prestigious committee in a prominent industry standards
group (IEEE, ISO, etc.) The applicant is awarded no credits
for chairing but is still eligible for credits for attending
and serving. |
 |
The applicant attends a non-IFPUG software measurement related
meeting. The first hour of the meeting is a “social hour”,
the second hour is dinner and presentation, and the third hour
is a business meeting. Award 0 credits for attending the business
meeting. The two hours of presentation and business meeting
do not meet the criteria for a ½ day equivalent. |
 |
Same example as above, but the applicant attends two such
meetings during the eligible reporting period; award four credits. |
Definitions
 |
Attend: Be present at a qualifying
event. |
 |
Complete: Finish, with evidence
of completion, a qualifying event. |
 |
Serve: The act of providing goods
or services to a relevant professional organization. |
 |
Software Measurement Related Group Meetings
– IFPUG: IFPUG, local IFPUG chapters, organizations
affiliated with IFPUG |
 |
Software Measurement Related Group Meetings
– non-IFPUG: SEI, PMI, ISO, IEEE. (not intended
as an exhaustive list of qualifying groups)
|
Category Name: Software Measurement-Related
Publishing (MP) (10%)
Description:
This category awards applicants for published works
related to Software Measurement. Contributions include authoring
and co-authoring, reviewing, editing, and translating of relevant
written materials. A minimum of 40 credits must be attained for
this category to qualify for submission.
| Software
Measurement Related Publishing (MP) 10% |
|
Author / Co-Author |
Contributing Author |
Expert Review |
Expert Edit |
Translate |
| Book |
80 |
40 |
30 |
20 |
80 |
| Refereed Article |
40 |
|
20 |
10 |
20 |
| Non-Refereed Article |
20 |
|
|
|
20 |
| Software Measurement Exam |
20 |
20 |
20 |
20 |
40 |
Example inclusion:
 |
The applicant writes a chapter in the IT Measurement book
as a contributing author. Award 40 credits. |
 |
The applicant reviews and edits the IT Measurement book as
an expert review and editor. Award 30 credits. |
 |
The applicant writes with an associate, an article published
in CrossTalk (refereed). Award 40 credits. |
 |
The applicant writes an article for Government Computer News
(non-refereed). Award 20 credits. |
 |
An article authored by the applicant is published in another
publication. Updates and changes are made. Award up to ½
the credits of the original article. |
 |
The applicant translates the GSM into Korean. Award 80 credits. |
 |
The applicant co-translates the GSM into Portuguese. Award
40 credits. |
Example exclusion:
 |
Nothing included in other Categories. |
 |
An article is re-published without change of content. Award
no credits. |
 |
The applicant authors a column for the IFPUG newsletter. Award
no credits (but nice job!) |
 |
The applicant writes an article or book that references or
mentions IT measures, but is not the focus of the material.
Award no credits. |
 |
The applicant translates a non-software measurement-related
book or article into Italian (or any language). Award no credits.
|
Definitions
 |
Article: An original work created
by the author and is typically 1000 – 3000 words. May
be the equivalent of a chapter in a book and credited as such.
(See also Non-Refereed Article and Refereed Article.) |
 |
Author: The person who solely writes
an original piece of work. The author’s name appears alone
on the work. |
 |
Book: A copyrighted published piece
of work of substantial size (typically greater than 150 pages),
has an ISBN number and is registered with the Library of Congress. |
 |
Co-author: The person who with
another or others, writes an original piece of work. The authors’
names appear (usually on the front) of the work. |
 |
Contributing author: The person
who with others writes an original piece of work. The authors’
names appear on pieces of the work, not with the title of the
whole work itself. |
 |
Expert edit: The person who is
sought because of their knowledge and background in a topical
area, to make technical changes to an original piece of work.
|
 |
Expert review: The person who is
sought because of their knowledge and background in a topical
area, to make technical suggestions, or in some cases to reject,
to an original piece of work. |
 |
Non-Refereed Article: A published
article in a copyrighted media that does not undergo expert
review. (See also Article.) |
 |
Refereed Article: A published article
in a copyrighted media that undergoes expert review. (See also
Article.) |
 |
Software Measurement Exam: The
exam offered by IFPUG used for part of the Software Measurement
certification. |
 |
Translate: To transform the complete
contents of one document into a different language. |
Category Name: Teaching (TE) (10%)
Description:
This category awards applicants for software measurement
Teaching Activities. The credits below for Author / Co-Author and
Teach columns are based on a daily accrual in ½ day increments.
A minimum of 40 credits must be attained for this category to qualify
for submission.
| Teaching
(TE) 10% |
|
Author / Co-Author |
Teach |
Present (at IFPUG) |
Present (not at IFPUG) |
| Software Measurement Course |
8 |
24 |
|
|
| Software Measurement Poster |
|
|
5 |
|
| Software Measurement Presentation |
|
|
10 |
5 |
Example inclusion:
 |
The applicant authors or co-authors (original material or
upgrades to) a 40-hour Software Measurement Course. Award 40
credits. |
 |
The applicant authors or co-authors (original material or
upgrades to) a 10-hour Software Measurement Course. Award 8
credits for a 1-day equivalent course |
 |
The applicant teaches an 8-hour Software Measurement Course
as part of an IFPUG seminar. Award 24 credits. If the applicant
also authored the material, award 8 additional credits. |
 |
The applicant presents a measurement-related topic at IFPUG.
Award 10 credits, which includes preparation time. |
 |
The applicant presents a measurement-related topic at a non-IFPUG
conference. Award 5 credits, which includes preparation time. |
 |
The applicant presents a poster at IFPUG or Software Measurement
related forum. Award 5 credits, which includes preparation time. |
 |
The applicant teaches software measurement principles for
8 hours of a 36-hour college course. Award 24 credits. |
 |
The applicant authors the material taught for 8 hours of a
36-hour college course. Award 8 credits |
Example exclusion:
 |
Nothing included in other Categories. |
 |
The applicant obtains a teaching certification for the public
school system. Award no credits. |
 |
The applicant teaches a university course on software engineering
that contains no modules, exercises, or testing on measurements.
Award no credits. |
 |
The applicant creates and displays a poster at a non-IFPUG
event. Award no credits. |
Definitions
 |
Author: the person who solely writes
an original piece of work. The author’s name appears alone
on the work. |
 |
Co-author: the person who with
another or others, writes an original piece of work. The authors’
names appear (usually on the front) of the work. |
 |
Organization: a company, government
agency, or university, as examples. |
 |
Software Measurement Course: a
course that is designed and taught that has as its primary content
and focus, principles and application of software measurement.
Its duration is 40 hours for the purpose of crediting. |
 |
Software Measurement Poster: a
display that is presented at an software measurement (or closely
related) conference that is designed and presented and that
has as its primary content and focus, principles and application
of software measurement. |
 |
Software Measurement Presentation:
a presentation that is developed and presented at a software
measurement (or closely related) conference that has as its
primary content and focus, principles and application of software
measurement. |
|
|