
ALT Capture current business needs and anticipate future ones Software architecture does not exist in isolation to the business. If we could produce architecture that is independent of the businesses’ needs, then we would have truly ‘best practices’ in architecture approaches: ones that could be blindly used, guaranteed to come with the best trade offs. But these don’t exist, because every organization has different current and future priorities and constraints. Good software architecture keeps the business requirements in mind, and translates them into architecture priorities and constraints. This is true for the current requirements, and the likely future evolution of the business - and the change of requirements. Capture the current business needs. Capture business requirements, as they relate to non-functional requirements like performance, reliability, scalability and others.
























