Service Architect / Java Architect

Title : Service Architect

Location : Detroit MI

Duration : 4 months

Top Three Skills/Experience:

1. Must know ISIM, Oracle IAM, and Java Development (4 - 6 years)

2. Communication (turn business requirements into technical design) (2 - 3 years)

3. Lead a small team of developers (1 ¿ 2 years)

Required Skills/Experience:

• Documentation experience of Use Cases, Software Architecture Documentation, UML, XML schema, WSDL for enterprise level services (8+ years).
• Service Oriented Architecture Design using WS-Security, SOAP/HTTP, WSDL, XML/XSD (Schemas) or other technologies (8+ years).
• Knowledge and participation of different types of testing (Unit testing, Integration Testing, Performance Testing) (8+ years).
• Knowledge of Enterprise and Software Design Patterns (8+ years).
• Excellent communication skills with various stakeholders from business consumer to technical staff. (8+ years).
• Lead development team from design to deployment of enterprise services (8+ years).

Preferred Skills/Experience:

• Developed Web Services/EJB in Java at some point in history. Has development background. However, candidate will not be expected to develop/code.
• Message Queue usage (IBM MQ preferred)
• Test Driven Development background
• Continuous Integration environment usage.

Educational Requirements:

• Bachelors degree in computer science, information systems, computer engineering, systems analysis, or related field required.
• Masters degree in computer science, information systems, computer engineering, systems analysis, or related field preferred.

Description

Service Architect is the primary designer of an enterprise service used by one or many consuming applications. The Service Architect should have the following:

1. Create release/iteration plan for service with help from Systems Integration Lead

2. Requirements gathering agile and/or waterfall, collaborate with consumers etc

3. Follow production release process

4. Come up with service design / architecture

5. Create/update Use case, Supplementary Spec, Software Architecture Documentation and backend mapping documents

6. Create/update WSDL/XML schema

7. Request review of WSDL/schema and get approval after making recommended changes

8. Present quality reviews of design and get approval after making recommended changes

9. Help developer understand design and guide them thru implementation/development. Will require some project management background to direct developers.

10. Validate/test service before turning it to consumers

11. Respond to any service related questions/issues/defects from consumers/business users; system integration and user acceptance support

12. Coordinate Performance test with developer(s), provider summary results to CS lead

13. Assist/guide developers with SDD and Consumer Guide documents

14. Create necessary documents and follow thru the process (change controls, checklists) for QA and PROD promotions

15. Update release notes document for Production releases

16. Transition service/component to production support

17. Is the primary face to face contact between project/business users representing the technical team. Liaison in understanding and converting business requirements into a technical solution.

18. Determine test cases from business requirements to support test first/driven development.

Essential Duties:

Author Documentation - Ensure implementations are properly documented within design documents. Create appropriate documentation to standards, XML schemas, WSDLs, Use Cases, Software Architecture Documentation, Service Mapping (i.e. map Service schema to backend source systems), Consumer Guide (i.e. end user documentation), and transition documentation to support team. There are also Service Level Agreements, Supplementary Specifications (i.e. non-functional specifications).

Ensure implementations are up to current standards for coding, naming, security, and versioning.

Requirements analysis with Consumers. Thus, working with business analysts, business users, technical teams (both Service and Consumer) to come up with a viable Services solution. Decide if an existing Service can fulfill the needs or is a new Service required. Coordinate with the Service consumers to resolve the issues related to accessing the services.

Research and become the Subject Matter Expert (SME) on the interaction of the Service with source systems as well interaction with the consumers (business users). When consumer wants to know what a Service does, how to call it and use it, they usually come to the Service Architects (SAs). Will need to become familiar with other Services not necessarily part of candidate¿s immediate project.-Define validation logic in the Services. For example, define required inputs, conditional inputs/outputs, and overall flow of logic in SOA Services. Map the inputs/outputs to backend systems.

Quality Reviews. Attend and present Service design (Use Cases and Software Architecture Document) to the rest of the Services team. This is required before building anything. Commonly known as a CS-QR (Common Service Quality Review). These last on average 2-3 hours (normally a Friday morning, but not limited to this day).

Schedule and moderate code reviews. Not required to know the code but should have knowledge of what the code is supposed to do from a design standpoint.

Lead the development team in the right direction. Will need continuous contact with the development staff and track/monitor what is being built. Oversight of defect tracking and issue fixing.

Delivery Oversight - assist in defining test cases (Unit/JUnit), mock, integration, and performance test cases. Coordinate and validate test case coverage and code coverage is complete. Ensure all IT processes and artifacts are completed. Thus, responsible for delivery of artifacts even if not personally completing. Oversight and delivery to higher environments (to production) is required.

If you are interested please contact on 734-418-0079.