Thomas Koeppen Blog

ARCHITECTURE

from The Rational Edge: This introduction to the relatively new discipline of software architecture is the first of a four-part series on “architecting” in general. The author begins by defining the discipline’s key terms and goes on to explore what a well-designed architecture contributes to the environment in which it is deployed.

IBM’s Peter Eeles recent article he wrote in February 2006 some interesting aspects of What is software architecture?.

That’s like asking, what is culture? Culture is the way you do things in a group of people. Architecture is the way you do things in a software product. You could argue by analogy, then, that architecture is to a software product as culture is to a team. It is how that team has established and chosen its conventions.

One of the most important ways to think about architecture should be that it is an opportunity to provide leadership. The architecture embodies the decisions of the architects, the leaders, on how things should be done in the project. The architecture should make it easy for people working on the project to do things the right way: the way the architects believe things should be done. In other words, instead of just saying that things should be done a certain way, the architects should design architectural systems and structures that guide the team down that path.

REQUIREMENTS

Tyner Blain’s blog every worth reading about process, requirements, development as an artistic expression, quality, and HCI (human-computer interfaces). Never forget the Top five requirements gathering tips

1. Interviewing.
2. Brainstorming
3. Documenting use cases
4. Prototyping
5. Analyzing documents

No comments yet.

Comments RSS TrackBack Identifier URI