Object-Oriented Software Reuse in Business Systems

Author(s):  
Daniel Brandon Jr.

“Reuse [software] engineering is a process where a technology asset is designed and developed following architectural principles, and with the intent of being reused in the future” (Bean, 1999). “If programming has a Holy Grail, widespread code reuse is it with a silver bullet. While IT has made and continues to make laudable progress in our reuse, we never seem to make great strides in this area” (Grinzo, 1998). “The quest for that Holy Grail has taken many developers over many years down unproductive paths” (Bowen, 1997). This article is an overview of software reuse methods, particularly object oriented, that have been found effective in business systems over the years.

Author(s):  
Daniel Brandon

“Reuse [software] engineering is a process where a technology asset is designed and developed following architectural principles, and with the intent of being reused in the future” (Bean, 1999). “If programming has a Holy Grail, wide-spread code reuse is it with a silver bullet. While IT has made and continues to make laudable progress in our reuse, we never seem to make great strides in this area” (Grinzo, 1998). “The quest for that Holy Grail has taken many developers over many years down unproductive paths” (Bowen, 1997). This article is an overview of software reuse methods, particularly object oriented, that have been found effective in business systems over the years.


Author(s):  
Daniel Brandon Jr.

“Reuse (software) engineering is a process where a technology asset is designed and developed following architectural principles, and with the intent of being reused in the future” (Bean, 1999). “If programming has a Holy Grail, wide-spread code reuse is it with a bullet. While IT has made and continues to make laudable progress in our reuse, we never seem to make great strides in this area” (Grinzo, 1998). The quest for that Holy Grail has taken many developers over many years down unproductive paths” (Bowen, 1997). This chapter reports on software reuse research (both literature research and design/coding research) and presents an approach for effective software reuse in the development of business systems. This approach is based on Object Oriented technology and provides for both the specification and enforcement of software reuse and corporate standards.


Author(s):  
Anna Birney

AbstractMore and more people and organisations who are addressing complex sustainability challenges are turning to systems change practices. They are looking to get to grips with complexity and to better understand how to use their resources, position and influence to address the challenges. These people are working across civil society, philanthropy, business, international development, government and beyond. Many hope that adopting this emerging practice will give them the answers to the long held questions of – How do I know where to intervene? How do I know that what I am doing is the ‘right’ thing? Am I using my resources for their greatest effect? Once we have set ambitious goals around issues like inequality and climate change, how do I know I am creating impact?. In 1999 Donella Meadows wrote a paper entitled Leverage points: places to intervene in a system to help translate the work of systems dynamics into understanding where a small amount of energy might have a greater effect. Ever since, practitioners have been chasing these elusive leverage points trying to understand how this might be made useful and practical. There is, however, no silver bullet to changing a system. At Forum for the Future and through the School of System Change, we work on a number of different projects such as the Protein Challenge and Boundless Roots Community as well as collaborate on, coach and co-inquire with others such as the Marine CoLAB, Oneless, Lankelly Chase Foundation. In this paper we seek to build on systems change ideas and theories, using Forum for the Future experience of working with these ideas in practice, and offer actionable knowledge (Coghlan 2007) to other change makers who are grappling with these questions. This paper provides four qualities that help us understand the dynamics of a changing system, and how potential in these dynamics might be identified and be translated into strategy and interventions. I explore and illustrate these through cases and examples and raise the question about how change makers might value what we measure when understanding impact in the context of a changing system.


Author(s):  
Elizabeth M. Borycki ◽  
Andre W. Kushniruk ◽  
Ryan Kletke ◽  
Vivian Vimarlund ◽  
Yalini Senathirajah ◽  
...  

Objectives: This paper describes a methodology for gathering requirements and early design of remote monitoring technology (RMT) for enhancing patient safety during pandemics using virtual care technologies. As pandemics such as COrona VIrus Disease (COVID-19) progress there is an increasing need for effective virtual care and RMT to support patient care while they are at home. Methods: The authors describe their work in conducting literature reviews by searching PubMed.gov and the grey literature for articles, and government websites with guidelines describing the signs and symptoms of COVID-19, as well as the progression of the disease. The reviews focused on identifying gaps where RMT could be applied in novel ways and formed the basis for the subsequent modelling of use cases for applying RMT described in this paper. Results: The work was conducted in the context of a new Home of the Future laboratory which has been set up at the University of Victoria. The literature review led to the development of a number of object-oriented models for deploying RMT. This modeling is being used for a number of purposes, including for education of students in health infomatics as well as testing of new use cases for RMT with industrial collaborators and projects within the smart home of the future laboratory. Conclusions: Object-oriented modeling, based on analysis of gaps in the literature, was found to be a useful approach for describing, communicating and teaching about potential new uses of RMT.


Proceedings ◽  
2021 ◽  
Vol 74 (1) ◽  
pp. 13
Author(s):  
Hatice Koç ◽  
Ali Mert Erdoğan ◽  
Yousef Barjakly ◽  
Serhat Peker

Software engineering is a discipline utilizing Unified Modelling Language (UML) diagrams, which are accepted as a standard to depict object-oriented design models. UML diagrams make it easier to identify the requirements and scopes of systems and applications by providing visual models. In this manner, this study aims to systematically review the literature on UML diagram utilization in software engineering research. A comprehensive review was conducted over the last two decades, spanning from 2000 to 2019. Among several papers, 128 were selected and examined. The main findings showed that UML diagrams were mostly used for the purpose of design and modeling, and class diagrams were the most commonly used ones.


IEEE Software ◽  
2008 ◽  
Vol 25 (1) ◽  
pp. 91-94 ◽  
Author(s):  
Steven Fraser ◽  
Dennis Mancl

Sign in / Sign up

Export Citation Format

Share Document