CFP last date
20 January 2025
Reseach Article

Domain Engineering: A Conceptual Model of the Software Application Architecture

by Sanjay Bhagwan Sonar, Vimal N. Pandya
International Journal of Computer Applications
Foundation of Computer Science (FCS), NY, USA
Volume 180 - Number 30
Year of Publication: 2018
Authors: Sanjay Bhagwan Sonar, Vimal N. Pandya
10.5120/ijca2018916770

Sanjay Bhagwan Sonar, Vimal N. Pandya . Domain Engineering: A Conceptual Model of the Software Application Architecture. International Journal of Computer Applications. 180, 30 ( Apr 2018), 32-40. DOI=10.5120/ijca2018916770

@article{ 10.5120/ijca2018916770,
author = { Sanjay Bhagwan Sonar, Vimal N. Pandya },
title = { Domain Engineering: A Conceptual Model of the Software Application Architecture },
journal = { International Journal of Computer Applications },
issue_date = { Apr 2018 },
volume = { 180 },
number = { 30 },
month = { Apr },
year = { 2018 },
issn = { 0975-8887 },
pages = { 32-40 },
numpages = {9},
url = { https://ijcaonline.org/archives/volume180/number30/29236-2018916770/ },
doi = { 10.5120/ijca2018916770 },
publisher = {Foundation of Computer Science (FCS), NY, USA},
address = {New York, USA}
}
%0 Journal Article
%1 2024-02-07T01:02:17.163912+05:30
%A Sanjay Bhagwan Sonar
%A Vimal N. Pandya
%T Domain Engineering: A Conceptual Model of the Software Application Architecture
%J International Journal of Computer Applications
%@ 0975-8887
%V 180
%N 30
%P 32-40
%D 2018
%I Foundation of Computer Science (FCS), NY, USA
Abstract

Domain is the business functional workout area to be designed in the mode of discrete component, domain workout area is a conceptual representation of the business logic and rules and real situation objects in the domain, here domain is also called conceptual model of the requirement engineering. In software development requirements must start with domain modeling and business workout area is formulated by the domain modeling for software application architecture. Before requirements can be defined the application domain must be defined. Here domain is the initial conceptual model of the requirement engineering. Domain classify with vertical and horizontal method to prove number of modules in hierarchical mechanism with interface in vertical method and functionalities of the each modules is defined in horizontal method. Domain engineering directly support to the acquiring business rule, logic and functionalities. As well as define the requirement elicitation and specification using tools and techniques of the domain engineering. Using this the physical objectization is extracted. In this paper we outline the basic facets of objectization from domains.

References
  1. Bernd Bruegge, Allen H. Dutoit. “Object Oriented Software Engineering, Using UML, Patterns, and Java”, Second Edition, Pearson Education, 2010
  2. Craig Larman. “Applying UML and Patterns”, 3rd Addition, Pearson Education Inc 2005
  3. Civello F, “Roles for composite Objects in Object Oriented Analysis and Design”, OOPSLA, ACM SIGSOFT Vol. 28 No. 10, pp 376-393
  4. Desmond Francis D’ Souza and Alan Cameron Wills, “Objects, Components, and Framework with UML”, 2nd Addition, Addition-Wesley Object Technology Series 1999
  5. G. Kotonya and I. Somerville, “Requirements Engineering”, Processes and Techniques, John Wiley Sons
  6. Geri Schneider, Jason P. Winters. “Applying Use Cases”, 2nd Addition, Addition-Wesley Object Technology Series 1998
  7. Grady Booch. “Object Solutions”, 2nd Addition, Addition-Wesley Object Technology Series 1996
  8. Ian Somerville, “Software Engineering”, 6th Edition, Pearson Education, 2005
  9. Juhani Livari, “Object Oriented as Structural, Functional and behavioral Modeling”: A comparison of six methods for Object Oriented Analysis, Department of Computer Science and Information science, University of Jyvdskyla
  10. Jim Arlow, Ila Neustadt. “UML and the Unified Process”, 2nd Addition, Addition-Wesley, Object Technology Series, 2002
  11. M. Mattsson and J Bosch “Object oriented frameworks” Composition problems, causes and solutions In Building Application Frameworks: Object-Oriented Foundations of Framework Design, pp. 467-487, M. Fayad, D. Schmidt, R. Johnson editors, Wiley Press, 2000
  12. M. Davis, “Software Requirements”: Objects, Functions, & States, Prentice Hall, Englewood Cliffs, 1993
  13. Meyer B., “Applying Design by Contract”, IEEE Computer, Oct 1992
  14. N. Bouassida, H. Ben-Abdallah, and F. Gargouri, A. Ben-Hamadou:” A stepwise Framework Design Process”, IEEE International Conference on Systems Man and Cybernetics, 07-09 October, Hammamet, Tunisia, 2002
  15. P. Loucopoulos and V. Karakostas, “System Requirements Engineering”, McGraw-Hill 3rd Addition 2007
  16. R. H Thayer and M Dortman “System and Software Requirements Engineering”, Tutorial, IEEE Computer Society Press
  17. Yun-Tung Lau, “The Art of Objects” Object-oriented Design and Architecture, Addison-Wesley object technology series, Addison-Wesley, 2001
  18. Wirfs - Brock, R. and Wilkerson, B. “Object Oriented Design” A Responsibility- Driven Approach. In Proceedings of OOPSLA '89 Conference, SIGPLAN Not (ACM) 24, 10, (New Orleans, Louisiana, October 1989), pages 71-76
  19. R. H Thayer and M Dortman “System and Software Requirements Engineering”, Tutorial, IEEE Computer Society Press
  20. Sonar Sanjay Bhagwan, “Object Identification for Pure Object Oriented Cross Languages Software Development”. International Journal of Applied Information Systems Vol. 9, No.3, pp 42-48, June 2015. Published by Foundation of Computer Science, ISSN 2249-0868, New York, USA.
Index Terms

Computer Science
Information Sciences

Keywords

Domain Sub-Domain Co-Domain Ethnography Heuristics Brainstorming Composition Segmentation Objectization.