[Relational data modeling] 2. Task analysis for relational data modeling (requirements analysis)

 

Intro

This article deals with the first step of relational data modeling, task analysis (work identification, requirement analysis). We're going to do it sequentially!

 

Hope you enjoy it!

 

What is Business Analysis (Requirements Analysis)?

It means an analysis of the screen and function to be developed. Requirement analysis determines the purpose of the database and creates a requirement statement accordingly. In the case of me, who is a PM and is planning together, I often put the screen and analyze the screen with the backend developer to draft the schema. Or they're going to take what they've caught and run the simulation around to optimize it, etc.

 

The work analysis conducted here can be seen as a step of thinking about which screen and work process to analyze and what relationships and attributes to manage. That is, it can be said that it is the first step in which the definition of relation and attribute is made.

 

 

How do you do it?

The analysis is conducted by looking at the planning specification, requirement specification, or storyboard for development.

 

From the PM's point of view, it is important for developers who conduct business analysis in the process of analyzing this work to understand as well as possible what PM has planned. So backend developers have to bully PMs or planners in the beginning. Because the right DB can come out only when they understand what intention and process they planned this screen in sync with PM.

 

 

Conclusion

In relational data modeling, task analysis is the most basic task and must be done well without missing it meticulously. This is because physical modeling has been completed while missing the analysis, but if there is a case that it needs to be modified later, it may have to replace the planned relationships.

P.S.

As a product manager, I actually experienced while working on a project, and when a backend developer discovered that it was missing while conducting physical modeling with missing planning understanding, I had to blow up about half the created relationship.

 

 

Reference

https://opentutorials.org/course/3883/25260

업무파악 - 생활코딩

https://velog.io/@rg970604/데이터베이스-4.-개념적-데이터-모델링

[데이터베이스] 4. 개념적 데이터 모델링