Archive for Software Products
A LinkedIn forum question resonated with a question that has long interested me.
“The UML comprises 13 diagram types, the SysML comprises 9 diagram types. Each of these offers a different view of a planned system and helps to create a common understanding. But how many diagrams are necessary, and how many…
Read MoreWe don’t need a miracle cure for rogue algorithms. More regulation will not prevent them. Proven software engineering and testing will.
Read MoreThe confluence of many technology streams made today’s Internet. It is now so ingrained in daily life that it is hard to grasp what an immense project it has been.
Read MoreA few days ago, I participated in a panel discussion on open source tools for testing at the QUEST conference with the two founders of Selenium: Jason Huggins of Sauce Labs and Simon Stewart of Google.
Before the panel started we chatted a bit with the moderator. We couldn’t come up with…
Technical debt refers to aspects of a codebase are incomplete, deficient, obsolete, or buggy. This can occur for many reasons: insufficient time, uncertainty, omissions, poor workmanship, or poor management. This is termed “debt” because it will take additional time and money to correct, update, or revise.
Technical equity refers to aspects of a…
Open source tools for model-based testing are listed in five groups: Binaries, Fielded, Club, Beta, Development.
Read MoreTechnical Equity is the value that accrues when a software system is well-formed. Instead of burdening you with unnecessary excess cost, your codebase works for you. Technical equity pays dividends: you avoid wasted effort and the consequences of buggy releases, and gain the advantage of releasing sooner and/or with more features,…
Read More
Technical Bankruptcy occurs when technical debt overwhelms the maintainers of a software system. I’ve previously blogged about a case study: how the accumulation of poor development practices resulted in the business failure of highly successful Enterprise IT software company.
The technical debt metaphor provides a nice handle for a software development …
Through Google Circles, I happened to see David Welton’s very interesting reflection on the Tcl programming language (posted in 2010):
http://journal.dedasys.com/2010/03/30/where-tcl-and-tk-went-wrong/
About ten years ago, I chose to develop a commercial automated software testing tool with Tcl and Tk. This post explains that decision and its consequences.
Despite testing tools that tout “visual programming”…
I think’ve finally found a good visual metaphor for model-based testing. In Aliens, Ellen Ripley uses the power lifter suit to battle the Alien Queen. Model-based testing is like the power lifter suit. It has to be driven with intelligence and skill, but it’s your only hope against the super bugs that…
Read More
J on 
Bob Binder on 