Professional Behaviour - Databaseof Stakeholder Networks

Designing and accessing databases gives career practitioners access to a range of networks that can benefit their clients.

CPD Assessments
Professional Behaviour - Database of Stakeholder Networks

Professional Behaviour - Database of Stakeholder Networks

Case study

Paul has been working at a local company for the last year. Recently, management decided to run several training programmes as part of a drive to improve employee skills. Paul is keen to participate in the Microsoft Access programme, which focuses on how to create a database using Microsoft software. Through the programme, he comes to understand what a database management system is, the benefits of using one, and the phases of the database lifecycle.

Paul is pleased that his company gave him the opportunity to learn new skills, and is glad to know he can transfer them should he start a new job. He also realises there are many other ways to access and create databases, such as through spreadsheet software, and takes the time to learn about the different options available.

How do I design a database?

Database design refers to the organisation of information and data according to a database model. The person designing the database decides what data will be stored. A database has a lifecycle made up of six phases:

1. Initial study. The designer examines the situation, describes the challenges, outlines the goals, and determines the scope of the design.

2. Design. This phase focuses on the database model itself and is considered the most critical phase, as the designer must ensure the model meets the requirements of both the system and its users.

3. Implementation and loading. This phase involves implementing all the design specifications, such as domains, views, storage and other instructions created during the design phase.

4. Testing and evaluation. The designer tests, tunes and refines the database to ensure it is functional and meets expectations.

5. Operation. Once a database has passed testing and is considered functional, it becomes operational, encompassing management, users and all associated application programmes.

6. Maintenance and evolution. The database administrator must maintain the database on an ongoing basis. This includes:

   - regularly backing up the system;

   - maintaining the system to ensure recovery is straightforward;

   - carrying out constant performance checks;

   - managing access permissions; and

   - maintaining user accounts (both old and new).

Conclusion

Creating an effective, user-friendly database has never been simpler. Platforms such as Microsoft Access and Excel enable individuals to create straightforward, reliable databases that support multiple users while minimising redundancy.


Author

Sacda

Assessment Reward

You can earn 0.50 CPD point/s by completing and passing the self-assessment questionnaire for this article.
0.50

Take the Assessment