Software requirements and estimates
•Descargar como PPTX, PDF•
0 recomendaciones•1,164 vistas
Recomendados
Más contenido relacionado
Similar a Software requirements and estimates
Similar a Software requirements and estimates (20)
Más de Chuck Reeves
Más de Chuck Reeves (9)
Último
Último (20)
Software requirements and estimates
- 1. Software Estimations and Requirements
- 3. Requirements
- 4. Requirements How?
- 6. Requirements Avoid
- 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 / •Enable Superior •User Friendly / Simple
- 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
- 10. Estimates What is a good Estimate?
- 11. Estimates
- 12. Estimates
- 15. Estimates What Can you do
- 16. Estimates Count Computer Compare
- 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
Notas del editor
- 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