Qiyu Chen

I agree with you. Encryption can be used for database design and implementation to protect the database from information security issues Encryption can be external encryption (referring to the encryption of the entire database, so that the database is not visible without the database credentials), data encryption (refers to the encryption of…[Read more]

I like you post. Yes, Database design is a complicated but necessary process. It involves creating a functional database system that can manage all the company’s information in one place.

I agree with you. People with business and technology can become bright spots between business and IT departments. But in general, business units and day-to-day employees should improve their needs and needs in order to achieve their business goals and efficiencies.

Making a database is a complex process that not only builds physical functions but also separates the different responsibilities of the data. Basically, I would like to know more about the senior managers or stakeholders of application requirements, and the design experts who understand good database design are very important in the process of…[Read more]

good point. The sequence diagram can be used to present a sequence for a specific use case; CRUD is an abbreviation for “create, read, update, and delete”, and the CRUD matrix is a table for displaying the main authority, which relates to the operation of each entity in the system;

I like your point. The CRUD matrix is a table that shows the functions in an application that contains SQL statements that affect various parts of the database. Combining a CRUD matrix with the analysis of possible user scenarios for a Web site is very valuable.

Thank you for sharing. using case diagrams show system behavior and key roles in interacting with the system In the integrated model.

good point. Each figure fits into a different group. Some of them are suitable for employees to learn, understand and train; some of them are suitable for managers to analyze, adjust and make decisions, etc.

I agree with you. Different charts have different functions to describe business processes. If an organization uses only one kind of chart, it will not be able to fully show the entire process of business activities

Each map has a different function. For example, the use case diagram is a representation of the user interacting with the system. The system displays the relationship between the user and the different use cases involved by the user; a CRUD diagram shows the type of processing a system performs on the data and represents each function in a matrix…[Read more]

I agree with you. Domain classes (things) are important components in the class diagram, they must work together with the user to be effective

Good post.Even though all participants read the same narrative description, each participant tends to have a different understanding of business units, services, roles, responsibilities, and functions.

I like your point. “Everyone has a different understanding of the same thing, it is also same for drawing diagrams. Because human has different views, orders, and thoughts to the processes, so the results been presented are different.”

I agree with you. For coupling, we can see how close the correlation between related classes and quantitative measures is; if two classes are tightly coupled, then there will be many associations and messages with another class. It is best to have loosely coupled classes.

I agree with you. In order to evaluate the revisions of these figures, it is important to evaluate the relationship between different subsystems because the class diagram describes the structure of the system.

When evaluating class diagrams, we reduced coupling. Coupling is a quantitative measure of the close relationship between related classes. The two classes are preferably loosely coupled, which means that the two classes do not have a large number of tightly coupled associations and messages. Cohesion is a quantitative measure of the focus or unity…[Read more]

I agree with you. Bypassing formal data analysis and moving directly into the design can lead to risks such as loss of data integrity and errors in data and applications. These risks will affect the cost and work efficiency during database development.

Good post. Most importantly, by conducting formal data analysis, the organization will be able to define the importance of these data and determine the appropriate level of security measures based on their importance.

I agree with you. If we do not analyze the data before designing a new database, it will affect data integrity and reduce work efficiency. If we analyze the data before designing a new database, it will help the organization to reduce errors, reduce costs, and improve integrity.

I agree with you. Formal data analysis will deepen understanding of business goals and direction. Based on this understanding, databases can be designed to better meet business needs.