One of the first steps in developing any kind of software is identifying who your users are. This then allows you to incorporate elements that are important to them, and grants you insights into how your target audience would use, or attempt to use, your program. In the case of database systems, however, the gamete of users varies dramatically.
Some of the users of a database system could be any of the following: An enduser, a programmer of application software, a database administrator or a designer of database management system. Clearly, each of these users have very different concerns when they access a database, and one of the key skills necessary to both understanding and designing databases is to understand these roles. In this Assignment,
you will identify what types of users are concerned with specific scenarios noted in the Assignment instructions.
To prepare for this Assignment: Review your Weekly Learning Resources with a focus on database characteristics and access
conditions.
Analyse the concerns of the following database system users: enduser, programmer of application software, database administrator, and designer of database management system software. Analyse the characteristics of a database and infer how each user type would utilise them. Reflect on the following questions, and which user would be most concerned with each:
- How should data be stored on a disk to maximise efficiency?
- Is there a vacancy on flight 243?
- Could a relation be stored as a sequential file?
- How many times should a user be allowed to mistype a password before the conversation is terminated?
- How can the PROJECT operation (of the relational model) be implemented?
To complete this Assignment:
Submit a 23
paragraph paper in which you address the following:
- Identify the user (enduser, programmer of application software, database administrator, and designer of
- database management system software) who would be most concerned with the following scenarios:
- How data could be most efficiently stored on a disk.
- If there is a vacancy on Flight 243.
- How a relation could be stored as a sequential file.
- How many times a user should be allowed to mistype a password before a conversation is terminated.