Overview of software maintenance; Why maintenance is expensive; Evolution of software processes and models; A recommended sofwate maintenance process; Pre-delivery software maintenance activities; Planning, parts I & II: the maintenance concept and the maintenance plan; Planning, part III: resources; Transition; Transition experiences, part I; Transition experiences, part II; Setting up the software maintenance organization; Tools and environment; Software maintenance metrics; Software maintenance metrics experiences; Maintainability; Sofwtare maintenance management; Education and training; Impact of object oriented technology on software maintenance; Software maintenance resources; The future of software maintenance; Glossary; Bibliography; Index.
Software systems now invade every area of daily living. Yet, we still struggle to build systems we can really rely on. If we want to work with software systems at any level, we need to get to grips with the way software evolves. This book will equip the reader with a sound understanding of maintenance and how it affects all levels of the software evolution process.
Stereotypes portray software engineers as a reckless lot, and stereotypes paint software configuration management (SCM) devotees as inflexible. Based on these impressions, it is no wonder that projects can be riddled with tension! The truth probably lies somewhere in between these stereotypes, and this book shows how proven SCM practices can foster a healthy team-oriented culture that produces better software. The authors show that workflow, when properly managed, can avert delays, morale problems, and cost overruns. A patterns approach (proven solutions to recurring problems) is outlined so that SCM can be easily applied and successfully leveraged in small to medium sized organizations. The patterns are presented with an emphasis on practicality. The results speak for themselves: improved processes and a motivated workforce that synergize to produce better quality software.
This application-oriented book shows how to apply proven software metrics and methods to efficiently manage software development and maintenance--to help boost productivity, efficiency, and quality of software projects at every stage of the process. Detailing practical methods throughout, the book covers tips to best measure and present progress, a useful model for understanding organization limitations, possible problems in process improvement illustrated by examples, evidence of what works and what doesn't work, and more. An ideal reference for project managers and professionals responsible for process improvement.n
"A clearly written book that is a useful primer for a very complicated set of topics." --Capers Jones, Chief Scientist Emeritus, Software Productivity Research LLC Practical Software Estimation brings together today's most valuable tips, techniques, and best practices for accurately estimating software project efforts, costs, and schedules. Written by a leading expert in the field, it addresses the full spectrum of real-world challenges faced by those who must develop reliable estimates. M. A. Parthasarathy draws on the immense experience of Infosys, one of the world's largest and most respected providers of IT-enabled business solutions, to bring you the only book with detailed guidance on estimating insourced and outsourced software projects, as well as projects that blend both approaches. He demonstrates how to successfully utilize Function Point (FP) methods, the industry's leading estimation model. Then, using real case studies, he systematically identifies pitfalls that can lead to inaccurate estimates--and offers proven solutions. Coverage includes How to estimate all types of software projects, including "fresh" development, reengineering, and maintenance How to incorporate the impact of core project elements on estimates: scope, environment, experience, and tools FP analysis from start to finish: data and transaction functions, general system characteristics, and more FP methods for any platform or business function Innovative re-estimation methods to track progress How to quote RFPs and prepare contracts: fixed price, time/material, and project execution lifecycle models Alternatives to FP: Delphi, COCOMO II, and COSMIC-FFP How to choose the right estimation tools Practical Software Estimation is the definitive reference for anyone who must estimate software projects accurately: project and IT managers, individual developers, system designers, architects, executives, consultants, and outsourcers alike. List of Figures List of Tables Foreword Preface Acknowledgments Chapter 1: Introduction Chapter 2: Role of Estimation in Software Projects Chapter 3: A Study of Function Point Analysis Chapter 4: Data Functions Chapter 5: Transactional Functions Chapter 6: General System Characteristics Chapter 7: Size, Effort, and Scheduling of Projects Chapter 8: Estimation Flavors Chapter 9: A Sense of Where You Are Chapter 10: Tips, Tricks, and Traps Chapter 11: Insourcing versus Outsourcing Chapter 12: Key Factors in Software Contracts Chapter 13: Project Estimation and Costing Chapter 14: Other Estimation Methods Chapter 15: Estimation Tools Chapter 16: Estimation Case Study Appendix A: Reference Tables: Transaction Function Counts Appendix B: Reference Tables: Data Function Points Bibliography Index
Practical Support for Lean Six Sigma Software Process Definition: Using IEEE Software Engineering Standards addresses the task of meeting the specific documentation requirements in support of Lean Six Sigma. This book provides a set of templates supporting the documentation required for basic software project control and management and covers the integration of these templates for their entire product development life cycle. Find detailed documentation guidance in the form of organizational policy descriptions, integrated set of deployable document templates, artifacts required in support of assessment, organizational delineation of process documentation.
The Software Factory methodology is based on recognition of these similarities and a drive to extend the concept of "reusability" to the point where we achieve entirely automated product lines. Based on an analysis and understanding of the common features and techniques of a set of applications, a Software Factory defines a tailored, end-to-end methodology for building these applications. At the heart of the Software factory methodology is the concept of Domain Specific Languages (DSLs), which in essence are development environments specifically tailored to the set of applications in hand. It removes a certain degree of flexibility but greatly enhances productivity by removing a lot of the coding complexity (for an analogy, consider the use of the now ubiquitous drag-and-drop controls in Winforms or Visual Basic). Further, in the SF methodology, patterns, process advice, and best practices can be harvested and applied for all applications in the set. There are some good books on the theory of SF already on the market. Up until this point, a lot of these concepts were fairly theoretical and abstract.
This book provides an overview of tools and techniques used in enterprise software development, many of which are not taught in academic programs or learned on the job. This is an ideal resource containing lots of practical information and code examples that you need to master as a member of an enterprise development team. This book aggregates many of these "on the job" tools and techniques into a concise format and presents them as both discussion topics and with code examples. The reader will not only get an overview of these tools and techniques, but also several discussions concerning operational aspects of enterprise software development and how it differs from smaller development efforts. For example, in the chapter on Design Patterns and Architecture, the author describes the basics of design patterns but only highlights those that are more important in enterprise applications due to separation of duties, enterprise security, etc. The architecture discussion revolves has a similar emphasis – different teams may manage different aspects of the application’s components with little or no access to the developer. This aspect of restricted access is also mentioned in the section on logging. Theory of logging and discussions of what to log are briefly mentioned, the configuration of the logging tools is demonstrated along with a discussion of why it’s very important in an enterprise environment.
This book addresses how to meet the specific documentation requirements in support of the ISO 9001 software process definition, documentation, and improvement, which is an integral part of every software engineering effort Provides a set of templates that support the documentation required for basic software project control and management The book provides specific support for organizations that are pursuing software process improvement efforts
