|
How to Deliver Client/Server Applications that Work Alex Bakman 1995 | 227 pages ISBN: 013304601X |
|||
| $29.00 | Softbound print book | Out of print (?) | |
Table of Contents
| Preface | xi |
| Acknowledgments | xii |
|
I Business and Management Issues | |
| Chapter 1 Introduction | 1 |
| Whom is This Book For? | 1 |
| How to Read This Book | 2 |
| Terminology | 3 |
| Client/Server Computing | 4 |
| Cooperative Processing | 6 |
| State of the Industry | 7 |
| Suggested Reading | 7 |
| Chapter 2 To Proceed or Not to Proceed | 9 |
| Management Support | 9 |
| Get a Client Sponsor | 10 |
| Start Simple, Start Small | 10 |
| Get Users on Your Side | 11 |
| Strike a Balance | 12 |
| Good Team = Success | 12 |
| Decision Support or Transaction Processing | 13 |
| System Size | 15 |
| Is it a WAN or LAN Application? | 16 |
| The Geography | 17 |
| Importance of Proper Application Architecture | 17 |
| Scale?epartmental or Enterprise Wide? | 19 |
| Operational Support | 19 |
| Conclusion | 21 |
| Suggested Reading | 21 |
| Chapter 3 Cost/Benefit Analysis of Client/Server Systems | 23 |
| The Mechanics of Cost/Benefit Analysis | 23 |
| The Biggest Client/Server Myth | 24 |
| Expenses, Expenses, and More Expenses | 24 |
| Software | 25 |
| Operating Systems | 26 |
| Support Tools | 27 |
| Development Tools | 28 |
| How Can Client/Server Systems Cost More? | 29 |
| The Cost of Testing | 30 |
| The Cost of Operational, Ongoing Support | 30 |
| State of Support Tools | 32 |
| Business Benefits | 32 |
| Graphical User Interface | 35 |
| Justifying Client/Server | 36 |
| Examples | 37 |
| Conclusion | 42 |
| Suggested Reading | 42 |
| Chapter4 Vendor Management | 43 |
| Vendor Selection | 43 |
| Writing a Vendor Contract | 46 |
| Conclusion | 47 |
| Suggested Reading | 48 |
| Chapter 5 Assembling the Right Team | 49 |
| A Technical Architect | 49 |
| A GUI Designer and Programmer | 50 |
| AServer Programmer | 52 |
| Systems Administrator | 53 |
| Putting it All Together | 53 |
| Suggested Reading | 55 |
|
II Distributed Systems Technology | |
| Chapter 6 Computer Networking | 57 |
| The Local Area Network (LAN) | 57 |
| The Open Systems Interconnect (OSI) Model | 59 |
| The Physical Layer | 62 |
| The Data LinkLayer | 63 |
| Ethernet | 63 |
| Token Ring | 64 |
| FDDI | 65 |
| 100-Megabit/Second Ethernet | 66 |
| The Network Layer | 66 |
| The Transport Layer | 69 |
| TCP/IP | 70 |
| IPX/SPX | 71 |
| NetBIOS | 72 |
| APPC | 72 |
| Example: NetBIOS Datagrams | 74 |
| Connection-Oriented Service | 75 |
| The Session Layer | 77 |
| The Presentation Layer | 78 |
| The Application Layer | 79 |
| Suggested Reading | 80 |
| Chapter 7 Operating Systems and Network Operating Systems | 81 |
| Networking | 82 |
| Preemptive Multitasking | 83 |
| Support for Multiprocessing and Threads | 84 |
| File System Support | 86 |
| Interprocess Communication Facilities | 86 |
| Virtual Memory Management | 87 |
| Robustness | 88 |
| Security | 88 |
| Network Operating Systems | 89 |
| Redirection | 89 |
| Architecture of a Network Operating System | 91 |
| Popular Network Operating Systems | 91 |
| Peer-to-Peer Network Operating Systems | 92 |
| Which Network Operating System Should I Use? | 93 |
| Suggested Reading | 94 |
| Chapter 8 Database Management Systems and Application Development Tools | 95 |
| Database Middleware | 97 |
| Database Gateways | 99 |
| Gateway Selection | 100 |
| Data Distribution Capabilities | 101 |
| Application Interfaces to DBMSs | 104 |
| Static SQL | 104 |
| Dynamic SQL | 106 |
| DBMS Server Memory Requirement | 107 |
| DBMS User Support Architecture | 107 |
| Example: Microsoft's SQL Server | 108 |
| SQL Server Programming | 108 |
| Application Development Tools | 109 |
| 4GLs | 110 |
| Example: PowerBuilder | 111 |
| Building a PowerBuilder Application | 113 |
| 4GLs Versus 3GLs | 113 |
| Suggested Reading | 116 |
| Chapter 9 Groupware | 117 |
| Workflow Systems | 120 |
| Example: Lotus Notes | 121 |
| Customizing Notes | 123 |
| Suggested Reading | 125 |
|
III Application Development and Deployment | |
| Chapter 10 Distributed Application Models | 127 |
| Understanding the Network | 127 |
| Minimize NetsvorkTrips | 128 |
| Fat Versus Thin Clients | 129 |
| Six Principles of Function Placement | 130 |
| Distributed Application Models | 132 |
| The Distributed Interface Model | 134 |
| The Remote Interface Model | 140 |
| Distributed Logic Model | 143 |
| Benefits of Using Transport Protocols | 152 |
| Disadvantages of the Distributed Logic Model | 155 |
| The Remote Data Management Model | 155 |
| File Server Disadvantages | 157 |
| Distributed Database Model | 160 |
| Remote Request | 161 |
| Remote Unit of Work | 162 |
| Distributed Unit of Work | 162 |
| Distributed Request | 163 |
| Chapter 11 Development Methodology | 165 |
| Proposed Methodology | 166 |
| Suggested Reading | 182 |
| Chapter 12 Testing | 183 |
| Cost of Quality | 183 |
| Testing Client/Server Applications | 185 |
| The Model of lice | 186 |
| Usability Testing | 187 |
| Common GUI Design Mistakes | 187 |
| Usability Labs | 189 |
| Suggested Reading | 202 |
| Chapter 13 Systems Management and Deployment | 203 |
| Change Management | 205 |
| Acceptance Testing Lab | 208 |
| Problem Management | 209 |
| The Problem Management Process | 211 |
| Disaster Recovery Procedures | 212 |
| Software Distribution | 213 |
| Protocol Analyzers | 216 |
| Network Management | 217 |
| An Alternative to SNMP | 220 |
| Distributed Systems Management | 220 |
| Conclusion | 222 |
| Suggested Reading | 222 |
| Index | 223 |
DESCRIPTION
How to Deliver Client/Server Applications that Work focuses on the needs of a project leader or a technical architect who is responsible for turning the vision of the executive into a successful client/server system. Unlike other current books, which are either written for senior management responsible for strategy or for programmers who need low level programming details, this is a practical and concise, "how-to" guide and a roadmap for the process which will successfully deliver client/server applications. It leads the project leader through all the stages of the life cycle -- from conceptualization to system development and deployment. How to Deliver Client/Server Applications That Work offers practical, proven advice on the business and technical issues that a project leader must deal with effectively.Some highlights:
- covers entire system development life cycle
- presents various client/server models
- discusses organizational deployment issues
- provides cost/benefit analyses
- explains distributed systems technologies
- rich in practical pointers, checklists, etc.
- based on real-life experience
How to Deliver Client/Server Applications that Workis for technical architects, systems consultants, project leaders, chief programmers, technical managers, systems support managers, systems administrators, and all others working on client/server applications.
