Business yst CBAP

Provide a short description of the Position: The Software Analyst will elicit requirements for development and implementation of DLMS for the NYS Office of Mental Health and other agency needs.

This project is an ongoing effort to build a new webbased application for the public to apply directly to the Office of Mental Health to fill several key directcare titles providing significant business process improvements in identifying and hiring OMH support staff.

This is a custom application development project already underway.

The application includes an externalfacing interface whereby applicants can submit their qualifications for prospective OMH employment and an OMH internal system for evaluating applicants maintaining eligibility lists and communicating with external applicants.

The NOD/Mail Log rewrite project aims to capture detailed asis business requirements of OMH legacy systems to be referenced by the developers tasked with rewriting these systems within modernized ITSsupported platforms. There is no existing documentation capturing the asis business requirements for these legacy platforms. The software analyst will be responsible for creating all asis and tobe documentation in a detailed manner as possible to support the development team throughout the entirety of the rewrite project for both NOD and Mail Log. Provide a list of the daytoday tasks to be performed by the Selected Candidate: Daily Tasks will include but are not limited to the following:

1. Work closely with the project manager ITS manager technical team members and other project stakeholders to provide guidance throughout the System Development Life Cycle (SDLC).
2. Work closely with other Business Analysts and the project team to identify and scope the stated business problem provide guidance and recommend/execute the best approach to problem.
3. Work as a liaison to stakeholders and Subject Matter Experts (SME) to elicit analyze communicate validate and verify the requirements for complex changes to current business processes policies and information systems and for the development of new business processes policies and information systems.
4. Conveys the demands of software users to the developers and ensures understanding of requirements through clearly articulated artifacts.
5. Create asis and tobe business process flows to ensure that the implemented business process and supporting software meets agency needs.
6. Conduct requirements workshops and JAD sessions with agency subject matter experts as one of the many techniques to be used to elicit requirements.
7. Create business requirements documents context diagrams business requirements document (BRD) system asis and to be states system specifications use cases and workflow diagrams report and screen mockups swim lane diagrams and prototypes.
8. Ensure that artifacts required by ITS governance process and Secure Systems Development Lifecycle (SSDLC) are created and support the project scope. 9. Manage requirements through the life of the contract using a requirements management plan and traceability matrix to ensure coverage between the source of each requirement and the test case(s) it will be tested by.