Technical Structure Definition
This technique can be useful in defining scope where the project is focused on infrastructure. It can also be useful in a situation where an existing system is being modified. The output can be either a table, or a diagram. A table might just list the components to be modified and the modification. The structure diagram might identify the whole system and highlight which components are being modified and how they are being modified. It may also be appropriate to indicate the purpose of each component, however it will probably be vague at this stage of development.
The ‘outputs HTML’ module takes information retrieved from the database and inserts it into an .asp document for output to the server. It also updates a transaction log with the database information and time of the output. If an error occurs in retrieving data from the database, an error log is updated and an error page sent to the server.
Example Technical Structure Table
|Subsystem1||Handles all customer processing and interfaces to CMS (Customer Management System).|
|Subsystem2||Carries out inquiries on billing systems (2) and combines data into common format. Sorts data by date of payment.|
Previous article: Defining the Scope in IT Projects – Part V – Defining the Data
Project Perfect is a project management software and project infrastructure consulting organisation based in Sydney Australia. Their focus is to provide creative yet pragmatic solutions to Project Management issues as well as to set up the infrastructure an organisation requires to successfully manage projects.
Project Perfect sell “Project Administrator” software, which is a tool to assist organisations better manage project risks, issues, budgets, scope, documentation planning and scheduling. They also created a technique for gathering requirements called “Method H”, and sell software to support the technique. For more information on Project tools or Project Management visit www.projectperfect.com.au.