Differences

This shows you the differences between two versions of the page.

--- committees:curriculum:mobile [2015/01/22 14:55] – judi
+++ committees:curriculum:mobile [2015/01/28 14:43] (current) – gklotz
@@ Line 1: / Line 1: @@
+  * [[committees:curriculum:mobile:courses|List of Proposed Courses]]
+  * [[committees:curriculum:mobile:competition|Other Similar Programs]]
+  * [[committees:curriculum:mobile:learningoutcomes|Learning Outcomes specific to Mobile Major]]
+  * The draft Calendar description for Mobile: Regular {{:committees:curriculum:1516bcompmobmajpc.doc|}}
+  * The draft Calendar description for Mobile: Co-op {{:committees:curriculum:1516bcompmobcooppc.doc|}}
+  * The draft schedule of studies, highlighting errors and omissions: {{:committees:curriculum:mobilecomputingschedule.docx|}}
-==== Proposed Courses for the Major in Mobile Computing ====
+==Remaining steps for mobile major==
-===  CIS*1aaa Introduction to Mobile Computing (F) [0.5] (3-1) ===
+  * Receive School support for the plan to introduce new majors.
+  * Review current proposal
-An introduction to the field of mobile computing. The course examines the current state of mobile computing. Students will be exposed to the breadth of the technology and terminology of the field.\\ **Academic Goals:**
+  * Complete the proposal documents.
+  * Receive the School's approval of the proposal.
-  * literacy, definitions such as client server
+  * Get the B.Comp. Committee to approve the proposal.
-  * survey of current state of the field
+  * Get a library assessment for the proposal. The one we have from previous attempts to develop the major does not reflect the  current proposal.
-  * communications infrastructure
+  * Receive approval from the Co-op office for the new program. This raises a lot of questions about which of the existing majors will need to change their Co-op schedule, how are we going to offer Summer courses?
-  * interconnection of components, DB, interface, perhaps combine for an
+  * We will need an external review for the new program. This involves a reviewer to be appointed by the AVPA. I don't know when their review will need to be completed but it is likely that it will be needed for the Feb. 12 BUGS meeting and it is certainly going to be needed for the April 6 Senate meeting. Getting the proposal into the hands of the reviewer and back for the BUGS meeting is going to be challenging.
-  * social networking, aspects and trends
+  * Someone with some social skills should contact the library, the Co-op office, and the Chair of BUGS and apologize for the lateness of the proposal and request their assistance in completing the necessary work in such a short time.
-  * an introduction to privacy, security, and ethics for mobile devices
+  *
-  * a survey of usability issues related to mobile devices application
-**Applied Goals:**
-  * reinforce introductory programming
-  * learn about high level tools
-  * Develop small programs using high level tools for organizing and accessing content. Use a basic set of tools such as HTML, javascript, or Swift. Potentially develop a mobile application which is a wrapper around a web page.
-  * Provide a brief introduction to using SQLight. Include an explanation and examples of it’s use. Do not teach all of SQL. Provide specific examples for specific tasks. Approximately one lecture of material.
-Open to majors in the Mobile Computing only.\\ [[Recommended Books for Mobile Courses]]:
-===  CIS*2aaa Mobile Applications Design (W) [0.5] (3-1) ===
-This course explores the design and development issues associated with mobile applications. Students will learn about and experience the technologies used to develop mobile applications.\\ **Academic Goals:**
-  * design issues with handheld applications, restrictions and allowances provided by such systems
-  * patterns for mobile applications, restrictions, design standards
-  * interface items; touch screens, limited space, input limitations
-  * user experience with cloud technology and other back end systems
-  * design issues with server technology, from the consumer’s perspective, not the developer of such systems
-**Applied Goals:**
-  * developing for mobile platform, objective C, Java, or C++
-  * the instructor will be responsible for setting assignments and providing design which highlight the unique aspects of mobile applications
-Prerequisite: CIS*2500, CIS*2520, CIS*2430\\ Open to all students.\\ [[Recommended Books for Mobile Courses]]
-===  CIS*3aaa Pervasive Systems [0.5] (W) (3-1) ===
-This course is a study of the systems level details found in mobile technology. It includes a comparison of system details and a survey of method for network interaction and other system level details.\\ **Academic Goals:**
-  * comparison of design choices for system architectures, what is proprietary and consistent and what is not (ecosystem design choices for different systems)
-  * networking issues from client side, methods of network interaction
-  * system level API’s for accessing, control, and communication
-  * privacy and security
-  * embedded system components, power usage planning, the influence of economics (everything is as cheap and simple as possible, the limitations of such systems and the design tradeoffs that are made)
-  * fault tolerance on the client side
-  * internet of things (IOT), internet devices
-**Applied Goals:**
-  * interaction through networks (i.e. bluetooth, WIFI) to receive information from sensors or external devices, control of devices such as actuators with the goal of integrating them in a pervasive system
-Prerequisite: CIS*2aaa, CIS*2030, CIS*2520, CIS*3110 (CIS*3210 Networking is difficult due to Co-op scheduling).\\ Open to all students.\\ [[Recommended Books for Mobile Courses]]\\
-===  CIS*3aab Server Side Technology [0.5] (F) (3-1) ===
-This course will study the server side technology used in mobile applications. It will examine issues involving the types of servers and services available, reliability and redundancy of network services, and issues which are specific to servers for mobile applications.\\ **Academic Goals:**
-  * study of server side technology, servers, DB, cloud, web services, API’s
-  * examine methods for managing unreliable network connections
-  * security and privacy
-  * server side economics
-  * scaling issues for servers, parallel processing issues
-  * errors resultant from processing large amounts of data
-  * design choices and their implications on handheld devices
-**Applied Goals:**
-  * build back end internet infrastructure for an application, experience with different API’s
-  * data management for mobile applications: online versus offline storage (where does the data reside?)
-  * comparison of cloud infrastructure, examine the different implementation choices
-Prerequisite: CIS*2aaa, CIS*3530\\ Open to all students.\\ [[Recommended Books for Mobile Courses]]:
-===  CIS*4aaa Mobile Systems Project Course [1.0] (F) (1,6) ===
-This course focuses on the development of a large, interactive mobile system. This will involve the development of both the client and server for the system. Students are expected to research the implementation details in order to design the server.\\ **Academic Goals:**
-  * An opportunity to develop the requirements and design of a mobile application and server.
-**Applied Goals:**
-  * Implementing the application and server.
-  * Look for opportunities for joint projects which combine hardware and software system. Consider ESC and ECE. Look at C-Base and OVC for application ideas.
-Prerequisite: CIS*2aaa, CIS*3aaa, CIS*3aab\\ Open to majors in the Mobile Computing only.\\ [[Recommended Books for Mobile Courses]]:
-===  Other required courses for the Mobile Major ===
-  * CIS*2170 User Interface Design
-  * CIS*3210 Computer Networks
-  * CIS*3530 Data Base Systems and Concepts