In recent years, enterprise applications have begun to migrate from a local hosting to a cloud provider and may have established a business-to-business relationship with each other manually. Adaptation of existing applications requires substantial implementation changes in individual architectural components. On the other hand, users may store their Personal Identifiable Information (PII) in the cloud environment so that cloud services may access and use it on demand. Even if cloud services specify their privacy policies, we cannot guarantee that they follow their policies and will not (accidentally) transfer PII to another party. In this paper, we present Identity-as-a-Service (IDaaS) as a trusted Identity and Access Management with two requirements: Firstly, IDaaS adapts trust between cloud services on demand. We move the trust relationship and identity propagation out of the application implementation and model them as a security topology. When the business comes up with a new e-commerce scenario, IDaaS uses the security topology to adapt a platform-specific security infrastructure for the given business scenario at runtime. Secondly, we protect the confidentiality of PII in federated security domains. We propose our Purpose-based Encryption to protect the disclosure of PII from intermediary entities in a business transaction and from untrusted hosts. Our solution is compliant with the General Data Protection Regulation and involves the least user interaction to prevent identity theft via the human link. The implementation can be easily adapted to existing Identity Management systems, and the performance is fast.
Abstract:The growing complexities of software and the demand for shorter time to market are two important challenges that face today's IT industry. These challenges demand the increase of both productivity and quality of software. Model-based testing is a promising technique for meeting these challenges. Traceability modeling is a key issue and challenge in model-based testing. Relationships between the different models will help to navigate from one model to another, and trace back to the respective requirements and the design model when the test fails. In this paper, we present an approach for bridging the gaps between the different models in model-based testing. We propose relation definition markup language (RDML) for defining the relationships between models.
Reusing software components is an important but not standardised task in software engineering. This will become a problem if requirements change in the future. By the use of web services in service-oriented architecture, as a communication interface for devices, the automation area has to define how to handle these reusable units. At the moment, no standardised way is defined. This publication analyses the use of web services in a service-oriented environment as a communication interface of physical devices in the area of automation. An analysis matrix will be built by the use of defined research challenges of web services and known reuse aspects in the area of software engineering. The results of a Device Profile for Web service (DPWS) case study will be compared to this matrix in order to define research steps and important factors for device services for the future.
Today's software units (classes, components and services) require large amounts of information during their development and use that can be documented for future reference, like documentation, multimedia files, specification, and models. The availability of certain information, for example documentation, is one of the factors that determines the capabilities of a unit, especially by reusing it. Additional information is necessary and essential for the success of the entire development process when applying certain procedure models, like Rational Unified Process (RUP). Acquiring these units and their content is important for reuse. However, this causes a problem in the area of global cooperation. Currently, approaches are missing that deal with software reuse in distributed software reuse scenarios. Especially the problem of missing knowledge about integration of reusable software units in these scenarios has not yet been addressed. This knowledge is also an important factor for reuse and reuse decisions. As a result software development teams locate at different locations my have problem to integrate exchanged reusable software units. This paper discusses the challenges of integration in distributed reuse scenarios by focusing on an industrial example and create a model extension for a existing reuse system. As an result integration of reusable software units can be done remotely without the necessary integration knowledge.
The development of software applications is partly or entirely based on the re-use of software units. For software engineers, this leads to the problem that it is not possible to know all processes, technologies and supporting applications and the alternatives needed for the re-use of a software unit. As a result software engineers are not able to employ the most optimal solution known. Based on case based reasoning this paper outlines a way to use the stored knowledge of a specific re-use activity in order to give software engineers assistance if they want to perform similar activities. This solution consists of a proposal system for a re-use activity information system. The publication concludes with the result that it is possible to re-use, within a given an environment, specific knowledge for other integration activities.
scite is a Brooklyn-based organization that helps researchers better discover and understand research articles through Smart Citations–citations that display the context of the citation and describe whether the article provides supporting or contrasting evidence. scite is used by students and researchers from around the world and is funded in part by the National Science Foundation and the National Institute on Drug Abuse of the National Institutes of Health.
hi@scite.ai
10624 S. Eastern Ave., Ste. A-614
Henderson, NV 89052, USA
Copyright © 2024 scite LLC. All rights reserved.
Made with 💙 for researchers
Part of the Research Solutions Family.