Software Books
Related Subjects:
More Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250

Used price: $37.00

The only guide for Oracle DBA's on PeoplesoftReview Date: 2007-06-21
Pragmatic, focused, detailedReview Date: 2005-01-10
Served as excellent overview for meReview Date: 2007-08-11
After skimming through the book for few hours, I was able to fully understand and talk to Peoplesoft people at client side. In some cases, I knew even more details (or where to get more) than DBA on client site. Showed this book to the client DBA and he was so much thrilled with that - ran and bought it right away.
Well done David! Excellent Job. Thanks!
Best PeopleSoft book for Oracle DBA who needs to learn PeopleSoft supportReview Date: 2006-01-23

Used price: $30.00

Good book. Menasce's operating class was excellent as well.Review Date: 2007-12-24
His operating systems class was one of the most memorable that I took at GMU (over a decade ago). I don't know how many other Operating Systems professors take his approach in focusing on queuing theory in modeling performance problems, but his approach is enlightening.
Using one of his performance models, we were (in class) able to tweak the performance characteristics of the various (modeled) components and watch bottlenecks move from one device to another, underscoring how you can reach a point where improving performance in the wrong component can be a waste, while making small improvements in the bottleneck can provide much better (often linear) improvements.
Excellent Representation of Complex Thoery with real world examplesReview Date: 2006-12-29
This book stood out to my quest. The pace of the coverage was gradual from Gear 1 to Overdrive. Every ounce of theory was supported with examples. Normally I would skip theory and look for examples. But here I enjoyed reading theory. Well Written!
The Case Studies were real world examples. I gained a lot reading this book. Would recommend this book for Technology professionals who want to switch to Capacity and Performance Management.
I would definitely want Mr Menasce and his team to write books on the same topic to address real world end-to-end and new challenges like Petri Nets, Technology Consolidation, Data Warehousing, GRID, Utility Computing, Virtualisation etc. This should definitely help the Technology Community at large.
Factoring performance into the development lifecycleReview Date: 2004-02-12
Performance engineering is a discipline that attempts to integrate concerns about the responsiveness of computer applications and their capacity requirements into standard application development practices, which otherwise focus almost exclusively on meeting functional requirements. Just like not getting the functional spec right in the early stages of the application development lifecycle can lead to a cascading series of design and implementation decisions that are difficult to reverse in later stages of the development process, neglecting performance considerations until after the applications has met its functional requirements is often too late to tackle them effectively.
The first part of the book surveys a wide range of performance modeling and capacity planning techniques, served up in clear, concise language with a minimum of mathematics. It is a gentle introduction to analytic queuing networks written at the level that any advanced undergraduate Computer Science student ought to be able to master. The heart of the book, representing Chapters 5 through 9, is a series of Case Studies that rounds out and concludes Part 1. Each of the case studies deftly illustrates another analytic technique that a performance engineer needs to understand how to apply. Chapter 5, for instance, steps through descriptive statistics and cluster analysis as it discusses what is involved in deriving model parameters for a simple database transaction workload. Chapter 6 builds upon this discussion by solving a simple multi-class model, delving into confidence limits and the use of a factorial design to limit the number of trials of a benchmark experiment. Finally, Chapter 9 illustrates using software performance engineering techniques to model a new application during its initial development phases, beginning with the database design.
The first half of the book is designed to stand alone if the Reader doesn't have the stomach for the rigorous mathematical treatment of analytic queuing models that characterizes Part 2. The second half of the book should be familiar territory to readers of Menasce's other books on performance modeling, beginning with Markov chains and proceeding through Mean Value Analysis. The final two chapters describe approaches to modeling serialization delays and servers that have load-dependent performance characteristics, two topics that are essential to accurate models of application-level performance.
The great challenge of the performance engineering approach is how to persuade experienced applications developers to adopt these techniques. "Performance by Design" is aimed at getting software developers to pay closer attention to performance concerns throughout the application development life cycle. Compared to other books on the subject, this may be the best attempt yet to promote the practice of performance engineering as a discipline that deserves to be integrated into the wider context of application development.
Outstanding introductory book to a complex topicReview Date: 2004-01-30
The book is structured into two parts - Part I consists of four chapters that lay the foundation. Chapter 1 covers system life cycles, Chapter 2 moves the reader from systems to descriptive models of the systems, and Chapters 3 and 4 delve into the essence of performance - quantifying performance models and giving a performance engineering methodology. This material is reinforced with five chapters, each of which is a case study of a specific performance problem. These include database services, web servers, data center, e-business services and help-desk services.
Part II, The Theory of Performance Engineering, addresses the underlying knowledge that performance and capacity planners will need in order to approach their tasks using true quantitative methods. The six chapters in this part of the book cover the following topics in detail, and are clearly and succinctly written: Markov models, single queue systems, single class MVA (Mean Value Analysis), queuing models with multiple classes, queuing models with load dependent devices, and non product-form queuing models. Armed with a knowledge of these fundamentals you should be able to tackle complex performance and capacity problems, both in the software engineering domain when a system is being designed, and in the operational support domain when service level management and availability are the goals. In addition to the way the authors step you through complex math in a clear, easy-to-understand manner, this material is augmented by Microsoft Excel workbooks that bring the material to life. Nearly every chapter has associated workbooks and spreadsheets that can be downloaded from the web site that supports this book, adding considerably to the value of the material.
If you are new to performance planning as a discipline this should be the first book you read on the subject. If you teach performance planning, this is an ideal text around which you can base a curriculum that will prepare your students for real world challenges.
Used price: $1.75

the masterReview Date: 2006-12-21
Before reading this book I thought the Jeff Duntemann assembly book was pretty good but this book makes it look bad!
First half of book has you working in debug which comes with every version of windows and easier to get going than masm.
2nd half covers masm but code still works with latest version of microsoft assembler 8.0 which I'm currently using!
Great book/ Great authors/ A must-readReview Date: 1999-04-15
A must book on assembly concepts and tutorialsReview Date: 1997-12-19
My first Assembly bookReview Date: 1997-11-08

Used price: $0.09

Excellent!Review Date: 1998-10-31
Absolutley a must for Photshop hobbyist or professionalsReview Date: 1998-03-12
Photoshop 4 F/X proved its value the first time I opened it!Review Date: 1997-10-09
Last week I had to do an info-graphic to accompany an article I had written. I needed to cut an image out of its background, soften the edges, and add a realistic shadow. Oh yeah, I needed three different images, too.
After a half hour of unsuccessful fiddling around I remembered this book. I found the right section, and it told me what to do in clear, quick prose. AND...it worked!
Ken Milburn and Mary Jane Mara have done a great job on this book, and a great service to the community. I can tell by the stuff I don't understand yet, that there are tips that willl appeal to more experienced users, too.
Bottom line? If you use Photoshop, you need this book.
Practical Solutions for Professional PhotographersReview Date: 1997-09-12

Used price: $11.00

Great Book for Beginners and AdvancedReview Date: 2002-09-16
Excellent sourceReview Date: 2002-08-29
Master Photoshop's powerful tools with real-world uses!Review Date: 2002-08-27
A Stand-Out Among Photoshop BooksReview Date: 2002-09-03

Used price: $23.32

A perfect pick for any who find detailed Photoshop coverages confusing.Review Date: 2007-09-07
Diane C. Donovan
California Bookwatch
A usable practical guide for serious readers.Review Date: 2007-08-14
awesome resourceReview Date: 2007-07-12
Excellent full explanation referenceReview Date: 2007-07-19

Used price: $15.99

Very helpful!Review Date: 2008-01-29
Wonderful Book for Digital Scrapbookers!Review Date: 2008-01-18
Worth it for the kits alonwReview Date: 2008-01-18
Very Comprehensive IntroductionReview Date: 2008-03-07
Used price: $0.82

An excellent addition to your powerbuilder repositoryReview Date: 1999-01-11
An excellent collection to your powerbuilder repositoryReview Date: 1999-01-06
A valuable addition to your powerbuilder repositoryReview Date: 1999-01-06
CODE CODE CODEReview Date: 1998-12-29

Used price: $1.25

Practical Data Structures in C++ Roma 6.03.2002Review Date: 2002-03-06
le principali caratteristiche delle strutture implementate in C++.
L'unico difetto - non imputabile all'Autore - sta nel linguaggio
adoperato, oramai piuttoso obsoleto e lontano dall'attuale standard ANSI.
Perchè la Wiley non invita il dr Flamig a pubblicare un aggiornamento dei suoi ottimi libri? Sono sicuro che diventerebbe un best-seller!
In ogni modo, anche cosi' è altamente raccomandabile ai programmatori di ogni livello, perchè contiene un'infinita' di
varianti e suggerimenti e,soprattutto, il codice completo che mostra come realizzare in pratica quanto appreso nella teoria.
-
A very good C/C++ bookReview Date: 1999-02-04
I don't understand why the codes in ch8 don't work.Review Date: 1997-12-04
Practical Data Structures in C++Review Date: 2001-04-06

Used price: $14.42

Excellent book on a topic long over due.Review Date: 2002-05-02
The three part approach to the book makes it easy for you to find the topics you need to get your job done. Part 2 defines each of the processes in detail. Chapter 5, which covers reporting/tracking progress gives a good feel for the control you have in producing project deliverables, and reporting on the true progress of the project. Realistic, acurate reporting.
I would recommend this book to anyone who is a slave to their process, or even those that are new to process. This one works!
Lower your risk on large business software developmentReview Date: 2003-01-02
The authors stress that feature-driven development, as they describe it, is intended for a very specific type of project. There's nothing new in the book, except the way the authors have combined tried-and-true techniques to handle very large business application development in a consistent and low-risk manner. The smallest headcount that could justify the overhead is about twenty, although it could scale up almost indefinitely. Palmer and Johnson describe their methodology as light but, on a scale of five (heavy) to one (agile), FDD rates about a four.
The second point is that the techniques used assume very heavy customer involvement and clearly understood business rules. For example, the original project that inspired the book was a banking system in Asia. The procedures wouldn't be well-suited to innovative product development in a competitive environment. This is no alternative to extreme programming.
Lastly, the methods used aim to get good results from inexperienced employees. Despite a reminder that highly-ranked programmers are better value than entry-level personnel, this type of project often relies on an army of tightly-controlled programmers, led by a few experienced team leaders. Although the authors differentiate the FDD organization from the old Chief Surgeon model, this is still basically just a variant on that theme.
There are also more than a few hints that the book is not intended solely, or even primarily, for US readers. We are abjured to speak in English and leaders are advised to use a soccer whistle to control meetings. As beautifully as the authors describe how to divide up a large project by feature (and it is beautifully clear and simple), some of the advice in handling personnel leads me to hesitate before recommending it without reservation to every potential reader, which is the criterion Amazon requires for a 5-star rating.
Packed with good advice on Software Development Process!Review Date: 2002-04-28
This book is packed with good advice for developers and those involved in managing software development, and is clearly written by people with real world experience. The authors do a good job of explaining the issues in software development and how FDD helps address them.
The book is highly readable and should be accessible to those who currently have a limited understanding of formal software development processes. One of the themes carried through the book is an ongoing dialogue between the two authors and several other persons, including the project manager of a software project for a car dealership that is worked through in the book. At first I found this dialogue distracting, I guess because they were initially dealing with material I am already familiar with, but by the end of the book, I looked forward to these sections, and felt they gave the book an overall coherence.
FDD is most radical, in its approach to management (reporting), by dispensing with Gannt charts and estimates of task completeness (most people are aware of the 90% complete, 90% of the time, syndrome), replacing them with measuring features complete (as in 100% complete!) as a percentage of all features to be built. I am familiar with why Gannt charts and Microsoft Project style planning doesn't work for software projects, but the book would have benefited from a more detailed discussion of what will be the hardest part of FDD for many to accept. The book's only real fault is several digressions into software quality and online help, that it was hard to see the relevance of.
I recommend this book to people, including managers, who want to understand why we need software development processes and the issues involved in selecting one. The book, naturally enough, points out the issues with widely used processes such as RUP - too heavyweight, and XP - questionable scalability, and these criticisms are IMO largely valid. The book explains in a straightforward way, how FDD works and how it satisfies all the main requirements of a development process, especially scalability, manageability and getting the domain model (shape) right as early as possible, minimizing the need to refactor later.
Elegant, Effective and PowerfulReview Date: 2002-04-26
Although the approach is based on object-oriented development, and the book is focused towards that approach, it can be refactored into function- and procedure-oriented programming environments. Moreover, the book is written to fit within agile methods, but the approach can be fit to any development life cycle approach. This is because the focus is on features, which translate into what the business *needs* from an application. This is where elegance and simplicity comes in. By focusing on the features needed applications are less apt to be 'gold-plated' with unnecessary features that developers may think is nice, but add little business value. In this respect the time to deliver is shortened and what is delivered is going to reflect genuine business requirements.
The power of FDD comes from the highly structured approach that i based on the ETVX (entry-task-validation-exit) framework. Entry criteria is typical: requirements, authority to proceed and other 'quality gates' that must be passed before a development project is initiated. The tasks follow a five-step process as follows:
(1) Develop the model, including scope, validation in the form of walkthroughs, and peer reviews. The approach described in the book assumes an object model, but in a non-OO setting this can be realigned to first cut system diagramming in the form of block- and data flow-diagrams,and first-cut design.
(2) Build the features list. The OO approach is domain partitioning based on the model; in a non-OO setting this is where the team maps functional requirements to features.
(3) Plan by feature. This step, in my opinion, shows FDD to be a legitimate software engineering method. Feature prioritization, dependency analysis and effort estimation occur here. Done properly this step will make the difference between success or failure. I do have one issue with the book at this point: the prioritization is done by the technical team - it should be done with the business stakeholders.
(4) Design by feature. This is an iterative step that feeds back into step 1 (build the model) wherein class ownership is determined and the original model is refined based on the design approach. In non-OO environments this would loop back into the first-cut design and trigger trade-off analysis and design refinement.
(5) Build by feature. This is where the application is actually developed on a feature-by-feature basis within the context of the defined architecture (model).
Verification is accomplished using traditional methods. The authors introduce what they call 'feature-based testing' which is no different than product test (also called functional qualification testing, and in some circles, acceptance testing). Verification procedures are thoroughly covered in the book, further adding to the software engineering approach that is incorporated into FDD. Exit criteria is when the sponsors accept the system.
What makes this book important is that is gives a straightforward approach that is based on deliverables (features) within a process context (ETVX). This approach is consistent with best practices in software project management and has the additional benefit of assuring that what gets designed and built is what the customer needs. Bolt FDD onto your favorite methodology and you'll probably see quality increase, and costs and time to deliver decrease.
Related Subjects:
More Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250