home

Smart (Enough) Systems

Is anyone else here reading "Smart (Enough) Systems" by James Taylor and Neil Raden?

I am about half-way through, and it is a 'good read'; anyone want to discuss it here?

...even amusing!

So far, I particularly like the history of IT that is part of describing why systems are not smart. Maybe its just me, but I actually laughed out loud at the description of Operational Data Stores as "a sort of kludge..."... now I am heading into the "Core Concepts" chapter.

Also, there is a related website (of course) smartenoughsystems.com, where J. Taylor has a blog, and there is a wiki for adding your own thoughts on the topic, I recommend checking it out.

David Wright
Member, IIBA
"As a general rule the most successful man in life is the man who has the best information."
Benjamin Disraeli (1804 - 1881)

    Sponsored Announcements & Special Offers

view counter

Whitepaper from HP - Why Focus on Requirements Definition Management in the Application Lifecycle?

Increasingly, smart businesses are looking much closer at requirements definition (RD) and requirements management (RM) (sometimes grouped together under the Gartner-coined phrase, requirements definition management (RDM)) to streamline the entire application lifecycle. Why? Because systematic and effective RDM captures software defects earlier in the lifecycle, and it reduces the overall likelihood that defects will be introduced. That’s important. How important? According to one study, the cost to fix a defect after delivery is more than 100 times the cost to fix it in the requirement and design phase. No business wants to be hit with that bill. Now to add to this the growing interest in agile development techniques as a way to deliver higher quality applications and we have an interesting recipe for success.

Download a Free Copy

view counter
© 2007-2010 Requirements Networking Group All rights reserved. contact | advertise | privacy
Requirements Networking Group