Download - Business Analysts V Architects
![Page 1: Business Analysts V Architects](https://reader033.vdocuments.site/reader033/viewer/2022061213/549867b8b47959424d8b5488/html5/thumbnails/1.jpg)
Business Analystsvs
Architects
Kevin Francis, Principal Architect
Business Analyst World, Melbourne, July 2009
![Page 2: Business Analysts V Architects](https://reader033.vdocuments.site/reader033/viewer/2022061213/549867b8b47959424d8b5488/html5/thumbnails/2.jpg)
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
![Page 3: Business Analysts V Architects](https://reader033.vdocuments.site/reader033/viewer/2022061213/549867b8b47959424d8b5488/html5/thumbnails/3.jpg)
3
Agenda
Architects defined. Responsibilities – BAs and Architects Interface Points Processes and Best Practices Tools
![Page 4: Business Analysts V Architects](https://reader033.vdocuments.site/reader033/viewer/2022061213/549867b8b47959424d8b5488/html5/thumbnails/4.jpg)
4
Architects:
Develop the architecture Choose the technologies Design the development approach Oversee the development Manage technical change
![Page 5: Business Analysts V Architects](https://reader033.vdocuments.site/reader033/viewer/2022061213/549867b8b47959424d8b5488/html5/thumbnails/5.jpg)
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
![Page 6: Business Analysts V Architects](https://reader033.vdocuments.site/reader033/viewer/2022061213/549867b8b47959424d8b5488/html5/thumbnails/6.jpg)
6
Interface Points
User Interface Design Non-Functional Requirements Architectural Design Data Design Scope Management Test Management
![Page 7: Business Analysts V Architects](https://reader033.vdocuments.site/reader033/viewer/2022061213/549867b8b47959424d8b5488/html5/thumbnails/7.jpg)
User Interface Design
![Page 8: Business Analysts V Architects](https://reader033.vdocuments.site/reader033/viewer/2022061213/549867b8b47959424d8b5488/html5/thumbnails/8.jpg)
8
The Usual Process
Screens
UI Components (Data Items)Technology
Flow
![Page 9: Business Analysts V Architects](https://reader033.vdocuments.site/reader033/viewer/2022061213/549867b8b47959424d8b5488/html5/thumbnails/9.jpg)
9
UI Approaches
•Easily deployed•Non-responsive•Non-integrated•Difficult to develop•Difficult to maintain
•Responsive•Attractive•Integrated•Easier to develop•Easier to maintain•Easily deployed
![Page 10: Business Analysts V Architects](https://reader033.vdocuments.site/reader033/viewer/2022061213/549867b8b47959424d8b5488/html5/thumbnails/10.jpg)
10
Web Application Technologies
HTML SharePoint etc Silverlight Desktop applications
![Page 11: Business Analysts V Architects](https://reader033.vdocuments.site/reader033/viewer/2022061213/549867b8b47959424d8b5488/html5/thumbnails/11.jpg)
11
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
![Page 12: Business Analysts V Architects](https://reader033.vdocuments.site/reader033/viewer/2022061213/549867b8b47959424d8b5488/html5/thumbnails/12.jpg)
12
Get up to date with technical options
![Page 13: Business Analysts V Architects](https://reader033.vdocuments.site/reader033/viewer/2022061213/549867b8b47959424d8b5488/html5/thumbnails/13.jpg)
13
Gather requirements (without making commitments)
![Page 14: Business Analysts V Architects](https://reader033.vdocuments.site/reader033/viewer/2022061213/549867b8b47959424d8b5488/html5/thumbnails/14.jpg)
14
Design the Architecture
![Page 15: Business Analysts V Architects](https://reader033.vdocuments.site/reader033/viewer/2022061213/549867b8b47959424d8b5488/html5/thumbnails/15.jpg)
15
Prototyping
![Page 16: Business Analysts V Architects](https://reader033.vdocuments.site/reader033/viewer/2022061213/549867b8b47959424d8b5488/html5/thumbnails/16.jpg)
Non-Functional Requirements
![Page 17: Business Analysts V Architects](https://reader033.vdocuments.site/reader033/viewer/2022061213/549867b8b47959424d8b5488/html5/thumbnails/17.jpg)
17
The Tension
NFRs
Availability
Performance
Scalability
Cost
![Page 18: Business Analysts V Architects](https://reader033.vdocuments.site/reader033/viewer/2022061213/549867b8b47959424d8b5488/html5/thumbnails/18.jpg)
18
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
![Page 19: Business Analysts V Architects](https://reader033.vdocuments.site/reader033/viewer/2022061213/549867b8b47959424d8b5488/html5/thumbnails/19.jpg)
Architecture
![Page 20: Business Analysts V Architects](https://reader033.vdocuments.site/reader033/viewer/2022061213/549867b8b47959424d8b5488/html5/thumbnails/20.jpg)
20
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
![Page 21: Business Analysts V Architects](https://reader033.vdocuments.site/reader033/viewer/2022061213/549867b8b47959424d8b5488/html5/thumbnails/21.jpg)
Data Design
![Page 22: Business Analysts V Architects](https://reader033.vdocuments.site/reader033/viewer/2022061213/549867b8b47959424d8b5488/html5/thumbnails/22.jpg)
22
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
![Page 23: Business Analysts V Architects](https://reader033.vdocuments.site/reader033/viewer/2022061213/549867b8b47959424d8b5488/html5/thumbnails/23.jpg)
Scope Management
![Page 24: Business Analysts V Architects](https://reader033.vdocuments.site/reader033/viewer/2022061213/549867b8b47959424d8b5488/html5/thumbnails/24.jpg)
24
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
![Page 25: Business Analysts V Architects](https://reader033.vdocuments.site/reader033/viewer/2022061213/549867b8b47959424d8b5488/html5/thumbnails/25.jpg)
25
Scope Management
Change RequestDiscuss Options
with ArchitectEstimate
Options
![Page 26: Business Analysts V Architects](https://reader033.vdocuments.site/reader033/viewer/2022061213/549867b8b47959424d8b5488/html5/thumbnails/26.jpg)
Test Management
![Page 27: Business Analysts V Architects](https://reader033.vdocuments.site/reader033/viewer/2022061213/549867b8b47959424d8b5488/html5/thumbnails/27.jpg)
27
Test Management
Test Early Decipher requirements Prioritise testing Support non-functional testing
Project
Testing
BA Requirement
![Page 28: Business Analysts V Architects](https://reader033.vdocuments.site/reader033/viewer/2022061213/549867b8b47959424d8b5488/html5/thumbnails/28.jpg)
28
Tools
Why use a tools-based approach to managing the interface?
Process tools Rational Tools Microsoft Tools Open Source Options
![Page 29: Business Analysts V Architects](https://reader033.vdocuments.site/reader033/viewer/2022061213/549867b8b47959424d8b5488/html5/thumbnails/29.jpg)
29
Thank you
Questions (and hopefully) Answers
http://msmvps.org/blogs/architecture www.objectconsulting.com.au [email protected]