background preloader


Facebook Twitter


Mvc. Cab. Plugins. Multi-Tenant Data Architecture. SOLID Software Principles - Presentation And Code - Documenting your software architecture - why and how? NVelocity - NVelocity. How to build practical enterprise architecture team - Natty Gur. Enterprise architecture team might be the successful CIO right hand (especially in today economic situation) or a group of people that you can’t really understand what they are doing.

How to build practical enterprise architecture team - Natty Gur

A successful enterprise architecture group will help you to reduce IT costs, optimize IT operation, make better IT planning and keep the enterprise compliance with laws and regulations. The problem is that in order to build a successful enterprise architecture group, there is huge learning curve that CIOs need to go through. If you wish to reduce your learning curve significantly, keep reading. There are 5 main Steps that you have to understand and follow. Because each step influences the others, I tried to order them by dependencies: 1) Have a clear understanding what EA means for your enterprise. The term ‘Enterprise architecture’ has many definitions running on a scale that moves from a purely business oriented definition to a technological one.

Having the definition is not enough. Convention over Configuration in MSDN Magazine - Jeremy D. Mille. The February ’09 edition of MSDN Magazine includes my latest article entitled “Convention over Configuration.”

Convention over Configuration in MSDN Magazine - Jeremy D. Mille

Personally, I think this is an exciting topic and I really enjoyed writing on this subject. I hope this article can help to spawn some ideas and conversation about how we design configuration intensive frameworks. When we build systems, we’re trying to accomplish certain business goals, but to get there, we have to jump through hoops to satisfy infrastructural concerns. You could say that there are two types of code we write: The “Essence” of the system that satisfies our original business goalsThe “Ceremony” we have to go through to satisfy infrastructural requirements, the compiler, configuration mappings, and other drudgery I think that one of the next frontiers for .Net development is adopting and experimenting with techniques that allow us to accomplish the Essence of the system with less effort devoted to Ceremony code. A Sarcastic History Lesson. Patterns & practices: App Arch Guide - Home. J.D.

patterns & practices: App Arch Guide - Home

Meier, Alex Homer, David Hill, Jason Taylor, Prashant Bansode, Lonnie Wall, Rob Boucher Jr, Akshay Bogawat Objectives Understand the fundamental concepts of software architecture.Learn the key design principles for software architecture.Learn the guidelines for key areas of software architecture. Overview Software architecture is often described as the organization or structure of a system, while the system represents a collection of components that accomplish a specific function or set of functions. Figure 1 Common application architecture In addition to the grouping of components, other areas of concern focus on interaction between the components and how different components work together. Key Design Principles. Tools for Framework Architecture Verification. This is a suite of tools primarily aimed at validating the architecture of a framework.

Tools for Framework Architecture Verification

Currently, there are three tools: Deps: produces dependency diagrams between assemblies, based both on implementation, as well as API-only.Layering: verifies that a layering and grouping diagram is indeed satisfied by a set of assembliesPotentialCallers: lists all the methods that call, directly or indirectly, a set of methods. More documentation is included with the tool zip file (please see the Downloads section) Feedback is more than welcome! Please feel free to use the Discussions page. Note: the tools are built using F#. Evaluating and Improving Architectural Competence - A New SEI Pa. The Carnegie Mellon® Software Engineering Institute (SEI) recently published "Models for Evaluating and Improving Architecture Competence", an 87 page report that examines how software architects and organizations can foster environments that consistently produce high quality architectures.

Evaluating and Improving Architectural Competence - A New SEI Pa

From the abstract: Software architecture competence is the ability of an individual or organization to acquire, use, and sustain the skills and knowledge necessary to carry out software architecture-centric practices. Previous work in architecture has concentrated on its technical aspects: methods and tools for creating, analyzing, and using architecture. However, a different perspective recognizes that these activities are carried out by people working in organizations, and those people and organizations can use assistance towards consistently producing high-quality architectures.

The duties, skills, and knowledge (DSK) required of a software architect Identified duties included: (My) Default ASP.NET Architecture - Billy McCafferty. In developing any software application, it's important to keep things as simple as possible and add complexity only when needed.

(My) Default ASP.NET Architecture - Billy McCafferty

(I spoke about this in a previous post, Planning for vs. Reacting to Change.) On the flip-side, a certain amount of architecture may be assumed at the start of a project depending on the type of application being developed. Selecting an appropriate, default architecture provides your application with a solid foundation and offers guidance for other developers, and yourself, for further development. This entry describes a suggested, default architecture for data-driven, ASP.NET applications for both individual and team development. NServiceBus - Communications Framework for .NET. Bryan Wheeler, Director Platform Development at “Udi Dahan is the real deal. We brought him on site to give our development staff the 5-day “Advanced Distributed System Design” training.

The course profoundly changed our understanding and approach to SOA and distributed systems. Consider some of the evidence: 1. Months later, developers still make allusions to concepts learned in the course nearly every day 2. One of our developers went home and made her husband (a developer at another company) sign up for the course at a subsequent date/venue 3. If I were to do the whole thing over again, I’d start the week by playing the clip from the Matrix where Morpheus offers Neo the choice between the red and blue pills. Newsletter Index.