Software Requirements – SWR301
  • There is no houres or category chosen or category doesn't contain any items

We have 100 guests and no members online

This Week
Last Week
This Month
Last Month
All days

Your IP:
Server Time: 2020-03-30 20:15:25

Request Here

Software Requirements – SWR301

In oder to supplying the better references to students, lecturers and researchers; FPT Library and Information Center delighted to inform you about the subject guide for this subject: Software Requirements.

Main book

Requirements engineering: from system goals to UML models to software specifications


Call number: 005.1 L241

Author: Axel van Lamsweerde

Publisher: Chichester, England: John Wiley, 2009. – xxix, 682 p.: ill ; 24 cm

ISBN: 0470012706 / 9780470012703

Library code: FSE (06)

Call number: 005.1 L241

The book presents both the current state of the art in requirements engineering and a systematic method for engineering high-quality requirements, broken down into four parts. The first part introduces fundamental concepts and principles including the aim and scope of requirements engineering, the products and processes involved, requirements qualities to aim at and flaws to avoid, and the critical role of requirements engineering in system and software engineering.

The second part of the book is devoted to system modeling in the specific context of engineering requirements. It presents a multi-view modeling framework that integrates complementary techniques for modeling the system-as-is and the system-to-be. The third part of the book reviews goal-based reasoning techniques to support the various steps of the KAOS method. The fourth part of the book goes beyond requirements engineering to discuss the mapping from goal-oriented requirements to software specifications and to software architecture.

Online resources will accompany the book and will add value to both classroom and self-study by enabling students to build models and specifications involved in the book’s exercises and case studies, helping them to discover the latest RE technology solutions. Instructor resources such as slides, solutions, models and animations will be available from an accompanying website.

Reference books

Requirements engineering: processes and techniques


Call number: 005.1 K875

Author: Kotonya, Gerald

Publisher: Wiley, 2003. – 282 tr ; 24 cm.

ISBN: 0471972088

Library code: FSE (22 +19 photos)

Call number: 005.1 K875

Requirements Engineering Processes and Techniques Why this book was written The value of introducing requirements engineering to trainee software engineers is to equip them for the real world of software and systems development. What is involved in Requirements Engineering? As a discipline, newly emerging from software engineering, there are a range of views on where requirements engineering starts and finishes and what it should encompass. This book offers the most comprehensive coverage of the requirements engineering process to date – from initial requirements eli through to requirements validation. How and Which methods and techniques should you use? As there is no one catch-all technique applicable to all types of system, requirements engineers need to know about a range of different techniques. Tried and tested techniques such as data-flow and object-oriented models are covered as well as some promising new ones. They are all based on real systems descriptions to demonstrate the applicability of the approach. Who should read it? Principally written for senior undergraduate and graduate students studying computer science, software engineering or systems engineering, this text will also be helpful for those in industry new to requirements engineering.


Requirements engineering: a good practice guide


Call number: 005.1 S697

Author: Ian Sommerville, Pete Sawyer

Publisher: New York: Wiley, 2006. – 391tr. ; 24cm

ISBN: 9780471974444

Library code: FSE ( 21+19 photos)

Call number: 005.1 S697

“A marvellous book.a unique focus on what practising engineers need to do.” Watts Humphrey, Software Engineering Institute, USA Requirements Engineering

A good practice guide Find more RE resources at this web support site


Visit our Web page! http://www compbooks/

Requirements engineering is the process of discovering, documenting and managing the requirements for a computer-based system. The goal of requirements engineering is to produce a set of system requirements which, as far as possible, is complete, consistent, relevant and reflects what the customer actually wants. Although this ideal is probably unattainable, the use of a systematic approach based on engineering principles leads to better requirements than the informal approach which is still commonly used. This book presents a set of guidelines which reflect the best practice in requirements engineering. Based on the authors’ experience in research and in software and systems development, these guidelines explain in an easy-to-understand way how you can improve your requirements engineering processes. The guidelines are applicable for any type of application and, in general, apply to both systems and software engineering. The guidelines here range from simple ‘common sense’ to those which propose the introduction of complex new methods. The guidelines and process improvement schemes have been organised so that you can pick and choose according to your problems, goals and available budget. There are few dependencies between guidelines so you can introduce them in any order in your organisation. Guidelines presented in the book are consistent with ISO 9000 and CMM are ranked with cost/benefit analysis give implementation advice can be combined and applied to suit your organisation’s needs are supported by a web page pointing to RE tools and resources


Systems development: a project management approach


Call number: 650/.0285 M478

Authors: Raymond McLeod, Jr., Eleanor Jordan

Publisher: New York: Wiley, 2002. – xix, 524 p.: ill. ; 27 cm.

ISBN: 471220892

Library code: FSE (01)

Call number: 650/.0285  M478

Software engineering: theory and practice. – 3rd ed.


Call number: 005.1 P531

Authors: Shari Lawrence Pfleeger, Joanne M. Atlee.

Publisher: Pearson international ed. – Upper Saddle River, N.J.: Pearson Prentice Hall, 2006. – xix, 716p.: ill. ; 24cm

ISBN: 0131984616

Library code: FSE (01)

Call number: 005.1 P531

            For introductory courses in Software Engineering. This introduction to software engineering and practice addresses both procedural and object-oriented development. The book applies concepts consistently to two common examples — a typical information system and a real-time system. It combines theory with real, practical applications by providing an abundance of case studies and examples from the current literature. This revision has been thoroughly updated to reflect significant changes in software engineering, including modeling and agile methods.

Software engineering . – 8th ed.


Call number: 005.1 S697

Author:  Ian Sommerville

Publisher: New York: Addison-Wesley, 2007. – xxiii , 840 p.: ill. ; 24 cm.

ISBN: 0321313798

Library code: FSE (05)

Call number: 005.1 S697

“Sensible choice and organization of topics, made all the more authoritative by the author’s credentials as a senior academic in the area” Prof. David S. Rosenblum, University College London“I find Somerville inviting and readable and with more appropriate content” Julian Padget, University of Bath“Sommerville takes case studies from radically different areas of SE. This avoids excessive stereotyping (hence blinkering), but permits some depth and detail.” Dr C Lester, Portsmouth University Software Engineering 8 presents a broad perspective on software systems engineering, concentrating on widely used techniques for developing large-scale systems. Structured into 6 parts:1: Introduction; 2: Requirements Engineering; 3: Design; 4: Software Development; 5: Verification and Validation; 6: Management… And now with additional new chapters on System Security Engineering, Aspect-oriented Software Development, and Service-oriented systems! Building on the widely acclaimed strengths of the 7th edition, 8 updates readers with the latest developments in the field, whilst maintaining the structure and content of the 7th – easily upward compatible for those using the text in a teaching environment.

Reference Ebooks  (Books24x7)

The Quest for Software Requirements

the-quest-for-software-requirementsAuthor:  Roxanne E. Miller

Publisher: MavenMark Books © 2009 (346 pages)

ISBN: 9781595980670

Overlooked or poorly defined nonfunctional software requirements are widely recognized to be among the most expensive and difficult errors to correct after a softward system has been implemented. This book presents over 2,000 suggested questions to help master the eli of these hard-to-identify, yet vital, requirements. Its proven step-by-step techniques, insightful tips and tools, easy-to-use checklists, examples of nonfunctional requirements, and requirements-gathering questions, will assist the reader in developing and installing software requirements.

Telling Stories: A Short Path to Writing Better Software Requirements

telling-stories-a-short-path-to-writing-better-software-requirementsAuthor:  Ben Rinzler

Publisher: John Wiley & Sons © 2009 (160 pages)

ISBN: 9780470437001

From System Designers to Top Management, Everyone loves a good story Once upon a time, it was well understood that stories teach better than plain facts. Why then are most software requirements documents a baffling hodge-podge of diagrams, data dictionaries, and bullet points, held together by little more than a name and a staple. Telling Stories teaches you to combine proven standards of requirements analysis with the most ancient and effective tool for sharing information, the narrative.Telling Stories simplifies and refines the classic methods of Structured Analysis, providing organization, design, and old-fashioned writing advice. Whether you’re just getting started or an experienced requirements writer, telling stories can help you turn dull, detailed material into an engaging, logical, and readable story, a story that can make the difference for your project and your career. Learn why readers believe and remember what they learn from stories. Work with team members to gather content, tell their stories, and win their support. Use stories to find every requirement Create diagrams that almost tell the story on their own (while looking clear and professional). Explain everything important about a process. Use precise language to remove the ambiguity from requirements Write a forceful executive summary that stands on its own and sells a project to senior management Summarize often to keep the reader focused on key issues Structure the document so every part has a clear place and purpose

Engineering Software for Accessibility

engineering-software-for-accessibilityAuthors:   Jason Grieves and Masahiko Kaneko

Publisher: Microsoft Press © 2009 (832 pages)

ISBN: 9780735626805

Create Web sites and software that meet the sensory, dexterity, and cognitive needs of your users. Whether you’re a developer or a project manager, this guide teaches you how to incorporate programmatic access and keyboard access into your interfaces—starting at the product planning and design stage.

Requirements Modelling and Specification for Service Oriented Architecture

requirements-modelling-and-specification-for-service-oriented-architectureAuthor:  Ian Graham

Publisher: John Wiley & Sons © 2008 (320 pages)

ISBN: 9780470775639

            Many software developers often confuse requirements engineering with software specification and, as a result, build unusable systems, despite meeting specifications. Bringing together all the techniques needed by the modern software developer, here is a practical handbook to requirements engineering and systems specification for developers building systems within a service oriented architecture. It introduces the concepts of SOA and relevant standards and technology, such as Web services and ESBs, and then presents a range of modern requirements engineering techniques.


Software Studies: A Lexicon

software-studies-a-lexiconAuthor:  Matthew Fuller (ed)

Publisher: The MIT Press © 2008 (349 pages)

ISBN: 9780262062749

            This collection of short expository, critical, and speculative texts offers a field guide to the cultural, political, social, and aesthetic impact of software. Computing and digital media are essential to the way we work and live, and much has been said about their influence. But the very material of software has often been left invisible. In Software Studies, computer scientists, artists, designers, cultural theorists, programmers, and others from a range of disciplines each take on a key topic in the understanding of software and the work that surrounds it. These include algorithms; logical structures; ways of thinking and doing that leak out of the domain of logic and into everyday life; the value and aesthetic judgments built into computing; programming’s own subcultures; and the tightly formulated building blocks that work to make, name, multiply, control, and interweave reality. The growing importance of software requires a new kind of cultural theory that can understand the politics of pixels or the poetry of a loop and engage in the microanalysis of everyday digital objects. The contributors to Software Studies are both literate in computing (and involved in some way in the production of software) and active in making and theorizing culture. Software Studies offers not only studies of software but proposes an agenda for a discipline that sees software as an object of study from new perspectives.


Requirements Management Using IBM Rational RequisitePro

requirements-management-using-ibm-rational-requisiteproAuthor:  Peter Zielczynski

Publisher: IBM Press © 2008 (360 pages)

ISBN: 9780321383006

            Optimize Your Entire Requirements Process–and Use Requirements to Build More Successful Software Using IBM(R) Rational(R) RequisitePro(R), you can systematically improve the way you create and maintain requirements–and use those requirements to build more effective, higher-quality software. Now, for the first time, there’s a comprehensive, hands-on guide to optimally using RequisitePro in real-world development environments. Utilizing a start-to-finish sample project, requirements expert Peter Zielczynski introduces an organized, best-practice approach to managing requirements and shows how to implement every step with RequisitePro. You’ll walk through planning, eliciting, and clarifying stakeholder requirements; building use cases and other key project documents; managing changing requirements; transforming requirements into designs; and much more. Every stage of the process is illuminated with examples, realistic artifacts, and practical solutions. This book is an invaluable resource for everyone who creates requirements, and everyone who relies on them: business analysts, systems analysts, project managers, architects, designers, developers, and testers alike.

Requirements Engineering, Second Edition

requirements-engineering-second-editionAuthors:  Elizabeth Hull, Ken Jackson and Jeremy Dick

Publisher: Springer © 2005 (201 pages)

ISBN: 9781852338794

            Using the latest research and driven by practical experience from industry, this book offers useful hints to practitioners on how to write and structure requirements. It explains the importance of Systems Engineering and the creation of effective solutions to problems. It describes the underlying representations used in system modeling and introduces the UML2, and considers the relationship between requirements and modeling. Covering a generic multi-layer requirements process, the book discusses the key elements of effective requirements management. The latest version of DOORS (Version 7) — a software tool which serves as an enabler of a requirements management process — is also introduced to the reader here.

Discovering Real Business Requirements for Software Project Success

discovering-real-business-requirements-for-software-project-successAuthor:  Robin F. Goldsmith

Publisher: Artech House © 2004 (241 pages)

ISBN: 9781580537704

            While a number of books on the market deal with software requirements, this is the first resource to offer a methodology for discovering and testing the real business requirements that software products must meet in order to provide value.

Software Requirements, Second Edition

software-requirements-second-editionAuthor:  Karl E. Wiegers

Publisher: Microsoft Press © 2003 (516 pages)

ISBN: 9780735618794

            Without formal, verifiable software requirements and an effective system for managing them the programs that developers think they ve agreed to build often will not be the same products their customers are expecting. In Software Requirements, Second Edition, requirements engineering authority Karl Wiegers amplifies the best practices presented in his original award-winning text?now a mainstay for anyone participating in the software development process. In this book, you ll discover effective techniques for managing the requirements engineering process all the way through the development cycle including dozens of techniques to facilitate that all-important communication between users, developers, and management. This updated edition features new case examples, anecdotes culled from the author s extensive consulting career, and specific Next Steps for putting the book s process-improvement principles into practice. You ll also find several new chapters, sample documents, and an incisive troubleshooting guide.

UML Xtra-Light: How to Specify Your Software Requirements

uml-xtra-light-how-to-specify-your-software-requirementsAuthors:  Milan Kratochvil and Barry McGibbon

Publisher: Cambridge University Press © 2003 (106 pages)

ISBN: 9780521892421

Business managers often find it impossible to communicate business objectives and specify their software requirements to technical members of staff. This beginner’s guide to the Unified Modeling Language (UML) – the standard for documenting software designs – teaches readers to communicate with software developers in a more focused, effective way. It describes the basic diagrams of the UML modeling notation and shows how they are used to specify requirements in an unambiguous way. When applied on a project, the risk of failure through unclear requirements is removed. If you are a non-technical person with a stake in the success of a software project, this book is for you. Milan Kratochvil has worked as an IT-consultant, instructor and writer in methodology for nearly twenty-five years, focusing on areas where IT and business intersect. Barry McGibbon is a principal consultant for Princeton Softech.

Software Requirements

software-requirementsAuthor:  Karl E. Wiegers

Publisher: Microsoft Press © 1999 (350 pages) Archive

ISBN: 9780735606319

            Concise, readable, and expert advice for collecting and analyzing software requirements. Wiegers presents a palette of best practices for collecting, validating and managing software requirements, together with examples of their successful application to real-world projects. This is one of the few pragmatic resources on this topic.

Internet resources

Requirements Engineering: Processes and Techniques by Gerald Kotonya, Ian Sommerville; August 1998, Hardcover.

See also at:

(content, preface, slides, solutions, tools)

Requirements Engineering: A Good Practice Guide by Ian Sommerville, Pete Sawyer; April 1997, Paperback.

See also at:

(content, preface, general information, sprcific topis, examples, tools, methods)

CMU/SEGVN articles and/or public lectures on tendency of  software engineering in the world  (SEGVN website and forum) at


магазин DVD фильмов
Battlefield 4 Beta обзоры, тесты, новости