System Architect

Job Description

Job Description

Education Qualifications:

Bachelors or masters degree in computer science, management information systems or equivalent work experience and ten years of work experience in information technology, systems analysis, management analysis, program planning, program research, or program evaluation.

Required Qualifications:

Minimum 5 years of experience with .Net and Visual Studio.

Minimum 3 years of experience in programming in Microsoft ASP.NET and MS Framework 4.0 or higher.

Minimum 5 years of experience in programming with Oracle Web Forms and Reports.

Minimum 5 years of experience working with AES LIMS application and database components.

Experience with AES DIVAS components and program areas.

Experience with AES ICOMS components and program areas.

Experience and ability to work independently.

Experience working in a multi-development group.

Experience with object-oriented development techniques is required.

Excellent verbal and written communication skills.

Ability to communicate effectively with technical and user staff.

Ability to communicate effectively with management.

Candidate must follow FDACS standards and guidelines for application development.

Documentation of the solution for each item, with a narrative explaining what modifications were made, should be reported weekly.

Testing will be scheduled and coordinated by the Division Information Officer or designee with users for gathering information, testing, task verification and other aspects that require interaction with Division staff.

Testing will incorporate a test plan of asking the user to test the application, to provide the test steps the user is to take for testing each scenario of the corrected feature, form, report or functionality.

All code behind the forms, procedures, packages or other objects where code is written or modified will be documented as comments above or within the code and will include, at a minimum, the following:

• name of developer affecting code.
  
• date code was affected.
  
• explanation of what change was made and for what reason.
  

Change log requests will include a description of the events represented or actions taken on data by the scripts, packages or procedures in the request