I.T. Discussion Community!
-Collapse +Expand
Proj Man
Search Proj Man Group:

-Collapse +Expand Proj Man Store

Prestwood eMagazine

September Edition
Subscribe now! It's Free!
Enter your email:

   ► KBRole-Based T...PSDP & ProcessPSDP Develop...   Print This    All Groups  
Proj Man PSDP Development:
Proof of Concept (POC)
Posted 11 years ago on 5/12/2009
Take Away:

Guidelines for create proof of concepts (POCs).


The following is from the PSDP Overview document:

2.4 The Tough Stuff First

One of the reasons why projects end up taking longer than estimated and therefore costing more is because the tough stuff is left to the end or at least not accomplished first. Sometimes the development team takes too much time on the project 'fine tuning' unimportant or at least less important features. After the customer has prioritized the desired features, the development team should work on the highest priority items first focusing on the features that are more technically difficult for the team to implement.

2.4.1 Proof of Concept Method*

A proof of concept is a test of technology used to establish the truth. A proof of concept allows the developer to isolate a technology problem for testing. PSDP uses them at key points of the software development process. Proofs of concepts are particularly important when working with new technology or extreme business rules. For example, if the software must communicate to LED signs through a particular piece of hardware over the Internet, PSDP recommends the development team perform a proof of concept for that aspect of the software as soon as possible.

*Proof of Concept Method is explained in more detail in the PSDP Development document.


  • Keep it simple.

  • Keep it independent of your project.

  • For database examples, use default databases. Whenever possible, use the default databases that come with the tools you're using.

Check Into SourceSafe

Because proofs are independent of your project and reusable by other developers, check them into SourceSafe. For example, the following are guidelines we use at Prestwood:

Create a subproject for each proof with the following naming convention:

ProductVersionID ProofIdentifier

For example:

CS08 Outlook Calentdar Insert
P8 ExitWin API Call
D7 TrayApp

Sample ProductVersionID Examples:

P8 = Paradox 8
P9 = Paradox 9
D6 = Delphi 6
D8 = Delphi 8
VB6 = Visual Basic 6
VB7 = Visual Basic.Net
CS08 = Visual Studio 2008, C#

The full paths in SourceSafe would be:

\\ClientsOther\Proofs\P8 ExitWin API Call
\\ClientsOther\Proofs\D7 TrayApp

ONLY check in completed, clean, and simple proofs!


Share a thought or comment...
Write a Comment...
Sign in...

If you are a member, Sign In. Or, you can Create a Free account now.

Anonymous Post (text-only, no HTML):

Enter your name and security key.

Your Name:
Security key = P1304A1
Enter key:
KB Post Contributed By Mike Prestwood:

Mike Prestwood is a drummer, an author, and creator of the PrestwoodBoards online community. He is the President & CEO of Prestwood IT Solutions. Prestwood IT provides Coding, Website, and Computer Tech services. Mike has authored 6 computer books and over 1,200 articles. As a drummer, he maintains play-drums.com and has authored 3 drum books. If you have a project you wish to discuss with Mike, you can send him a private message through his PrestwoodBoards home page or call him 9AM to 4PM PST at 916-726-5675 x205.

Visit Profile

 KB Article #101994 Counter
Since 5/12/2009

Follow PrestwoodBoards on: 

©1995-2020 PrestwoodBoards  [Security & Privacy]
Professional IT Services: Coding | Websites | Computer Tech