Lessons learned in the application of formal methods to the design of a storm surge barrier control system

The Maeslantkering is a key flood defense infrastructural system in the Netherlands. This movable barrier protects the city and harbor of Rotterdam, without impacting ship traffic under normal circumstances. Its control system, which operates completely autonomously, must be guaranteed to work correctly even under extreme weather conditions, although it closes only sporadically. During its development in the 1990's, the formal methods Z and Spin were used to increase reliability. As the availability of industrial expert knowledge on these formal methods declines, maintaining the specifications defined back then has become cumbersome. In the quest for an alternative mathematically rigorous approach, this paper reports on an experience in applying supervisory control synthesis. This formal method was recently applied successfully to other types of infrastructural systems like waterway locks, bridges, and tunnels, with the purpose to ensure safe behavior by coordinating hardware components. Here, we show that it can also be used to coordinate several (controller) software systems. Additionally, we compare the lessons learned from the originally used formal methods and link Z to supervisory control synthesis

The Knowledge Application and Utilization Framework Applied to Defense COTS: A Research Synthesis for Outsourced Innovation

Purpose -- Militaries of developing nations face increasing budget pressures, high operations tempo, a blitzing pace of technology, and adversaries that often meet or beat government capabilities using commercial off-the-shelf (COTS) technologies. The adoption of COTS products into defense acquisitions has been offered to help meet these challenges by essentially outsourcing new product development and innovation. This research summarizes extant research to develop a framework for managing the innovative and knowledge flows. Design/Methodology/Approach – A literature review of 62 sources was conducted with the objectives of identifying antecedents (barriers and facilitators) and consequences of COTS adoption. Findings – The DoD COTS literature predominantly consists of industry case studies, and there’s a strong need for further academically rigorous study. Extant rigorous research implicates the importance of the role of knowledge management to government innovative thinking that relies heavily on commercial suppliers. Research Limitations/Implications – Extant academically rigorous studies tend to depend on measures derived from work in information systems research, relying on user satisfaction as the outcome. Our findings indicate that user satisfaction has no relationship to COTS success; technically complex governmental purchases may be too distant from users or may have socio-economic goals that supersede user satisfaction. The knowledge acquisition and utilization framework worked well to explain the innovative process in COTS. Practical Implications – Where past research in the commercial context found technological knowledge to outweigh market knowledge in terms of importance, our research found the opposite. Managers either in government or marketing to government should be aware of the importance of market knowledge for defense COTS innovation, especially for commercial companies that work as system integrators. Originality/Value – From the literature emerged a framework of COTS product usage and a scale to measure COTS product appropriateness that should help to guide COTS product adoption decisions and to help manage COTS product implementations ex post

Bridging the gap between research and agile practice: an evolutionary model

There is wide acceptance in the software engineering field that industry and research can gain significantly from each other and there have been several initiatives to encourage collaboration between the two. However there are some often-quoted challenges in this kind of collaboration. For example, that the timescales of research and practice are incompatible, that research is not seen as relevant for practice, and that research demands a different kind of rigour than practice supports. These are complex challenges that are not always easy to overcome. Since the beginning of 2013 we have been using an approach designed to address some of these challenges and to bridge the gap between research and practice, specifically in the agile software development arena. So far we have collaborated successfully with three partners and have investigated three practitioner-driven challenges with agile. The model of collaboration that we adopted has evolved with the lessons learned in the first two collaborations and been modified for the third. In this paper we introduce the collaboration model, discuss how it addresses the collaboration challenges between research and practice and how it has evolved, and describe the lessons learned from our experience

Bridging the Gap

School districts across the country are increasingly seeking out digital tools to support the work of educators, in the hopes of improving students' academic achievement. With the rapid emergence of this new market, many districts have been challenged by the task of identifying and procuring educational technology (ed-tech) products that match the needs of their educators and students.The NYC Department of Education's "Innovate NYC Schools" division, supported by a U.S. DOE Investing in Innovation (i3) grant, aims to address this problem, in part by promoting "user-centered design," an approach that puts the needs and preferences of products' intended users (in this case, teachers, students, and parents) front and center in the development and procurement of new technology.Bridging the Gap describes the design and implementation of three Innovate NYC Schools initiatives grounded in user-centered design theory:School Choice Design Challenge (SCDC),an effort to develop apps that would help students explore and narrow down their choices of high school.#SharkTankEDU events, during which ed-tech developers present a product to a panel of educators who provide feedback on the tool.Short-Cycle Evaluation Challenges (SCEC), a classroom-based, semester-long pilot of ed-tech tools intended to inform product development, as well as the ultimate procurement decisions of school staff.The report focuses on four phases of work involved in bringing ed-tech companies and the users of their products together: defining a problem; selecting users and ed-tech companies; implementing pilot-based initiatives; and evaluating products. It describes strategies used and challenges faced, and offers practical lessons gleaned from the experiences of the individuals who designed and participated in these efforts.

Beyond the Numbers: Data Use for Continuous Improvement of Programs Serving Disconnected Youth

The American Youth Policy Forum (AYPF) conducted a series of in-depth case studies to examine how three programs which serve a disconnected youth population are utilizing data as a tool for continuous program improvement and ongoing accountability. The resulting publication, Beyond the Numbers: Data Use for Continuous Improvement of Programs Serving Disconnected Youth, describes data collection and use at three successful programs, and distills the key lessons learned and issues to consider both for practitioners and policymakers aiming to improve outcomes for the disconnected youth population

Using the Internet of Things to Teach Good Software Engineering Practice to High School Students

This paper describes a course to introduce high school students to software engineering in practice using the Internet Of Things (IoT). IoT devices allow students to get quick, visible results without watering down technical aspects of programming and networking. The course has three broad goals: (1) to make software engineering fun and applicable, with the aim of recruiting traditionally underrepresented groups into computing; (2) to make young students begin to approach problems with a design mindset; and (3) to show students that computer science, generally, and software engineering, specifically, is about much more than programming. The course unfolds in three segments. The first is a whirlwind introduction to a subset of IoT technologies. Students complete a specific task (or set of tasks) using each technology. This segment culminates in a “do-it-yourself” project, in which the students implement a simple IoT application using their basic knowledge of the technologies. The course’s second segment introduces software engineering practices, again primarily via hands-on practical tutorials. In the third segment of the course, the students conceive of, design, and implement a project that uses the technologies introduced in the first segment, all while being attentive to the good software engineering practices acquired in the second segment. In addition to presenting the course curriculum, the paper also discusses a first offering of the course in a threeweek summer intensive program in 2017, including assessments done to evaluate the curriculum.Cockrell School of Engineerin

Investing In Results: How Business Roundtable Is Supporting Proven Education Reforms

The CEO effort to expand on what's working started in 2013 when Business Roundtable launched its Education Philanthropy Initiative. Two years later, this report examines how the five programs selected for their outstanding work in K-12 education reform have reached more students and improved educational outcomes as a result of the more than $15 million contributed to the Initiative by Roundtable CEOs