Oriented Software Development Research Articles

An Analysis on Software Testability and Security in Context of Object and Aspect Oriented Software Development

Testability is a property of program which introduces with the purpose of forecasting efforts need to test the programs. Software quality is the most important factor in the development of software, which depend upon many quality attributes. The absence of testability is responsible for higher maintenance and testing effort. This paper presents a literature review on software testability and its importance. Object-Oriented and Aspect-Oriented metrics are considered for analysis. These metrics are closely related to the Software quality factors i.e. Controllability, Observability, Built in Test Capability, Understandability and Complexity, all these factors are independent to each other. We have identified factors which affect software testability in general as well specific to Aspect Oriented Systems. In addition to testability, security features in term of aspect oriented programming have been explored.

Composition of Aspectual Requirements: A Multi-criteria Process for Conflict Resolution

In Aspect Oriented Software Development, aspects are not only used at the programming level but also tend to arise at the requirements analysis and software architecture design. We previously proposed an approach named AspeCiS (An aspect-oriented Approach to Develop a Cooperative Information System) to develop a Cooperative Information System from existing Information Systems by using their artifacts such as existing requirements and design elements. This approach include an important step in which the aspectual requirements composition problem is considered to be one of the remaining challenges. So, when multiple aspectual requirements share the same join point, undesired behavior may emerge and a conflict resolution process must be triggered. This study presents a conflict resolution process among aspects during the requirements engineering level: A priority value is computed for each aspect and it allows identifying a dominant aspectual requirement on the basis of stakeholder priority. This process is more formal than those currently proposed, which requires a trade-off negotiation to resolve conflicts.

The Research on Software Reuse Technology

Software reuse has gained increasing attention by academic organizations and software development agencies. Existing researches on software pattern concentrate on constructing and representing patterns in unstructured way, so it is difficult to maintain and reuse them. This article puts forward pattern-oriented software development process that integrates modeling method based on architecture with software process for software reuse. Through the research on pattern oriented software development process, the reusability of software is enhanced.

Exploring modal worlds

Modal idempotent semirings cover a large set of different applications. The paper presents a small collection of these, ranging from algebraic logics for program correctness over bisimulation refinement, formal concept analysis, database preferences to feature oriented software development. We provide new results and/or views on these domains; the modal semiring setting allows a concise and unified treatment, while being more general than, e.g., standard relation algebra.

Agent Based Distributed Tutoring System modeling using Extended Tropos approach

Due to the availability of enormous amount of resources for the tutoring system, there is a need for the distribution of the resources when developing such tutoring system.There are several users inthe distributed system where there is aconcurrent access of the resources. In such scenario there should be a definite access control policies for the resources. Since the agents are suitable for the distributed system and these access control policies would restrict the agents in accessing the resources. In our work we have extended Tropos which is an agent oriented software development methodology.Our extension would classify the resources based on the types of resources by which it can be accessed by other agents. This extension would also consider the temporal constraints in accessingthe resources. The resources have been classified into four types and the temporal constraints have been classified into three types. Our approach provides a systematic way of development of the distributed systems than the formal UML modeling technique by capturing the security constraints and providing the access control policies in the modeling stage itself. In our work, the Agent based distributed Tutoring System(ABDTS) has been taken as a case study and we have modeled the system using the extended Tropos methodology and the results are evaluated. We also we provide a comparativeanalysis between the models developed using Tropos, Unified Modeling Language (UML) which could incur that the Tropos could be used where the agents goals and tasks are to be modeled explicitly.

New Set of Metrics for Accessing Usability in Feature Oriented Programming

Quality and complexity assessment are critical aspects in feature oriented software development. Feature oriented development is part of software product line methodology where software is framed using feature concept. In course of research; object oriented metrics are being used to assess the quality of feature model. But these metrics limit the complexity within the features and complexity across the classes and features relationship are untouched .This state of art proposes a new set of metrics to provide usability and complexity assessment crosswise the feature-class relationship. This will provide better understanding of feature oriented system and help to develop a sustainable system.

AO4AADL: Aspect oriented extension for AADL

Abstract Managing embedded system complexity and scalability is one of the most important problems in software development. To better address this problem, it is very recommended to have an abstraction level high enough to model such systems. Architectural description languages (ADLs) intend to model complex systems and manage their structure at a high abstraction level. Traditional ADLs do not normally provide appropriate formalisms to separate any kind of crosscutting concerns. This frequently results in poor descriptions of the software architectures and a tedious adaptation to constantly changing user requirements and specifications. AOSD (Aspect Oriented Software Development) deals with these problems by considering crosscutting concerns in software development. The effectiveness of considering an aspect-oriented architectural design appears when aspect concepts are taken into account early in the software’s life-cycle. In this paper, we propose a new aspect language called AO4AADL that adequately manipulates aspect oriented concepts at architecture level in order to master complexity and ensure scalability. The abstract nature of our proposed language allows the generation of aspect code for several programming languages and platforms.

Agglomerative Hierarchical Approach for Clustering Components of Similar Reusability

This paper presents a clustering approach for grouping components of similar reusability using an already worked out fuzzy data set [2]. Research has shown that, component based systems development concept benefits the object oriented software development. A Component based system achieves flexibility by clearly separating the stable parts of systems from the specification of their composition. Many software systems contain many similar or even identical components and these components are developed from scratch over and over again which require extra effort. So to minimize the extra effort in developing these components, it is more beneficial to reuse the existing components. To reuse components effectively in Component Based Software Development, it is required to quantify the reusability of components. However it is difficult to use clustering approach to predict reusability. This paper discusses a technique to cluster components of similar reusability together for the purpose of minimizing the efforts of the developer using agglomerative hierarchical clustering. Components attribute affecting the reusability are classified into rules using fuzzy system and are then taken as the inputs to the proposed clustering model.

Using UML Behavioral Model to Support Aspect Oriented Model

Aspect oriented software development is an emerging paradigm of software development. The notion of this technique is separation of concerns which means to implement each concern in a single object in object oriented programming but still there are concerns which are distributed on different objects and are called crosscutting concerns while another form is Core concerns are the core functionality provided by the system but crosscutting concerns are the concerns like logging, performance etc. Modeling of aspect oriented software is different from the normal modeling of object-oriented or procedural language software, because aspects don’t have the independent identity or existence and they are tightly coupled to their woven context so it is difficult to model them. The one aim of our research paper is to explore the domain of Modeling of the aspect-oriented software. The goal of this research paper is to give a UML Behavioral modeling techniques in the domain of aspect oriented software development. This technique of generating UML Behavioral Model for aspects will give better understating of separations concerns.

SRS Document Proposal Analysis on the Design of Management Information Systems According to IEEE STD 830-1998

A software development process generally consists of several stages ranging from analysis to implementation, which will result in need (requirement) of software. Results of analysis for different applications in a similar problem domain will usually produce similar definition needs. In the field of software engineering, especially in object- oriented software development, requirements for different problem domain have been developed. This research is to obtain a similarity (commonality) of the software requirements specifications, here in after in short-SRS. Management Information System (MIS) has been chosen due to several years has developed into concepts that are essential both in the scope of major agencies as well as small and medium scale. SRS is the identification of commonality for the MIS application which is focused on the function of customer service standards, particularly for the Management Information System. From this research it also can be concluded that the SRS commonality can be generated by capturing best practices from existing business processes.

Sm@rtConfig: A context-aware runtime and tuning system using an aspect-oriented approach for data intensive engineering applications

Distributing the workload upon all available Processing Units (PUs) of a high-performance heterogeneous platform (e.g., PCs composed by CPU–GPUs) is a challenging task, since the execution cost of a task on distinct PUs is non-deterministic and affected by parameters not known a priori. This paper presents Sm@rtConfig, a context-aware runtime and tuning system based on a compromise between reducing the execution time of engineering applications and the cost of tasks' scheduling on CPU–GPUs' platforms. Using Model-Driven Engineering and Aspect Oriented Software Development, a high-level specification and implementation for Sm@rtConfig has been created, aiming at improving modularization and reuse in different applications. As case study, the simulation subsystem of a CFD application has been developed using the proposed approach. These system's tasks were designed considering only their functional concerns, whereas scheduling and other non-functional concerns are handled by Sm@rtConfig aspects, improving tasks modularity. Although Sm@rtConfig supports multiple PUs, in this case study, these tasks have been scheduled to execute on an platform composed by one CPU and one GPU. Experimental results show an overall performance gain of 21.77% in comparison to the static assignment of all tasks only to the GPU.

Report from the 3rd international workshop on requirements prioritization for customer oriented software development

Prioritization is an essential task within requirements engineering to cope with complexity and to establish focus properly. The 3rd Workshop on Requirements Prioritization for customer oriented Software Development (RePriCo'12) focused on requirements prioritization and adjacent themes in the context of customer oriented development of bespoke and standard software. Five submissions have been accepted for the proceedings and for presentation. The report summarizes and points out key findings.

Object Oriented Software Effort Estimate with Adaptive Neuro Fuzzy use Case Size Point (ANFUSP)

Use case size point (USP) method has been proposed to estimate object oriented software development effort in early phase of software project and used in a lot of software organizations. Intuitively, USP is measured by counting the number of actors, preconditions, post conditions, scenarios included in use case models. In this paper have presented a Adaptive fuzzy Neural Network model to estimate the effort of object oriented software using Use Case size Point approach. In our proposed system adaptive neural network fuzzy use case size point has less error and system worked more accurate and appropriative than prior methods.

PENGEMBANGAN SISTEM INFORMASI SELEKSI BEASISWA UNGGULAN P3SWOT KEMDIKNAS ONLINE MENGGUNAKAN UNIFIED PROCESS

The Ministry of National Education has declared excellence scholarship program, one kind of these excellence scholarships is P3SWOT. P3SWOT is an excellence scholarship given to researcher, writer, creator, artist, journalist, athlete, and figure. As a holder of P3SWOT excellence scholarship, the Secretary of Excellence Scholarship, Bureau Planning and International Cooperation, the Ministry of National Education has been taking the advantage of the information technology by building a website that provides registration information, a registration form that can be downloaded by registrant, and the announcement of the scholarship winners. However, the website is not optimal because it is static. The selection mechanism of P3SWOT excellence scholarship still has some problems. Recently there are ineffective registration and unintegrated scholarship registration data. The online selection of P3SWOT excellence scholarship information system was developed to solve those problems. This information system was developed using Unified Process. Unified Process is an object oriented software development process that consists of five workflows. They are requirement, analysis, design, implementation, and test. This information system was built using PHP 5 programming language and MySQL 5 database management system. This information system can be used to handle the selection of P3SWOT excellence scholarship including registration, registration verification and scoring, deciding the winners, and reporting.

Feature interactions, products, and composition

The relationship between feature modules and feature interactions is not well-understood. To explain classic examples of feature interaction, we show that features are not only composed sequentially, but also by cross-product and interaction operations that heretofore were implicit in the literature. Using the Colored IDE (CIDE) tool as our starting point, we (a) present a formal model of these operations, (b) show how it connects and explains previously unrelated results in Feature Oriented Software Development (FOSD) , and (c) describe a tool, based on our formalism, that demonstrates how changes in composed documents can be back-propagated to their original feature module definitions, thereby improving FOSD tooling.

선박 추진시스템 설계를 위한 PDM 구현

Present study introduces an implementation of product data management (PDM) that can be applied to the design of ship propulsion system. The PDM system is developed based on both object oriented software development environment and Open Scene Graph (OSG) library while the system architecture is modeled by the unified modeling language (UML). Suggested PDM system also integrates the modeling & simulation components required to estimate the performance of ship propulsion system as the product information is represented based on the 3-dimensional digital mock-up (DMU). Finally, functions of the implemented PDM system that is integrated with the M&S softwares are illustrated in order to suggest a practical guidance for the efficient design of ship propulsion system.

Process–Oriented Software Development Based on HPN Business Process Model

In order to develop the process-oriented software, we put forward hierarchical colored Petri net (HCPN) to model business process. This approach consists of hierarchical decomposition graph, detailed process graph. Furthermore, the concept of business process components (BPCs) is proposed to facility the business process modeling. The software components, which are constructs of the information system, can be derived by means of the mapping from the relevant business process components. The development of business process-oriented application will be more convenient and rapid based on component library. Such an application becomes more flexible to the changing environment.

Role of UML Class Diagram in Object-Oriented Software Development

Role of UML Class Diagram in Object-Oriented Software DevelopmentUML is an industrial standard for object-oriented software specification which offers a notation for class modeling during object oriented software development. Since the UML class diagram is a so-called "bridge" between software specification at the user side and software realization at the developer side, it requires strong guidelines for identification of class objects from the problem domain and notational conventions for modeling of the class diagram for its further usage in system coding. This paper presents a discussion on problematic stages and possible element transformations into software components. Several conclusions are drawn on potential usage of the class diagram in industry.

Incorporating AOSD to Enhance Model Driven Architecture

Various software development approaches in the present scenario are best suited for a specific application. The software development strategies include both merits and demerits when talked in terms of generalization. The Model Driven Architecture (MDA) describes software development based on models on various levels of abstraction. The model driven software development process consists of sequence of model transformations between various models. This paper presents incorporation of the merits of Aspect Oriented Software Development (AOSD) like modularization, reusability and reduced complexity into Model Driven Architecture (MDA) software development strategy. The proposed Model Driven Software Development approach which combines the merits of MDA and AOSD meets the ever changing and challenging demand of the enterprise software development.

Aspect Oriented Software Development vs. other Techniques (Structured Approach and Object Oriented Approach)

Aspects are a natural evolution of the object-oriented paradigm. They provide a solution to some difficulties you may have encountered with modularizing your object-oriented code: sometimes functionality just doesn't fit! You've probably found yourself repeating the same lines of code in lots of different object-oriented classes because those classes each need that functionality, and so you can't easily wrap it up in a single place. Good examples of this kind of code are audit trails, transaction handling, concurrency management, and so on. You can now modularize such code with aspects. Aspect-Oriented Software Development (AOSD). Provides unique and advanced program structuring and modularization techniques. The implementation of software applications using AOSD techniques results in a better implementation structure which has an impact on many important software qualities such as enhanced reusability and reduced complexity. In turn, these software qualities lead to an improved software development lifecycle and, hence, to better software.