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

The Development of Learning Object Design System (LODS) for Instructional Designers

This project intended to build a platform for Instructional Designers (IDs) to analyse the content and document their inputs on the content analysis. The purpose of the system is to aid IDs in the process of content design and produce an efficient design plan for learning objects using technology, in this case Learning Object Design System (LODS). LODS is a system where the instructional designer record the findings from content analysis (learning outcome, scope of content, cognitive level of content, content structure, summary) as well as learning design attributes for the particular learning object (instructional approach, content presentation method, learning activities, assessment method). The system was initiated due to the absence of standardised procedures in the beginning phase of the learning object design which is content design. This is a case study involving interviews with experts and literature reviews to derive the attributes for the content analysis process. A set of guidelines was developed which highlighted the steps in analysing the content. These guidelines were then transformed into a Learning Object Design System (LODS). LODS enable the IDs to record, save, retrieve and print their input on the content analysis findings. The LODS is expected to aid the IDs in the decision making process as it provides step-by-step template with options. The documentation will become as easy as filling in forms as they would be automatically formatted into one standard version. LODS is expected to speed up the content production and simplify the IDs’ current work process. For further research, it is recommended to make the LODS as collaborative platform between IDs and SMEs to enhance the quality of learning objects. (Abstract from authors

A practical approach to object based requirements analysis

Presented here is an approach developed at the Unisys Houston Operation Division, which supports the early identification of objects. This domain oriented analysis and development concept is based on entity relationship modeling and object data flow diagrams. These modeling techniques, based on the GOOD methodology developed at the Goddard Space Flight Center, support the translation of requirements into objects which represent the real-world problem domain. The goal is to establish a solid foundation of understanding before design begins, thereby giving greater assurance that the system will do what is desired by the customer. The transition from requirements to object oriented design is also promoted by having requirements described in terms of objects. Presented is a five step process by which objects are identified from the requirements to create a problem definition model. This process involves establishing a base line requirements list from which an object data flow diagram can be created. Entity-relationship modeling is used to facilitate the identification of objects from the requirements. An example is given of how semantic modeling may be used to improve the entity-relationship model and a brief discussion on how this approach might be used in a large scale development effort

Comprehensive Description and Critical Analysis of Object-Oriented Software Development

Object-orientation and the object model underlie a simple, intuitive, and useful approach to software development that has great potential for significantly improving the software development process. Object-orientation unifies activities, such as analysis and design, that currently largely independent and somehwat incompatible. Despite its simplicity, a sroud of msytery surrounds this approach. The difficult often encountered when learning and understanding object-oriented methods sems partly from the capricious and improper use of object-oriented jargon in conversation and in the literature. This paper explores the foundations of the object model, defines the associated terminology in concrete terms, and gives an overview of various object-oriented methods as they relate to the software lifecycle

Recursive forward dynamics for multiple robot arms moving a common task object

Recursive forward dynamics algorithms are developed for an arbitrary number of robot arms moving a commonly held object. The multiarm forward dynamics problem is to find the angular accelerations at the joints and the contact forces that the arms impart to the task object. The problem also involves finding the acceleration of this object. The multiarm forward dynamics solutions provide a thorough physical and mathematical understanding of the way several arms behave in response to a set of applied joint moments. Such an understanding simplifies and guides the subsequent control design and experimentation process. The forward dynamics algorithms also provide the necessary analytical foundation for conducting analysis and simulation studies. The multiarm algorithms are based on the filtering and smoothing approach recently advanced for single-arm dynamics, and they can be built up modularly from the single-arm algorithms. The algorithms compute recursively the joint-angle accelerations, the contact forces, and the task-object accelerations. Algorithms are also developed to evaluate in closed form the linear transformations from the active joint moments to the joint-angle accelerations, to the task-object accelerations., and to the task-object contact forces. A possible computing architecture is presented as a precursor to a more complete investigation of the computational performance of the dynamics algorithms

Rigorous object-oriented analysis

Object-oriented methods for analysis, design and programming are commonly used by software engineers. Formal description techniques, however, are mainly used in a research environment. We have investigated how rigour can be introduced into the analysis phase of the software development process by combining object-oriented analysis (OOA) methods with formal description techniques. The main topics of this investigation are a formal interpretation of the OOA constructs using LOTOS, a mathematical definition of the basic OOA concepts using a simple denotational semantics and a new method for object- oriented analysis that we call the Rigorous Object-Oriented Analysis method (ROOA). The LOTOS interpretation of the OOA concepts is an intrinsic part of the ROOA method. It was designed in such a way that software engineers with no experience in LOTOS, can still use ROOA. The denotational semantics of the concepts of object-oriented analysis illuminates the formal syntactic transformations within ROOA and guarantees that the basic object- oriented concepts can be understood independently of the specification language we use. The ROOA method starts from a set of informal requirements and an object model and produces a formal object-oriented analysis model that acts as a requirements specification. The resulting formal model integrates the static, dynamic and functional properties of a system in contrast to existing OOA methods which are informal and produce three separate models that are difficult to integrate and keep consistent. ROOA provides a systematic development process, by proposing a set of rules to be followed during the analysis phase. During the application of these rules, auxiliary structures are created to help in tracing the requirements through to the final formal model. As LOTOS produces executable specifications, prototyping can be used to check the conformance of the specification against the original requirements and to detect inconsistencies, omissions and ambiguities early in the development process

A Methodology for Structured Object-Oriented Elicitation and Analysis of Temporal Constraints in Hardware/Software Co-Analysis and Co-Design of Real-Time Systems

The hardware/software co-design of a high-quality real-time system relies heavily on the modeling of both the hardware and software components from three aspects: structures, functionalities, and constraints, especially the temporal constraints. However, there is not a systematic process for the elicitation and analysis of temporal constraints in hardware/software co-design. Furthermore, existing object-oriented methods provide no means for the explicit specification of system/component constraints in object models. This paper presents a systematic methodology for structured object-oriented analysis and specification of temporal constraints in hardware/software co-analysis and co-design using an extended High-Order Object-Oriented Modeling Technique (HOOMT). This methodology hierarchically elicits and analyzes the temporal constraints in hardware/software co-design based on the integration of the High-Order Object Model (HOOM) and Hierarchical Timed Automata (HTA). It helps to identify temporal constraints of hardware and software components as well as their interactions level by level. In addition, it helps trace the relationships among these constraints at multiple levels during the co-design of real-time systems. A case study from the hardware/software co-design of the simulated FACTS Power Transmission System is used to illustrate the feasibility and merits of this methodology

Structured Object-Oriented Co-Analysis/Co-Design of Hardware/Software for the FACTS Powers System

There are several approaches to the hardware/software design in embedded systems, ranging from the traditional sequential methods which focus on the determination of the hardware architecture prior to software design, to newer object-oriented approaches that attempt to apply software engineering methods to hardware design without a systematic process. This paper discusses a structured object-oriented methodology for the integrated co-analysis and co-design of hardware/software systems using an extended high order object-oriented modeling technique (HOOMT). This methodology offers a uniform method for hardware and software developers to jointly develop the specifications for and partitioning of the hardware and software components of a system, as well as developing the interfaces between components, and allows easy design migration of components between hardware and software. In this paper it is applied to the co-analysis/co-design of the hardware and software of a simulated advanced power grid control system

ANALISIS DAN PERANCANGAN SISTEM INFORMASI AKADEMIK UNIVERSITAS BENGKULU DENGAN PENDEKATAN BERORIENTASI OBJEK (ANALYSIS AND DESIGNING OF ACADEMICALLY INFORTMATION SYSTEM BENGKULU UNIVERCITY WITH OBJECT ORIENTED APPROACH)

ABSTRACT An 00 (Object Oriented) mode consists of OOA (Object Oriented Analysis) and 001) (Object Oriented Design). A goal of OOA is to model the semantics of the problem, in terms of distinct but related object. Target which will be achieved from the OOA is domain problem mode comprises class, attribute, service and inter-object message. OOD models the solution domain, which includes the semantics classes (with possible additions), PDC, HIC, TMC and DMC classes identified during the design process. OOD also involves reexamining the problem domain classes-refining, extending or reorganizing them, to improve reusability and take advantage of inheritance. This tesis precent OOA and OOD of the registration and academics system of UNIB. During OOA process 44 classes were idénfied and groped in 6 subjects. From the test results, discussion and modification to the preliminary PDC, it can be concluded that the final PDC in this research had been able to accommodated all of the registration rules and the academically system in Bengkulu University. Keywords Academically information system, Object Oriented Analysis (OOA), Object Oriented Design (OOD

A Domain Analysis to Specify Design Defects and Generate Detection Algorithms

Quality experts often need to identify in software systems design defects, which are recurring design problems, that hinder development\ud and maintenance. Consequently, several defect detection approaches\ud and tools have been proposed in the literature. However, we are not\ud aware of any approach that defines and reifies the process of generating\ud detection algorithms from the existing textual descriptions of defects.\ud In this paper, we introduce an approach to automate the generation\ud of detection algorithms from specifications written using a domain-specific\ud language. The domain-specific is defined from a thorough domain analysis.\ud We specify several design defects, generate automatically detection\ud algorithms using templates, and validate the generated detection\ud algorithms in terms of precision and recall on Xerces v2.7.0, an\ud open-source object-oriented system