Guide to object-oriented analysis and design

The purpose of this guide is to provide Marshall Space Flight Center personnel with guidelines for the use of object-oriented analysis and design and to describe how it can be accomplished within the framework of existing development directives, including the Software Development Plan. It is not intended as a detailed tutorial. The reader is referred to the Coad and Yourdon texts in the References

A comparative analysis of data redundancy and execution time between relational and object oriented schema table

The design of database is one of the important parts in building software, because database is the data storage inside the system. There are some techniques that allow the programmer to improve design of the database. One of the most popular techniques being used for database is the relational technique, which content entity relationship diagram and normalization. The relational technique is easy to use and useful for reducing data redundancy because the normalization technique solves the data redundancy by applying normalization normal forms on the schema tables. The second technique is the object oriented technique, which content class diagram and generate schema table. An advantage of object oriented technique is its closeness to programming languages like C++ or C#. This project is starting with applying relational technique and object oriented technique to define which technique uses less data redundancy during design database. Based on experimental results for total data redundancy in HMS case study was 336 for relational technique and 364 for object oriented technique as well as, course database case study was 186 for relational technique and 204 for object oriented technique. Also, this project is focus on query execution time between relational databases and object oriented database by using user friendly window. The experimental result for query execution time in HMS case study was 107.25 milliseconds for RDBMS and 80.5 milliseconds for OODBMS. In course database case study was 46.75 milliseconds for RDBMS and 31.75 milliseconds for OODBMS. However, the comparative analysis in this project is explaining the result of comparison between relational and object oriented techniques specifically with data redundancy and query execution time

An object-oriented model of measurement systems

This paper presents a general object-oriented model for measurement systems. The limitations of the conventional function-oriented models are examined in the light of the generalized concept of measurement and its theoretical framework proposed previously by the authors. The proposed model identifies five classes of objects, i.e., measured object, measuring instrument, reference standard, human observer, and operating environment. Each is characterized by its own attributes and operations or functions at three levels, i.e., internal, operational, and environmental. The interactions between them are also modeled, including the coupling between the measured object and the measuring instrument, the human-instrument interface, the calibration, and the interference. It serves as both a modeling framework and a practical tool for description, analysis and design, and, in particular, for computer-aided analysis and design of a measuring system. It will find applications in instrumentation engineering and measurement research and education

Design of object-oriented debugger model by using unified modeling language.

Debugging on computer program is a complex cognitive activity. Although it is complex, it’s still one of the popular issues in computer programming task. It is a difficult task, which is to understand what the error is and how to solve such error? In computer programming the difficulty is to understand the Object-Oriented programming concept together with the programming logic. If the programming logic is incorrect, the program codes will have such error named as logic error and can caused highly maintenance cost. Logic error is a bug in a program that causes it to operate incorrectly, without terminating or crashing the program.It will produce unintended output or other behavior than what we are expecting. Method that use to develop a propose model Object Oriented Debugger is Unified Modeling Language (UML). It is the best choice model and suitable to design the Object Oriented Debugger which will be developed in an object oriented programming environment. The model will provide an ability to capture the characteristics of a system by using notations in the process of designing and implementing the system. The model of Object Oriented Debugger has been successfully implemented. This model has been developed using Unified Approach methodology, which consists of two methods such as Object-Oriented Analysis (OOA) and Object-Oriented Design (OOD). The model developed is to capture the structure and behavior of the Object Oriented Debugger by using the UML diagram. The model also can ease the readability of the documentation for the maintenance purposes. The design of the Object Oriented Debugger Model has been developed using the UML notation. It’s consisting of two parts that are object-oriented analysis and object-oriented design. All the developing and designing are based on the model in UML

An Approach to Teaching Object-Oriented Analysis and Design

This paper presents a syllabus that attempts to address the problem of teaching systems analysis and design in the changing world of today. In the first part of the paper, major issues and constraints that affect the development of a syllabus for this discipline are identified and analyzed. The second part of the paper focuses on the key points of a methodology constructed from traditional and object-oriented techniques, designed to satisfy the academic demands of the subject and reflect current practice, while providing students with a coherent and organized approach to systems analysis and design. Analysis of the outcomes and experience of implementing the syllabus provide the basis for conclusions and identification of possible areas for future research

Functional Analysis and Object-Oriented Design- A Hybrid Methodology

We propose a methodology for information systems analysis and design which is a hybrid of two main streams in software engineering, the functional (or process-oriented) approach and the object-oriented (OO) approach. System analysis, which aims at eliciting and defining user requirements, continues to be carried out in the functional approach, utilizing data flow diagrams (DFD). System design, which aims at designing the software, is carried out in the OO approach, yielding an object model that consists of an object schema and a behavior schema (i.e., methods and messages). The transition from the functional model (in the analysis stage) to the OO model (in the design stage) is enabled by the use of ADISSA methodology, which facilitates design of the object schema from DFD data stores, and design of the behavior schema from transactions, which by themselves are derived from the DFDs