|
 By adopting the processes and concepts outlined in this book, readers
will have everything they need to implement and execute a sound SCM
organization. Whether one is a project manager with responsibility for
CM, a CM manager, or a CM team lead, this book would be beneficial.
Perhaps the best feature of this book is that it is life-cycle
oriented. For each phase of the generalized life cycle it identifies
the relevant SCM activities and the SCM milestones.
- Software Quality Professional
|
|
| Great code doesn't just function: it clearly
and consistently communicates your intentions, allowing other
programmers to understand your code, rely on it, and modify it with
confidence. But great code doesn't just happen. It is the outcome of
hundreds of small but critical decisions programmers make every single
day. Now, legendary software innovator Kent Beck-known worldwide for
creating Extreme Programming and pioneering software patterns and
test-driven development-focuses on these critical decisions, unearthing
powerful "implementation patterns" for writing programs that are
simpler, clearer, better organized, and more cost effective.
|
 Creating secure code requires more than just
good intentions. Programmers need to know that their code will be safe
in an almost infinite number of scenarios and configurations. Static
source code analysis gives users the ability to review their work with
a fine-toothed comb and uncover the kinds of errors that lead directly
to security vulnerabilities. Now, there's a complete guide to static
analysis: how it works, how to integrate it into the software
development processes, and how to make the most of it during security
code review. Static analysis experts Brian Chess and Jacob West look at
the most common types of security defects that occur today. They
illustrate main points using Java and C code examples taken from
real-world security incidents, showing how coding errors are exploited,
how they could have been prevented, and how static analysis can rapidly
uncover similar mistakes. This book is for everyone concerned with
building more secure software: developers, security engineers,
analysts, and testers.
|
Written in an engaging style and relevant for any software analyst or designer, Mastering the Requirements Process
The heart of this book is the authors'
Volere Requirements Process Model, a step-by-step guide to gathering
your requisites. Throughout this book, the authors use this process to
explicate a single case study--a system for a municipality that will
optimize the de-icing of roadways during snowy weather. Along the way,
the book provides a solid guide to identifying and refining
requirements, both functional and nonfunctional (such as performance
and ease of use).
provides a powerful and useful guide to defining more complete software
requirements that lead to better software overall. It's also filled
with innovative advice.
|
| This practical reference discusses why essential processes so often
fail to deliver quality industrial software to meet user needs. It
describes how to integrate processes and metrics to ensure easier and
more effective enterprise software development. Its metrics-driven
approach guides practitioners at every step of the life cycle and helps
them analyze, design, implement, test and deploy solutions with greater
confidence, purpose and sensitivity to evolving business needs.
|
Software Engineering with Microsoft Visual Studio Team System
is written for any software team that is considering running a software
project using Visual Studio Team System (VSTS), or evaluating modern
software development practices for its use.
It
is about the value-up paradigm of software development, which forms the
basis of VSTS: its guiding ideas, why they are presented in certain
ways, and how they fit into the process of managing the software
lifecycle. This book is the next best thing to having an onsite coach
who can lead the team through a consistent set of processes.
|
| For any software developer who has spent days in "integration hell," cobbling together myriad software components, Continuous Integration: Improving Software Quality and Reducing Risk
illustrates how to transform integration from a necessary evil into an
everyday part of the development process. The key, as the authors show,
is to integrate regularly and often using continuous integration (CI)
practices and techniques.
|
|
|
|
|
<< Start < Prev 1 2 Next > End >>
|
|
Page 1 of 2 |
