The Perpetual Calendar Structure

Posted on jueves, mayo 20, 2010 by Pedro Wave

To understand us, both users and programmers, we should speak the same language to manipulate of information.

To manipulate the databases we use the Structured Query Language - SQL, although we are not aware of it because the sentences are embedded within the application that interacts with databases but, to define the structure of a program or application, we have not defined a common language with the users.

Our software engineers create the Information Arquitecture by means of modeling techniques, own dictionaries and languages that do not share with users such as:
- Data Flow Diagramas - DFD
- Logical Data Model - LDM by means of high-level conceptual schemes.
- Data Dictionaries - DD as sets of metadata in a Data Base - DB.

To visualize, specify, build and document a software application, programmers we understand the graphic language modeling software systems currently most known and used, the Unified Modeling Language - UML based on 13 different types of diagrams classified into 3 categories:
- Structure Diagrams: classes, components, objects, composite, deployment, packages.
- Behavior Diagrams: activities, use cases, estates.
- Interaction Diagrams: sequence, communication, interaction, timing.

The problem is that UML lacks a precise semantics, so it is not objective and can result in different interpretations for different users. Another factor is the lack of components to define persistence of a remote application or a distributed system. But the worst thing is the freedom to use any of the 13 types of diagrams, while we are not superstitious. Always we are going to use the least appropriate following our common sense...

To facilitate Interactive Design is best to decide by the behavior diagrams such as use case diagrams and state diagrams that leave no doubt about the interaction with users and can show to take joint decisions concerning the structured design plan for a Perpetual Calendar in Excel:

As you can see, in this Use Case Diagram coexist different types of users, from commercial or secretary to controller or practical people, from customers to workers and unemployed people. Everyone wants to know how they will be his coming days, months or years (some nostalgic look past years) and some will try to keep the present in their own diaries.

If you don't mind my asking, what type of user you are and what language you communicate with?
Traducción al español aquí.

No Response to "The Perpetual Calendar Structure"

Leave A Reply

Dime si te gusta lo que lees y, si no te gusta, dime por qué. Tengo habilitada la moderación de comentarios. Tu comentario se publicará pronto.

Tell me if you like what you read here and if you don't like, tell me why. I've enabled comment moderation. Your comment will be published ASAP.

Mi Lista de Blogs- My Blog List