INTERVIEW QUESTION:

In which document do you include the Class Diagram (business requirements, functional requirements, software specification document)?


The easy answer is “It depends!”

Just like any other diagram, the Class Diagram is just a tool at the disposal of the analyst. In the absence of a set process, it is at the analyst’s discretion to determine when to use a class diagram. Therefore, in which analysis artifact/document a class diagram should be included depends on its use.

But first, let’s determine what a Class Diagram can do for you by looking at some of its characteristics:

Therefore, if the analyst uses the Class Diagram to depict the key nouns found in the lingo of the business users (aka the business domain) and the relationships among those things, then this class diagram would represent a domain model and would probably belong in one of the earlier artifacts of the project such as the Business Requirements Document (BRD).

On the other hand, if the Class Diagram is used to explain what C# classes will be used to realize the functional requirements and the types of data attributes which describe those classes, then this diagram would be considered a design artifact and would probably belong in the System Specification/Technical Specification document.

--
Chris Adams
LinkedIn Profile


posted @ Tuesday, May 6, 2008 11:13 AM by sonavi