Creating telecommunication services based on object-oriented frameworks and SDL

This paper describes the tools and techniques being applied in the TINA Open Service Creation Architecture (TOSCA) project to develop object-oriented models of distributed telecommunication services in SDL. The paper also describes the way in which Tree and Tabular Combined Notation (TTCN) test cases are derived from these models and subsequently executed against the CORBA-based implementations of these services through a TTCN/CORBA gateway

DIGITAL CO-CREATION Digitalization within Service Design : Transformation from analog thinking towards digital doing

The German automotive industry has accelerated its digital transformation as OEMs (Original Equipment Manufacturers) moving from car manufacturers towards becoming mobility providers, striving for new mobility solutions like offering Mobility as a Service (MaaS), Electric Vehicles (EVs) and Self-Driving-System (SDS). OEMs focus on expanding their core product-driven businesses to access service-orientated business models, the transformation from ownership towards shared mobility. Considering internal and external factors, this requires a new set of expertise, capabilities and an underlying approach to fulfill the demands in the complexity of human-centered development and front- and backstage alignment within the organization. At the same time, Service Design as a practice has risen in attraction by industry, being recognized and increasingly requested for its integration in the functions and divisions of the organization. The scale of Service Design in influence and impact has reached professional practice, making its way from a trendy buzzword to professional practice of turning complex problems collaboratively into tangible solutions. It is seen as a powerful opportunity for combining Business, Human-Centered Design and Engineering. Service Design establishes new ways of exploring business opportunities towards agile problem-solving but focuses on the ‘doing’ side towards further implementation. The contribution of this industrial-based doctoral thesis shall define how Service Design can be deployed and implemented in the field of organizational transformation and mobility development in the era of digital transformation (Digitalization). This research approach seeks to acquire new knowledge on how the Service Design practice can be applied and executed to be perceived as a practical approach to improve the enterprise’s processes and operating procedures and also provide a strategy to grow Service Design within the organization. This research has followed developing a pilot in a lean start-up approach of build, measure, learn with various business units and brands within the Volkswagen Group, this also implies that this research case study consisted of analyzing the Volkswagen Group needs for Service Design. The ‘10X-Service Design Lab’ (10X-SDL) has been designed as the framework of a combination of modular lab space, facilitation enhanced process, methodological driven tool box, operational model in alignment with a digital workflow and workspace striving for accelerated decision making. It is based on the hypothesis that the proposed framework enhances Service Design practice and, at the same time, it increases its attractiveness for business purposes. The 10X-SDL is designed to accelerate project development in a human-centered and holistic way by an open workspace platform lead by facilitators on which project developers, participants, and stakeholders can digitally co-create products, services, systems, and strategies. This research has been conducted as a case study within the Volkswagen Group from 2015 to 2019 in cooperation with the main partners of Service Innovation Corner (SINCO) of the University of Lapland and visual collaboration software company DEON

A survey of agent-oriented methodologies

This article introduces the current agent-oriented methodologies. It discusses what approaches have been followed (mainly extending existing object oriented and knowledge engineering methodologies), the suitability of these approaches for agent modelling, and some conclusions drawn from the survey

Formalising the Chisel Feature Notation

The CHISEL notation was developed by Bellcore as an informal graphical notation for describing telecomms services and features. CRESS (CHISEL Representation Employing Systematic Specification) is an enhanced version of CHISEL with tightly defined rules for the syntax and static semantics of diagrams. More importantly, CRESS has formal denotations given by SDL (Specification and Description Language) and LOTOS (Language Of Temporal Ordering Specification). This permits rigorous checking, analysis and prototyping of descriptions. The accompanying toolset has been written in an open and extensible manner

Contribution to Software Development Method based on Generalized Requirement Approach

Requirements’ gathering is one of the first steps in the software development process. Gathering business requirements, when the final product requirements are dictated by a known client, can be a difficult process. Even if the client knows their own business best, often their idea about a new business product is obscure, and described by general terms that contribute very much to common misunderstandings among the participants. Business requirement verification when the requirements are gathered using text and graphics can be a slow, error-prone, and expensive process. Misunderstandings and omitted requirements cause the need for revisions and increase project costs and delays. This research work proposes a new approach to the business software development process and is focused on the client’s understanding of how the business software development process works as well as a demonstration of the business requirement practices during requirement negotiation process. While the current software development process validates the business requirement at the end of the development process, this method implementation enables business requirement validation during the requirement negotiation phase. The process of the business requirement negotiation is guided by a set of predefined questions. These questions are guidelines for specifying a sufficient level of requirement details for generating executable code that is able to demonstrate each requirement. Effective implementation of the proposed method requires employment of the GRA Framework. Besides providing guidelines for requirement specification, the Framework shall create executable and provide the test environment for a requirement demonstration. This dissertation implements an example framework that is built around a central repository. Stored within the repository is the data collected during the requirement negotiations process. Access to the repository is managed by a Web interface that enables a collaborative and paperless environment. The result is that the data is stored in one place and updates are reflected to the stakeholders immediately. The executable code is generated by the Generator, a module that provides general programming units that are able to create source code files, databases, SQL statements, classes and methods, navigation menus, and demo applications, all from the data stored in the data repository. The generated software can then be used for the business requirement demonstration. This method assumes that any further development process is built around the requirements repository, which can provide continuous tracking of implementation changes. Besides readily documenting, tracking, and validating the requirements, this method addresses multiple requirement management syndromes such as the insufficient requirements description details provision, the IKIWISI (“I’ll know it when I see it”) Syndrome, the Yes, But Syndrome (“That is not exactly what I mean”), and the Undiscovered Ruins Syndrome (“Now that I see it, I have another requirement to add”).

Spacecraft Avionics Software Development Then and Now: Different but the Same

NASA has always been in the business of balancing new technologies and techniques to achieve human space travel objectives. NASA s historic Software Production Facility (SPF) was developed to serve complex avionics software solutions during an era dominated by mainframes, tape drives, and lower level programming languages. These systems have proven themselves resilient enough to serve the Shuttle Orbiter Avionics life cycle for decades. The SPF and its predecessor the Software Development Lab (SDL) at NASA s Johnson Space Center (JSC) hosted flight software (FSW) engineering, development, simulation, and test. It was active from the beginning of Shuttle Orbiter development in 1972 through the end of the shuttle program in the summer of 2011 almost 40 years. NASA s Kedalion engineering analysis lab is on the forefront of validating and using many contemporary avionics HW/SW development and integration techniques, which represent new paradigms to NASA s heritage culture in avionics software engineering. Kedalion has validated many of the Orion project s HW/SW engineering techniques borrowed from the adjacent commercial aircraft avionics environment, inserting new techniques and skills into the Multi-Purpose Crew Vehicle (MPCV) Orion program. Using contemporary agile techniques, COTS products, early rapid prototyping, in-house expertise and tools, and customer collaboration, NASA has adopted a cost effective paradigm that is currently serving Orion effectively. This paper will explore and contrast differences in technology employed over the years of NASA s space program, due largely to technological advances in hardware and software systems, while acknowledging that the basic software engineering and integration paradigms share many similarities

Developing human-centred framework and guidelines for disc golf application design

Abstract. Disc golf is an increasingly popular sport, especially in Finland and the USA. The disc golf industry and Professional Disc Golf Association have proceeded in the digital transformation; therefore, disc golf applications have penetrated the markets. There is a need for evaluating and developing the current quality of disc golf application design and looking for general guidelines for designing comprehensive applications. This thesis aims to study what kind of framework is hidden behind the disc golf application design from a human-centred perspective when also several stakeholders are concerned. The study is based on theoretical and empirical research. Theoretical research is conducted by literary review of existing disc golf application design guidelines, together with human-centred design, user-centred design, and stakeholder-centred design theory and methodologies in general. Nevertheless, a research gap is found as far as disc golf, golf, and sports application design are concerned. Thus, the review expands to study field practitioners and mobile health context. The literary review also examines disc golf as a sport and in numbers, together with current disc golf applications. Empirical research adapts human-centred design methods by studying users’ expectations, needs, and wishes in the mean of questionnaires, and interviews. Also, the context of use is identified and visited, user requirements are mapped, disc golf personas are created, and the disc golf application’s stakeholders are identified. Then, the method adapted from service-dominant logic is used for preparing value proposals for all disc golf application users, and other stakeholders. By adapting the design guidelines from the literature and empirical findings, the human-centred guidelines for disc golf application design (HGDG) framework is presented as the first main finding of the thesis. The HGDG framework can be used for disc golf application design and ensuring the usage of the human-centred approach. The second main finding, 15 design guidelines and instructions for disc golf application design reinforces the HGDG framework. The third main finding suggests using 15 design guidelines as a metric for evaluating if the designed application achieves an ideal win-win-…-win situation between of application provider, users, and other stakeholders