ARCHIVED - Estimate Software Product Size - Basic Procedure

• Previous Page
• Table of Contents
• Next Page

This page has been archived.

1. Introduction

1.1 Purpose

This procedure is an activity in the Project Planning Process (PPTO-PS-002). It uses the requirements to calculate a functional size measure which is converted to source lines of code (KSLOC). The size estimate is input into other activities in the Project Planning Process, namely, Estimate Project Resources/Schedule Basic Procedure.

1.2 Scope

This document is applicable to any Information Management/Information Technology (IM/IT) project that is delivering software.

Ensure that all assumptions, constraints and rationale (i.e. decisions) are documented in the Project Plan.

1.3 Roles

Everyone in the organisation has a role to perform in this procedure.

Everyone in the organisation has a role to perform in these processes.

Role	Description/Responsibilities
Project Leader (PL)	This is the person appointed by the sponsoring department to be accountable for all external and internal aspects of a capital project. http://www.tbs-sct.gc.ca/pubs_pol/dcgpubs/TBM_122/abkglos-eng.asp
Project Manager (PM)	This is a person formally appointed to manage a project with specific accountability for achieving defined project objectives within allocated resources. A project manager has access to, and a formally defined relationship with, the project leader to which the specific project has been assigned.  http://www.tbs-sct.gc.ca/ pubs_pol/dcgpubs/TBM_122/abkglos-eng.asp
Project Team Member (PTM)	Software engineer or writer assigned to a project Responsible for completing project tasks, providing input to plans, and providing status
Project Management Office (PMO)	This is a distinct and temporary organisational unit led by the project manager tasked to administer a project. It consists of assigned full or part-time members of the sponsoring department and, when appropriate, representatives of participating departments working together in accordance with any interdepartmental agreements or memorandums of understanding.  http://www.tbs-sct.gc.ca/ pubs_pol/dcgpubs/TBM_122/abkglos-eng.asp
Quality Assurance (QA )	Responsible for support of quality assurance activities.
Configuration Management (CM)	Responsible for support of configuration management activities.

1.4 Definitions and Acronyms

Algorithm	(1) A finite set of well-defined rules for the solution of a problem in a finite number of steps; for example, a complete specification of a sequence of arithmetic operations for evaluating sine x to a given precision. [IEEE-STD-610] (2) Any sequence of operations for performing a specific task. [IEEE-STD-610] (3) An algorithm is defined as the set of rules which must be completely expressed in order to solve a significant computational problem [Capers Jones]
Inputs	Inputs are screens or forms through which human users of an application or other programs add new data or update existing data. If an input screen is too large for a single normal display and flows over onto a second screen, the set counts as 1 input. Inputs that require unique processing are what should be considered. [Capers Jones]
Inquiries	Inquiries are screens which allow users to interrogate a application and ask for assistance or information, such as HELP screens. [Capers Jones]
Interface	Interfaces are files shared with other applications such as incoming or outgoing tape files, shared databases and parameter lists. [Capers Jones]
Master files	Data files are logical collections of records which the application modifies or updates. [Capers Jones]
Outputs	An output results in the generation of derived data. [Garmus, Herron] Outputs are screens or reports, which the application produces for human use of for other programs. Note that outputs requiring separate processing are the units to count: In a payroll application, an output that created 100 cheques would still count as 1 output [Capers Jones]

Refer to Enhanced Management Framework Lexicon.

Refer to Enhanced Management Framework Acronyms.

Refer to Enhanced Management Framework Web Links.

1.5 References

1.5.1 Traceability

This procedure was designed to satisfy the SEI Software Capability Maturity goals for Level 2 Key Practice: Software Project Planning.

1.5.2 Policies

Treasury Board Secretariat Policies:

• Capital Plans - Glossary
• Management of Major Crown Projects
• Procurement Review Policy
• Project Management
• Project Approval

The policies above are located at the following URL:

http://www.tbs-sct.gc.ca/pubs_pol/dcgpubs/TBM_122/siglist-eng.asp

1.5.3 Standards

Annex A – Flowcharting Symbols

1.5.4 Processes

PPTO-PS-002 Project Planning Process

PPTO-PS-003 Project Tracking and Oversight Process

PEER-PS-001 Peer Review Process

1.5.5 Procedures

PPTO-PD-002 Estimate Project Resources/Schedule Basic Procedure

1.5.6 Guidelines

Not applicable at this time.

1.5.7 Templates

PPTO-TM-001 Process/Procedure Template

PPTO-TM-002 Project Plan Template

PPTO-TM-003 Project Estimates Template

1.5.8 Checklists

PPTO-CK-001 Project Management Checklist

• Previous Page
• Table of Contents
• Next Page