Relational Database Management System (RDBMS

Added on - 05 Apr 2021

  • 43

    Pages

  • 8083

    Words

  • 26

    Views

  • 0

    Downloads

Trusted by +2 million users,
1000+ happy students everyday
Showing pages 1 to 8 of 43 pages
DATABASEASSIGNMENT
DATABASE2018Table of ContentsTask 1 [ P1]............................................................................................................................................3Introduction:...........................................................................................................................................3Prerequisite Specifications:....................................................................................................................4Flaws of the old database system:..........................................................................................................4Design of a relational database system:.................................................................................................5Entity Relationship Diagram:.................................................................................................................5ER Diagram Symbols:............................................................................................................................6ER Diagram For Patient Record System:...............................................................................................6Relationship Diagram.............................................................................................................................7Data Dictionary:.....................................................................................................................................8Conclusion:..........................................................................................................................................10Task4/P2...............................................................................................................................................10Introduction:.........................................................................................................................................10Data Validation....................................................................................................................................11Constraints............................................................................................................................................11Primary Key.........................................................................................................................................11Foreign key:.........................................................................................................................................11Unique Key..........................................................................................................................................11Not Null Key........................................................................................................................................12Implementing Necessary Constraints...................................................................................................12Primary key..........................................................................................................................................12Unique Key..........................................................................................................................................13Not null Key.........................................................................................................................................13Evidence of user interface and data validation....................................................................................14Snapshots of login page and error message.........................................................................................14Snapshots of data entry forms..............................................................................................................14
DATABASE2018Validate data querying multiple tables using joins..............................................................................15Conclusion............................................................................................................................................17Task6/P3...............................................................................................................................................17Introduction..........................................................................................................................................17SQL......................................................................................................................................................18Basic Query Languages:......................................................................................................................18Insert Statement....................................................................................................................................18Examples..............................................................................................................................................18Update Statement.................................................................................................................................21Delete Statement..................................................................................................................................24Product table.........................................................................................................................................24Select Statement...................................................................................................................................27Conclusion:..........................................................................................................................................28Task8/P4...............................................................................................................................................29Introduction..........................................................................................................................................29Testing of Stock Management System.................................................................................................291.Insert.............................................................................................................................................292.Update...........................................................................................................................................30Test Log...............................................................................................................................................33Conclusion............................................................................................................................................34Task11/P5.............................................................................................................................................34Introduction..........................................................................................................................................35Technical Documentation....................................................................................................................35Introduction..........................................................................................................................................35Overview..............................................................................................................................................35Constraints/Risks..................................................................................................................................36User Documentation.............................................................................................................................36
DATABASE2018User Manual.........................................................................................................................................36Introduction..........................................................................................................................................36Login Form...........................................................................................................................................36For Inserting data.................................................................................................................................37For updating data..................................................................................................................................39For deleting data...................................................................................................................................40Conclusion............................................................................................................................................41Bibliography.........................................................................................................................................42
DATABASE2018Task 1 [ P1]Design a relational database system using an appropriate design tools and techniques,containing at least four tables, with clear statements of user and system requirements.Introduction:Stands for "Relational Database Management System." A RDBMS is a DBMS plot especially forsocial databases. A relational database refers to a database that stores data in a composedarrangement, using lines and sections. This makes it easy to discover and get to specific qualitiesinside the database. It is "relational" because values inside each table are connected with each other.Tables might be connected with different tables. The relational structure makes it conceivable to runinquiries over different tables on the double.The management system of a stationary shop means to make a database in order to keep records ofall data about product, Purchase, sales and so forth. As a junior database administrator I was enlistedto design a relational database system of the stationary shop.In this task I have designed a relational database system of the stationary shop incorporating clearprerequisites of both, user and system. Be that as it may, before designing an alluring and interactivedatabase I required data about the stationary and its working system. Without procuring data aboutthe stationary and its management system the important database design was very unthinkable. Inthis way, to design a compelling and productive database that can satisfy every one of the necessitiesof stationary management I utilized beneath specified apparatuses and strategies:Interviews:Like surveys, interviews are the crucial strategy in gathering data about the current system.Different questions are advanced among the members of the system straightforwardly togather data about the system with respect to the issues and changes required in it. We metwith every member of the stationary exclusively and addressed them about the presentsystem, challenges they are confronting and changes required in the present system to expeleach one of those troubles.Observations:Observation is likewise an accommodating methodology for accumulation of informationand data about any system. After observing the structure of a system, an essential idea aboutit can be obtained. We observed the work place, stationary records, sales records, purchase
DATABASE2018records and working days of members deliberately which help to design the database of thestationary management system. We even observed the old database management system ofthe database and made notes about confinements of the current system and redesignsrequired in it. Observation helped us to think about the correct state of the old system andchanges that are required in the new system.Prerequisite Specifications:The diverse management system has numerous necessities and requirements that are should havebeen satisfied. After breaking down all the gathered data utilizing the above strategies andmethodology we investigated the different necessities that are required in the stationary managementsystem. The old database systems had different limitations and confinements which were shouldhave been overcome. The users and new connection database system included after prerequisites:i.To keep enrollment points of interest of item, buy and deals.ii.To keep rundown of all the customer with their address.iii.To show rundown of the considerable number of customers.iv.To track records of the new clients.v.To ascertain add up to number of customer that were suffered by a specific illness.Flaws of the old database system:After analyzing the needs and requirements of the users and system with detailed examination of theold system function procedures and methods I have pointed out the limitations of the old databasesystem:i.Use of old database system with limitations and inaccessibility of new highlights.ii.Difficulty in overseeing documents and records because of poor illustrations.iii.Unable to track records of customer with their genuine address.iv.Difficulty in generating reports of the patients as the information were notstandardized.v.Problem in seeking patients and customer by utilizing their ID as the outside keyswere not utilized.Design of a relational database system:
DATABASE2018A design is a work procedure in which greeting or conceptualization is kept into setup, configuration,display, pattern, plan or part in light of particular customer design. To meet specificmatters a designis made. The design that will be utilized as a part of full setting must be alluring, satisfy thenecessities of the users and good to the earth. With a mean to design an interactive and appealingsocial database system satisfying every one of the users and system prerequisites following design ofstationary uniquely quiet record system has influenced utilizing Entity Relation To diagram (ERDiagram).Entity Relationship Diagram:Entity Relationship Diagram, also called Entity Relationship Model is a visual representation ofdifferent data using conventions that illustrates how entities relate to each other within asystem[ CITATION erd18 \l 1033 ].It is a graphical portrayal utilized as a part of processingregularly for organization of data. ER diagram are oftentimes utilized amid advancement organizeprocedure to distinguish different components and their relationships with each other.Relationships between Entities:A relationship demonstrates how different entities are relationship with each other. There arefour sorts of relationship between elements:One-to –one:The relationship can be one-to-one when just a single occasion of an element is related withother example of another substance. In understanding record framework, a patient has onespecific address.One-to-Many:The relationship can be one-to-many when one instance of a substance is related with one ormany instances of another element. In persistent record system, a customer,sales and stockhave one or many contact numbers.Many-to-One:The relationship can be many-to-one when many instances of an entity is related with onecase of another element. In stuck record system, many customers can be related with onesingle system.Many-to-Many:The relationship can be many-to-many when one occurrence of a substance An is relatedwith one, zero or numerous cases of element B and another case of element B is related withone, zero or numerous cases of element A. In understanding record framework, numerouspurchase may visits numerous sales
DATABASE2018ER Diagram Symbols:In ER Diagram various symbols are used to represent the information of the system. Differentsymbols different elements:Rectangular Boxes represents entities.Circle represents attributes.Diamond represents relationships.ER Diagram For Patient Record System:Fig: ER diagram of Stock Management SystemRelationship Diagram
desklib-logo
You’re reading a preview
Preview Documents

To View Complete Document

Click the button to download
Subscribe to our plans

Download This Document