Benefits of DBMS Techniques

DBMS can store a lot of information or data in one place. The information is stored for many reasons. In the place of work, DBMS can be utilized to store a large quantity of important, and at times, confidential information, such as personal details and pay records and pay records.

Of all the benefits, security is a major issue (Sumathi & Esakkirajan, 2007). Data is limited only to people who are permitted to manipulate it, thus averting breach of information by dishonest individuals.

The DBMS speed is as well a huge benefit than having to search through a collection of papers to access certain information. Since information is kept on multiple computers using DBMS, handling data becomes much easier compared to paper systems. In addition, organizations employ DBMS to maintain information accuracy (Rob & Coronel, 2009). By doing so, such organizations are able to implement high standards.

This is important as it supports the organization in a number of ways, for instance, the data management responsiveness using DBMS is better than linear computer applications. For example, processes such as calculate, count and sum are automated with simplicity. In a DBMS, the applications to store, update and report the information are planned in an organized manner.  

With issues related to flat file systems, for storing data, I propose creating a Windows-based Information Management System that uses SQL Server. These technologies are appropriate to a multi-user setting, fulfilling the existing requirements and allowing for growth in the future. With a Windows-based Information Management System, all the paper and spreadsheets-based systems will be merged into a single system. Information will be ‘normalized’ to make sure it is kept in a well-organized manner so that information is not reproduced in the database.

Elicitation techniques include brainstorming, prototypes and workshops. Brainstorming sessions are employed to enable the stakeholders generate creative new approaches or ideas to a problem (Paech & Rolland, 2008). With prototyping, the Engineer uses partially completed software versions that have been generated to assist validate requirements. Workshops, on the other hand, are facilitated meetings with several stakeholders in order to draw out and also document requirements for the development of a new database.