DOCSLIB.ORG

Models in the Zend Framework

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Models in the Zend Framework Zend Framework 1.8 Web Application Development Design, develop, and deploy feature-rich PHP web applications with this MVC framework Keith Pope BIRMINGHAM - MUMBAI This material is copyright and is licensed for the sole use by Vadim Kudria on 4th October 2009 6352 108th St, , Forest Hills, , 11375 Zend Framework 1.8 Web Application Development Copyright © 2009 Packt Publishing All rights reserved. No part of this book may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, without the prior written permission of the publisher, except in the case of brief quotations embedded in critical articles or reviews. Every effort has been made in the preparation of this book to ensure the accuracy of the information presented. However, the information contained in this book is sold without warranty, either express or implied. Neither the author, nor Packt Publishing, and its dealers and distributors will be held liable for any damages caused or alleged to be caused directly or indirectly by this book. Packt Publishing has endeavored to provide trademark information about all of the companies and products mentioned in this book by the appropriate use of capitals. However, Packt Publishing cannot guarantee the accuracy of this information. First published: September 2009 Production Reference: 1160909 Published by Packt Publishing Ltd. 32 Lincoln Road Olton Birmingham, B27 6PA, UK. ISBN 978-1-847194-22-0 www.packtpub.com Cover Image by Vinayak Chittar ([email protected]) This material is copyright and is licensed for the sole use by Vadim Kudria on 4th October 2009 6352 108th St, , Forest Hills, , 11375 Credits Author Editorial Team Leader Keith Pope Akshara Aware Reviewers Project Team Leader Wenbert Del Rosario Lata Basantani Md. Mahmud Ahsan Project Coordinator Acquisition Editor Rajashree Hamine Rashmi Phadnis Proofreader Development Editor Lynda Sliwosk Ved Prakash Jha Jeff Orloff Technical Editor Graphics Pallavi Kachare Nilesh Mohite Copy Editor Production Coordinator Leonard D'Silva Shantanu Zagade Indexer Cover Work Hemangini Bari Shantanu Zagade This material is copyright and is licensed for the sole use by Vadim Kudria on 4th October 2009 6352 108th St, , Forest Hills, , 11375 About the Author Keith Pope has over ten years of experience in web-related industries and has had a keen interest in programming from an early age. Keith currently works in the airline industry as a technical project manager, providing entertainment systems for aircraft. He has been working with the Zend Framework since its first preview release, using it in many of his work and personal projects. I would like to thank my wife; without her support and patience, this book would not have been possible. I would also like to thank Matthew Weier O'Phinney who has been instrumental in the success of the Zend Framework project as well as giving lots of time to the mailing lists, answering both mine and others questions. The rest of the Zend team for all their hard work while creating a great framework that I could write about. Rob Allen and Alex Mace for general help and support. The technical reviewers and the team at Packt for their hard work in getting everything together. Derek Au for his bug reports. Big thanks to my family, the Adkins family, Phil Dunsford, Martin Williams, Tom Hoddell, Sally Hoddell, the Allpay team, Francesca Oliveri, Lucy Hughes-Martin, and Rob Whittle; you all supported me in various ways. This material is copyright and is licensed for the sole use by Vadim Kudria on 4th October 2009 6352 108th St, , Forest Hills, , 11375 About the Reviewers Wenbert Del Rosario is from Cebu, Philippines. He started his career as a web developer in college, learning PHP and Adobe Photoshop. He works with open source technologies—Zend Framework, Code Igniter, MySQL, and jQuery are some of the tools he has under his sleeve. He likes to keep it simple and believes that being mindful of best practices in software development can be more effective than adopting every latest technology. In his free time, he loves to work on personal projects using PHP, Javascript, and MySQL. He also does some freelance jobs and consulting from time to time. All in all, he is very passionate about what he does and is a big fan of open source software. Wenbert has worked for Lexmark Research and Development Corporation in Cebu. He develops in-house web-based applications using Apache, PHP, MySQL, and Linux. Some of his web applications are used in different geographc regions (USA, Europe, and Asia Pacific) by Lexmark employees, while other small but significant ones are used locally by Lexmark Cebu employees. I would like to thank my family. My mother, Wenia, who is always very supportive and understanding. My brothers, Andrew, John, and Alberto. And my sister Jonina Mae. To my father, Luis, who passed away a few years ago and to God. This material is copyright and is licensed for the sole use by Vadim Kudria on 4th October 2009 6352 108th St, , Forest Hills, , 11375 Md. Mahmud Ahsan is a freelance consultant currently working as a software engineer in Berkeley-based i2we, inc. Mahmud received a Bachelor's degree in Computer Science and Engineering from the International Islamic University Chittagong, in Bangladesh. He is also a Zend Certified Engineer. He has about four years of experience in the world of PHP. He has extensively worked on small and large scale social networking web applications developed in PHP and Zend Framework. I'm grateful to my parents and Hasin Hayder (author at Packt Publishing). I would also like to thank my wife Jinat Jahan for her consistent support. This material is copyright and is licensed for the sole use by Vadim Kudria on 4th October 2009 6352 108th St, , Forest Hills, , 11375 Table of Contents Preface 1 Chapter 1: Creating a Basic MVC Application 9 Overview of MVC architecture 10 Setting up the environment 10 Installation 11 Creating the project structure 11 Application directory structure 13 Bootstrapping 14 The index file 14 Application configuration 16 The bootstrap file 17 Your first controller 18 The Action Controller 19 Subclassing 19 Initialization 20 Actions 21 The standard router 24 Utility methods 27 Action Helpers 29 Your first view 30 View directories 31 Creating a view 31 View Helpers 35 URL View Helper 35 View customization 37 Handling errors 38 Summary 40 This material is copyright and is licensed for the sole use by Vadim Kudria on 4th October 2009 6352 108th St, , Forest Hills, , 11375 Table of Contents Chapter 2: The Zend Framework MVC Architecture 41 Zend framework MVC overview 41 What is a request 42 Request handling 42 Abstractness of MVC components 45 The Front Controller 45 Design 45 Defaults 46 Using the Front Controller 47 Invocation parameters 47 Options 48 Modules, controllers, and actions 48 MVC component customization 51 Plugins 52 The router 53 Design 54 Defaults 54 Using the router 55 Zend_Controller_Router_Route 56 Zend_Controller_Router_Route_Static 59 Zend_Controller_Router_Route_Regex 59 Zend_Controller_Router_Route_Hostname 63 Zend_Controller_Router_Route_Chain 64 Zend_Config 65 The Dispatcher 67 Design 67 Request dispatching 67 Using the Dispatcher 69 The Request object 70 Design 71 Defaults 71 Using the Request object 71 The HTTP Request object 73 The Response object 75 Design 75 Defaults 76 Using the Response object 76 Summary 80 Chapter 3: Storefront Basic Setup 81 Getting started 81 Software requirements 82 Coding standards 82 The Storefront requirements 82 [ ii ] This material is copyright and is licensed for the sole use by Vadim Kudria on 4th October 2009 6352 108th St, , Forest Hills, , 11375 Table of Contents The Storefront overview 83 Basic structure and setup 83 The directory structure 84 Bootstrapping with Zend_Application 85 Zend_Application basics 85 Bootstrapping the storefront 86 Zend_Application configuration 88 The bootstrap class 94 Creating the bootstrap resources 96 Bootstrapping complete 100 The basic layout 100 A little task for you 102 Building the Storefront 102 The Storefront database 104 Database installation 104 Product table 105 ProductImage table 106 Category table 106 The user table 107 Introducing Zend_Db 107 Adding Zend_Db to the Storefront 108 Logging and debugging 108 Zend_Debug 109 Zend_Log 109 Adding Zend_Log to the Storefront 109 Using the logger 111 Database profiling with Zend_Log 113 Summary 114 Chapter 4: Storefront Models 115 Models in the Zend Framework 115 Model design 116 The application stack 116 Fat Model Skinny Controller 117 Fat Controller 117 Fat Model 118 Model design strategies 120 Direct inheritance 120 Has-a relationship (composition) 122 Domain Model 123 Further reading 124 Storefront Models 125 Model Resources 125 Managing Model Resources 126 Model Resource data sources 126 [ iii ] This material is copyright and is licensed for the sole use by Vadim Kudria on 4th October 2009 6352 108th St, , Forest Hills, , 11375 Table of Contents Model Resource Items 127 Resource Item business logic 127 Loading Models and Resources 129 Zend_Loader_Autoloader_Resource 129 Resource Autoloading 129 The SF Library 131 Summary 132 Chapter 5: Implementing the Catalog 133 Getting started 133 Creating the Catalog Model and Resources 134 Catalog model skeleton 134 Naming conventions 135 Catalog methods 136 Catalog Model Resources 137 Zend_Db_Table 138 Model Resource Items 140 Implementing the Catalog Model 143 Model Resource interfaces 143 Model Resource implementation 146 Catalog Model 156 Loading Models and other assets
Load more

Recommended publications
  • Design Pattern Interview Questions
    DDEESSIIGGNN PPAATTTTEERRNN -- IINNTTEERRVVIIEEWW QQUUEESSTTIIOONNSS http://www.tutorialspoint.com/design_pattern/design_pattern_interview_questions.htm Copyright © tutorialspoint.com Dear readers, these Design Pattern Interview Questions have been designed specially to get you acquainted with the nature of questions you may encounter during your interview for the subject of Design Pattern. As per my experience good interviewers hardly plan to ask any particular question during your interview, normally questions start with some basic concept of the subject and later they continue based on further discussion and what you answer: What are Design Patterns? Design patterns represent the best practices used by experienced object-oriented software developers. Design patterns are solutions to general problems that software developers faced during software development. These solutions were obtained by trial and error by numerous software developers over quite a substantial period of time. What is Gang of Four GOF? In 1994, four authors Erich Gamma, Richard Helm, Ralph Johnson and John Vlissides published a book titled Design Patterns - Elements of Reusable Object-Oriented Software which initiated the concept of Design Pattern in Software development. These authors are collectively known as Gang of Four GOF. Name types of Design Patterns? Design patterns can be classified in three categories: Creational, Structural and Behavioral patterns. Creational Patterns - These design patterns provide a way to create objects while hiding the creation logic, rather than instantiating objects directly using new opreator. This gives program more flexibility in deciding which objects need to be created for a given use case. Structural Patterns - These design patterns concern class and object composition. Concept of inheritance is used to compose interfaces and define ways to compose objects to obtain new functionalities.
    [Show full text]
  • Zend Framework 3 Cookbook
    Table of Contents Introduction 1.1 About the authors 1.2 Configuration zend-config for all your configuration needs 2.1 Manage your application with zend-config-aggregator 2.2 Data Manipulation Convert objects to arrays and back with zend-hydrator 3.1 Scrape Screens with zend-dom 3.2 Paginating data collections with zend-paginator 3.3 Log and Feeds Logging PHP applications 4.1 Discover and Read RSS and Atom Feeds 4.2 Create RSS and Atom Feeds 4.3 Authentication and Authorization Manage permissions with zend-permissions-rbac 5.1 Manage permissions with zend-permissions-acl 5.2 Web Services Implement JSON-RPC with zend-json-server 6.1 Implement an XML-RPC server with zend-xmlrpc 6.2 Implement a SOAP server with zend-soap 6.3 2 Security Context-specific escaping with zend-escaper 7.1 Filter input using zend-filter 7.2 Validate input using zend-validator 7.3 Validate data using zend-inputfilter 7.4 End-to-end encryption with Zend Framework 3 7.5 Deployment and Virtualization Create ZPKs the Easy Way 8.1 Using Laravel Homestead with Zend Framework Projects 8.2 Copyright Copyright note 9.1 3 Introduction Zend Framework 3 Cookbook During the year 2017, Matthew Weier O'Phinney and Enrico Zimuel started a series of blog posts on the offical Zend Framework blog covering its components. Zend Framework is composed by 60+ components covering a wide range of functionality. While the framework has typically been marketed as a full-stack MVC framework, the individual components themselves typically work independently and can be used standalone or within other frameworks.
    [Show full text]
  • Student Website Setup
    MVC in JSF and Spring Overview @author R.L. Martinez, Ph.D. Complexity is one of the primary challenges that has troubled software developers from the inception of the discipline. Software systems designed to perform multifaceted tasks are by nature complicated. Furthermore, software complexity continues to increase as we ask systems to accomplish more. With that in mind, designers are regularly pursuing techniques and methods to help reduce, or at least control, complexity growth. One such approach is known as MVC or, Model- View-Controller. Model-View-Controller MVC has its origins at Xerox’s PARC (Palo Alto Research Center) during the 1970-80’s. While there, Trygve Reenskaug, a visiting researcher from Norway, along with others such as Adele Goldberg, developed the MVC pattern for conceptualizing user interface based programs. PARC was an active site at that time for other important developments such as the graphical pointing device (mouse) and Object Oriented Programming (OOP). The first published work dealing with MVC at length was a 1988 article in The Journal of Object Technology. In software development terminology, MVC is known as an architectural pattern. A pattern is a reproducible and reusable construct which appears often enough in computer science as to be recognized. Instead of solving the same problem in a variety of sub-optimal ways, a pattern attempts to overlay a design with a common architectural solution. Developers not only become familiar with its application, but can also more easily understand a solution that uses a familiar pattern. There are a number of popular web application frameworks that offer MVC architectures which include: ASP.NET, Ruby on Rails, Zend Framework, Spring-MVC, etc.
    [Show full text]
  • Allench2.Pdf
    Zend Framework in Action by Rob Allen Nick Lo Steven Brown Chapter 2 Copyright 2009 Manning Publications Hello Zend Framework! This chapter covers ■ An introduction to the Model-View-Controller design pattern ■ Zend Framework’s controller components ■ The Zend_View component ■ Databases as models Before we can investigate in detail all the components of Zend Framework, we must get our bearings, and this is best done by building a simple website that uses the MVC) components. For a standard PHP application, the code to display the text “Hello World” constitutes just one line in one file: <?php echo 'Hello World'; In this chapter, we will build a Hello World application using Zend Framework. We will also consider how to organize the website’s files on disk to make sure we can find what we are looking for, and we will look at Zend Framework files required to create an application that uses the MVC design pattern. NOTE Zend Framework requires many files to create the foundation from which a full website can be created. This means the code for our Hello 18 The Model-View-Controller design pattern 19 World application may appear unnecessarily verbose as we set the stage for the full-blown website that will follow in later chapters. This chapter will walk through all the files required to build Hello World. We will also discuss Zend Framework’s MVC design and the core components it provides for build- ing the controller, view, and model in our application. Let’s dive right in and look at what the Model-View-Controller design pattern is all about.
    [Show full text]
  • The Mvc-Web Design Pattern
    THE MVC-WEB DESIGN PATTERN Ralph F. Grove and Eray Ozkan Department of Computer Science, James Madison University, Harrisonburg, VA, U.S.A. Keywords: Web, Web framework, Design patterns, Model view controller pattern. Abstract: The Model-View-Controller design pattern is cited as the architectural basis for many web development frameworks. However, the version of MVC used for web development has changed as it has evolved from the original Smalltalk MVC. This paper presents an analysis of those changes, and proposes a separate Web-MVC pattern that more accurately describes how MVC is implemented in web frameworks. 1 INTRODUCTION 2 SMALLTALK MVC The Model-View-Controller (MVC) design pattern The MVC design pattern was introduced with the is cited as the basis for the architecture of several Smalltalk programming environment as a way to web application frameworks, such as ASP .Net, structure interactive applications in a modular Rails, and Struts. The MVC pattern was originally fashion (Krasner and Pope, 1988). As the name implemented in the Smalltalk-80 programming implies, the MVC design pattern decomposes environment developed at Xerox PARC (Goldberg functionality into three major components. and Robson, 1985). As it has been adapted for web The model component encapsulates the domain- frameworks the MVC pattern has evolved in specific structure and functionality of the different ways, resulting in implementations that application. This essentially includes the state of the differ significantly from each other and from the application and operations that can change state. The original Smalltalk implementation. model also maintains dependencies of view and The first goal of this paper is to present the MVC controller components, which it notifies in the event design pattern, both in its original form (section 2) of changes in state.
    [Show full text]
  • Enterprise Application Design Patterns: Improved and Applied
    Enterprise Application Design Patterns: Improved and Applied Stuart Thiel A Thesis in The Department of Computer Science and Software Engineering Presented in Partial Fulfillment of the Requirements for the Degree of Master of Computer Science at Concordia University Montreal, Quebec, Canada January 2010 © Stuart Thiel, 2010 i CONCORDIA UNIVERSITY School of Graduate Studies This is to certify that the thesis prepared By: Stuart Thiel Entitled: Enterprise Application Design Patterns: Improved and Applied and submitted in partial fulfillment of the requirements for the degree of Master of Computer Science complies with the regulations of the University and meets the accepted standards with respect to originality and quality. Signed by the final examining committee: ______________________________________________Chair Dr. Nematollaah Shiri ______________________________________________Examiner Dr. Greg Butler ______________________________________________Examiner Dr. Yuhong Yan ______________________________________________Supervisor Dr. Patrice Chalin Approved by __________________________________________ Chair of Department or Graduate Program Director _____________________________________ Dr. Robin Drew, Dean Faculty of Engineering and Computer Science Date ______________________________________________ i ii Abstract Enterprise Application Design Patterns: Improved and Applied Stuart Thiel Providing developers with proper tools is of ever increasing importance as software integrates itself further into all aspects of our lives. Aside from conventional hardware and software tools, architectural and design patterns have been identified over the years as a means to communicate knowledge of known problems and their solutions. In this thesis, we present several refinements and additions to these patterns, building primarily on Martin Fowler’s Patterns of Enterprise Application Architecture (2003). We present a practical implementation approach to using these patterns and discuss a framework that we have developed to aid practitioners in following this methodology.
    [Show full text]
  • Design Patterns Past and Future
    Proceedings of Informing Science & IT Education Conference (InSITE) 2011 Design Patterns Past and Future Aleksandar Bulajic Metropolitan University, Belgrade, Serbia [email protected]; [email protected] Abstract A very important part of the software development process is service or component internal de- sign and implementation. Design Patterns (Gamma et al., 1995) provide list of the common pat- terns used in the object-oriented software design process. The primary goal of the Design Patterns is to reuse good practice in the design of new developed components or applications. Another important reason of using Design Patterns is improving common application design understand- ing and reducing communication overhead by reusing the same generic names for implemented solution. Patterns are designed to capture best practice in a specific domain. A pattern is supposed to present a problem and a solution that is supported by an example. It is always worth to listen to an expert advice, but keep in mind that common sense should decide about particular implemen- tation, even in case when are used already proven Design Patterns. Critical view and frequent and well designed testing would give an answer about design validity and a quality. Design Patterns are templates and cannot be blindly copied. Each design pattern records design idea and shall be adapted to particular implementation. Using time to research and analyze existing solutions is recommendation supported by large number of experts and authorities and fits very well in the pattern basic philosophy; reuse solution that you know has been successfully implemented in the past. Sections 2 and 3 are dedicated to the Design Patterns history and theory as well as literature sur- vey.
    [Show full text]
  • Object-Oriented Design Patterns
    Object-Oriented Design Patterns David Janzen EECS 816 Object-Oriented Software Development University of Kansas Outline • Introduction – Design Patterns Overview – Strategy as an Early Example – Motivation for Creating and Using Design Patterns – History of Design Patterns • Gang of Four (GoF) Patterns – Creational Patterns – Structural Patterns – Behavioral Patterns Copyright © 2006 by David S. 2 Janzen. All rights reserved. What are Design Patterns? • In its simplest form, a pattern is a solution to a recurring problem in a given context • Patterns are not created, but discovered or identified • Some patterns will be familiar? – If you’ve been designing and programming for long, you’ve probably seen some of the patterns we will discuss – If you use Java Foundation Classes (Swing), Copyright © 2006 by David S. 3 you have certaJiannzleyn. Aulls rieghdts rsesoervmed.e design patterns Design Patterns Definition1 • Each pattern is a three-part rule, which expresses a relation between – a certain context, – a certain system of forces which occurs repeatedly in that context, and – a certain software configuration which allows these forces to resolve themselves 1. Dick Gabriel, http://hillside.net/patterns/definition.html Copyright © 2006 by David S. 4 Janzen. All rights reserved. A Good Pattern1 • Solves a problem: – Patterns capture solutions, not just abstract principles or strategies. • Is a proven concept: – Patterns capture solutions with a track record, not theories or speculation 1. James O. Coplien, http://hillside.net/patterns/definition.html Copyright © 2006 by David S. 5 Janzen. All rights reserved. A Good Pattern • The solution isn't obvious: – Many problem-solving techniques (such as software design paradigms or methods) try to derive solutions from first principles.
    [Show full text]
  • Web Applications Engineering: Web Design Patterns and Guideline
    Web Applications Engineering: Web Design Patterns and Guideline Service Oriented Computing Group, CSE, UNSW Week 6 References used for the Lecture: http://java.sun.com/blueprints/patterns/index.html Core J2EE patterns, Deepak Alur, John Crupi and Dan Marlks, Prentice Hall Patterns of Enterprise Application Architecture, Martin Fowler, Addison-Wesley H. Paik, S. Venugopal (CSE, UNSW) COMP9321, 14s2 Week 6 1 / 65 J2EE Design Patterns What is a design pattern? Patterns in software were popularised by the book Design Patterns: Elements of Reusable Object-Oriented Software by Erich Gamma, Richard Helm, Ralph Johnson, and John Vlissides (aka Gang of Four) They observed and recognised recurring designs in numerous projects and documented this collection Since then many other design patterns are published covering patterns for various domains and purposes J2EE patterns: J2EE patterns represent best practice design based on collective experience of working with J2EE projects Patterns aim to provide and document a solution to a known, recurring problem in building J2EE applications http://java.sun.com/blueprints/patterns/index.html H. Paik, S. Venugopal (CSE, UNSW) COMP9321, 14s2 Week 6 2 / 65 J2EE Design Patterns There are over 20 patterns (and growing). We look at a few patterns that are highly relevant to COMP9321 ... Model View Controller: MVC is the J2EE BluePrints recommended architectural design pattern for interactive applications. Front Controller (Command): For providing a central dispatch point to handle all incoming requests. Service Locator: Typically used in business layer for locating resources (such as database connection) Data Access Object: typical pattern for data access layer (linking the data storage layer with the application) Business Delegate: in business layer H.
    [Show full text]
  • [ Team Lib ] Crawford and Kaplan's J2EE Design Patterns Approaches
    [ Team LiB ] • Table of Contents • Index • Reviews • Reader Reviews • Errata J2EE Design Patterns By William Crawford, Jonathan Kaplan Publisher: O'Reilly Pub Date: September 2003 ISBN: 0-596-00427-3 Pages: 368 Crawford and Kaplan's J2EE Design Patterns approaches the subject in a unique, highly practical and pragmatic way. Rather than simply present another catalog of design patterns, the authors broaden the scope by discussing ways to choose design patterns when building an enterprise application from scratch, looking closely at the real world tradeoffs that Java developers must weigh when architecting their applications. Then they go on to show how to apply the patterns when writing realworld software. They also extend design patterns into areas not covered in other books, presenting original patterns for data modeling, transaction / process modeling, and interoperability. [ Team LiB ] [ Team LiB ] • Table of Contents • Index • Reviews • Reader Reviews • Errata J2EE Design Patterns By William Crawford, Jonathan Kaplan Publisher: O'Reilly Pub Date: September 2003 ISBN: 0-596-00427-3 Pages: 368 Copyright Preface Audience Organization of This Book For Further Reading Conventions Used in This Book Comments and Questions Acknowledgments Chapter 1. Java Enterprise Design Section 1.1. Design Patterns Section 1.2. J2EE Section 1.3. Application Tiers Section 1.4. Core Development Concepts Section 1.5. Looking Ahead Chapter 2. The Unified Modeling Language Section 2.1. Origins of UML Section 2.2. The Magnificent Seven Section 2.3. UML and Software Development Lifecycles Section 2.4. Use Case Diagrams Section 2.5. Class Diagrams Section 2.6. Interaction Diagrams Section 2.7.
    [Show full text]
  • IC Coder's Club Design Patterns (In C++)
    Andrew W. Rose Simple exercise You have been tasked to move this pile from A to B Simple exercise You have been tasked to move this pile from A to B You have three resources available to you: a) Bare hands b) A stack of timber c) A horse and cart Simple exercise You have been tasked to move this pile from A to B You have three resources available to you: a) Bare hands b) A stack of timber c) A horse and cart How do you achieve the task in the quickest, least-painful way, which won’t leave you up-to-your-neck in the produce you are moving, nor smelling of it? Software analogy a) Bare hands b) A stack of timber c) A horse and cart Software analogy a) Bare hands b) A stack of timber c) A horse and cart Do a task manually Software analogy a) Bare hands b) A stack of timber c) A horse and cart Design Do a task the tools manually yourself Software analogy a) Bare hands b) A stack of timber c) A horse and cart Benefit from Design Do a task someone the tools manually else’s yourself hard work Software analogy a) Bare hands b) A stack of timber c) A horse and cart Benefit from someone else’s This is the purpose of design patterns! hard work Motivation I will, in fact, claim that the difference between a bad programmer and a good one is whether he considers his code or his data structures more important: Bad programmers worry about the code; good programmers worry about data structures and their relationships.
    [Show full text]
  • An Assessment of Design Patterns' Influence on a Java-Based E-Commerce Application Maria Mouratidou1, Vassilios Lourdas2, Alexander Chatzigeorgiou3 and Christos K
    Journal of Theoretical and Applied Electronic Commerce Research This paper is available online at ISSN 0718–1876 Electronic Version www.jtaer.com VOL 5 / ISSUE 1 / APRIL 2010 / 25-38 DOI: 10.4067/S0718-18762010000100004 © 2010 Universidad de Talca - Chile An Assessment of Design Patterns' Influence on a Java-based E-Commerce Application Maria Mouratidou1, Vassilios Lourdas2, Alexander Chatzigeorgiou3 and Christos K. Georgiadis4 University of Macedonia, Department of Applied Informatics, Thessaloniki, Greece 1 [email protected], 2 [email protected], 3 [email protected], 4 [email protected] Received 23 April 2009; received in revised form 23 December 2009; accepted 8 March 2010 Abstract Design patterns, acting as recurring solutions to common problems, offer significant benefits such as avoiding unnecessary complexity, and promoting code reuse, maintainability and extensibility. This paper describes how four not technology-specific or language-specific design patterns (Front Controller, Model View Controller, Transfer Object and Service to Worker) can be applied to one typical e-commerce application developed using Java EE platform. The first goal is to evaluate the improvement of design properties after the implementation of each design pattern using software metrics. Another goal is to assess the influence of design patterns on the maintainability of the e-commerce application under study by examining the evolution of software metrics when performing certain extensions. The results indicate that the application of patterns positively influences design properties such as coupling, complexity and messaging implying a possible improvement in high-level quality attributes such as flexibility, extensibility and reusability. Key words: Design Pattern, e-Commerce Application, Java Enterprise Edition, Software Metrics, Software Quality 25 Maria Mouratidou, Vassilios Lourdas, An Assessment of Design Patterns' Influence on a Java-based E-Commerce Application Alexandros Chatzigeorgiou and Christos K.
    [Show full text]