bmason's blog

OO vs CASE

Software development is hard. There are two principle paradigms intended to make it easier. CASE (Computer Assisted Software Engineering) systems seeks to exploit common patterns and machine generate explicit code to handle each process. Object Oriented systems seek to exploit common patterns and handle each process by reusing those common patterns. Correctness and reliability are vital to the success of software systems. A common strategy to ensure these is to test the system after development. The two principle development paradigms offer different strategies.
 

Changes late in the cycle!?!?! GREAT!

Changes, especially those late in the software development life cycle (SDLC), are a favorite bogey man.  Changes are problematic(a convenient excuse) for weak rigid teams and welcome for stronger Agile teams.
Changes late in the cycle are OK for strong Agile teams because both the management and software itself are Agile and able to accommodate changes - new ways of doing things.
 

The Pareto Principle

This is the idea that most effects come from a few causes and is more commonly known as the 80-20 rule. If you do the math - $10 in sales generated by ten customers - two customers generated $8 - eight customers generated $2 - one of the two are sixteen times more valuable than one of the eight. Of course it is never exactly eighty-twenty but a significant clumping of causes-effects always holds.

 

Goals

A familiar story:  We are trying to defend an area from the enemy and have set up some fire bases.  A squad of men with small arms behind a sandbag barrier will shoot at the enemy from these fire bases. The bases will be much more effective and the men safer if they can support each other with small arms fire so we carefully measure the elevation and place the bases on high ground for maximum vision, clear jungle and some old buildings to improve the line of sight, and install firing platforms to improve stability and accuracy.  We demonstrate the effectiveness of

Syndicate content