Senin, 20 Februari 2012

[F195.Ebook] Download PDF Requirements Analysis and System Design: Developing Information Systems with UML, by Leszek A. Maciaszek

Download PDF Requirements Analysis and System Design: Developing Information Systems with UML, by Leszek A. Maciaszek

Requirements Analysis And System Design: Developing Information Systems With UML, By Leszek A. Maciaszek. Haggling with reviewing behavior is no requirement. Reading Requirements Analysis And System Design: Developing Information Systems With UML, By Leszek A. Maciaszek is not type of something sold that you could take or not. It is a thing that will alter your life to life much better. It is the thing that will make you many points worldwide as well as this universe, in the real life and also here after. As exactly what will certainly be provided by this Requirements Analysis And System Design: Developing Information Systems With UML, By Leszek A. Maciaszek, exactly how can you haggle with things that has many advantages for you?

Requirements Analysis and System Design: Developing Information Systems with UML, by Leszek A. Maciaszek

Requirements Analysis and System Design: Developing Information Systems with UML, by Leszek A. Maciaszek



Requirements Analysis and System Design: Developing Information Systems with UML, by Leszek A. Maciaszek

Download PDF Requirements Analysis and System Design: Developing Information Systems with UML, by Leszek A. Maciaszek

Just for you today! Discover your favourite publication right below by downloading and install as well as obtaining the soft documents of guide Requirements Analysis And System Design: Developing Information Systems With UML, By Leszek A. Maciaszek This is not your time to commonly visit the e-book establishments to purchase an e-book. Below, ranges of e-book Requirements Analysis And System Design: Developing Information Systems With UML, By Leszek A. Maciaszek and collections are offered to download and install. One of them is this Requirements Analysis And System Design: Developing Information Systems With UML, By Leszek A. Maciaszek as your favored e-book. Getting this book Requirements Analysis And System Design: Developing Information Systems With UML, By Leszek A. Maciaszek by on-line in this website can be recognized now by visiting the web link page to download and install. It will certainly be very easy. Why should be below?

Exactly how can? Do you think that you do not require sufficient time to go for buying book Requirements Analysis And System Design: Developing Information Systems With UML, By Leszek A. Maciaszek Don't bother! Merely rest on your seat. Open your gadget or computer system and be online. You can open up or check out the link download that we supplied to obtain this Requirements Analysis And System Design: Developing Information Systems With UML, By Leszek A. Maciaszek By through this, you can get the on-line publication Requirements Analysis And System Design: Developing Information Systems With UML, By Leszek A. Maciaszek Checking out the publication Requirements Analysis And System Design: Developing Information Systems With UML, By Leszek A. Maciaszek by on the internet can be actually done effortlessly by conserving it in your computer and gadget. So, you could continue each time you have spare time.

Reading the book Requirements Analysis And System Design: Developing Information Systems With UML, By Leszek A. Maciaszek by on the internet can be likewise done easily every where you are. It appears that hesitating the bus on the shelter, waiting the list for line, or other locations possible. This Requirements Analysis And System Design: Developing Information Systems With UML, By Leszek A. Maciaszek could accompany you during that time. It will not make you feel weary. Besides, through this will additionally enhance your life high quality.

So, simply be below, discover guide Requirements Analysis And System Design: Developing Information Systems With UML, By Leszek A. Maciaszek now as well as check out that promptly. Be the first to review this e-book Requirements Analysis And System Design: Developing Information Systems With UML, By Leszek A. Maciaszek by downloading and install in the web link. We have other publications to read in this internet site. So, you could locate them additionally conveniently. Well, now we have actually done to provide you the most effective book to check out today, this Requirements Analysis And System Design: Developing Information Systems With UML, By Leszek A. Maciaszek is actually ideal for you. Never ever overlook that you require this publication Requirements Analysis And System Design: Developing Information Systems With UML, By Leszek A. Maciaszek to make far better life. On-line e-book Requirements Analysis And System Design: Developing Information Systems With UML, By Leszek A. Maciaszek will truly give simple of everything to read as well as take the perks.

Requirements Analysis and System Design: Developing Information Systems with UML, by Leszek A. Maciaszek

This is a thorough text on object-oriented software development emphasizing large-scale applications and capitalizing on the increasing popularity of UML and client-server techniques. The book addresses the latest developments in database technology including object-relational databases. In this context, the Internet-driven shift from thick-clients back to server-based computing is acknowledged. The analysis and design principles discussed in the text apply equally well to conventional client-server solutions and modern component-based distributed applications.

  • Sales Rank: #4414642 in Books
  • Published on: 2001-04-13
  • Original language: English
  • Number of items: 1
  • Dimensions: 9.00" h x 1.00" w x 6.90" l,
  • Binding: Paperback
  • 378 pages

From the Back Cover

The development of a software system takes place in three iterative and incremental phases — analysis, design and implementation. This book describes the methods and techniques used for analysis and design, with implementation issues addressed to the extent to which they must be considered in the design. The text concentrates on object-oriented software development, using the Unified Modeling Language (UML). The book uses the teach-by-example principle — all concepts are exemplified and the running case studies present integrated solutions.

The focus of the book is on developing large-scale, client/server, multi-tier object-oriented information systems. The client is a workstation with a GUI and the server manages a database. The client, server and middle-tier processes communicate via object messaging. The server database can be relational, object-relational or purely object-oriented. The book identifies ways to:

  • integrate analysis and design models;
  • harness the complexity of large system models;
  • improve software architectures;
  • promote layered structuring of objects;
  • understand consequences of reckless modeling;
  • conduct testing and manage change;
  • build maintainable and scalable systems.

The book can be used for undergraduate courses in computer science or information systems such as systems analysis, systems design, software engineering, databases and abject technology, as well as being a valuable resource for software projects. The book has also been written for professionals developing business information systems, such as IT managers, application developers, consultants, analysts, designers, programmers, testers, software engineers, systems integrators and educators. The text is accompanied by a comprehensive website that contains a wealth of additional material for instructors, students and professionals.

About the Author
Leszek Maciaszek is Associate Professor of Computing at Macquarie University, Sydney, Australia. Originally from Poland, Professor Maciaszek has worked as a researcher, consultant and educator in various countries around the world, including the US, Germany, France, Italy, The Netherlands, Macao, Malaysia, Thailand, and Kuwait. He moved to Australia in 1985. He has extensive consulting and training experience, frequently to large international companies. His research has been in databases, object-oriented technology, software engineering and the development of large-scale business information systems. He has authored close to 100 publications including the book Database Design and Implementation (Prentice Hall, 1990).

Excerpt. � Reprinted by permission. All rights reserved.
Outline of the book

The development of an information system (IS) - from its inception to the first release to stakeholders comprises three iterative and incremental phases: analysis, design, and implementation. This book describes the methods and techniques used in the first two phases. The implementation issues are only addressed to the extent to which they need to be considered in the design phase. Testing and change management are addressed in the final chapter.

The text concentrates on object-oriented software development. The Unified Modeling Language (UML) is used to capture modeling artifacts. Emphasis is placed on the development by elaboration where the same modeling language (UML) is used throughout the development lifecycle. Analysts, designers, and programmers 'speak' the same language, although perhaps use the dialects (profiles) of the language fitting their individual needs.

The early applications of object technology targeted graphical user interfaces (GUIs) and focused on the speed of developing new systems and the speed of program execution. In this book, I emphasize the application of object technology in IS development. The challenge is the large volume of data, complex data structures, shared access to information by many concurrent users, transaction processing, changing requirements, etc. The main advantage of object technology in IS environments is in facilitating software maintenance and scalability.

Developing information systems is synonymous with doing analysis and design 'in-the-large'. No IS project can succeed without following strict development processes and without understanding the underlying software architectures. The development is large-scale, object-oriented, iterative and incremental. The software architecture is based on a client/server solution, where the client is a workstation with GUI and the server stores a database. Client and server run in separate processes and communicate via object messaging. A server database can be relational, object-relational, or purely object-oriented.

The book proposes a detailed approach to analysis and design of information systems with UML. The book identifies ways to:

  • harness the complexity of large system models;
  • improve software architectures;
  • facilitate software readability, maintainability and scalability;
  • promote layered structuring of objects;
  • handle component integration;
  • improve modeling of collaboration between GUI and persistent database objects, etc.
  • Distinguishing features

    This book has a number of features which, when combined, create a unique offering. The 'teach-by-example' approach is the cornerstone of the text. The main discussion is based on examples and a guided tutorial drawn from five application domains University Enrollment, Video Store, Contact Management, Telemarketing, and Online Shopping. The examples are independent. They build up into case studies that can be extended or diversified through questions formulated at the end of most chapters (Exercise Questions). Some exercises refer to a sixth application domain — Advertising Expenditure Measurement.

    To facilitate self-education, the guided tutorial (Online Shopping) and the case studies are formulated using the question-and-answer principle. A separate section at the beginning of the book, 'Book Activity Diagrams' offers diagrams that link the question-and-answer steps used in the tutorial and in the case studies. The book activity diagrams can serve as an alternative table of contents for examples scattered in the text.

    The book discusses principles, methods and techniques of good analysis and good design. Special attention is paid to the design phase. Design is not treated as a straightforward transformation from analysis. The book acknowledges the difficulties and intricacies of large-scale object-oriented client/server system development. In many ways, the book takes a fresh look at the 'design-in-the-large,' at iterative and incremental development of large systems, and at capabilities and limitations of tools and methods in large software production.

    A unique character of the book comes from a balanced blend of practical explanation and theoretical insight. A major premise is to avoid unnecessary over-complication, but without the loss of rigor. The book 'speaks' from experience. Topics that are not relevant to industry or that are only of research interest have been excluded.

    The book is on the 'cutting-edge' of information technology. It uses the latest standard in system modeling — UML. It addresses the latest developments in database technology, including object-relational databases. In this context, the Internet-driven shift from 'thick-clients' (i.e. large desktop computers) back to server-based computing is acknowledged. The analysis and design principles discussed in the text apply equally well to conventional client/server solutions and to modern component-based distributed applications.

    Software development is not amenable to 'black-white,' 'true-false,' 'zero-one' solutions. Good software solutions come from good business analysts and system designers/programmers, not from blindly applied algorithms. A policy of the book is to warn the reader about potential difficulties that the advocated approach cannot entirely resolve. In consequence it is hoped that readers will apply their acquired knowledge with care and will not assume unrealistic expectations of the ease with which the approach can be applied (and thereby, possibly, fail more dramatically).

    In summary, the distinguishing features of the book are:

  • The book relates the theories to reality — in the form of practical problems and limitations, which will have to be addressed when applying the approach 'in the field.'
  • The book gives special attention to the design phase. Design is not treated as a straightforward transformation from analysis and it acknowledges the difficulties and intricacies of large-scale client/server system development.
  • A wealth of nontrivial examples and exercises with all solutions are included in the book or the supplementary materials. The Instructor's Manual is not an afterthought — it has been written concurrently with the text and is meticulous.
  • Intended readership

    In tune with the growing demand for university courses to be more relevant to industry practice, this textbook is aimed at students and practitioners alike. This has been a difficult task but, it is hoped, it has been successfully achieved. To ensure a lasting educational benefit, the implementation aspects of software development are discussed in non-vendor-specific terms (although commercial CASE tools have been used in illustrations and solutions).

    The book is aimed at computer science and information systems curricula. As it contains both 'high-level' system modeling topics and 'low-level' user interface and database design issues, the book should be attractive to courses in system analysis, system design, software engineering, databases, object technology, and to software project courses that require students to develop a system following the development lifecycle: from requirements determination to GUI and database implementation. The book is designed for a one-semester course, but it can potentially be used over two one-semester courses — one on requirements analysis and the other on system design.

    For the practitioners' audience, the presented theories are related to realities. Most problem statements, examples and exercises are drawn from the consulting practice of the author. We have adopted a policy of warning the reader of potential difficulties or limitations with advocated approaches. The following categories of practitioners are likely to benefit most from the book: business and system analysts, designers, programmers, system architects, project leaders and managers, reviewers, testers, technical writers, and industry trainers.

    Organization of the book

    The book provides comprehensive coverage of object-oriented analysis and design of information systems. The material is presented in an order consistent with modern development processes. The book consists of ten chapters. The coverage is balanced between analysis and design. The first five chapters address the analysis issues and the last five design and related considerations.

    Readers with varying amounts of background knowledge should be able to accommodate the text. Two chapters in the book are dedicated to an explanation of the underpinnings of analysis and design. The remaining chapters assume that the reader understands these underpinnings. The reader has a choice of studying the 'underpinnings' chapters in detail or of using them for review only.

    The book has several features to improve its clarity and to break the monotony of the text, in particular:

    • Sections are small.
    • Example and problem statements are placed in frames to distinguish them from the rest of the text. A graphical icon (see below) in the page margin also marks the beginning of each example.
    • Page margins are used to:
      - number and caption figures and tables,
      - show graphical icons to identify examples in the text and end-of-chapter questions
    Supplementary materials

    A comprehensive package of supplementary material is provided on the companion websites. Most of the web documents are freely available to the readers, but some material is password-protected for the benefit of instructors who have adopted the textbook in their teaching. The home page for the book is simultaneously maintained at:

    http://www.booksites.net/maciaszek
    http://www.comp.mq.edu.au/books/maciaszek

    The web package includes:

  • Instructor's Manual with:
    — Lecture Slides in Microsoft PowerPoint and Acrobat Read (.pdf) formats.
    — Answers and Solutions manual containing annotated answers and solutions to all review and exercise questions from the end of each chapter. The organization of the manual corresponds to the textbook structure. The questions from the textbook are repeated in the manual. Answers and solutions follow the questions.
  • Student's Resources with printable lecture slides in Acrobat Read format.
  • Self-education Resources with Rational Rose (.mdl) and PowerDesigner (.pdm) model files containing solutions to the guided tutorial, the case studies and all other modeling examples in the textbook.
  • Errata page dedicated to corrections of errors and omissions in the book.
  • For More Information page to point the reader to the latest ideas and trends in the textbook's subject area. Also, to identify courses that adopted the book and which are prepared to share their web facilities with other readers.

    Your comments, corrections, suggestions for improvements, contributions, etc. are very much appreciated. Please, direct any correspondence to:

    Leszek A. Maciaszek
    Department of Computing
    Macquarie University
    Sydney
    NSW 2109
    Australia
    leszek@ics.mq.edu.au
    http://www.comp.mq.au/~leszek/
    phone: +61 2 9850-9519
    facsimile: +61 2 9850-9551
    courier: North Ryde, Herring Road, Bld. E6A, Room 319

    Acknowledgements

    The writing of this book would be impossible without my interactions with friends, colleagues, students, industry gurus, and all the other people who, consciously or not, have shaped my knowledge in the subject area. I am truly indebted to all of them. An attempt to list all their names would be injudicious and impractical - please accept a blanket 'thank you.' However, even in the little space available for, acknowledgments, a few 'mates' must be mentioned:

    • Keith Mansfield, Mary Lince and the staff of Pearson Education — for recognizing the potential of this book and bringing it to the international market.
    • Stephen Bills and his staff at ACNielsen AdEx, Sydney, Australia, in particular: Steven Grotte, Kevin Mathie, Cameron Murray, James Rees, Jovan Spoa, and Eric Zurcher — for providing me with a production IS development testbed for this book.
    • My friends and colleagues in the Department of Computing at Macquarie University in Sydney Australia — for their support in the making of this book.
    • The formal (unknown to me) and informal reviewers — for invaluable feedback that has greatly benefited the book.
    • The staff at Rational, Oracle and Sybase — for providing me with the CASE and database software indispensable to the development of tutorials, case studies and examples.

    Most helpful customer reviews

    6 of 6 people found the following review helpful.
    A UML and system development book with rich case studies
    By IL YEOL SONG
    Here is another excellent book on UML and system development using UML. I found this book highly practical, amusing, and instructive to read. Among the many excellent features of this book, I found the following five main strengths of the book. First, the book is rich with five case studies. Many books are rich in discussion, but weak in examples and case studies. This book uses five case studies. Some case studies are detailed while other case studies are short. Second, the book covers many advanced concepts, not usually covered by many other popular UML books in one volume. Those advanced features include reified classes, interface inheritance, implementation inheritance, extension inheritance, delegation, four types of aggregations, etc. Fourth, the book integrates other important parts of the system development activities such as user interface design, window navigation diagrams, database design for OO, OR, and relational databases. Fifth, therefore, the book covers all the life cycle of OO system developments, beginning from requirements modeling to user interface design, database design and testing. All these features make this book as an excellent choice for learning how to use UML to develop a complete system. One of several minor drawbacks is that some discussions appear in several different sections. This is due to a fairly long guided tutorial in Chapter 2.

    6 of 6 people found the following review helpful.
    Developing Information Systems with UML
    By Jan Seruga
    This book covers a very important issue of applying the new modeling language UML to analyse and design object-oriented information systems. The author clearly explains problems facing developers of information systems and offers practical advice on analysing and designing systems. Examples are offered to illustrate each new concept as it is introduced. The content of the book is applicable to the creation of high- quality software system. The book offers a good source for the learning about UML. The book is an interesting and useful and I recommend it to anyone who wants to learn more about UML and object-oriented systems. It contains all you might want to know about software process: Requirements, Analysis, Design, Implementation and Test. Each chapter states the emphasis of the corresponding phase, describes the planning required for the phase. It mentions how this all fits in with the business case for the project and what the key deliverables are for each phase.

    7 of 9 people found the following review helpful.
    Superficial, strained and vague
    By Andrey Taranov
    Honestly, I only endured this book to its middle. Superficial is the first characteristic that comes to mind. The author gives a brief description of object technology (which turnes out to be rather a list of UML concepts). A very short overview of requirement analysis follows - only "what", little of "why", almost nothing about "how". The requirements document template is here too, but you could really find better examples on the net, including real standards.
    But only in chapter 4 the book starts to blossom. You quickly find out, that the author has little if any real world design experience. Yes, the case-studies are a bit strained, still they are tolerable. But the author does poor modeling: his models are, well, arguable. Some classes 'follow' from the requirements without real explanation. And the naming is just plain ugly: consider a 'areYouOpen' method on a Course class and an 'areYouValid' method on a Student class.
    UML is covered, again, superficially. The short Fowler's book, UML Distilled, goes to greater depths on almost any topic (not to say Fowler *does* cover some experience in software process).
    If you need anything better, than a one term undergraduate learn-and-forget coursebook, don't bother.

    See all 6 customer reviews...

    Requirements Analysis and System Design: Developing Information Systems with UML, by Leszek A. Maciaszek PDF
    Requirements Analysis and System Design: Developing Information Systems with UML, by Leszek A. Maciaszek EPub
    Requirements Analysis and System Design: Developing Information Systems with UML, by Leszek A. Maciaszek Doc
    Requirements Analysis and System Design: Developing Information Systems with UML, by Leszek A. Maciaszek iBooks
    Requirements Analysis and System Design: Developing Information Systems with UML, by Leszek A. Maciaszek rtf
    Requirements Analysis and System Design: Developing Information Systems with UML, by Leszek A. Maciaszek Mobipocket
    Requirements Analysis and System Design: Developing Information Systems with UML, by Leszek A. Maciaszek Kindle

    Requirements Analysis and System Design: Developing Information Systems with UML, by Leszek A. Maciaszek PDF

    Requirements Analysis and System Design: Developing Information Systems with UML, by Leszek A. Maciaszek PDF

    Requirements Analysis and System Design: Developing Information Systems with UML, by Leszek A. Maciaszek PDF
    Requirements Analysis and System Design: Developing Information Systems with UML, by Leszek A. Maciaszek PDF
  • Tidak ada komentar:

    Posting Komentar