A Trace in the Sand, Software Architecture Journal by Ruth Malan. April 2014 It's Me Day! Woohoo! What's a Trace? My Trace is a playground for developing ideas, for exploring architecture and the role of architects. It is a journal of discovery, and traces my active reflection. I've been journaling "out loud" here for over eight years. To get a sense of the span, calibre and contribution of this body of work, there's a selection of traces linked here. Oooo, look: I'm a people, I'm a people!!
And look what Peter Bakker did! Image by Sara B. No Point Left Unmassacred [my modus operandi] [The first bullet brought to you by Brenda Michelson. ] More? Oh. Here, have a meeting (via Kai Schlüter) My Trace. "Bang your head against the wall, to activate your brain" -- Thea, lyrics to a song about school :-) You're welcome. Um. “The primary indication, to my thinking, of a well-ordered mind is a man's ability to remain in one place and linger in his own company. 2. Abstraction Powertools Naming Architecture Sustainability Measuring Architecture Sustainability, Koziolek, H. Peeling Back the Onion Architecture - DevelopMentor. Download the code for this article. I recently started a consulting project as an architect on an ASP.NET MVC application and quickly found myself immersed in the world of N* open source tools.
MVC(which stands for Model-View-Controller) lends itself to an Agile development methodology where TDD and BDD (Test-Driven and Behavior-Driven Development) are important components. Writing applications that are testable requires that you separate business logic from presentation logic so that they can be independently tested. This is a concept known as separation of concerns (SoC), which, in addition to testability, provides other benefits, such as greater application longevity and maintainability. The life of an application is extended because loose coupling makes it easer to upgrade or replace components without affecting other parts of the system.
This is where the “Onion Architecture” comes in. The term was first coined by Jeffery Palermo back in 2008 in a series of blog posts. The Role of the Software Architect: Caring and Communicating. Magnus Mårtensson March 2008 Summary: The role of the software architect is a subject of much debate. In this article, I will discuss the qualities and personal traits of the ideal software architect.
I will discuss why it is critical that the architect be a caring person who values interpersonal communication above all else. This article describes the role of the software architect from the perspective of the ideal nature of a successful architect. My exploration touches the octopus/chameleon/parrot/bull-nature that is the heart and soul of the architect.
Table of Contents Architecture is user experienceArchitecture is negotiating and bargainingArchitecture is technologyArchitecture is formArchitecture is communicationArchitecture is artfulArchitecture is agileArchitecture is the creation of a better worldAbout the author Architecture is user experience Let’s start from the top: What the user of any piece of software sees, feels and experiences when touching the application.
CQRS. Scale. EA Roles - Enterprise Architecture. Brian H. Prince | Windows Azure, community, and architecture. TOGAF. How to move to business architecture, and a 'bigger picture' for SOA. At last week's ebizQ/TechTarget's SOA & Application Integration conference, Forrester analyst and SOA proponent Randy Heffner provided the following advice for moving to a business architecture-driven approach, which extends service orientation across the enterprise: It's about business capabilities, not technology: "Stop referring to applications by their primary technology," Heffner advises.
"Don't take that technology focus. Maybe you should refer to it as 'the system that partly does customer care,' or 'partly provides for the customer care capability.' Don't refer to it as 'the event-driven app' or what have you. "Business metrics: "Be sure that every key member of your project understands the business metrics. ," Heffner says. "Seeing the business metrics at a lower level is a key cultural shift, that gets people focused on the business rather than the technology. "Look at the big picture: "Develop a high-level draft capabilities map to find project synergies," Heffner advises. Four steps for selecting your development technologies | Programming and Development | TechRepublic.com.
Architecture Stacks.