소프트웨어 종합설계 (Software Capstone Design)

Presentation on theme: "소프트웨어 종합설계 (Software Capstone Design)"— Presentation transcript:

1 소프트웨어 종합설계 (Software Capstone Design)
September 1, 2016 Jongmoo Choi

2 Introduction What is Capstone Design (창의적 종합설계)? Three essentials
Source: Three essentials Open-ended problem: based on SW knowledge learned from courses Collaboration: teamwork, design methodology Communication: presentation, discussion

3 Objective Open problem Design topic: anything each team wants
Need to be related to the recent hot topics such as IoT, Bigdata, Cloud, Deep learning and so on Also need to be based on the courses you’ve already taken in the department of software Not recommend to develop an App alone. (Modifying Android framework is welcomed) 2016년 1학기 예

4 Objective Team 4 persons per a team (possibly 3) Role Team activities
Team leader and members Role Team leader: communicate with a professor ( , submit) Team members: need to have his/her own role in team activities Team activities Design and Implementation Presentation and Document Demonstration at exhibition Background knowledge survey Notice Members in the same team may have different grade. Anyone who has his/her own role has a favorable position for good grade

5 Objective Communication Presentations: around 6 times
Team introduction, Brain storming, Design proposal, Progress, Evaluation, Final presentation Documents: 2 times Design report, final report Demonstration: the final exhibition day Poster Fundamental knowledge survey One topic per each team Candidates: IoT, Cloud, Big data, Deep learning, …. Discuss with a professor (or professors) Strongly recommend all members to participate survey presentation

6 Expected Schedule 9/7: Introduction
9/21: Team introduction, Team presentation 9/28: Brain storming (RA), Team presentation, Peer evaluation 10/5: Proposal, Team presentation, Design report 10/12: Individual team meeting 10/19: Fundamental survey 1 10/26: Fundamental survey 2 11/2: Progress, Team presentation 11/9: Fundamental survey 3 11/16: Fundamental survey 4 11/23: Fundamental survey 5 11/30: Evaluation, Team presentation 12/7: Individual team meeting 12/14: Final presentation, Final report 12/15: Demonstration with Poster Notice: 강의 진행에 따라 일정은 조정될 수 있음

7 Presentation Requirement
Team introduction Team name, Each member’s characteristics, plan Brain storming Idea proposal, Business Model Canvas Proposal How to design. Based on Design methodology Progress Component test results Evaluation Integrated system test results Final presentation All what you do Notice: include humor slide

8 Presentation Requirement
Business Model Canvas

9 Expected output Presentations Documents Design results Poster
Submit to before the 6 PM on the previous day of the due day Design results SW, HW, Mockup, … Poster Video clip Demonstration day

10 Evaluation 강의 평가 팀별 평가 개인별 평가
시스템 완성도(20%), 창의성 (15%) Fundamental knowledge survey (15%) Survey는 중간 고사/기말 고사 대치 자료임 (중요) 발표 내용, 보고서 완성도 (10%) 개인별 평가 발표 횟수, 발표 내용 (10%) 질의 응답 (10%) 보고서 기여도 (10%) Team leadership (10%) Notice: 1) 평가 기준은 강의 진행에 따라 변경 가능, 2) 같은 팀이라도 다른 점수를 받을 수 있음

11 Reference 공학설계의 원리와 실제 I부: 공학 설계 프로세스 II부: 설계 도구 III부: 전문가 기술 부록 공학 설계
프로세스 선택 및 필요성 인식 요구사항 명세서 개념 생성 및 평가 II부: 설계 도구 시스템 설계: 기능 분할 시스템 설계: 동적 모델 테스트 시스템 신뢰성 III부: 전문가 기술 팀과 팀워크 프로세스 관리 윤리와 법적인 문제들 프레젠테이션 부록 제안서, 최종 발표 예시

12 To do 다음 수업 준비 사항: 팀 구성 Team introduction PPT 준비
팀 이름: 신중하게 작명 하시고.. (가능하면 설계 주제를 나타낼 수 있도록) 관심 분야: Initial proposal if possible 팀원 소개 컴퓨터 전공 분야 중 관심 있는 것 및 이유 자신이 지금까지 수행한 대표적인 과제 or 작성한 프로그램 미래의 모습 Humor Slide 추가 수업 전날 오후 6시까지 전송