Job title: Application Software Architect

Location: Ottawa

Type of work: Remote

Contact Term : 5 Years

Security Clearance: Reliability

Responsibilities:

1. Lead and develop technical architectures, Spring or .Net frameworks and strategies, either for an organization or for a major application area, to meet the business and application requirements;
2. Provide guidance or architecting solutions leveraging Cloud Technologies;
3. Design and implement database schema and integrate with the application;
4. Identify the policies and requirements that drive out a particular solution;
5. Analyze requirements and design solutions that fit into the organization enterprise architecture;
6. Prepare plans, charts, tables and diagrams to assist in analyzing or displaying problems;
7. Translate business requirements into an architected solution;
8. Recommend industry best practices to technology and business stakeholders;
9. Analyze and evaluate alternative technology solutions to meet business problems;
10. Ensures the integration of all aspects of technology solutions;
11. Analyze functional requirements to identify information, procedures and decision flows;
12. Evaluate existing procedures and methods, identify and document database content, structure, and application sub-systems, and develop data dictionary;
13. Define and document interfaces of manual to automated operations within application subsystems, to external systems and between new and existing systems;
14. Define input and output sources, including detailed plan for technical design phase, and obtain approval of the system proposal;
15. Identify and document system specific standards relating to programming, documentation and testing, covering program libraries, data dictionaries, naming conventions, etc.;
16. Facilitate architecture review sessions to document, design, architect, implement, customize, develop and integrate solutions;
17. Assist clients in obtaining governance and gating approvals related to development of the application(s);
18. Advise Business and Senior Management on trends and emerging technologies and the impact on client's and DFO's architecture and business strategy;
19. Provide strategic direction and guidance for projects in terms of architecture impact;
20. Provide architectural strategies, frameworks and roadmaps;
21. Apply Agile-Scrum 1 principles into Sprints 2 , participate in daily scrum stand-ups and sprint retrospectives;
22. Develop project documentation and architectural artefacts;
23. Conduct preliminary analysis and development of recommendations; and
24. Provide status reporting, plans, briefing notes and management presentations as required.

Deliverables:

1. Present application demonstrations to stakeholders as required;
2. Build and present solution architecture documentation;
3. Provide design solutions;

Resource Mandatory Technical Criteria

1.0

The Contractor must demonstrate, using Reference Projects(s), that the proposed resource has a minimum of one hundred twenty (120) months of experience within the past one hundred eighty (180) months as of the Task Authorization request date as an Application Software Architect in accordance with the TBIPS Supply Arrangement.

To demonstrate such experience, the Contractor must provide one (1) or more Reference Project(s) as defined in Section

1.0 of this appendix.

2.0

The Contractor must demonstrate, using Reference Project(s) that the proposed resource has a minimum of one hundred twenty (120) months of experience within the last one hundred eighty (180) months from Task Authorization request date, as an Application Architect for business implemented IM/IT Systems in technical environments which must include any one of the following:

1. Microservice
2. Event-driven
3. Web Services (REST & SOAP)
4. Client-Server
5. Model-View-Controller
6. Monolithic

The Contractor must include a description of how and which technical environments were used and how it was applied.

To demonstrate such experience, the Contractor must provide one (1) or more Reference Project(s) as defined in Section

1.0 of this appendix.

3.0

The Contractor must demonstrate, using Reference Project that the proposed resource has a minimum of eighty four (84) months of experience within the last one hundred twenty (120) months from Task Authorization request date, developing Java or .Net applications using access distributed relational databases such as: Oracle, SQL Server, PostgreSQL.

To provide context, the Contractor must include a description of the type of Java or

.Net applications and the distributed relational databases.

To demonstrate such experience, the Contractor must provide one (1) or more Reference Project(s) as defined in Section

1.0 of this Appendix.

4.0

The Contractor must demonstrate, using Reference Project that the proposed resource has a minimum of one hundred twenty (120) months of experience within the past one hundred eighty (180) months from Task Authorization request date, performing all the following tasks for business information management systems:

1. Object oriented analysis
2. Design
3. Development

To provide context, the Contractor must include a description of the tasks performed for each of the tasks for business information management systems listed above.

To demonstrate such experience, the Contractor must provide one (1) or more Reference Project(s) as defined in Section

1.0 of this Appendix.

5.0

The Contractor must demonstrate, using Reference Project(s) that the proposed resource has a minimum of eighty four (84) months of experience within the last one hundred twenty (120) months as of the Task Authorization request date, analyzing functional and technical requirements to establish the application architectural frameworks.

To provide context, the Contractor must include a description of the tasks performed in the analysis of the functional and technical requirements.

To demonstrate such experience, the Contractor must provide one (1) or more Reference Project(s) as defined in Section

1.0 of this Appendix.

6.0

The Contractor must demonstrate, using Reference Project(s) that the proposed resource has a minimum of thirty six (36) months of experience within the last ninety

six (96) months as of the Task Authorization

request date, using one or more of the following Cloud technologies:

1. Platform as a service (PaaS): Azure App Service, Google Cloud Engine, AWS Beanstalk;
2. DB as a service (hosted, managed DB services both relational (SQL Server, Postgres, Oracle) and noSql (MongoDB, Cassandra, Neo4J);
3. Enterprise Service Bus/Broker, Messaging (RabbitMQ, Apache Kafka - Azure Event Hub, Amazon Kinesis);
4. Containers (Docker), Container orchestration/run times (Kubernetes, Cloud Foundry);
5. Cloud authorization; solutions/providers (Oauth, OIDC, SAML - Azure AD, Amazon Cognito); and,
6. Hybrid on prem/cloud architectures
7. Continuous Integration / Continuous Deployment design and configuration (Azure Pipeline, GitHub Actions, AWS CodePipeline)

To provide context, the Contractor must include a brief description of the framework, environment or technology utilized. A description of what the technology was used for must also be provided.

To demonstrate such experience, the Contractor must provide one (1) or more

Reference Project(s) as defined in Section

1.0 of this Appendix.

7.0

The Contractor must demonstrate, using Reference Project(s) that the proposed resource has a minimum of sixty (60) months of experience within the last hundred twenty

(120) months as of the TA request date, using two (2) or more of the following web application development frameworks, environments and technologies.

1. Spring 4.0+, .Net Framework 4x+
2. Messaging Services
3. JPA/Hibernate or Entity Framework
4. Maven/Gradle or MS Build

To provide context, the Contractor must include a brief description of the framework,

environment or technology and how it was utilized.

To demonstrate such experience, the Contractor must provide one (1) or more Reference Project(s) as defined in Section

1.0 of this Appendix.

1 Scrum A lightweight, agile framework that has a set of roles, events and artifacts that allow teams to focus and commit to delivering value by breaking down work into short cycles called sprints

2 Sprints - Short, time-boxed iterations (typically two (2) - four (4) weeks during which a team works on a specific set of tasks