2
Who and how do you define the layout of data in software such as Editors, Dbms or even who creates text encodings? When I say "data layout", I mean, for example, how a PDF file stores the document data; what comes first in the file, the coding, the standards so that the software can understand the file, etc. In the case of Dbms, who and how design the layout that ensures the efficiency and security of databases? What is the area that studies this?
5
In general it is called software engineer, but it also meets by developer, programmer, architect and a lot of other names. There is something so specific and there are few definitions of ways of what each function should do. I’ve made up a question and gave a reply about this.
In general the same person designing all the rest determines the layouts of archives or other forms. In practice the layout One of the most important things about software development is that it’s common for people to neglect. When it is well made it is easier to produce the algorithms around it and evolve the code and all architecture.
Of course in a large project a person can be assigned to do this, but it is not common. Maybe there’s a data curler, but I’ve never seen the term used for that, let alone someone being that. It’s kind of like saying that the doctor is an expert at sewing skin.
Maybe because some people think that they study a part and not the whole and then make mistakes because they don’t know everything you need.
Globally this is still software engineering, more specifically is the area of data structure.
Although tangentially it can help security, it has little to do with the data structure itself.
2
The team as a whole defines how the data will be treated, in a meeting for example.
After this you have all the development documentation and the scope of the software with its requirements phases, etc..
Browser other questions tagged database filing-cabinet software-engineering language-independent
You are not signed in. Login or sign up in order to post.
Thanks for the clarification. But I think where I used "security", I should have also put "reliability". I don’t know if this has anything to do with it, but for example, let’s assume that a file is more likely to get corrupted at the end, I put the most important part of the data at the beginning, maybe the chance to recover data in case of loss was greater. I wanted more in that sense. But I may be wrong.
– Carlos
– Carlos
@Carlos very common the terms be confused, I myself sometimes exchange them improperly. A structure created redundantly is important to give more reliability, although it brings other "problems"
– Maniero