Picture 1 of 1

Gallery
Picture 1 of 1

Have one to sell?
A Discipline for Software Engineering by Watts S Humphrey: Used
US $19.45
ApproximatelyS$ 24.95
Condition:
Good
A book that has been read but is in good condition. Very minimal damage to the cover including scuff marks, but no holes or tears. The dust jacket for hard covers may not be included. Binding has minimal wear. The majority of pages are undamaged with minimal creasing or tearing, minimal pencil underlining of text, no highlighting of text, no writing in margins. No missing pages.
Oops! Looks like we're having trouble connecting to our server.
Refresh your browser window to try again.
Shipping:
Free Standard Shipping.
Located in: Sparks, Nevada, United States
Delivery:
Estimated between Sat, 27 Sep and Fri, 3 Oct to 94104
Returns:
30 days return. Buyer pays for return shipping. If you use an eBay shipping label, it will be deducted from your refund amount.
Coverage:
Read item description or contact seller for details. See all detailsSee all details on coverage
(Not eligible for eBay purchase protection programmes)
Seller assumes all responsibility for this listing.
eBay item number:364027382231
Item specifics
- Condition
- Book Title
- A Discipline for Software Engineering
- Publication Date
- 1994-12-31
- Pages
- 789
- ISBN
- 9780201546101
About this product
Product Identifiers
Publisher
Addison Wesley Professional
ISBN-10
0201546108
ISBN-13
9780201546101
eBay Product ID (ePID)
49190
Product Key Features
Number of Pages
816 Pages
Publication Name
Discipline for Software Engineering
Language
English
Publication Year
1994
Subject
Software Development & Engineering / General
Type
Textbook
Subject Area
Computers
Series
Sei Series in Software Engineering Ser.
Format
Hardcover
Dimensions
Item Height
1.3 in
Item Weight
41.9 Oz
Item Length
6.7 in
Item Width
9.5 in
Additional Product Features
Intended Audience
Scholarly & Professional
LCCN
93-041673
Dewey Edition
20
TitleLeading
A
Dewey Decimal
005.1
Table Of Content
1. The Personal Process Strategy. The Logic for a Software Engineering Discipline.What is a Software Process?Process Maturity.Your Personal Responsibilities.The Personal Software Process (PSP) Strategy.The Logic for the PSP.Productivity and the PSP.Caveats. 2. The Baseline Personal Process. The Baseline Process.Why Forms are Helpful.The PSP Process Elements.The PSPO Process.PSPO Measures.Time Recording Log.Defect Recording Log.PSPO Project Plan Summary.Customizing the Initial Process 3. Planning I: The Planning Process. Why Make Plans.What is a Plan.Contents of a Software Plan.Planning a Software Project.Producing a Quality Plan. 4. Planning II: Measuring Software Size. Size Measures.A Size Measurement Framework.Establishing a Counting Standard.Using LOC Counts.Reuse Considerations.Line of Code Accounting.Calculating Productivity.LOC Counters. 5. Planning III: Estimating Software Size. Background.Popular Estimating Methods.Proxy-based Estimating.The PROBE Size Estimating Method.Object Categories.Estimating Considerations. 6. Planning IV: Planning. Resource Planning.Estimating Development Time.Estimating Task Time.Combining Multiple Estimates.Using Multiple Regression.Schedule Estimating.Earned Value Tracking.Estimating Accuracy. 7. Measurement In The Personal Software Process. Measurement Overview.Fundamental Process Measures.Goal-Question-Metric Paradigm.General PSP Objectives, Goals, and Questions.A GQM Example .Gathering Data.The Impact of Data Gathering.Establishing a Baseline for Your Personal Process. 8. Design and Code Reviews. What are Reviews?Why Review Programs.Personal Reviews.Review Principles.Separate Design and Code Reviews.Design Review Principles.Review Measures.Checklists.Reviewing before or after You Compile.The Relationship between Reviews and Inspections. 9. Software Quality Management. What is Software Quality'.The Economics of Software Quality.Developing a Quality Strategy.Process Benchmarking.Yield Management.Defect Removal Strategies.Defect Prevention Strategies. 10. Software Design. The Design Process.Design Quality.Structuring the Design Process.Design Notation.Design Templates.The Functional Specification Template.The State Specification Template.The Logic Specification Template.The Operational Scenario Template.Using Templates in DesignDesign Guidelines. 11. Scaling Up The Personal Software Process. Using Abstractions.The Stages of Product Size.Developing Large-scale Programs.A Potential Problem with Abstractions.The Development Strategy. 12. Design Verification. Selecting Verification Methods.Design Standards.Verification Methods.Verifying the Object State Machine.Program Tracing.Verifying Program Correctness.Comments on Verification Methods. 13. Defining the Software Process. Why Define Processes.Software Process Basics.Process Definition.Defining Process Phases.Process Development Considerations.Process Evolution.The Process-development Process. 14. Using the Personal Software Process. Making Personal Commitments.Using the PSP in an Organization.The Personal Costs of a PSP.The Personal Benefits of a PSP.Coaching.The Responsible Software Professional.Your Future in Software Engineering. 0201546108T04062001
Synopsis
This book from Watts Humphrey broadens his disciplined approach to software engineering. In his earlier book, Managing the Software Process, Humphrey developed concrete methods for managing software development and maintenance. These methods, now commonly practiced, provide programmers and managers specific steps for evaluating and improving their software capabilities. In this book, he scales down those methods to a personal level, helping software practitioners develop the skills and habits they need to plan, track, and analyze large and complex projects more carefully and successfully., Designed to help individual programmers develop software more effectively and successfully, this book presents a scaled-down version of Humphrey's popular methods for managing the software process. It: presents concepts and methods for a disciplined software engineering process for individual programmers, following the Capability Maturity Model (CMM); scales down industrial practices for planning, tracking, analysis and defect management to fit the needs of small-scale program development; and provides readers with a solid base for work in industry on much larger projects.
LC Classification Number
QA76.758.H857 1995
Item description from the seller
Seller feedback (527,154)
- eBay 自動留下信用評價- Feedback left by buyer.Past month訂單成功完成 — 物品享追蹤服務且準時送達
- 0***s (249)- Feedback left by buyer.Past monthVerified purchaseIn Excellent Condition And Played Well. Was Wonderful Watching This Oldie But Goodle Once Again. Thank You For This Addition To My Collection
- eBay 自動留下信用評價- Feedback left by buyer.Past month訂單成功完成 — 物品享追蹤服務且準時送達