Seems like a simple question…but many valid opinions have elicited many fiery debates. Help me provide some answers by reacting to my perspective below. I decomposed design into 3 parts: A). Definition. B). Major inputs into design. C). Who owns it.
A: Definition of Design:
The act of design is not unique to software. It exists in many areas of our lives. There are many definitions but here is one I think most of us could agree on: “Design is an activity that translates an idea into a blueprint for something useful, whether it's a car, a building…a service or a process.” For an IT shop, the “something useful” is software, the “blueprint” is the design and the “idea” is the requirement(s).
B: Major perspectives/influences into Design:
Before we tackle who “owns” it, let’s think about who needs to be around the table and the perspectives they bring. I’d argue there are 4 key perspectives that need to be considered in order to be successful in the vast majority of design decisions.
1. Immediate business need / idea.
2. Condition of target legacy system.
3. Longer-term solution target.
4. Resource constraints (time, money, human resource capacity).
