0
Software Estimations and     Requirements
RequirementsWhy Bother?
Requirements
Requirements      How?
Requirements  Gathering
Requirements      Avoid
Requirements                Ambiguous•Acceptable / Adequate          •Including / Not Limited Too•As much as Practicable  ...
Requirements                   Use Case•Actors (User)               •Priority•Description                 •Frequency Of Us...
RequirementsSet in Stone?
EstimatesWhat is a good Estimate?
Estimates
Estimates
EstimatesOver / Under
EstimatesCone Of Uncertainty
EstimatesWhat Can you do
EstimatesCount Computer   Compare
Estimates Be Iterative
Citations•Images:    •http://blogs.mentor.com/verificationhorizons/blog/author/hfoster/page/2    •http://www.flickr.com/ph...
Upcoming SlideShare
Loading in...5
×

Software requirements and estimates

1,283

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,283
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
15
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Keeps timeline shortEnsures Proper DeliveryHow names change
  • Break up into groups:Business RequirementsBusiness Rules User RequirementsFunctional RequirementsQuality Attributes – Portability Constraints
  • Break up into groups:Business RequirementsBusiness Rules User RequirementsFunctional RequirementsQuality Attributes – Portability Constraints
  • Identifying the Actors (Users)Ask them what they need (Use case)Understanding the Goal
  • Feature CreepGold Plating Ambiguous Terms
  • Ambiguous Terms
  • Per Requirement
  • Change Controls need to be in placeDependencies For requirements will affect change
  • Change Controls need to be in placeDependencies For requirements will affect change
  • Measure what is mesuarble
  • Over:Parkinson's Law (Project will fill the budget)Students Law (Procrastination)Under:Dependency FalloutFailure to Plan (Less time to work less time to plan)Project is late Cause other failures More Meetings Less Development Failure to Deliver Re-prioritization Interim Release Quick and Dirty Workarounds Which introduce bugs
  • Describes how accurate an estimate will be in which phase of a projectEarlier in Design more inaccurate the estimate will be (This is based off skilled estimators your estimate will be more uncertin)
  • Many Techniques exists but depend on project style
  • Count what you canHours / FeatureHours / Web PageHours / Integration Points Hours / ClassesHours / Defects Hours / Complexity (CRAP Index with Unit testing or Cylomatic Complexity with PHP MD)
  • Constantly Re-evaluate at every step
  • Identifying the Actors (Users)Ask them what they need (Use case)Understanding the Goal
  • Transcript of "Software requirements and estimates"

    1. 1. Software Estimations and Requirements
    2. 2. RequirementsWhy Bother?
    3. 3. Requirements
    4. 4. Requirements How?
    5. 5. Requirements Gathering
    6. 6. Requirements Avoid
    7. 7. Requirements Ambiguous•Acceptable / Adequate •Including / Not Limited Too•As much as Practicable •Several•Between •Shouldn’t•Depends on •State-Of-The-Art•Efficient •Normally•Fast / Rapid •Seamless / Transparent•Flexible •Support•Improved / Better / Faster / •EnableSuperior •User Friendly / Simple
    8. 8. Requirements Use Case•Actors (User) •Priority•Description •Frequency Of Use•Pre-Conditions •Business Rule•Post-Conditions •Special Requirements•Normal Courses •Assumptions•Alternative Courses •Notes and Issues•Exceptions•Includes
    9. 9. RequirementsSet in Stone?
    10. 10. EstimatesWhat is a good Estimate?
    11. 11. Estimates
    12. 12. Estimates
    13. 13. EstimatesOver / Under
    14. 14. EstimatesCone Of Uncertainty
    15. 15. EstimatesWhat Can you do
    16. 16. EstimatesCount Computer Compare
    17. 17. Estimates Be Iterative
    18. 18. Citations•Images: •http://blogs.mentor.com/verificationhorizons/blog/author/hfoster/page/2 •http://www.flickr.com/photos/krazydad/4067542/sizes/z/in/photostream •http://www.frontrowreviews.co.uk/editorial/greatest-comic-spoof- movies/5900•Books: •“Software Estimation” Steve McConnell 0-7356-0535-1 •“Software Requirements” Karl E Weigers 0-7356-1879-8•References: •https://github.com/pmjones/php-framework-benchmarks•Tools: •Apache Benchmark •PHPMD and PHPUnit •Mylyn
    1. A particular slide catching your eye?

      Clipping is a handy way to collect important slides you want to go back to later.

    ×