物件導向軟體之架構(Object-Oriented Software Construction)探討

Aspect] is a simple and practical aspect-oriented extension to Java With just a few new constructs, AspectJ provides support for modular implementation of a range of crosscutting concerns. In AspectJ's dynamic join point model, join points are well-defined points in the execution of the program; pointcuts are collections of join points; advice are special method-like constructs that can be attached to pointcuts; and aspects are modular units of crosscutting implementation, comprising pointcuts, advice, and ordinary Java member declarations. AspectJ code is compiled into standard Java bytecode. Simple extensions to existing Java development environments make it possible to browse the crosscutting structure of aspects in the same kind of way as one browses the inheritance structure of classes. Several examples show that AspectJ is powerful, and that programs written using it are easy to understand.

An overview of AspectJ

The objective of this paper is to give a comprehensive introduction to applied cryptography with an engineer or computer scientist in mind. The emphasis is on the knowledge needed to create practical systems which supports integrity, confidentiality, or authenticity. Topics covered includes an introduction to the concepts in cryptography, attacks against cryptographic systems, key use and handling, random bit generation, encryption modes, and message authentication codes. Recommendations on algorithms and further reading is given in the end of the paper. This paper should make the reader able to build, understand and evaluate system descriptions and designs based on the cryptographic components described in the paper.

[서평]「Applied Cryptography」

The Quark and the Jaguar

A translation apparatus is provided which comprises: an inputting section for inputting a source document in a natural language; a layout analyzing section for analyzing layout information including cascade information, itemization information, numbered itemization information, labeled itemization information and separator line information in the source document inputted by the inputting section and specifying a translation range on the basis of the layout information; a translation processing section for translating a source document text in the specified translation range into a second language; and an outputting section for outputting a translated text provided by the translation processing section.

Automated Planning: Theory and Practice.

Web services are becoming progressively popular in the building of both inter- and intra-enterprise business processes. These processes are composed from existing Web services based on defined requirements. In collecting together the services for such a composition, developers can employ languages and standards for the Web that facilitate the automation of Web service discovery, execution, composition and interoperation. However, there is no guarantee that a composition of even very good services will always work. Mechanisms are being developed to monitor a composition and to detect and recover from faults automatically. A key factor in such self-healing is to know what faults to look for. If the nature of a fault is known, the system can suggest a suitable recovery mechanism sooner. This paper proposes a novel taxonomy that captures the possible failures that can arise in Web service composition, and classifies the faults that might cause them. The taxonomy covers physical, development and interaction faults that can cause a variety of observable failures in a system's normal operation. An important use of the taxonomy is identifying the faults that can be excluded when a failure occurs. Examples of using the taxonomy are presented.

/pdf/a-fault-taxonomy-for-web-service-composition-2k44u9hiu8.pdf

A Fault Taxonomy for Web Service Composition

The management of variability plays an important role in successful software product line engineering There is a need for a universal variability management approach to be consistent and scalable; it should provide traceability between variations at different levels of abstraction and across various generic development artifacts; and there should be a means for visualizing variability Focusing specifically on the aspect of traceability in the context of such an approach, we define a conceptual variability model that captures variability information in a third dimension, and allows a 1-to-1 mapping of variability between the problem space and the solution space Decision models, of which the feature model is most popular, are commonly used for, amongst others, managing traceability of variation These, however, usually reside in a two dimensional space We analyze the feature model in a small case study with regards to our conceptual variability model, and present our findings

/pdf/tracing-software-product-line-variability-from-problem-to-2h0mdu8y9u.pdf

Tracing software product line variability: from problem to solution space

Massive Open Online Courses (MOOCs) have recently gained high popularity among various universities and even in global societies. A critical factor for their success in teaching and learning effectiveness is assignment grading. Traditional ways of assignment grading are not scalable and do not give timely or interactive feedback to students. To address these issues, we present an interactive-gaming-based teaching and learning platform called Pex4Fun. Pex4Fun is a browser-based teaching and learning environment targeting teachers and students for introductory to advanced programming or software engineering courses. At the core of the platform is an automated grading engine based on symbolic execution. In Pex4Fun, teachers can create virtual classrooms, customize existing courses, and publish new learning material including learning games. Pex4Fun was released to the public in June 2010 and since then the number of attempts made by users to solve games has reached over one million. Our work on Pex4Fun illustrates that a sophisticated software engineering technique -- automated test generation -- can be successfully used to underpin automatic grading in an online programming system that can scale to hundreds of thousands of users.

https://www.microsoft.com/en-us/research/wp-content/uploads/2013/05/icse13see-pex4fun.pdf

Teaching and learning programming and software engineering via interactive gaming

Objects, Models, Components, Patterns

Technology plays an ever-increasing role in our everyday lives. We would like it to be a help rather than a hurdle in our work, particularly in collaborating with others. An emerging problem for both individuals and groups is information spread and neglect, where users have the same copy of the same work, stored on various conventional devices, but no way to keep track of where the most recent version resides. One type of computer support collaborative work application, groupware, tackles this problem, aiming to assist in joint authoring projects, where artifacts such as files, pictures, reports and sound are being gathered to form a whole. Such groupware systems - and we survey seven of them - vary in terms of their functional, architectural, focal, temporal, user involvement and platform dependencies. While we found a wide variety of options for each system, there were also strong commonalities. All of them work with closed communities or groups. There is no public file sharing. All users are aware of all other collaborators in the community and all systems focus on collaboration; not sharing. The comparison includes our own system Nomad, a framework for distributed resource management, with special emphasis placed on the accessibility of information stored on detached devices, such as personal computers, laptops, PDA's and flash-disks. In the comparison, Nomad has advantages of flexibility and temporal independence over the other systems, together with low requirements on the user, and a high level of mobility and platform independence. The contributions of this paper are twofold: we identify and define a specific type of CSCW, groupware, together with a set of criteria for evaluating such systems; and we survey and classify some of the main systems according to the criteria, as well as introducing a custom-designed system, Nomad. From these results, a collaborative group of workers can more easily select a specific groupware that suits its needs. Moreover, designers of new systems will find the commonality factors useful, so they can more easily position their own products.

Judith Bishop

Papers

A Fault Taxonomy for Web Service Composition

Tracing software product line variability: from problem to solution space

Teaching and learning programming and software engineering via interactive gaming

Objects, Models, Components, Patterns

A survey and comparison of CSCW groupware applications