![[PukiWiki]](image/pukiwiki.png "[PukiWiki]")
Why is it that many software developers don't pay enough attention to requirements engineering? Are there ever circumstances where you can skip it?
What are the four design models required for a complete specification of a software design? Describe the role of one of them in your own words.
The four design models are data design, architectural design, procedural design, and interface design.
In the process of data design, you need to define data models, entity types, attributes, and relationships. To design relational database, which is the most widely used data model, you will create data specification such as data definitions and E-R diagrams.
You can use different data models depending on types and purposes of data. If you need to read and write database records very often, for instance, if you treat HTTP sessions in a database, key-value stores can be more faster. In case you analyze large amounts of numerical data such as point-of-sales data, column-oriented data warehouse is more efficient.
Describe the worst interface you have ever worked with and the best interface you have ever worked with.
The worst interface that I have ever used is the Japanese feature phone, and the best interface I have ever used is iPhone.
I first started to have a feature phone when I was 15 years old. That had very useful functions other than telephone and e-mail. For example, I could enjoy the mobile Web and purchase a variety of ring tones.
However, because feature phones' OSs were developed by cell-phone makers themselves, their interface designs were different by makers and models. Therefore, I had to read a thick user manual to use it perfectly.
On the other hand, iPhone has very simple user interface. Its interface hierarchy is few. In other words, users can reach the intended function by a few touches, so that they will hardly get lost in the screen.
