scispace - formally typeset
Search or ask a question
Topic

Software requirements specification

About: Software requirements specification is a research topic. Over the lifetime, 7911 publications have been published within this topic receiving 143829 citations. The topic is also known as: requirements & requirements specification.


Papers
More filters
Book ChapterDOI
04 Jul 2009
TL;DR: This chapter reviews the state of the art on the treatment of non-functional requirements (hereafter, NFRs), while providing some prospects for future directions.
Abstract: Essentially a software system's utility is determined by both its functionality and its non-functional characteristics, such as usability, flexibility, performance, interoperability and security. Nonetheless, there has been a lop-sided emphasis in the functionality of the software, even though the functionality is not useful or usable without the necessary non-functional characteristics. In this chapter, we review the state of the art on the treatment of non-functional requirements (hereafter, NFRs), while providing some prospects for future directions.

2,443 citations

Book
16 Sep 1998
TL;DR: Tried and tested techniques such as data-flow and object-oriented models are covered as well as some promising new ones and are all based on real systems descriptions to demonstrate the applicability of the approach.
Abstract: 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 elicitation 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. Accompanying Website: http: //www.comp.lancs.ac.uk/computing/resources/re Visit our Website: http://www.wiley.com/college/wws

1,688 citations

Book
09 Feb 2009
TL;DR: Serving as a helpful introduction to the fundamental concepts and principles of requirements engineering, this guide offers a comprehensive review of the aim, scope, and role of requirements Engineering as well as best practices and flaws to avoid.
Abstract: Essential comprehensive coverage of the fundamentals of requirements engineering Requirements engineering (RE) deals with the variety of prerequisites that must be met by a software system within an organization in order for that system to produce stellar results. With that explanation in mind, this must-have book presents a disciplined approach to the engineering of high-quality requirements. Serving as a helpful introduction to the fundamental concepts and principles of requirements engineering, this guide offers a comprehensive review of the aim, scope, and role of requirements engineering as well as best practices and flaws to avoid. Shares state-of-the-art techniques for domain analysis, requirements elicitation, risk analysis, conflict management, and more Features in-depth treatment of system modeling in the specific context of engineering requirements Presents various forms of reasoning about models for requirements quality assurance Discusses the transitions from requirements to software specifications to software architecture In addition, case studies are included that complement the many examples provided in the book in order to show you how the described method and techniques are applied in practical situations.

1,199 citations

Book
01 May 2000
TL;DR: Through discussions, interaction and demonstrations, you ensure that you have the requirements process that is suitable for your organization.
Abstract: ● The teaching chapters are reinforced with hands-on workshops. ● Discuss issues with an instructor who has real-world experience. ● Learn industry-proven requirements techniques. ● In the final session, through discussions, interaction and demonstrations, you ensure that you have the requirements process that is suitable for your organization. ● Receive the Volere Requirements Specification Template with advice on how to make this your own template. ● Receive a copy of Suzanne and James Robertson's book Mastering the Requirements Process Second Edition. Special Features

1,040 citations

Book
01 Jan 1999
TL;DR: This updated edition of Software Requirements, Second 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.
Abstract: From the Publisher: 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.

1,006 citations


Network Information
Related Topics (5)
Software development
73.8K papers, 1.4M citations
93% related
Component-based software engineering
24.2K papers, 461.9K citations
93% related
Software system
50.7K papers, 935K citations
93% related
Software construction
36.2K papers, 743.8K citations
92% related
Business process
31.2K papers, 512.3K citations
86% related
Performance
Metrics
No. of papers in the topic in previous years
YearPapers
202317
202258
202186
2020107
2019101
2018144