The Software Architect is responsible for identifying the business and stakeholder (internal and external) requirements on the project.
This position is also responsible for the design of the entire system based on the received requirements, choosing the system architecture and each individual component of the system at a high level, as well as choosing the technologies for the implementation of each component and connections between the components.
The Software Architect is responsible for performing the process of designing the Software Architecture and checking its implementation throughout the project (i.e.
decomposition of SW functions and requirements to module level, specification of interfaces between SW modules and their interaction).
ESSENTIAL FUNCTIONS:
- Defines technical requirements and creates software architectural designs, ensures feasibility, functionality, and integration with existing and future automotive systems/platforms
- Participates in the selection of development/ test tools and environments to enhance overall the software infrastructure and ecosystem
- Designs the SW architecture
- Defines and approving module interfaces
- Conducts SW architecture reviews
- Collaborates with third-party vendors to evaluate and/or develop key software technologies required to offer comprehensive Software Development
- Contributes to the overall software quality by defining best-practice software engineering methods, including specifications, testing guidelines, and code-review processes
- Collaborates with other teams in an international setting and transfer knowledge gained on advanced technology
- Supports the System Architect when defining the System Architecture
- Supports the creation of the Software integration strategy
- Supports the planning of the architecture activities (e.g.
time effort estimations, etc.)
ADDITIONAL FUNCTIONS:
- Authorized to propose rejection of certain requirements to the SW Requirements Engineer and SW Project Manager, if they could cause serious problems in the SW Architecture, lead to instability, or would otherwise compromise important underlying architectural concepts
- Authorized to decide between alternatives within the SW architecture in cases where pros and cons, along with other decision criteria do not clearly indicate the best choice option
- Authorized to accept or reject a work product in the object reviews in which this role participates, if the topic falls into the expertise of this role
- Authorized to escalate obstacles for the SW architecture which cannot be resolved within the team