Ted Faison

Ted Faison has over 25 years of experience in the software industry and has been involved with object-oriented-programming and component-based development since the inception of those technologies. He has worked primarily in the private sector, also as a consultant for the U.S. and Italian governments. He is a member of IEEE and ACM, and an active researcher in the field of software engineering, specializing in component-based software. He is a senior software engineer at the Southern California Auto Club, where he works on the development of a large .NET distributed system for customer relationship management. Ted is the author of Component-Based Development with Visual C#, Borland C++ Object-Oriented Programming, and Graphical User Interfaces with TurboC++.

Event-Based Programming

Event-Based Programming

16/11/2014

Ted Faison
Languages like C#, VB .NET, and Delphi include built-in support for events, and these events become very powerful when they connect the objects and components of a system. Events make it possible for such parts to interact without any coupling. And the resulting parts can be developed and tested individuallywhich keeps the code clean and simple. Component-based development (CBD) is an extension of object-oriented programming. CBD does away with the language and vendor-specific limitations of OOP, makes software reuse more practical and accelerates the development process. Event-based programming is the next logical step in CBD, and makes components more reusable due to their decoupled nature. But event-based systems are easier to develop, which means they're cheaper and more reliable than traditional OOP or CBD systems. This book teaches you how to develop software based on parts that interact primarily through an event mechanism. You'll learn how to use events in many different situations, to solve recurring development problems without coupling. The book introduces Signal Wiring Diagram, a novel form of software diagram similar to the circuit diagrams used by hardware designers. The book concludes with a series of case studies, incorporating all featured concepts. In a nutshell, you'll want to pick up a copy of this book because it How to use an event-based paradigm to reduce or completely eliminate coupling between classes and components Describes components, including coordinators, workers, builders, binders, and routers Three complete case studies that model concepts being used to design small, medium, and large systems
Event-Based Programming - Second Edition

Event-Based Programming - Second Edition

23/12/2011

Ted Faison
Languages like C#, VB .NET, and Delphi include built-in support for events, and these events become very powerful when they connect the objects and components of a system. Events make it possible for such parts to interact without any coupling. And the resulting parts can be developed and tested individually which keeps the code clean and simple. Component-based development (CBD) is an extension of object-oriented programming. CBD does away with the language and vendor-specific limitations of OOP, makes software reuse more practical and accelerates the development process. Event-based programming is the next logical step in CBD, and makes components more reusable due to their decoupled nature. But event-based systems are easier to develop, which means they're cheaper and more reliable than traditional OOP or CBD systems. This book teaches you how to develop software based on parts that interact primarily through an event mechanism. You'll learn how to use events in many different situations, to solve recurring development problems without coupling. The book introduces Signal Wiring Diagram, a novel form of software diagram similar to the circuit diagrams used by hardware designers. The book concludes with a series of case studies, incorporating all featured concepts. In a nutshell, you'll want to pick up a copy of this book because it: Shows how to use an event-based paradigm to reduce or completely eliminate coupling between classes and components Describes components, including coordinators, workers, builders, binders, and routers Contains three complete case studies that model concepts being used to design small, medium, and large systems