DOT NET Interview Questions - DotNetSpider

Second very important point to remember is normally all diagrams are not implemented
in project , but some basic diagrams are important to have in order that project is readable.
When we talk about project’s every project have phases example (Requirement’s phase,
design phase, coding phase etc etc).As every phase of the software cycle proceeds these
diagrams come in picture. Some diagrams span across multiple phases.
Note: - If you want to have a detail about software life cycle look out for chapter “Project
Management”.
Normally following are different basic phases:-
Requirement phase (Use Case Diagrams , Activity diagrams)
Requirement phase is the phase where you normally gather requirement and Use Cases
are the best things to make explanation of the system. In requirement phase you can
further make complicated Use Cases more simple and easy to understand by using activity
diagrams, but I do not see it as must in every project. If the Use cases are really complicated
go for a Activity diagram. Example CRUD (creates, read, update and delete) operation
use cases have no significance for making activity diagrams. So in short the outcome
UML documents from requirement phase will be Use Case and Activity diagram documents
(Activity diagram documents will only be there if there are complicated Use Cases to be
simplified).
Just a small Twist: - Do I need all UML diagrams in a project?
Note: - This question is specially asked to know have you actually used UML. I have seen
many guys trying to give some jack of all answer’s saying “YES”. Beware it’s a trap.
Not all diagrams are needed in project example: - Activity diagrams will only be needed
when you want some simplified look of a complicated use case.
Design phase (Class diagrams , object diagrams , Component diagrams ,
Collaboration diagrams , Deployment diagrams, Sequence diagrams)
Design phase is the phase where you design your technical architecture of your project.
Now again in this you do not use all UML documents of a project.
But the next document after the Use Case document will be the Component diagram.
Component diagrams form a high level classification of the system. So after “Use Cases”
just try to come out with a high level classification / grouping of related functionalities.
220