Records Requirements in Enterprise Architecture
The purpose of this project is to create a common reference for records professionals and Enterprise Architects* about requirements for records processes and systems. The goal is to establish the records professional as a key stakeholder in Enterprise Architecture in order to:
- embed records requirements into organizational goals and systems planning at a strategic level
- strongly influence planning and systems design.
This is equivalent to the way that the Management Systems for Records (MSR 30300 series) products are designed for senior managers.
Enterprise Architects are highly influential in the creation of organisation-wide business requirements and in solution architectures. They create and maintain Enterprise Architecture Representations, usually made of multiple models or views that show how the current and future needs of an organization will be met in an efficient, sustainable, agile, and adaptable manner. Records requirements, principles and models should be stated in ways that can be readily incorporated into these Enterprise Architecture Representations in order to embed records processes and systems into normal business practice and into solutions designed by Solution Architectsǂ.
We currently have three objectives:
- Explaining the core concepts of records processes and systems to Enterprise Architects
- Explaining the core Enterprise Architecture concepts to records professionals
- Establishing a set of core records stakeholder requirements to be incorporated into Enterprise Architecture services.
The set of requirements is intended to be a Technical Report, and is likely to incorporate some of the concept explanations.
* Enterprise Architects work with stakeholders, both leadership and subject matter experts, to build a holistic view of the organization's strategy, processes, information, and information technology assets. The role of the Enterprise Architect is to take this knowledge and ensure that the business and IT are in alignment. The Enterprise Architect links the business mission, strategy, and processes of an organization to its IT strategy, and documents this using multiple architectural models or views that show how the current and future needs of an organization will be met in an efficient, sustainable, agile, and adaptable manner.
ǂ Solution Architects are assigned to a particular project or programme in an organization to ensure technical integrity and consistency of the solution on every stage of its life-cycle. They can get involved with all aspects and activities of an initiative: from concept definition, through requirements analysis and implementation, ending up with handover to IT operations and business-as-usual ongoing maintenance.