Table of Contents

1 ABSTRACT 2

2 INTRODUCTION 3

2.1. Architecture Business Cycle (ABC) 3

2.2. Microsoft Windows Desktop Timeline 4

3 MICROSOFT WINDOWS 3.1 5

3.1. Relationship to the Architecture Business Cycle 5

4 MICROSOFT WINDOWS 95 7

4.1 Relationship to the Architecture Business Cycle 7

5 MICROSOFT WINDOWS 98 9

5.1 Relationship to the Architecture Business Cycle 9

6 MICROSOFT WINDOWS ME 11

6.1 Relationship to the Architecture Business Cycle 11

7 MICROSOFT WINDOWS XP 13

7.1. Relationship to the Architecture Business Cycle 13

8 CONCLUSION 15

9 REFERENCE 16

10 BIBLIOGRAPHY 16

APPENDIX 17

ABSTRACT

This paper is intended to define the software architecture, and the importance of software architecture for the software development. Here the highlighted topic is the Architecture Business Cycle (ABC) for Microsoft Windows Desktop operating systems, namely Windows 3.1, Windows 95, Windows 98, Windows ME and Windows XP. By applying ABC for each of the Windows, we are able to identify the architecture of Microsoft Windows, and to review how Microsoft Windows desktop operating systems evolve over the time. The ABC diagrams for each Windows summarize the influences from the stakeholder, developing organization, the architect’s technical environment and experiences, and the requirements or qualities over the process of developing the Windows.

INTRODUCTION

1 Architecture Business Cycle (ABC)

Software architecture is defined as:

“A program or computing system is the structure or structures of the system, which comprise software elements, the externally visible properties of those elements, and the relationships among them.” (Bass, Clements, Kazman, 2003).

Architecture is a key to quality, i.e. analysis of an architecture can be