Timeline
| Activities |
Timeline |
Tasks |
Action by
|
| Project Sourcing and Registration |
Week -16 to Week -8
|
- Team Formation
- Confirmation of Sponsor
- Project Sourcing & Requirements Gathering from Sponsor
|
Students
|
| Proposal |
Due before the start of Week -8
|
- Proposal Submission (see below for templates)
|
Students (Email to SMT Programme Director)
|
| Decision on Proposal |
Week -4
|
- Review by SMT Programme Director (Acceptance/Rejection)
|
SMT Programme Director (Optional: Sponsor)
|
| Supervisors Assignment |
Week -1
|
- Supervisors - Teams Assignment
|
Project Coordinator
|
| Start of Project
|
Week 1
|
|
Students
|
| Midterm |
Week 7 to 9
|
|
Students, Supervisor, SMT Programme Director (Optional: Sponsor)
|
| Finals |
Week 13 to 16
|
|
Students, Supervisor, SMT Programme Director, Sponsor
|
Additional note: after acceptance of the project proposal, students will need to bid for IS483 (not SMT483) during BOSS2, and they should bid only e$10. If there is insufficient e$ balance in a student's account, they will not be able to enroll in IS483 even if their team's proposal is accepted.
SMT Project Types
|
|
Type I - Application Project
|
Type II - Smart City Analytical/Research Project
|
| Team Size |
4-6 |
2-3
|
| Objective and Scope
|
- To design and implement a smart city application that incorporates a combination of technology enablers, and which addresses an urbanisation, sustainability, or societal challenge in domains such as housing, environment, etc.
|
- (Analytical) To conduct an evidence-based analysis of smart city blueprint (locally or overseas) or analytical models addressing an urbanisation, sustainability, or societal challenge in different domains such as housing, environment, etc.
- (Research) To conduct research based on an identified problem related to addressing a smart city challenge. The scope may include a new algorithm / approach, simulation, and/or analysis for urbanisation, sustainability, or societal challenge in different domains such as housing, environment, etc.
|
| Recommended Skill-sets / Pre-requisites
|
- You should have passed: IS111 Introduction to Programming, SMT203 Computational Social Science: Principles and Applications, IS112 Data Management
- For the AY2022 intake, IS212 Software Project Management is a co-requisite
- Other highly recommended courses: Interaction Design & Prototyping, Web Application Development I & II, Internet of Things
|
- Empirical Studies, Research Methods, Analytics Foundation, Geographic Information Systems, Sustainable (Digital) Cities, Introduction to Public Policy.
|
| Project Sponsor / Supervisor
|
- SCIS-sourced OR
- Self-sourced external sponsor OR
- SCIS faculty supervisor
|
- SCIS-sourced OR
- Self-sourced external sponsor OR
- Faculty supervisor (from SCIS or any school) supervises team
|
| Expected Outcomes
|
- System prototype and documentation
- Midterm presentation
- Final presentation
- Final report
|
- Proposal of the problem
- Wireframe/Proof-of-concept/analytical model/city blueprint along with evidence-based analysis
- Midterm presentation with approaches and initial findings
- Final presentation
- Final report
- Dashboard/analytical model, acceptance/review by sponsor
|
| Available Period
|
- Year 3 Term 1 onwards (Y3T2 onwards preferred)
|
|
Assessment Weightages
| Assessment Item(s)
|
Weightage (%)
|
| Type I - Application Project |
Type II - Smart City Analytical/ Research Project
|
| Project Proposal |
10 |
10
|
| Mid-term presentation* |
20 |
30
|
| Final Presentation |
40 |
20
|
| Final Report |
30 |
40
|
| Total |
100 |
100
|
(*) If needed, Type II projects may optionally complement their midterm presentation with a midterm report (discuss with your supervisor).
Assessment Details
| Assessment Item |
Type I - Smart City Application Project |
Type II - Smart City Analytical/Research Project
|
| Project Proposal
|
- Clarity of project
- Project plan and schedule
- Benefits to society
|
- Clarity of project
- Project plan and schedule
- Benefits to society
- Description of available data
|
| Mid-term
|
- Project management
- Quality of project, including demo
|
- Project management
- Literature survey
- Preliminary findings
|
| Final Presentation
|
- Motivation and solution approach
- Project management
- Demonstration of product
- Reflections and learning outcomes
|
- Motivation and solution approach
- Project management
- Research / analysis findings
- Reflections and learning outcomes
|
| Final Report
|
- Key findings to demonstrate value to sponsor and benefits to society
- Real challenges faced, mitigation steps and lessons learnt
|
- Key findings to demonstrate value to sponsor and benefits to society
- Real challenges faced, mitigation steps and lessons learnt
|
Document Templates
Project Proposal
- Type I Project Proposal [docx]
- Type II Project Proposal [docx]
Final Report
We recommend* that you write your final report using the IEEE double-column conference paper template. This is available from either of the following links:
- Official Microsoft Word Template: here
- Collaborative Overleaf (LaTeX) Template: here
There is no strict upper word limit, but concise technical writing is preferred. (FYI: academic publications that use this format rarely exceed 10 pages!)
(*) The above template is only a recommendation, and you are free to use any other appropriate template if you prefer (see, for example, the reports of previous projects). Content is what counts!
