For courses on the development of large client-server and web database systems. A Methodology for Client/Server and Web Application Development shows you how to impose needed discipline on even the most complex Web and client/server development projects. Fournier's start-to-finish methodology walks you step-by-step through every phase: survey, analysis, design, construction, implementation and beyond. Master powerful techniques for delivering finished software faster, including iterative/incremental development, prototyping, timeboxing and joint facilitated user sessions.
Book Description
Editorial Reviews
From the Inside Flap
Preface
WHY THIS BOOK?
This book proposes a comprehensive methodology that guides you through the successful development of large-scale and complex client-server or Web database applications. Doing so, it also explains how to circumvent critical issues and potential dangers that might adversely affect the development of large software systems.
Moreover, this book offers several powerful techniques that can be used by your IT organization to accelerate the construction of large and complex business applications, such as iterative/incremental system development, prototyping, timeboxing, and joint facilitated sessions with users. Similarly, the book strongly recommends the use of component-based application development architectures to maximize reusability and hence reduce the cycle time associated with the system development process.
WHAT MAKES THIS BOOK UNIQUE?
This book addresses the various sets of technical activities that must be conducted to effectively develop a sound client-server or Web database system. However, rather than concentrating on the "how to," this publication primarily focuses on the "what to do."
The book contains numerous guidelines, suggested best practices, hints, and checklists that are based on practical experience and that can be advantageously used by practitioners to successfully develop quality-oriented client-server and Web-based software systems.
This book also emphasizes the importance of enterprises investing efforts in developing and implementing a robust yet flexible enterprise technology infrastructure. An efficient enterprise technology infrastructure is mandatory to effectively support the accelerated development of large software systems. The current enterprise technology infrastructures must be re-engineered or extended to appropriately account for the introduction of new development tools, technologies, and techniques. The new enterprise technology infrastructures must be built on industry-wide standards to accommodate the emergence of new and improved technologies, as time goes by.
WHAT DOESN'T THIS BOOK CONTAIN?
This book does not address the set of project management processes that must be conducted to effectively plan, organize, manage, track, and control the development process of large software systems. It addresses solely the technical activities that are involved in developing large software systems. However, a companion publication will likely be developed in the near future, to address the most critical project management best practices and therefore complement the technical information provided in this current book. This book is not your typical "one-minute" methodology cookbook to client-server and Web database application development. Its content is at the right level of detail for large software development undertakings. In fact, the book is primarily intended for "real-world" software practitioners who must work in the "trenches," often with newer technologies, and yet are hard pressed by their customers to deliver workable system solutions in a compressed timeframe.
As such, this book does not promise you silver bullets. It does not attempt to fool you into thinking that large-scale software development efforts are easy and can be achieved overnight, only with the help of the latest RAD tool available on the market, and without the support of a solid information technology infrastructure. Those involved in developing large and complex software systems know better than this the perils of any particular software development process.
WHO SHOULD READ THIS BOOK?
This book should be read by IT executives, managers, project leaders, developers, specific information technology specialists, software testers, and operations staff around the world who are involved in developing large and complex client-server or Web database applications.
The book is also intended for modern IT organizations who are currently in the process of renewing themselves while planning the introduction of new client-server and Web technologies in their enterprise. These organizations will then be interested in reading the chapter titled Client-Server and Web Technology Architecture and Support Services. This chapter provides the readers with a holistic view of the major issues involved in planning, designing, and implementing the new type of enterprise technology infrastructure that is required to successfully nurture the development, deployment, and support of large client-server or Web database applications.
Finally, the book can be used as a textbook for college or university courses on the development of large client-server and Web database systems.
BOOK ROADMAP
Looking at Figure P.1, the book consists of an introduction chapter, which is then followed by three broad logical sections, identified as sections A, B, and C.
Figure P.1 Book Roadmap.
Following is a brief description of the introduction chapter and the three major sections A, B, and C.
INTRODUCTION
The introduction chapter provides an overview of the book and discusses how it is organized. It presents the fundamental concepts that are critical to support the proposed client-server and Web database application development methodology. The process-driven system development methodology that is provided in this book is suited for a variety of business projects of different sizes and complexities. However, it is particularly well adapted for large and complex client-server or Web database applications.
SECTION A
Section A contains the five core chapters that describe in detail the particular system development phases and set of technical activities that should be performed to successfully build a quality client-server or Web database application.
Table P.1 provides a brief description of these five chapters.
Table P.1 Section A:
CHAPTER DESCRIPTION
Chapter 2:
Survey Phase
The preliminary business needs that point toward a client-server/Web application system solution are identified and documented during this stage. A sketch of the initial scope and boundaries of the proposed system are outlined jointly with the customers. Similarly, the development team assesses the major project assumptions, risks, and constraints. The survey phase technical activities can be conducted either through a series of joint facilitated sessions, with the active participation of the users, or in a more traditional system development approach.
Chapter 3:
Analysis Phase
A blueprint of the major application data and functional requirements is quickly captured with the direct involvement of the customers. A series of joint facilitated sessions can be used specifically for this purpose. The preliminary data and process application distribution requirements are also documented at this stage, along with additional system requirements, such as the security, performance, and hardware/software/networking application needs.
If necessary, the system is partitioned into smaller chunks, where core functions can be implemented more rapidly by the development team, either in sequence or in parallel. Moreover, a first stab at defining the system data conversion, training, and testing strategies is done with the users during this phase.
Finally, a live system prototype is quickly constructed to demonstrate the graphical user interface and some of the core functionality elements of the proposed client-server or Web database application. Reusable GUI classes or application system templates are used to speed up the delivery of the initial application graphical interface. This fully interactive prototype is used to firm up the initial set of critical user requirements that center on the application graphical interface.
Chapter 4:
Design Phase
During this phase, the design of the client-server or Web-based system solution is gradually refined and augmented with all the necessary automated solution details. The application reusable GUI classes and system templates may be created or extended, where applicable.
The sets of reusable functions that can be effectively reutilized across the application are developed first, prior to developing the application custom functions.
The detailed design of the database(s) that is(are) required to support the system information needs is finalized, including stored procedures and triggers.
The data and process distribution design solutions are revisited and expanded with more detailed information. Similarly, the system training, data conversion, and testing strategies are refined and augmented with more detailed information. Based on the design specifications, high-level test cases are defined by the developers toward the end of the design phase.
Chapter 5:
Construction Phase
The detailed functional components of the client-server or Web application are coded, unit tested, and then gradually integrated into a complete and robust application system. In parallel to the coding and testing activities, the development team gradually sets up the initial user training
WHY THIS BOOK?
This book proposes a comprehensive methodology that guides you through the successful development of large-scale and complex client-server or Web database applications. Doing so, it also explains how to circumvent critical issues and potential dangers that might adversely affect the development of large software systems.
Moreover, this book offers several powerful techniques that can be used by your IT organization to accelerate the construction of large and complex business applications, such as iterative/incremental system development, prototyping, timeboxing, and joint facilitated sessions with users. Similarly, the book strongly recommends the use of component-based application development architectures to maximize reusability and hence reduce the cycle time associated with the system development process.
WHAT MAKES THIS BOOK UNIQUE?
This book addresses the various sets of technical activities that must be conducted to effectively develop a sound client-server or Web database system. However, rather than concentrating on the "how to," this publication primarily focuses on the "what to do."
The book contains numerous guidelines, suggested best practices, hints, and checklists that are based on practical experience and that can be advantageously used by practitioners to successfully develop quality-oriented client-server and Web-based software systems.
This book also emphasizes the importance of enterprises investing efforts in developing and implementing a robust yet flexible enterprise technology infrastructure. An efficient enterprise technology infrastructure is mandatory to effectively support the accelerated development of large software systems. The current enterprise technology infrastructures must be re-engineered or extended to appropriately account for the introduction of new development tools, technologies, and techniques. The new enterprise technology infrastructures must be built on industry-wide standards to accommodate the emergence of new and improved technologies, as time goes by.
WHAT DOESN'T THIS BOOK CONTAIN?
This book does not address the set of project management processes that must be conducted to effectively plan, organize, manage, track, and control the development process of large software systems. It addresses solely the technical activities that are involved in developing large software systems. However, a companion publication will likely be developed in the near future, to address the most critical project management best practices and therefore complement the technical information provided in this current book. This book is not your typical "one-minute" methodology cookbook to client-server and Web database application development. Its content is at the right level of detail for large software development undertakings. In fact, the book is primarily intended for "real-world" software practitioners who must work in the "trenches," often with newer technologies, and yet are hard pressed by their customers to deliver workable system solutions in a compressed timeframe.
As such, this book does not promise you silver bullets. It does not attempt to fool you into thinking that large-scale software development efforts are easy and can be achieved overnight, only with the help of the latest RAD tool available on the market, and without the support of a solid information technology infrastructure. Those involved in developing large and complex software systems know better than this the perils of any particular software development process.
WHO SHOULD READ THIS BOOK?
This book should be read by IT executives, managers, project leaders, developers, specific information technology specialists, software testers, and operations staff around the world who are involved in developing large and complex client-server or Web database applications.
The book is also intended for modern IT organizations who are currently in the process of renewing themselves while planning the introduction of new client-server and Web technologies in their enterprise. These organizations will then be interested in reading the chapter titled Client-Server and Web Technology Architecture and Support Services. This chapter provides the readers with a holistic view of the major issues involved in planning, designing, and implementing the new type of enterprise technology infrastructure that is required to successfully nurture the development, deployment, and support of large client-server or Web database applications.
Finally, the book can be used as a textbook for college or university courses on the development of large client-server and Web database systems.
BOOK ROADMAP
Looking at Figure P.1, the book consists of an introduction chapter, which is then followed by three broad logical sections, identified as sections A, B, and C.
Figure P.1 Book Roadmap.
Following is a brief description of the introduction chapter and the three major sections A, B, and C.
INTRODUCTION
The introduction chapter provides an overview of the book and discusses how it is organized. It presents the fundamental concepts that are critical to support the proposed client-server and Web database application development methodology. The process-driven system development methodology that is provided in this book is suited for a variety of business projects of different sizes and complexities. However, it is particularly well adapted for large and complex client-server or Web database applications.
SECTION A
Section A contains the five core chapters that describe in detail the particular system development phases and set of technical activities that should be performed to successfully build a quality client-server or Web database application.
Table P.1 provides a brief description of these five chapters.
Table P.1 Section A:
CHAPTER DESCRIPTION
Chapter 2:
Survey Phase
The preliminary business needs that point toward a client-server/Web application system solution are identified and documented during this stage. A sketch of the initial scope and boundaries of the proposed system are outlined jointly with the customers. Similarly, the development team assesses the major project assumptions, risks, and constraints. The survey phase technical activities can be conducted either through a series of joint facilitated sessions, with the active participation of the users, or in a more traditional system development approach.
Chapter 3:
Analysis Phase
A blueprint of the major application data and functional requirements is quickly captured with the direct involvement of the customers. A series of joint facilitated sessions can be used specifically for this purpose. The preliminary data and process application distribution requirements are also documented at this stage, along with additional system requirements, such as the security, performance, and hardware/software/networking application needs.
If necessary, the system is partitioned into smaller chunks, where core functions can be implemented more rapidly by the development team, either in sequence or in parallel. Moreover, a first stab at defining the system data conversion, training, and testing strategies is done with the users during this phase.
Finally, a live system prototype is quickly constructed to demonstrate the graphical user interface and some of the core functionality elements of the proposed client-server or Web database application. Reusable GUI classes or application system templates are used to speed up the delivery of the initial application graphical interface. This fully interactive prototype is used to firm up the initial set of critical user requirements that center on the application graphical interface.
Chapter 4:
Design Phase
During this phase, the design of the client-server or Web-based system solution is gradually refined and augmented with all the necessary automated solution details. The application reusable GUI classes and system templates may be created or extended, where applicable.
The sets of reusable functions that can be effectively reutilized across the application are developed first, prior to developing the application custom functions.
The detailed design of the database(s) that is(are) required to support the system information needs is finalized, including stored procedures and triggers.
The data and process distribution design solutions are revisited and expanded with more detailed information. Similarly, the system training, data conversion, and testing strategies are refined and augmented with more detailed information. Based on the design specifications, high-level test cases are defined by the developers toward the end of the design phase.
Chapter 5:
Construction Phase
The detailed functional components of the client-server or Web application are coded, unit tested, and then gradually integrated into a complete and robust application system. In parallel to the coding and testing activities, the development team gradually sets up the initial user training
From the Back Cover
Bring discipline and power to all your Web & C/S projects! Roger Fournier's.
A Methodology for Client/Server and Web Application Development shows you how to impose needed discipline on even the most complex Web and client/server development projects. Fournier's start-to-finish methodology walks you step-by-step through every phase: survey, analysis, design, construction, implementation and beyond. Master powerful techniques for delivering finished software faster, including iterative/incremental development, prototyping, timeboxing and joint facilitated user sessions.
With extensive examples, checklists and worksheets, Fournier demonstrates how to:
- Build an enterprise architecture with true scalability and flexibility.
- Leverage object-oriented programming techniques to the fullest.
- Establish an effective testing process.
- Promote reusability with DCOM/ActiveX ™, CORBA, and JavaBeans ™ components.
Implement technology infrastructures that support Web and C/S development. Discover specific ways to mitigate the risks that lead so many Web and client/server projects to fail. Learn how to improve communication with users, design databases and Web database access more effectively, plan for user training and data conversion and much more. There are no silver bullets, but this book's systematic "best practices" approach, tips and techniques will help you take charge of your Web and client/server development-and deliver business results faster than ever before.
Product Details
Would you like to update product info or give feedback on images?
|
More About the Author
Discover books, learn about writers, read author blogs, and more.
Customer Reviews
|
Share your thoughts with other customers:
|
||||||||||||||||||||||
|
Most Helpful Customer Reviews
47 of 49 people found the following review helpful:
5.0 out of 5 stars
Build Real-World Enterprise Systems,
By George R. McCullen (Washington D.C.) - See all my reviews
This review is from: A Methodology for Client/Server and Web Application Development (Paperback)
I thoroughly enjoyed reading Roger Fournier's book. I am a voracious reader with many books on Client-Server, Web technology, systems development, etc.; however, Mr. Fournier's methodology is a welcome addition to my library. This may be the most practical book that I have seen for systematically approaching the development of complex systems. I plan on incorporating much of his methodology and ideas in my future projects. I would recommend it for anyone interested in learning about client-server or web technology and it is a great reference for professionals involved in project development (both large and small).I am encouraged by the books honesty in stressing that building large systems is hard work. Too often the literature touts "sure-fire" success if you follow a particular "cook book" sequence or employ specific technology. As anyone in the business knows, good preparation, realistic goals, teamwork and attention to detail are more important than choosing the latest "hot" technology. The book walks through the stages of a projects life cycle and provides much "food for thought" in how to get each stage right. But it never deceives one into thinking the process is easy and it never implies that the proposed methods are the only logical approach to take. Although the title focuses on C/S and Web Application development, the methodology presented has a much broader application. It provides an excellent framework for development of any complex system. The book is well written. It provides broad coverage from requirements discovery through project deployment. The book contains so much information that the reader may want to focus on specific areas of high personal interest at first- such as Web architecture or systems analysis. Fortunately, Mr. Fournier's style is such that you can concentrate on the chapters that are most relevant to your needs first and later read the other sections without a significant loss of continuity. As an Enterprise Architect, I have found the book very helpful. It contains useful information for project managers, enterprise and system architects, analysts, developers and test engineers. Without going into details I'll say that the tables, checklists and web-references presented throughout the book have been very useful. I believe the survey, analysis and joint facilitated session chapters are well presented and offer a lot of information on project definition and scoping. They certainly make clear the importance of up-front planning to a projects success. For my purposes, the C/S and Web Architecture chapter was of high interest and was well presented. I was glad to see a chapter devoted to software re-use. However, I would like to see this chapter expanded to include more information on infrastructure, middleware and components. I would recommend anyone interested in the book to quickly scan the table of contents to see the wide range of information that can be found. Mr. Fournier mentions that there might be a follow-up book focusing on the project management aspects of building complex systems. I sincerely hope he writes this.
34 of 35 people found the following review helpful:
5.0 out of 5 stars
A great roadmap to Client/Server and Web Development,
By A Customer
This review is from: A Methodology for Client/Server and Web Application Development (Paperback)
Having just read Roger Fournier's book on Client/Server methodology & Web development, I can offer the opinion that this book is a great roadmap for anyone responsible for large client/server and web Application Development. He has obvious knowledge of the System Development life cycle and his book illustrates with very good detail, the major technical phases and deliverables required for a successful development effort. He has also provided some real life examples that will help you both avoid the most commonly encountered problems, and using best practices, be capable of successfully delivering a major Development effort. Fournier's coverage of the testing process is detailed and complete. Testing is covered in the development phase's chapters, from analysis to construction. Chapter 8 is entirely dedicated to client/server and web testing. Chapter 9 provides some valuable discussions on the type of IT technology infrastructures that must be put in place to facilitate the development and support of mission-critical client/server and web database applications. In chapter 9, Fournier also describes some of the most critical system management services that are required to successfully manage distributed IT environments. Finally, chapter 9 ends with a very complete but high level description of all the different web technologies that an organization can use to increase productivity in the work place. The information on GUI design is relevant and to the point, although it is scattered in different chapters of the book. Even though chapter 12 is entirely dedicated to this important subject, Fournier should have consolidated all GUI-related design guidelines in a single chapter. Such an approach would have saved valuable time for busy developers who want to quickly read, in one location, everything there is about this subject. I also wish Fournier had covered web-specific GUI guidelines in greater depth in chapter 11, which also covers a variety of design topics on web application development. His treatment of web page navigation provides interesting guidelines and suggestions. Although Fournier clearly stated that his book does not cover project management activities, it would have been nice to provide more information on this important subject. It could have been the subject of a separate chapter or maybe an appendix. However, in his book's preface Fournier states that a "companion" book on project management should be written soon. I am not aware of any comparable methodology book out there that can compete with Fournier's book, except maybe some costly commercial methodologies. As a whole, I most definitely recommend this down-to-earth, practical technical reference guide on large client-server and web application development software to both developers and Project Managers. Despite little quirks, I give Fournier's book five stars and hope he publishes a companion book on project management best practices in the not too distant future.
5.0 out of 5 stars
Completeness,
By
Amazon Verified Purchase(What's this?)
This review is from: A Methodology for Client/Server and Web Application Development (Paperback)
I am very carefull about the books I buy simply because most books just teach you the alphabet again. This one is a rare exception. Very exhaustive coverage and an important reference book in my collection.
Share your thoughts with other customers: Create your own review
|
|
Tags Customers Associate with This Product(What's this?)Click on a tag to find related items, discussions, and people.
|
Sell a Digital Version of This Book in the Kindle Store
If you are a publisher or author and hold the digital rights to a book, you can sell a digital version of it in our Kindle Store.
Learn more
Customer Discussions
|
This product's forum
Active discussions in related forums
Search Customer Discussions
|
Related forums
|
Listmania!
So You'd Like to...
Look for Similar Items by Category
- Books > Computers & Technology > Business & Culture > Manager's Guides to Computing
- Books > Computers & Technology > Computer Science > Software Engineering > Information Systems
- Books > Computers & Technology > Computer Science > Systems Analysis & Design
- Books > Computers & Technology > Networking
- Books > Computers & Technology > Software
- Books > Computers & Technology > Web Development > Web Services
- Books > Science & Math > Mathematics
