소프트웨어 종합설계 (Software Capstone Design) August, 2017 Jongmoo Choi choijm@dankook.ac.kr http://embedded.dankook.ac.kr/~choijm

Introduction What is Capstone Design (종합설계)? Three essentials Source: www.coe.neu.edu/Groups/mimecap/What.html Three essentials Open-ended problem: based on SW knowledge learned from courses Collaboration: teamwork, design methodology Communication: presentation, discussion

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년 2학기 예

Objective Team 3 persons per a team (possibly 2 or 4 if necessary) Team leader and members Role Team leader: communicate with a professor (email, 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

Objective Communication Presentations: roughly 6 times Team introduction, Brain storming, Design proposal, Progress, Evaluation, Final presentation Documents: 2 times Design report, Final report Demonstration: final exhibition day Poster Topic Survey 1. Market trend, 2. Key technology, 3. Proof of Concept (or Scenario) Candidates: IoT, Cloud, Big data, Deep learning, …. Discuss with a professor (or professors) Strongly recommend all members to participate survey presentation

Expected Schedule 8/28: Introduction 9/4: Team introduction, Team presentation 9/11: Brain storming (RA), Team presentation, Peer evaluation 9/18: Individual team meeting 9/25: Proposal, Team presentation, Design report 10/2: Survey 1 10/16: Survey 2 10/23: Survey 3 10/30: Progress, Team presentation 11/6: Invite talk 11/13: Evaluation, Team presentation 11/20: Individual team meeting 11/27: Final presentation with video clip 12/4: Demonstration with Poster 12/11: Final report with discussion Notice: 강의 진행에 따라 일정은 조정될 수 있음 Peer review: 6/4/2만원

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

Expected output Presentations Documents Design results Poster Submit to choijm@dankook.ac.kr before the 6 PM on the previous day of the due day Design results SW, HW, Mockup, … Poster Video clip Demonstration day

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

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

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

Discussion