Reference library
APPENDIX N

Source Role Description Traceability

Excerpts of the authoritative role description this curriculum is built from, with a cross-reference to the modules.

About This Appendix

A.

Purpose of This Appendix

  • 1.This appendix reproduces the key excerpts of the real, authoritative Church workforce role description that this curriculum's content is built to align with, so that anyone building a future training or learning program from this document can trace a specific piece of curriculum content back to the actual job requirement it supports.
  • 2.Cite this source as·[Internal Workforce Role Description: Functional Analyst 1 - Hybrid, Job Code FNA1, Approved 12/15/2023].
B.

Position Title Note

  • 1.The official Church workforce title for this position is "Functional Analyst 1 - Hybrid" (Job Code FNA1).
  • 2.This curriculum deliberately continues to use "OFA" and "OFA 1" throughout, by explicit decision of the curriculum owner, rather than renaming the document to match the official title.
  • 3.Every fact, qualification, and responsibility below is drawn directly from the official role description, not invented for this curriculum.

Official Role Description Excerpts

A.

Purpose (Verbatim)

"This entry-level professional position fundamentally identifies, documents, and demonstrates the optimal technical and user experience. This is accomplished through requirements, activities/deliverables, and requirement-driven processes, which are aligned with the business requirements and solution scope. This position is primarily responsible for the design and development of fundamental solutions from the conception to implementation. This is an individual contributor role. This individual works with divine guidance to provide or support technology that furthers the mission of the Church and reflects the eternal impact of the gospel. We value early, mid and late-career candidates and encourage all applicants with the posted skills and abilities to apply."

B.

Responsibilities (Verbatim)

  • 1.Elicit, represent and communicate requirements through requirement-driven processes, written requirements deliverables, diagrams, flow charts, presentations, etc.
  • 2.Participate in functional testing and validation.
  • 3.Support requirement-driven processes and best practices.
  • 4.Initiate the launch of fundamental solutions after the design and development phase.
  • 5.Encourage a culture of user-centered design and knowledge sharing.
  • 6.Support analyst activities as needed.
C.

Qualifications - Required (Verbatim)

  • 1.Practical, relevant experience and/or applicable skills in emerging technologies will be given strong consideration and may substitute for years of formal education. Skills testing and project experience may be used for evaluation purposes.
  • 2.Bachelor's degree in related field or equivalent professional experience.
  • 3.Two years of professional, related experience.
  • 4.Working knowledge and application of two to four of the following competencies: Business Architecture, Business Analysis, Enterprise Analysis, Requirements Elicitation/Analysis, Solution Assessment/Validation, Requirements Management.
  • 5.Under supervision, may perform task-level work that is diverse and requires some complex functional analyst competencies.
  • 6.Intermediate knowledge of requirements elicitation and requirement-driven process and best practices.
  • 7.Familiarity with software needed, SaaS products, and with requirements and plans.
  • 8.Organization experience and understanding of technical and operational application functionality.
  • 9.Effective writing and presentation skills.
  • 10.Professional environment; possible physical requirements (sitting for long periods, computer monitors/equipment).
D.

Qualifications - Preferred (Verbatim)

Left blank in the official role description template; no preferred qualifications are specified beyond the required qualifications above.

E.

Note (Verbatim)

"The specific statements shown in each section of this Workforce Role Description are not intended to be all-inclusive but instead represent typical elements and criteria considered necessary to successfully perform the job."

Curriculum Cross-Reference

A.

Cross-Reference Map

The table below maps each of the six official responsibilities above to the module or modules of this curriculum built to develop it, so a curriculum reviewer can trace coverage directly.

Official ResponsibilityCurriculum Coverage
1. Elicit, represent, and communicate requirements through written deliverables, diagrams, flow charts, and presentationsModule 4 (Contributing to Requirements Documentation, including its Requirements Deliverables Take More Than One Form section) and Module 5 (Discovery and Communication Basics)
2. Participate in functional testing and validationModule 7 (Supporting Testing and Validation)
3. Support requirement-driven processes and best practicesModule 1 (Four Stewardship Areas) and Module 3 (Learning OFA Terminology and Team Processes)
4. Initiate the launch of fundamental solutions after the design and development phaseModule 8 (Supporting the Launch of Fundamental Solutions)
5. Encourage a culture of user-centered design and knowledge sharingModule 5 (Encouraging a Culture of User-Centered Design and Knowledge Sharing) and Module 6 (Documentation as a Culture of Knowledge Sharing)
6. Support analyst activities as neededModule 2 (Role Definition and the Six Core Behaviors) and Module 9 (Working Under Direct Guidance)
B.

General Church Workforce Requirements

The general Church workforce requirements referenced in the official role description - a current temple recommend if endowed or a temple worthiness certification if not, living the teachings of Jesus Christ and Church leaders, honesty and integrity, supporting ecclesiastical leaders where applicable, serving as a role model, and regular, timely attendance - apply to this position as they do to all Church employment, and are outside the technical scope this curriculum addresses.