Develop an Information Architecture |
|
|
|
|
Written by Graham Stoney
|
|
Given the top-down nature of system engineering, it is possible early in the project to develop an information architecture defining the scope and purpose of every document that will eventually be produced, along with the level of maturity expected at each major project milestone.
This information architecture or family tree gives a road map to all the information generated by the project. People should not spend time writing documents which fulfil no purpose, nor should they simply start writing and see what pops out; the scope of each document should be defined ahead of time.
Concise, readable documentation should be an integral part of the development process, and not merely be a deliverable. Each document should fulfil a defined need rather than simply evolving on their own.
Excluding project management documents, there are 3 main classes of engineering documents: Requirement Specifications, Design Descriptions, and Verification Protocols. Pretty much everything falls into one of these classes.
|