Muutke küpsiste eelistusi

E-raamat: Software Engineering Best Practices: Lessons from Successful Projects in the Top Companies

  • Formaat: 608 pages
  • Ilmumisaeg: 05-Nov-2009
  • Kirjastus: Osborne/McGraw-Hill
  • Keel: eng
  • ISBN-13: 9780071621625
Teised raamatud teemal:
  • Formaat - PDF+DRM
  • Hind: 90,79 €*
  • * hind on lõplik, st. muud allahindlused enam ei rakendu
  • Lisa ostukorvi
  • Lisa soovinimekirja
  • See e-raamat on mõeldud ainult isiklikuks kasutamiseks. E-raamatuid ei saa tagastada.
  • Formaat: 608 pages
  • Ilmumisaeg: 05-Nov-2009
  • Kirjastus: Osborne/McGraw-Hill
  • Keel: eng
  • ISBN-13: 9780071621625
Teised raamatud teemal:

DRM piirangud

  • Kopeerimine (copy/paste):

    ei ole lubatud

  • Printimine:

    ei ole lubatud

  • Kasutamine:

    Digitaalõiguste kaitse (DRM)
    Kirjastus on väljastanud selle e-raamatu krüpteeritud kujul, mis tähendab, et selle lugemiseks peate installeerima spetsiaalse tarkvara. Samuti peate looma endale  Adobe ID Rohkem infot siin. E-raamatut saab lugeda 1 kasutaja ning alla laadida kuni 6'de seadmesse (kõik autoriseeritud sama Adobe ID-ga).

    Vajalik tarkvara
    Mobiilsetes seadmetes (telefon või tahvelarvuti) lugemiseks peate installeerima selle tasuta rakenduse: PocketBook Reader (iOS / Android)

    PC või Mac seadmes lugemiseks peate installima Adobe Digital Editionsi (Seeon tasuta rakendus spetsiaalselt e-raamatute lugemiseks. Seda ei tohi segamini ajada Adober Reader'iga, mis tõenäoliselt on juba teie arvutisse installeeritud )

    Seda e-raamatut ei saa lugeda Amazon Kindle's. 

Jones, who has worked in programming technology and software research and has written many other books on software, explains the need for better measurements, benchmarks, quality control, and security in software engineering. Drawing from observations of projects in about 600 companies, he shows how a combination of metrics and measurement can demonstrate effectiveness of software engineering methods, and presents 50 best practices for development, maintenance, management, sociology, risk analysis, governance, and renovation of legacy applications. He then explores software engineering 40 years in the future and technical topics such as the role of data mining, intelligent agents and search-bots, and other improvements. He also discusses ways for learning new software engineering information, curricula for engineers and personnel, different kinds of team organization and specialization, project management, requirements and design issues, programming and code development, and measuring programming productivity and quality levels. He includes material on dealing with layoffs and downsizing, the changing economic balance between the US and other countries, and the economics of software during a recessionary period. Annotation ©2010 Book News, Inc., Portland, OR (booknews.com)

Proven techniques for software engineering success

This in-depth volume examines software engineering topics that are not covered elsewhere: the question of why software engineering has developed more than 2,500 programming languages; problems with traditional definitions of software quality; and problems with common metrics, "lines of code," and "cost per defect" that violate standard economic assumptions. The book notes that a majority of "new" projects are actually replacements for legacy applications, illustrating that data mining for lost requirements should be a standard practice. Difficult social engineering issues are also covered, such as how to minimize harm from layoffs and downsizing.

Software Engineering Best Practices explains how to effectively plan, size, schedule, and manage software projects of all types, using solid engineering procedures. It details proven methods, from initial requirements through 20 years of maintenance. Portions of the book have been extensively reviewed by key engineers from top companies, including IBM, Microsoft, Unisys, and Sony.

  • Manage Agile, hierarchical, matrix, and virtual software development teams
  • Optimize software quality using JAD, OFD, TSP, static analysis, inspections, and other methods with proven success records
  • Use high-speed functional metrics to assess productivity and quality levels
  • Plan optimal organization, from small teams through more than 1,000 personnel
Chapter 1. Introduction and Definitions of Software Best Practices;Chapter 2. Overview of 50 Software Best Practices;Chapter 3. A Preview of Software Development and Maintenance in 2049;Chapter 4. How Software Personnel Learn New Skills;Chapter 5. Software Team Organization and Specialization;Chapter 6. Project Management and Software Engineering;Chapter 7. Requirements, Business Analysis, Architecture, Enterprise Architecture, and Design;Chapter 8. Programming and Code Development;Chapter 9. Software Quality: The Key to Successful Software Engineering;Index
McGraw-Hill authors represent the leading experts in their fields and are dedicated to improving the lives, careers, and interests of readers worldwide