Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

How to “Picture” the SER modeling perspective, from an application developers point of view?

0
Posted

How to “Picture” the SER modeling perspective, from an application developers point of view?

0

To “picture SER”, you probably should try the following perspectives: 1. Application: Consider a basic (non-decomposed) subject being a report, a form, or something corresponding to a (relational) view. On this basis, a subject can also be used to represent an application, application family, activity, or process that can be decomposed (in the manner of DFD/IDEF) into the basic subjects. In this sense, the subject is the exclusive carrier of data semantics while the context defines expressly the interaction rules of data flows among subjects. Thus, contexts are indeed semantic relationships of the semantic entities we now call subjects, except that we don’t define data items in these relationship (but merely refer to them in the rules). A context can be compared to a process of DFD in terms of its contents. The subtle difference here is, of course, that a DFD is focused primarily on processes while an SER is anchored methodologically in subjects – this reflects our roots in databases a

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123