Herding Cats

DECEMBER 3, 2017

Seems there is still some confusion (intentional or accidental) about the Cone of Uncertainty and its purpose and its use in software development. Tim Menzies, Steve Williams, Oussama Elrawas, Daniel Baker, Barry Boehm, Jairus Hihn, Karen Lum, and Ray Madachy, Software Process Improvement And Practice, (2009). 37-48, 2007.

2007 34

2007 2012 2009 2010 34

Herding Cats

JANUARY 9, 2017

The idea of risk and its management and handling is a critical success factor for all software development. Peter Drucker (1975) Management (From The Principles of Software Engineering , Chapter 6, Tom Glib, 1988). 1] Control or Economic Law Paperback, Eugen von Boehm-Bawerk, 2010. [2] Related articles.

Estimate 28

Estimate Risk 2010 Software Engineering 28

nTask

AUGUST 8, 2019

Its simplicity and ease of implementation has made it the most popular version of the systems development life cycle (SDLC) for software engineering and IT projects. What Dr. Royce was describing was a flawed model for software development as he argued for a model with multiple iterations or runs.

Software Review 97

Software Review 2019 Development Team Review Technical Review 97

Herding Cats

APRIL 8, 2017

These systems fall into the Software Intensive System of Systems (SISoS) category. The notion that innovation and engineering - software engineering - are somehow in conflict is common. . Both agile advocates and engineered systems advocates practice innovation and creativity. 39-58, 1997. [3] Related articles.

Web Development 37

Web Development Software Engineering 2010 Engineering 37

Herding Cats

MARCH 4, 2017

Software development project schedule estimation has long been a difficult problem. Reducing Estimation Uncertainty with Continuous Assessment: Tracking the “Cone of Uncertainty ” Pongtip Aroonvatanaporn, Chatchai Sinthop, Barry Boehm, ASE’10, September 20–24, 2010, Antwerp, Belgium. . "A For example for a recent paper abstract.

2010 28

2010 2007 Estimate Aerospace 28

Herding Cats

JANUARY 22, 2017

Barry Boehm's work in “Software Engineering Economics”. 4] Defense Acquisition Guide , Chapter 4, Systems Engineering , 15 May 2013. [5] ASE’10, September 20–24, 2010, Antwerp, Belgium. . [8] Software Engineering Economics”. Software Sizing, Estimation, and Risk Management, Auer-bach, 2006. [15]Jorgensen,

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

JANUARY 17, 2017

Barry Boehm's work in “Software Engineering Economics”. 4] Defense Acquisition Guide , Chapter 4, Systems Engineering , 15 May 2013. [5] ASE’10, September 20–24, 2010, Antwerp, Belgium. . [8] Software Engineering Economics”. Software Sizing, Estimation, and Risk Management, Auer-bach, 2006. [15]Jorgensen,

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

FEBRUARY 4, 2017

Barry Boehm's work in “Software Engineering Economics”. 4] Defense Acquisition Guide , Chapter 4, Systems Engineering , 15 May 2013. [5] ASE’10, September 20–24, 2010, Antwerp, Belgium. . [8] Software Engineering Economics”. Software Sizing, Estimation, and Risk Management, Auer-bach, 2006. [15]Jorgensen,

Technical Review 28

Technical Review Estimate 2005 Software Review 28

Herding Cats

APRIL 4, 2019

Misconceptions of Risk , Terje Aven, John Wiley & Sons, 2010. Critical Code, Software Producibility for Defense, Committee for Advancing Software-Intensive Systems Producibility , Computer Science and Telecommunications Board Division on Engineering and Physical Sciences, National Research Council of the National Academies, 2010.

Risk Management 43

Risk Management Risk 2003 2011 43

Herding Cats

MAY 7, 2019

Effort Distribution to Estimate Cost in Small to Medium Software Development Project with Use Case Points,” Putu Linda Primandari and Sholiq, The Third Information Systems International Conference, Procedia Computer Science, 72, pp. Software Development Effort Estimation using Fuzzy Bayesian Belief Network with COCOMO II,” B.

Estimate 40

Estimate Software Review Software 2012 40

Herding Cats

NOVEMBER 7, 2016

The primary purpose of software estimation is not to predict a project’s outcome; it is to determine whether a project’s targets are realistic enough to allow the project to be controlled to meet them ‒ Steve McConnell. The Future of Systems-and Software Development. Springer International Publishing, 2016.

Estimate 64

Estimate 2006 2005 2012 64

Herding Cats

MAY 10, 2019

Taxonomy-Based Risk Identification,” Marvin Carr, Suresh Konda, Ira Monarch, Carlo Ulrich, and Clay Walker, Technical Report, CMU/SEI-93-TR-6, Software Engineering Institute, June 1993. IEEE Transactions on Software Engineering , Vol. 255, April 2010. 24, 2010. “A México, 1 al 3 de Febrero de 2006.

Risk Management 38

Risk Management Risk Technical Review 2002 38

Herding Cats

MAY 11, 2019

This blog page is dedicated to the resources used to manage the risk encountered on software-intensive systems using traditional and agile development methods. Let's start with a critical understanding of the purpose of managing risk on software development projects. IEEE Transactions on Software Engineering , Vol.

Risk Management 35

Risk Management Risk Technical Review 2002 35