Table of Contents
This part addresses the work that the document type design team will perform: designing the requirements for the DTD's markup model.
The complete list of steps for analysis and modeling is as follows. Steps 1 through 3 make up the analysis work, discussed in Chapter 4, Document Type Needs Analysis, and steps 4 through 10 make up the modeling work, discussed in Chapter 5, Document Type Modeling and Specification.
Identify potential needs, defining them as thoroughly as possible.
Classify them into logical categories, thereby taking their definition a step further.
Validate the needs against other analyses of similar data.
Select the needs that the markup model should ultimately address.
Build the model for the document hierarchy.
Build the models for the information units.
Build the models for the data-level elements.
Populate the remaining branches of the model.
Make connections within the model and from the model to the outside world.
Validate that the model is complete and that it has been informed by similar models already developed.
Chapter 6, Modeling Considerations offers advice on modeling techniques that the design team can apply, and Chapter 7, Design Under Special Constraints describes special circumstances under which the usual steps of analysis and modeling might need to change.
The analysis and modeling phases of DTD development bear some resemblance to the phases of software and systems development. The analysis work generates functional requirements, and the modeling work generates a partial design specification, which is recorded in a “document analysis report.” The DTD implementor must later design and document choices made in the final markup model and the DTD's architecture, which completes the final design specification.
