2. Learning Objectives Understand the points of interface between Business Analysts and Architects from an Architect’s perspective Learn the best practices available in the space and the division of labour across the roles Review tools available to support the analysis, design and architecture of solutions
3. Agenda Architects defined. Responsibilities – BAs and Architects Interface Points Processes and Best Practices Tools
4. Architects: Develop the architecture Choose the technologies Design the development approach Oversee the development Manage technical change
5. BA and Architect Responsibilities Business Analyst: Gather requirements Document Requirements Work out design Focus on business processes Change management Training Process Change Interface to the business Project vision/purpose Scope Management Architect: Design system to meet requirements Manage the Development Team Implement technology Focus on non-functional, technical and UI Interface to Enterprise Architecture Project vision/purpose Scope Management
6. Interface Points User Interface Design Non-Functional Requirements Architectural Design Data Design Scope Management Test Management
20. Best Practice BAs understand the requirements BAs understand the business Architects understand the technology and best practices for implementation Technical UI design is a specialised Designer/Developer task, with assistance from the BA Poor result without BA, Architect and Designer working together
27. Non-Functional Requirements Balance between cost and requirements Architects understand this balance Needs BAs to translate to the business though Can't be a one-way street
29. Architectural Design Architecture is a set of trade-offs They need to be understood from a business perspective The trade-offs impact the requirements Cooperation therefore produces the best outcome
31. Data Design Data requirements come through the BAs Database design is a specialist Architecture job BAs can assist the Architect to understand the data Focus is needed on aspects like availability, recovery, auditing and archiving
33. Scope Management Scope is always a trade-off between cost and functionality There are always multiple ways to achieve the end-game The aim is efficiency and minimum wasted cost BA and Architects work together with ongoing change: Estimate early Manage trade-offs Present alternatives