Object Oriented Design and Object Oriented Programming
ffalourd utilisateurs-ldap · 2017
Cited by 0
Read the abstract, see who wrote it and who cites it, and get the citation in APA, MLA, Chicago or Harvard.
About 10,000 papers for “Object-oriented design”
ffalourd utilisateurs-ldap · 2017
Cited by 0
Pankaj Jalote · 1997
Cited by 0
Salvatore A. Buono · 2019
Cited by 1
Roger Y. Lee · Atlantis Press eBooks · 2013
Object design is primarily adding details to the requirements analysis and making implementation decisions. Object design serves as the basis for implementation in an object-oriented paradigm. During object design, developers define solution domain objects to bridge the gap between the analysis model and the hardware/software platform defined during system design. This includes precisely describing object and subsystem interfaces, selecting off-the-shelf components, restructuring the object model to attain design goals such as extensibility and understandability, and optimizing the object model for performance. An object model describes how a component or system works, down to programming language classes or some other level that can be coded.
Cited by 3
Mathiassen, Lars, Munk-Madsen, Andreas, Nielsen, Peter A.; id_orcid 0000-0002-0282-7445 et al. · VBN Forskningsportal (Aalborg Universitet) · 1995
Cited by 0
Günther Blaschek · 1994
Cited by 4
Kenneth M. Anderson, Oo A D · 2007
Cited by 35
Peter Coad, Edward Yourdon · CERN Document Server (European Organization for Nuclear Research) · 1991
Introduction. 1. Improving Design. 2. Developing the Multi-Layer, Multi-Component Model. 3. Designing the Problem Domain Component. 4. Designing the Human Interaction Component. 5. Designing the Data Management Component. 6. Applying OOD with OOPLs (or less than an OOPL). 7. Applying OOD Criteria. 8. OOD and CASE. 9. Getting Started with OOD. Appendix A. OOA Strategy Summary Appendix B. OOD Strategy Summary. Appendix C. An Example: OOA to OOD to OOP. Bibliography.
Cited by 634
Steve Skidmore · 1996
Object-oriented analysis (OOA) was introduced in the companion text Introducing Systems Analysis. It considered the emergence of generic models and template software as well as introducing Meyer's (1988) notation and constructs and his arguments for an object rather than functional approach to systems development.
Cited by 1
Dzielski, Dale G · The Research Repository @ WVU (West Virginia University) · 2018
Cited by 0
Naoufel Kraeim, Gargouri, F, Boufares, F · HAL (Le Centre pour la Communication Scientifique Directe) · 1993
International audience
Cited by 0
Naoufel Kraïem, Faı̈ez Gargouri, Faouzi Boufarès · Notes on numerical fluid mechanics and multidisciplinary design · 1993
Cited by 4Open access
Martin Fagerfjäll · 2005
Cited by 0
Jeffrey Dean · Zenodo (CERN European Organization for Nuclear Research) · 2026
This whitepaper introduces Object-Oriented System Design (OOSD), a conceptual framework that applies proven object-oriented programming paradigms to infrastructure architecture. OOSD provides a structured lens through which system administrators and IT leaders can understand the evolution from traditional server management to containerized infrastructure—drawing explicit parallels between the programming revolution from procedural languages (C, BASIC) to object-oriented languages (C++, Java) and the current transition from monolithic servers to container-based systems. The framework defines four pillars—System Encapsulation, Infrastructure Inheritance, Service Polymorphism, and Operational Abstraction—mapping familiar software development concepts directly onto container and orchestration platforms such as Docker and Kubernetes. OOSD is not a new technology; rather, it offers vocabulary and mental models that reduce conceptual friction for practitioners transitioning from traditional environments. The paper demonstrates alignment between OOSD principles and federal Zero Trust security mandates, arguing that container technology's inherent compartmentalization satisfies Zero Trust requirements that traditional monolithic architectures cannot adequately address. Practical benefits including dependency isolation, security improvements, and operational efficiency are examined alongside risk considerations and a strategic implementation roadmap.
Cited by 0Open access
MacDonald A., Carrington D. · Queensland's institutional digital repository (The University of Queensland) · 1998
Cited by 0
John F. Dooley, Vera A. Kazakova · Apress eBooks · 2024
Now that we’ve spent some time looking at object-oriented analysis and design, let’s recapitulate some of what you’ve already seen and talk about some common design characteristics.
Cited by 0
Kenneth Mølbjerg Jørgensen · VBN Forskningsportal (Aalborg Universitet) · 1992
Cited by 0
Jessica Robinson - · 2019
This chapter provides an overview of Hierarchical Object Oriented Design (HOOD). HOOD was developed by the European Space Agency as a design method for Ada, looking forward to the use of Ada as a major language for software for embedded space systems. HOOD has been adopted project wide for the European Fighter Aircraft, and is usually considered for any Ada software development projects because of its direct applicability and the availability of a range of HOOD Toolsets. The design strategy is globally top-down and consists of a set of basic design steps, in each of which a given object, called a parent object, is decomposed into a set of components called child objects which together provide the functionality of the parent object. A basic design step has as goals the identification of child objects of a given parent object and of their individual relationships to other existing objects.
Cited by 55
Kenmore S. Brathwaite · 1993
Cited by 1
John F. Dooley · Apress eBooks · 2017
Now that we’ve spent some time looking at object-oriented analysis and design, let’s recapitulate some of what we’ve already seen and add some more prose. First, let’s talk about some common design characteristics.
Cited by 0