[G-622] - PROJECT DESIGN AUTHORITY - PDA

Thales


Thales people architect identity management and data protection solutions at the heart of digital security. Business and governments rely on us to bring trust to the billons of digital interactions they have with people. Our technologies and services help banks exchange funds, people cross borders, energy become smarter and much more. More than 30,000 organizations already rely on us to verify the identities of people and things, grant access to digital services, analyze vast quantities of information and encrypt data to make the connected world more secure. **MAIN RESPONSABILITIES** At a technical level, is the maximum authority in the project. Responsible for general definition of design, scope and requirements, their traceability and delivery according to the personalized life cycle. Guarantees that the development of the solution is aligned with design authorized in the DVa document at all times. Leads the technical BID/design team from engineering, does teamwork with the Project Manager, Solution Manager and other stakeholders. May take over technical responsibility for one or more projects in parallel if needed. Specific Responsibilities Responsible for defining the design and product specifications of the customer's requirements to ensure that they are detailed enough for clean software development and to facilitate the validation process. Specifies the elements to be delivered at the beginning of the project (SW deliveries, documents, guides, training, etc.). Ensures that transversal requirements (eg security) are defined and applied in the design of the solution. Identify risks and opportunities and assess the feasibility of the project. Validate that the workload and schedule meet the project budget. Define the architecture of the solution. Proposes the engineering strategy to consider third-party deliveries or R&D; directly related to the development of software in the project: follow-ups, coordination of third-party software specifications, development and acceptance processes. Define the MTB strategy for each element, component or subsystem. Ensures proper communication and reporting for Project Manager, BID Manager, SM and other stakeholders. Define the amount of manpower (software related) required for RFPs, change requests and share all data with the project manager, BID Manager, SM and other stakeholders. Is the main interface with software architects. Is in charge of preparing the DVa coordinating the collaboration of the owners of each specialty, plus their own collaboration.

trabajosonline.net © 2017–2021
Más información