Database and design development, Study notes of Computer science

Download Database and design development and more Study notes Computer science in PDF only on Docsity!

DATABASE DESIGN

DEVELOPMENT

By: Ibrahim Zitouni

[DATE]

[COMPANY NAME]

[Company address]

Contents

Introduction I am currently employed in a software development company called Emtech where I have been hired as

• Introduction.................................................................................................................................................
• querying across multiple tables................................................................................................................... Developing the database system with evidence of user interface, output and data validations, and - Referential Integrity.............................................................................................................................
  • Cascade Update and delete.....................................................................................................................
• Data validation.............................................................................................................................................
  • Input mask...............................................................................................................................................
• Implementing queries................................................................................................................................
• Test the system to see if it meets the user and system requirements......................................................
• Table testing..............................................................................................................................................
• Primary Key Testing...................................................................................................................................
• Query Testing............................................................................................................................................
• Report testing............................................................................................................................................
• Non-Null Testing........................................................................................................................................
• Forms Testing............................................................................................................................................
• Form testing..............................................................................................................................................
• Test Model.................................................................................................................................................
• Producing technical and user documentation...........................................................................................
• User Manual.............................................................................................................................................. - Table.................................................................................................................................................. - Queries.............................................................................................................................................. - Forms................................................................................................................................................. - Reports.............................................................................................................................................. - Conclusion.........................................................................................................................................
• References.................................................................................................................................................

You should repeat the same process as many times required to fil out the table. It is also important to save the table in order to keep the modifications made in the table. Making a table in design view In order to make table in design view you need to do the following: click on the “Home Tab”, under it you should find the “View” tab, then click on “Design View”. I will provide screenshot of this process below: When Design View is opened, a new table appears. Press Enter after entering a field name in the Field Name column. I will show screenshot below

Then set the data type necessary for field name, I will now provide screenshot below: You should provide the same process for all the different field types you make. It is then essential to save your table to save the changes you make.

Referential Integrity

Before I construct forms, I create a relationship table. Referential integrity is my responsibility. Access relationships enable users to add information from two different tables. In each relationship, two fields from two different tables are linked together the purpose of referential integrity is to prevent orphan records, which are records referring to records that no longer exist.. Activating referential integrity for a table relationship enforces referential integrity. The referential integrity of a table relationship is protected when Access is enabled.

Cascade Update and delete Users can delete records from one table and have entries in the other table deleted as well. Known as cascading updates and deletions. Select Relationships from the Tools menu in the Database window. Double-click the line between Course IDs to switch between them. After users have only selected the Cascade Update Related Fields option, click OK. Close the Relationships window. Data validation It is showing an error because I added a validation rule so there is no confusion when it comes to gender.

above shows me using placeholder character for the phone numbers. I will now go on to the next step. The next screenshot show if I would want to put the first three digits in brackets. after I made that choice I will finish the input mask. I am now going to show how I made the forms on my database. The first step would include going to the “Create” tab under that I would click on form wizard.

As shown above I would click on the form wizard. I would then click on the “next” button which it would proceed to what type of layout I would decide to go with. After that I could either change the name of my form or I could leave it to what originally. Access also gives me the option to change the design of the form to make it more suitable or change the design to what access would give me.

This is what the form looks like in the design view as I have edited the form to look more better and readable. I will now move on to the how Login details and how I made the form. I used the same way as I did for the Courses form.

I will now click on “Next”. I will now click on the first option.

The next form I will show that I made is the Student form. I will once again use the same procedure as I did for the other forms. I will now click on “next”.

I will now use the second option instead of the first because I think it looks more neater in the tabular layout instead of the columnar. This is the result th a t access have given me, as shown above it is not neat all and does not present itself as being done professionally, in order to fix this I will have to open the form and fix the problem.

I then clicked on next. This time, I switched backed to the columnar layout because I think its suits the format to the table.

I then clicked on the ‘finish’ button. Upon glance I think the form columns are too close together so I would modify it to make it look neater. I will now show the screenshot of the form in design view.