Good code-isnt-enough
7 likes567 views
The document discusses the role of software architecture in the development process, emphasizing that good code alone is not sufficient for a successful software project. It highlights the importance of structure, guidelines, and collaboration in designing and managing software systems while introducing practices like continuous integration and load testing. The training course mentioned aims to equip enterprise software developers with skills to create structured, pragmatic software architectures.
Good code-isnt-enough
- 1. s re f or developer Softwar e architectu What is software What is therole of How do you define How do you share How do you deliver architecture? a software architect? software architecture? software architecture? software architecture? Good code isn’t enough
- 2. simon.brown@codingthearchitecture.com @simonbrown on Twitter
- 3. “Software Architecture for Developers” Enterprise Architecture Technology and business strategy across organisations and organisational units. { System Architecture Software and infrastructure architecture for an end-to-end system. Application We call this Architecture software Software architecture for an application, sub-system or component. architecture and it’s the scope /// <summary> /// Represents the behaviour behind the ... /// </summary> public class SomeWizard : AbstractWizard of the training { private DomainObject _object; private WizardPage _page; course private WizardController _controller; public SomeWizard() { } ... }
- 4. “Enterprise Software Developer” ctical train ing course A fo ur-day pra g softwar e within an ab out buildin ructured, e environm ent in a st enterpris atic way. and pragm lightweight
- 5. Does good code guarantee a successful software project?
- 6. A successful software project is about much more than good code
- 7. The reputation of the development team is at stake! It’s important It’s important that we know that the software we what release we’re releasing “works” That’s us!
- 8. How much up-front work do you need to do? This much? Iterative & Incremental Development Serial Development This much?
- 9. Most projects simply do what they’ve always done a lly a usu is is e An d th f th iat ion o l! :- ) var mod e er fall” “ Wat
- 10. “ What are we building?
- 11. User stories are high-level requirements ant to statements tome r, I w s a c us y bank ( 003) A n ma nage m that I ca log in so ts o nline. ac coun (009) Cus tomers ca statement n downloa s for the d : Must last three Priority months. Priority: M ust
- 12. Software architecture is the big picture
- 13. Structure = components/services and their interactions Guidelines = patterns, templates and examples Software architecture introduces structure and guidelines into a software system, leading to consistency clarity and Consistency = a standard approach to solving common and recurring problems Clarity = a thought out design with a clear architectural vision
- 14. Systems & Containers Requirements 1-2 days for an initial design y ativel coll abor te h is e para Do ing t e’s s eopl allows p o meet ide as t Components & Estimates
- 15. Can you deliver everything? Prob ably not! Refine a nd challenge Prioritise the scope
- 16. Kanban boards are an excellent way to visually track progress
- 17. Does your architecture work? ng Satisfies th e Fou ndations for Platfo rm for solvi vers blem arch itectural dri the code the business pro
- 18. y e ss b l y gu r c a n on ms o You d iagra g at look in e code Will these software systems s ourc perform and scale acceptably?
- 19. Concrete experiments Requirements A system / type p roto wa way pt o r thro once Foundations A of of c code pro c tion p rodu
- 20. Load testing client simulating concurrent Website user access Simulate multiple users with a typical usage profile, preferably with an environment as near Other systems, data to production as possible sources, etc
- 21. Source code control introduces a number of things, including: Backed-up source code A log of the e changes mad to A simple w ay to revert opy a previou s working c Sim plified parall el development
- 22. Developers c ommit ode Source code Developers u pdate orking (check-in) c heir local w repository t ocal -out) from their l copy (check y working cop Developers have a local y working cop of the code
- 23. 2. Work on the branch instead of the trunk branch 4. Merge the 1. Create a branch branch back to from the trunk the trunk when finished 3. Merge from the trunk to keep the branch up to date trunk
- 24. How do you know that you’ve not broken something? e you t s giv te d tes acto r Au toma t o re f de nce c onfi
- 25. Low-level tests for classes and components Unit & integration tests “Functional” tests across container boundaries
- 26. How much do you test? This much? 0% 100% e t th s , tes all step code Sm ” ortant d goal) This much? “imp a go o is + (70%
- 27. to do when T hings e soft ware build ing th 1. Compile the code to your w eb server 2. Pub lish files it works 3. M aybe check
- 28. “ It works on my machine! Even t h shou e sim ld pl be a est ut of build omat ed s
- 29. Continuous Integration Development Server Web-tier Server Development Server Middle-tier Automated build script Development Server Database Subversion Source code repository The continuous integration server gets the source code from the repository and runs the build compiling, testing, script; packaging and installing the software
- 30. Build-Test-Run when we commit code to the repository Continuous & nightly builds Continuous build + longer running integration tests
- 31. Automation introduces consistency and repeatability Auto mate ly us d rel eful eas if es a you’ re re es real br anch ing on work
- 32. Database connection strings Web service URLs Server IP addresses Software E-mail addresses System File locations are it ems ation se Service credentials igu r xte rnali conf if ic; e de Many spec e co nmen t urc o e so envir f rom th them
- 33. “ Anybody know which version we’re running?
- 34. “It doesn’t look like version 1.2 I’ve wo se en th rryin gly is h regu app lar en o n a basis !
- 35. Software architectures don’t live in isolation
- 36. Current Development Team Business Sponsors Future Development Team Your system Database Administrators Operations/Support Staff e e ctur r chit w are a for Soft pla tfor m ocia l! is a .. be s t ion . ersa conv Other Teams Security Team Compliance and Audit
- 37. O peration al View stem How does the sy nd support monitoring a management? ple diagnose How do peo problems?
- 38. Let’s wrap up...
- 39. “Enterprise Software Developer” ctical train ing course A fo ur-day pra g softwar e within an ab out buildin ructured, e environm ent in a st enterpris atic way. and pragm lightweight
- 40. Source Code Release Control Enterprise software developer Software Automated Unit Configuration Development and Integration Management Processes Testing Automated Requirements Load Testing Builds Architecture Continuous Operational and Design Integration Hand-over
- 41. simon.brown@codingthearchitecture.com @simonbrown on Twitter ! Th anks http://www.codingthearchitecture.com s re f or developer Softwar e architectu