|SWE432: Design and Implementation of Software for the Web|
This course teaches students how to develop high quality software for web applications. The concepts of client-server computing, theories of usable graphical user interfaces, and models for web-based information retrieval and processing are covered. In the past few years, the way software is built has been rapidly changing. As use of the world wide web has shifted from information presentation to information gathering to direct customer sales (e-commerce) to enterprise applications, the amount and complexity of software has steadily been increasing. This course will help students use new models of programming and new technologies to design and develop high quality, usable, web software.
|Prerequisite||MATH125 and CS211|
|Professor Contact Information||
Dr. Kinga Dobolyi
Office: Engineering (Rm. 4440)
Office Hours: Tuesdays and Thursdays 12:45 — 2:45, or by appointment. Please email the professor at least 48 hours in advance when seeking an appointment.
|Course Materials||All assignments must be submitted (per published deadlines) through students' public webpages. Piazza will be used for discussion boards and announcements this semester — all other materials (slides, etc) will be available only on the course homepage. Grades (except the final course grade) will be posted to Blackboard.|
Students must use the GMU email system for all correspondence with professor (using the following email subject format:
Please note that general project or class questions should NOT be sent to the professor or TAs - in such events, your email will be returned and you will be asked to post your question to the discussion board. In general, the turnaround time for responses to questions will be much quicker on the discussion board.
Students should also avoid emailing their code to the professor or TAs unless permission has been obtained (under no circumstances should code be posted publicly to the discussion board).
Final course grades are calculated as follows:
A+ (>= 98.0%) A (>= 92.0%) A– (>= 90.0%)
B+ (>= 88.0%) B (>= 82.0%) B– (>= 80.0%)
C+ (>= 78.0%) C (>= 72.0%) C– (>= 70.0%)
D (>= 60.0%)
F (< 60.0%)
Note: per departmental policy, a failing grade on the final exam (<60.0%) will result in a failing grade (F) for the entire course, regardless of performance on other assignments.
Contesting of grades on any/all submissions must be requested within one week of the item's return. No grade changes will be considered subsequent to that deadline, or after the final exam meeting.
SWE 432 will use the Piazza software for a discussion board. Information for accessing our class will be provided on the first day of class. Participation on the discussion threads will count for 5% of your grade, which you can earn in several ways;
|Homework Assignments||Some homework assignments will be written and some will require programming. Most will allow collaboration with one partner. Assignments will be posted on the class website before class and discussed in class. You will submit your solutions by placing them on your websites and submitting the source files through blackboard. You should submit links to executable versions of programs, but may not post source files on your websites. Posting program source on your website will be considered an honor code violation! Be sure that you check the discussion board daily, as refinements and hints for the assignments will be posted there. Homeworks must be submitted before class on the day they are due. Assignments will be checked immediately after the due date.|
All assignments must be submitted by the deadline to be considered for credit.
Blackboard or other resources being unavailable is not an excuse for turning in a late assignment; in the rare situation that a website is somehow unavailable or giving the student an error, the student MUST email their submission to their GTA before the deadline, otherwise it will be considered late.
Similarly, having a laptop die or losing source code is not an excuse for turning in a project late — students are responsible for maintaining their own backup copies of code.
Students are encouraged to use the discussion board, Piazza, to ask and answer questions.
Students can post questions and code privately, although the instructor reserves the right to make any post public, so that other students can see the responses. Therefore, students may post anonymously, if they choose to do so, although in general this is less preferred as it is often easier to help a student if we know their name.
Exams are closed book/notes unless specified otherwise by instructor. Appropriate documentation (as determined by instructor) and requisite permissions are required for make-up exam requests. Picture IDs are required to take all exams. Note: A failing grade on the final exam (<60%) will result in a failing grade (F) for the entire course, regardless of performance on other assignments.
If you know in advance that you are unable to make an exam for a valid and unavoidable reason (such as a scheduled surgery, etc), you must notify the professor at least one week before the scheduled exam date to make arrangements for a make-up, and bring documentation with you when you take the make-up. If you miss an exam due to a university-accepted excused absence (such as an illness or car accident the day and time of the exam), you must notify your professor within 24 hours of your absence to make arrangements for a makeup, and bring approved documentation with you when you take the make-up exam. Failure to follow either of these policies will result in a zero.
You must take the final exam for the section that you are registered for.
All students are expected to abide by the GMU Honor Code. This policy is rigorously enforced. All class-related assignments are considered individual efforts unless explicitly expressed otherwise (in writing). Review the university honor code and present any questions regarding the policies to instructor.
Cheating on any assignment will be prosecuted and result in a notification of the Honor Committee as outlined in the GMU Honor Code. Sharing, collaboration, or looking at any code related to programming assignments that is not your own is considered cheating.
The computer science department has an additional, more restrictive CS Honor Code that you are also subject to. Make sure you read and familiarize yourself with these rules.
It is your responsibility to lock your computers with a password, to not post your code to websites like Pastebin that are publicly accessible, to guard your USB drives, to not upload your files to someone else's computer, etc. You will be liable for any accidental access you give to your code. Stating that "I don't know how he/she got access to my code" is not an acceptable excuse in an honor code violation.
|Learning Disabilities||Students with a learning disability or other condition (documented with GMU Office of Disability Services) that may impact academic performance should speak with professor ASAP to discuss accommodations.|
|Tentative Class schedule|
|Week #||Date (start of week)||Assignments||Lecture Topics||Readings (to be completed prior to lecture)|
|See the course homepage, http://www.cs.gmu.edu/~kdobolyi/swe432/, at for a list of detailed topics and class schedule|