Object-oriented design choices (Record no. 70721)

000 -LEADER
fixed length control field 03763cam a2200529Mi 4500
001 - CONTROL NUMBER
control field 9781003013488
005 - DATE AND TIME OF LATEST TRANSACTION
control field 20220531132322.0
006 - FIXED-LENGTH DATA ELEMENTS--ADDITIONAL MATERIAL CHARACTERISTICS
fixed length control field m o d
008 - FIXED-LENGTH DATA ELEMENTS--GENERAL INFORMATION
fixed length control field 201104s2021 flua fo 000 0 eng d
040 ## - Cataloging Source
-- OCoLC-P
-- eng
-- rda
-- OCoLC-P
020 ## - INTERNATIONAL STANDARD BOOK NUMBER
International Standard Book Number 9781000338089
-- (e-book)
020 ## - INTERNATIONAL STANDARD BOOK NUMBER
International Standard Book Number 1000338088
020 ## - INTERNATIONAL STANDARD BOOK NUMBER
International Standard Book Number 9781003013488
-- (electronic bk.)
020 ## - INTERNATIONAL STANDARD BOOK NUMBER
International Standard Book Number 1003013481
-- (electronic bk.)
020 ## - INTERNATIONAL STANDARD BOOK NUMBER
International Standard Book Number 9781000338102
-- (electronic bk. : Mobipocket)
020 ## - INTERNATIONAL STANDARD BOOK NUMBER
International Standard Book Number 100033810X
-- (electronic bk. : Mobipocket)
020 ## - INTERNATIONAL STANDARD BOOK NUMBER
International Standard Book Number 9781000338126
-- (electronic bk. : EPUB)
020 ## - INTERNATIONAL STANDARD BOOK NUMBER
International Standard Book Number 1000338126
-- (electronic bk. : EPUB)
020 ## - INTERNATIONAL STANDARD BOOK NUMBER
Canceled/invalid ISBN 9780367820817 (hbk.)
020 ## - INTERNATIONAL STANDARD BOOK NUMBER
Canceled/invalid ISBN 9780367820183 (pbk.)
035 ## - SYSTEM CONTROL NUMBER
System control number (OCoLC)1235966968
035 ## - SYSTEM CONTROL NUMBER
System control number (OCoLC-P)1235966968
050 #4 - LIBRARY OF CONGRESS CALL NUMBER
Classification number QA76.64
072 #7 -
-- COM
-- 000000
-- bisacsh
072 #7 -
-- COM
-- 012040
-- bisacsh
072 #7 -
-- COM
-- 014000
-- bisacsh
072 #7 -
-- UB
-- bicssc
082 04 -
-- 005.117
-- 23
100 1# - MAIN ENTRY--PERSONAL NAME
Personal name Dingle, Adair,
Relator term author.
245 10 - TITLE STATEMENT
Title Object-oriented design choices
Statement of responsibility, etc. Adair Dingle.
264 #1 -
-- Boca Raton :
-- Chapman & Hall/CRC,
-- 2021.
300 ## - PHYSICAL DESCRIPTION
Extent 1 online resource
Other physical details illustrations (black and white)
336 ## -
-- text
-- txt
-- rdacontent
337 ## -
-- computer
-- c
-- rdamedia
338 ## -
-- online resource
-- cr
-- rdacarrier
520 ## -
-- Do modern programming languages, IDEs, and libraries make coding easy? Maybe, but coding is not design. Large-scale or expensive apps clearly require evaluation of design choices. Still, software design directly impacts code reuse and longevity even for small-scale apps with limited overhead. This text evaluates and contrasts common object-oriented designs. A given problem may have many solutions. A developer may employ different design techniques - composition, inheritance, dependency injection, delegation, etc. - to solve a particular problem. A skilled developer can determine the costs and benefits of different design responses, even amid competing concerns. A responsible developer documents design choices as a contract with the client, delineating external and internal responsibilities. To promote effective software design, this book examines contractual, object-oriented designs for immediate and sustained use as well as code reuse. The intent of identifying design variants is to recognize and manage conflicting goals such as short versus long-term utility, stability versus flexibility, and storage versus computation. Many examples are given to evaluate and contrast different solutions and to compare C# and C++ effects. No one has a crystal ball; however, deliberate design promotes software longevity. With the prominence of legacy OO code, a clear understanding of different object-oriented designs is essential. Design questions abound. Is code reuse better with inheritance or composition? Should composition rely on complete encapsulation? Design choices impact flexibility, efficiency, stability, longevity, and reuse, yet compilers do not enforce design and syntax does not necessarily illustrate design. Through deliberate design, or redesign when refactoring, developers construct sustainable, efficient code.
588 ## -
-- OCLC-licensed vendor bibliographic record.
650 #0 - SUBJECT ADDED ENTRY--TOPICAL TERM
Topical term or geographic name as entry element Object-oriented programming (Computer science)
650 #0 - SUBJECT ADDED ENTRY--TOPICAL TERM
Topical term or geographic name as entry element Computer software
General subdivision Development.
650 #7 - SUBJECT ADDED ENTRY--TOPICAL TERM
Topical term or geographic name as entry element COMPUTERS / General
Source of heading or term bisacsh
650 #7 - SUBJECT ADDED ENTRY--TOPICAL TERM
Topical term or geographic name as entry element COMPUTERS / Computer Graphics / Game Programming & Design
Source of heading or term bisacsh
650 #7 - SUBJECT ADDED ENTRY--TOPICAL TERM
Topical term or geographic name as entry element COMPUTERS / Computer Science
Source of heading or term bisacsh
856 40 -
-- Taylor & Francis
-- https://www.taylorfrancis.com/books/9781003013488
856 42 -
-- OCLC metadata license agreement
-- http://www.oclc.org/content/dam/oclc/forms/terms/vbrl-201703.pdf

No items available.

Technical University of Mombasa
Tom Mboya Street, Tudor 90420-80100 , Mombasa Kenya
Tel: (254)41-2492222/3 Fax: 2490571