• Refine Query
  • Source
  • Publication year
  • to
  • Language
  • 4
  • 1
  • 1
  • Tagged with
  • 5
  • 4
  • 3
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • About
  • The Global ETD Search service is a free service for researchers to find electronic theses and dissertations. This service is provided by the Networked Digital Library of Theses and Dissertations.
    Our metadata is collected from universities around the world. If you manage a university/consortium/country archive and want to be added, details can be found on the NDLTD website.
1

CTO生產模式之研究~以我國筆記型電腦為例

張勇毅 Unknown Date (has links)
筆記型電腦由於本身產品的生命週期短,技術淘汰率高、製程組裝不易、市場反應快速、原料價值變動大以及競爭性高的特性,客製化生產CTO (Configure To Order)生產模式成為筆記型電腦廠商的核心競爭能力,關係著未來的競爭優勢,因此我國各大筆記型電腦生產廠商莫不積極開發建立CTO生產模式。   研究者作為國內電子業廠商推動CTO工作的實務工作者,以1999年突破接單內兩天生產挑戰的個案公司為個案,在遵守商業倫理的必要限制下,以個人實際開創CTO生產流程之實務經驗敘述為主,撰寫研究報告,探討筆記型電腦產業CTO的生產流程作業,分析關鍵因素,據以提出生產管理與控制CTO的運作模式與建議,提供相關產業參考。   本研究主要研究目的分述如下:    一、CTO生產模式之意義、功能與限制。    二、探究CTO生產模式各流程之主要內涵。    三、就個案公司實例分析CTO生產模式之關鍵因素。    四、就個案公司之經驗,探討CTO生產模式台灣經驗移植至大陸的可行性與限制,提供建議與我國資訊產業實施參考。   討論部分,研究者針對政府ABCDE計畫對CTO生產模式的影響、OEM大廠對BTO/CTO的要求、CTO生產模式的構建成本與其所帶來附加價值以及CTO生產模式的應用範圍與移植大陸的可行性,做了詳盡的論述。最後研究者分別針對相關產業以及後續研究者提出建議,以供參考。 / Notebook computer is a short life, high technology, difficult assembly, fast marketing change, fluctuated material pricing and highly competed product. CTO (Configure To Order) manufacturing capability becomes Notebook PC manufacturers' core competence. All Taiwan Notebook PC manufacturers aggressively make a lot of efforts to build up CTO process capability.   The researcher has CTO process establishment experience. The established CTO process has achieved 2 days delivery after receipt of the orders. The researcher is willing to share his CTO process experience with public under business morality constraint. The analysis includes CTO process flow, the key success elements, CTO operation model and production control for associated industry's reference.   The purpose for this search is as follows:    1). The meaning, function and limitation of CTO process.    2). CTO process flow content    3). CTO process key success elements    4). The feasibility and constraint to transfer CTO process to China   With regard to the discussion that covers several areas: 1) How did government “ABCDE” project affect CTO process? 2) Major OEM customers' such as Compaq & Dell requirement in terms of BTO/CTO process, 3) The cost to build up CTO process and the added value CTO process may generate, 4) The suitable products to use CTO process and the feasibility to transfer CTO process to China. At last, the researcher made some suggestion to the associated industry and the follow-up researchers.
2

Fault-tolerant Mating Process of Electric Connectors in Robotic Wiring Harness Assembly Systems

Huang, Jian, Di, Pei, Fukuda, Toshio, 福田, 敏男, Matsuno, Takayuki 06 1900 (has links)
No description available.
3

Availability Management In Configure-to-order Manufacturing Systems

Yontem, Huseyin Erdem 01 December 2009 (has links) (PDF)
AVAILABILITY MANAGEMENT IN CONFIGURE-TO-ORDER MANUFACTURING SYSTEMS Y&ouml / ntem, H&uuml / seyin Erdem M.Sc., Operational Research Supervisor: Asst. Prof. Dr. Sedef Meral December 2009, 98 pages In resource constrained supply chains, where demand is higher than the supply, the decision whether to accept or reject the customer order is a very critical task from resource planning and customer service level perspectives. Since the customers, in today&lsquo / s e-business environment, expect quick responses to their orders, some in-advance work has to be done before the arrival of actual customer orders, especially in configure-to-order (CTO) and make-to-order (MTO) production systems. Available-to-Promise (ATP) is a business function that is becoming the central management system for today&lsquo / s dynamic supply chains whose responsibility is to respond customer orders by considering the trade-off between front-end customer satisfaction and back-end capacity allocation. In this study, we propose an availability management approach that introduces push-based allocation planning by using order segmentation before the arrival of actual customer orders in CTO production environments. Moreover, a two-step order promising framework is introduced in order to increase customer service levels through giving certain or v tentative delivery dates immediately to customer orders before the batch, rule-based actual resource consumption processes. The proposed approach is applied to the real-life processes of an enterprise in order to analyze its applicability and evaluate the benefits that accrue. The results of the experiments prove that, the four-phased availability management approach contribute to both overall profit and customer service levels.
4

Web applications using the Google Web Toolkit / Webanwendungen unter Verwendung des Google Web Toolkits

von Wenckstern, Michael 04 June 2013 (has links) (PDF)
This diploma thesis describes how to create or convert traditional Java programs to desktop-like rich internet applications with the Google Web Toolkit. The Google Web Toolkit is an open source development environment, which translates Java code to browser and device independent HTML and JavaScript. Most of the GWT framework parts, including the Java to JavaScript compiler as well as important security issues of websites will be introduced. The famous Agricola board game will be implemented in the Model-View-Presenter pattern to show that complex user interfaces can be created with the Google Web Toolkit. The Google Web Toolkit framework will be compared with the JavaServer Faces one to find out which toolkit is the right one for the next web project. / Diese Diplomarbeit beschreibt die Erzeugung desktopähnlicher Anwendungen mit dem Google Web Toolkit und die Umwandlung klassischer Java-Programme in diese. Das Google Web Toolkit ist eine Open-Source-Entwicklungsumgebung, die Java-Code in browserunabhängiges als auch in geräteübergreifendes HTML und JavaScript übersetzt. Vorgestellt wird der Großteil des GWT Frameworks inklusive des Java zu JavaScript-Compilers sowie wichtige Sicherheitsaspekte von Internetseiten. Um zu zeigen, dass auch komplizierte graphische Oberflächen mit dem Google Web Toolkit erzeugt werden können, wird das bekannte Brettspiel Agricola mittels Model-View-Presenter Designmuster implementiert. Zur Ermittlung der richtigen Technologie für das nächste Webprojekt findet ein Vergleich zwischen dem Google Web Toolkit und JavaServer Faces statt.
5

Web applications using the Google Web Toolkit

von Wenckstern, Michael 05 June 2013 (has links)
This diploma thesis describes how to create or convert traditional Java programs to desktop-like rich internet applications with the Google Web Toolkit. The Google Web Toolkit is an open source development environment, which translates Java code to browser and device independent HTML and JavaScript. Most of the GWT framework parts, including the Java to JavaScript compiler as well as important security issues of websites will be introduced. The famous Agricola board game will be implemented in the Model-View-Presenter pattern to show that complex user interfaces can be created with the Google Web Toolkit. The Google Web Toolkit framework will be compared with the JavaServer Faces one to find out which toolkit is the right one for the next web project.:I Abstract II Contents III Acronyms and Glossary III.I Acronyms III.II Glossary IV Credits 1 Introduction 2 Basics 2.1 Development of the World Wide Web 2.2 Hypertext Markup Language 2.3 Cascading Style Sheets 2.4 JavaScript 2.5 Hypertext Markup Language Document Object Model 2.6 Asynchronous JavaScript and XML 3 GWT toolbox and compiler 3.1 GWT in action 3.2 A short overview of the toolkit 3.3 GWT compiler and JSNI 3.3.1 Overview of GWT compiler and JSNI 3.3.2 Deferred binding and bootstrapping process 3.3.3 GWT compiler steps and optimizations 3.4 Java Runtime Environment Emulation 3.5 Widgets and Panels 3.5.1 Overview of GWT Widgets 3.5.2 Event handlers in GWT Widgets 3.5.3 Manipulating browser’s DOM with GWT DOM class 3.5.4 GWT Designer and view optimization using UiBinder 3.6 Remote Procedure Calls 3.6.1 Comparison of Remote Procedure Calls with Remote Method Invocations 3.6.2 GWT’s RPC service and serializable whitelist 3.7 History Management 3.8 Client Bundle 3.8.1 Using ImageResources in the ClientBundle interface 3.8.2 Using CssResources in the ClientBundle interface 4 Model-View-Presenter Architecture 4.1 Comparison of MVP and MVC 4.2 GWT Model-View-Presenter pattern example: Agricola board game 4.3 Extending the Agricola web application with mobile views 4.4 Introducing activities in the Agricola Model-View-Presenter pattern enabling browser history 5 Comparison of the two web frameworks: GWT and JSF 5.1 Definitions of comparison fields 5.2 Comparison in category 1: Nearly completely static sites with a little bit of dynamic content, e.g. news update 5.3 Comparison in category 2: Doing a survey in both technologies 5.4 Comparison in category 3: Creating a forum to show data 5.5 Comparison in category 4: Writing a chat application 5.6 Comparison in category 5: Writing the speed game Snake 5.7 Summary 6 Security 6.1 Download Tomcat 6.2 Dynamic Web Application Project with GWT and Tomcat 6.3 Establish HTTPS connections in Tomcat 6.3.1 Create a pem certificate 6.3.2 Convert pem certificate into a key store object 6.3.3 Configure Tomcat’s XML files to enable HTPPS 6.4 Establish a database connection in Tomcat 6.4.1 Create TomcatGWT user and schema, and add the table countries 6.4.2 Configure Tomcat’s XML files to get access to the database connection 6.4.3 PreparedStatements avoid MySQL injections 6.5 Login mechanism in Tomcat 6.6 SafeHtml 7 Presenting a complex software application written in GWT 8 Conclusions 8.1 Summary 8.2 Future work A Appendix A 1 Configure the Google Web Toolkit framework in Eclipse A 1.1 Install the Java Developer Kit A 1.2 Download Eclipse A 1.3 Install the GWT plugin in Eclipse A 1.4 Create first GWT Java Project A 2 Figures A 3 Listings A 3.1 Source code of the Agricola board game A 3.2 Source code of GWT and JSF comparison A 4 Tables R Lists and References R 1 Lists R 1.1 List of Tables R 1.2 List of Figures R 1.3 List of Listings R 2 References R 2.1 Books R 2.2 Online resources / Diese Diplomarbeit beschreibt die Erzeugung desktopähnlicher Anwendungen mit dem Google Web Toolkit und die Umwandlung klassischer Java-Programme in diese. Das Google Web Toolkit ist eine Open-Source-Entwicklungsumgebung, die Java-Code in browserunabhängiges als auch in geräteübergreifendes HTML und JavaScript übersetzt. Vorgestellt wird der Großteil des GWT Frameworks inklusive des Java zu JavaScript-Compilers sowie wichtige Sicherheitsaspekte von Internetseiten. Um zu zeigen, dass auch komplizierte graphische Oberflächen mit dem Google Web Toolkit erzeugt werden können, wird das bekannte Brettspiel Agricola mittels Model-View-Presenter Designmuster implementiert. Zur Ermittlung der richtigen Technologie für das nächste Webprojekt findet ein Vergleich zwischen dem Google Web Toolkit und JavaServer Faces statt.:I Abstract II Contents III Acronyms and Glossary III.I Acronyms III.II Glossary IV Credits 1 Introduction 2 Basics 2.1 Development of the World Wide Web 2.2 Hypertext Markup Language 2.3 Cascading Style Sheets 2.4 JavaScript 2.5 Hypertext Markup Language Document Object Model 2.6 Asynchronous JavaScript and XML 3 GWT toolbox and compiler 3.1 GWT in action 3.2 A short overview of the toolkit 3.3 GWT compiler and JSNI 3.3.1 Overview of GWT compiler and JSNI 3.3.2 Deferred binding and bootstrapping process 3.3.3 GWT compiler steps and optimizations 3.4 Java Runtime Environment Emulation 3.5 Widgets and Panels 3.5.1 Overview of GWT Widgets 3.5.2 Event handlers in GWT Widgets 3.5.3 Manipulating browser’s DOM with GWT DOM class 3.5.4 GWT Designer and view optimization using UiBinder 3.6 Remote Procedure Calls 3.6.1 Comparison of Remote Procedure Calls with Remote Method Invocations 3.6.2 GWT’s RPC service and serializable whitelist 3.7 History Management 3.8 Client Bundle 3.8.1 Using ImageResources in the ClientBundle interface 3.8.2 Using CssResources in the ClientBundle interface 4 Model-View-Presenter Architecture 4.1 Comparison of MVP and MVC 4.2 GWT Model-View-Presenter pattern example: Agricola board game 4.3 Extending the Agricola web application with mobile views 4.4 Introducing activities in the Agricola Model-View-Presenter pattern enabling browser history 5 Comparison of the two web frameworks: GWT and JSF 5.1 Definitions of comparison fields 5.2 Comparison in category 1: Nearly completely static sites with a little bit of dynamic content, e.g. news update 5.3 Comparison in category 2: Doing a survey in both technologies 5.4 Comparison in category 3: Creating a forum to show data 5.5 Comparison in category 4: Writing a chat application 5.6 Comparison in category 5: Writing the speed game Snake 5.7 Summary 6 Security 6.1 Download Tomcat 6.2 Dynamic Web Application Project with GWT and Tomcat 6.3 Establish HTTPS connections in Tomcat 6.3.1 Create a pem certificate 6.3.2 Convert pem certificate into a key store object 6.3.3 Configure Tomcat’s XML files to enable HTPPS 6.4 Establish a database connection in Tomcat 6.4.1 Create TomcatGWT user and schema, and add the table countries 6.4.2 Configure Tomcat’s XML files to get access to the database connection 6.4.3 PreparedStatements avoid MySQL injections 6.5 Login mechanism in Tomcat 6.6 SafeHtml 7 Presenting a complex software application written in GWT 8 Conclusions 8.1 Summary 8.2 Future work A Appendix A 1 Configure the Google Web Toolkit framework in Eclipse A 1.1 Install the Java Developer Kit A 1.2 Download Eclipse A 1.3 Install the GWT plugin in Eclipse A 1.4 Create first GWT Java Project A 2 Figures A 3 Listings A 3.1 Source code of the Agricola board game A 3.2 Source code of GWT and JSF comparison A 4 Tables R Lists and References R 1 Lists R 1.1 List of Tables R 1.2 List of Figures R 1.3 List of Listings R 2 References R 2.1 Books R 2.2 Online resources

Page generated in 0.3052 seconds