Architecture development steps

I used mind-mapping technique to represent and structure the architecture development
steps.

It is being influenced by TOGAF and RUP architecture development guidelines.

Software Quality vs Design Principle, Pattern and Practice Catalog

The Software System usually has many quality attributes, such as Maintainance, Performance, Security, Usabality etc. It is very important to have catalog of patterns, principles or other related practices which is being mapped to software quality attributes.

For example; I tried like this:

Utility Projects and Strategic Projects

I like the idea of project catagorization like utility projects and strategic projects. This helps organizations to spend their IT investments rather carefully; again it is inline with application portfolio of an enterprise.

But enterprise can really focus their energy and investments on strategically aligned projects so that competetive advanatages are more.

Architecture vs Design

Architecture is all about identifying the major components and its associations/responsibilities with right level of abstraction. It also involves taking decisions which are having system wide effect.
Where in design is all about constructing the software based on the context set by architecture. It involves choice of better algorithms, applying logic, patterns, reusable/generic blocks etc.

User story vs. Use case

Few things about the possible differences between these concepts
1) A user story is the title of one scenario, whereas a use case is the contents of multiple scenarios.
2) User story is written by customer before getting into actual conversation, where in use case is formal record of that conversation