36,245 research outputs found
Aligning a Service Provisioning Model of a Service-Oriented System with the ITIL v.3 Life Cycle
Bringing together the ICT and the business layer of a service-oriented system
(SoS) remains a great challenge. Few papers tackle the management of SoS from
the business and organizational point of view. One solution is to use the
well-known ITIL v.3 framework. The latter enables to transform the organization
into a service-oriented organizational which focuses on the value provided to
the service customers. In this paper, we align the steps of the service
provisioning model with the ITIL v.3 processes. The alignment proposed should
help organizations and IT teams to integrate their ICT layer, represented by
the SoS, and their business layer, represented by ITIL v.3. One main advantage
of this combined use of ITIL and a SoS is the full service orientation of the
company.Comment: This document is the technical work of a conference paper submitted
to the International Conference on Exploring Service Science 1.5 (IESS 2015
Annotated bibliography of Software Engineering Laboratory literature
An annotated bibliography of technical papers, documents, and memorandums produced by or related to the Software Engineering Laboratory is given. More than 100 publications are summarized. These publications cover many areas of software engineering and range from research reports to software documentation. All materials have been grouped into eight general subject areas for easy reference: The Software Engineering Laboratory; The Software Engineering Laboratory: Software Development Documents; Software Tools; Software Models; Software Measurement; Technology Evaluations; Ada Technology; and Data Collection. Subject and author indexes further classify these documents by specific topic and individual author
JWalk: a tool for lazy, systematic testing of java classes by design introspection and user interaction
Popular software testing tools, such as JUnit, allow frequent retesting of modified code; yet the manually created test scripts are often seriously incomplete. A unit-testing tool called JWalk has therefore been developed to address the need for systematic unit testing within the context of agile methods. The tool operates directly on the compiled code for Java classes and uses a new lazy method for inducing the changing design of a class on the fly. This is achieved partly through introspection, using Java’s reflection capability, and partly through interaction with the user, constructing and saving test oracles on the fly. Predictive rules reduce the number of oracle values that must be confirmed by the tester. Without human intervention, JWalk performs bounded exhaustive exploration of the class’s method protocols and may be directed to explore the space of algebraic constructions, or the intended design state-space of the tested class. With some human interaction, JWalk performs up to the equivalent of fully automated state-based testing, from a specification that was acquired incrementally
BAREMO: How to Choose the Appropriate Software Component Using the Analytic Hierarchy Process
To select a software component from several similar candidates is a complex task, since each project pursues different objectives. We intend to use the Analytic Hierarchy Process in the taking of multicriteria decisions for software component reuse. This method is called BAREMO. It will help the software engineer to make estimations which will enable him/her to choose the appropriate component. The article presents a case study of the application of the method, where a project manager assesses a certain software component in order to consider its reuse in the domain of image processing
Annotated bibliography of software engineering laboratory literature
An annotated bibliography of technical papers, documents, and memorandums produced by or related to the Software Engineering Laboratory is given. More than 100 publications are summarized. These publications cover many areas of software engineering and range from research reports to software documentation. This document has been updated and reorganized substantially since the original version (SEL-82-006, November 1982). All materials have been grouped into eight general subject areas for easy reference: the Software Engineering Laboratory; the Software Engineering Laboratory-software development documents; software tools; software models; software measurement; technology evaluations; Ada technology; and data collection. Subject and author indexes further classify these documents by specific topic and individual author
Object-oriented Programming Laws for Annotated Java Programs
Object-oriented programming laws have been proposed in the context of
languages that are not combined with a behavioral interface specification
language (BISL). The strong dependence between source-code and interface
specifications may cause a number of difficulties when transforming programs.
In this paper we introduce a set of programming laws for object-oriented
languages like Java combined with the Java Modeling Language (JML). The set of
laws deals with object-oriented features taking into account their
specifications. Some laws deal only with features of the specification
language. These laws constitute a set of small transformations for the
development of more elaborate ones like refactorings
Specifying Reusable Components
Reusable software components need expressive specifications. This paper
outlines a rigorous foundation to model-based contracts, a method to equip
classes with strong contracts that support accurate design, implementation, and
formal verification of reusable components. Model-based contracts
conservatively extend the classic Design by Contract with a notion of model,
which underpins the precise definitions of such concepts as abstract
equivalence and specification completeness. Experiments applying model-based
contracts to libraries of data structures suggest that the method enables
accurate specification of practical software
- …