SEP522 요구공학 (Requirement Engineering)
 Instructor: 김익환
(ikkim707@gmail.com, Twitter:@ikkim56,
 Class Hour: 2011.4.18 – 2010.8.8
010-9062-6171)
Monday 14:00~17:00
 http://code.google.com/p/sep522/Downloads/Syllabus_SEP_522......doc
 Goals: Students will
1.
learn practical capability to write Software Requirements Specification(SRS) for various kinds
of software in the real world.
2.
understand why requirements engineering is important and very difficult to master.
3.
understand how requirements are related to every aspect of the software development.
4.
learn how to write various documents related to requirements.
5.
write a real world SRS by simulating a real world project at software company.
6.
learn how the real software companies in Silicon Valley operate.
Selected Reference Material:
1.
SWEBOK (2004 version) www.swebok.org/home.html
2.
IEEE Recommended Practice for Software Requirements Specifications (830-1998)
Grade: Midterm (20%), Project(40%),
Final(40%)
Class Discussion
1
Project Stages, Comments
Description of course and explanation of
SRS History&Purpose
SE from Requirements’ view point
2
Overview of Software Engineering(SE)
3
Explanation of Requirements in details #1
4
Explanation of Requirements in details #2
5
Brief discussion of SWEBOK.
SRS Project Inception stage
Discuss what to consider in writing SRS
Write MRD
Explanation of SRS template #1
Decide SRS topic and start writing SRS
6
Project Discussion & Selection
7
Explanation of SRS template #2
8
Mid-term
Knowledge-focused
9
SRS Chapter 1,2,3 Homework
Finish MRD
10
Requirements Specification(IRS) explanation
test
SRS Chapter 5,6 Homework
11
SRS Chapter 4,7 Homework
How to write System Specification
12
SRS Chapter 4,7 Homework Review #1
Software Design Specification(SDS)
13
Brief review of System Specification
Development Process Diagram in real world
SRS Chapter 4,7 Homework Review #2
Developing at Silicon Valley SW company
How to integrate UI, IRS, DB and Ch7
CMMI Perspective
14
Full review of SRS project
15
Project presentation
Presentation of final version of SRS
16
Final Exam
Real world case based
2009년 11월 27일 오후 3시 3분
test
106753783
모든 Communication 은 http://code.google.com/p/sep522/ 을 사용한다.
 교수와 학생, 프로젝트 팀간의 모든 공지, 연락사항은 "Wiki" 를 사용

유일한 공식적인 Communication Channel 이다.

매일 몇 시간 마다 한번씩 Check 한다.

다른 Communication 은 보조 수단이다.
 파일 배포는 "Download" 에서 한다

버전관리가 필요한 파일의 경우에는 "Source"를 사용한다.
 이슈등록 및 처리는 "Issues"

제출한 SRS 의 Feedback 을 주기 위해서는 Tagging 이 필수이다.

Issue status flow

New (보고자)  Accepted  Started  Done or Fixed  Verified (교수)
 Project 관련 문서나 소스코드는 "Source"를 사용

SRS 제출은 tags directory 에 tagging 을 한다.
svn/
branches/
tags/
Project_name1_srs_week1
trunk/
Project_name1/
build/
doc/
/* SRC 문서 저장할 곳 */
src/
/* Function Prototype for component */
inc/
lib/
etc/
bin/
Project_name2/
2009년 11월 27일 오후 3시 3분
106753783