• No se han encontrado resultados

Software engineering: Theory and practice . 2nd Edition. Shari Lawrence Pfleeger. Prentice Hall, 2001

N/A
N/A
Protected

Academic year: 2017

Share "Software engineering: Theory and practice . 2nd Edition. Shari Lawrence Pfleeger. Prentice Hall, 2001"

Copied!
1
0
0

Texto completo

(1)

Book Review:

Software Engineering: Theory and Practice, 2nd Edition

Shari Lawrence Pfleeger

Prentice Hall, 2001

ISBN 0130290491

A book that describes and applies Software Engineering methods according to the state of the art of the subject matter; it is integrated with a proper exemplification and evolves as each topic is introduced. The material is designed for undergraduates of the initial course of Software Engineering and/or professionals who wish to improve their techniques for the development of software systems.

The thematic presentation of the text might be one of its strongest points. Some of the aspects of this work, which, in the judgment of this reviewer, outstands over others dealing with the same subject matter, are described below:

p The integration of metrics and measurement concepts as part of the strategy of Software Engineering. Some bibliography considers the topic as a separate area or discipline, while this work shows how to incorporate the quantitative assessment in daily software developments and how to improve, from this assessment, such developments.

p The treatment deserved by the initial planning and management of a software project is faced interestingly and in deep. Topics such as risk and cost management are assessed and presented according to desired expectations of a book which introduces the student to the area of Software Engineering. In addition, the exemplification attempts to clarify the application of such concepts.

p Software Reutilization and Quality are conceptually developed within each branch of interest in the subject matter. In this way, and alike some other bibliographies, it does not present a chapter in which these topics are encompassed, but it presents them for each stage of the software product development; which, all in all, renders a better understanding of the topic.

With respect to the development of the material of the book, it is in itself divided in three sections:

p Initial and basic concepts of Software Engineering. It encompasses concepts such as a project management (estimation, planning, risk analysis, software configuration management, etc.) and modeling techniques. p Software development and maintenance, making it independent of the previously defined and presented

construction model. With development, the initial decision on requirements, the solution design, the concepts related to codification, and the final delivery to the client are covered, embracing all the stages of software testing.

p The third section focuses on the evaluation and continuos improvement applicable to software development. Special emphasis is made on the quality of both the final product and the process which leads to such development.

Finally, the book has an associated web page, in which a large number of examples of mostly real problems are presented, discussed and solved. Each chapter presents a revision questionnaire and exercises that the reader can solve. The referenced bibliography is good, complete and updated.

Rodolfo Bertone [email protected]

JCS&T Vol. 5 No. 1 April 2005

Referencias

Documento similar

 SecurityRules2CubePermissions and SecurityRules2Dimension- Permissions transformations, which process more complex security rules defined in the conceptual model by using

Keywords: context change, evidence in software process, Variant-Rich Processes, tailoring management, process institutionalization, project management.. 1

However, for early steps of the development (stages on which our proposal is focussed) where all the system requirements are not com- pletely stated (and the already stated

It consists of the following steps: (a) to extend the software models used for development with annotations describing dependability properties; (b) to transform automatically

propose a UML profile (namely DAM, C6 ), as a specialization of the OMG stan- dard [UML-MARTE 2009], to support the dependability analysis of UML-based software systems, in the

We reproduced these experiments using our performance model, which meant to put as many tokens as users in places users and p userDevice of the GSPN, so to also match one user to

The characteristics of interest are defined as attributes of NFP or dependability basic types (see e.g., attributes associated to DaComponent and DaService), so they can

L´ opez-Grao, J., Merseguer, J., Campos, J.: From UML activity diagrams to stochastic Petri nets: Application to software performance engineering. G´ omez Mart´ınez, E., Merseguer,