8,481 research outputs found
Resource Oriented Modelling: Describing Restful Web Services Using Collaboration Diagrams
The popularity of Resource Oriented and RESTful Web Services is increasing rapidly. In these, resources are key actors in the interfaces, in contrast to other approaches where services, messages or objects are. This distinctive feature necessitates a new approach for modelling RESTful interfaces providing a more intuitive mapping from model to implementation than could be achieved with non-resource methods. With this objective we propose an approach to describe Resource Oriented and RESTful Web Services based on UML collaboration diagrams. Then use it to model scenarios from several problem domains, arguing that Resource Oriented and RESTful Web Services can be used in systems which go beyond ad-hoc integration. Using the scenarios we demonstrate how the approach is useful for: eliciting domain ontologies; identifying recurring patterns; and capturing static and dynamic aspects of the interface
Semantic discovery and reuse of business process patterns
Patterns currently play an important role in modern information systems (IS) development and their use has mainly been restricted to the design and implementation phases of the development lifecycle. Given the increasing significance of business modelling in IS development, patterns have the potential of providing a viable solution for promoting reusability of recurrent generalized models in the very early stages of development. As a statement of research-in-progress this paper focuses on business process patterns and proposes an initial methodological framework for the discovery and reuse of business process patterns within the IS development lifecycle. The framework borrows ideas from the domain engineering literature and proposes the use of semantics to drive both the discovery of patterns as well as their reuse
MOSDEN: An Internet of Things Middleware for Resource Constrained Mobile Devices
The Internet of Things (IoT) is part of Future Internet and will comprise
many billions of Internet Connected Objects (ICO) or `things' where things can
sense, communicate, compute and potentially actuate as well as have
intelligence, multi-modal interfaces, physical/ virtual identities and
attributes. Collecting data from these objects is an important task as it
allows software systems to understand the environment better. Many different
hardware devices may involve in the process of collecting and uploading sensor
data to the cloud where complex processing can occur. Further, we cannot expect
all these objects to be connected to the computers due to technical and
economical reasons. Therefore, we should be able to utilize resource
constrained devices to collect data from these ICOs. On the other hand, it is
critical to process the collected sensor data before sending them to the cloud
to make sure the sustainability of the infrastructure due to energy
constraints. This requires to move the sensor data processing tasks towards the
resource constrained computational devices (e.g. mobile phones). In this paper,
we propose Mobile Sensor Data Processing Engine (MOSDEN), an plug-in-based IoT
middleware for mobile devices, that allows to collect and process sensor data
without programming efforts. Our architecture also supports sensing as a
service model. We present the results of the evaluations that demonstrate its
suitability towards real world deployments. Our proposed middleware is built on
Android platform
An Abstract Formal Basis for Digital Crowds
Crowdsourcing, together with its related approaches, has become very popular
in recent years. All crowdsourcing processes involve the participation of a
digital crowd, a large number of people that access a single Internet platform
or shared service. In this paper we explore the possibility of applying formal
methods, typically used for the verification of software and hardware systems,
in analysing the behaviour of a digital crowd. More precisely, we provide a
formal description language for specifying digital crowds. We represent digital
crowds in which the agents do not directly communicate with each other. We
further show how this specification can provide the basis for sophisticated
formal methods, in particular formal verification.Comment: 32 pages, 4 figure
Attributes of Embodied Leadership: A beginning in the next chapter of leadership development
Research and guidance on leadership behaviour has been documented throughout history, from the epics to more recent leadership theories, evolved over the last century. Why then, when there is so much research and advice available are leaders still making so many errors?
A review of literature in leadership studies reveals that recommendations have often been descriptive, assumptive and prescriptive without considering various differences in individuals. Additionally, leadership development often utilises methodologies in which individuals are trained to ‘act’ as leaders rather than fully embody leadership behaviour. This paper explores the generic attributes that describe embodied leadership behaviour. Semistructured interviews were performed on a panel of individuals from different backgrounds and analysed using a grounded theory approach. Along with the interviews, the works of Scharmer (2008) and behavioural traits identified in leadership by Derue, Nahrgang, Wellman and Humphrey (2011) were also taken into consideration. A final consensus was reached using a set of ten attributes that potentially contribute to embodied leadership behaviour; being non-judgemental, embracing uncertainty, active listening, congruence (morals and ethics), intuition, reflective practice, sense of meaning/purpose, holistic decision making, authentic presence and intention
Checking-in on Network Functions
When programming network functions, changes within a packet tend to have
consequences---side effects which must be accounted for by network programmers
or administrators via arbitrary logic and an innate understanding of
dependencies. Examples of this include updating checksums when a packet's
contents has been modified or adjusting a payload length field of a IPv6 header
if another header is added or updated within a packet. While static-typing
captures interface specifications and how packet contents should behave, it
does not enforce precise invariants around runtime dependencies like the
examples above. Instead, during the design phase of network functions,
programmers should be given an easier way to specify checks up front, all
without having to account for and keep track of these consequences at each and
every step during the development cycle. In keeping with this view, we present
a unique approach for adding and generating both static checks and dynamic
contracts for specifying and checking packet processing operations. We develop
our technique within an existing framework called NetBricks and demonstrate how
our approach simplifies and checks common dependent packet and header
processing logic that other systems take for granted, all without adding much
overhead during development.Comment: ANRW 2019 ~ https://irtf.org/anrw/2019/program.htm
ELICA: An Automated Tool for Dynamic Extraction of Requirements Relevant Information
Requirements elicitation requires extensive knowledge and deep understanding
of the problem domain where the final system will be situated. However, in many
software development projects, analysts are required to elicit the requirements
from an unfamiliar domain, which often causes communication barriers between
analysts and stakeholders. In this paper, we propose a requirements ELICitation
Aid tool (ELICA) to help analysts better understand the target application
domain by dynamic extraction and labeling of requirements-relevant knowledge.
To extract the relevant terms, we leverage the flexibility and power of
Weighted Finite State Transducers (WFSTs) in dynamic modeling of natural
language processing tasks. In addition to the information conveyed through
text, ELICA captures and processes non-linguistic information about the
intention of speakers such as their confidence level, analytical tone, and
emotions. The extracted information is made available to the analysts as a set
of labeled snippets with highlighted relevant terms which can also be exported
as an artifact of the Requirements Engineering (RE) process. The application
and usefulness of ELICA are demonstrated through a case study. This study shows
how pre-existing relevant information about the application domain and the
information captured during an elicitation meeting, such as the conversation
and stakeholders' intentions, can be captured and used to support analysts
achieving their tasks.Comment: 2018 IEEE 26th International Requirements Engineering Conference
Workshop
- …