hybrid Design based research for Agile Software development (hDAS) in ISD contexts: a discovery from studying how to design MUVEs for VET

[EN] hDAS methodology in phases determines the tailored hDAS method. Enacting the hDAS method then leads to discoveries for and from method and methodology, which leads to further tailoring of the method. I posit, a class of ADDIE like ISD processes that intrinsically trend towards increasing complexity in their design, in order to meet newly formed theoretic perspectives. Using hDAS addresses an on-going increase in complexity of ISD, through a paradigmatic change, in which the outcome of the design is also the design process adapted to current theoretical understanding and discipline needs. The way forward, as formalised in hDAS, is tailoring of ISD through DBR and Agile software development. In this paper a context for hDAS is presented by reflection on hDAS in ISD that uses: ADDIE, Agile and explicitly tests educational theory. hDAS resolves gaps identified for each of these. By enacting hDAS a tailored ISD method is induced that meets the current theoretic and vocational understanding for the instructional situationCochrane, T. (2020). hybrid Design based research for Agile Software development (hDAS) in ISD contexts: a discovery from studying how to design MUVEs for VET. En 6th International Conference on Higher Education Advances (HEAd'20). Editorial Universitat Politècnica de València. (30-05-2020):875-882. https://doi.org/10.4995/HEAd20.2020.11167OCS87588230-05-202

A Reference Model for Software and System Inspections. White Paper

Software Quality Assurance (SQA) is an important component of the software development process. SQA processes provide assurance that the software products and processes in the project life cycle conform to their specified requirements by planning, enacting, and performing a set of activities to provide adequate confidence that quality is being built into the software. Typical techniques include: (1) Testing (2) Simulation (3) Model checking (4) Symbolic execution (5) Management reviews (6) Technical reviews (7) Inspections (8) Walk-throughs (9) Audits (10) Analysis (complexity analysis, control flow analysis, algorithmic analysis) (11) Formal method Our work over the last few years has resulted in substantial knowledge about SQA techniques, especially the areas of technical reviews and inspections. But can we apply the same QA techniques to the system development process? If yes, what kind of tailoring do we need before applying them in the system engineering context? If not, what types of QA techniques are actually used at system level? And, is there any room for improvement.) After a brief examination of the system engineering literature (especially focused on NASA and DoD guidance) we found that: (1) System and software development process interact with each other at different phases through development life cycle (2) Reviews are emphasized in both system and software development. (Figl.3). For some reviews (e.g. SRR, PDR, CDR), there are both system versions and software versions. (3) Analysis techniques are emphasized (e.g. Fault Tree Analysis, Preliminary Hazard Analysis) and some details are given about how to apply them. (4) Reviews are expected to use the outputs of the analysis techniques. In other words, these particular analyses are usually conducted in preparation for (before) reviews. The goal of our work is to explore the interaction between the Quality Assurance (QA) techniques at the system level and the software level

Teachers enacting a technology-rich curriculum for emergent literacy

PictoPal is the name of a technology-rich curriculum with a focus on emergent literacy of Dutch kindergarteners. A case study design was used to examine teacher technology integration within PictoPal along with their perceptions about teaching/learning, technology and technology-based innovations. Observations were undertaken on pupils’ engagement and teachers’ technology integration within PictoPal. Interviews were used to examine teachers’ perceptions. Pupils’ emergent literacy learning was examined in a nonequivalent control quasi experimental design. Four kindergarten teachers and four classes (N = 95 pupils) participated in the use of PictoPal. The findings suggest that a high extent of technology integration is related to: a developmental approach to teaching/learning; positive attitudes and expectations towards technology-based innovations; and positive perceptions of support in stressful work conditions. Significant learning gains were found for the experimental group using PictoPal. High pupil learning gains were not related to a high extent of technology integration. Senior kindergarteners engaged to a higher extent with PictoPal than junior kindergartener

OperA/ALIVE/OperettA

Comprehensive models for organizations must, on the one hand, be able to specify global goals and requirements but, on the other hand, cannot assume that particular actors will always act according to the needs and expectations of the system design. Concepts as organizational rules (Zambonelli 2002), norms and institutions (Dignum and Dignum 2001; Esteva et al. 2002), and social structures (Parunak and Odell 2002) arise from the idea that the effective engineering of organizations needs high-level, actor-independent concepts and abstractions that explicitly define the organization in which agents live (Zambonelli 2002).Peer ReviewedPostprint (author's final draft

Planning and Scheduling of Business Processes in Run-Time: A Repair Planning Example

Over the last decade, the efficient and flexible management of business processes has become one of the most critical success aspects. Furthermore, there exists a growing interest in the application of Artificial Intelligence Planning and Scheduling techniques to automate the production and execution of models of organization. However, from our point of view, several connections between both disciplines remains to be exploited. The current work presents a proposal for modelling and enacting business processes that involve the selection and order of the activities to be executed (planning), besides the resource allocation (scheduling), considering the optimization of several functions and the reach of some objectives. The main novelty is that all decisions (even the activities selection) are taken in run-time considering the actual parameters of the execution, so the business process is managed in an efficient and flexible way. As an example, a complex and representative problem, the repair planning problem, is managed through the proposed approach.Ministerio de Ciencia e Innovación TIN2009-13714Junta de Andalucía P08-TIC-0409

Sunbeam: A Ray of Hope for Trademark Licensees

In the 1985 decision Lubrizol Enterprises v. Richmond Metal Finishers, the Fourth Circuit established that a licensor’s rejection of an intellectual property license under § 365 of the U.S. Bankruptcy Code terminates the licensee’s right to continue using the license. Concerned about the detrimental effects that Lubrizol would have on technological development in the United States, Congress responded swiftly by enacting the Intellectual Property Licenses in Bankruptcy Act (IPLBA), which exempted certain forms of intellectual property, such as copyrights, patents, and trade secrets, from rejection under § 365 of the Code. Trademarks, however, are notably absent from Congress’s definition of “intellectual property,” causing the trademark licensing community to question the reach of the IPLBA’s protections. Recently, the Seventh Circuit held that a trademark licensee may continue using a licensed trademark following rejection, despite Congress’s omission of trademarks from its listed definition of “intellectual property.” This Note examines the divide between the Fourth and Seventh Circuits, and it contends that careful consideration of existing executory contract doctrine and the IPLBA’s legislative history, as well as the balance of equities, suggests that trademark licensees should retain their rights to continue utilizing licensed trademarks following rejection