SRS Documents: Requirements and Diagrammatic Notations

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

• Practice transforming requirements into readable documents
• Use storytelling and diagrams to explain concepts
• Enable understanding of scope, resources, and expectations
• Clarify reasons for rejecting alternative options

• Basic computer and internet skills
• Ability to read course instructions in English