most recent 30 from softwareengineering.stackexchange.com2025-05-01T22:21:28Zhttps://softwareengineering.stackexchange.com/feeds/tag?tagnames=data-modeling database-design domain-modelhttps://creativecommons.org/licenses/by-sa/4.0/rdfhttps://softwareengineering.stackexchange.com/q/35488538Istvan Devaihttps://softwareengineering.stackexchange.com/users/2794452017-08-01T10:40:01Z2021-03-26T15:27:04Z
<p>Which arguments should someone consider when designing a new system and has to either store the name of a person as one field or separately as first/last name?</p>
<p>Pros for single field:</p>
<ul>
<li>Simpler UI</li>
<li>No ambiguity when trying to enter the name of a person, who has a very long name (often non evident which is the last name / first name..)</li>
<li>Less complexity when handling titles (e.g. no need for separate field to enter "M.D" or "Dr.")</li>
</ul>
<p>Pros for split field:</p>
<ul>
<li>Personalised communication is possible "Dear Mr X" or "Dear Julie"</li>
<li>If a consumed web service needs the first / last name separately, it can be provided easily.</li>
<li>Better choice for any industry with strict identification requirements (e.g. medical, government, etc.)</li>
<li>Safer choice, as you can always go back to the single field alternative</li>
</ul>
<p>Do you see any <strong>additional</strong> argument that is not listed above?</p>
<p>Update: the question is, what <strong>additional</strong> (=not listed in the question) <strong>arguments</strong> can be listed for each solution. I think giving opinions instead of possible pros and cons drives the discussion in the wrong way. Each developer has to make his/her decision about this problem, the aim of this question is to assemble a list of non-trivial arguments that can be evaluated if needed.</p>
https://softwareengineering.stackexchange.com/q/38162829NaNhttps://softwareengineering.stackexchange.com/users/585132018-11-17T13:21:21Z2019-01-08T17:47:09Z
<p>I am modeling a database that should be used as generic non-functional requisite for all services of the startup company, like persons, users, services and commercial data like coupons, signature packages, etc.</p>
<p>I am thinking about the <strong><em>gender</em></strong> model. In these modern days and with different laws across countries about subjective identity, should I take that into consideration and model my Person entity with more than just the <strong>male</strong> and <strong>female</strong> options?</p>
<p>Options are: undefined, not-answered, other, transgender... or any other <strong>industry standard</strong> that I am unaware of...</p>
<p><em>Or does this offend LGBT people by saying that they are not truly male or female?</em></p>