SE Freshman Seminar

SE 101 Freshman Seminar

Course Syllabus - Fall 2012

Course Instructors and Assistants:

Course

Section

Instructor –

Course Assistants

Day

Time

Building

Room

Section 01

Kenn Martinez –

Derek Erdman

Justin Peterson

8:00AM - 9:50AM

GOL

1550

Section 02

Kenn Martinez –

Andy Lyne

Brad Bensch

10:00AM - 11:50AM

GOL

1550

Section 03

Daniel Krutz –

Brian Besmanoff

Rebecca Dudley

10:00AM - 11:50AM

GOL

1520

Section 04

Daniel Krutz –

Dan Larsen

Brad Bensch

2:00PM - 3:50PM

GOL

1550

Course Assistant Office Hours (Find them in the Mentoring Lab -- SSE room). .

Course Assistants are here to help you and to answer any questions you might have.

You can contact them via email or look for help at the SSE room.

Please note, any assistant can help you, regardless of your section.

Assistant	Email
Derek Erdman	dwe2864@mail.rit.edu
Justin Peterson	jmp3833@rit.edu
Andy Lyne	ajl2612@mail.rit.edu
Brad Bensch	brb7020@rit.edu
Brian Besmanoff	bmb6316@rit.edu
Becca Dudley	rcd1575@mail.rit.edu
Dan Larsen	dgl2311@mail.rit.edu

Course Description: This seminar will provide Software Engineering students with an overview of the discipline of Software Engineering and opportunities that exist for students. Topics include an overview of departmental resources, fundamental concepts and events, teaming, testing, co-op and full-time employment opportunities. Students will participate in a variety of activities that present an introductory view of the different facets of Software Engineering.

Course Objectives: Upon completion of this seminar, you can:

Describe different employment opportunities for Software Engineering graduates.
Identify fundamental Software Engineering concepts and resources.
Apply a project test plan and assess the effectiveness of the test plan to the development team.
Identify strategies to address issues that can arise in a team project.
Develop a simple project using appropriate tools in a team environment.
Identify departmental resources available to support students traverse the program.
Describe differences in the characteristics between Software Engineering courses and other computing courses.

Tentative Schedule: *

Week #	Topic
Week 1	Introduction to the Seminar, Departmental Resources for Students
Week 2	Software Engineering in Our World
Week 3	Software Engineering and the Software Lifecycle
Week 4	Development Processes and the XP Game
Week 5	Teaming & Introduction of Interview Assignment
Week 6	Professional Responsibility
Week 7	Robocode Part I
Week 8	Robocode Part II
Week 9	Testing Software (for SE 361 projects)
Week 10	Co-op and Career Day
Finals	Interview Discussion/Presentation

* The instructor reserves the right to adjust the schedule as needed. Mycourses will have updated information.

Method of Instruction:This seminar is an activity-based course rather than a lecture-based course. You will participate in hands-on activities that address targeted areas of Software Engineering during the quarter. You will utilize different resources and work in small teams during the course of the seminar. Each activity will result in a deliverable that represents your effort.

Grade Breakdown

Grade Item	Percentage
Week 1-11 Attendance	40%
Preparation, and Participation (including any assignment/activity submission)	40%
Interview Paper	20%

Method of Evaluation: Your grade in Freshman Seminar depends on your active participation in each of the class sessions and in the successful completion of assignments. Such participation may include reading or some other form of preparation be done before class. Class attendance alone does not give you credit for that day's activities - if pre-class/after-class work is required, then that is a part of your credit for that week's activity.

There is 40% assigned to class attendance. Attendance in the first week of class is not counted. Attendance in weeks 2 through 10 counts for 5% each week. Attendance at the Finals Week meeting is required to pass the course. There are also 9 homework and activity submissions that you do. Each one counts for 5% and is paired with the attendance for a particular class session according to the following table:

Homework/Activity	Paired week
Software Engineering's Impact on the World	Week 2
What is Software Engineering brochure or presentation	Week 3
Development Process scenarios	Week 4
Code of Ethics	Week 5
Professional responsibility activity	Week 6
Robocode - first version	Week 7
Robocode - final version	Week 8
SE361 Test Report	Week 9
Interview questions	Week 10

For weeks 2 through 10, the attendance grade and homework/activity grade are summed together giving 9 grade pairs each worth a maximum of 10%. Missing a class session gives you a zero for that week's attendance/homework pair. For final grading, the lowest attendance and homework/activity pair is dropped. This allows you to do poorly one week, or miss a week of class without an excused absence given prior to the class session. These points (maximum 80%) are then added to your Interview paper grade to get your final numeric grade.

If you are just interested in starting your "career" with a passing grade of "D" then come to class, don't participate and submit a formidable Final Interview Paper. On the other hand if you follow the above you should be able to score a good grade.