If you're in business, your company strategy, solutions and process are impacted by eBusiness and Internet technology.
In business-to-business (B2B) transactions in particular, the greatest impact of online commerce is not its size, but that technology changes the rules of the game.
Having said this, it's also been noted that although eBusiness architecture has been built on technology, it's not strictly about technology. In the same way, eBusiness architecture is not strictly about architecture. It's about what it takes to develop an eBusiness solution.
Think of eBusiness architecture as the ordering of your business design. Your role as the architect is to structure and shape the relationships between business components, so that the business process--and therefore the customer's experience--is as smooth and efficient as possible.
In this module, you'll learn about the role of architecture and the architect in eBusiness.

By the end of the module, you should be able to perform the following tasks:

1. Define architecture and its role in eBusiness
2. Identify the scope of the architect's role and responsibilities
3. Define the differences between the roles of the architect and the developer
4. Identify the viewpoint and perspectives of eBusiness stakeholders
5. Describe the primary business models available for eBusiness
6. Explain why service quality is part of an architect's responsibility
7. Apply quality metrics to a an eBusiness environment
8. Outline the key issues and concerns that an architect must address

The next lesson defines architecture and its role in eBusiness.