PC developers are being called on to develop ever more complex systems, and in response the established tools for program design are now available on PC. "Clouds" is the colloquial name for the object diagrams that are central to UML. This book is a complete walk-through of the transition from design to development for programmers.
I am new to software project time estimation.
I have learned that people are using some techniques such as ‘Function point analysis’ , ‘Cocomo model’ etc.
Can you tell me the some of the latest and best techniques? Also would you please let me know some good tutorial links for these models so that I could go through them and understand?
I want to suggest a few time-consuming areas often ignored when breaking down strict requirements but always come into play during implementation. Especially be aware of these if you're contracting and every hour is your own. You'll be surprised at how often employers count these hours against development time because they are piecemeal tasks and expected in due course of the project - of course these things add up. I suggest allocating time for these - and explicitly outline them as such in your estimation process so there is no confusion:
These are truly parts of real-world software project estimation. There are more gotchas but this might help provide some direction about kinds of things to pragmatically consider outside an ideal or academic process. I think a lot of text books give sound advice; one book I fondly remember is Clouds to Code (for the sake of throwing out a link).
In my experience full-time employees don't necessarily have to be as concerned because organizations tend to absorb salaried time outside strict project timelines as a cost of doing business.