Scribd
Upload
5 views3 pages

Note 2

The document discusses the expression and classification of software requirements, emphasizing natural language as the most common form for articulating needs. It introduces structured natural language and user stories as effective methods for requirement specification, along with various diagrammatic notations like context and problem diagrams. Additionally, it mentions the use of UML diagrams such as ERD and SADT for visual representation of requirements.

Uploaded by

personal1234pranav
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
5 views3 pages

Note 2

The document discusses the expression and classification of software requirements, emphasizing natural language as the most common form for articulating needs. It introduces structured natural language and user stories as effective methods for requirement specification, along with various diagrammatic notations like context and problem diagrams. Additionally, it mentions the use of UML diagrams such as ERD and SADT for visual representation of requirements.

Uploaded by

personal1234pranav
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

CSE 563: Software Requirements

January 22, 2025

Requirement Specification and Classification

 Most common form of expression of needs in the total population is via


natural language
 Upsides are that there are
o No limitation on expressive barrier
o Questions: Upsides and downsides of using natural language-
based expression
o What is the right time and place to use these expressions.
 Time Flies like an arrow:
o Meaning 1: Both time and arrow flies by very quickly
o Should measure how fast a fly moves the same way that you
would be an arrow.
o There is a kind of fly, a time of fly, and they like arrows

 Structured Natural Language


o Use of global rules, about how to organize such documents
o Use of local stylistic rules to avoid common problems
o A short review to introduce the goal and the solution concept
o A systematic development of the solution concepts
 User stories are a structured form of natural language
 As a <type of user> I want to <do something> so <a goal is
achieved>
 Diagrammatic notation:
o Context Diagram:
 Node Rectangle
 System Component
 Edges with a label
o Problem Diagram:
 Similar to context diagram
 Add notation of requirements, system to be, components to
be
 Problem Frame Diagram: Proven useful problem frames in the same
vein as design pattern are to design.

 More UML Diagram: ERD, SADT, DATAFLOW, Use Case, etc


 SADT: with actigram and datagram

You might also like