System Architect

System Architect

The System Architect (Contractor) shall protect CalSTRS' best interests by working and collaborating closely with the CalSTRS' project management team and a third-party vendor to ensure that the third-party vendor has done their due diligence in managing the project and producing project deliverables and artifacts that meet CalSTRS' quality expectations in a timely manner.

The Contractor defines, analyzes and assists with the implementation of the architecture of a computerized system (i.e., a system composed of software and hardware) in order to fulfill business and technical requirements.

All deliverables and services will be provided in a diligent, professional, competent, and timely manner.

Tasks/Deliverables

1. The Contractor's tasks may include, but are not limited to, the following:

• Evaluate Technical Dependencies in Project Deliverables and Documents
• Assess Architecturally Significant Dependencies or Implications
• Analyze and Recommend Architecture Options
• Guide the Technical Implementation and Delivery from a System Architecture Perspective

Examples of anticipated deliverables include, but are not limited to, all the following:

• Review and recommend any potential revisions to deliverables/documents to include any technical dependencies/provisions;
• Review and recommend any potential revisions to applicable project deliverables/documents to incorporate all necessary technical activities and schedules;
• Impact Analysis of 'to-be' Business Architecture;
• Impact Analysis of 'to-be' Technical Architecture;
• Alternative Analysis of Architectural Designs & Options;
• Technical and/or Implementation Dependencies;
• One or more architectural options with trade-offs;
• Benefit(s), cost(s), risk(s), and schedule impact analyses for each architecture option;
• Client, analyze, document and communicate technical risks and architectural impacts;
• Raise and/or escalate technical issues and concerns in a timely manner;
• Enforce proper SDLC adherence;
• Timely communicate and resolve technical issues and risks; and
• Written weekly and/or monthly reports detailing various technical findings that may impact schedules, resources, and activities, etc.