Implementing the IEEE Software Engineering Standards is a practical and professional guide to implementing the IEEE Software Engineering standards in your software development process. There are 39 complex standards involved, some more critical than others. This book explains where to start, which standards to implement first, and how to integrate them into your current software development process. The book presents a realistic Software Life-Cycle Model to complement the standards and aid development. One of the book’s biggest benefits is that it helps software engineers reconcile some latest “best practices” such as rapid prototyping and use of CASE tools with use of the standards.

There is more to “object-oriented” than application programming. Object-oriented methods have revolutionized the way analysts, designers, software engineers, project managers, and tool builders construct entire software systems.

Object-Oriented System Development will help you to better understand the role of analysis and design in the object-oriented development process. Rather than subscribing to a particular object-oriented method, this book gives step-by-step instructions on how to put key object-oriented concepts to work in software construction. Many examples, including a full banking system, are developed throughout the book to illustrate the process of object-oriented software development from analysis, through design, and into implementation.

Although geared to software professionals involved in the development of medium, large, and distributed systems, Object-Oriented System Development is equally valuable to anyone who wants to gain a detailed technical perspective on the object-oriented software development process.

Aimed at developers and IT managers alike, Software Project Management in Practice
offers an invaluable guide to using lightweight software processes in
real projects. Filled with sample documents, this book can benefit any
organization seeking to improve the ways it manages software.

In an
era of ever tighter schedules, implementing a serious software process
becomes even more difficult. This book ventures a simple argument: that
the techniques for software process management used by InfoSys (a
company with a “mature” software process) can be applied to other
organizations. Packed with sample documents drawn from real projects,
this book is also notable for its clear presentation and the absence of
the theoretical and jargon-laden prose that can be found in many
software engineering texts.

The author first looks at how to
assess a company’s software process using the Capability Maturity Model
(CMM) and other schemes. Surprisingly, the tools at InfoSys (which earn
high CMM marks) are not fancy case tools, but databases, spreadsheets,
and Microsoft Project files. Its software process database, for
example, allows new projects to reuse existing documents and expertise.
After an overview of the modified waterfall model software process used
at InfoSys, the author looks at techniques for estimating the size and
scope of projects. Then it’s on to quality planning. A consistent theme
here is that metrics and statistical process control (SPC) should be
used to track defects. The book then covers risk assessment and the
structure of teams. A standout section on configuration management
outlines the role for preserving builds and project documents at each
stage of the game.

Later sections examine the actual
implementation and deployment of software. The author’s argument for
peer review of code is a strong one. He details strategies for running
design and code reviews (if even by a single person) to catch defects
and improper designs, as well as tips for overcoming resistance to such
practices.

Sample defect tracking and status for projects also
gets its due. Sample documents (using spreadsheets and even the layout
of disk directories) to store project information show that a simple
approach can yield productive results. The author then shows how to
analyze the patterns of defects in software, including how to use
statistical techniques to spot out-of-control projects. The book closes
with the ways in which a project postmortem (or “project closure
analysis”) can be used to spot what went wrong and to improve things
the next time around.

As a co-founder of Symbian and former executive of Psion Software, David Wood has been actively involved in well over 100 smartphone development projects worldwide. Over the time spent on these projects, he has come to understand the key issues which determine the difference between successful and unsuccessful projects for Symbian OS. This book highlights and explains: How to tame the awesome inner complexity of smartphone technology Optimal project team organisation, combining agility and reliability The design and the philosophy behind key features of Symbian OS The potential trouble spots of smartphone integration, testing, and optimisation How to receive the full benefit of the diverse skills in the extensive Symbian partner ecosystem The methods that are most likely to deliver commercial success when using Symbian OS The wider significance of Symbian OS skills and expertise in the evolving mobile marketplace The particular importance of software leaders in bringing breakthrough smartphone products to the market

by Theo Pavlidis

Hardcover: 384 pages

Publisher: Springer; 1 edition (April 1, 1999)

Language: English

ISBN: 0306460653

Management of the Object-Oriented Development Process consists of a series of high-level discussions on technical and managerial issues related to object-oriented development. This book introduces object-oriented development techniques, including modeling languages, programming languages, reusable patterns and software development processes. It discusses the ongoing trends of object-oriented development, including emerging e-business development frameworks, executable UML and requirements engineering. There is also a focus managerial issues such as project management and software evaluation, and how to manage the paradigm shift from structured to object-oriented development. Management of the Object-Oriented Development Process offers systems developers, project managers, information systems students and researchers technical skills as well as strategic insights on how to manage
software projects, deploy object-oriented software development processes, understand the current trends and make the transition from structured to object-oriented techniques.