Write your Technical Specification Right

Posted on August 25, 2012 by doctonic

A technical specification describes how the system will be implemented internally. It covers non-functional aspects of the system such as the hardware and software architecture, interfaces to other systems, data base, programming language used, etc. A technical specification document explains the following items. Hardware specification Hardware configurations for the web server, application server and work Read more about Write your Technical Specification Right[…]

IT Request for Change Documentation

Posted on August 21, 2012August 21, 2012 by doctonic

When there is a need to alter a software system, the details of the modification required are documented. This documentation is initiated by the entity which requests the change. The entity which has to implement the change in the software also makes contributions to the Change Request (CR) document. The CR document just specifies the Read more about IT Request for Change Documentation[…]

Communication Plan Template

Posted on August 11, 2012January 4, 2017 by doctonic

Purpose:This Communication Plan Template details how communication will be managed. It will include all planned & periodic communications, scheduled written & oral communications, responses to ad-hoc requests for information, frequency of communications, and the responsible person(s) for providing the information.

How to write a powerful Letter of Intent

Posted on August 9, 2012August 25, 2015 by doctonic

A letter of intent expresses the writer’s interest to bid on a project, or to make a business proposition. It is written in response to a Request For Proposal (RFP). It indicates the sender’s intention to get into an agreement with the receiver to execute specific tasks or render service. Note: This article relates to Read more about How to write a powerful Letter of Intent[…]

Test Case Spreadsheet

Posted on August 7, 2012January 4, 2017 by doctonic

Purpose: This excel spreadsheet serves as a tool to monitor and manage both unit and system testing. This Test Case Spreadsheet / Template could be applied to a variety of applications and is particularly useful when used in conjunction with a functional requirements template and a test plan template.

Strategic Analysis Tools

Posted on August 7, 2012August 7, 2012 by doctonic

Strategic Analysis is the process of collecting data about an organization and its operating environment then analyzing it in order to come up with a strategy to achieve optimal utilization of resources and thereby improve business efficiency. The analysis may be done in order to address specific issues of the organization or to improve business Read more about Strategic Analysis Tools[…]

Project Risk Assessment Reporting

Posted on August 7, 2012 by doctonic

Risk assessment, monitoring and reporting are done to identify risks in executing a project and to plan for contingencies and mitigate unexpected road blocks during the project life cycle. Based on the risk assessment report, a risk management process is put in place. In order to prepare a Risk Assessment Report, the following details are Read more about Project Risk Assessment Reporting[…]

Use Cases and Business Cases

Posted on August 5, 2012January 2, 2018 by doctonic

Use Case A Use Case describes the interaction between a user and the system. The user is termed as “Actor”. The functionality or interaction scenario is the Use Case. The Actor may be a human or an external hardware / software system. The user may assume different roles while interacting with the system to achieve Read more about Use Cases and Business Cases[…]

System Standard Operating Procedure (SOP) Documentation

Posted on August 5, 2012August 5, 2012 by doctonic

After the coding and testing phases are finished, specific documentation is needed on how to operate the system. This documentation is important because the developers who write the code will be assigned to new projects after turnover and implementation of the system. Consider the following situations where System (Standard Operating) Procedure Documentation is needed. Mainframe Read more about System Standard Operating Procedure (SOP) Documentation[…]

What is a Requirements Traceability Matrix

Posted on August 5, 2012August 5, 2012 by doctonic

[raw] Software development projects have multiple phases: Feasibility, Requirements, Design, Coding, Test, Implementation, and Maintenance. All projects, whether large or small, generate documentation in the form of business requirements, design documents, test plans, and system operating instructions. In small projects the documents can be minimal and easy to manage. But in a large project the Read more about What is a Requirements Traceability Matrix[…]