Dos and dont's of sw architecture by Kamil Witecki
- 1. DO’s and DON’Ts of SW Architecture Kamil Witecki
- 2. The information and views set out in this publication are those of the author(s) and do not necessarily reflect the official opinion of the NOKIA. Publication is not authorized or endorsed by NOKIA. The publication contains work of other authors. Work of other authors might be protected by licenses. Consult information collected in last chapter for details and acknowledgments. Author claims no right to the work of other authors.
- 3. Key drivers Users Organization Business
- 4. Users
- 5. By users we mean end-users, ones deploying and maintaining product. Anybody involved is affected by architect’s choices.
- 6. Organization
- 7. There are different types of organizations. Startup with collocated team of 5-10 people works differently than global enterprise.
- 8. Business
- 9. Business will shape architect’s decisions too. Different business models and goal must be taken into account.
- 11. Architects are technical leaders. Well selected architecture will help to realize the mission.
- 13. Ignoring factors other than technical ones impedes execution. Architect in such case does not help and lead. Creates pressure by demands. Is more like a boss, not leader.
- 15. Solutions
- 18. Users Actor consider what users are capable of. You will certainly be willing to use regular expression. Average person - rather not. Goal take into account what user wants to achieve. You are here to provide solution. Purpose even if goals are same, purposes will differ. Reader and renovator want to localize a book on a shelf, but for very different reasons
- 20. Analyze the use case diagram carefully? What do you see? It is a restaurant. Your system is supposed to improve effectiveness. How about an ordering machine next to an entrance?
- 22. Do you see the problem with diagrams? They are synthetic. After seeing the type of restaurant you immediately feel ordering machine will not work. Being served is a selling point of fancy restaurants.
- 23. What is the difference? Diagrams can oversimplify. Keep in mind whole context and environment. Diagram Reality
- 24. If I’d asked people what they wanted, they would have asked for a faster horse. Henry Ford We can easily propose quantitative changes. Willing to get something faster, stronger, lighter. Qualitative changes require creative mind and additional knowledge. Therefore we cannot simply ask what to deliver. As in the example above the real issue was faster means of transportation and the answer was a car.
- 25. Organization
- 26. Organizations which design systems . . . are constrained to produce designs which are copies of the communication structures of these organizations Melvin Conway Organization will twist your architecture. Instead of fighting it - use it. Aligning design with natural communication channels will help execution. Additionally it can help to realize your design. For example assign independent parts to remote teams and observe how well natural communication issues help to keep components separate.
- 27. ProducerA Dispatcher Controller ProducerC ConsumerAConsumerC InterfaceA InterfaceB InterfaceC ControlInterfaceBControlInterfaceC How to efficiently assign 3 teams to components?
- 30. Business
- 31. Goals Time to market Sometimes we have to deliver product on an exact date. Sometimes we can benefit from delaying release to provide a cherry on top. Check in what situation you are. Business model and roadmap Do you "fire and forget" the project? If no maintenace is involved, you can probably give up extendability. Though if you will keep project running for 10 years invest in it a lot! Target customer Who is going to buy it? What is the relation? Is it one vendor <-> one customer contract? Or world market product?
- 32. Summary
- 33. Users
- 35. Business
- 37. Bibliograpy I Kishorekumar 62. https://en.wikipedia.org/wiki/File:Restaurant_Model.png. Gregor Cresnar. https://www.flaticon.com/. Icons made by Gregor Cresnar from www.flaticon.com. Freepik. https://www.flaticon.com/. Icons made by Freepik from www.flaticon.com. IgorSaveliev. https://pixabay.com/pl/kawiarnia-na-%C5%9Bwie%C5% BCym-powietrzu-705881/.
- 38. Bibliograpy II John Lester. boss vs leader. https://www.flickr.com/photos/pathfinderlinden/12155264433, 2014. Split image into two. See licence: https://creativecommons.org/licenses/by/2.0/ (Attribution 2.0 Generic (CC BY 2.0)). OpenClipart-Vectors. https://pixabay.com/p-156742/. OpenClipart-Vectors. https://pixabay.com/pl/komputer-1295358/.
- 39. Bibliograpy III Smashicons. https://www.flaticon.com/. Icons made by Smashicons from www.flaticon.com. Unknown. https://pixnio.com/architecture/city-downtown/ architecture-bridge-buildings-city-water-reflection-sea-sky.