Comments for Effective Software Design

Comment on Adaptable Designs for Agile Software Evolution by Hayim Makabee

Hayim Makabee — Wed, 22 May 2013 15:25:23 +0000

Thanks for your comments and references, Bryan. I like the distinction between “doing Agile” and “being Agile”.

Comment on Adaptable Designs for Agile Software Evolution by Hayim Makabee

Hayim Makabee — Wed, 22 May 2013 15:18:30 +0000

Thanks. I agree that producing adaptable designs is very challenging. But my experience is that having plugable components allows the software to evolve faster.

Comment on Adaptable Designs for Agile Software Evolution by Hayim Makabee

Hayim Makabee — Wed, 22 May 2013 15:15:35 +0000

Thanks, Alex. I used OO concepts to say that an adaptable design should describe a class (or family) of systems and that each version of the system during its evolution should be an “instance” of this design.

Comment on Adaptable Designs for Agile Software Evolution by Hayim Makabee

Hayim Makabee — Wed, 22 May 2013 15:13:06 +0000

Thanks, Daniel. I agree that experience is essential to model the domain, and for this reason I believe that Agile teams must have the support of SW architects.

Comment on Adaptable Designs for Agile Software Evolution by Hayim Makabee

Hayim Makabee — Wed, 22 May 2013 15:10:57 +0000

Thanks, Putcha. I agree that adaptability is always necessary, independently of the software development methodology. But in the case of Agile there are too many people fighting against BDUF but not offering any alternative. My goal was to propose ADUF as an alternative to BDUF.

Comment on Adaptable Designs for Agile Software Evolution by Hayim Makabee

Hayim Makabee — Wed, 22 May 2013 15:06:54 +0000

Thanks, Gene. Unfortunately a common mistake in the “just enough design” approach is not understanding the need for adaptability. The result is a design that is simple but not flexible.

Comment on Illusory Superiority: Are you a good programmer? by André Amram Duque

André Amram Duque — Mon, 20 May 2013 12:11:09 +0000

My ‘habib, code alone not fun. Sometimes code alone also not learn and doesn’t grow group practice as team leader or candidate

Comment on Adaptable Designs for Agile Software Evolution by boomerang

boomerang — Thu, 16 May 2013 16:04:00 +0000

Although most of what u said is highly pertinent, Agility at times has a cost. Because systems today go from somewhere and from something, we cannot consider agility to be a key and fondamental factor when it comes to designing the system. technology has given us a great helped in this sense and we should add it on the balance. By the way architecture is about reusability, who says reusability also says loosely coupled and from that building blocks. This said agility shouldn’t add a question mark even on our building blocks. Business processes allows us to be flexible meanwhile SOA gives us reusability and all the buzz around it. when this are put together we deliver a solution that is aligned to business.
As to me I don’t share the point of view stating that the Agile methodology could ameliorate the design of EA in the sense that business processes when well orchestrated gives us full agility and an unlimited reuse potential. and because we must always go from somewhere (web services wrappers for legacy systems and composite application) we can’t actually reconsider even our building block for the sake of agility. Let us focus on understanding the business. the problem today in EA is the need for architects to be extremely competent and rigorous when approaching EA problems but once a good foundation is set…

Comment on Adaptable Designs for Agile Software Evolution by Adaptable Design Up Front | Chris F Carroll

Adaptable Design Up Front | Chris F Carroll — Thu, 16 May 2013 13:07:44 +0000

[…] A term to describe the idea of (1) avoiding Big Design Up Front (2) doing Enough Design Up Front and (3) recognising that for agile development that up-front design must very specifically be a design that caters for future change. First coined as far as I know in a blog post by Hayim Makabee. […]

Comment on Adaptable Designs for Agile Software Evolution by CloudEntity (@AlexDGarrett)

CloudEntity (@AlexDGarrett) — Fri, 10 May 2013 01:22:17 +0000

@Bryan are you at a point in your research where you have further findings that you can share? regards Alex