Estimating software development effort based on use cases -- experiences from industry
From MaRDI portal
Recommendations
- Sizing use cases: How to create a standard metrical approach
- Measurement and effort prediction for web applications
- scientific article; zbMATH DE number 2087592
- CEOS -- a cost estimation method for evolutionary, object-oriented software development
- Integration of the Grey relational analysis with genetic algorithm for software effort estimation
Cited in
(12)- Requirements-based estimation of change costs
- Replicating the CREWS use case authoring guidelines experiment
- Software development cost estimation approaches -- A survey
- An empirical study of ICASE learning curves and probability bounds for software development effort
- CEOS -- a cost estimation method for evolutionary, object-oriented software development
- Quality and understandability of use case models
- Use case analysis based on formal methods: an empirical study
- scientific article; zbMATH DE number 2088713 (Why is no real title available?)
- Bin-packing-based planning of agile releases
- Measurement and effort prediction for web applications
- Program understanding behavior during estimation of enhancement effort on small Java programs
- scientific article; zbMATH DE number 2087592 (Why is no real title available?)
This page was built for publication: Estimating software development effort based on use cases -- experiences from industry
Report a bug (only for logged in users!)Click here to report a bug for this page (MaRDI item Q4435890)
