[Date]
System Request
Project Name:
Project Sponsor:
Name:
Department:
Organization:
Phone:
E-mail:
Business Need:
Functionality:
Expected Value:
Tangible:
Intangible:
Special Issues or Constraints:
Feasibility Analysis
Technical Feasibility: Can We Build It?
 Familiarity with Application

Familiarity with Technology

Project Size
Economic Feasibility: Should We Build It?
 Development Costs

Annual Operating Costs

Annual Benefits (Cost Savings and Revenues)

Intangible Costs and Benefits
Organizational Feasibility: If We Build It, Will They Come?
 Project Champion(s)

Senior Management

Users

Other Stakeholders
Function Point Estimation Worksheet
Description
Inputs
Outputs
Queries
Files
Program Interfaces
Complexity
Medium
___ x 4
___ x 5
___ x 4
___ x 10
___ x 7
Low
___ x 3
___ x 4
___ x 3
___ x 7
___ x 5
High
___ x 6
___ x 7
___ x 6
___ x 15
___ x 10
Total
___
___
___
___
___
Total Unadjusted Function Points (TUFP): _______________
(0=no effect on processing complexity; 5=great effect on processing complexity)
Data communications
Heavily use configuration
Transaction rate
End-user efficiency
Complex processing
Installation ease
Multiple sites
Performance
Distributed functions
On-line data entry
On-line update
Reusability
Operational ease
Extensibility
0-5
___
___
___
___
___
___
___
___
___
___
___
___
___
___
Processing Complexity (PC): ______
Adjusted Processing Complexity (PCA) = 0.65 + (0.01 * ____________)
Total Adjusted Function Points (TAFP):
___________ * ____________ =
Workplan
Step
Planning Phase
Analysis Phase
Examine Current System
Identify Improvements
Develop Concept for New
System
Design Phase
Develop Factored Models
Design System Architecture
Design Infrastructure
Design Interface
Design Data Storage
Program Design
Implementation Phase
Construction
Implementation
Deliverables
Behavioral Models
Structural Models
Ideas for system
Behavioral Models
Structural Models
Factored Models
System Architecture
Infrastructure Design
Windows Navigation Diagram
Interface Standards
Interface Design
Use Scenarios
Real Use Cases
Data Storage Design
Restructured Models
Class Design
Contracts
Method Design
Test Plan
Documentation
Completed System
Implementation Plan
Change Management Plan
Training Plan
Implemented System
Estimated
Hours
Actual
Hours
Assigned to
Analysis Plan
Step
Understand the AsIs System
Identify
Improvements
Develop a
To-Be System
Concept
Technique
Specific Activities
Gather
Information

Develop
Behavioral Model

Develop
Structural Model

Problem Analysis

Root Cause
Analysis
Duration Analysis
Activity-based
Costing
Informal
Benchmarking
Formal
Benchmarking
Outcome Analysis
Breaking
Assumptions
Technology
Analysis
Activity
Elimination
Proxy
Benchmarking
Process
Simplification

Gather
Information
Develop
Behavioral Model
Develop
Structural Model













Interview Report
Interview Notes Approved By: _________________________
Person Interviewed:
Interviewer:
Date:
Primary Purpose:
Summary of Interview:
Open Items:
Detailed Notes:
Use Case Description
Use Case Name:
Primary Actor:
Stakeholders and Interests:
Brief Description:
Trigger:
Type:
Relationships:
Association:
Include:
Extend:
Generalization:
Normal Flow of Events:
1.
SubFlows:
1.
.
Alternate/Exceptional Flows:
ID:
Use Case Type:
Importance Level:
CRC Card
Front:
Class Name:
ID:
Description: an individual that needs to receive or has received medical attention
Responsibilities
_____________________________
_____________________________
_____________________________
_____________________________
_____________________________
_____________________________
_____________________________
_____________________________
_____________________________
_____________________________
Back:
Attributes:
_____________________________
_____________________________
_____________________________
_____________________________
_____________________________
_____________________________
Type:
Associated Use Cases:
Collaborators
_____________________________
_____________________________
_____________________________
_____________________________
_____________________________
_____________________________
_____________________________
_____________________________
_____________________________
_____________________________
_____________________________
_____________________________
_____________________________
_____________________________
_____________________________
_____________________________
Relationships:
Generalization (a-kind-of):
__________________________________________
_______________________________________________________________________
Aggregation (has-parts): _________________________________________________
_______________________________________________________________________
Other Associations:
__________________________________________
_______________________________________________________________________
Sample Contract Format
Method Name:
Clients (Consumers):
Associated Use Cases:
Description of Responsibilities:
Arguments Received:
Type of Value Returned:
Pre-Conditions::
Post-Conditions:
Class Name:
ID:
Method Specification Form
Method Name:
Class Name:
ID:
Contract ID:
Programmer:
Date Due:
Programming Language:
 Visual Basic
Triggers/Events:
 Smalltalk
Arguments Received:
Data Type:
Messages Sent & Arguments Passed:
ClassName.MethodName:
Argument Returned:
Data Type:
Algorithm Specification:
Misc.Notes:
 C++
 Java
Notes:
Data Type:
Notes:
Notes:
Class Test Plan
Class Test Plan
Page ___ of ___
Class Name: ________________ Version Number: _____ CRC Card ID: __________
Tester: _________________
Date Designed : ________
Class Objective:
Associated Contract IDs: __________________________________________
Associated Use Case IDs: __________________________________________
Associated Superclass(es): _________________________________________
Testing Objectives:
Walkthrough Test Requirements:
Invariant-Based Test Requirements:
State-Based Test Requirements:
Contract-Based Test Requirements:
Date Conducted : ________
Class Invariant Test Specification
Class Invariant Test Specification
Page ___ of ___
Class Name: ________________ Version Number: _____ CRC Card ID: __________
Tester: _________________
Date Designed : ________
Date Conducted : ________
Testing Objectives:
Test Cases
Invariant
Description
Original Event
Attribute
Value
New
Attribute
Value
Expected
Result
Attribute Name:
1) ____________ _________
_______ ________
________
____
2) ____________ _________
_______ ________
________
____
3) ____________ _________
_______ ________
________
____
Attribute Name:
1) ____________ _________
_______ ________
________
____
2) ____________ _________
_______ ________
________
____
3) ____________ _________
_______ ________
________
____
Attribute Name:
1) ____________ _________
_______ ________
________
____
2) ____________ _________
_______ ________
________
____
3) ____________ _________
_______ ________
________
____
Result
P/F