Course Syllabus

CIS 5750Wireless Information Systems

Summer 2016

Dr. FrancisCirillo, Adjunct Professor, Computer Information Systems

Text:

Stallings, William, “Wireless Communications & Networks, 2/E”, 2nd Edition, Prentice Hall, ISBN 9780131918351, ©2005 (NOTE WE ARE USING THE SECOND EDITION).

Prerequisites:

None.

Course Description:

Studies the fundamentals of wireless information and communications. Includes principles of cellular radio, wireless modulation and multiple access techniques, and wireless protocols and standards. Provides an overview of wireless evolution (1G to 4G), and Wireless Local Area Network (WLAN) and Wireless Personal Area Network (WPAN) networks. This class is worth 3 credits.

Learning Goals of Course (by topic):

  • Understand the technical principles for radio waves, frequency spectrum and characteristics of signals
  • Understand analog and digital modulation techniques
  • Understand multiplexing and multiple access schemes
  • Understand the technical principles for the wireless network components
  • Understand the first wireless generation systems (e.g. Advanced Mobile Phone Systems (AMPS) and Total Access Communication System (TACS)) technologies

Assessment:

  • Homework Assignments20%
  • Class Project / Paper15%
  • Test Number 120%
  • Test Number 220%
  • Final Exam20%
  • Class Participation 5%

Proposed Course Schedule:

Week One (May 19)

  • Reading assignment:Chapter 1

Chapter 2

  • Instructor lecture:Discuss Course Syllabus
    Discuss Research Paper
    Ch. 1 – Introduction.

Ch. 2 – Transmission Fundamentals

Week Two (May 26)

  • Reading assignment:Chapter 3

Chapter 4

  • Instructor lecture:Ch. 3 – Communication Networks

Ch. 4 – Protocols and the TCP/IP Suite

Week Three (June 2)

  • Reading assignment:Chapter 5
  • Instructor lecture:Ch. 5 – Antennas and Propagation

Week Four (June 9)

  • Exam Number 1:Exam 1– Computer Based –In Class

Week Five (June 16)

  • Reading assignment:Chapter 9

Chapter 10

  • Instructor lecture:Ch. 9– Satellite Communications.

Ch. 10 – Cellular Wireless Networks

Week Six (June 23)

  • Reading assignment:Chapter 11

Chapter 12

  • Instructor lecture:Ch. 11 – Cordless Systems and Wireless Local Loop

Ch. 12 – Mobile IP and Wireless Access Protocol

Week Seven (June 30)

  • Reading assignment:Chapter 13
  • Instructor lecture:Ch. 13 – Wireless LAN Technology

Week Eight (July 7)

  • Exam Number 2:Exam 2 – Computer Based – In Class

Week Nine (July 14)

  • Reading assignment:Chapter 14

Chapter 15

  • Instructor lecture:Ch. 14 – Wi-Fi and the IEEE 802.11 Wireless LAN Standard

Ch. 15 – Bluetooth and IEEE 802.15

Week Ten (July 21)

  • Reading assignment:Chapter 6
  • Instructor lecture:Ch. 6 – Signal Encoding
  • Class Project:Class Project us due by 6:30 PM

Week Eleven (July 28)

  • Final ExamFinal Exam – Computer Based – In Class (Time is 8:30 to 10:30 PM)

Day, Time, and Location:

This class meets on Thursday evenings, from 6:30 PM to 10:30 PM, in Crawford, Room 220.

Relation to Program Level Outcomes:

This course will be used for partial assessment of all three Program Learning Outcomes for the Computer Information Systems Master of Science program. These include:

  • Ability to apply knowledge of computing, computer programming, system analysis, hardware, data structures, and information transmission, storage and retrieval. (DSK: Discipline Specific Knowledge)
  • Ability to organize and present technical information, whether it be programs, methods, ideas related to computing or information systems, in both written and oral form. (COM: Communication)
  • Ability to perform independent research and apply information systems knowledge related to the computing field. This may include design, implementation, administration of information systems or the maintenance and problem solving aspects of systems. (CT: Critical Thinking)

Important Dates:

  • 05/16First Day of class for the Summer Semester
  • 05/19First Day of class for CIS 5750
  • 05/17Last day to register, add a class, or drop a class without a grade of W
  • 05/30Holiday – Memorial Day
  • 06/17Last day to drop a class with a grade of W
  • 07/04Holiday – Independence Day
  • 07/18Last day to complete graduate-level defense and examination
  • 07/28Final Exam for CIS 5750 – 8:30 PM to 10:30 PM
  • 07/29Last day of classes for the Summer Semester

Course Grading Criteria:

GradeRange

A90.0 to 100.0

B80.0 to 89.9

C70.0 to 79.9

D60.0 to 69.9

F 0.0 to 59.9

Cheating and Plagiarism Policy for all CIS Classes and Students:

Overview

We believe that everyone has a right to work in an environment where people treat one another honestly andfairly. Because academic dishonesty can threaten this environment we will pursue abuses of the policiesoutlined below aggressively.

When you submit any piece of work for grading or other evaluation, the reader will assume that you are the soleauthor of all aspects of it. The expectation is that you are the originator of every idea and author of everysentence in an essay, help file, or other document, that you wrote every line of code, that you designed everydata structure and created every piece of data. In practice, you will often have good reason to use other people'swork or to collaborate with others in creating a work that you will submit. In these cases, it is yourresponsibility to make the reader clearly aware of what has come from other sources. If a reasonable readerwould assume, on reading your work, that some part was created by you alone when in fact it was created bysomeone else or by you in partnership with someone else, that reader has been misled. It is your responsibilityto prevent such misimpressions, and the department will hold students accountable both for intentionallymisleading readers and for failing to prevent reasonable misimpressions.

Code Plagiarism

Computer science is a discipline where it is difficult to draw a precise line between acceptable and unacceptablecollaboration. On the one hand we want to encourage you to try out other peoples' code; code reuse is an area ofactive research within computer science. On the other hand you will learn to write code only if you do ityourself. You are not learning and have crossed the line of acceptable behavior if you do not understand thesolution you have submitted. We have the right to ask students to explain the code they submit. If you have"reused'' someone else's code to an extent that you feel a need to change variable names or slightly rearrange theorder of statements, then you have also violated the honor code. We also reserve the right to use electronic toolsto check code for plagiarism. By submitting code for grading in any computer science course, you grant theinstructor a license to send a copy of that code for plagiarism analysis to a research service, such as MOSS. Theinstructor, or their service, may compare your code against other students' code, or compare their code to yours.Give credit to someone else's ideas with a citation rather than turning in their work as your own.

Text Plagiarism

When you hand in an essay or other writing assignment, you must give credit to your sources. You mustprovide a reference for any idea, conclusion, information or data that you got from another source (such as abook, an article on the Net, or a person). If you use someone's words, you must show that you are quoting them(use quotation marks or indent long quotes) and your reference should show your exact source (such as the pagenumber of the article or book). If you quote someone, you must quote them accurately, word for word. To avoidplagiarizing, you might find the following articles useful:

•Academic Dishonesty, Cheating, and Plagiarism

•How Not to Plagiarize

•Citing Sources and Avoiding Plagiarism

By submitting a writing assignment for grading in any computer science course, you grant the instructor alicense to send a copy of that assignment for plagiarism analysis to a research service, such as TurnItIn. Theinstructor, or their service, may compare your paper against other students' papers, or compare their papers toyours.

Social Responsibility

Many people use our machines: students, faculty, staff, and outside visitors. Our machines affect othermachines on and off campus and they affect the users of these machines. It is not hard to abuse others bymailing spam, flaming to newsgroups, being a cracker, displaying digital pornography, bogging down the CPUwith processes, or hogging the printer. We expect your use of computer resources will be based on the GoldenRule: do unto others as you would have them do unto you. Poor social responsibility because you are new is onething, but malicious practices are another matter and will not be tolerated.

Right to Privacy

You are encouraged to store electronic property on computers provided for your use by Computer Sciences, andyou have a privacy right to this information. Others also have a right of privacy to the property they store on ourcomputers. You should not search other's file systems, read their mail, scan or remove their files, try to cracktheir password, login as someone else, intercept other's network traffic, install viruses, or otherwise violate theright to privacy of others. We will not intentionally abuse your right to privacy. However, to administer ourmachines we may need to do things you should not, for example, we may need to try to crack your password toverify that it is secure, or kill your processes, or remove your files, or read your email, or otherwise invade yourprivacy when we suspect you are an abuser of our systems.

Discrimination

It is the policy of the university that all students, faculty, staff, and guests enjoy an environment free from allforms of discrimination, including ethnic, racial, religious, and sexual harassment.

Disclaimers

The Florida Tech Acceptable Use Policy for Campus Information Technology Services. The Florida TechCatalog and the Student Handbook have additional guidelines on campus standards, behavior, discipline,complaint resolution, etc. The Computer Science Honor Code does not replace or supersede these polices.Faculty teaching computer science courses may establish other honor criteria for their classes.As our machines are part of a larger international network, we assume certain responsibilities as a member of agrowing electronic community. Exercising this responsibility may require us to search for suspected abusers ofour or others computers. If you suspect that someone has violated your rights as a user of our machines, informthe systems administrator; do not attempt to track them down yourself.

Penalties

The following penalties are recommended for violation of this honor code.

Offense Penalty Reported To

First Zero on work Dean of Students

Second F in course University Disciplinary Committee

Third Expulsion from program University Disciplinary Committee