DEVELOPING HIGH-LEVEL REQUIREMENTS. The high-level requirements define documents and tracks the necessary information required to effectively define impact, scope, business, application, design, interdependencies, technical, functional and non-functional requirements. The Requirements Definition document is created during the Planning Phase of the project. Its intended audience is the project manager, project team, project sponsor, client/user, and any stakeholder whose input/approval into the requirements definitions process is needed. Below is a brief description of the requirements stated for each registry: • Scope: Outlines the project goals, features, activities, deliverables, timeline and cost of a project • Business requirements: Defines project objectives, criteria, facts, assumptions, risks, constraints, business processes for project success • Interdependencies: Describes the relationships between project tasks. A prior task must be completed to enable the succeeding task to be performed • Security requirements: Outlines security policies and procedures to minimize potential risks and have the ability to respond to security incidents • Design requirements: Defines the project components, capabilities and methods for development • Technical requirements: Outline the technical issues such as reliability and and availability to be considered for a successful completion of project • Data requirements: Outlines data standards and reporting for quality assurance • Functional requirements define the system components function while the non- functional requirements describe the characteristics of the system. • The business requirements identify business needs, stakeholders, requirements and others for better understanding to influence decisions that guides the implementation of the proposed project. • The technical requirements outline the technical issues such as reliability and performance that has to be addressed to successfully build and utilize the registries.
