4. Do U know Imagine Cup?
• World software industry’s largest student technology
competition
– Over 300,000 students from 100 countries entered in 2009
• Like the Olympics for TECHNOLOGY Students!
– The winner from Thailand compete at the world finals held in a
different country each year
• 4 CATEGORIES
– SOFTWARE DESIGN – Thailand & Poland
– MULTIPOINT DEVELOPMENT – Thailand & Online
– GAME DEVELOPMENT – Online
– DIGITAL MEDIA – Online
17/01/10 ICT@Mahidol 4
5. Host Countries
1 Spain
6
18 5 3
7 4
2 Brazil
3 Japan
2
4 India
5 South Korea 6 France 7 Egypt
16. Proposal outline
Application Name Project
Team Name Background
& Elementary
Team Members
Information
Short Description
User Scenarios
Functional and non-functional Analysis
requirements
Summary of Application Components
Technologies/Resources Used in the
Application Preliminary
Design
Architectural Overview
User Interface Prototype/Examples
17/01/10 ICT@Mahidol 16
17. Project background (1)
• Application Name – “Catchy Title”
– Concise and meaningful
• Live Book, Windows Light, Wikipedia
– Unique, attractive, unconventional, innovative
• Bing.com , Longdo.com
• Team Name
– Statement of personality/characteristics of your team
• Team Member
– Name & School
17/01/10 ICT@Mahidol 17
18. Project background (2)
• Short Description - “First Impression is very important!”
– How important is your problem in respect of Imagine Cup
theme?
– Highlights of your solution
– Technology used
– Benefits gained
17/01/10 ICT@Mahidol 18
19. Project background (cont.) –
Concept of writing
Introduction
general -> specific
Body
Conclusion
specific -> general
17/01/10 ICT@Mahidol 19
20. • Application Name / Team Name
• Short Description
• 20 minutes
17/01/10 ICT@Mahidol 20
21. User Scenario
An actor may participate in
Use case analysis
many use case. A use case
Identify your actors may have many actors
Key question – who will use your application?
Identify your use cases
Key question – what are the functions that your actors can
use from your application?
User scenario = the steps that your actors will involve in
your use cases
Key question – what are the situations when the actors will
use your application and how do they do?
17/01/10 ICT@Mahidol 21
23. Functional and non-functional requirements
• Functional Requirements
– Function name (corresponding to your use cases)
– Function short description
– Technology or technique used
– Inputs & Outputs
• Non-Functional Requirements
– Additional requirements on user information design,
hardware, devices, platforms, security, networking, etc.
17/01/10 ICT@Mahidol 23
25. Summary of Application Components
• Idea: “Group your functions into meaningful modules”
• Example
– Shopping Cart Component
• Display the products that the user wants
• Check out to bring to the checkout
– Electronic Payment Component
• Fill in payment details
• Confirm payment
• Charge!
17/01/10 ICT@Mahidol 25
26. Technologies/Resources
Used in the Application
• Core Microsoft Technologies
• Special Technologies used in your project
• Content Supplements
17/01/10 ICT@Mahidol 26
27. Windows Form Web Form
Mobile Form
17/01/10 ICT@Mahidol 27
28. Core Microsoft Technologies
Operating System
Microsoft Windows 7
Microsoft Windows Server 2008 R2
Tools
Microsoft Visual Studio 2008 Pro.
Microsoft Expression Studio
Database
Microsoft SQL Server 2008
Technologies
Microsoft .NET Framework 3.5 sp1
17/01/10 ICT@Mahidol 28
29. Special Technologies used in
your project
Hardware
Windows Phone
Microsoft Robotics Studio
Design
Microsoft Silverlight
Entertainment
DirectX 11
Business
Bing Search Engine, Bing Maps
17/01/10 ICT@Mahidol 29
30. Content Supplements
API
Facebook,Twitter,Youtube,Windows Live
Microsoft Speech API
Web Services
Technology Sponsor
Microsoft Multipoint ®
K-bank
Anything you want…
17/01/10 ICT@Mahidol 30
31. Architectural Overview
• Idea: “Picture is worth a thousand words”
• Show how to plug these together:
– Application components
– Technologies/resources used in the application
– External resources
17/01/10 ICT@Mahidol 31
32. User Interface Prototype/Examples
• Idea: “Show sample of your solution and how to use it”
– Attractive design
– Clarify your functionality
Note that: you don’t need to include all screens and
dialogues. Just highlight the main and eye-catching ones.
17/01/10 ICT@Mahidol 32
34. • Summary of Application Component
• Technologies in used
• Architecture Overview
• User Interface / Prototype
• 1 hours
17/01/10 ICT@Mahidol 34
35.
36.
37. • Asst. Prof. Dr. Thanwadee Sunetnanta
(Deputy Dean for Administration ICT at Mahidol)
for content
• Microsoft Student Partner @ Mahidol University
• ICT @ Mahidol University
• Microsoft Thailand
• In Marketing Co.,Ltd.
17/01/10 ICT@Mahidol 37