Hi I hope you are doing well. I am sending the new requirement, please go through it and let me know if you are comfortable.
*Position : Telematics & Infotainment Systems ArchitectLocation : Detroit, MI Duration : 6-12 months* *TASKS AND RESPONSIBILITIES:* *Security Lead Architect/System Role –* Lead effort to define security layers for telematics system including in-vehicle and back-office components. In addition to the description of the role above, this role will be lead or support the following tasks: • Sessions detailing use cases and to support project • Architecture development and documentation, would be involved in creation, critical review • System requirements creation and documentation, critical review • Failure mode analysis • Work with development teams in understanding system requirements • Trade off multiple implementation options balancing cost, performance, and complexity • Team deliverables are User Stories (Use Cases, Systems Requirements Documents, System Architecture Documents *Responsible for creating the following types documents:* SAD (Systems Architecture Document) • Block diagram level of various systems components comprising overall End-to-End ecosystem • Define all blocks necessary to provide launch feature set and ‘protect for’ features where reasonable • Denote blocks that are re-use, new, or modified • High level description of each block and function or behavior within the system • High level description of the interface between the architectural blocks • Define interface type at high level and information that is available • Any rules governing the relationships between blocks • Description of development ownership of various blocks • Used as a reference point for future systems development work *SRD (System Requirements Document)* • Takes requirements from BRD and breaks each into system level requirements for the various system components represented in the SAD • Form of the requirements will be guided by the needs of the development communities for each of the various system components • SRD will focus at a feature level and may represent more than one BRD when system synergies exist to combine multiple features • Contains sequence diagrams, detailed use cases and/or stories, call flows, lifecycle analysis • Where possible may be used directly by development teams or will drive detailed requirements generations -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Thanks&Regards James Miller | IT Recruiter ITBrainiac Inc, Princeton, NJ 08540 Direct: (609-935-3773)*101 | Fax 312.582.2699 Website:www.itbrainiac. Yahoo :james.usrecruiter Gtalk :james.usrecruiter Email : [email protected] Notice: This email contains confidential or proprietary information which may be legally privileged. It is intended only for the named recipient (s). If an.addressing or transmission error has misdirected the email, please notify the author by replying to this message. If you are not the named recipient, youare not authorized to use, disclose, distribute, copy, print or reply on this email, and should immediately delete it from your computer system list
