Information Technology (IT) Management Forms

292 views
182 views

Published on

This document contains a list of 16 IT Management Forms that can be used by IT managers, development and technical staff as well as other professionals in organizing, managing, running and improving IT Systems and Operations for any type of company or organization.

For details on how these fit into IT Operations, see my book:
‘IT Strategic & Operational Controls’
PUBLISHER: www.itgovernance.co.uk


Published in: Business, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
292
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
11
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Information Technology (IT) Management Forms

  1. 1. Information Technology (IT) Strategic & Operational Controls Copyright: John Kyriazoglou 1 INFORMATION TECHNOLOGY (IT) MANAGEMENT FORMS By John Kyriazoglou August 2013 This document contains a list of 16 IT Management Forms that can be used by IT managers, development and technical staff as well as other professionals in organizing, managing, running and improving IT Systems and Operations for any type of company or organization. For details on how these fit into IT Operations, see my book: ‘IT Strategic & Operational Controls’ PUBLISHER: www.itgovernance.co.uk
  2. 2. Information Technology (IT) Strategic & Operational Controls Copyright: John Kyriazoglou 2 List of IT Management Forms IT Form 01: INFORMATION ASSET REGISTER - EXAMPLE IT Form 02: TEST CASE FORM – EXAMPLE IT Form 03: TEST SCENARIO FORM - EXAMPLE IT Form 04: TEST CASE EXECUTION LOG FORM – EXAMPLE IT Form 05: ERROR LOG FORM – EXAMPLE IT Form 06: IT ACTIVITIES JOURNAL FORM - EXAMPLE IT Form 07: IT VISITORS LOG FORM - EXAMPLE IT Form 08: IT SECURITY INCIDENTS LOG FORM - EXAMPLE IT Form 09: IT PROBLEMS LOG FORM - EXAMPLE IT Form 10: SOFTWARE SUPPLIERS MINOR CHANGES FORM - EXAMPLE IT Form 11: SYSTEMS PERSONNEL CHANGES FORM – EXAMPLE IT Form 12: SYSTEMS SOFTWARE MAJOR CHANGES FORM – EXAMPLE IT Form 13: TEST CASE FORM – EXAMPLE IT Form 14: TEST SCENARIO FORM – EXAMPLE IT Form 15: TEST CASE EXECUTION LOG FORM - EXAMPLE IT Form 16: ERROR LOG FORM – EXAMPLE
  3. 3. Information Technology (IT) Strategic & Operational Controls Copyright: John Kyriazoglou 3 Information Entity Field Names and contents Payroll <File name>, <Format: Word, Excel, Hard copy, data base, etc.>, <application system mainting this information>, <File location>, <Officer responsible for the quality of this information>, <data classification category: secret, public, etc., according to corporate policy> Accounting <File name>, <Format: Word, Excel, Hard copy, data base, etc.>, <application system mainting this information>, <File location>, <Officer responsible for the quality of this information>, <data classification category: secret, public, etc., according to corporate policy> Xxx <File name>, <Format: Word, Excel, Hard copy, data base, etc.>, <application system mainting this information>, <File location>, <Officer responsible for the quality of this information>, <data classification category: secret, public, etc., according to corporate policy> IT Form 01: INFORMATION ASSET REGISTER – EXAMPLE SYSTEM NAME: < ………………………………….….…> Test Case Number: Tester Name: Hardware required: Software required: Other Test Case Dependency: Brief Description of the Test Case: Inputs required: Outputs expected: Note: For each test case the above should be recorded IT Form 02: TEST CASE FORM – EXAMPLE
  4. 4. Information Technology (IT) Strategic & Operational Controls Copyright: John Kyriazoglou 4 SYSTEM NAME: < ………………………………….….…> Test Scenario Title: Project Name: Work Package: Unit: Tester: Date: Number: Test Cases: Set Up Instructions: Start Instructions: Proceed Instructions: Performance Measures: Stop Instructions: Note: For each test case scenario the above should be recorded Form 03: TEST SCENARIO FORM - EXAMPLE SYSTEM NAME: < ………………………………….….…> Test Case Number Project Tester Date Pass/Fail Actual Results (For Fail) Error Log Number (For Fail) Approval Note: For each test case executed the above should be recorded Form 04: TEST CASE EXECUTION LOG FORM – EXAMPLE
  5. 5. Information Technology (IT) Strategic & Operational Controls Copyright: John Kyriazoglou 5 SYSTEM NAME: < ………………………………….….…> Error No Description Severity Note: For each test case executed the above should be recorded Form 05: ERROR LOG FORM – EXAMPLE <Organization>: <page no>: <IT Department Location>: The following data (as described in the next table) should be recorded on a standard form designed by the organization Seq. No. Data to be recorded 1 <date>, <time>, <procedure>, <transaction name>, <work done>, <success: yes/no>, <comments>, <name of staff>, <IT system involved> 2 <date>, <time>, <procedure>, <transaction name>, <work done>, <success: yes/no>, <comments>, <name of staff>, <IT system involved> … N <date>, <time>, <procedure>, <transaction name>, <work done>, <success: yes/no>, <comments>, <name of staff>, <IT system involved> Form 06: IT ACTIVITIES JOURNAL FORM
  6. 6. Information Technology (IT) Strategic & Operational Controls Copyright: John Kyriazoglou 6 <Organization>: <page no>: <IT Department Location>: The following data (as described in the next table) should be recorded on a standard form designed by the organization Seq. No. Data to be recorded 1 <date of entry>, <time of entry>, <date of exit>, <time of exit>, <location visited>, <visitor’s particulars (name, identification no., etc.), <escort’s name and phone no.>, <visitor’s signature>, <escort’s signature> 2 <date of entry>, <time of entry>, <date of exit>, <time of exit>, <location visited>, <visitor’s particulars (name, identification no., etc.), <escort’s name and phone no.>, <visitor’s signature>, <escort’s signature> … ……………………………. N <date of entry>, <time of entry>, <date of exit>, <time of exit>, <location visited>, <visitor’s particulars (name, identification no., etc.), <escort’s name and phone no.>, <visitor’s signature>, <escort’s signature> Form 07: IT VISITORS LOG FORM
  7. 7. Information Technology (IT) Strategic & Operational Controls Copyright: John Kyriazoglou 7 <Organization>: <page no>: <IT Department Location>: The following data (as described in the next table) should be recorded on a standard form designed by the organization Seq. No. Data to be recorded 1 <date reported>, <time reported>, <name of person who reported the incident>, <incident particulars (description, what location or system affected, etc.), <person’s name responsible to resolve incident>, <actions taken>, <date and time incident successfully resolved> 2 <date reported>, <time reported>, <name of person who reported the incident>, <incident particulars (description, what location or system affected, etc.), <person’s name responsible to resolve incident>, <actions taken>, <date and time incident successfully resolved> N ……………………….. Form 08: IT SECURITY INCIDENTS LOG FORM
  8. 8. Information Technology (IT) Strategic & Operational Controls Copyright: John Kyriazoglou 8 <Organization>: <page no>: <IT Building Location>: The following data (as described in the next table) should be recorded on a standard form designed by the organization Seq. No. Data to be recorded 1 <date and time reported>, <name of person who reported the problem>, <problem particulars (description, what location or system affected, etc.), <person’s name responsible to resolve problem>, <actions taken>, <date and time problem successfully resolved>, <date and time resolution of problem reported to affected person/function, etc.> 2 <date and time reported>, <name of person who reported the problem>, <problem particulars (description, what location or system affected, etc.), <person’s name responsible to resolve problem>, <actions taken>, <date and time problem successfully resolved>, <date and time resolution of problem reported to affected person/function, etc.> N ……………………….. Form 09: IT PROBLEMS LOG FORM
  9. 9. Information Technology (IT) Strategic & Operational Controls Copyright: John Kyriazoglou 9 NO. Data to be noted 1 Change No 2 Change Request Date 3 Change Requestor 4 Change Urgency 5 System or Application Affected 6 Description of Change 7 Requestor Signature 8 Impact of Change 9 Signature of IT Manager Form 10: SOFTWARE SUPPLIERS MINOR CHANGES FORM - EXAMPLE NO. Data to be noted 1 Change No 2 Change Request Date 3 Change Requestor 4 Change Urgency 5 System Software Affected 6 Description of Change 7 Requestor Signature 8 Impact of Change 9 Signature of IT Manager 10 Signature of Stakeholder Form 11: SYSTEMS PERSONNEL CHANGES FORM – EXAMPLE
  10. 10. Information Technology (IT) Strategic & Operational Controls Copyright: John Kyriazoglou 10 NO. Data to be noted 1 Change No 2 Change Request Date 3 Change Requestor 4 Change Urgency 5 System / Application Software Affected 6 Description of Change 7 Requestor Signature 8 Impact of Change 9 Signature of IT Manager 10 Signature of Stakeholder 11 Signature of DBA 12 Signature of Security Manager Form 12: SYSTEMS SOFTWARE MAJOR CHANGES FORM – EXAMPLE
  11. 11. Information Technology (IT) Strategic & Operational Controls Copyright: John Kyriazoglou 11 SYSTEM NAME: < ………………………………….….…> Test Case Number Tester Name Hardware required Software required Other Test Case Dependency Brief Description of the Test Case Inputs required Outputs expected Note: For each test case the above should be recorded Form 13: TEST CASE FORM – EXAMPLE
  12. 12. Information Technology (IT) Strategic & Operational Controls Copyright: John Kyriazoglou 12 SYSTEM NAME: < ………………………………….….…> Test Scenario Title Project Name Work Package Unit Tester Date Number Test Cases Set Up Instructions Start Instructions Proceed Instructions Performance Measures Stop Instructions Note: For each test case scenario the above should be recorded Form 14: TEST SCENARIO FORM – EXAMPLE
  13. 13. Information Technology (IT) Strategic & Operational Controls Copyright: John Kyriazoglou 13 SYSTEM NAME: < ………………………………….….…> Test Case Number Project Tester Date Pass/Fail Actual Results (For Fail) Error Log Number (For Fail) Approval Note: For each test case executed the above should be recorded Table 15: TEST CASE EXECUTION LOG FORM - EXAMPLE SYSTEM NAME: < ………………………………….….…> Error No Description Severity Note: For each test case executed the above should be recorded Table 16: ERROR LOG FORM – EXAMPLE

×