Solution Architect

Responsibilities will include:

         Identification of architectural solutions to meet the functional and non-functional requirements of initiatives.

         To de-risk proposed architectural solutions during the RUP Elaboration phase in coordination with the Corporate Solution Architecture (CSA) and Data Architecture (DA) groups.

         To demonstrate that requirements have been met through the use of working evolutionary prototypes.

         To complete and maintain the Software Architecture Document (SAD) and Reference Architecture documentation during the project lifecycle and provide traceability between proposed architectural solutions and the corresponding requirements.

         To select, reach agreement on, evaluate, prove and deploy architectural solutions and patterns to the software application development staff within the initiative.

         To collaborate with peers within other initiatives and within the corporate architecture team to reach consensus on solutions, to agree priorities and allocation of work in order to maximize the progress

         To champion the Object-Oriented Analysis and Design (OOAD) and Unified Modeling Language (UML) practices used by the Program

         To act as a point of liaison regarding architecture to various other roles within the initiative, including; project management, testing, software development teams and analysts.

         To ensure that product ownership requirements (for architectural components) have been identified and implemented.  The result of this activity being that the ERCB has sufficient capability to sustain and support new architectural solutions.

         Guide the design of reusable software components based on industry best practices and those defined in the Rational Unified Process Analysis & Design Discipline.

         To review design models prepared by the developers in support of the GRP development process.

         Identify, define, and document relevant software patterns and design mechanisms to be used to implement the underlying subsystems.

         To employ Application Lifecycle Management (ALM) tools to capture architectural models, trace to requirements, and synchronize application code.

         Participate in daily standup status meetings, estimating sessions and workshops to maintain a high level of understanding by the team to satisfy the software architecture requirements.

         To act as the GRP practice leader for the RUP disciplines of Analysis & Design, and Implementation.

Success in this role will be at the point where the necessary architectural components, patterns and standards are in place and are proven to meet both the functional and non-functional requirements of the initiative.

The successful candidate must have experience as the software/application/solution architect UML and OOAD on several successful software development projects. This experience should have built on several years of progressive industry experience as a developer, senior developer and architect. A range of experience in different technologies, not necessarily focused on Microsoft, would be advantageous, although recent experience must have been involved solutions built on a Microsoft technology stack.

 In general, key aspects of the role are:          

        .

         Collaboration with corporate solution architects and architects within other initiatives.

         To apply enterprise standards.

         To identify gaps in the current architectural stack with regard to the specific requirements of initiatives,

         Collaborate in the implementation of principles, standards, and guidelines on the proper use and deployment of .NET technology.

         Provide technical guidance, leadership, coaching and mentoring to the developers on the team.

         Identify other architectural issues and recommendations to improve our application systems environment. This includes current design patterns, component development and identification of common services.

Whilst not mandatory, architectural knowledge and experience with GIS, and in particular with ESRI ArcGIS will be an asset.

Proposed Commencement Date:	December 15, 2009
Expected End Date:	December 14, 2011