- Paperback: 288 pages
- Publisher: Addison Wesley; 1 edition (21 Dec 1999)
- Language English
- ISBN-10: 0201616068
- ISBN-13: 978-0201616064
- Product Dimensions: 23.1 x 18.5 x 1.5 cm
- Amazon Bestsellers Rank: 2,211,436 in Books (See Top 100 in Books)
- See Complete Table of Contents
Did you know you can trade in your old books for an Amazon.co.uk Gift Card to spend on the things you want? Visit the Amazon.co.uk Trade-In Store for more details. |
Product details |
More About the Author
Product Description
Product Description
It is a costly fact that a large percentage of information system development projects fail--ending up over budget, behind schedule, or so poorly designed that they remain unused. Essential System Requirements targets the discovery and definition of critical system requirements in the analysis phase of system development--where good design is vital to the success of a project. This book explores a design methodology that involves users early on to describe essential business events. These events then partition the system response into logical, more easily managed segments. The result is a conceptual model that reflects real business needs and accelerates the entire delivery process. Essential System Requirements assembles the information developers need to understand and apply this methodology and condenses it into a concise and practical guide. This book reviews the development life cycle, highlights the importance of requirements, and introduces the concept of business events.It provides a detailed description of experience-based techniques and methods to analyze, specify, and partition the requirements of an information system, covering project tasks and procedures, system behavior, data and process modeling techniques, and the transition to physical design. Inside you will also find a clear description of function point estimation, a promising method of estimating the time and cost of future software projects based on system requirements. In addition, Essential System Requirements shows you how responses to business events can be partitioned across object classes, focusing on the application of use cases in event-driven requirements analysis. Also featured: *A middle-out strategy that is similar to the way humans typically categorize and classify objects. *The need for rapid development combined with a sound, scalable software architecture (RAAD). *A discussion of the changing world market and the related need for adaptive business systems. *The impact of making a major paradigm switch in a corporate software environment and ways to move to an event-driven approach.*The specification of a system response to an event using a business scenario, data model, process model, entity life cycle, and event/entity interaction (CRUD) matrix. With this book as your guide, you will have at hand proven techniques for defining the systems your clients want and setting the stage for a smoother, faster, more easily managed development process. 0201616068B06012001
From the Back Cover
It is a costly fact that a large percentage of information system development projects fail--ending up over budget, behind schedule, or so poorly designed that they remain unused. Essential System Requirements targets the discovery and definition of critical system requirements in the analysis phase of system development--where good design is vital to the success of a project. This book explores a design methodology that involves users early on to describe essential business events. These events then partition the system response into logical, more easily managed segments. The result is a conceptual model that reflects real business needs and accelerates the entire delivery process.
Essential System Requirements assembles the information developers need to understand and apply this methodology and condenses it into a concise and practical guide. This book reviews the development life cycle, highlights the importance of requirements, and introduces the concept of business events. It provides a detailed description of experience-based techniques and methods to analyze, specify, and partition the requirements of an information system, covering project tasks and procedures, system behavior, data and process modeling techniques, and the transition to physical design. Inside you will also find a clear description of function point estimation, a promising method of estimating the time and cost of future software projects based on system requirements. In addition, Essential System Requirements shows you how responses to business events can be partitioned across object classes, focusing on the application of use cases in event-driven requirements analysis. Also featured:- A middle-out strategy that is similar to the way humans typically categorize and classify objects.
- The need for rapid development combined with a sound, scalable software architecture (RAAD).
- A discussion of the changing world market and the related need for adaptive business systems.
- The impact of making a major paradigm switch in a corporate software environment and ways to move to an event-driven approach.
- The specification of a system response to an event using a business scenario, data model, process model, entity life cycle, and event/entity interaction (CRUD) matrix.
0201616068B06012001
Tag this product(What's this?)Think of a tag as a keyword or label you consider is strongly related to this product.
Tags will help all customers organise and find favourite items. |
Sell a Digital Version of This Book in the Kindle Store
If you are a publisher or author and hold the digital rights to a book, you can sell a digital version of it in our Kindle Store.
Learn more
Customer Reviews
|
There are no customer reviews yet on Amazon U.K.
|
||||||||||||||||||||
|
Most Helpful Customer Reviews on Amazon.com (beta)
Amazon.com:
3.8 out of 5 stars (4 customer reviews)
3 of 3 people found the following review helpful:
5.0 out of 5 stars
UML is just a tool, Wiley tells us how to use the tool., 3 Sep 2000
By Norman L. Kerth "Norm Kerth" - Published on Amazon.com
This review is from: Essential System Requirements: A Practical Guide to Event-driven Methods (Information Technology) (Paperback)
Bill Wiley has written a very important book! He brings to light key discoveries made during the structured revolution and explains them to us in the context of modern day object-oriented thinking -- but I get ahead of myself:Before objects, many great minds worked on the problem of how do we improve the process of analyzing and designing software systems." These methodologists integrated their discoveries under the umbrella called the structured methodology.
When objects came along, the new generation of software experts and methodologists rejected all ideas associated with the structured revolution largely due to ignorance, or ego. While some of the basic notation of structured design did not fit object-oriented thinking, the deeper wisdom of how to approach systems and understand what needs to be built was still most applicable.
Essential systems analysis, a core tool for thinking about systems, has been (PICK ONE: rediscovered, dusted off, repackaged, rehabilitated) by Bill at the perfect time for the evolution of object-oriented methodology maturity. With UML established, we are no longer arguing about how to express an idea and now must turn our attention to the harder questions of how to use UML to approach problems and in particular discover Use Cases.
Bill's book answers these questions and his ideas feel as good to me as my grandfather's old hand plane -- both are time-tested tools to solve problems in a most elegant and effective manner.
5 of 6 people found the following review helpful:
3.0 out of 5 stars
Some excellent content, but bad style, 19 May 2000
By Travis Cottreau - Published on Amazon.com
This review is from: Essential System Requirements: A Practical Guide to Event-driven Methods (Information Technology) (Paperback)
This is a good book. It has all the information in it to facilitate gathering software requirements for pretty much any IT project.My problem with the book is the author's style, he just isn't very readable. There is a lot of passive voice and not very many examples of the ideas he presents. If there are examples, they tend to be collected at the back in an appendix where they are much less useful than they would be directly with the idea that needs an example.
I feel that the author settled for a less than his best in this book, and frequently stops partway along a direction that would have been much better if it were carried through more fully.
There is a little bit of covereage of Entity Relationship Diagrams (ERD), but he gives only a handful of examples and then immediately give a diagram in a section with symbols that aren't covered in any of the previous examples.
I was really looking forward to the function point covereage, but function points are covered only marginally well in the book, something that the author pretty much says himself in the first few paragraphs of the chapter on function points.
The real strength of the book is in the ideas, which I found very useful. The business event approach is quite powerful and allows the breakdown of projects into independant pieces. Also, the author gives "tips" on project management on how to apply his methods. There are a number of tables and diagrams for representing requirements that were also helpful.
A good effort, but I feel that it could have been much better. All the ideas where there, the author mentions them regularly, but just doesn't go all the way.
1 of 1 people found the following review helpful:
5.0 out of 5 stars
Ties it all together!, 3 Aug 2000
By Thomas R. Wilk - Published on Amazon.com
This review is from: Essential System Requirements: A Practical Guide to Event-driven Methods (Information Technology) (Paperback)
Mr. Wiley takes an interesting, academic approach to defining requirements based upon event-driven methods. Essential System Requirements is "a breath of fresh air" that uses a variety of diagramming techniques including the UML, but does not push the UML or a set of vendors' tools as a silver bullet. The book does an outstanding job of tying together a sound toolbox approach to extracting requirements with the function point estimation method. The section on object-partitioned system responses is also very enlightening. A must read for the independent thinker!
Listmania!
Look for similar items by category
Look for similar items by subject
Feedback
- Would you like to update product info or give feedback on images?
- I am the Author, and I want to comment on my book.
- I am the Publisher, and I want to comment on this book.
