Profile for Daniel Mall > Reviews

Browse

Daniel Mall's Profile

Customer Reviews: 104
Top Reviewer Ranking: 1,184,457
Helpful Votes: 464


Community Features
Review Discussion Boards
Top Reviewers

Guidelines: Learn more about the ins and outs of Your Profile.

Reviews Written by
Daniel Mall RSS Feed (San Gabriel, CA United States)
(REAL NAME)   

Show:  
Page: 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11
pixel
How to Build a Beowulf: A Guide to the Implementation and Application of PC Clusters (Scientific and Engineering Computation)
How to Build a Beowulf: A Guide to the Implementation and Application of PC Clusters (Scientific and Engineering Computation)
by Thomas Lawrence Sterling
Edition: Paperback
Price: $40.00
56 used & new from $0.01

4 of 8 people found the following review helpful
3.0 out of 5 stars Broad introduction to PC clusters, November 15, 2002
A "Beowulf" is the concept of using a network of low cost personal computers for distributed processing. The book doesn't specify a particular configuration. The author describes the three fundamental parts of a Beowulf system: node hardware, network hardware, and parallel software applications. Three chapters explain how to use the message passing interface (MPI) standard to distribute the work for a program executing on multiple nodes. An example MPI program for sorting is presented. The features of the Linux operating system are covered in Chapter 4 since Linux is a common choice for Beowulf clusters.


Object-Oriented Metrics: Measures of Complexity
Object-Oriented Metrics: Measures of Complexity
by Brian Henderson-Sellers
Edition: Paperback
Price: $62.67
38 used & new from $2.00

2 of 3 people found the following review helpful
3.0 out of 5 stars Combines practical metrics and academic theory, November 7, 2002
Research findings in the field of software measurement are thoroughly reviewed. Both traditional and object-oriented product metrics are examined. Methods for determining the mathematical validity of metrics area assessed in the chapter on "A Rigorous Approach to Metrics". Intriguing presentation of cognitive complexity models including an analysis of programming tasks, code chunks, and code landscape.


Object-Oriented Software Metrics
Object-Oriented Software Metrics
by Mark Lorenz
Edition: Paperback
Price: $70.33
47 used & new from $0.01

2 of 3 people found the following review helpful
4.0 out of 5 stars Relates metrics to quality, September 11, 2002
Defines a set of 39 metrics classified into 9 project metrics and 30 design metrics. The author explains how design metrics can be used to detect quality problems and offers recommended thresholds. Advice is provided on how to correct problems with the design and source code. A project experience database displays metrics for real projects in Smalltalk and C++. The book is relatively short at 146 pages.
The metrics covered in the text are number of scenario scripts, number of key classes, number of support classes, average number of support classes per key class, number of subsystems, average person-days per class, average number of classes per developer, number of major iterations, number of contracts completed, number of message sends, number of statements, lines of code, average method size, method complexity, number of public instance methods in a class, number of instance methods in a class, average number of instance methods per class, number of instance variables in a class, average number of instance variables per class, number of class methods in a class, number of class variables in a class, class hierarchy nesting level, number of abstract classes, use of multiple inheritance, number of methods overridden by a subclass, number of methods inherited by a subclass, number of methods added by a subclass, class cohesion, global usage, average number of parameters per method, use of friend functions, percentage function-oriented code, average number of comment lines per method, average number of commented methods, number of problem reports per class or contract, class coupling, number of times a class is reused, and number of classes/methods thrown away.


Software Architecture in Practice
Software Architecture in Practice
by Leonard J. Bass
Edition: Hardcover
59 used & new from $0.01

3 of 4 people found the following review helpful
4.0 out of 5 stars Emphasis on case studies, September 11, 2002
The authors examine 7 case studies representing 37% of the 19 chapters. "The software architecture of a program or computing system is the structure(s) of the system, which comprise software components, the externally visible properties of those components, and the relationships among them (pg 23)." Describes common structures for example module structure, conceptual or logical structure, process or coordination structure, physical structure, uses structure, calls structure, data flow, control flow, and class structure. Explains how choosing architecture influences the achievement of quality attributes. Illustrates architectural styles such as batch sequential, pipes & filters, event systems, repository, virtual machine, and object oriented.


AntiPatterns in Project Management
AntiPatterns in Project Management
by William J. Brown
Edition: Hardcover
36 used & new from $0.01

4 of 6 people found the following review helpful
2.0 out of 5 stars Boring, June 19, 2002
This book is dull compared to the first book in the series, "AntiPatterns: Refactoring Software, Architectures, and Projects in Crisis". The authors take a reactive instead of proactive approach to project management. Read the four page antipattern synopsis in appendix B. The rest of the book regurgitates these items in expanded form. The text concentrates on project management problems and offers little in the solutions section. The antipattern named "standards" was helpful, however the material was duplicated from James Moore's book "Software Engineering Standards: A User's Roadmap".


Software Architecture: Perspectives on an Emerging Discipline
Software Architecture: Perspectives on an Emerging Discipline
by Mary Shaw
Edition: Paperback
Price: $72.59
46 used & new from $0.49

11 of 16 people found the following review helpful
3.0 out of 5 stars Architectural paradigms and research topics, June 4, 2002
This book is often cited as one of the seminal references on software architecture. The first chapter explains how software architecture fits into the developing field of software engineering. The second chapter illustrates common architectural styles such as pipes and filters, object-oriented organization, event-based invocation, layered systems, repositories, interpreters, process control, distributed process, main program/subroutine, blackboard, and state transition. Case studies are used to compare and contrast the selection of different architectural solutions. The case studies are key word in context, instrumentation software, mobile robotics, cruise control, three vignettes using mixed styles, and shared information systems. The final half of the book is focused on academic research such as quantified design space, formal models, formal specifications, Z notation, connector models, automated case tools, Wright Model of architectural description, and education of software architects.


The Interpretation of Object-Oriented Programming Languages
The Interpretation of Object-Oriented Programming Languages
by I. Craig
Edition: Hardcover
42 used & new from $5.50

4.0 out of 5 stars Refreshing conceptual analysis, June 3, 2002
Use this text to study the conceptual basis of object-oriented programming. The author defines objects, classes, instances, slots, methods, inheritance, pure vs. impure languages, visibility, accessibility, encapsulation, abstraction, delegation, prototypes, actors, iterators, subtyping, multiple-inheritance, mixin classes, interfaces, aggregation, dynamic binding, polymorphism, genericity, overloading, overriding, downcasting, containers, reflection, and meta class. Variations in the implementation of these features in both common and obscure object-oriented programming languages are analyzed. The text covers three language approaches: class-based, prototype, and actor. The author familiarizes the reader with a broad array of programming languages such as Ada, Beta, C++, CLOS, Dylan, Eiffel, Java, JavaScript, Oberon, Omega, Sather, SELF, Simula, and Smalltalk. The book has an academic orientation. Practitioners will be imparted with a deeper and broader understanding of object-oriented principles after digesting this text.


Journey of the Software Professional: The Sociology of Software Development
Journey of the Software Professional: The Sociology of Software Development
by Luke Hohmann
Edition: Hardcover
Price: $30.00
66 used & new from $0.01

1 of 1 people found the following review helpful
5.0 out of 5 stars Effective techniques for software professionals, February 13, 2002
Luke Hohmann explains three aspects of the software development journey: inward focus, outward focus, and upward focus. Principles from psychology are used to demonstrate how the reader can achieve personal growth and develop skills as an engineer or manager. Practical advice for staff and management is prominent at the end of each chapter. Cognitive models, values, personality, goals, culture, strategy, rituals, future perfect thinking, domain experience, competency frameworks, learning styles, training plans, the Johari Window, organizational cohesion and coupling, topology, and roles are discussed in the context of software engineering. The structure, process, outcome (SPO) framework for organizing a software project is a constant thread.


After the Gold Rush: Creating a True Profession of Software Engineering (DV-Best Practices)
After the Gold Rush: Creating a True Profession of Software Engineering (DV-Best Practices)
by Steve McConnell
Edition: Paperback
67 used & new from $0.01

2 of 5 people found the following review helpful
4.0 out of 5 stars Software engineering as a profession?, October 30, 2001
Uses the analogy of moving stone blocks to illustrate how smart teams continuously look for ways to work efficiently. The author explains how the code-and-fix development pattern is fool's gold. The relationships of computer science vs. software engineering and engineering vs. art are analyzed. Software engineering is defined as the application of scientifically developed and mathematically defined algorithms, functional design methods, quality-assurance methods, and other practices to the development of software products and services. The SW-CMM rating system is explained including the performance benefits of a Level 5 organization. Table 9-1 examines the current status and maturity of software engineering as a profession in the categories of initial professional education, accreditation, skills development, certification, licensing, professional development, professional societies, code of ethics, and organizational certification. An outline for the software engineering body of knowledge is presented. The licensing and specialization of professionals acts as a filtering system. The chasm between "early adopters" and "early majority" in technology innovation is analyzed in respect to the software engineering profession.


Software Cost Estimation with Cocomo II
Software Cost Estimation with Cocomo II
by Barry W. Boehm
Edition: Hardcover
34 used & new from $4.94

21 of 22 people found the following review helpful
5.0 out of 5 stars A stalwart of software engineering modeling, September 22, 2001
The latest revision of the well known COCOMO constructive cost model is calibrated with a Bayesian approach that balances 161 industry reference points with the determination of software development experts. Software engineers use the COCOMO model to make financial decisions, set project budgets and schedules, negotiate tradeoffs, plan to maintain or upgrade legacy products, and decide where to implement process improvement. The model equations are provided including normative calibration using 5 scale factors and 17post-architecture effort multipliers. The criteria described for assessing your project for scale factors and effort multipliers are fuzzy in some cases (Default to the nominal level when in doubt). The model can accept estimates of either logical lines of code or function points as the primary input parameter. The book is accompanied with a CD that contains the USC implementation of the COCOMO model and some instructional videos. The final 2/3 of the text covers emerging extensions such as object point data, application point data, phase schedule and effort model (COPSEMO), dynamic COCOMO, RAD schedule estimation model (CORADMO), commercial-off-the-shelf integration model (COCOTS), quality estimation (COQUALMO), and productivity estimation (COPROMO). Read "Software Engineering Economics" published in 1981 for additional background information on the COCOMO model.


Page: 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11