Book Image

Visual SourceSafe 2005 Software Configuration Management in Practice

Book Image

Visual SourceSafe 2005 Software Configuration Management in Practice

Overview of this book

Why is Software Configuration Management important?Software Configuration Management (SCM) is the discipline of managing the building and modification of software through techniques including source-code control, revision control, object-build tracking, and release construction. SCM involves identifying the configuration of the software at given points in time, systematically controlling changes to the configuration, and maintaining the integrity and traceability of the configuration throughout the software development lifecycle.Software Configuration Management is one of the first skills a serious developer should master, after becoming proficient with his or her development tools of choice. Unfortunately, this does not always happen because the subject of SCM is not commonly taught in either academic or company training.When developing software, you need to have a manageable team development effort, track and maintain the history of your projects, sustain parallel development on multiple product versions, fix bugs, and release service packs while further developing the application. This is where the concepts of Software Configuration Management come into play; SCM is about getting the job done safer, faster, and better.Visual SourceSafe has a long history behind it. The previous versions were either loved for their ease of use and integration with other Microsoft products, or hated because the headaches caused by using them improperly. This book will help you to avoid such problems.
Table of Contents (15 chapters)
Visual SourceSafe 2005 Software Configuration Management in Practice
Credits
About the Author
About the Reviewers
Preface

Testing


Testing is the process of identifying the correctness, completeness, security, and quality of software and it is very important in ensuring its quality. I will only scratch its surface as it is a subject for an entire book by itself.

There are two types of tests, depending on how we look at the software being tested:

  • White-box testing

  • Black-box testing

In white-box testing, we look from inside the tested software having an intimate knowledge of the source code.

In black-box testing, we look from outside the tested software dealing only with inputs and outputs with no knowledge of the internal structure.

Code Analysis

Code analysis is the analysis of software that is performed without actually running it, by looking only at its structure and/or source code. Software is analyzed for compliance with design guidelines and to locate potentially vulnerable code.

In the .NET world, one of the tools for code analysis is FxCop. FxCop checks .NET managed code assemblies for conformance to...