■Performs software tradeoff analysis based upon the above inputs, capturing rationale for all significant architectural decisions.
■Responsible for documenting and maintaining the product line software architecture(s) Software Architecture
Documentation is specifically intended for the software development engineers. Deliverables include, but are not limited to:
- Software architectural rules (e.g. tasking methods, inter-component communication methods, etc.).
- Product line software decomposition including subsystem and component definitions
- Platform Reference Design: includes decomposition view and a collection of critical use case behavioral and collaboration views. Reference design shall be verified for correctness.
■Responsible for creating software implementation report (SIR), and product specific high level design (HLD) during platform development.
■Makes decisions involving tradeoffs and partitioning between software subsystems and provide technical analysis / reviews in support of platform software integration
■Leads design forum meetings with respect to platform development issues and general software architecture dissemination
■Ensures quality to platform software deliverables
■Aligns with software core teams to evaluate new technologies, suppliers, 3rd party software vendors etc. in support of product line architecture strategies
■Responsible for clarifying and / or resolving issues in the Product Line Architectures as raised by the core software team and software delivery team.
■Analyses defects and propose corrective / preventive actions for improved product quality.(product line level)
■Collection and cascading Lessons Learned (LLs) within product line and / or across product lines as appropriate
Required Skills and Experience
■Knowledge of the following: Dbus, SystemD, ALSA, Gstreamer, GENIVI.
■Hands on experience in Genivi platforms and OSS adoption and compliance
■Experience in Evaluation of SoCs, Linux distro and development tool vendors ) and assessment of partnerships for technology -development and scope definition (Make/Buy decision process).
■Experience in application/Communication frameworks facilitating component integration
■Experienced in leading Customer Quotes/Technical reviews (esp. Japanese OEMs )
Education: Minimum bachelor's degree in Electronics Engineering or Software
Engineering, or related field. Advanced degrees preferred
Language: Japanese & English