Average customer rating:
- Too complicated, author needs to "speak english doc!"
- Almost worthless as a textbook
- There's sure to be a better Databases textbook out there.
- Principles of Database Systems
- The best!
|
Principles of Database Systems with Internet and Java Applications
Greg Riccardi
Manufacturer: Addison Wesley
ProductGroup: Book
Binding: Hardcover
 General
| Java
| Programming
| Computers & Internet
| Subjects
| Books
General
| Programming
| Computers & Internet
| Subjects
| Books
General
| Languages & Tools
| Programming
| Computers & Internet
| Subjects
| Books
General
| Computers & Internet
| Subjects
| Books
General
| Databases
| Computers & Internet
| Subjects
| Books
Java & Databases
| Databases
| Computers & Internet
| Subjects
| Books
General
| Software
| Computers & Internet
| Subjects
| Books
All Titles
| Qualifying Textbooks - Fall 2007
| Stores
| Books
Computers & Internet
| Qualifying Textbooks - Fall 2007
| Stores
| Books
ASIN: 0321185560 |
Customer Reviews:
Too complicated, author needs to "speak english doc!".......2004-04-14
I used this book while I was attending a class in database systems. After some 100-150 pages I simply stopped reading it. The author is to much into using academic mombo-jombo talk, that just trying to understand one simple line sometimes seems impossible. After some time the lessons got to the point in the book where I had given up and after the teacher explained it, I was thinking "Was that it?". The author needs to realise that it is a LEARNING book he is trying to write, not a "look, im smarter than you" book. I'd pretty much recomend ANYTHING other than this book....its useless in my opinion.
Almost worthless as a textbook.......2003-10-16
The book relies heavily on explaining concepts through the examples outlined. So heavily, in fact, that trying to understand a single concept is almost impossible without reading the book as a whole.
To use it, you kind of have to read it cover to cover--novel style. This is rarely a useful way to approach technical learning, and other books do much better with alternate approaches.
There's sure to be a better Databases textbook out there........2000-08-26
I took this course from Dr. Riccardi himself at FSU. To be fair, the book was still in the development stage when I had his class. However, I found that the examples in the book never quite communicated the idea he was attempting to communicate. The examples were not simple enough, and very often showed multiple concepts which tended to take away from the effectiveness of the example.
The book is also a bit confusing. There are a lot of terms that have been carefully defined, however, similar sounding terms have a completely different connotation.
Although Java is not a stated prerequisite to this course, I would recommend having Java either before taking the class or during the same semester. Later in the book there are some assignments in Java. The author expected the class to be comfortable with reading and modifying Java source code.
Principles of Database Systems.......2000-08-25
This book does a wonderful job explaining database systems using Java. I have read many books on the subject and this is the best one I have found.
The best!.......2000-08-24
This is the best book on the subject that I have seen so far! A must for everyone who works with Java and databases.
Book Description
Software Quality Assurance (SQA) as a professional domain is becoming increasingly important. This book provides practical insight into the topic of Software Quality Assurance. It covers discussion on the importance of software quality assurance in the business of Information Technology, covers key practices like Reviews, Verification & Validation. It also discusses people issues and other barriers in successful implementatin of Quality Management Systems in organization. This work presents methodologies, concepts as well as practical scenarios while deploying Quality Assurance practices and integrates the underlying principle into a complete reference book on this topic.
Customer Reviews:
Good but overpriced........2007-08-22
I recently purchased an international version of this book for considerably less than the price advertised on Amazon. For what I paid I consider it a good reference to have for SQA, but I still like Schulmeyer's Handbook of SQA which has a new edition coming out September 30 for $99. No disrespect intended, but the book seemed written by someone who was not a native speaker of English, so the wording can be a little difficult to follow.
Expensive for nothing.......2007-04-07
The book quality is good the cover and papers are ok, the problem is the price with relation to the material inside.
The book is too expensive for what you get from it, there is many other books with the same subjects inside with less money.
This book can be useful if you are starting to learn the quality assurance.
Project Manager's Review.......2005-09-23
I recently had the pleasure in working with Mrs Godbole on a project in South Africa.
I was the project manager and she supported me in the role as a Senior QA Analyst.
After reading her book I was pleasantly surprised to see that she is actually putting into practice what she has documented in her book, Software Quality Assurance: Principles And Practice.
Chapter 4-Product Quality and Process Quality I found very interesting. As a project manager I have to manage the quality of product deliverables and at the same time this needs to be per a standard quality process.
This book is not a one time read for project managers.
I use this book every day in my day to day project management activity.
I recommend all project managers to not only read this book but to use it as an everyday project management tool.
I also set-up project management offices - I recently used this book to set-up the entire QA workstream within the organization.
A truly classic reference material and easy reading.......2005-08-08
In my career as a practitioner implementing sound Software Quality Assurance principles, this book has come as a great boon.
The author has adequately reflected her thoughts into a real world of SQA with very fine illustration of the implementation aspects in the organization. The book should be a good reference to both students and practitioners who wish to understand the principles of software quality assurance and the challenges faced during successful implementation. Practitioners are likely to benefit more from the author's excellent illustration of examples and the discussion on the people issues in successful implementation of the Quality Management System in their organization.
Chapters that will be of interest to real world SQA include Chapter 2- Managing Software Quality in an organization (excellent expression of the organization's commitment to Quality, chapter 4-Product Quality and Process Quality, chapter 5 (A sound foundation for a metrics initiative), Chapter 7. Software Configuration Management (Pitfalls in SCM), Chapters 8 (ISO 9001 - especially the insights into ISO consulting and services!!), Chapter 10-Software testing (The V model for testing phases and test process improvement framework is indeed very interesting and informative) The best part of the book which I enjoyed most was chapter 11-Careers in Quality, in which the author has so aptly brought out the role of a mentor who can help carve a career in Quality. The author's clarity in documenting the different roles for Quality professionals is really commendable.
SQA as a discipline is difficult to implement and is more engineering focused than most disciplines in development and operations. In spite of these challenges, this book has been written to support Software Quality Assurance as an important component of software engineering activity and contains chapters that are specifically slanted towards that approach. Included are chapters on Walkthroughs and Inspections, Software Configuration Management, Software testing and Software measurement and metrics. The author also provides solid information on ISO Quality Assurance standards, SEI CMM, SEI CMMI, and PCMM, as well as on common practices followed at "Mature Organizations".
As a textbook the coverage of every facet of SQA from why and what, to testing, metrics and its role in organizations and projects are thoroughly covered. The fact that the material is up-to-date and truly reflects the real world makes this one a must read for college level courses and more so, it prepares students for roles as practitioners. It is a classic and earns a solid 5 stars.
Great information source for Software Quality Assurance.......2005-07-08
As someone who has worked in both software development and quality, I instantly connected with the quality practices and scenarios that the author describes about the role of quality in most software development organizations. It states the challenges faced by SQA teams in implementing quality practices, especially in terms of people issues and the approach that may be taken to overcome them. This book provides insight into the SQA function and role, its importance and the commitment required to make it effective. I liked this part, as there are few books that stress on the crucial role played by the SQA in a company committed to quality.
I found the section on measurement and metrics with metrics and formulae that can be used through the SDLC. There are other books that provide in depth treatment on metrics, but the content here is useful because of its timing and context and it works well as a ready reference. The author has explained a number of international quality models like ISO and CMM along with their comparative study and mapped them to the various phases in the SDLC wherever possible. There are books available that dwell on a single quality model, but few go beyond more than a one page tabular comparison. I have found that quality professionals have to often struggle to map between multiple models to aggregate information at an organizational level when projects execute using models most appropriate to them.
The chapter that I enjoyed reading most was "Careers in Quality". This chapter is informative for IT professionals who aspire to move into the quality arena. It outlines the various opportunities available and the paths that may be taken to achieve them. The author has also explained the importance of a mentor and the qualities one should look for in a mentor who can help shape one's career. There are few places where one finds information on how one can make a complete career transition to quality, mentors and the various certifications that can be obtained for faster and focused growth.
Throughout this book, the author has explained concepts like process life cycle and inspection walkthroughs using diagrams, making them easy to understand. A number of sample documents (Quality Assurance Plan) and checklists (Configuration Audit) are available which can be used as a starting point by SQAs in their organizations.
On the whole a good read and informative. Recommended book to have.
Customer Reviews:
Sound background and concepts for CM.......2006-10-13
If you are going to be working in the field of build and release management, then you will need a good background and working knowledge of Software Configuration Management. This book is the one that I believe will most readily enable you to achieve this. It doesn't look at specific techniques or tools, just what SCM is and why we need to do it.
A Useful Survey Of Present-Day CM But Needs Supplementation.......2006-06-28
In what hopefully will not be an over-repetition of other's comments, I found this book generically descriptive, theoretical, and quite dense. One of the reviewers said it would be a book best suited for university, and I agree wholeheartedly -- it would make a decent textbook for those MIS programs brave enough to tackle CM. While in the minds of many that translates to "unsuitable for the real world", I would prefer to offer the following analogy, at the risk of sounding too self-referential.
As of this writing, I've reviewed three CM titles. If they were about cooking instead of CM, here's how they would map:
Hass's CM Principles and Practice --> A Survey of Current Cooking Methods and Techniques (e.g. Frying, Basting, Folding, Mixing, etc.)
Moreira's SCM Implementation Roadmap --> Betty Crocker Cookbook
Kenefick's Real World SCM --> Screenplay to "Hell's Kitchen" or maybe "The Galloping Gourmet" (for those who remember the '70s)
General commentary aside, I'd like to offer the following suggestions for the next edition:
1) Clarify the term "event registration" on pp. 20-1. I'd also like to say I disagree with the author's view that event registration and change requests be kept as separate entities. A CM program will become hopelessly bogged down in maintaining separate event and change logs.
2) Change the term "person responsible" on pp. 146-7 to "configuration manager" -- it's easy to want to use a generic term to avoid confusion, but it's not warranted in this context.
3) Switch Chapters 12 and 13, to maintain progression of scale.
4) On page 225, what is the meaning of the word "louse"? Does the author mean "bug"?
5) Clarify the term "balance point" on pp. 302-3.
To sum, the book has a broad reach, with a useful bibliography, but by itself will not suffice for implementing CM at your company.
Room for improvement.......2006-03-17
First, I must agree with other reviewer that it is odd that this book is in "The Agile Software development series". It reads more like an "old-school" book, that may well be used at university for an "encompassing" "fool-proof" view into CM.
I bought this book on reading the other reviews and since it was an "agile" book (almost all other agile books I have read are concise and worthwhile, packed with useful thoughts). This was, from that perspective, a great dissapointment.
My recommendation: Read the table of contents of this book. It is quite telling. In short: 1 chapter definition, 2 on standards/maturity models, 4 on what fields go into a CM system (phew), 5 on roles in CM (yup, you read that right). Then we get to the "practice" (part 4): 3 chapters that again list suggestions for id's of items, storing them, tracing them, etc. Heads up, here is the agile chapter (18). Or rather, its a section. Then there are some chapters that seem interesting but fail to be.
Lastly we get 5 more chapters on maturity models, this time on how to achieve them.
My biggest issues with the book are the constant repetition and the lack of form. Every chapter is a listing of things, the train of thought seems to be derived from a powerpoint slidedeck. I am impressed that the author managed to actually write a book that is as boring as this, constantly listing and reiterating points already touched upon. I would have wanted the maturity model coverage in a separate book and any knowledge left after that condensed in a useful format.
I am sorry to say that I cannot find this book that useful today. Were I charged with implementing a very formal SCM project at a fairly large shop, then... I would have looked into it seeing as it sits in the shelf, but I probably wouldnt use it then either. Sorry.
Very disappointing - just theory, not agile.......2005-07-20
This book is the most disappointing book I read for years. The book is published as part of the "Agile Software Development Series".
If you know agile software processes you know they are very hands on. They are for team up to 10 maybe 20 people. Agile processes focus on delivering working software, not on documentation and too much formalism. The focus of this book is the complete oposite. For me, it targets projects with at least 50 or more team members in very large organisations. Far away from agile.
The second thing I don't like is that it's all just theory in this book. But no practice how I really implement configuration management in my company. Which tools do I need for what (ok, there is one page about that) and so on.
All in all, very disappointing and definitly far away from agile processes.
A good insight into Configuration Management.......2004-11-22
This volume should be prescribed reading for all IT professionals. Everybody but everybody has an opinion on the merits or otherwise of Configuration Management, but a better understanding would help us all. People not actively part of Configuration Management [CM] will then say, "Yes, it is both more important and more involved that I had thought hitherto".
There are five parts to the book; what is CM, the data required for CM, roles within CM, CM in practice and improving CM. The last three are probably the more interesting, but without the first two, it is talking into a vacuum. Throughout, there is emphasis that CM is a tool to be used, and should not become a priority in its own right. Good CM should provide benefits; unfortunately, those who receive the benefits are not always those who have paid the cost (in terms of extra effort and/or information that is required of them).
In the first two sections, there is a lot of material that seems repetitive. An example of this is material regarding the naming of configuration items, deliveries, etc. However, this is also an advantage, as chapters or parts of chapters can be read in isolation. I particularly like the use of the same examples in various parts of the text. When referred to, there is usually a diagram, and this is in text, rather than referring to another page in another chapter. Table 15-1 is the same as table 6-1. In books where the diagram is NOT repeated, but the reader referred back to re-read the other section, they never do!
Fundamental questions about what to include under the control of CM are addressed (although not always prescriptively answered). What should be included in the CM system? Do you include program source and object code, just source code, or source and the compiler? If the compiler is not included, it may not be possible to amend code for old platforms. Similarly, all tools should be potentially under CM control. Otherwise, a document written is an obscure word processor format may be available in the future, but not the means to even read it easily?
There is discussion about the need to capture both physical objects (PC's, memory boards) AND electronic objects. In this case, CM can partly overlap with asset management; it is other ways very different from the latter. However, the author stresses the need to know the boundaries of CM; the defining of a software delivery is not the responsibility of the CM team. Similarly, the use of variants is a design decision, not decided or dictated by those in CM. The latter is essentially an administrative task, concentrating on the four cornerstones; identification, storage, change control and status reporting.
The challenges of these four categories are brought out in the latter parts. Most people would agree that documents need to come under CM control at some point. The storage of documents can present challenges, particularly if a master document has many composite parts. There are also needs to take account of cross-references (which may be different to the formal linkages that are reported by the CM tool). Much information can be gathered from the information available through CM. A well-made point is that there is no point in gathering information if no one is going to use it.
Anne Mette's first language is not English, and sometimes this shows. It is difficult to define how this is the case, but sometimes the use of language can be an advantage. Some things are described as being `an inspiration', not an expression that many would necessarily have chosen. That comes across well. However, do not confuse the style with the substance. The latter is the most important, and it is a very good standard.
How do fill a book of 350 pages on CM? Several items are covered that are not exactly mainstream CM, but are very relevant and appropriate to the discussion. The section on `people roles' comes over well, and is part of the selling of CM as a discipline. This section draws on the work of Dr Meredith Belbin, and his nine team roles, applying this specifically to CM.
The last comments are reserved for the final part, allowing the CM process to be part of the overall Process Improvement drive within an organisation. If there is no CM process in place (not to be confused with there being no CM tool in place), it can be difficult to know where to start. An apt comparison is about a centipede thinking about how to walk - too much thought makes for a tangled heap in a ditch, instead of just doing it. The author says go for quick cheap wins, and if possible base any initial procedures on existing practices. This will significantly enhance the chances of success.
CM is a big topic. This volume brings out many of the issues that are involved, and gives guidelines on overcoming some specific challenges. There are practical examples, but these are more in the line of serving suggestions, rather than a fixed menu.
Peter Morgan, Bath, UK (morganp@supanet.com)
Average customer rating:
|
Principles of Database Systems (Computer software engineering series)
Jeffrey D. Ullman
Manufacturer: W H Freeman & Co (Sd)
ProductGroup: Book
Binding: Hardcover
Mathematics
| Professional Science
| Professional & Technical
| Subjects
| Books
| Applied
| Chaos & Systems
| Geometry & Topology
| Mathematical Analysis
| Mathematical Physics
| Number Systems
| Pure Mathematics
| Transformations
| Trigonometry
General
| Reference
| Subjects
| Books
General
| Databases
| Computers & Internet
| Subjects
| Books
Similar Items:
-
Introduction to Algorithms
ASIN: 0716780690 |
Average customer rating:
- Great book on Software Engineering
- Sound ideas, but tedious to read
- Simply the best book on software development I have read
- Good but limited
- Good discussion of evolutionary development
|
Principles Of Software Engineering Management
Tom Gilb
Manufacturer: Addison-Wesley Professional
ProductGroup: Book
Binding: Paperback
MIS
| Industries & Professions
| Business & Investing
| Subjects
| Books
Software Development
| Software Design, Testing & Engineering
| Programming
| Computers & Internet
| Subjects
| Books
General
| Programming
| Computers & Internet
| Subjects
| Books
General
| Languages & Tools
| Programming
| Computers & Internet
| Subjects
| Books
General
| Project Management
| Computers & Internet
| Subjects
| Books
Information Systems
| Software Engineering
| Computer Science
| Computers & Internet
| Subjects
| Books
General
| Software
| Computers & Internet
| Subjects
| Books
Mathematics
| Professional Science
| Professional & Technical
| Subjects
| Books
| Applied
| Chaos & Systems
| Geometry & Topology
| Mathematical Analysis
| Mathematical Physics
| Number Systems
| Pure Mathematics
| Transformations
| Trigonometry
Look Inside Computer Books
| Trip
| Specialty Stores
| Books
All Titles
| Qualifying Textbooks - Fall 2007
| Stores
| Books
Business & Investing
| Qualifying Textbooks - Fall 2007
| Stores
| Books
Computers & Internet
| Qualifying Textbooks - Fall 2007
| Stores
| Books
Professional
| Qualifying Textbooks - Fall 2007
| Stores
| Books
Similar Items:
-
Competitive Engineering: A Handbook For Systems Engineering, Requirements Engineering, and Software Engineering Using Planguage
-
Software Inspection
-
Rapid Development
-
Software Requirements, Second Edition
-
The Mythical Man-Month: Essays on Software Engineering, 20th Anniversary Edition
ASIN: 0201192462 |
Customer Reviews:
Great book on Software Engineering.......2007-08-30
This book covers two very important software engineering topics: the unambiguous specification of business goals and product specification and on evolutionary project management. It also covers the Fagan inspections process which is one of the most powerful techniques in software development. If you like this book, you should also consider the boook "Competitive Engineering" by the same author.
Sound ideas, but tedious to read.......1999-09-29
I found this book hard to read. I often had to force myself to read further, although the ideas and principles described are important and should be required knowledge of any software engineer and SE manager (which does not mean that they necessarily apply to all projects).
The book contains endless redundancy and lots of hard to understand details of projects the author has worked on. One chapter even contains excerpts from other books and articles that confirm the author's views - as though the author feared he hadn't been convincing enough (that wasn't the problem).
In summary, the book should have had half the length and that would have still covered the same content. It might be interesting to readers new to the principles of evolutionary delivery, measurable attribte objectives, and inspection.
Simply the best book on software development I have read.......1999-09-20
Firstly, don't let the title put you off -this book is relevant to a lot of people who wouldn't call themselves "sofware engineers" or "managers" - it's also highly relevant to systems analysts / designers & just about any sort of IT consultant, amongst others.
What separates this from most other books on software development is that just about every page is obviously written by someone who has been there and done it (recently), not just talked about it. The main ideas of the book (evolutionary delivery, defining ojectives as either "functional" or "attributes" ) may not seem revolutionary, but apply it and it could revolutionise your project and maybe career. No IT book I've ever has ever affected my own work so profoundly.
It's also well written and exceptionally well laid out. More please, Tom!
Good but limited.......1998-06-26
Gilb covers only a small portion of "Software Engineering Management" in detail. Other important issues are either not addressed at all or receive only cursory treatment. Still, what it does go into depth about it usually well thought out and makes imminent sense. I'd say it's worth reading, but it may be a bit expensive for it's narrowness.
Good discussion of evolutionary development.......1998-05-19
This book covers three main topics: evolutionary development, requirements management, and inspections. A good introduction to all three, but if you plan on trying evolutionary development, I also suggest reading the pertinent sections of Rapid Development by Steve McConnell.
Book Description
Software project managers and their team members work individually towards a common goal. This book guides both, emphasizing basic principles that work at work. Software at work should be pleasant and productive, not just one or the other.
This book emphasizes software project management at work. The author's unique approach concentrates on the concept that success on software projects has more to do with how people think individually and in groups than with programming. He summarizes past successful projects and why others failed. Visibility and communication are more important than SQL and C. The book discusses the technical and people aspects of software and how they relate to one another.
The first part of the text discusses four themes: (1) people, process, product, (2) visibility, (3) configuration management, and (4) IEEE Standards. These themes stress thinking, organization, using what others have built, and people. The second part describes the software management principles of process, planning, and risk management. Part three discusses software engineering principles, the technical aspects of software projects. The fourth part examines software practices giving practical meaning to the individual topics covered in the preceding chapters. The final part of this book continues these practical aspects by illustrating a sample project through seven distinctive documents.
Customer Reviews:
The best book on the subject of software project management.......2005-04-28
This book is the best book on software project management available for three reasons: (1) it talks to the basics of what makes a successful project and manager, (2) it describes what does not work in a software project, and (3) it walks through practical steps that can be used on real software projects to solve real process problems through the complete life cycle. The book is well written, concise and does not subscribe to any fad methodology or proscribe any silver bullet solutions (smart work and attention to detail are the only effective methods). In fact, the author spends much time debunking industrial myths. There is a good section on cookbook solutions and an example project included as a learning tool. I use this book on the job and highly recommend it.
A good reference, but not sufficient on its own.......2003-02-25
This book covers Software Project Management broadly with a lot of good information for both the new project manager as well as the old hand. The material is presented as a comprehensive overview rather than a detailed instruction. By itself the book does not go deeply enough into any of the areas to provide a novice with enough useful information so it's a good book to use in conjunction with books providing more detail.
Despite its lack of detail, the book presents many important points - the importance of the human equation, analysis/organization tools such as Tony Buzan's MindMap, having a Management Information Center, and using standards without having a programmer's revolt. There is only passing mention of key issues such as scope creep, the tendency of management to try to throw more personnel at a project in trouble, needing to build testing into the initial design process, and the pro's and con's of the various development methods (waterfall, spiral, etc.). A number of references are quoted, including many IEEE documents (IEEE is the publisher) plus books by Gerald Weinberg, Capers Jones, Tom Demarco, and other recognized gurus - which make good adjuncts to this handbook.
Phillips perpetuates one of my pet peeves, the issue of including the top ten risks in the risk assessment document. What if there are only 7 risks which seem to be significant? What if there are 12? Granted, it would be unwieldy to track & evaluate dozens of risks routinely, but it doesn't make sense to suggest that exactly 10 be tracked.
The discussions of Configuration Management are quite lengthy and in a bit more detail than other topics covered.
Although the book is fairly short at 500 pages and is easy reading, there is a substantial amount of information covered. The 5 star rating is for the breadth of information covered, with the caveat that other references would be needed by those unfamiliar with the concepts presented.
It does work at work........2000-07-11
Don't confuse the ease of reading this excellent book with the depth and power of the information within it. Being involved in software project management myself, I related to the ideas the author expressed and feel I have learned much from reading the book. Other project managers in my company are now reading this book and share similar opinions.
The book contains good explanations of various techniques for formalising projects. It also contains a number of case study experiences which are very apt.
I recommend this book to project managers of all levels and to managers of software companies.
An easy-to-read guide to project management........1999-09-24
Unlike most text books, it is a very easy to read book allowing one to read it from cover to cover. The book is an excellent source for novice project managers who need a guide to the many aspects that come with the job. Personally I refer to it often for suggestions on which documents I should produce or what actions to take while managing a project.
Well written and insightful.......1998-08-24
This is a well written book for the people interested in succeeding with software project management. The author spells out the key pit falls to software development and offers realistic solutions. There are many up to date helpful graphics and tables throughout the book. This is easy reading and keeps the reader interseted.
Book Description
Learn how to use service modelling to streamline and optimize processes!
Information about customer needs, the technical composition of services, and service performance are fundamental to effective service management. Service modelling is a structured approach to utilizing this information to improve the way services are delivered. Consistent application of service modelling provides the automation of processes and timely access to information.
Service Modelling presents a comprehensive, up-to-date overview of the topic, presented in the context both of business processes, and of requirements stemming from the need to manage network resources. Vilho Raisanen delivers a justification for service modelling, and explains state-of-the-art concepts, frameworks and standards in detail.
Service Modelling:
- Provides a complete and illustrated overview of state-of-the-art concepts for service modelling, covering requirements and frameworks.
- Includes industry initiatives, conceptual frameworks, and the work of standardisation bodies.
- Discusses different modelling approaches, and the positioning of modelling of services in service management and in the wider operational context.
- Sets the modelling framework in the context of business drivers and modelling paradigms.
- Illustrates principles with real-world use cases, providing both fixed Internet and mobile network examples.
- Relates concepts to the work of TeleManagement Forum, giving practical examples throughout.
Service Modelling: Principles and Applications is an invaluable guide to service modelling for telecommunications and data communications professionals, including vendors, operators, consultants, training organizations, service and content providers, system architects and engineers for IP-based services. Educational organizations, advanced undergraduate and graduate students on telecommunications and networking courses will also find this text invaluable.
Average customer rating:
- For the classroom only...
|
Software Product Line Engineering: Foundations, Principles and Techniques
Klaus Pohl ,
Günter Böckle , and
Frank J. van der Linden
Manufacturer: Springer
ProductGroup: Book
Binding: Hardcover
Software Development
| Software Design, Testing & Engineering
| Programming
| Computers & Internet
| Subjects
| Books
General
| Programming
| Computers & Internet
| Subjects
| Books
Internet
| Home Computing
| Computers & Internet
| Subjects
| Books
| Internet & Education
| Online Searching
| Web Browsers
| Web for Kids
Design Tools & Techniques
| Software Engineering
| Computer Science
| Computers & Internet
| Subjects
| Books
Information Systems
| Software Engineering
| Computer Science
| Computers & Internet
| Subjects
| Books
General
| Computer Science
| Computers & Internet
| Subjects
| Books
General
| Computers & Internet
| Subjects
| Books
General
| Software
| Computers & Internet
| Subjects
| Books
Look Inside Computer Books
| Trip
| Specialty Stores
| Books
All Amazon Upgrade
| Amazon Upgrade
| Stores
| Books
Computers & Internet
| Amazon Upgrade
| Stores
| Books
All Titles
| Qualifying Textbooks - Fall 2007
| Stores
| Books
Computers & Internet
| Qualifying Textbooks - Fall 2007
| Stores
| Books
Similar Items:
-
Software Product Lines : Practices and Patterns
-
Designing Software Product Lines with UML: From Use Cases to Pattern-Based Software Architectures (The Addison-Wesley Object Technology Series)
-
Software Factories: Assembling Applications with Patterns, Models, Frameworks, and Tools
-
Software Product Lines: Research Issues in Engineering and Management
-
Model-Driven Software Development: Technology, Engineering, Management
Accessories:
-
Founders at Work: Stories of Startups' Early Days
-
Use Case Driven Object Modeling with UML: Theory and Practice
-
Practical Subversion, Second Edition (Expert's Voice in Open Source)
ASIN: 3540243720 |
Book Description
This textbook addresses students, professionals, lecturers and researchers interested in software product line engineering. With more than 100 examples and about 150 illustrations, the authors describe in detail the essential foundations, principles and techniques of software product line engineering.
The authors are professionals and researchers who significantly influenced the software product line engineering paradigm and successfully applied software product line engineering principles in industry. They have structured this textbook around a comprehensive product line framework.
Software product line engineering has proven to be the paradigm for developing a diversity of software products and software-intensive systems in shorter time, at lower cost, and with higher quality. It facilitates platform-based development and mass customisation. The authors elaborate on the two key principles behind software product line engineering: (1) the separation of software development in two distinct processes, domain and application engineering; (2) the explicit definition and management of the variability of the product line across all development artefacts.
As a student, you will find a detailed description of the key processes, their activities and underlying techniques for defining and managing software product line artefacts. As a researcher or lecturer, you will find a comprehensive discussion of the state of the art organised around the comprehensive framework. As a professional, you will find guidelines for introducing this paradigm in your company and an overview of industrial experiences with software product line engineering.
Customer Reviews:
For the classroom only..........2005-11-30
This book is an excellent classroom book, but not practical for PLE in the field. It does an excellent job of laying out a framework for a PLE process and it does an excellent job of teaching variability. The main problem with the book is that it uses the Orthogonal Variability Model to trace the variability in the project's artifacts, and there are no tools to support an Orthogonal Variability Model. It is a perfect way to teach variability, and the Orthogonal Variability Model works well in a text book context, but would not be practical on a real project.
The book makes reference to SEGOS-VM Tool, which is being developed to support the authors Orthogonal Variability Model, but it is no where to be found on the web.
So I would suggest this book only if you are interested in becoming "book smart" about PLE, it does do an excellent job of teaching the topic, but it's process holds little value for real projects.
Average customer rating:
- Poor writing but many various examples
- Best database book for engineers
- Database: Principles, Programming, Performance
- Worst database book ever--a waste of money!
- Wordy, redundant, tedious, still a good coverage
|
Database: Principles, Programming, and Performance, Second Edition (The Morgan Kaufmann Series in Data Management Systems)
Patrick O'Neil , and
Elizabeth O'Neil
Manufacturer: Morgan Kaufmann
ProductGroup: Book
Binding: Hardcover
General
| SQL
| Databases
| Computers & Internet
| Subjects
| Books
Database Management Systems
| Databases
| Computers & Internet
| Subjects
| Books
General
| Databases
| Computers & Internet
| Subjects
| Books
Databases
| Software
| Computers & Internet
| Subjects
| Books
General
| Programming
| Computers & Internet
| Subjects
| Books
General
| Computers & Internet
| Subjects
| Books
Look Inside Computer Books
| Trip
| Specialty Stores
| Books
All Amazon Upgrade
| Amazon Upgrade
| Stores
| Books
Computers & Internet
| Amazon Upgrade
| Stores
| Books
All Titles
| Qualifying Textbooks - Fall 2007
| Stores
| Books
Computers & Internet
| Qualifying Textbooks - Fall 2007
| Stores
| Books
Similar Items:
-
Oracle 9i Programming: A Primer
-
Object-Oriented Design and Patterns
-
Operating System Concepts with Java
-
Guide to TCP/IP
-
Introduction to the Theory of Computation, Second Edition
ASIN: 1558604383 |
Amazon.com
A standard text for database designers and programmers, Database: Principles, Programming, and Performance is out in a new edition. This latest version of the detailed work of the O'Neils includes a new chapter on Object-Relational Structured Query Language (SQL) and its implementations in Oracle and Informix products. On top of that, the authors have revised their chapters on basic and advanced SQL, and added product-specific details (particularly having to do with Oracle, Informix, and IBM DB2 database products) to most areas of their coverage. As a result of these revisions, this book does a great job of balancing academic material with practical examples.
Furthermore, this book does a good job of straddling the schism that's begun to open up in the world of database architecture. Perhaps better than any other volume, this book documents the emerging object-relational strategy for representing data fairly, although most of the authors' coverage (as is fitting) goes to the more firmly established and better-supported relational database model. The authors' style intersperses sequences of theory-oriented prose and diagrams with queries and other listings that have to do with specific implementations, allowing readers to observe many of the phenomena described here. This book is a fine picture of the state of the art, painted with influences from business as well as information science. --David Wall
Topics covered: Modern database design and operation, including basic Structured Query Language (SQL), Object-Relational SQL and the object-relational model, indexing, query parsing, and performance-minded design.
Book Description
This second edition relies on the same successful approach that distinguished the first: it covers the principles of database theory with unmatched thoroughness, and it rigorously links theory to the real world of database programming and administration. A careful discussion of SQL standards and a multitude of examples drawn from actual databases-Oracle, DB2, and Informix-complements the authors' concept-oriented instruction, allowing you to develop product-specific understanding and to learn the important differences between the SQL dialects that will enable you to write portable applications.
* Focuses extensively on the object-relational model that is rapidly gaining acceptance and revolutionizing the database industry. Collection types and UDF's are thoroughly covered.
* Introduces new relational features of SQL taken from the latest versions of today's most popular database products, Oracle, DB2, and Informix.
* Offers thorough coverage of the SQL-99 standard, including additions designed to help you take full advantage of the object-relational model.
* Provides expanded programming examples intended to improve your understanding of transaction processing and error handling.
* Explains clearly the principles of logical database design, including those relating to the E-R model and normalization, with a number of new illustrations and examples.
* Presents the latest indexing and query processing techniques, such as bitmap indexing, and shows how to use them to achieve significant performance improvements.
Customer Reviews:
Poor writing but many various examples.......2004-01-13
Pros:
- many examples
- examples for various databases (Oracle, DBQ, etc.)
Cons:
- poorly written, wordy
- difficult to read
- gives examples for various databases, but each example does
not have a version for each database -> if you want to
learn on a specificat database, you will have holes in the
examples
Overall: Poor book, would not recommend
Best database book for engineers.......2002-12-05
This was my first database book which i have read, and I can honestly say that it made me an expert. All other books which iI read after this one seemed useless and very boring and content-weak. It's a heave book, I do agree on that, and it has too many theoretical and mathematical models applied to designing a database, but those actually make you understand the subject even more. I don't recommend this book for an average computer scientist, it is not appropriate for such a level. But if you're on your way to an engineering degree, I'm sure you will find this book very appealing.
Database: Principles, Programming, Performance.......2002-06-22
This is one of the best books on the subject.
It gives a thorough and solid foundation on the databases.
It helped me quickly identify the weaknesses and strengths in all the leading DBMS products but above all, realized that 80% of all the experts out there in the field, don't know what they are doing.
However, if you have a short attention span, are intimidated by certain dry material and used to books like Databases in 24hrs, this book is not for you.
Worst database book ever--a waste of money!.......2002-04-19
This is the worst computer-science text I have ever read. The explanations are confused and extremely wordy. The writing style is very disorganized. Many examples serve to completely confuse the reader rather than to illustrate a point. My guess is that the authors never bothered to proofread the text carefully.
In short, don't waste your money on this worthless book!
Wordy, redundant, tedious, still a good coverage.......2001-10-10
I agree that this book could be well resumed in 300 pages. Too much text, too few figures. For instance, when you make a classification or an enumeration of things that have long definitions, it is a good idea to organize them in a bullet-list or numbered list or something similar, instead of just plain text. If you constanly fail to use such synthetic representations, the result is made of large chunks of plain text, hard to read, tedious, redundant.
Also, you can use more visual indicators that give you an instant information about various pieces of text: bold text, spaces, various font sizes and shapes, icons, etc, so that the reader can focus on particular sections of such a big book. They call it Readability, and it's far from being great here.
There are also some points left unfinished: when you read "The first idea would be to...", you expect that the second idea follows sometime. Well, there are exceptions in this book.
I like the idea of mixing theory with industry examples in the same book, but please make a clear separation. Sometimes I can't say whether a particular sentence refers to such a real system or it is a theoretical statement.
In conclusion, this book features a good coverage of the subject but also a lack of organization and readability.
Books:
- Country Risk Assessment: A Guide to Global Investment Strategy (The Wiley Finance Series)
- Crypto: How the Code Rebels Beat the Government--Saving Privacy in the Digital Age
- Decision Support Systems and Intelligent Systems (7th Edition)
- Developing Multi-Agent Systems with JADE (Wiley Series in Agent Technology)
- e-Business 2.0: Roadmap for Success (2nd Edition)
- Enabling Knowledge Creation: How to Unlock the Mystery of Tacit Knowledge and Release the Power of Innovation
- Enterprise Architecture As Strategy: Creating a Foundation for Business Execution
- Enterprise Knowledge Management: The Data Quality Approach (The Morgan Kaufmann Series in Data Management Systems)
- Enterprise Security Architecture: A Business-Driven Approach
- Essentials of Management Information Systems: Managing the Digital Firm (6th Edition)
Books Index
Books Home
Recommended Books
- Managers and the Legal Environment: Strategies for the 21st Century
- D.V.
- The Couple's Wedding Survival Manual: How To Tie The Knot Without Coming Unraveled
- The Illustrated Natural History of Selbourne
- Train Your Mind, Change Your Brain: How a New Science Reveals Our Extraordinary Potential to Transfo
- Big Boss Man: The Life and Music of Bluesman Jimmy Reed
- America's Last Wild Horses: The Classic Study of the Mustangs--Their Pivotal Role in the History of
- The Dilemma Deepens: A Box of Unfortunate Events, Books 7-9
- The Global Citizen: A Guide to Creating an International Life and Career
- Tuyo Es El Reino / Thine Is the Kingdom
Management of Construction Projects: A Constructor's Perspective
Construction Cost Estimating: Process and Practices
The Federal Government and Urban Housing: Ideology and Change in Public Policy
Construction Jobsite Management 2e
Building Construction: Principles, Materials, and Systems
