3.5.3 Object‐Oriented Systems Engineering (original) (raw)
Related papers
Toward integrating systems engineering with software engineering through Object-Process Programming
International Journal of Information Technology
Modern systems comprise hardware and software components that together provide value through enabling the functionality that the system is intended to provide. Systems engineering (SE) and software engineering (SwE) are therefore interdependent, tightly coupled, and complementary activities that must be carefully aligned and coordinated throughout the system development process. Yet, these two disciplines have historically grown quite separated from each other, with too little interaction and mutual learning. In this work, we develop and evaluate Object-Process Programming (OPP) as a proof-of-concept for a common framework that integrates SE and SwE based on ISO 19450-Object-Process Methodology. The ability of designers to use the same paradigm for engineering the software, the hardware, and the system as a whole, using the same concepts and principles and the same design environment, described and discussed in this work, is a major step towards the integration and streamlining of engineering new systems that feature significant hardware and software components. To evaluate OPP, we established a focus group and conducted an experiment in which participants were asked to develop systems using OPP. Overall, the results were positive in terms of usability and understandability. In particular, the language and the environment were far superior in comparison to textual languages. OPP will contribute to the continuous endeavor to bridge the gap between SE and SwE by providing a seamless, easy-to-learn environment. Non-technical stakeholders can also benefit from OPP by improving their communication with technical stakeholders. The ideas underlying OPP have already served to augment OPM with computational capabilities.
WORLD SCIENTIFIC eBooks, 1996
This paper deals with the problems that arise during the transisition from analysis to design. All impact factors like a supportive structure and contents of the analyis model or requirements of the following implementation environment are discussed. Additionally the transition process and the influences of current software engineering concepts and conditions are treated. Problem areas were identified through practical reports while solutions are taken both from practical experience papers and theoretical reports. The reader should be familiar with basic object-oriented concepts.
OBJECT-ORIENTED ANALYSIS AND DESIGN With applications SECOND EDITION
Mankind, under the grace of God, hungers for spiritual peace, esthetic achievements, family security, justice, and liberty, none directly satisfied by industrial productivity. But productivity allows the sharing of the plentiful rather than fighting over scarcity; it provides time for spiritual, esthetic, and family matters. It allows society to delegate special skills to institutions of religion, justice, and the preservation of liberty.
Applying Object Oriented Systems Engineering to Complex Systems
2008 2nd Annual IEEE Systems Conference, 2008
Analyzing systems using functional analysis has been the mainstream for Systems Engineering for five decades. With the advent of object oriented software methods and the Object Management Group's (OMG) Unified Modeling Language™ (UML), a number of Systems Engineers working on software intensive systems began to apply Use Cases and Object Oriented Analysis and Design (OOAD) methods to large scale, complex systems. While the use of these OO methods is still controversial within the systems engineering community, many systems engineers that apply OO methods effectively have used functional analysis and understand the strengths of both methods. One challenge systems engineer's face when applying OO methods to the early phases of engineering is that most experienced users of UML define and design the solution, not to develop the concept. Therefore, published examples of UML/SysML usage tend to be at the implementation level instead at the much higher abstract level of problem definition and concept development. However, defining the concept and developing the initial semantics in a tool other than PowerPoint or Visio can set the tone for the entire project and drive the success of the entire engineering effort. Additionally, UML/SysML offers an extended and connected set of diagrams that allow one to better explore the operational scenarios and system design, and their related semantics. FireSAT is a well known fictitious system of systems space mission to provide a space based approach to wildfire detection, monitor and control. This paper will explore the use of OOAD methods to FireSAT for problem definition, concept development, and system architecture development. Using the OMG's recently adopted System Modeling Language™ (SysML) and more traditional Systems engineering modeling techniques, this paper will compare and contrast some of the differences between OO and functional methods, showing diagrams from each approach.
Applying object-oriented analysis on a case study
Information Systems, 1994
This paper aims at showing that some object-oriented fundamental principles provide new suitable mechanisms for the analysis and the specification of complex systems. Three principles are presented and discussed in this paper through a case study. The locality principle allows to concentrate on one object, stressing its structure and behaviour through the notion of life cycle, the refinement principle allows to refine objects by means of inheritance links, the globality principle allows to enlighten on different kinds of dependencies amongst objects. The case study is developed with the model of the Modway method. The Modway method is an object-oriented method which makes use of object concepts since the very beginning of the development process.
2008
A large number of the system of systems developed over the past decade have been software intensive systems. The predominant systems engineering approach in use over that period is the waterfall process, sometimes referred to as a 'V' methodology or model. In this model, steps that are defined as the sound engineering rigor are executed in a sequential manner. This process has been in use for over 20 years by most Department of Defense contractors (as well as commercial enterprises that employ a systems engineering discipline). However, the past decade has seen a migration to object oriented (OO) methodologies for software intensive systems. This methodology typically brings other technologies, products & processes which impact the way organizations develop systems. This paper addresses lessons learned from both a project manager's perspective and an architect's perspective in producing large system of systems using an object oriented systems engineering methodology.
Object-oriented analysis and design: a question of approach
Later this year, the Open University (OU) will offer the first presentation of a new course in object-oriented software technology. This course covers a wide range of issues from programming in Smalltalk to object-oriented analysis and design, to management of object-oriented projects. It is part of the Masters degree programme which is aimed at individuals who are involved in software development professionally. As with all OU courses, the course is to be taught using distance teaching techniques, so course materials are presented through a combination of media including written text, computer software and video. Each course is expected to have a lifetime of about six years-a long time in a field which is moving as rapidly as object-orientation. This paper discusses our experiences of designing the object-oriented analysis and design element of the course: the approach chosen, the difficulties encountered, and the solutions devised.
International Journal of Advanced Computer Science and Applications, 2011
This paper discusses the comparison between Traditional approaches and Object-Oriented approach. Traditional approach has a lot of models that deal with different types of projects such as waterfall, spiral, iterative and v-shaped, but all of them and other lack flexibility to deal with other kinds of projects like Object-Oriented. Object-oriented Software Engineering (OOSE) is an object modeling language and methodology. The approach of using objectoriented techniques for designing a system is referred to as object-oriented design. Object-oriented development approaches are best suited to projects that will imply systems using emerging object technologies to construct, manage, and assemble those objects into useful computer applications. Object oriented design is the continuation of object-oriented analysis, continuing to center the development focus on object modeling techniques.
An undergraduate course in object-oriented software design
FIE '98. 28th Annual Frontiers in Education Conference. Moving from 'Teacher-Centered' to 'Learner-Centered' Education. Conference Proceedings (Cat. No.98CH36214)
Many software development organizations are adopting object-oriented methodologies as their primary paradigm for software development. The object-oriented method appears to increase programmer productivity, reduce the overall cost of the software, and perhaps most importantly creates software that promotes reuse and subsequently is easier to modify. Consistent with the change in industry, many universities and industry training organizations are currently in the process of integrating object orientation into their curriculum. There are several approaches including horizontal integration (integrating a small dose of the object orientation into many courses) and vertical integration (having a large dose of the concepts in a single course). In 1996, the Systems Analysis department of Miami University opted for the latter approach and added a new course to its curriculum. It is a course that is intended to provide some in-depth exposure to object-oriented design and implementation. It should be of particular value to faculty in computer science and information systems departments (both at the 4-year and 2-year institutions) as well as those in industry training organizations who are looking for ways to incorporate the object orientation into their curriculum. In this paper, we will describe the choices our department made, what worked well, and what needs to be improved.