Project documentation and analysis is the most important part of any project. Without a proper analysis, any project takes more time to develop, is not robust, there's no way to find out if all the milestones have been met. trouble always awaits if a project starts without proper analysis. I have always had interest in analyzing the projects properly although have not been much interested in reading huge books. I want to read all the books about all the tech stuff but it is not humanly possible to read them, now i think no one takes time out to read out something especially when a person works, studies and does a lot of work at the same time.
ah... everyone has a different perspective of life, what can anyone say about anyones lifestyle or priorities!!!
This is an interesting article, would like people to read it out. The link describes what a UML 2 class diagram is in a very precise short and to the point manner.
Introduction to UML 2 Class Diagrams
I update this blog when i am in the development mode, most of the times when I am developing systems, and i find new things that I believe are interesting, I post them on this blog, this helps me a lot too for future references and when i repeat the things i've already done. Hope this helps others too.
Wednesday, October 12, 2005
Subscribe to:
Post Comments (Atom)
Blog Archive
-
▼
2005
(24)
-
▼
October
(10)
- How would you initialize the child class from the ...
- a great article on the inheritence in c#. This art...
- Have you ever wanted to strip all of the HTML tags...
- How to fix bugs in the Live / Production environme...
- Google Groups : microsoft.public.inetserver.iis
- A use case is a sequence of actions that provide a...
- Building Object Applications: Your Step-By-Step ...
- The Full-Lifecycle Object-Oriented Testing (FLOOT)...
- A fundamental concept of the Unified Modeling Lang...
- Project documentation and analysis is the most imp...
-
▼
October
(10)
No comments:
Post a Comment