• Journal of KIISE:Software and Applications
• /
• v.30 no.3_4
• /
• pp.293-307
• /
• 2003

Object-oriented development has been generalized, but object-oriented project planning and scheduling techniques have not been studied enough. Furthermore, it is difficult to apply the conventional software management techniques to object-oriented projects. Especially, the large scaled projects are increasing, but the project planing techniques for these large scaled projects have not been proposed enough. In this paper, we propose systematic techniques for OO based project scheduling. We suggest a 7 step-process for deriving the OO project schedule from the use-case diagram which is describing the functional requirements of the system. The proposed process includes identifying use-cases, drawing preliminary chart through interdependency analysis, identifying characteristics of each use case, determining the number of iteration, assigning use-cases to iteration, considering available resource and constraints, drawing revised PERT chart. Each step has the explanation of the input, output, and the guidelines needed to perform the step. The project scheduling technique proposed in this paper ran be used effectively in the planning phase which the purpose is to plan a development schedule to yield the high quality software in minimum time.

• Journal of the Korean Institute of Intelligent Systems
• /
• v.15 no.6
• /
• pp.780-787
• /
• 2005

Many researches and validations for the complexity metrics of the object-oriented systems have been studied. Most of them are aimed for the measurement of the partial aspects of the systems, for example, the coupling between objects, the complexity of inheritance structures, the cohesion of methods, and so on. But the software practitioners want to measure the complexity of overall system, not partial. We studied the complexity of the overall structures of object-oriented systems by analyzing the class diagram of UML. The class diagram is composed of classes and their relations. There are three kinds of relations, association, generalization, and aggregation, which are making the structure of object-oriented systems to be difficult to understand. We proposed a heuristic metric to measure the complexity of object-oriented systems by putting together the three kinds of the relations. Tn analyze the complexity of the structure of a object-oriented system for the maintainability of the system, we measured the degree of understandability of it, the reverse engineering time to draw a class diagram from the source codes, and the number of errors in the diagram. The results of this experiment shows that our proposed metric has a considerable relationship with the complexity of object-oriented systems. The metric will be helpful to the software developers for their designing tasks by evaluating the complexity of the structures of object-oriented systems and redesigning tasks , of them for the future maintainability.

• The Journal of Korean Association of Computer Education
• /
• v.5 no.1
• /
• pp.99-108
• /
• 2002

As window programming and internet programming are more required, requirement of the training on the object-oriented programming and the object oriented software development are growing. But, it is not easy to learn new brand methodologies or techniques. In this paper, we tried to apply software reuse to object modeling education for effective learning of new programming and modeling method. In this paper, we present analogical matching techniques for the reuse of object models and patterns in object modeling education. Analogy-based matching is better than keyword-based retrieval for model reuse. Reuse can help to reduce the learning curve of object modeling. Also, by applying analogical reasoning, the performance of retrieval is better than keyword-based retrieval.

• The Transactions of the Korea Information Processing Society
• /
• v.3 no.7
• /
• pp.1739-1752
• /
• 1996

Software reengineering involves improving the software maintenance process and improving existing systems by applying new technologies and software tools. Software reengineering can help us understand existing systems and discover software components that are common across systems. In the paper, we discuss the program analysis and environment to assist reengineering. Program analysis takesan existing program as input and generates information about structured part and object-oriented part. It is used to restructure the information by extracting code through reengineering methodology. These restructuring informations with object-oriented archilccture are mapping prolog form to query by using direct reation and summary relation.

• Journal of the Korea Society of Computer and Information
• /
• v.5 no.2
• /
• pp.37-42
• /
• 2000

Object technologies like the OMG's CORBA are enabling technologies the aim to facilitate integration implementation of diverse software components in distributed. heterogeneous environment. CORBA and similar object integration technologies define a standard component interconnection and inter-operation model , promote object-oriented principles to encapsulate incompatible component implementations. In this Paper. we present a connector model for software architectural representation of complex component collaborations. Our Connector model is base on research in software achitecture and object-oriented modeling. and part of a design framework for modeling component-based system. We believe the connector concepts to be vary benificial for a clear expression of dependencies between multiple component in Java Bean-based system.

• Journal of the Korea Convergence Society
• /
• v.9 no.8
• /
• pp.17-24
• /
• 2018

Design patterns can be classified as software reuse technique that might provide effective solutions to specific problems that occur repeatedly in software development. In particular, object-oriented design patterns are incorporated into various software platforms and frameworks to increase software productivity. This paper aims to support general guidelines relating to design patterns for Android-based game programming. The proper use of the design pattern could be effective in not only for software development productivity, but also for post-development software maintenance. This paper provides fundamental procedures and case studies for applying design patterns to game programming on the Android platform. Typical object-oriented design patterns such as MVP, Singleton, Observer, and State have been applied to the development of Android game programs.

• Journal of the Korea Society of Computer and Information
• /
• v.3 no.1
• /
• pp.63-80
• /
• 1998

In object-oriented software development, reuse has been studied for the enhancement of software quality and software developer's productivity. But improper modeling in design phase and uncontrolled change during maintenance activities have a problem to reuse a class. In this paper we analyze a semantic cohesion of classes using C++ Program dependency graph, and slice a class with cohesion, so that this method supports the re-estimate of class quality and the extensibility of class. Therefore this proposed method in this paper increases the easibility of the restructuring in the reusable systems, when the developer selects a requested component for a object-oriented program development.

• The Transactions of the Korea Information Processing Society
• /
• v.3 no.4
• /
• pp.817-833
• /
• 1996

Most object-oriented analysis and design methodologies are based on structured analysis and information modeling and are using for intuitive analysis and design models based on object-oriented programming languages. Therefore there are many problems such as when a system is implemented incorrect semantics and inconsistency between models.This paper submits a decomposition and design method for object, dynamic and functional module of the methodology of a new system development life-cycle. Thus, we present a new system development life cycle, and suggestsa object-oriented design methodand standards of module decomposition for the decomposition of object, dynamic, functional models due to object-oriented design procedures and specifications. This proposed method enables developers to reflect user's software requirements conveniently. We prove the validity and practicality of this object-oriented design method through implementing a real-system.

• The KIPS Transactions:PartD
• /
• v.10D no.5
• /
• pp.859-872
• /
• 2003

Class hierarchies often constitute the backbone of object-oriented software. Their quality is therefore quite crucial. Building class hierarchies with good qualify is a very important and common tasks on the object oriented software development, but such hierarchies are not so easy to build. Moreover, the class hierarchy structure under construction is frequently restructured and refined until it becomes suitable for the requirement on the iterative and incremental development lifecycle. Therefore, there has been renewal of interest in all methodologies and tools to assist the object oriented developers in this task. In this paper, we define a set of quantitative metrics which provide a wav of capturing features of a rough estimation of complexity of class hierarchy structure. In addition to, we suggest a set of algorithms that transform a original class hierarchy structure into reorganized one based on the proposed metrics for class hierarchy structure. Furthermore, we also prove that each algorithm is "object-preserving". That is, we prove that the set of objects are never changed before and after applying the algorithm on a class hierarchy. The technique presented in this paper can be used as a guidelines of the construction, restructuring and refinement of class hierarchies. Moreover, the proposed set of algorithms based on metrics can be helpful for developers as an useful instrument for the object-oriented software development.velopment.

• Water for future
• /
• v.31 no.6
• /
• pp.21-25
• /
• 1998