Explore chapters and articles related to this topic
Requirements Specification and Agile Methodologies
Published in Phillip A. Laplante, Mohamad H. Kassab, Requirements Engineering for Software and Systems, 2022
Phillip A. Laplante, Mohamad H. Kassab
Kanban teams write the work items onto cards, usually one item per card. The cards are placed on the board, which is typically divided into columns, that show each flow of the software production (e.g., In Progress, In Testing, Completed, etc.). As the development evolves, the cards contained on the board are moved to the proper column that represents its status, and when a new task comes into play, a new “card” is created. Work moves around the board as capacity permits, rather than being pushed into the process when requested.
COBACABANA: a real industrial application in a job shop system
Published in Production Planning & Control, 2022
Marcello Braglia, Leonardo Marrazzini, Luca Padellini
WLC stabilises the shop floor workload using order release control to decouple the shop floor from a pre-shop pool of orders (Stevenson, Hendry and Kingsman 2005). Orders are released from the pool onto the shop floor in time to meet their due dates while keeping the shop floor workload balanced. To limit the Work-In-Process (WIP), COBACABANA retains work orders in the pre-shop pool. The orders in the pool are sorted in accordance with company priorities (i.e. Operation due date (ODD), First In First Out (FIFO), etc.) and released according to the workload of the workstations (Sweeney, Sweeney, and Campbell 2019). As shown in Figure 1, to monitor the workload on the workstations, COBACABANA establishes a loop of cards between a central planner and each station on the shop floor. Each card represents an operation to be carried out at a workstation.
The Behavior Change Design Cards: A Design Support Tool for Theoretically-Grounded Design of Behavior Change Technologies
Published in International Journal of Human–Computer Interaction, 2022
Chrysanthi Konstanti, Evangelos Karapanos, Panos Markopoulos
Design cards have become a widely adopted design support tool in Interaction Design providing what Rogers (2004) calls knowledge transfer (i.e., the translation of research findings from one discipline into another). It has been argued that design cards provide a number of benefits for the design process: they make the design process visible and less abstract, they communicate knowledge between the members of a group and increase creativity and idea generation, among others (Wölfel & Merritt, 2013). A recent survey by Roy and Warren (2019) examined 155 card sets and argued that they can aid the design process and provide information, methods, or good practice in a handy form. However, they point out the scarcity of empirical evidence for these benefits of cards and invite researchers to provide empirical support for their claims.
An evaluation of three designs to engage users when providing their consent on smartphones
Published in Behaviour & Information Technology, 2021
Daniel Lindegren, Farzaneh Karegar, Bridget Kane, John Sören Pettersson
General layout: At the outset, it is important to develop a hierarchy of information and determine the information to be displayed and at which positions (Cooper, Reimann, and Cronin 2007) because the layout of items is an important aspect to facilitate users' comprehension (Patrick and Kenny 2003). To create a visual hierarchy for users, while presenting clear actions, we used card-based interaction model which is widely utilised in the design of various websites and mobile applications. Aggregation of many individual pieces of content can be presented in the form of cards. Cards are rectangles containing text, images, and functions related to one subject. In our proposed prototypes, cards are used to separate information according to their content: (i) a box presenting information about the identity of the service provider making the request, (ii) a box presenting the mandatory data types with the general purpose of collecting these items, and (iii) a box for the optional data types accompanied with the general purpose of collecting optional information. According to GDPR (The European Parliament and the Council of the European Union 2016), consent should be unambiguous, freely given, specific, and informed. For a consent to be informed, pursuant to Article 13 (1) GDPR, people should at least be made aware of the personal data that will be collected and processed, by whom, and for which purposes. For example, is the information going to be used for targeted advertising or will the service provider use the information to deliver services to the user?