Identifying and Engaging Database Stakeholders During Requirements Gathering

DataSys+ · Database Deployment · Bởi Super Admin

Learn how to identify and engage all stakeholder groups when gathering database requirements, from end users to regulators.

Understanding Stakeholder Diversity in Database Projects

Requirements gathering is a critical step in the database design process, as it ensures that the database meets the needs of its users and applications. The first essential task is identifying the stakeholders who will end up using the database. Many parties may be interested in the database you are creating, and each brings unique perspectives and requirements to the project. Understanding the full spectrum of stakeholders helps ensure that the database design addresses all necessary business objectives and operational needs. Stakeholders range from those who directly interact with data to those who oversee compliance and governance, making comprehensive identification crucial for project success.

Direct Data Users and Technical Stakeholders

End users directly input or retrieve data from the database and represent the primary consumers of the system's functionality. Executive management uses data from the database to track operational performance metrics and inform strategic decisions, though executives most frequently use a reporting tool like Tableau, Qlik, or Power BI instead of interacting directly with the database. Data analysts use the database to perform complex queries, generate reports, and perform other data-related tasks, and may write SQL directly against the database or use reporting tools. Data scientists use the database to perform advanced analytics, develop predictive models, and gain insights into business trends and patterns. Application developers write applications that interact with the database using generalized programming languages like JavaScript, Java, C#, and Swift to create APIs, mobile applications, or web applications that store data in the database.

Infrastructure and Governance Stakeholders

Database developers write SQL to create tables, views, stored procedures, and other database objects, and occasionally may be involved in maintaining or upgrading the database. Database administrators (DBAs) are responsible for the ongoing maintenance and management of the database, including backups, performance tuning, security, and database upgrades. System administrators operate the virtual or physical servers where the database runs, performing typical tasks including sizing servers, allocating and configuring disk space, and operating system upgrades and maintenance. Beyond internal technical staff, customers usually interact with the database indirectly, using an application to submit orders or retrieve information, such as when looking at the location history of a FedEx package on the web. Vendors may use the database to manage inventory, track shipments, or perform other business functions related to their products or services, though vendors more commonly use an application rather than interacting directly with the database.

Compliance and Oversight Stakeholders

Regulators may require access to the database to ensure compliance with industry or government regulations, such as the Health Insurance Portability and Accountability Act (HIPAA) for healthcare databases or Payment Card Industry Data Security Standard (PCI DSS) for payment card databases. Auditors may review the database to ensure it meets internal or external audit standards, such as Sarbanes-Oxley compliance for financial databases. Legal teams may review the database to ensure compliance with legal requirements or to prepare for litigation. Once you have identified the relevant stakeholders, you can ask them questions during the planning phase to inform the database design and determine the total number of users who will ultimately use the database.

0.0 (0 đánh giá)

Thảo luận / Bình luận (0)

Chưa có thảo luận nào cho bài viết này. Hãy gửi bình luận đầu tiên nhé!

Vui lòng Đăng nhập để tham gia thảo luận.