SRS Documents: Requirements and Diagrammatic Notations
- 4.5
-
![]()
![]()
![]()
![]()
![]()
Description
As requirements are being gathered and prioritized, they also need to be documented. In Diagrammatic Notations and Software Requirements Specification Writing, we discuss and practice the process of turning requirements into something readable to the customers at a high level, and the developers. When a designer or developer reads your document, they should be able to understand the overall idea, the scope, the domain, the resources, the expectations, and why alternative choices are not selected. To create a document in this way, you use a balance between storytelling (with pictures!) and complex diagrams.
Outline
- Beginning to Write an SRS Document
- Introduction to Diagrammatic Notations and Software Requirements Specification Writing
- Following Local Rules
- Standardized Statement Templates
- Global Organization Templates
- Introduction to Diagrammatic Notations - Slides
- Local Rules | Standardized Templates - Slides
- Global Organization Templates - Slides
- Begin to Write an SRS Document
- Beginning Diagramming
- Diagramming- Adding Use/Misuse/Abuse Cases
- Context and Problem Diagrams
- Frame Diagrams
- Diagramming-Adding Use/Misuse/Abuse Cases -Slides
- Misuse Cases: Use Cases with Hostile Intent
- Misuse and abuse cases: getting past the positive
- Context and Problem | Frame Diagrams - Slides
- Relating software requirements and architectures using problem frames
- Use/Misuse Cases and High Level Diagramming
- Lower-Level Diagramming
- Entity Relationship and Class Diagrams
- SADT Diagrams: Actigrams and Datagrams
- Data Flow Diagrams
- The entity-relationship model for multilevel security
- Entity Relationship | SADT |Data Flow Diagrams - Slides
- Lower-Level Diagramming
- Tracing Events
- Putting the Diagrams Together
- Event Trace Diagrams
- State Machine Diagrams
- Concurrent StateCharts and R-Nets
- Putting the Diagrams Together | Event Trace Diagrams - Slides
- State Machine Diagrams | Concurrent State Charts & R-Nets - Slides
- Tracing Events
- Combining and Confirming Diagram Consistency and Completeness
- Diagrams: Putting them all together
- Formal Notation
- Combining Natural Language and Diagrams - Reminders
- Diagrams: Putting Them All Together - Slides
- Formal Notation - Slide
- Combining Natural Language and Diagrams - Slide
- Model driven security for process-oriented systems
- Combining and Confirming Diagram Consistency and Completeness
Summary of User Reviews
Read reviews for SRS Documents & Requirements course on Coursera. Many users found this course to be helpful for understanding software requirements. Overall, users have rated this course positively.Key Aspect Users Liked About This Course
Helpful for understanding software requirementsPros from User Reviews
- Course is easy to follow
- Instructor provides real-life examples
- Material is relevant to industry
Cons from User Reviews
- Course can be repetitive
- Some material is outdated
- Not enough focus on agile development
Kristen Walcott-Justice
4.5 Raiting
SRS Documents: Requirements and Diagrammatic Notations
- 4.5
-
![]()
![]()
![]()
![]()
![]()
As requirements are being gathered and prioritized, they also need to be documented. Beginning to Write an SRS Document Introduction to Diagrammatic Notations and Software Requirements Specification Writing...
