Term Project – Final

Term Project Final Presentation & Report

-최종 발표 데모에서 재미요소 (내용의 전개 등), 시각적 사실감 (realistic graphics, physics, character, complexity, background effects), 동적 요소 (animation, movement, user interface), 기타 (online help, configuration, usability) 등을 평가의 기초로 삼는다.

– 최종 보고서는 게임 소개, 게임플레이 방법, 사용자 인터페이스 설명 (다이어 그램과 그림을 포함시킬 것), 스케치, 디자인에 사용된 이미지, 게임 개발을 진행하면서 만들어진 다양한 버전, 플레이하는 게임 장면 사진을 포함하여 약 30개 정도의 그림, 기술적 문서 (메인 루프, NPC, FSM, 자료 구조, 구현된 그래픽 효과에 대한 설명과 그림, 기본적인 인공지능 알고리즘 설명, 네트워크 게임 경우 사용된 네트워크 메시지 다이어그림 및 설명, 게임 사운드 효과와 만들어진 방법), 게임 테스트 및 사용자 평가 내용을 포함한다.

– 팀별 기말 발표자료 (팀이름_final.ppt)와 최종 보고서 (팀이름_final.doc)를 제출한다.


참고: 게임 기획서 표준양식 개선안 (2006)

Term Project5

“Mobile VR ExerGame ” UI Design Document (due by 12/8)

제안했던 게임(“Mobile VR ExerGame ”)의 Technical Document 에서 확장하여 게임전체 흐름을 알 수 있도록 UI Design Document를 작성하여 12월 8일 발표한다. (10~15장)

제안한 게임 시나리오를 HCI적인 관점을 반영하여 UI 디자인을 재작성한다.

*그룹원 중에 한 명이 e-learning에 올릴 것

Term Project4

“Mobile VR ExerGame ” Technical Design Document (due by 11/10)

제안했던 게임 아이디어 브레인스토밍(“Mobile VR ExerGame ”)에서 확장하여 Technical Design Document를 작성하여 11월 10일 발표한다. (5장~10장)

Technical Design Document는 아래 제시한 바와 같이 작성하도록 한다.

-게임 제목
-게임 요약 (1-2장)
-게임장르, 플랫폼, 게이머 수, 게임 규칙 요약 (1-2장)
-Software design document
+게임 구조 (즉, 게임 루프)
+그래픽 (2D/3D) 디자인
+ 인터페이스 디자인
+사운드 디자인
-게임 요소 (i.e., Characters/NPCs, Items, Backgrounds/Terrinas, Events, Story, etc)

*그룹원 중에 한 명이 e-learning에 올릴 것

Finite State Machine (FSM)

Unity Gems: Advanced Tutorial on Finite State Machines


public enum EnemyStates
    sleeping = 0,
    following = 1,
    attacking = 2,
    beingHit = 3,
    dying = 4
public EnemyStates currentState = EnemyStates.sleeping;




Term Project 2

Game Production (470420-1)
– “Mobile VR ExerGame ” Brainstorming & Storyboarding
Fall 2015
2015년 10월 6일


Group term project assignment –
“Mobile VR Game” 브레인스토밍 (장수 제한 없음)
2015년 10월 13일 수업시간에 브레인스토밍 발표를 한다.


각 그룹별로 “모바일 가상현실 시스템 (Oculus Rift 등)을 사용한 운동게임,  인터랙션방식, 다중 사용자의 경우 협력적 모드, 지하철역/버스정차역/박물관/전시장 등에서 가볍게 즐길 수 있는 게임 )”에 대한 브레인스토밍 아이디어 발표 시 다음과 같은 정보를 포함하여 설명하도록 한다:


-그룹 멤버와 맡은 역할 소개
-게임플레이 아이디어
-모든 스토리보드 그림들


Project Management 101

Randy Pausch’s Tips for working successfully in a group

Tips for Working Successfully in a Group

By Randy Pausch, for the Building Virtual Worlds course at Carnegie Mellon, Spring 1998
Meet people properly.  It all starts with the introduction.  Then, exchange contact information, and make sure you know how to pronounce everyone’s names.  Exchange phone #s, and find out what hours are acceptable to call during.
Find things you have in common.   You can almost always find something in common with another person, and starting from that baseline, it’s much easier to then address issues where you have differences.  This is why cities like professional sports teams, which are socially galvanizing forces that cut across boundaries of race and wealth.  If nothing else, you probably have in common things like the weather.
Make meeting conditions good.  Have a large surface to write on, make sure the room is quiet and warm enough, and that there aren’t lots of distractions.  Make sure no one is hungry, cold, or tired.  Meet over a meal if you can; food softens a meeting.  That’s why they “do lunch” in Hollywood.
Let everyone talk.  Even if you think what they’re saying is stupid.  Cutting someone off is rude, and not worth whatever small time gain you might make.  Don’t finish someone’s sentences for him or her; they can do it for themselves.  And remember: talking louder or faster doesn’t make your idea any better.
Check your egos at the door.  When you discuss ideas, immediately label them and write them down.  The labels should be descriptive of the idea, not the originator: “the troll bridge story,” not “Jane’s story.”
Praise each other.  Find something nice to say, even if it’s a stretch.  Even the worst of ideas has a silver lining inside it, if you just look hard enough.  Focus on the good, praise it, and then raise any objections or concerns you have about the rest of it.
Put it in writing.  Always write down who is responsible for what, by when.  Be concrete.  Arrange meetings by email, and establish accountability.  Never assume that someone’s roommate will deliver a phone message. Also, remember that “politics is when you have more than 2 people” – with that in mind, always CC (carbon copy) any piece of email within the group, or to me, to all members of the group.  This rule should never be violated; don’t try to guess what your group mates might or might not want to hear about.
Be open and honest.  Talk with your group members if there’s a problem, and talk with me if you think you need help.  The whole point of this course is that it’s tough to work across cultures.  If we all go into it knowing that’s an issue, we should be comfortable discussing problems when they arise — after all, that’s what this course is really about. Be forgiving when people make mistakes, but don’t be afraid to raise the issues when they come up,
Avoid conflict at all costs. When stress occurs and tempers flare, take a short break. Clear your heads, apologize, and take another stab at it.  Apologize for upsetting your peers, even if you think someone else was primarily at fault; the goal is to work together, not start a legal battle over whose transgressions were worse. It takes two to have an argument, so be the peacemaker.
Phrase alternatives as questions.  Instead of “I think we should do A, not B,” try “What if we did A, instead of B?”  That allows people to offer comments, rather than defend one choice.