Buy Used
$4.00
FREE Shipping on orders over $35.
Condition: Used: Good
Comment: This is a used book and might have some creases and minor marks from reading. You can use your prime account and this item qualifies for free shipping!
Have one to sell? Sell on Amazon
Flip to back Flip to front
Listen Playing... Paused   You're listening to a sample of the Audible audio edition.
Learn more
See this image

Software Maintenance Guidebook Hardcover – June, 1981


See all 2 formats and editions Hide other formats and editions
Amazon Price New from Used from
Hardcover
"Please retry"
$102.02 $0.01
Unknown Binding
"Please retry"
Best%20Books%20of%202014
NO_CONTENT_IN_FEATURE

Hero Quick Promo
Year-End Kindle Daily Deals
Load your library with great books for $2.99 or less each, today only. Learn more

Product Details

  • Hardcover: 193 pages
  • Publisher: Prentice Hall (June 1981)
  • Language: English
  • ISBN-10: 0138217289
  • ISBN-13: 978-0138217280
  • Product Dimensions: 8.9 x 5.9 x 0.6 inches
  • Shipping Weight: 12.8 ounces
  • Average Customer Review: 5.0 out of 5 stars  See all reviews (1 customer review)
  • Amazon Best Sellers Rank: #5,554,438 in Books (See Top 100 in Books)

Customer Reviews

5.0 out of 5 stars
5 star
1
4 star
0
3 star
0
2 star
0
1 star
0
See the customer review
Share your thoughts with other customers

Most Helpful Customer Reviews

Format: Hardcover
Explains character traits that are ideal for a maintenance programmer such as flexibility, broad background, patience, self-motivation, responsibility, humility, innovation, and historian. Compares and contrasts the styles used for programming in languages such as assembly, Fortran, COBOL, and ALGOL. Enumerates tools for software development and proposes a "supercompiler" and "programmer's workbench". These concepts are similar to the modern interactive development environment (IDE). Excellent discussion of preventing maintenance using techniques such as modularity, clustering, program structure, data structure, parameterization, data communication, defensive programming, programming standards, and documentation. Defines the content and structure of good internal documentation for use in the maintenance phase of the life cycle. This outstanding book is still relevant and will remain relevant.
Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again