The project manager's guide to software engineering's best practices / (Record no. 59712)
[ view plain ]
| 000 -LEADER | |
|---|---|
| fixed length control field | 05472nam a2201189 i 4500 |
| 001 - CONTROL NUMBER | |
| control field | 5989224 |
| 005 - DATE AND TIME OF LATEST TRANSACTION | |
| control field | 20200421114120.0 |
| 008 - FIXED-LENGTH DATA ELEMENTS--GENERAL INFORMATION | |
| fixed length control field | 151221s2011 nju ob 001 eng d |
| 020 ## - INTERNATIONAL STANDARD BOOK NUMBER | |
| ISBN | 9781118156629 |
| -- | electronic |
| 020 ## - INTERNATIONAL STANDARD BOOK NUMBER | |
| ISBN | 1118156625 |
| 020 ## - INTERNATIONAL STANDARD BOOK NUMBER | |
| -- | paper |
| 020 ## - INTERNATIONAL STANDARD BOOK NUMBER | |
| -- | |
| 100 1# - AUTHOR NAME | |
| Author | Christensen, Mark J., |
| 245 14 - TITLE STATEMENT | |
| Title | The project manager's guide to software engineering's best practices / |
| 300 ## - PHYSICAL DESCRIPTION | |
| Number of Pages | 1 PDF. |
| 490 1# - SERIES STATEMENT | |
| Series statement | Practitioners |
| 505 0# - FORMATTED CONTENTS NOTE | |
| Remark 2 | Foreword.Preface.Acknowledgements.Reviewers.I: Software Systems Engineering.1. Software Systems Engineering.2. Concept of Operations.3. Software Requirements Specification.4. Software User Documentation.5. Software Verification and Validation.6. Software Maintenance.II: Process Management and Control.7. Software Life Cycle Process Management.8. Software Process Improvement.9. Software Configuration Management.10. Software Quality Assurance.11. Software Reviews.III: Project Planning and Management.12. Software Cost and Schedule.13. Software Engineering Project Management.14. Software Risk Management.15. Software Metrics.A. The Work Breakdown Structure.B. Representing Project Schedules.Index.About the Authors. |
| 520 ## - SUMMARY, ETC. | |
| Summary, etc | Since the earliest days of the computer industry, managing a software project has been a complex and demanding activity. While the technical content of software products and the technical methods used to build them have changed over time, the fundamental issues that determine the success or failure of software project have remained fairly constant. The contents of this book, together with the underlying IEEE Standards, are dedicated to helping the reader in their ongoing task to produce quality software products in a conventional manner.This book, containing all original material, is built on the proposition that the IEEE Software Engineering Standards capture many of the fundamental "best practices" of software project management. It will assist the reader in successfully applying those standards to their projects and their organization. To meet this goal, the authors discuss and elaborate on the standards covering these three key management areas:. Software systems engineering. Process for developing software products. Planning and control of software project activitiesThe body of the text is correspondingly organized into three important parts: Software Systems Engineering; Process Management and Control; and Project Planning and Management. |
| 700 1# - AUTHOR 2 | |
| Author 2 | Thayer, Richard H. |
| 856 42 - ELECTRONIC LOCATION AND ACCESS | |
| Uniform Resource Identifier | http://ieeexplore.ieee.org/xpl/bkabstractplus.jsp?bkn=5989224 |
| 942 ## - ADDED ENTRY ELEMENTS (KOHA) | |
| Koha item type | eBooks |
| 264 #1 - | |
| -- | [Los Alamitos, California] : |
| -- | IEEE Computer Society, |
| -- | 2001 |
| 264 #2 - | |
| -- | [Piscataqay, New Jersey] : |
| -- | IEEE Xplore, |
| -- | [2011] |
| 336 ## - | |
| -- | text |
| -- | rdacontent |
| 337 ## - | |
| -- | electronic |
| -- | isbdmedia |
| 338 ## - | |
| -- | online resource |
| -- | rdacarrier |
| 588 ## - | |
| -- | Description based on PDF viewed 12/21/2015. |
| 650 #0 - SUBJECT ADDED ENTRY--SUBJECT 1 | |
| -- | Software engineering. |
| 695 ## - | |
| -- | Accreditation |
| 695 ## - | |
| -- | Aerospace electronics |
| 695 ## - | |
| -- | Air safety |
| 695 ## - | |
| -- | Aircraft |
| 695 ## - | |
| -- | Biographies |
| 695 ## - | |
| -- | Business |
| 695 ## - | |
| -- | Capability maturity model |
| 695 ## - | |
| -- | Context |
| 695 ## - | |
| -- | Contracts |
| 695 ## - | |
| -- | Documentation |
| 695 ## - | |
| -- | Electric breakdown |
| 695 ## - | |
| -- | Electronic equipment |
| 695 ## - | |
| -- | Equations |
| 695 ## - | |
| -- | Estimation |
| 695 ## - | |
| -- | Guidelines |
| 695 ## - | |
| -- | Hardware |
| 695 ## - | |
| -- | IEEE standards |
| 695 ## - | |
| -- | Indexes |
| 695 ## - | |
| -- | Industries |
| 695 ## - | |
| -- | Inspection |
| 695 ## - | |
| -- | Maintenance engineering |
| 695 ## - | |
| -- | Manuals |
| 695 ## - | |
| -- | Manufacturing |
| 695 ## - | |
| -- | Marine vehicles |
| 695 ## - | |
| -- | Materials |
| 695 ## - | |
| -- | Measurement |
| 695 ## - | |
| -- | Modeling |
| 695 ## - | |
| -- | Monitoring |
| 695 ## - | |
| -- | Organizations |
| 695 ## - | |
| -- | Personnel |
| 695 ## - | |
| -- | Planning |
| 695 ## - | |
| -- | Process control |
| 695 ## - | |
| -- | Production |
| 695 ## - | |
| -- | Productivity |
| 695 ## - | |
| -- | Programming |
| 695 ## - | |
| -- | Project management |
| 695 ## - | |
| -- | Proposals |
| 695 ## - | |
| -- | Radar |
| 695 ## - | |
| -- | Risk management |
| 695 ## - | |
| -- | Schedules |
| 695 ## - | |
| -- | Scheduling |
| 695 ## - | |
| -- | Software |
| 695 ## - | |
| -- | Software engineering |
| 695 ## - | |
| -- | Software maintenance |
| 695 ## - | |
| -- | Software metrics |
| 695 ## - | |
| -- | Software quality |
| 695 ## - | |
| -- | Software reliability |
| 695 ## - | |
| -- | Software reviews |
| 695 ## - | |
| -- | Software systems |
| 695 ## - | |
| -- | Standards organizations |
| 695 ## - | |
| -- | Systematics |
| 695 ## - | |
| -- | Systems engineering and theory |
| 695 ## - | |
| -- | Terminology |
| 695 ## - | |
| -- | Training |
| 695 ## - | |
| -- | Transforms |
| 695 ## - | |
| -- | Unified modeling language |
No items available.