The Experts below are selected from a list of 657525 Experts worldwide ranked by ideXlab platform
Tyler Comings - One of the best experts on this subject based on the ideXlab platform.
-
Emergency hand loan : a product Design Case Study
2015Co-Authors: Piyush Tantia, Tyler ComingsAbstract:The poor and other underserved populations in developing countries have unique financial services needs. However, there is often a mismatch between what financial institutions offer and what underserved populations need or want. This product gap may reflect a lack of interest by financial institutions in Designing more target products, or a lack of willingness or capacity on the part of financial institutions to Design, market and implement tailor-made financial products. The objectives of the Product Design Case Studies are to 1) develop expertise related to product Design and innovation processes through a better understanding of best practices in the field, in depth research and application of behavioral economics concepts; 2) increase awareness of product Design/innovation and the links between product development and financial inclusion; and 3) generate publicity and knowledge sharing around product Design and innovation. While the hand loan product was broadly successful in achieving its original intent, the pilot encountered considerable institutional and execution challenges that are instructive for future product innovation efforts. The first two sections describe the problem and the innovative product Designed to address it. The next section describes the final Design and implementation of the product in detail. The fourth section covers post-pilot data collection and results. The final sections discuss lessons learned and planned future enhancements.
-
WING mobile payments : a product Design Case Study
2015Co-Authors: Saugato Datta, Piyush Tantia, Tyler ComingsAbstract:Economists have long known that financial services have benefits for users by allowing them to smooth consumption, save for bulky purchases, etc. But the recognition of their importance even for people with relatively low incomes those earning one to two dollars a day, for instance is relatively recent. This recognition has been spurred by a better understanding of the financial lives of the poor, and of the critical role played by uncertainty and volatility. The objective of this Case Study is to describe the Design and implementation of WING, a Cambodian mobile-phone-based payment system. The product has been successful in providing access to formal banking to the previously unbanked in Cambodia. The following sections present the problem of financial exclusion, how WING meets this problem by providing a mobile banking network, the unique aspects of WINGs Design compared to other products, challenges in achieving technology adoption and other constraints faced by the product, and how WING has responded to these challenges throughout implementation. Finally, the Case Study presents lessons learned and behavioral applications for future products.
-
Commitment savings accounts in Malawi : a product Design Case Study
2015Co-Authors: Piyush Tantia, Tyler ComingsAbstract:Malawis economy is heavily dependent on agriculture, especially tobacco, which comprises a majority of the countrys exports. Tobacco farmers have one harvest a year, and while their income stream occurs over several months it must last them for the entire year, making it difficult to smooth consumption throughout the year. The objective of this Case Study is to present the Design and implementation of a commitment savings product for groups of tobacco farmers in Malawi. The product was successful in encouraging savings, increasing input purchases and yields for the next years harvest, and increasing consumption after the harvest. The following sections describe the lack of formal savings options for rural farmers, the behavioral concept behind commitment savings accounts, the product Designed to address these problems and subsequent changes to the original Design, results of a field experiment evaluating the product, and lessons learned for other commitment savings products.
Jan L. Harrington - One of the best experts on this subject based on the ideXlab platform.
-
Database Design Case Study 3: SmartMart
Relational Database Design and Implementation, 2016Co-Authors: Jan L. HarringtonAbstract:This chapter presents the third of three major Case studies in the book. It presents a large retail environment that includes multiple stores and warehouses. The Design examines additional features of database Design, including reference entities, circular relationships, and mutually-exclusive relationships. It also revisits the issue of true one-to-one relationships.
-
Database Design Case Study #1: Mighty-Mite Motors
Relational Database Design and Implementation, 2016Co-Authors: Jan L. HarringtonAbstract:This chapter presents the first of three major Case studies in the book. The emphasis is on reengineering an existing database system, and includes a discussion of the ways in which an organization may need to change along with the introduction of more up-to-date technology.
-
Database Design Case Study #2: East Coast Aquarium
Relational Database Design and Implementation, 2016Co-Authors: Jan L. HarringtonAbstract:This chapter presents the second of three major Case studies in the book. It presents a database environment for which two distinct databases that do not share data are an appropriate solution. The larger of the two databases include several many-to-many relationships that must be handled by the Design. The Case Study also includes the use of a Case tool to provide a prototype user interface for database applications.
-
Chapter 13 – Database Design Case Study 3: SmartMart
Relational Database Design, 2009Co-Authors: Jan L. HarringtonAbstract:Publisher Summary This chapter explores the database Design of SmartMart. SmartMart is a long established retailer with 325 stores across North America that has expanded into Web sales. SmartMart has three major areas for which it wants to an integrated database—in-store sales, Web sales, and some limited human resources needs. The sales data must be compatible with accounting systems to simplify data transfer. In addition, both the in-store sales and Web sales applications must use the same data about products. The products that SmartMart sells are stocked throughout the company's stores, although every store does not carry every product. The database must therefore include data about the products, stores, departments within stores, products stocked within a specific department, and current sales promotions for a specific product. The store and department data must be integrated with the database's Human Resources data. The data describing in-store sales serve two purposes, accounting and inventory control. Furthermore, the database must distinguish between cash and credit transactions. At the same time, the database does not store customer data about cash transactions, but it must retain credit card numbers, expiration dates, and customer names on credit sales.
-
Database Design Case Study #3: Independent Intelligence Agency
Relational Database Design Clearly Explained, 2002Co-Authors: Jan L. HarringtonAbstract:The final Case Study presents two different challenges: first, the specifications have been written by people who are more concerned with security than they are with helping database Designers; second, the environment contains an enormous number of repeating groups. In addition, this is a large database. Although, at the outset it may appear that there are two or three separate databases, the parts of the database share just enough data that the only way to meet all the organization's requirements is to maintain a single schema. The problems faced by the company are: the file processing system is slow and hard to maintain. The file processing system does not provide enough flexibility for current application program technologies. The distributed file system has led to inconsistencies in the types of data that are stored on the organization's various computers. Probably, the easiest way to approach a database Design where the specifications are presented in this way is to begin to create an ER diagram. When the database is as large as the one mentioned in the chapter, it is also easier to break the Design into several components. Like any relational schema, the object-relational schema for the IIA has difficulty representing a relationship between two entities, whose primary keys are defined over the same domain.
Birgit Vogelheuser - One of the best experts on this subject based on the ideXlab platform.
-
a comparison of inconsistency management approaches using a mechatronic manufacturing system Design Case Study
Conference on Automation Science and Engineering, 2015Co-Authors: Stefan Feldmann, Daniel Kammerl, Konstantin Kernschmidt, Thomas Wolfenstetter, Christiaan J. J. Paredis, Sebastian J. I. Herzig, Helmut Krcmar, Ahsan Qamar, Udo Lindemann, Birgit VogelheuserAbstract:Designing and developing complex mechatronic systems requires the consolidation of models from a variety of domains. These models are created by different stakeholders using a variety of formalisms for the purpose of addressing specific concerns, and are used for representing different views on the same system. While it is considered good practice to separate concerns as much as possible, a complete separation is impossible. The resulting model overlap opens the possibility of inconsistencies being introduced — that is, disagreements between views. Numerous approaches to identify and resolve such inconsistencies have been introduced in the software and systems engineering literature. However, in mechatronic Design practice, these have gained little acceptance. The goal of this paper is two-fold: to investigate why their wide spread use is not common, and to assess which of the approaches is the most promising for multi-disciplinary systems Design. To aid in the investigation, a change scenario is analyzed using the models of a mechatronic manufacturing system as a Case Study.
Piyush Tantia - One of the best experts on this subject based on the ideXlab platform.
-
Emergency hand loan : a product Design Case Study
2015Co-Authors: Piyush Tantia, Tyler ComingsAbstract:The poor and other underserved populations in developing countries have unique financial services needs. However, there is often a mismatch between what financial institutions offer and what underserved populations need or want. This product gap may reflect a lack of interest by financial institutions in Designing more target products, or a lack of willingness or capacity on the part of financial institutions to Design, market and implement tailor-made financial products. The objectives of the Product Design Case Studies are to 1) develop expertise related to product Design and innovation processes through a better understanding of best practices in the field, in depth research and application of behavioral economics concepts; 2) increase awareness of product Design/innovation and the links between product development and financial inclusion; and 3) generate publicity and knowledge sharing around product Design and innovation. While the hand loan product was broadly successful in achieving its original intent, the pilot encountered considerable institutional and execution challenges that are instructive for future product innovation efforts. The first two sections describe the problem and the innovative product Designed to address it. The next section describes the final Design and implementation of the product in detail. The fourth section covers post-pilot data collection and results. The final sections discuss lessons learned and planned future enhancements.
-
WING mobile payments : a product Design Case Study
2015Co-Authors: Saugato Datta, Piyush Tantia, Tyler ComingsAbstract:Economists have long known that financial services have benefits for users by allowing them to smooth consumption, save for bulky purchases, etc. But the recognition of their importance even for people with relatively low incomes those earning one to two dollars a day, for instance is relatively recent. This recognition has been spurred by a better understanding of the financial lives of the poor, and of the critical role played by uncertainty and volatility. The objective of this Case Study is to describe the Design and implementation of WING, a Cambodian mobile-phone-based payment system. The product has been successful in providing access to formal banking to the previously unbanked in Cambodia. The following sections present the problem of financial exclusion, how WING meets this problem by providing a mobile banking network, the unique aspects of WINGs Design compared to other products, challenges in achieving technology adoption and other constraints faced by the product, and how WING has responded to these challenges throughout implementation. Finally, the Case Study presents lessons learned and behavioral applications for future products.
-
Commitment savings accounts in Malawi : a product Design Case Study
2015Co-Authors: Piyush Tantia, Tyler ComingsAbstract:Malawis economy is heavily dependent on agriculture, especially tobacco, which comprises a majority of the countrys exports. Tobacco farmers have one harvest a year, and while their income stream occurs over several months it must last them for the entire year, making it difficult to smooth consumption throughout the year. The objective of this Case Study is to present the Design and implementation of a commitment savings product for groups of tobacco farmers in Malawi. The product was successful in encouraging savings, increasing input purchases and yields for the next years harvest, and increasing consumption after the harvest. The following sections describe the lack of formal savings options for rural farmers, the behavioral concept behind commitment savings accounts, the product Designed to address these problems and subsequent changes to the original Design, results of a field experiment evaluating the product, and lessons learned for other commitment savings products.
Stefan Feldmann - One of the best experts on this subject based on the ideXlab platform.
-
a comparison of inconsistency management approaches using a mechatronic manufacturing system Design Case Study
Conference on Automation Science and Engineering, 2015Co-Authors: Stefan Feldmann, Daniel Kammerl, Konstantin Kernschmidt, Thomas Wolfenstetter, Christiaan J. J. Paredis, Sebastian J. I. Herzig, Helmut Krcmar, Ahsan Qamar, Udo Lindemann, Birgit VogelheuserAbstract:Designing and developing complex mechatronic systems requires the consolidation of models from a variety of domains. These models are created by different stakeholders using a variety of formalisms for the purpose of addressing specific concerns, and are used for representing different views on the same system. While it is considered good practice to separate concerns as much as possible, a complete separation is impossible. The resulting model overlap opens the possibility of inconsistencies being introduced — that is, disagreements between views. Numerous approaches to identify and resolve such inconsistencies have been introduced in the software and systems engineering literature. However, in mechatronic Design practice, these have gained little acceptance. The goal of this paper is two-fold: to investigate why their wide spread use is not common, and to assess which of the approaches is the most promising for multi-disciplinary systems Design. To aid in the investigation, a change scenario is analyzed using the models of a mechatronic manufacturing system as a Case Study.
