Advertisement

The SDBC Approach

  • Boris Shishkov
Chapter
  • 330 Downloads
Part of the The Enterprise Engineering Series book series (TEES)

Abstract

We make a clear distinction between issues that concern the enterprise-engineering aspects of Enterprise Information Systems (EIS) and issues that concern the software-engineering aspects of such systems—see Chap.  1. At the same time, we need to bring together enterprise modeling (driven by social theories—see Chap.  4) and software specification (driven by computing paradigms—see Chap.  5) for the sake of bridging the enterprise-software gap (as discussed in Chap.  1). We have put conceptual foundations for this in Chap.  2 (by considering systemics) and we have explicitly addressed the environmental and user perspectives with regard to EIS (see Chap.  3). What is nevertheless missing so far is the operationalization perspective—we need an approach and methodological guidelines on what to do and how to do it in order to actually realize an enterprise-modeling-driven software generation; this is a challenge because most current approaches and methods are either rooted in social theories or based on computing paradigms—this claim has been justified in the previous chapters of the current book. For this reason, we consider previous works of the Author [1] who has been studying and addressing the mentioned challenge for more than 15 years already, reflecting innovative ideas in his SDBC APPROACH—“SDBC” stands for “Software Derived from Business Components.” Hence, the reasons for considering and developing further this approach are the following:

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Shishkov B (2005) Software specification based on re-usable business components. Delft University Press, DelftGoogle Scholar
  2. 2.
    Shishkov B (2017) Enterprise information systems, a modeling approach. IICREST Press, SofiaGoogle Scholar
  3. 3.
    Shishkov B, Janssen M (2018) Enforcing context-awareness and privacy-by-design in the specification of information systems. In: Shishkov B (ed) Business modeling and software design, BMSD 2017. Lecture notes in business information processing, vol 309. Springer, ChamGoogle Scholar
  4. 4.
    Shishkov B, Janssen M, Yin Y (2017) Towards context-aware and privacy-sensitive systems. In: 7th International symposium on business modeling and software design, BMSD 2017, SCITEPRESSGoogle Scholar
  5. 5.
    Shishkov B, Van Sinderen M, Quartel D (2006) SOA-driven business-software alignment. In: Proceedings of the ICEBE’06 IEEE international conference on e-business engineering. IEEEGoogle Scholar
  6. 6.
    Cockburn A (2000) Writing effective use cases. Addison-Wesley, Boston, MAGoogle Scholar
  7. 7.
    Shishkov B, Larsen JB, Warnier M, Janssen M (2018) Three categories of context-aware systems. In: Shishkov B (ed) Business modeling and software design, BMSD 2018. Lecture notes in business information processing, vol 319. Springer, ChamGoogle Scholar
  8. 8.
    Shishkov B, Van Sinderen M, Tekinerdogan B (2007) Model-driven specification of software services. In: Proceedings of the ICEBE’07 IEEE international conference on e-business engineering. IEEEGoogle Scholar
  9. 9.
    Shishkov B (2010) Methodological support for the design of enterprise information systems with SDBC: towards distributed, service-oriented and context-aware solutions. In: Proceedings of the 4th international workshop on enterprise systems and technology, SCITEPRESS, Athens, Greece, July 2010Google Scholar
  10. 10.
    Shishkov B, Warnier M, Van Sinderen M (2010) On the application of autonomic and context-aware computing to support home energy management. In: Proceedings of the 12th international conference on enterprise information systems (ICEIS), SCITEPRESS, Funchal, Madeira, Portugal, 8–12 June 2010Google Scholar
  11. 11.
    Shishkov B, Dietz JLG (2004) Design of software applications using generic business components. In: Proceedings of the 37th Hawaii international conference on system sciences (HICSS), IEEE, Big Island, Hawaii, USA, 5–8 January 2004Google Scholar
  12. 12.
    Wieringa RJ (1995) Requirements engineering, framework for understanding. Wiley, New YorkGoogle Scholar
  13. 13.
    Kotonya G, Sommerville I (1998) Requirements engineering. Wiley, New YorkGoogle Scholar
  14. 14.
    UML. The unified modeling language. http://www.uml.org
  15. 15.
    Atkinson C, Muthig D (2002) Enhancing component reusability through product line technology. In: Proceedings of the 7th international conference on software reuse, Austin, TX, USA, 15–19 April 2002Google Scholar
  16. 16.
    Atkinson C, Bayer J, Bunse C, Kamsties E, Laitenberger O, Laqua R, Muthig D, Paech B, Wust Z, Zettel J (2001) Component-based product line engineering with UML. Addison-Wesley, Boston, MAGoogle Scholar
  17. 17.
    Liu K (2000) Semiotics in information systems engineering. Cambridge University Press, CambridgeCrossRefGoogle Scholar
  18. 18.
    Dietz JLG (2006) Enterprise ontology, theory and methodology. Springer, HeidelbergCrossRefGoogle Scholar

Copyright information

© Springer Nature Switzerland AG 2020

Authors and Affiliations

  • Boris Shishkov
    • 1
    • 2
    • 3
  1. 1.Faculty of Information SciencesUniversity of Library Studies and Information TechnologiesSofiaBulgaria
  2. 2.Institute of Mathematics and InformaticsBulgarian Academy of SciencesSofiaBulgaria
  3. 3.Interdisciplinary Institute for Collaboration and Research on Enterprise Systems and TechnologySofiaBulgaria

Personalised recommendations