Thesis (Ph. D.)--New York University, School of Education. / Also on microfilm. eContent provider-neutral record in process. Description based on print version record.

Thesis (Ph. D.)--New York University, School of Education. / Also on microfilm. eContent provider-neutral record in process. Description based on print version record.

Thesis (M.S.)--University of Michigan, 1964. / Title from half-title page.

Thesis (M.S.)--University of Wisconsin--Madison, 1990. / Typescript. eContent provider-neutral record in process. Description based on print version record. Includes bibliographical references (leaves 86-93).

Thesis (M.S.)--Boston University

Master of Science / Department of Computing and Information Sciences / Daniel A. Andresen / In COBMIN project, we explore two popular software architectural pattern to implement WHO (World Health Organization) STEPS Instrument for Non-Communication Diseases Risk Factor Surveillance for Nepal. COBMIN web application implements Model-View-Controller(MVC) pattern, which divides the application into three interconnected parts - model, view, and controller. Similarly, COBMIN mobile application utilizes one of the most popular Model-View-ViewModel (MVVM) software architectural pattern which isolates the development of graphical user interface from the business logic and data models. We implement above-mentioned pattern using new .Net Core technologies and a cross-platform mobile development API Xamarin.Forms. The COBMIN project comprises of a web application, a web API, and a mobile application to facilitate community-based management of hypertension in Nepal. The primary purpose of the web application is to manage demographic, behavioral, and physical information of the members of the community who are part of the study group. The mobile application is used to expedite the process of data acquisition from the members. The Web API defines request-response message system for mobile client application employing the central data storage.

Thesis (M.S.)--Boston University / PLEASE NOTE: Boston University Libraries did not receive an Authorization To Manage form for this thesis or dissertation. It is therefore not openly accessible, though it may be available by request. If you are the author or principal advisor of this work and would like to request open access for it, please contact us at open-help@bu.edu. Thank you. / 2031-01-01

Proximity Warning Systems are currently the focus of many research groups. Their goal is to produce a system that will reduce the number of run over incidents that occur in large mobile equipment operations. A majority of these incidents occur when the equipment starts from the In-rest state and begins to move. The addition of a transmission locking mechanism to a GPS based proximity warning system will prevent more run over incidents. This transmission locking mechanism will automatically prevent equipment from moving when there is a high risk for a potential run over incident to occur. Additional safety and optimization for surface equipment can be provided by utilizing GIS software for data analysis just by using the data collected from a GPS based proximity warning system. Combining these ideas and methods can provide better safety for large mobile equipment operations. / Master of Science

No description available.

REpresentational State Transfer or REST is the software architecture style most commonly used for Web Application Programming Interfaces (APIs) and was first defined in 2000 by Roy Thomas Fielding in his PhD dissertation Styles and the Design of Network-based Software Architectures and became a standard for the design of the early World Wide Web and Web-based software. The REST standard continues to be influential in the design of Web systems today, however, it was defined over 15 years ago when the Web was still in its infancy. This paper analyzes REST as it was originally defined by Fielding in 2000 and investigates the validity of its original principles in the modern Internet and Web APIs by sampling a number of prominent APIs and their use of REST. REST definitely has drawbacks for certain types of APIs as evidenced by deviations in the majority of sampled APIs. It is not popular with services that are difficult to represent in REST's resource model. However, REST’s popularity has not noticeably decreased since it was defined rather it has most likely increased. Additionally, each use case that is unsupported by REST goes against some REST constraints that crucial in other areas of it implementation. In conclusion, RESTful properties were not only relevant in the late 1990s and early 2000s but continue to be relevant today as evidenced by its continued widespread use by reputable Web APIs.