|
所在平台: Coursera |
课程主页: https://www.coursera.org/learn/srs-documents-requirements
课程评论：没有评论
课程名称：软件需求规范文档（SRS）与图示符号 课程概述：在需求收集和优先级排序的过程中，需求的文档化同样至关重要。在本课程中，我们将讨论和实践如何将需求转化为对客户及开发人员都易于理解的文档。设计师或开发人员在阅读文档时，应该能够理解整体构思、范围、领域、资源、期望，以及为何未选择其他替代方案。为实现这种文档，我们需要在叙述（配合图示）与复杂图表之间找到平衡。 课程大纲： 1. **撰写SRS文档的起始** 描述：开始撰写软件需求规范文档（SRS）可能让人感到压力很大。随着需求获取的开始，您应该规划您的方法并尽早开始写作。在这一模块中，我们会讨论成功过程中应遵循的本地和全球规则。 2. **初步图示** 描述：在需求文档中，您需要讲述一个故事，而图片有助于传递故事！在本课中，我们将探讨可以创造的“图片”，以帮助所有读者明确理解内容，并确保所有要点都得到清晰和完整的表达。具体来说，我们将考虑高层次的系统范围图。 3. **低层次图示** 描述：在更低的层面上，可以使用实体关系图、数据流图和SADT图。这三种图表共同解释系统组件的关系和数据流动。在本课中，我们将讨论这些图表的样式及应包含的信息。 4. **事件追踪** 描述：系统级图示与低级图示相互结合。每个低级图示也与其他低级图示相关。此外，我们还需要图示来解释事件。 5. **组合与确认图示的一致性和完整性** 描述：为SRS文档创建的所有图表必须彼此关联，同时也要在文本中得到解释。在本课中，我们将考虑图表之间的相互关系，如何通过多个图表的组合来分析系统观点和说明内容。我们还将简要讨论针对任务关键和安全关键系统的规范写作的更正式格式。最后，我们将讨论如何使用图表与SRS文档中的文本相互呼应——请记住：您在讲述一个故事！
Name:Beginning to Write an SRS Document
Description:Beginning to write a Software Requirements Specification (SRS) is a daunting process. As you start elicitation and move onward through the requirements cycle, you should plan your approach and begin writing as soon as possible. In this module, we discuss local and global rules that should be followed to lead to success.
Name:Beginning Diagramming
Description:Within a requirements document, you should tell a story. Pictures help in stories! In this lesson, we'll look into some of the "pictures" that you can create to clarify understanding for all readers and to help yourself know that all points are being covered clearly and completely. Specifically, we'll consider high, system-scope diagrams.
Name:Lower-Level Diagramming
Description:At a lower level, Entity Relationship Diagrams, Data Flow Diagrams, and SADT diagrams can be used. All three sets of diagrams work together to explain lower-level relationships and dataflow for components in the system-to-be. In this lesson, we'll discuss what these diagrams look like and what information should be included in such diagrams.
Name:Tracing Events
Description:System level diagram and low level diagrams work together. Each low level diagram also relates to other low level diagrams. In addition to these diagrams, we also have diagrams to explain events.
Name:Combining and Confirming Diagram Consistency and Completeness
Description:All diagrams created for a SRS document must link together, in addition to being linked to and explained in the text. In this lesson, we consider inter-view relationships between diagrams and how the combination of multiple diagrams assists in analysis of our system view and explanation. We also talk briefly about a more formal format of requirements writing for mission critical and safety critical systems. Lastly, we discuss using diagrams to correspond with text in the SRS document- remember: you're telling a story!
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.
