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.
이 강좌는 Requirements Engineering: Secure Software Specifications 전문 분야의 일부입니다.
SRS Documents: Requirements and Diagrammatic Notations
제공자:
About this Course
최근 조회 10,385회
공유 가능한 수료증
완료 시 수료증 획득
100% 온라인
지금 바로 시작해 나만의 일정에 따라 학습을 진행하세요.
다음 전문 분야의 5개 강좌 중 5번째 강좌:
유동적 마감일
일정에 따라 마감일을 재설정합니다.
초급 단계
완료하는 데 약 7시간 필요
권장: 4 weeks, 1-2 hours/week
영어
자막: 영어
제공자:
콜로라도 대학교
The University of Colorado is a recognized leader in higher education on the national and global stage. We collaborate to meet the diverse needs of our students and communities. We promote innovation, encourage discovery and support the extension of knowledge in ways unique to the state of Colorado and beyond.
강의 계획 - 이 강좌에서 배울 내용
완료하는 데 2시간 필요
Beginning to Write an SRS Document
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.
완료하는 데 2시간 필요
4개 동영상 (총 39분), 3 readings, 1 quiz
4개의 동영상
Following Local Rules12m
Standardized Statement Templates5m
Global Organization Templates10m
3개의 읽기 자료
Introduction to Diagrammatic Notations - Slides20m
Local Rules | Standardized Templates - Slides20m
Global Organization Templates - Slides20m
1개 연습문제
Begin to Write an SRS Document30m
완료하는 데 4시간 필요
Beginning Diagramming
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.
완료하는 데 4시간 필요
3개 동영상 (총 17분), 5 readings, 1 quiz
5개의 읽기 자료
Diagramming-Adding Use/Misuse/Abuse Cases -Slides20m
Misuse Cases: Use Cases with Hostile Intent1h
Misuse and abuse cases: getting past the positive30m
Context and Problem | Frame Diagrams - Slides15m
Relating software requirements and architectures using problem frames1h
1개 연습문제
Use/Misuse Cases and High Level Diagramming30m
완료하는 데 3시간 필요
Lower-Level Diagramming
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.
완료하는 데 3시간 필요
3개 동영상 (총 18분), 2 readings, 1 quiz
3개의 동영상
SADT Diagrams: Actigrams and Datagrams5m
Data Flow Diagrams5m
2개의 읽기 자료
The entity-relationship model for multilevel security1h
Entity Relationship | SADT |Data Flow Diagrams - Slides20m
1개 연습문제
Lower-Level Diagramming30m
완료하는 데 4시간 필요
Tracing Events
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.
완료하는 데 4시간 필요
4개 동영상 (총 24분), 2 readings, 2 quizzes
4개의 동영상
Event Trace Diagrams5m
State Machine Diagrams6m
Concurrent StateCharts and R-Nets6m
2개의 읽기 자료
Putting the Diagrams Together | Event Trace Diagrams - Slides20m
State Machine Diagrams | Concurrent State Charts & R-Nets - Slides15m
1개 연습문제
Tracing Events30m
Requirements Engineering: Secure Software Specifications 전문 분야 정보
This specialization is intended for software engineers, development and product managers, testers, QA analysts, product analysts, tech writers, and security engineers. Even if you have experience in the requirements realm, this course will expand your knowledge to include new viewpoints, development styles, techniques and tools.
For anyone seeking a graduate degree, certificate, or professional degree in computer science, these courses will additionally give you a broad understanding of how requirements engineering is performed and help you get a first foot forward into your upcoming careers.
The Software Requirements specialization focuses on traditional software requirements elicitation and writing techniques, while also looking at requirements from a security standpoint. In traditional methods, non-functional requirements, such as security, are often ignored overall. In this specialization, students will be introduced to ways of eliciting requirements from stakeholders, how to analyze these requirements, conduct risk mitigation and analysis, prioritize requirements, document, and bring security concerns into the software lifecycle early on.
자주 묻는 질문
강의 및 과제를 언제 이용할 수 있게 되나요?
강좌에 등록하면 바로 모든 비디오, 테스트 및 프로그래밍 과제(해당하는 경우)에 접근할 수 있습니다. 상호 첨삭 과제는 이 세션이 시작된 경우에만 제출하고 검토할 수 있습니다. 강좌를 구매하지 않고 살펴보기만 하면 특정 과제에 접근하지 못할 수 있습니다.
이 전문 분야를 구독하면 무엇을 이용할 수 있나요?
강좌를 등록하면 전문 분야의 모든 강좌에 접근할 수 있고 강좌를 완료하면 수료증을 취득할 수 있습니다. 전자 수료증이 성취도 페이지에 추가되며 해당 페이지에서 수료증을 인쇄하거나 LinkedIn 프로필에 수료증을 추가할 수 있습니다. 강좌 내용만 읽고 살펴보려면 해당 강좌를 무료로 청강할 수 있습니다.
환불 규정은 어떻게 되나요?
재정 지원을 받을 수 있나요?
궁금한 점이 더 있으신가요? 학습자 도움말 센터를 방문해 보세요.