Earticle

The traditional Architectural Description Languages ADLs lack the ability to describe the crosscutting concerns and crosscutting interactions in the software architecture, which result in the design of the system difficulty in comprehension, evolution and reuse. This paper proposes a new Aspect-Oriented ADL—AC2-ADL to provide a formal basis for representation of the tangling and scattering concerns and establish the software architecture with higher dependability.

Colonic polyps appear like elliptical protrusions on the inner wall of the colon. The many proposed algorithms assumed the shape of a polyp as a spherical cap, so the algorithms are not flexible when the polyps are irregular shapes. In this paper, we propose a mapping using regional unit sphere (MuRUS) method to overcome the problem caused by unexpected polyp shapes. The MuRUS has shape invariant and size invariant properties. Our method was applied to colon CT images from 37 patients each having a prone and supine scan. There are 45 colonscopically confirmed polyps. The results obtained by our algorithm were compared with those gold standards. 100% of polyps >= 10mm in diameter were detected, 90% of polyps >= 6mm in diameter were detected and 70% of polyps < 6mm in diameter were detected at 7.0 FPs per patient.

Extreme programming (XP) is one of the most frequently used methodologies in Agile Software Development. According to various reports it had a significant effect on the software projects that use XP. In this paper, one of the main practices of XP, called "on-site customer" is considered, in detail. Also, various important challenges related to its implementation are considered. In each case, according to reports and researches related to user involvement, suitable solutions for resolving the problems are offered. At the end of each case, having an appropriate alternative that uses "Product Management Team" is proposed.

In the current marketplace, there are maturity models, standards, and guidelines that can help an organization improve the way it does business. Software process assessment models, ISO/IEC 15504 and CMMI provide good strategy to assess organization’s software development capability. However these models are too heavy to apply small and medium enterprise organization. A ISO/IEC 15504(Software Process Improvement and Capability determination) and CMMI(Capability Maturity Model Integration) can be considered as representative software process assessment models since assessors assign ratings to indicators and metrics to measure the capability of software processes. In this paper we show the K-model that can easily apply small and medium sized business to process improvement and certification in Korea. This study also compares the practices of K-model with practices of CMMI and ISO/IEC 15504. We expect the small and light model, K-model will make software process improvement of Korea enterprises.

A data model is a plan for building a database and is comparable to an architect's building plans. There are two major methodologies used to create a data model: the Entity-Relationship (ER) approach and the Object Model. This paper will be discussed only the object model approach. The goal of the data model is to certify that all data objects required by the database are completely and accurately represented. Ontologies are objects of interest (Universal of discourse). The objective of this paper is to simplify object models compare with ontologies models. There are some similarities between objects in object models and concepts sometimes called classes in ontologies. Ontology can help building object model. The object model is the center of data modeling; on the other hand ontology itself has the concept which is the basis of knowledge base. Because ontologies are closely related to modern object-oriented software design, it is good attempt to adapt existing object-oriented software development methodologies for the task of ontology development. Selected approaches originate from research in artificial intelligence; knowledge representation and object modeling are presented in this paper. Some issues mentioned in this paper are related with their connection; some are addressed directly into the similarities or differences point of view of both. This paper also presents the available tools, methods, procedures, language, reusability which shows the corporation with object modeling and ontologies.

Web services have become popular in order to access multimedia stream contents. However, these Web services are not supported with the same quality to Web clients who frequently access multimedia services. Also, ontologies provide meaning to concepts and their relationships for supporting semantic Web Service. This paper proposes ontological technique to apply user level Quality of Servic(QoS) that provides two different levels to serve Web service with proper quality by contribution value. Main contribution of this paper is to support user level QoS and to use Ontology for it. Therefore, this work uses an ontology-based approach to organize QoS, enabling semantic classification of all Web services based on domains and QoS attributes.

In relational data model, two important referential integrity constraints are inclusion dependency(ID) and foreign key(FK). In last decade, with the growing use of XML as data representation and exchange format over the web, the issue of integrity constraints in XML has received great importance to the database community. In this paper, we propose XML Inclusion Dependency(XID) and XML foreign key(XFK). When proposing, we show how both XID and XFK can be defined over the Document Type Definition(DTD) and are satisfied by the XML documents. We introduce a novel concept tuple that produces semantically correct values in the XML documents when satisfactions are checked. We also show that XFK is defined with the combination of XID and XML Key.

Improving model-based component testability can further model-based approaches to software component testing (SCT) for desirable testing effectiveness. Component contracts are useful testing-support artefacts to improve component testability. This paper presents a new contract-based SCT technique, Test by Contract (TbC), which extends the Design by Contract concept to the SCT domain, and leverages UML-based testing with the contract mechanism to design model-based test contracts for UML-based SCT. We introduce a new concept of Contract for Testability as the principal goal of the TbC technique, and develop a set of important contract-oriented concepts (test contract, effectual contract scope, and internal/external test contract) and useful test criteria to improve model-based testability. We develop a useful stepwise TbC working process, and use a case study to demonstrate how to put the TbC technique into practice to undertake contract-based SCT with UML models.