DOT NET Interview Questions - DotNetSpider

This should be compulsory diagram as outcome of this document will form
“NAMESPACES” structure of .NET project.
Ok now once your high level grouping is done you can go ahead with class diagrams.
Especially from Use Case you get the “NOUNS” and “VERBS” which can form the class
name and the method name respectively. From my point of view class diagrams should
be compulsory in projects.
Object diagrams are not compulsory it depends on how complicated your project. Object
diagrams show’s the relation between instances of class at runtime. In short it captures
the state and relation of classes at any given moment of time. Example you have class
which creates objects of different classes, it’s like a factory. In class diagram you will only
show that it as a simple class with a method called as “CreateObject”.But in object
diagrams actually you will show the types of instances creates from that object.
Collaboration diagrams mainly depict interaction between object to depict a some purpose.
I find this diagram to be more useful than Object diagrams as they are addressed for some
purpose. Example “Login Process” which will use “Login object”, “User Object” etc to
fulfill the login purpose. So if you find the process very complicated go for this diagram.
I see as a thumb rule if there is a activity diagram which shows some serious complicated
scenarios I will like to go for this diagram inorder to simplify the explanation.
State chart diagram is again created if your project requires it. If your project has some
complicated start and end states to show then this diagram is most useful. Recently I was
making a call center project where the agent phone pickup and hang state has to be
depicted. So my first state was when agent picks up the phone and the final stage was
when agent hangs the phone, in between process was very complicated, which can only
be shown by using state chart diagrams.
Sequence diagrams are needed if some sequence is complicated. Do not confuse sequence
diagrams with Activity diagram, Activity diagram’s map to a Use Case while sequence
diagrams show object interaction in sequence.
Deployment diagrams are again not a compulsory requirement. It shows the hardware
and software deployment of your system. If you really have leisure in your project go for
it or if you want to make the client smile seeing some diagrams.
Implementation phase / Coding phase (Class diagrams for reverse
221