Qna about Database-Life Cycle.
- myura dellya
- Apr 15, 2020
- 3 min read
1. Explain about 6 Life cycle database!
-System definition.
(Define the user and the application )
-Requirement collection and analyst.
( we need to collecting data and analyst users needs )
-Database design
(Designing database with conceptual,logic and physicly )
-Implementation.
(Determine the definition of database external, build empty database and implementation the software)
-Data & App conversion.
(saving file into the direct database and changing format file and upgrading the system )
-Testing and validation.
( testing the new system and validating it )
-Operation.
( operation of the software and database )
-Control and maintenance.
( During the stage of operational, system permanently stay in the monitor. Somehow there is a development of the system)
2. The first priority from the 6 life cycle database ?
Not only planning for the database we will apply, we also need to the first priority of database life cycle, that is Database design. From Database SDLC, designing is the key how good or not the database system we will build. We need to collect and analisis the data and then we build a good and fit design for the data. There is two important thing before we designing the system,
-Transaction Design
-User Interface Design
However we need to learn about 3 things to make a great design for our data before we testing it.
-Conceptual database.
-Logical database.
-Physical database.
Without knowing those things the data will be not fitting any design. If design wasn’t work while testing process, we need to analyst again the data, we need to collect again and making the design again. So I think we should be careful when we making design of database. 😊
3. Why the implementation-independent used during designing the system in conceptual scheme?
In conceptual data modeling, the overriding emphasis is on simplicity and readability. The goal of conceptual schema design, where the ER and UML approaches are most useful, is to capture real-world data requirements in a simple and meaningful way that is understandable by both the database designer and the end user. The end user is the person responsible for accessing the database and executing queries and updates through the use of DBMS software, and therefore has a vested interest in the database design process.
Take a note ER(is one of independent data model).
The purpose of conceptual data model:
· Provide flexible data-structuring capabilities
· Present a “community view”: the logical structure of the entire database
· Contain data stored in the database
· Show relationships among data including:
Constraints
Semantic information (e.g., business rules)
Security and integrity information
· Consider a database as a collection of entities (objects) of various kinds
· Are the basis for identification and high-level description of main data objects; they avoid details
· Are database independent regardless of the database you will be using
4. Why is the scheme and application done by parallel?
Because we want scheme design with a stable transaction. To avoid the complexity of the software so we have to do it right and step by step.
5. Why we need to collect data and analyst the needs ?
Because this is the key before we build a database, w e need to collect first then we analysis the problem from the data we have and after that we can make a solution. In this part we need to becarefull to collecting the data, if the data isn’t correctly, we cant find a good solution and the data is useless.
source:
PowePoint from Gunadarma University's lecturer Hasma Rasjid
Comments