• Introduction
• Requirement Management
• Software Modeling
• UML
• Design Pattern
• Software Architecture
• Risk Management
• Outsourcing

• Requirements are the foundation of any project, yet the number of project failures attributed to inadequate requirements development and management is staggering.
• As projects progress, "scope creep" often occurs due to the inability to manage constant change.
• Customers’ needs and the project sponsor’s needs frequently seem to be at odds. How does the project manager cope with all the turmoil?
• A critical part of any project is the requirements management. If you are unsure about what is going to be delivered how will you know when you get there?
• A company with poor requirements practices is just asking for over-budget costs and regular failure,
• Good user requirements lead to better estimates, improved customer satisfaction, reduced cost and a shorter duration
• Are bugs in your software costing you money? Did you know that most defects originate in the requirements phase? They do! If you don’t do requirements right, this one part of your software development effort can cost you the most in time, money, and customer dissatisfaction
• Requirements engineering carries on for the whole life of the system. It focuses on ensuring that “the voice of the customer” is based at all points in the development process from the initial conception of the system, through design, testing and changes introduced for maintenance and system evolution

The Real Cost of Software Defects

• Executives need to pay attention: “companies can, and do, achieve over 80% success rates and can bring the majority of strategic projects in on time and on budget through the adoption of superior requirements practices.”
• 71% of software projects that fail do so because of poor requirements management
• 50 to 60% of defects originate from requirements phase
• Rework effort amounts to 40 to 50% of the project cost
• Cost to fix defects due to failed requirements accounts for 82% of the effort to fix defects
• National Institute of Standards and Technology(USA) showed in a typical development project, fully 80% of software development are spent correcting software defects.
• NIST Estimated that software defects cost the U.S. economy, alone, $60billion
• Deficient requirements are the single biggest cause of software project failure. (Hofmann and Lehner, 2001)
• 50% of defects are due to requirements problems (Schwaber, 2006).
• Fixing requirements errors eats up roughly one-third of your software project budget. If you’re budgeting $500,000, you’re spending about $150,000 fixing defects that originate in your requirements
• One of the top three risks for projects is related to customer issues—approval delays, requirements changes, and poor communication (42% risk) (Rodrigues, 2001).
• To get the right product, you need to articulate your requirements early on, before the cost of fixing requirements errors kills your development budget, causes ill will with customers, and jeopardizes your business

"Little change" means "big headache"

Clients who use phrases like "minor enhancement," "little change," and "slight clarification" to communicate a change of requirements during the project's construction phase.

Translated, these phrases all mean that your client has changed the requirements and wants you to accommodate those changes without impacting the schedule or budget.

The inexperienced project manager believed that he was best serving the client by acquiescing to every requirement change. The result was disastrous: the project was over budget, beyond schedule, and failed to meet the client's expectations.

Finally, expecting but managing change is the best way to avoid feature creep and ensure successful delivery.