It has been an ongoing debate or area of confusion that requirements and designs are being used and elaborated upon interchangeably. In the past, we have said that you must first establish the requirements and then another role, such as a solution architect, will typically be responsible for elaborating on the design aspects of the initiative or planned solution. However, through our years of experience, we have realized that this is not always practical and not always appropriate. In some situations, requirements will be defined and elaborated initially, and, in some cases, the design will initiate further definition of more requirements.
People are solution-driven, which means that, occasionally, design or solution sometimes drives the analysis of requirements rather than requirements being the first step in the life cycle. Regardless of whether requirements...