Skip to main content Accessibility help

We use cookies to distinguish you from other users and to provide you with a better experience on our websites. Close this message to accept cookies or find out how to manage your cookie settings.

Close cookie message
×
  1. Home
  2. Series
  3. SIGS: Managing Object Technology

The Managing Object Technology series focuses on the managerial aspects of object orientation. Specifically, this series provides readers with timely and accurate information dealing with a wide range of issues related to managing object-oriented software projects. The books are written by, and for, the professional community and are aimed at managers, consultants, developers, and educators involved in managing systems developed using these new, emergent technologies.

  • General Editors: Barry McGibbon, SIGS Publications, Inc., New York

Refine search

Refine search

Content type:
Publication date:
Subject: Show more
Journals Show more
Publishers: Show more
Series: Show more
Collections: Show more

Actions for selected content:

Select all | Deselect all
  • View selected items
  • Export citations
  • Download PDF (zip)
  • Save to Kindle
  • Save to Dropbox
  • Save to Google Drive

Save Search

You can save your searches here and later view and run them again in "My saved searches".

Please provide a title, maximum of 40 characters.
Cancel
×

5 results in SIGS: Managing Object Technology

Distributed Object Architectures with CORBA
  • Henry Balen
  • With Mark Elenko, Jan Jones, Gordon Palumbo
  • Published online:
    07 September 2010
    Print publication:
    13 February 2000
  • Distributed Object Architectures with CORBA is a guide to creating a software architecture comprising distributed components. While it is based on OMG's Common Object Request Broker Architecture (CORBA) standard, the principles also apply to architecture built with other technology (such as Microsoft's DCOM). As ORB products evolve to incorporate new additions to CORBA, the knowledge and experience required to build stable and scalable systems is not widespread. With this book the reader can develop the skills and knowledge that is necessary for building such systems. The book assumes a familiarity with object-oriented concepts and the basics of CORBA. Software developers who are new to building systems with CORBA-based technologies will find this book a useful guide to effective development.

Building Object Applications that Work
  • Your Step-by-Step Handbook for Developing Robust Systems with Object Technology
  • Scott W. Ambler
  • Published online:
    07 September 2010
    Print publication:
    01 January 1997
  • Written by internationally acclaimed trainer and developer Scott Ambler, this book is a must-have resource for designers, programmers and testers of today's OO applications. The author takes you through the entire process of building object applications, from analyzing the project (so you know what you need to build), to designing a user-friendly interface, to testing your approaches to make sure your applications work properly.Building Object Applications That Work includes sections on:how to use the Unified Modeling Language effectively analysis, so you know what you need to build design techniques, so that you know how you are going to build your application collecting the right metrics to improve your development approach applying OO patterns to improve the quality of your applications creating applications for stand-alone, client/server and distributed environments using both relational and object-oriented databases to make your objects persistent architecting your applications so they are maintainable and extensible.

More Process Patterns
  • Delivering Large-Scale Systems Using Object Technology
  • Scott W. Ambler
  • Published online:
    04 August 2010
    Print publication:
    13 January 1999
  • With his new book, More Process Patterns, Scott Ambler picks up where Process Patterns left off. In this book, the author presents process patterns for the second half of the development lifecycle. He covers the Deliver phase and the Maintain and Support phase of large-scale, object-oriented system development. Each presented pattern is based upon proven, real-world techniques and is geared toward medium to large-size organizations who need to develop software internally to support their main line of business. The book covers major management issues, such as people and risk management, and quality assurance. Developers and project managers who have just taken their first OO development course will find this book essential. It takes the true needs of software development and delivery into consideration, including cross-project, maintenance, operations, and support issues. This book uses the Unified Modeling Language (UML).

Tried and True Object Development
  • Industry-Proven Approaches with UML
  • Ari Jaaksi, Juha-Markus Aalto, Ari Aalto, Kimmo Vättö
  • Foreword by Derek Coleman
  • Published online:
    06 July 2010
    Print publication:
    28 December 1998
  • Written by four experienced Nokia Telecommunications software developers, this is a practical book about object-based and component-based software development. The book concentrates on the most important issues in real-life software development, such as the development process itself, software architecture, the development of user interfaces, data management, and the development of large commercial software products. The book exemplifies the presented practices by using the Unified Modeling Language (UML).

UML Xtra-Light
  • How to Specify your Software Requirements
  • Milan Kratochvil, Barry McGibbon
  • Published online:
    14 October 2009
    Print publication:
    18 November 2002
  • If you are a non-technical person with a stake in the success of a software project, this book is for you. Business managers often find it impossible to communicate business objectives and specify their software requirements to technical members of staff. This beginner's guide teaches readers to communicate with software developers in a more focused, effective way. It describes the basic diagrams of the UML modeling notation and shows how they are used to specify requirements in an unambiguous way. When used on project, the risk of failure through unclear requirements is removed.