Book Description
Use Case Driven Object Modeling with UML--Theory and Practice shows how to drive an object-oriented software design from use case all the way through coding and testing, based on the minimalist, UML-based ICONIX process. In addition to a comprehensive explanation of the foundations of the approach, the book makes extensive use of examples and provides exercises at the back of each chapter.
This book leads by example. It demonstrates common analysis and design errors, shows how to detect and fix them, and suggests how to avoid making the same errors in the future. The book also encourages you to examine its UML examples and to search for specific errors. You'll get clues, then later receive the answers during "review sessions" toward the end of the book.
Customer Reviews:
A recommended read for anyone........2007-08-23
This book does everything it promises and more. While reading this book you will learn a design methodology that will help you in every project you work on. What you won't learn is a framework that does all the work for you. You also won't learn to rely on someone else's code. Instead you will learn how to really think about your project from the initial design to the final solution. You will learn how to properly document the requirements and the user interaction with the system. You will learn how to be a Software "Developer" not just a Software "Programmer". Some will say there is no difference, but others that have read this book will understand the work and thought process that goes into real development of a software solution.
The best, most practical Business Analyst guide.......2007-08-10
This book puts the whole business analysis process into perspective with a practical guide for how to go from step A to step Z. I am new to the ICONIX process and am very impressed with how ICONIX eliminates the burden of learning all the steps of UML and instead teaches in detail just the essential components of UML, so you can quickly develop the use cases, requirements, test cases, and coding specifications. The book is written with the business analyst in mind by highlighting the theory, but concentrating and demonstrating the practices with straight forward guidelines and examples. The Enterprise Architect modeling tool, which we are learning how to use, is referenced occasionally and is shown to be a very useful tool for the business analyst. This is one of the finest IT books I have ever purchased.
Feeble.......2007-07-09
If your domain model consists of webpages and form validation and if page navigation is your big problem, this book is for you. (In modern development however, we use frameworks to solve those problems.) This book will be useful for those people on your project who think that Struts2, Spring web flow and Velocity are all inadequate for page navigation; you'll want to give them some stone tools so they can reinvent the wheel. The examples in this book so remind me of the concerns we had in the 90s with the JSP development.
Great methodology, well explained.......2007-05-26
The book combines explaining how to drive use cases to code and lots of examples. In fact one of the best parts is the 'bad example' followed by the corrected version - lots of those.
Iconix is pretty easy to use ONCE YOU UNDERSTAND IT. This book goes a long way toward understanding how to write good use cases that CAN be used for software development rather than just documentation.
I've read many, many use case books and this one boils the details down to something that is pragmatic. I've used the Iconix technique in both industry and the university and it works in both areas.
Good book? Yes. Buy it? Yes!
Well Written & Great Methodology.......2007-05-19
Easily one of the best methodology books I've read in quite some time. The book is very well written and flows very well. The structure walks you through the entire ICONIX process from beginning to end and explains in-detail the steps involved and most importantly "why". I also liked how the authors referenced other highly ranked OO books to reinforce how to allocate behavior to your objects during sequence diagraming.
I never heard of ICONIX until recently and I was very happy I got this book. The process is logical, stream-lined, and easy to pickup. The chapter on sequence diagrams just clicked for me and brought everything together.
I highly recommend this book!
Customer Reviews:
Best Use Case format for your clients.......2007-07-20
Here is the scenario... you're a business analyst that is attempt to show business clients the value of writing use cases. Many books exist with various ways to format the use case. You take all those books and write the same use case in all the different formats. Guess which one the business looked at and understood? You got it. The really fine work of Bittner and Spence. If you use a table driven methodology, your clients won't be happy. The use case structure that is recommended in this book has been used in many projects where I currently work, and they have been very successful in forming a dialog with the clients as to how they need to the use the system and what true value they get out of it. The key part of this book is the concept of maturity of the use case. This is something that you can schedule in a project plan and demonstrate to the customers. Great job guys.
Very Pleased.......2007-01-12
The subject matter in the book provided me with the information that I needed to go forward on my project.
great info - terrible editing.......2006-07-21
This book came so highly recommended it seemed like a sure thing. And in fact, it has a wealth of info on use cases; I can certainly see it being a valuable reference for someone who is already an expert with use cases. For those with no previous exposure, however, it is a tiresome morass to wade through; so cluttered and muddled that finding the underlying meaning becomes a real challenge. This book could have been edited to 2/3rds the size, and been a far better book because of it. Was the editing staff on vacation?
The BEST book about use cases.......2005-10-06
I teach the official IBM Rational training called Requirements Management with Use Cases here in Brazil.
Basically this IBM training is based on this book.
It saved me a lot of time during my consulting period helping companies to create a better requirements management process using use case modeling.
I always tell all my students: If you can buy only one book about use cases (and an excellent introduction about Vision artifact and stakeholders also) then buy this one !!!!
Great book.......2005-04-14
This is the best book i have read on use case modeling. Pitfalls are covered in great detail. The book is well structured. The only negative thing i can think off, if I have to state one, is that the author sometimes gives better definitions of terms in places where you would not expect to find them. Still all definitions are more consistent, than I have seen in other books related to usecase modeling.
Book Description
Since its original introduction in 1997, the Unified Modeling Language has revolutionized software development. Every integrated software development environment in the world -- open-source, standards-based and proprietary -- now supports UML, and more importantly the model-driven approach to software development. This makes learning the newest UML standard UML 2.0, critical for all software developers -- and there isn't a better choice than this clear, step-by-step guide to learning the language.
Richard Mark Soley, Chairman and CEO, OMG
If you're like most software developers you're building systems that are increasingly complex. Whether you're creating a desktop application or an enterprise system, complexity is the big hairy monster you must manage.
The Unified Modeling Language (UML) helps you manage this complexity. Whether you are looking to use UML as a blueprint language, a sketch tool or as a programming language, this book will give you the need to know information on how to apply UML to your project. While there are plenty of books available that describe UML, Learning UML 2.0 will show you how to use it. Topics covered include:
- Capturing your system's requirements in your model to help you ensure that your designs meet your users' needs
- Modeling the parts of your system and their relationships
- Modeling how the parts of your system work together to meet your system's requirements
- Modeling how your system moves into the real world, capturing how your system will be deployed
Engaging and accessible, this book shows you how to use UML to craft and communicate your project's design. Russ Miles and Kim Hamilton have written a pragmatic introduction to UML; based on hard earned practice, not theory. Regardless of the software process or methodology you use, this book is the one source you need to get up and running with UML 2.0. Additional information including exercises can be found at http://www.learninguml2.com
Russ Miles is a software engineer for General Dynamics UK where he works with Java and Distributed Systems, although his passion at the moment is Aspect Orientation and in particular AspectJ. Kim Hamilton is a senior software engineer at Northrop Grumman, where she's designed and implemented a variety of systems including web applications and distributed systems, with frequent detours into algorithms development.
Customer Reviews:
UML 101.......2006-11-29
This book could have been titled UML 101, because it is very readable. However it assumes that the reader knows a bit of an object oriented language, in particular Java. Chapters 4 thru 7 demonstrate how UML diagrams are used to model OOP principles such as class inheritance, interfaces, and messaging using Java snippets of code. This is an important part of the book, but it isn't a show stopper for those unfamiliar with object oriented concepts. The authors briefly explain what classes are; they also define abstraction, encapsulation, state, and behavior.
I Highly recommend this book for getting familiar with UML.
In particular:
- It's very readable.
- It is not specific to any UML software tool, only the standard symbols and diagram layout practices.
- It is a book that you could open up to any page and browse.
- As a future reference.
Good and Handy.......2006-11-17
Nice to read and quick to understand with the illustrations. Well described examples and after going through the frist few models you would able to quick start building the models. Overall, It is recommended for a one time read.
Good conversational approach that builds on itself..........2006-09-30
Based on a recent project at work, I realized I needed a better understanding of UML. To that end, I decided to review the book Learning UML 2.0 by Russ Miles and Kim Hamilton. While there's still a lot to learn there, I think I have a much better grasp on what's going on...
Contents: Introduction; Modeling Requirements - Use Cases; Modeling System Workflows - Activity Diagrams; Modeling a System's Logical Structure - Introducing Classes and Class Diagrams; Modeling a System's Logical Structure - Advanced Class Diagrams; Bringing Your Classes to Life - Object Diagrams; Modeling Ordered Interactions - Sequence Diagrams; Focusing on Interaction Links - Communication Diagrams; Focusing on Interaction Timing - Timing Diagrams; Completing the Interaction Picture - Interaction Overview Diagrams; Modeling a Class's Internal Structure - Composite Structures; Managing and Reusing Your System's Parts - Component Diagrams; Organizing Your Model - Packages; Modeling an Object's State - State Machine Diagrams; Modeling Your Deployed System - Deployment Diagrams; Object Constraint Language; Adapting UML - Profiles; A History of UML; Index
Miles and Hamilton use a conversational approach to introduce the reader to UML 2.0, and they build on a model that makes sense. The Use Case view drives nearly everything, as that's the "what" of what the system is supposed to be able to do. Then they cover the logical, process, physical, and development views that support the system and show different perspectives of what the system will look like depending on which angle you view it from. All too often, it seems like UML diagrams are just thrown at the reader one after another, and there's no real explanation as to how it all fits together. Fortunately, that's not the case here, as the model framework for their tutorial puts everything in the right relationship to each other. I also appreciated how the diagram tutorials started out with just the basics and built from there. Again, it's common to see a tutorial diagram with every possible permutation thrown in right at the start. As such, it's far too easy to zone out right away because of all the baggage. Here, you get the core elements of the diagram first (which often cover 80 - 90% of what you need to know anyway), and then the extra details are introduced after that. I was much better able to conceptualize the whole discussion when put in that light... Very nice job...
I would say that if you have this book coupled with a full UML 2.0 reference manual of some sort, you'd be pretty well set to do most anything you'd need to in the world of UML. I know I'm better equipped to do those sequence diagrams now, where before I was faking it pretty well... :)
UML Definitely Made Easy.......2006-05-19
Easy to understand -- great diagrams -- I highly recommend this book.
The are much better options.......2006-05-12
Unfortunately, this book is so poorly written that it is often confusing. Especially for a beginner, I highly recommend obtaining a copy of Pilone's book instead. The examples are much clearer and easier to follow, and the exposition is extremely clear.
Amazon.com
Combining some of today's best ideas about customer-driven object-oriented design, Use Case Driven Object Modeling with UML: A Practical Approach shows you how to use Unified Modeling Language (UML) in the real world, keeping with the author's proprietary software design process.
The book begins with the genesis of the author's ICONIX Unified Object Modeling Approach, borrowing ideas and strategies from the "three amigos" who invented UML: Grady Booch, James Rumbaugh, and Ivar Jacobson. Throughout this text, the ICONIX method is used to model a stock trading system, with all the relevant UML diagrams, beginning with class definition and use cases.
The author's approach to software relies heavily on customer requirements and use case scenarios for which he has a good deal of practical advice. He provides numerous hints for avoiding bogged-down diagrams. After preliminary design, he advocates drilling down into specifics with robustness diagrams, which trace how classes interact with one another. The most detailed design work comes next with sequence diagrams.
Subsequent chapters offer tips on project management, implementation, and testing. Throughout this lively and intelligently organized book, the author presents numerous real-world tips (and Top 10 lists) that supply wisdom to his perspective on effective software design.
Written for the reader who already knows a little UML notation, Use Case Driven Object Modeling with UML provides an appealing blueprint for the software design success. --Richard Dragan
Customer Reviews:
More practical...but still a tad too much for my tastes.......2007-06-19
I liked a lot of the book but still felt much of it was too much BUFD, at least for what I do. As with any UML book or article I find myself lost between the similarities and subtle differences between many of the diagrams. I figure that if I am lost then surely the business experts and stakeholders I am working with will be too. The best thing I take away from this book is the real need to develop a high-level model, develop solid use cases or user stories, and then flesh out the model to handle these user stories.
I give it 4 stars because what is too much or too little in regards to UML and modeling in general is highly subjective and should not detract from the quality of the book.
Ditto this NOT being Unified Process.......2004-03-02
I had to read this book for a class I took. Here is my interpretation of the purpose of this book:
"I think the world should have used my ICONIX process! This UML stuff is inferior. I hate UML, but I will use it to sell my book."
Fortunately, the class also used Martin Fowler's great UML Distilled book. If you want to know about UML, get that one instead!
Not Unified Process.......2003-07-03
If you are looking for a book on the Unified Process (as I was), then this book is not for you. This book covers the author's Iconix process. Considering the book's title I would have expected it to examine use cases and UML more than it does.
I was really intereted in the Unified Process. But, the Iconix methodology is a good one, and were it to be more prevalent in the industry I would take a harder look at it.
Heresy! This is ICONIX, a compact method borrowing UML.......2002-04-01
This is the eighth software engineering title that uses the UML (Unified Modeling Language) that I have read in the last five months as I work to establish a software engineering guide and reference framework for a small team at my technology company. This book really sets forth the ICONIX methodology, the author's streamlined approach to modeling using mostly, but not only, UML.
Because of the author's quarrelsome nature and unusual departures from common progressions in the model views, I found this book less useful than the others. The author repeatedly explains (with a careful record of the dates) how much of his integration of the competing OO modeling methods preceded the work of the UML founders (Booch, Jacobson, and Rumbaugh) and frequently raises the small quarrels in the UML world for no purpose except to give a quick and unsupported opinion. Not surprisingly, ten of the twenty-five citations in the bibliography are the author's prior papers.
Although the title claims the method is "use case driven," techniques and guidelines for use cases are poorly done; and the author suggests that the requirements stage should begin with domain modeling and "robustness diagrams" before text for use cases is written. The author also places heavy emphasis on screen mockups during the requirements stage.
The contents would make a good lecture or two; but it is an annoying departure from the efforts of many to extend and enrich UML. Since the book is only 165 pages, it won't hurt for long, and there are thoughts here and there worth reading. Perhaps it's tongue-in-cheek, a test to see if we can spot obvious logical problems with the method.
The title is misleading.......2002-02-27
I expected this book to delve more into UML and use cases than it does. It really is a book about the ICONIX methodology. It only deals with UML and use cases at a high level.
The robustness analysis is interesting and may help people who have trouble linking the user interface to the model.
If you are looking for a book on the ICONIX methodology then this book is for you. If you are looking for a book on UML or use cases then this is not the right book.
Customer Reviews:
Advanced Use Case Modeling: Software Systems.......2006-03-01
This book was nice .it was NEW.I never thought I will get a New book for less cost.
Tells you how to start and when to stop.......2001-10-23
I have found this book of tremendous help in my work.
My first books on use cases focused more on UML rather than use cases. I did not give a hoot on use cases, because they look so simple on paper (and that's why I didn't buy a book specifically on use cases!) But as I grew as a developer, I began to believe that use case modelling if done well can significantly reduce development effort and bring about quality solutions. Use cases are the foundation to the understanding of the system that you are trying to develop. Use cases deserve serious attention.
The main problem with use cases is that you either don't know how to start or when to stop. This book tells you both. It tells you how to develop your use case model systematically from scratch and how to make provisions so that your use case model can grow. IMO, that's the main draw for this book.
The authors also give good insights on the possible approaches the reader can take to expand his/her use case model iteratively. It cautions the modeller to keep a balanced model so that stakeholders can understand, rather than one that specifies everything but gets bogged down by the details.
Semantics, you can get it elsewhere, but this book discusses it pretty well too. The examples are clear and relevant.
All in all, Frank and Granville did an excellent job covering the topic.
An Outstanding Guide for Experienced Practioners.......2001-10-12
It is refreshing to a read a text that caters for those of use who already have experience in this domain and are seeking to develop their skills - without reverting to acadamia style writing. Useful examples, balanced descriptions, and an excellent coverage are all attributes of this text.
Excellent practical guide.......2001-04-20
I strongly recommend this book!
A very thorough and well-written book.......2001-02-06
This book has some powerful advice for those projects that use Use Cases to drive their analysis and design efforts. It lays out a good process to follow for developing the Use Cases so you don't jump right into the details without a plan. Much of the advice is good Software Engineering practices, but a lot of people seem to forget that it still applies even when making use of newer techniques such as Use Cases.
The chapters pertaining to relating the Use Cases to other artifacts - such as test cases, the User Interface, and the Object Model - offer very practical and sound advice. You can tell that the authors have actually done it before and are speaking from experience and lessons learned.
The chapter explaining Extend Relationships offered the clearest and most complete description of the Extend Relationship that I have encountered.
All of the writing is very approachable and the examples sprinkled throughout the book and in the Appendixes are very helpful.
Customer Reviews:
An expense that can be justified........2002-05-24
You are already into various Java technologies like
Servlets, JDBC, EJBs and can put together a
small to medium application/project using those.
You somehow implemented the project/app to
satisfy the requirements but you are thinking
that there has to be a better way of going from
a set of requirements to a design (from which the leap to
actual coding is smooth) without feeling like
some vague unrepeatable 'magic' was being done.
You want to formalize the process of jumping from the
'analyze' phase to a 'Object oriented design' phase (that
results in sequence/collaboration diagrams etc) but
without being encumbered by an elaborate and complex
methodology.
You want this process to be small, easy to understand
and flexible so that you can adapt it to your needs.
If the above applies, you should seriously consider
investing in this book.
The Authors use the often used bookstore example to drive
home the process which starts with writing usecases
and ends with a detailed design that satisfies all the
user's requirements.
A list of 10 common mistakes made during each step of
the process can be used as a reference when you are
done understanding the process and are actually applying
it in your projects.
Paul Reed's Application Development with Java and UML
makes a good complement to this book, though
Conallen uses a modified but still complex enough form
of Rational Unified Process (RUP) in his book.
Pricey for what it provides.......2002-01-16
I was excited about this book when I bought it online. Now that I read it, I am not very happy. The authors could have drilled deeper into some examples of how to implement the application using some wide spread technology like Java or ASP and COM. Giving concrete examples of what a Boundary Object should be, or what classes make sense to implement to interact with databases, just to mention a few, would have been very helpful. I also found "the top ten error" method very tiresome (I often skipped it and went straight to the right ways of doing things). The book was helpful though in providing a guide of what steps to follow in the design process as well as giving us a good idea on how to break the project into objects and diagrams.
A practical follow-up.......2001-08-03
Okay. I became interested in the lightweight Iconix process after a series of 5 articles in Software Development magazine, so I went out and bought the first book "Use case driven object modeling with UML - a practical approach".
I design community based web portal applications. Our applications are medium-sized, but complex. So RUP is too big, and XP is too small. The Iconix process presented here is about right for most of our applications, and to satisfy client expectations for design.
The first book is more theoretical. This one has better, more complete, illustrative examples. There is some repetition between the two, but no pages are taken up by code. Like the first book, it is easy to read.
If you work in web development, read Conallen's "Building web applications with UML" also. The books complement each other well. (See my review)
Learn object modeling by example with solution.......2001-06-30
All of the different jobs found in software development are learned in two ways. Either through trial and error on the job or by working through examples. The first is the most effective, but by far the most expensive. While the second is less thorough, it is cheaper and reduces the cost when you make the inevitable move to the first. Since object modeling is always open to many differing interpretations, learning how to create and use them has a slow learning curve. The best approach to learning how to model objects is to find and plow through detailed, complete examples, which of course presupposes that such examples exist. Well, they do and some of the best are found in this book.
The approach is one that maximizes the teaching effectiveness. An Internet bookstore project is created from the beginning. It is large enough to be instructive yet not so large that it becomes unwieldy. The authors then take you through the sequence of steps:
1) Domain Modeling, 2) Use Case Modeling, 3) Requirements Review, 4) Robustness Analysis, 5) Preliminary Design Review, 6) Sequence Diagrams, and 7) Critical Design Review.
What is different about this book is that after the explanation of the development stage, there is a top ten list of common errors made in that stage followed by an example described in UML. The UML diagram includes some of the errors in the list and they are pointed out and explained. This really drives the point of the error home.
The book is a distillation of the experience of the authors as they built a comparable system. They documented the complete process via videotape and then distilled their actions, including errors, down to the material in the book. This has led to some very good examples of how to model development at all stages and will certainly help you avoid some of the most common pitfalls as you make the treacherous, exhaustive and gratifying move from idea to product.
Average customer rating:
|
Contracts, Scenarios and Prototypes: An Integrated Approach to High Quality Software
Reinhold Ploesch
Manufacturer: Springer
ProductGroup: Book
Binding: Hardcover
 Object-Oriented Design
| Software Design, Testing & Engineering
| Programming
| Computers & Internet
| 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
| Computers & Internet
| Subjects
| Books
General
| Software Engineering
| Computer Science
| Computers & Internet
| Subjects
| Books
General
| Software
| Computers & Internet
| Subjects
| 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
ASIN: 3540434860 |
Book Description
The number of methods and tools available to the software engineer nowadays is overwhelming; nevertheless many software projects fail to meet their schedules, are over budget, do not meet the user requirements, or simply have considerable quality defects.
Reinhold Ploesch emphasizes methods, techniques and tools that can be used by typical software engineers in everyday projects. The important requirements for the methods and techniques presented are simplicity, preciseness, generality and expressiveness; the challenge is to develop approaches that are balanced in the sense that all four requirements are fairly equally fulfilled. His approach combines contract and scenario techniques into a consistent methodology that can be used in analysis and design. It can also be combined with prototyping-based software development.
Graduate students and researchers will gain a thorough understanding of contract techniques and related approaches. Professional software engineers will find many techniques applicable in their daily work, as all approaches given are compared with techniques available in the realm of the popular UML language.
Average customer rating:
|
Objektorientierter Softwareentwurf: Integration mit UML
Ruth Breu
Manufacturer: Springer
ProductGroup: Book
Binding: Paperback
Software Development
| Software Design, Testing & Engineering
| Programming
| Computers & Internet
| Subjects
| Books
UML
| Software Design, Testing & Engineering
| Programming
| Computers & Internet
| Subjects
| Books
Logic
| Software Design, Testing & Engineering
| Programming
| Computers & Internet
| Subjects
| Books
General
| Programming
| Computers & Internet
| Subjects
| Books
German
| Foreign Language Nonfiction
| Nonfiction
| Subjects
| Books
Nonfiction
| German
| Foreign Language Books
| Specialty Stores
| Books
All German Books
| German
| Foreign Language Books
| Specialty Stores
| Books
ASIN: 3540412867 |
Book Description
Das Buch vermittelt die grundlegenden Konzepte und Zusammenhänge objektorientierter Entwurfsmethoden. Im Mittelpunkt stehen dabei die graphischen Beschreibungstechniken der Unified Modeling Language (UML). Neben einer kurzen Einführung in Klassen-, Sequenz- und Zustandsdiagramme wird der Leser zunächst mit den Grundbegriffen objektorientierter Systemmodellierung vertraut gemacht. Im Vordergrund steht das Zusammenspiel der unterschiedlichen Diagrammtypen und ihre methodische Verwendung im Use-Case-gesteuerten Entwurf.Das Buch, das nur Grundkenntnisse in objektorientierter Technologie voraussetzt, wendet sich sowohl an Praktiker als auch an Studierende und Lehrende. Es bietet aber auch neue Ansätze, die es für Wissenschaftler interessant machen. Durch seine Einordnung von Konzepten vermittelt es ein tiefgehendes Verständnis der Techniken und der Methodik des objektorientierten Entwurfs - als Grundstein für den effizienten Einsatz in der Praxis.
Average customer rating:
|
A Case Study Evaluation of the Use of the Viable System Model in Information Systems Development.(Technology Information): An article from: Journal of Database Management
P. Kawalek , and
D.G. Wastell
Manufacturer: Idea Group Publishing
ProductGroup: Book
Binding: Digital
Nonfiction
| Subjects
| Books
| Automotive
| Books on CD
| Books on Cassette
| Crime & Criminals
| Current Events
| Economics
| Education
| Foreign Language Nonfiction
| Government
| Holidays
| Law
| Philosophy
| Politics
| Social Sciences
| Transportation
| True Accounts
| Urban Planning & Development
| Women's Studies
Management
| Management & Leadership
| Business & Investing
| Subjects
| Books
Database Design
| Databases
| Computers & Internet
| Subjects
| Books
Database Management Systems
| Databases
| Computers & Internet
| Subjects
| Books
Object-Oriented Design
| Software Design, Testing & Engineering
| Programming
| Computers & Internet
| Subjects
| Books
General
| Programming
| Computers & Internet
| Subjects
| Books
Management
| Business & Investing
| Subjects
| e-Docs
| Formats
| Books
Programming
| Computers & Internet
| Subjects
| e-Docs
| Formats
| Books
General
| Nonfiction
| HTML
| Formats
| e-Docs
| Formats
| Books
ASIN: B00099OZF8
Release Date: 2005-07-28 |
Book Description
This digital document is an article from Journal of Database Management, published by Idea Group Publishing on October 1, 1999. The length of the article is 6522 words. The page length shown above is based on a typical 300-word page. The article is delivered in HTML format and is available in your Amazon.com Digital Locker immediately after purchase. You can view it with any web browser.
Citation Details
Title: A Case Study Evaluation of the Use of the Viable System Model in Information Systems Development.(Technology Information)
Author: P. Kawalek
Publication:
Journal of Database Management (Refereed)
Date: October 1, 1999
Publisher: Idea Group Publishing
Volume: 10
Issue: 4
Page: 24
Distributed by Thomson Gale
Book Description
This digital document is an article from Journal of Database Management, published by Idea Group Publishing on October 1, 2000. The length of the article is 7427 words. The page length shown above is based on a typical 300-word page. The article is delivered in HTML format and is available in your Amazon.com Digital Locker immediately after purchase. You can view it with any web browser.
Citation Details
Title: Understanding the Role of Use Cases in UML: A Review and Research Agenda(1).(Technology Information)
Author: Brian Dobing
Publication:
Journal of Database Management (Refereed)
Date: October 1, 2000
Publisher: Idea Group Publishing
Volume: 11
Issue: 4
Page: 28
Distributed by Thomson Gale
Books:
- VBScript Programmer's Reference (Programmer to Programmer)
- Web Design in a Nutshell: A Desktop Quick Reference (In a Nutshell (O'Reilly))
- Windows Presentation Foundation Unleashed (WPF) (Unleashed)
- Working with Microsoft Dynamics(TM) CRM 3.0
- World of Warcraft: The Burning Crusade Official Strategy Guide (World of Warcraft)
- World of Warcraft: The Burning Crusade Official Strategy Guide (World of Warcraft)
- A Practical Guide to Linux(R) Commands, Editors, and Shell Programming
- Adobe Photoshop CS2 One-on-One (One-On-One)
- Ajax in Action
- Apache: The Definitive Guide (3rd Edition)
Books Index
Books Home
Recommended Books
- Introduction to Health Occupation: Today's Health Care Worker, Sixth Edition
- Dreams from My Father: A Story of Race and Inheritance
- Using Sap R/3 Fi: Beyond Business Process Reengineering
- A Very Dangerous Citizen: Abraham Lincoln Polonsky and the Hollywood Left
- Business Analysis and Valuation: Using Financial Statements, Text and Cases
- Distant Pleasures: Alexander Pushkin and the Writing of Exile
- Colonial America in an Atlantic World
- El Proceso Decisional y Los Costos
- ARCH: Selected Readings
- Archie's Way: A Memoir of Friendship and Craftsmanship
Agile Development with ICONIX Process: People, Process, and Pragmatism
UML 2 Certification Guide: Fundamental & Intermediate Exams (The OMG Press)
The Elements of UML 2.0 Style
UML for the IT Business Analyst: A Practical Guide to Object-Oriented Requirements Gathering
Writing Effective Use Cases
Practical Subversion, Second Edition (Expert's Voice in Open Source)
Founders at Work: Stories of Startups' Early Days
