Section 1 - The beginning
Introduction
Section 2 - Modelling
Chapter 1: Modelling with UML
Section 3 - Delivering Software
Chapter 2: The WaterfallChapter 3: InitiationChapter 4: Requirements gatheringChapter 5: AnalysisChapter 6: A Design primerChapter 7: DesignChapter 8: Visual DesignChapter 9: Writing codeChapter 10: Releasing software
Section 4 - Approach and people
Chapter 11: Iterative, incremental methodsChapter 12: Managing the environmentChapter 13: When can I have it?Chapter 14: The way of the SAChapter 15: Patterns & antipatternsChapter 15a: Show me your architectureChapter 16: Enterprise architectureChapter 17: Where do we go from here?
Section 5 - Aardvark & Aardvark, Solicitors
Chapter 18: The Aardvark & Aardvark assignment
From here to software architecture
There is a tremendous amount of software being developed for an equally hugeamount of reasons. Unfortunately, in this high technology, leading edge,paradigm-shifting world of computing, we have forgotten the original promise of technology. It was meant to make our lives easier.This book is about how individuals can take the lead in realigning ourdevelopment efforts to that promise. In doing so, we shall in turn take our leadfrom the practice of Architecture, when Architects formed themselves into
organisations determined to combat the problem of buildings falling on people’sheads.The change is already underway. The position of Software Architect, or a similartitle, has been created by many organisations in the realisation that softwaredevelopment needs to be led by a single mind, or more accurately, by a singlevision. This book will guide you to the skills you need to become a softwarearchitect and survive as one.
Who needs software architects?
If, for a fleeting moment, you imagine a city built the way we build our software,it would be a city of uniform greyness. It may or may not include a water system,depending on whether or not one was asked for. Ninety percent of the buildingswould remain unfinished, or would have toppled to the ground as unsalvageablewaste for want of better foundations.Traffic would flow, but only because someone had found a giant to lift cars fromthe end of one jam and place them at the foot of another. And as you know, thecars would rarely fit the roads. Worst of all is the unending string and continuousmaintenance required to hold the buildings together.There in the midst of this rubble, picking a way through the web, walks thehastily hired architect with a simple brief: 'Please make our rubble into theglorious living spaces we imagined.'Before you enter the city, I should warn you, we haven't yet looked at thebuildings. The doors are not where we want them, and no-one measured aperson to see if they would fit in.Now you may argue this is not quite the case, but no-one can be sure. IT failuresare largely invisible to those outside the city walls.Enter the Software Architect. The Software Architect teamed with a BusinessAnalyst will extract, define and create a software architecture to deliver yourneeds. Then matched with a Project Manager, will control the technology and flowof development while the Project Manager controls the timelines and risks.At the highest level, the Software Architect will work with the sponsor to identifyarchitectural requirements while the Business Analyst identifies the businessrequirements. Together they will model the process the software must fulfil, andthe means by which it will do so. The sponsor will then identify those who haveinput into the project, and the model grows as it moves down through the ranks.Detail is added as appropriate, and when the model is presented to development,the architectural process moves from one of vision and design to one of management.In organisational structures, a Software Architect will begin to layer developmentefforts. A team of a hundred will have a Senior Software Architect, and furtherSoftware Architects who lead individual projects or manage specific areas of
expertise. Senior developers will take the Software Architects' models andconvert them to skeleton code for junior developers and specialists to complete.Doing so will make development run more smoothly, be more controlled andmore measurable. It is the job of the Software Architect to ensure standards arebeing met and that development plans are adhered to.At present, software development teams have little hierarchical structure. Puttingin place an architecturally led process will give the development teams a clearercareer path and career choice. Instead of the traditional Developer, Team Leader,Development Manager, they will see Developer, Senior Developer, SoftwareArchitect, Senior Software Architect. They may choose to become TechnicalSpecialists, or follow the more traditional path of Team Leader then DevelopmentManager.As more of us become Software Architects, we will begin to conform to thestandards of the Software Architect community. This, in turn, will meanbusinesses begin to manage the processes and techniques of softwaredevelopment as they would manage any other discipline, from accounting toproduct development.For business leaders, Software Architects will be looking over the horizon whenmodelling systems. We will be looking at new technologies, and the businessmilestones you wish to cross and hurdles you must jump to get there. It alldepends what you want in your software, more hurled up skylines or morebeautifully crafted cathedrals.
What does a software architect do?
Figure 1.1. Joe
Meet Joe. Joe is the product of long years at the forefront of softwaredevelopment. One day, perhaps we will have a Joe in every organisation. For now,he is a mythical being, a shining light on the horizon towards which we mighttravel.If the description of Joe overwhelms you, fear not. You will be a SoftwareArchitect long before you are Joe.Joe is the perfect Software Architect. We can define him by who he is and whathe does.
Who Joe is
Search History:
Result 00 of 00
00 results for result for
p.
Notes
Load more
