Where message types do not have an existing schema (or information model), or where the message content extends existing schema, the architect may want to begin the creation of new schema definitions created using the relevant example messages. While it may be useful to begin message schema creation at this point, most likely it will not complete until service-oriented design, as there are many considerations that can effect the design of a good message schema, including the use of namespaces, re-usability, modularity, etc.
Once the schema has been created, it should be validated against the relevant set of example messages defined in the business analysis phase.
Information model defined for each message schema.
Repo: Store information model. Identify dependencies between information models.
Input: Example messages.
Output: Information model.