Software Design - Architectural Kata
•
1 j'aime•1,131 vues
Here is a presentation of a BBS session on Architectural Kata that I have hosted at my company at 24 June 2015.
Recommandé
Recommandé
Contenu connexe
En vedette
En vedette (17)
Dernier
Dernier (20)
Software Design - Architectural Kata
- 1. Workshop – ArchitecturalKata Denİz YAVAŞ
- 2. Agenda • Introduction • Problem • Design Session • Presentation • Retrospective • CONCLUSION
- 3. Kata (方) • Kata(型 or 形 literally "form") a Japanese word, are the detailed choreographed patterns of movements practised either solo or in pairs.
- 4. CONDITIONS • Teams of 3-4 • No internet, phones etc. • Assumptions are permitted
- 5. World of Chesscraft • Ranking Service • NPC(AI) ranking • Online-Offline Availibility • Pattern Recognition
- 6. deliverables • High Level Architecture • Entity(Domain) Diagrams • Component Diagrams
- 8. JUST ENOUGH UP-FRONT DESIGN
- 10. STOVEPIPE SYSTEM
- 12. The Grand Old Duke of York
- 15. Swiss Army Knife
Notes de l'éditeur
- The Stovepipe Enterprise AntiPattern is characterized by a lack of coordination and planning across a set of systems.
- Document-driven software processes often produce less-than-useful requirements and specifications because the authors evade making important decisions. In order to avoid making a mistake, the authors take a safer course and elaborate upon alternatives.
- Egalitarian software processes often ignore people’s talents to the detriment of the project. Programming skill does not equate to skill in defining abstractions. There appear to be two distinct groups involved in software development: abstractionists and their counterparts the implementationists.
- Management of risk in follow-on system development is often overlooked due to overconfidence and recent system successes. A general architecture approach that is tailored to each application system can help identify unique requirements and risk areas.
- The pervasive lack of technology transfer between software projects leads to substantial reinvention. Design knowledge buried in legacy assets can be leveraged to reduce time-to-market, cost, and risk.
- A Swiss Army Knife is an excessively complex class interface. The designer attempts to provide for all possible uses of the class. In the attempt, he or she adds a large number of interface signatures in a futile attempt to meet all possible needs.
- The classic AntiPattern from standards bodies, Design by Committee creates overly complex architectures that lack coherence. Clarification of architectural roles and improved process facilitation can refactor bad meeting processes into highly productive events.