endava career days jan 2012 analysis and architecture in endava
TRANSCRIPT
A&A in Endava.How do we get to software quality? Carmen David
Cezar CocaFlorin Cardasim
- Career Days, Jan 2012 -
• The A&A discipline in Endava
● Disciplines & Projects
• Business Analysis at Endava
● Who, what and how?
•Architecture at Endava
● What is architecture? Views, tools, technologies,
practices?
● Sonar: one step towards software quality
● Toxicity matrix
Agenda
2
IN YOUR ZONE
Endava: disciplines and projects• 2 dimensions:
• Vertical one - disciplines• Horizontal one - projects
• Each discipline focuses on People Development and Best Practices
Projects Management
Development
Testing
Managed Services
Analysis & Architecture
IN YOUR ZONE
The Analysis & Architecture Discipline
Business Analyst System Analyst Architect•Owns requirements
management
•Owns functional specifications
•Helps in testing
•Owns detailed design
•Owns technical specifications
•Helps for requirements management
•Helps for functional specifications
•Does development
•Owns the architecture
• tools & technologies
• strategic decisions
• critical components
• coaching & training
•Does presales work
• Customer workshops & presentations
• Proposals
Close to the Team and very visible to the Customer
5IN YOUR ZONE
1. Scrum Master2. Dev Lead3. Developer4. Developer5. Developer6. Test Lead7. Tester8. Tester9. Product Owner10. Business Analyst11. Architect12. UAT Coordinator13. Environments14. Operational Support15. Your Mum
The Scrum and outside of it1 2 3
4 5
86 7
9
10
12
13
14
15
11
The Scrum
Everyone else you need to get the
software delivered
Business Analyst
System Analyst/Architect
6IN YOUR ZONE
The Project Team
Business Analyst
Dev LeadProject Manager Tester
Product owner
DeveloperSystem Analyst
Project plan
7IN YOUR ZONE
Who’s the BA in the room?
Let me be your
interpreter
I speak Java “Tell me what
you need”
I speak English “I will tell you what
I want”
I have to support it …
“must be user friendly”
I have to teach people to use it “…must be easy to use”
8IN YOUR ZONE
The Business Analyst is…
•A liaison among stakeholders to elicit, analyze,
communicate and validate requirements for changes to
business processes, policies, and information systems – IIBA
•The one who ensures that requirements are visible to and
understood by all stakeholders
9IN YOUR ZONE
The Business Analyst does…
Scope the Business Area
Elicit requirements
Analyze and Document
Requirements
Communicate Requirements
Identify solutions
Verify Solution Meets the
Requirements
IN YOUR ZONE10
What is Architecture?Architecture – is it just a bunch of views/diagrams?
IN YOUR ZONE
Architecture – is it about (the right) tools?
IN YOUR ZONE
Architecture – is it about (the right) technologies?
IN YOUR ZONE
Architecture - is it about (the best) practices?
13
14IN YOUR ZONE
So What is Architecture?
•Probably a smart combination of all the above
•What we know for sure is that Architecture is a
determinant factor for software quality
•Sonar: one step towards software quality
15IN YOUR ZONE
Sonar
Open platform to manage code quality
Covers the 7 axes of code quality
16IN YOUR ZONE
Sonar – the dashboard
17IN YOUR ZONE
Non respect of coding standards and best practices
18IN YOUR ZONE
Lacking comments in the source code, especially in public APIs
19IN YOUR ZONE
Having duplicated lines of codeRecommended best practice is that to qualify for deployment, code duplication levels should be kept under 8%
20IN YOUR ZONE
Complexity
21IN YOUR ZONE
Unit tests70-80% code coverage is a reasonable goal
22IN YOUR ZONE
Architecture and DesignHaving a spaghetti design (cyclic dependencies)
23IN YOUR ZONE
Dependency Matrix
24IN YOUR ZONE
Enforce Architectural rulesBuild Breaker plugin
26IN YOUR ZONE
Toxicity Chart – Open Source Project
27IN YOUR ZONE
Toxicity Chart – Reviewed Project
28IN YOUR ZONE
Carmen David | Business Analyst
Cezar Coca | System Analyst
Florin Cardasim | Head of Analysis & Architecture
Thank you!