1. Software Architect
Tomek Marszał
Wsinf 2016

2. Who is Software Architect
A software architect is a software expert who makes high-level design choices and dictates technical standards, including software coding standards, tools, and platforms. The leading expert is referred to as the chief architect

3. History
The software architect concept began to take hold whenobject-oriented programming (OOP) was coming into more widespread use (in the late 1990s and early years of the 21st century). OOP allowed ever-larger and more complex applications to be built, which in turn required increased high-level application and system oversight.

4. Responsibilities
The main responsibilities of a software architect include:
Limit choices available during development by
choosing a standard way of pursuing application development
creating, defining, or choosing an application framework for the application
Recognize potential reuse in the organization or in the application by
observing and understanding the broader system environment
creating the component design
having knowledge of other applications in the organization
Subdivide a complex application, during the design phase, into smaller, more manageable pieces
Grasp the functions of each component within the application
Understand the interactions and dependencies among components
Communicate these concepts to developers

5. Responsibilities
Recognize potential reuse in the organization or in the application by
observing and understanding the broader system environment
creating the component design
having knowledge of other applications in the organization
Subdivide a complex application, during the design phase, into smaller, more manageable pieces
Grasp the functions of each component within the application
Understand the interactions and dependencies among components
Communicate these concepts to developers
The main responsibilities of a software architect include:
Limit choices available during development by
choosing a standard way of pursuing application development
creating, defining, or choosing an application framework for the application

6. Responsibilities
Subdivide a complex application, during the design phase, into smaller, more manageable pieces
Grasp the functions of each component within the application
Understand the interactions and dependencies among components
Communicate these concepts to developers

7. Responsibilities
In order to perform these responsibilities effectively, software architects often use tools or standardized model and symbol sets such as Unified Modeling Language(UML) and OOP to represent systems or develop artifacts.

8. Duties
The role of software architect generally has certain common traits:
Architects makes high-level design choices much more often than low-level choices. In addition, the architect may sometimes dictate technical standards, including coding standards, tools, or platforms. Software architects may also be engaged in the design of the architecture of the hardware environment, or may focus entirely on the design methodology of the code.

9. Duties
The role of software architect generally has certain common traits:
Architects makes high-level design choices much more often than low-level choices. In addition, the architect may sometimes dictate technical standards, including coding standards, tools, or platforms. Software architects may also be engaged in the design of the architecture of the hardware environment, or may focus entirely on the design methodology of the code.

10. Responsibilities
In order to perform these responsibilities effectively, software architects often use tools or standardized model and symbol sets such as Unified Modeling Language(UML) and OOP to represent systems or develop artifacts.

11. Responsibilities
In order to perform these responsibilities effectively, software architects often use tools or standardized model and symbol sets such as Unified Modeling Language(UML) and OOP to represent systems or develop artifacts.

12. Responsibilities
In order to perform these responsibilities effectively, software architects often use tools or standardized model and symbol sets such as Unified Modeling Language(UML) and OOP to represent systems or develop artifacts.

13. Responsibilities
Subdivide a complex application, during the design phase, into smaller, more manageable pieces
Grasp the functions of each component within the application
Understand the interactions and dependencies among components
Communicate these concepts to developers