Skip to main content
Log in

Modeling Unified Language Templates for Designing Information Systems

  • INFORMATION LANGUAGES
  • Published:
Automatic Documentation and Mathematical Linguistics Aims and scope

Abstract—The most popular tools for developing object-oriented information systems are CASE-tools. More often, they do not support n-ary association relationships between classes. It is shown how, when describing a domain model, one can go from n-ary associations to binary ones, how to reduce the number of information system objects, and how to take into account the restrictions placed on objects. Situations that allow this kind of transformation are presented in the form of design patterns.

This is a preview of subscription content, log in via an institution to check access.

Access this article

Price excludes VAT (USA)
Tax calculation will be finalised during checkout.

Instant access to the full article PDF.

Institutional subscriptions

Fig. 1.
Fig. 2.
Fig. 3.
Fig. 4.
Fig. 5.
Fig. 6.
Fig. 7.
Fig. 8.
Fig. 9.
Fig. 10.
Fig. 11.
Fig. 12.
Fig. 13.
Fig. 14.

Similar content being viewed by others

Notes

  1. Unified Modeling Language: a unified modeling language that uses several types of diagrams for the specification, design, and documentation of software systems.

  2. CASE-tools (Computer Aided Software Engineering): a software tool that automates the process of developing software for an information system.

  3. n-ary (n > 2) the association relationship is a relationship in which n objects of classes included in the association participate.

  4. Object Constraint Language: the object language of restrictions. It serves to determine the restrictions imposed on objects that cannot be described on UML.

  5. A tuple is an ordered sequence of elements, in this case objects.

REFERENCES

  1. Booch, G., Jacobson, I., and Rumbaugh, J., The Complete UML Training Course, Prentice Hall PTR, 2000.

    Google Scholar 

  2. Matsyashek, L., Analiz I proektirovanie informatsionnykh sistem s pomoshch’yu UML 2.0 (Analysis and Design of Information Systems Using UML 2.0), Moscow: Vil’yams, 2016.

  3. Larman, C., Applying UML and Patterns, Prentice Hall Professional, 2002.

    Google Scholar 

  4. Gamma, E., Johnson, R., Helm, R., and Vlissides, J., Design Patterns. Elements of Reusable Object-Oriented Software, Addison-Wesley, 2001.

    MATH  Google Scholar 

  5. Sergievskiy, M., N-ary relations of association in class diagrams: Design patterns, Int. J. Adv. Comput. Sci. Appl., 2016, vol. 7, no. 2, pp. 265–268.

    Google Scholar 

  6. Brown, W., Malveau, R., McCormick III, H., and Mowbray, T., AntiPatterns: Refactoring Software, Architectures, and Projects in Crisis, John Wiley & Sons, Inc, 1998.

    Google Scholar 

  7. Sergievskiy, M. and Kirpichnikova, K., Optimizing UML class diagrams, in ITM Web of Conferences, vol. 18: 7th Seminar on Industrial Control Systems: Analysis, Modeling and Computing (ICS 2018), Moscow, 2018. https://www.itm-onferences.org/articles/itmconf/ abs/2018/03/contents/contents.html.

  8. Clark, T. and Warmer, J., Object Modeling with the OCL, Berlin: Springer, 2002.

    Book  Google Scholar 

  9. Sergievskii, M.V. and Kirpichnikova, K.K., Validation and optimization of diagrams of UML classes, Cloud Sci., 2018, vol. 5. no. 2, pp. 367–378.

    Google Scholar 

  10. Genova, G., Llorens, J., and Martınez, P., The meaning of multiplicity of n-ary associations in UML, Software Syst. Model., 2002, no. 1, pp. 86–97.

  11. Olive, A., Conceptual Modeling of Information Systems, Berlin: Springer Science & Business Media, 2007.

    MATH  Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to M. V. Sergievsky.

Ethics declarations

The authors declare that they have no conflicts of interest.

About this article

Check for updates. Verify currency and authenticity via CrossMark

Cite this article

Sergievsky, M.V. Modeling Unified Language Templates for Designing Information Systems. Autom. Doc. Math. Linguist. 54, 26–35 (2020). https://doi.org/10.3103/S0005105520010033

Download citation

  • Received:

  • Published:

  • Issue Date:

  • DOI: https://doi.org/10.3103/S0005105520010033

Keywords:

Navigation