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?Pros for single field:Simpler UINo 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..)Less complexity when handling titles (e.g. no need for separate field to enter M.D or Dr.)Pros for split field:Personalised communication is possible Dear Mr X or Dear JulieIf a consumed web service needs the first / last name separately, it can be provided easily.Better choice for any industry with strict identification requirements (e.g. medical, government, etc.)Safer choice, as you can always go back to the single field alternativeDo you see any additional argument that is not listed above?Update: the question is, what additional (=not listed in the question) arguments 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.
Modeling first and lastname separately
database design;data;domain model;data modeling