MODULE OUTLINE Created: 04-Aug-2008, Updated: 22-Jul-2014
Module Code CS4274
Semester Semester 1, 2014/2015
Modular Credits 4
Faculty School of Computing
Department Computer Science
Timetable Timetable/Teaching Staff
Module Facilitators
ASSOC PROF Pung Hung Keng Lecturer
CHEN PENGHE Teaching Assistant
MR Chan Chee Heng Others
WONG YONG JIE Teaching Assistant
LIM HONG WEI KELVIN Teaching Assistant
Tags --

Learning Outcomes | Prerequisites | Teaching Modes | Schedule | Synopsis | Syllabus | Practical Work | Assessment | Preclusions | Workload | References


Mobile phone is becoming more pervasive and capable of supporting many applications traditionally only suitable for desktops or laptops.  However, the technologies developed for conventional networked computing involved mostly relatively static devices may not be entirely relevant to mobile computing. This course aims to identify and study their differences in terms of system requirements focusing  on the enabling networking technologies for mobile and multimedia computing with the following objectives in mind: (i) understand the characteristics,  system and user requirements of mobile and multimedia systems, and the driving forces for the convergent of mobile computing and multimedia computing, (ii) understand the working principles of the key enabling technologies – various networks, mobile devices and software support -  for mobile and multimedia computing, and (iii) develop problem solving methodology and skills  through a practical term project in mobile multimedia applications.

After attending this course, s
tudents should be able to:

1. appreciate the converging trend of multimedia computing and mobile computing and its enormous potential applications as a result. 
2. understand and appreciate the extra system requirements and design considerations needed for mobile and multimedia applications in comparison with that of the conventional computing applications.
3. have a better insight into the operations and programming capabilities of the underlying network protocols and middleware for the development of mobile and multimedia applications.
4. conduct literature survey and be more critical on existing solutions or work(mainly in the context of term project). This helps me to identify new issues or to form new opinion which may subsequently lead to better project ideas.
5. take a systematic approach with rigorous analysis and a suitable development methodology for software projects.
6. apply some of the knowledge gained from the course, and programming tools, techniques and skills learned from the project to other software engineering projects.

CS2105 --> CS3103  --> CS4274

Please take note:
There is also a term project (50% of course weightage) requiring programming skills in TCP/IP server/client network programming and Android Java programming. Students are expected to learn the essential programming skills on their own as in your FYP. 


A combination of the traditional lecturing, supplemented by readings, problem solving as homework and term's projects.

(a)  Lectures:
      Two hours per week 
(b) Tutorials on problem solving:
      one hour per week – Tutorial problem sets will be disseminated via IVLE.
(c) Term projects:
     Students form teams each consisting 2-3 members  to work on a term project. The project carries a weigth of approximately 50% of the course work.
     Students will go through the following processes and activities during the project cycle:
      i)  acquiring background knowledge and programming capability development (learning Android programming on the job with some  programming resources )
      ii) identification, analysis and formulation of a problem (the output is a project proposal to be presented orally to the lecturer),  
      iii) synthesis of a solution (output is a design proposal report to be submitted for grading),
      iv) development of a prototype and its evaluation (output is a demonstratable prototype, a final written technical report and an oral project presentaion)
     The classroom course work is not on programming which is needed for doing your term projects. Students who are not comfortable with system and network programming ( TCP/IIP programming, web server, java in Android)
     will find this course very challenging
. Also the workload of this course may appear to be higher to students who are not proficient in system programming due to their longer learning curve.  
     You have to bear in mind of these challenges when deciding to take this course.




Lecture:  Fri 1000-1200 L(1) Venue: VCRm @ COM1(Video Conference Room) 

Term Projects :
     Starting date: 1st academic Week (starting 11 Aug 2014)
     End date: early Nov 2014
     Mid term review of the project: Week 6th, 15 Sep 2014
     Final evaluation of project: Week 12th or 13th,  two weeks before the reading week in Nov 2014

Tutorials: COM1 0208 (Weekly, starting 3rd week)

Lab Venue: Data Communications and Networking Lab 2 at COM1#B-01

Programming consultation @ the lab:  Schedule TBA

Exam: Afternoon session on 2nd Dec 2014


Mobile phone is becoming more pervasive and capable of supporting many applications traditionally only suitable for desktops or laptops.  A question immediately coming to our mind is: Are those enabling technologies (such as networking, data management, distributed computing, interfaces and software engineering) for networked computing  involving relative 'statics' and 'capable' computing devices remain relavent to 'mobile devices'?  If it is not (or not entirely) the case, then (1) what are the missing bits? (2) What should we do? and (3) What are you expected to take home after attending this course?

This course aims to answer the first question and address  the second and the third questions by focusing on mulrimedia and mobile networking issues, during the class room teaching. In addition, students are  to learn and practice the necessary skills for solving real problems in mobile computing through a term project.  You will be adviced in each term project (to be carried by a small group) related to mobile computing through which you learn how to indentify problem, define the objectives and scope of the project, synthesize your solution and then develop a prototype to proof the design concept.

This course is therefore suitable for students who wish not only to learn the basic foundation of multimedia and 
mobile computing but also to acquire some designing and programming skills for development of mobile applications.


The following topics are covered in the course:

(1) An overview of the development of networks, information systems and networked computing, computing devices, and  the driving forces toward mobile multimedia computing,
(2) Characteristics and system requirements of mobile and multimedia computing systems,
(3) Understanding the enabling technologies for mobile and multimedia networking:
     a). basic wireless communication concepts - multiplexing techniques, modulation methods and multiple access control,
     b). mobile network technologies: cellular networks, Wireless LANs, Bluetooth, WiMax, and mobile IP,
     c). network protocol design issues for mobile multimedia applications: connectivity and mobility management and support, multimedia mobile middleware and network quality of service
          (e.g. scheduling and policing, resource reservation and differentiation of service),
(4) Term projects involving the development of mobile applications using Android smart phones or tablets and application servers.

The detailed syllabus will be given during the first lecture.


It is carried out in the form of term projects. See "Teaching modes" for more details of term projects.



(I) Continuing Assessment:  ~50% 
    (a) Tutrials and assignments ( around 10%)

    (b) Term projects.(40%)

          i). Oral presentation of the Project proposal (4%)
          ii)  Pral progress report (2%)
          iii) Final technical report of the project with an oral presenttaion (34%)
(II) Final Examination (Closed book): 50%

(III) Makeup policy

       There will be no makeup if you miss the final exam/tutorial/term project

(IV) Submisson policy

      All written submissions, if any, must be submitted using IVLE via the Student Submission under the workbin. The due date of each submission will be published in IVLE.  

(V) Late policy

      Tutorial submissions: Students answer to tutorial qestions must be submitted to IVLE by the deadline. Late submissions will be penalized if without a valid reason in writing,.
      Project : No late submission of  report and deliverables will be accepted without a valid written reason.
                    All late project submissions/deliveries/oral presentations will be penalized (deduction of marks) according to their severity.


(VI) Honor code

All students of NUS are responsible for knowing and adhering to the academic integrity policy of this institution. Violations of this policy may include: cheating, plagiarism, aid of academic dishonesty, fabrication, lying, bribery, and threatening behavior. All incidents of academic misconduct shall be reported to the university authority. Students who are found to be in violation of the academic integrity policy will be subject to appropriate sanctions, including university probation, suspension, or expulsion.



Work load:  2-1-2-3-2

+ Workload Components : A-B-C-D-E 
A: no. of lecture hours per week 
B: no. of tutorial hours per week  (5-6 weeks of tutorial)
C: no. of lab hours per week (mainly for term project)
D: no. of hours for projects, assignments, fieldwork etc per week (C+D are mainly for term project)
E: no. of hours for preparatory work by a student per week ( Revision of courseware + preparation of tutorials)


Total 1 items
Title and AuthorEdition / Year /
Computer Networking: A Top-down apprach featuring the internet
Author:James F Kurose and Keith W Ross
3rd or 4th / 2005
Addison Wesley / PearsonSupplementary

Learning Outcomes | Prerequisites | Teaching Modes | Schedule | Synopsis | Syllabus | Practical Work | Assessment | Preclusions | Workload | References