Catalogue Search | MBRL
Are you sure you want to remove the book from the shelf?
{{itemTitle}}
290,101
result(s) for
"Software design"
Sort by:
A Taxonomy of Factors Influencing Perceived Safety in Human–Robot Interaction
Safety is a fundamental prerequisite that must be addressed before any interaction of robots with humans. Safety has been generally understood and studied as the physical safety of robots in human–robot interaction, whereas how humans perceive these robots has received less attention. Physical safety is a necessary condition for safe human–robot interaction. However, it is not a sufficient condition. A robot that is safe by hardware and software design can still be perceived as unsafe. This article focuses on perceived safety in human–robot interaction. We identified six factors that are closely related to perceived safety based on the literature and the insights obtained from our user studies. The identified factors are the context of robot use, comfort, experience and familiarity with robots, trust, the sense of control over the interaction, and transparent and predictable robot actions. We then made a literature review to identify the robot-related factors that influence perceived safety. Based the literature, we propose a taxonomy which includes human-related and robot-related factors. These factors can help researchers to quantify perceived safety of humans during their interactions with robots. The quantification of perceived safety can yield computational models that would allow mitigating psychological harm.
Journal Article
Strategic writing for UX : drive engagement, conversion, and retention with every word
When you depend on users to perform specific actions, like buying tickets, playing a game, or riding public transit, sell-placed words are most effective. But how do you choose the right words? And how do you know if they work? With this practical book, you'll learn how to write strategically for UX, using tools to build foundational pieces for UI text and UX voice strategy. UX content strategist Torrey Podmajersky provides strategies for converting, engaging, supporting, and re-attracting users. You'll use frameworks and patterns for content, methods to measure the content's effectiveness, and processes to create the collaboration necessary for success. You'll also structure your voice throughout so that the brand is easily recognizable to its audience.
The environment of cognitive-contextual software design: from concept to implementation
Two main points of the objectives to design software systems (SS) have been considered: achieving proper functioning of the SS with consistent results, and the possibility to obtain reliable assessments of the Software System quality depending on the initial requirements. A cognitive-contextual design strategy has been proposed that can significantly improve the perception of actual elements of the design task by creating a context with selected formalized conditions, and enhance cognitive coherence of the project elements throughout the Software System lifecycle.
Journal Article
Software for people : fundamentals, trends and best practices
\"The highly competitive and globalized software market is creating pressure on software companies. Given the current boundary conditions, it is critical to continuously increase time-to-market and reduce development costs. In parallel, driven by private life experiences with mobile computing devices, the World Wide Web and software-based services, people, general expectations with regards to software are growing. They expect software that is simple and joyful to use. In the light of the changes that have taken place in recent years, software companies need to fundamentally reconsider the way they develop and deliver software to their customers. This book introduces fundamentals, trends and best practices in the software industry from a threefold perspective which equally takes into account design, management, and development of software. It demonstrates how cross-functional integration can be leveraged by software companies to successfully build software for people. Professionals from business and academia give an overview on state-of-the-art knowledge and report on key insights from their real-life experience. They provide guidance and hands-on recommendation on how to create winning products. This combined perspective fosters the transfer of knowledge between research and practice and offers a high practical value for both sides. The book targets both, practitioners and academics looking for successfully building software in the future. It is directed at Managing Directors of software companies, Software Project Managers, Product Managers and Designers, Software Developers as well as academics and students in the area of Software and Information Systems Engineering, Human Computer Interaction (HCI), and Innovation Management\"--Provided by publisher.
Book
A Coordination Approach to Support Crowdsourced Software-Design Process
Crowdsourcing software design (CSD) is the completion of specific software-design tasks on behalf of a client by a large, unspecified group of external individuals who have the specialized knowledge required by an open call. Although current CSD platforms have provided features to improve coordination in the CSD process (such as email notifications, chat, and announcements), these features are insufficient to solve the coordination limitations. A lack of appropriate coordination support in CSD activities may cause delays and missed opportunities for participants, and thus the best quality of design contest results may not be guaranteed. This research aims to support the effective management of the CSD process through identifying the key activity dependencies among participants in CSD platforms and designing a set of process models to provide coordination support through managing this activity. In order to do this, a five-stage approach was used: First, the current CSD process was investigated by reviewing 13 CSD platforms. Second, the review resulted in the identification of 17 possible suggestions to improve CSD. These suggestions were evaluated in stage 3 through distributing a survey to 41 participants who had experience in using platforms in the field of CSD. In stage 4, we designed ten process models that could meet the requirements of suggestions, while in stage 5, we evaluated these process models through interviews with domain experts. The result shows that coordination support in the activities of the CSD can make valuable contributions to the development of CSD platforms.
Journal Article
RAPID: a knowledge-based assistant for designing web APIs
With the rise in initiatives such as software ecosystems and Internet of Things (IoT), developing web Application Programming Interfaces (web APIs) has become an increasingly common practice. One main concern in developing web APIs is that they expose back-end systems and data toward clients. This exposure threatens critical non-functional requirements, such as the security of back-end systems, the performance of provided services, and the privacy of communications with clients. Although dealing with non-functional requirements during software design has been long studied, there is still no framework to specifically assist software developers in addressing these requirements in web APIs. In this paper, we introduce Rational API Designer (RAPID), an open-source assistant that advises on designing non-functional requirements in the architecture of web APIs. We have equipped RAPID with a broad range of expert knowledge about API design, systematically collected and extracted from the literature. The API design knowledge has been encoded as a set of 156 rules using the Non-Functional Requirements (NFR) multi-valued logic, a formal framework commonly used to describe non-functional and functional requirements of software systems. RAPID uses the encoded knowledge in a stepwise inference procedure to arrive from a given requirement, to a set of design alternatives to a final recommendation for a given API design specification. Seven well-experienced software engineers have blindly evaluated the accuracy of RAPID’s consultations over seven different cases of web API design and on providing design guidelines for thirty design questions. The results of the evaluation show that RAPID’s recommendations meet acceptable standards of the majority of the evaluators 73.3% of the time. Moreover, analysis of the evaluators’ comments suggests that more than one-third of the unacceptable ratings (33.8%) given to RAPID’s answers are due to valid but incomplete design guidelines. We thus expect that the accuracy of the consultations will increase as RAPID’s knowledge of API design is extended and refined.
Journal Article
Establishing Representative No-Take Areas in the Great Barrier Reef: Large-Scale Implementation of Theory on Marine Protected Areas
The Great Barrier Reef Marine Park, an area almost the size of Japan, has a new network of no-take areas that significantly improves the protection of biodiversity. The new marine park zoning implements, in a quantitative manner, many of the theoretical design principles discussed in the literature. For example, the new network of no-take areas has at least 20% protection per “bioregion,” minimum levels of protection for all known habitats and special or unique features, and minimum sizes for no-take areas of at least 10 or 20 km across at the smallest diameter. Overall, more than 33% of the Great Barrier Reef Marine Park is now in no-take areas (previously 4.5%). The steps taken leading to this outcome were to clarify to the interested public why the existing level of protection was inadequate; detail the conservation objectives of establishing new no-take areas; work with relevant and independent experts to define, and contribute to, the best scientific process to deliver on the objectives; describe the biodiversity (e.g., map bioregions); define operational principles needed to achieve the objectives; invite community input on all of the above; gather and layer the data gathered in round-table discussions; report the degree of achievement of principles for various options of no-take areas; and determine how to address negative impacts. Some of the key success factors in this case have global relevance and include focusing initial communication on the problem to be addressed; applying the precautionary principle; using independent experts; facilitating input to decision making; conducting extensive and participatory consultation; having an existing marine park that encompassed much of the ecosystem; having legislative power under federal law; developing high-level support; ensuring agency priority and ownership; and being able to address the issue of displaced fishers.
Journal Article