Requirements Writing

Start Date: 11/06/2018

Course Type: Common Course

Course Link:

Explore 1600+ online courses from top universities. Join Coursera today to learn data science, programming, business strategy, and more.

About Course

Welcome to "Requirements Writing". As the title indicates, over the next four weeks, we will be looking at the important task of writing of text-based requirement statements. The course takes you step by step through the rules for writing requirements statements in accordance with the "Guide for Writing Requirements" published by the International Council on Systems Engineering (INCOSE). This course welcomes anyone who wants to find out how to write requirements. It is relevant to anyone in project management, engineering, QA, logistic support, operations, management, maintenance and other work areas. No specific background is required, and we welcome learners with all levels of interest and experience.

Course Syllabus

Welcome to the Requirements Writing MOOC. The course is run over five weeks. During the first four weeks you will complete four modules (one each week) that progressively move through the rules for writing requirements. Each week, you will have the opportunity to undertake a module quiz as many times as you wish to ensure that you have a grasp on the module material. The quizzes are drawn from a large set of questions, so each time you do the quiz, you will see new questions to test your knowledge. In Week 5, there will not be any presentations but you will have time to review the four modules and practice the module quizzes again so that you are prepared for the course exam.

Deep Learning Specialization on Coursera

Course Introduction

Welcome to "Requirements Writing". As the title indicates, over the next four weeks, we will be look

Course Tag

Related Wiki Topic

Article Example
Business requirements Business requirements are often listed in a Business Requirements Document or BRD. The emphasis in a BRD is on what is required, rather than on how to achieve it, which is usually delegated to a Systems Requirements Specification or Document (SRS or SRD) or other variation such as a Functional Specification Document. While supposedly describing the product, system, or software from an external perspective, such documents often define the product/system/software requirements in the context of a chosen technology (a solution approach or architecture). Further confusion often arises when people writing BRDs do not understand the distinctions; and consequently many BRDs actually describe requirements of a product, system, or software.
English writing style The requirements for writing and citing articles accessed on-line may sometimes differ from those for writing and citing printed works. Some of the details are covered in "The Columbia Guide to Online Style".
Requirements elicitation In 2013, Murali Chemuturi suggested the usage of Ancillary Functionality Requirements instead of Non-Functional Requirements as "Non-Functional" connotes "never functional". Second, these requirements in fact fulfill some requirements which are supportive to main or Core Functionality Requirements.
Requirements management The purpose of requirements management is to ensure that an organization documents, verifies, and meets the needs and expectations of its customers and internal or external stakeholders. Requirements management begins with the analysis and elicitation of the objectives and constraints of the organization. Requirements management further includes supporting planning for requirements, integrating requirements and the organization for working with them (attributes for requirements), as well as relationships with other information delivering against requirements, and changes for these.
Requirements elicitation Before requirements can be analyzed, modeled, or specified they must be gathered through an elicitation process. Requirements elicitation is a part of the requirements engineering process, usually followed by analysis and specification of the requirements.
Requirements Modeling Framework The Requirements Modeling Framework (RMF) is an Open-Source-software framework for working with requirements based on the ReqIF standard. RMF consists of a core allowing reading, writing and manipulating ReqIF data, and a user interface allowing to inspect and edit request data.
Requirements engineering Some research suggests that software requirements are often an illusion misrepresenting design decisions as requirements in situations where no real requirements are evident.
Business requirements Such confusion can be avoided by recognizing that business requirements are not objectives but rather meet objectives (i.e., provide value) when satisfied. Business requirements "whats" do not decompose into product/system/software requirements "hows". Rather, products and their requirements represent a response to business requirements—a way "how" presumably to satisfy the "whats". Business requirements exist within the business environment and must be discovered, whereas product requirements are human-defined (specified). Business requirements are not just high-level but need to be driven down to detail. No matter how far down in detail they are driven, business requirements are always business deliverable "whats" that provide value when satisfied; driving them down to detail never turns business requirements into product requirements.
System requirements Often manufacturers of games will provide the consumer with a set of requirements that are different from those that are needed to run a software. These requirements are usually called the Recommended Requirements. These requirements are almost always of a significantly higher level than the minimum requirements, and represent the ideal situation in which to run the software. Generally speaking this is a better guideline than minimum system requirements in order to have a fully usable and enjoyable experience with a software.
Requirements traceability Requirements are realized into design artifacts, implementation, and finally, verified. Artifacts tied to the latter stages should be traced back to the requirements as well. This is typically done via a Requirements Traceability matrix.
Requirements analysis Requirements are categorized in several ways. The following are common categorizations of requirements that relate to technical management:
Requirements traceability Requirements Traceability is concerned with documenting the relationships between requirements and other development artifacts. Its purpose is to facilitate:
Requirements specification Requirements specification in systems engineering and software engineering is the direct result of a requirements analysis and can refer to
Writing Writing is a medium of human communication that represents language and emotion through the inscription or recording of signs and symbols. In most languages, writing is a complement to speech or spoken language. Writing is not a language but a form of technology that developed as tools developed with human society. Within a language system, writing relies on many of the same structures as speech, such as vocabulary, grammar and semantics, with the added dependency of a system of signs or symbols. The result of writing is generally called "text", and the recipient of text is called a reader. Motivations for writing include publication, storytelling, correspondence and diary. Writing has been instrumental in keeping history, maintaining culture, dissemination of knowledge through the media and the formation of legal systems.
Requirements elicitation In requirements engineering, requirements elicitation is the practice of collecting the requirements of a system from users, customers and other stakeholders. The practice is also sometimes referred to as "requirement gathering".
Requirements management Requirements management involves communication between the project team members and stakeholders, and adjustment to requirements changes throughout the course of the project. To prevent one class of requirements from overriding another, constant communication among members of the development team is critical. For example, in software development for internal applications, the business has such strong needs that it may ignore user requirements, or believe that in creating use cases, the user requirements are being taken care of.
Software requirements Specification involves representing and storing the collected requirements knowledge in a persistent and well-organized fashion that facilitates effective communication and change management. Use cases, user stories, functional requirements, and visual analysis models are popular choices for requirements specification.
Writing Historians draw a sharp distinction between prehistory and history, with history defined by the advent of writing. The cave paintings and petroglyphs of prehistoric peoples can be considered precursors of writing, but they are not considered true writing because they did not represent language directly.
Writing about Writing Writing about Writing (WAW), is a method or theory of teaching composition which puts emphasis on reading and writing about writing in the writing course, and reimagines first-year composition as an "introduction to writing studies." This is not to say WAW only teaches a first-year writing course as if it were an introduction to a writing major, but rather it advocates merging the "how" of writing with its practice. An introduction course to a writing major has both a different audience and purpose than a first-year composition course framed in WAW. The development of WAW is largely credited to Elizabeth Wardle and Douglas Downs after the publication of their 2007 article "Teaching about Writing, Righting Misconceptions."
Writing about Writing WAW asks students to read about writing and various processes, which allows them to identify what works for them. By reading articles that a composition studies student might read, the first-year composition student is able to gain further insight into the ongoing conversation centered around writing. In her article "Writing about Writing in Basic Writing," Shannon Carter explains "a writing-about-writing approach foregrounds research in writing and related studies by asking students to read and discuss key research in the discipline and contribute to the scholarly conversation themselves." She explains that having students immerse themselves in this type of scholarship will not only improve their writing but their understanding of writing as an academic discipline will increase as well, which in turn contributes to changing the public perception that writing is only something that is a piece of other disciplines.