1.0 Title: Project Note file
2.0 Purpose: To record in chronological order, and for each project resource person reading or modifying project artifacts what they read or modified or any comments or action items resulting from their efforts.
3.0 Recommended Usage:
4.0 Frequency:
5.0 Reference Documents:
6.0 Responsibility:
7.0 Ownership:
8.0 Level of Effort (costs)
9.0 Risks
10.0 CONTENTS:
10.1 filename:
This is the filename for the note file itslef - format: pm45n <label text> <wo#>
10.2 entry timestamp:
This is the date/timestamp for the note being made - it format should be: yy/mm/dd HH:mm
10.3 note:
This is the actual note entry and consists of text, hyper-links and whatever else the person keeping the log finds useful. It should be as compact and concise as possible. (While it may be convenient to use the notepad as a editing pad - large text entries are usually for a deliverable of some sort and should be moved to an appropriative location with a link back to the notes file.)
10.4 entry hash
Once a note has been saved the system should generate a hash for the entry and store it (somewhere) as an auditing tool to see if and when the entry log has been modified.
11.0 Metadata (Data Typing)
12.0 File Handling Policy
12.1 There will normally be individual logs for each resource person - however the "project log file" will be the amalgamation of all of the log files.
12.2 Because almost all files will be in electronic format the CDID itself must state how documents of this type must be handled by the information system.
12.3 Backup
Backup policies must be stated for time of retention
12.4 Privacy
PIPEDA (Canada), Sorbanes Oxley (USA) and equivalent privacy handling methods must be specified.
12.5 Security
The security level of the document must be identified and options noted.