20050061 Geun-woo Kim ( 김근우 ) 20070124 Bo-seung Kim ( 김보승 ) 20080590 Jung-pil Yoon ( 윤정필 )

Slides:



Advertisements
Similar presentations
Presentation of Specialized software for shipping! wizards Client-specific user interface **2012: Danaos participates at the usability group working towards.
Advertisements

ARCH-05 Application Prophecy UML 101 Peter Varhol Principal Product Manager.
Spades Game Application with Video Conference Group 12 Anıl Yaman Emre Ergün Hüseyin Aktaş Pınar Tekir.
A social app for soccer-holics KIM, Sang Yeon PARK, Jae Hyun LEE, Joo Ho.
Write Your Project Title Here VU Logo Here Group Members Introduction Write your group members introduction here with names and VU Id.
Lord of Fries Team: Order of Fries. Team Members Carson Lee - Documentator Daniel McCue - Coder Franchesca Chung - Tester Michael Zhu - Coder James Sheldon.
Design of Web-based Systems IS Development: lecture 10.
0-1 Team # Status Report (1 of 4) Client Contact –Point 1 –Point 2 Team Meetings –Point 1 –Point 2 Team Organization –Point 1 –Point 2 Team #: Team Name.
Layered Game Architecture Li Yin Joe Polastre Takashi Suzuki Noah Treuhaft.
DePaul Bears Try Your Luck! Plan Methodology. Team Methodology Effective Communication s, phone calls, on-line chats, in-class meetings, outside.
OnME Platform Tutorial Ken Hui System Analyst OnME Research Laboratory.
0-1 Team # Status Report (1 of 4) Client Contact –Status Point 1 –Status Point 2 Team Meetings –Status Point 1 –Status Point 2 Team Organization –Description.
Networking Within MMOs Scott Seeley. Differences in game networking Peer-to-peer Client/Server Distributed Server.
Authentication Center for SDP Federation Motorola Israel Project: ADD The Team: Alina Mirinzon Gabi Brontvin Raz Zieber Dadi Suissa.
1 Decomposing the System Requirements  Specifications (Use cases)  Design --classes **entity **boundary **control --sequence diagrams --CRC cards **responsibilites.
0-1 Team 1 Status Report (1 of 3) Client Contact –Point 1 –Point 2 Team Meetings –Point 1 –Point 2 Team Organization –Point 1 –Point 2 Team 1: Auto-Owners.
Project title Team Members. Project Title Brief description of the project in bullet form.
0-1 Team ?? Status Report (1 of 3) Client Contact –Point 1 –Point 2 Team Meetings –Point 1 –Point 2 Team Organization –Point 1 –Point 2 Team 1: Auraria.
The interactive pub quiz game Interactive. Group Members Jo Chandler Jo Chandler Chris Martin (in Thailand!) Chris Martin (in Thailand!) Robin Noyce Robin.
Virtual Mechanics Fall Semester 2009
Requirement Analysis Functional & Non-Functional Requirements Scenarios Use cases: – View Fixtures – Manage Tournament – Register Team – Report Discrepancy.
These slides are designed to accompany Web Engineering: A Practitioner’s Approach (The McGraw-Hill Companies, Inc.) by Roger Pressman and David Lowe, copyright.
Windows Azure Team 9 Ben Holland Bao Nguyen Eric Petrowiak Barret Schloerke.
Example  Software for a virtual library (borrowing books using the Internet) Internt terminal DB.
Session 26 Modeling the Static View: The Deployment Diagram Written by Thomas A. Pender Published by Wiley Publishing, Inc. October 27, 2011 Presented.
CYBERSIM Dec Client: Information Assurance Center Advisor: Dr. Doug Jacobson Group Members: Ryan ApplegateCprE Saddam KhattakCprE Dan NguyenCprE/JLMC.
Verb Expansion Game Team 3 Bryan Bloss Jeremy Comardelle Gordon Gable Gleyner Garden Sponsored By: Dr. Beth Young.
Project Dragon Small Business Website Content Management System.
University of Palestine Faculty of Engineering and Urban planning Software Engineering department Software Engineering Group Project Design Document for.
KFC VIETNAM ORDER SYSTEM HTC TEAM. AGENDA 1.TEAM INTRODUCTION 2.PROJECT OVERVIEW 3.PLAN 4.PRODUCT ARCHITECTURE 5.DATABASE DESIGN 6.TEST PLAN & TEST REPORT.
PMCenter Project SPRING 2004 MOSP Team GEO. 2 Agenda Introduction Semester Goal Project Management ­Iteration Plan ­Risk Management ­Process Handbook.
HIMALAYA Test Review 16/12/2013 D4.8 Demonstration software subsystem unitary test report.
Fifa World Cup Spain Vs. Germany Maha Al Kuwari 7B.
Software Life Cycle The software life cycle is the sequence of activities that occur during software development and maintenance.
Final Class Diagram for C++ Implementation Clickermatic Software Clicker.
Understanding the Threats of and Defenses Against Cyber Warfare.
Natural Language to Machine Readable Format By: Damian Tamayo Presentation 2 – Nov. 13, 2009 CIS 895 – MSE Project.
Requirement Engineering. Recap Elaboration Behavioral Modeling State Diagram Sequence Diagram Negotiation.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
Slide 1 What the business needs  How to build it Functional requirements  + Nonfunctional requirements Performance System environment issues Problem.
ViralFlux and Logo Start New Game Load Save Game Start Multiplayer Game Change Settings Exit Game ViralFlux Flavor Text.
Homework #8 - Deliverable 5 due: 2 December 1. Exec Summary 2. Revisit Use Cases 3. The Analysis Model Class Diagrams Interaction Diagrams 4. Non-Functional.
Members:Toh Wei Jian Yeow Chun Wei Leong Zhao Sen Boh Gee Chuan Chuan Khai Jin Shane Supervisor:Mr Ee Kiam Keong Assessor:Mr.
4+1 View Model of Software Architecture
SynergySoft™ Distributed Meeting Scheduler Requirements Review Yasaman Haghpanah Ravindra Rudraraju Sowjanya Sakruti Jim Whitaker.
SmartPosition Customer Review and Feedback Presentation.
Prometheusaurus Final Demo Team Software Project Group #1 Fall 2012 Steve Danowitz, Kelly Helhowski, Emily Christ, Corbin Uselton, Chris Leer, and Briana.
Project 1 Data Communication Spring 2010, ICE Stephen Kim, Ph.D.
PROJECT SECME Carthik A. Sharma Juan Carlos Vivanco Majid Khan Santhosh Kumar Grandai. Software Engineering Fall 2002.
Client Acceptance Test Michel Atoudem Kana. 29 January 2003Client Acceptance Test2 Content System Architecture The Problem Project Organisation Project.
Behavioral Intervention Plan (BIP) By: Carrie Batschi & Haley McLean.
Supervisor : Trần Vinh Thu
CSC 110 – Fluency in Information Technology Chapter 7: An Introduction to Debugging Dr. Curry Guinn.
Objective – Teach players to run with the ball and scan the field
Mobile-Controlled Lighting
File service architecture
Write Your Project Title Here VU Logo Here
استراتيجيات تعديل السلوك بين النظرية والتطبيق
Skill – Tackle & Defensive Fundamentals
Dribbling Technique Practice 1.2 teams of 5 in their own channel
Decomposing the System
Defensive Heading Technique Practice
Structure diagrams for lab 13
Long Passing Technique Practice 1.2 teams of 5 in their own channel
Finding the nth term, Un Example
Online Pogo Game Customer Service
Pogo Game Customer Care Helpline Number

Call Pogo Contact Phone Number and Enjoy Pogo Game
Presentation transcript:

Geun-woo Kim ( 김근우 ) Bo-seung Kim ( 김보승 ) Jung-pil Yoon ( 윤정필 )

 Civilization Craft  Turn-based attack & defense game  Consume resources & Create units  Attacker – Attack the castle using his or her units  Defender – Defend the castle using his or her units  Turn limit(50 Turn / 25 vs 25)  1 vs 1 / 2 vs 2 Network match  Attacker(or Defender) players use their turn together  Attacker client / Part of server system

 Functional Requirements  Non-functional Requirements

 Functional Requirements (Use Case - Client)  Client Use Case Diagram

 Functional Requirements (Use Case - Client)  Client Use Case Diagram  Image Slide

 Functional Requirements (Use Case - Server)  Server Use Case Diagram

 Functional Requirements (Use Case - Server)  Server Use Case Diagram  Image Slide

 Non-functional Requirements  Performance  Unit action -> Less than 1 Sec  Map loading -> Less than 1 min  Safety  If an error occur during the game, the program must be ended in working order.

 Architecture Diagram

 Image Slide

 Structural models  Class diagram  Behavioral models  Sequence diagram

 Class Diagram

 Image Slide

 Sequence Diagram  Unit create

 Sequence Diagram  Unit create  Image Slide

 Sequence Diagram  Draw map

 Sequence Diagram  Draw map  Image Slide

 Geun-woo Kim  Client program implementation(Sub)  Presentation / Diagram modification  Bo-seung Kim  Server program implementation  Presentation / Diagram modification  Jung-pil Yoon  Client Program Implementation(Main)  Diagram modification

 Software development process  Requirement specification to implementation  The difficulties of making software  The importance of the documentation  Communication between team members / group members

 The demonstration of Civilization Craft

Thank You!