A Collaborative Commerce Framework for the Real Estate Industry

The Internet opens up new business opportunities for the real estate industry. It provides real estate companies with new ways to collaborate with service providers, gain customer and market information, and communicate with the customer in new ways to turn the industry into a customer-centric driven modus operandi. It also makes the real-estate market more transparent, and hence more efficient. This, in turn, will create downward pressure on existing commission fees, create multiple revenue channels, and redefine the role of the agent as an intermediary. A collaborative commerce-model framework is developed and illustrated to act as an enabler for turning these opportunities into a future reality. The collaborative model is based on a generic e-business applications framework, which incorporates Enterprise Resource Planning, Supply Chain Management, Customer Relationship Management, Selling Chain Management, and Enterprise Application Integration and Business Intelligence

System Design for a Data-driven and Explainable Customer Sentiment Monitor

The most important goal of customer services is to keep the customer satisfied. However, service resources are always limited and must be prioritized. Therefore, it is important to identify customers who potentially become unsatisfied and might lead to escalations. Today this prioritization of customers is often done manually. Data science on IoT data (esp. log data) for machine health monitoring, as well as analytics on enterprise data for customer relationship management (CRM) have mainly been researched and applied independently. In this paper, we present a framework for a data-driven decision support system which combines IoT and enterprise data to model customer sentiment. Such decision support systems can help to prioritize customers and service resources to effectively troubleshoot problems or even avoid them. The framework is applied in a real-world case study with a major medical device manufacturer. This includes a fully automated and interpretable machine learning pipeline designed to meet the requirements defined with domain experts and end users. The overall framework is currently deployed, learns and evaluates predictive models from terabytes of IoT and enterprise data to actively monitor the customer sentiment for a fleet of thousands of high-end medical devices. Furthermore, we provide an anonymized industrial benchmark dataset for the research community

Developing Distributed System with Service Resource Oriented Architecture

 Service oriented architecture (SOA) is a design paradigm in software engineering for an enterprise scale which built in a distributed system environment. This paradigm aims at abstracting of application functionality as a service through a protocol in web service technology, namely simple object access protocol (SOAP). However, SOAP have static characteristic and oriented by the service methode, so have restrictiveness on creating and accessing for big numbers of service. For this reason, this reasearch aims at combining SOA with resource oriented architecture (ROA) that is oriented by the service resource use representational state transfer (REST) protocol in order to expand scalability of service. This combination is namely service resource oriented architecture (SROA). SROA can optimize distributing of applications and integrating of services where is implemented to develop the project management software. To realize this model, the software is developed according with framework of Agile model driven development (AMDD) to reduce complexities on the whole stage processing of software development

Invited Paper: A Generalized, Enterprise-Level Systems Development Process Framework for Systems Analysis and Design Education

Current academic and industry discussions regarding systems development project approaches increasingly focus on agile development and/or DevOps, as these approaches are seen as more modern, streamlined, flexible, and, therefore, effective as compared to traditional plan-driven approaches. This extends to the current pedagogy for teaching systems analysis and design (SA&D). However, overemphasizing agile and DevOps neglects broader dimensions that are essential for planning and executing enterprise-level systems projects. Thus, a dilemma may arise: do we teach agile and DevOps techniques that may be inadequate for enterprise-level projects or do we teach the wider range of plan-driven skills and techniques that may conflict with the tenets and benefits of agile and DevOps? In this paper, we advocate for resolving this dilemma by adopting a generalized process framework that both fully supports enterprise-level projects but can also be selectively scaled back toward increased agility for smaller, less complex projects. In its full realization, this framework combines extensive project planning and up-front requirements with iterative delivery – an increasingly popular approach today for enterprise projects. In scaling back toward agile, the framework carefully accounts for system, environment, and team characteristics. Further, the model emphasizes issues frequently underemphasized by agile approaches, including the use of external software such as commercial-off-the-shelf (COTS), Software- as-a-Service (SaaS), and open source products and components; the need for business-oriented project planning and justification; and support for change management to ensure successful system adoption. The framework thereby flexibly accommodates the full range of activities that software projects must support to be successful

Ontology-based patterns for the integration of business processes and enterprise application architectures

Increasingly, enterprises are using Service-Oriented Architecture (SOA) as an approach to Enterprise Application Integration (EAI). SOA has the potential to bridge the gap between business and technology and to improve the reuse of existing applications and the interoperability with new ones. In addition to service architecture descriptions, architecture abstractions like patterns and styles capture design knowledge and allow the reuse of successfully applied designs, thus improving the quality of software. Knowledge gained from integration projects can be captured to build a repository of semantically enriched, experience-based solutions. Business patterns identify the interaction and structure between users, business processes, and data. Specific integration and composition patterns at a more technical level address enterprise application integration and capture reliable architecture solutions. We use an ontology-based approach to capture architecture and process patterns. Ontology techniques for pattern definition, extension and composition are developed and their applicability in business process-driven application integration is demonstrated

Modelling electronic service systems using UML

This paper presents a profile for modelling systems of electronic services using UML. Electronic services encapsulate business services, an organisational unit focused on delivering benefit to a consumer, to enhance communication, coordination and information management. Our profile is based on a formal, workflow-oriented description of electronic services that is abstracted from particular implementation technologies. Resulting models provide the basis for a formal analysis to verify behavioural properties of services. The models can also relate services to management components, including workflow managers and Electronic Service Management Systems (ESMSs), a novel concept drawn from experience of HP Service Composer and DySCo (Dynamic Service Composer), providing the starting point for integration and implementation tasks. Their UML basis and platform-independent nature is consistent with a Model-Driven Architecture (MDA) development strategy, appropriate to the challenge of developing electronic service systems using heterogeneous technology, and incorporating legacy systems