Software Engineering I - Fall 2009

Course Number: CS 07.321 1

Course Information

• Course Objective : An introduction to the discipline of Software Engineering. Students will explore the major phases of the Software Lifecycle, including analysis, specification, design, implementation, and testing. Techniques for creating documentation and using software development tools will be presented. Students will develop a software system, working in a team. The project will be taken through each of the major software development phases, and student teams will create appropriate deliverables for each phase. Students will gain experience in software project management; requirements, analysis, and design; procedural maturity; social, ethical, cultural, and safety issues in deployment; interpersonal skills for management and team membership; and the software engineering tact of systems architecture.
• Course Outcomes : Students who complete this course will feel comfortable in the role of a Software Requirements Engineer, Software Designer, Software Architect, Quality Assurance Engineer, Project Manager, Customer, User, Technical Team Leader, Member of the Technicall Staff, Advocate, and Critic for the use of software to solve business and technical problems. Students become conversant in methodologies, architectural approaches, project management techniques, and team dynamics.
• Topics to be covered : an overview of software engineering: introduction, software processes, software prototyping; requirements: software requirements, requirements engineering processes, system models; architectural design; module design: design and reuse, user interface design; implementation; testing: verification and validation, software testing.
• Prerequisites :
  • CS 04.222 (Data Structures and Algorithms) or CS 04.225 (Data Structures for Engineers), CMS 01.112 (College Composition II) or ENGR 01.201 (Engineering Sophomore Clinic I), CMS 06.202 (Public Speaking) or ENGR 01.202 (Engineering Sophomore Clinic II).
  • Familiarity with GUI programming.
• Course Format : Lecture + Discussion + Lab.
• Lecture : Monday 6:30PM-9:00PM. 
• Lecture Room : Savitz 321.  
• Lab : Monday 5:00PM-5:50PM. 
• Lab Room : Science 338.  
• Course Web Page  :  http://elvis.rowan.edu/~rusu/SoftwareEngineering.html
• Class Discussion Page :  http://webct.rowan.edu/ -  Software Engineering I  
• Instructor : Adrian Rusu
  Office: Robinson 3rd floor
  Email: rusu@rowan.edu
  Office Hours: Monday 3:00PM - 4:00PM, Tuesday 3:00PM - 5:00PM. Or, by appointment.
• Required Textbook :
  • Ian Sommerville. " Software Engineering" (8th edition): Addison-Wesley.
• Recommended Textbooks : Visual Basic, Visual C++, and Java Programmer's Manuals, or on-line tutorials.
• Grading Policy :
  • 2 Exams (individual grade) (10% Exam1, 10% Exam2)  
  • 3 Announced Quizzes (individual grade) (6%)
  • ~3 Unannounced Quizzes (individual grade) (6%)
  • Course Involvement and Attendance (individual grade) (qualifies you for Extra Credit - up to 3%) 
  • Class Participation (virtually unlimited Extra Credit)
  • 2 Mandatory Office Visits (individual grade) (2%)
  • Group Project (team grade) (58%)
    • Status reports (email weekly) (5%)
    • Requirements analysis and specification; prototype (13%)
    • Design (architectural + module) (13%)
    • Implementation; customer-oriented documentation and presentation; user manual production (18%)
    • Testing (9%)
  • Peer Evaluation (individual grade) (8%)
  • Final grades will be based on exams, class participation, mandatory office visits, quizzes, the deliverables associated with the class project, and the evaluation of your peers :  92-100% = A, 88-91.9% = A-, 84-87.9% = B+, 80-83.9% = B, 76-79.9% = B-, 72-75.9% = C+, 68-71.9% = C, 64-67.9% = C-, 60-63.9% = D+, 56-59.9% = D, 52-55.9% = D-, 0-51.9% = F.
• Exam Policy : Both exams closed everything. None of the exams is comprehensive.  
• Quizzes Policy : In-class closed everything announced and unannounced quizzes. For the announced quizzes, reading assignments will be provided a week before each quiz. Each announced quiz will take 20 minutes and consists of a summary of the reading assignment. Each unannounced quiz will take 10-15 minutes and consists of questions from the material just presented in class. 
• Class Attendance and Involvement Extra Credit Policy : At the end of the semester, you might have the opportunity to increase your grade by one level. Extra credit (usually a problem) will be provided, and a solution is expected. My personal, subjective evaluation will determine the amount and the difficulty of extra credit you qualify for at the end of the semester. Each missed class automatically decreases the amount of extra credit you might qualify for by 1%.
• Class Participation Extra Credit Policy : Each good in-class answer or interesting question will be awarded with 5 points. A total of 100 points is equivalent to 1% extra credit for your final grade. In order to encourage teamwork, each teammate of the student who provided the good answer, will also be awarded 1 point.
• Project Policy :
  • Each class will be divided into teams.
  • Initially, you will be given an initial set of customer requirements, which may need some enhancement.
  • Status reports (meeting logs): Teams are expected to set a day, time, and place where they meet regularly each week. Every week after teams have been formed, a status report must be emailed to the instructor detailing a log of meetings, team members in attendance, current project status, overall and individual accomplishments during the prior week, and what is scheduled for the coming week, including roles and assignments among the teammates. These logs should reflect meetings held during the scheduled time as well as other times the group meets.  
  • All deliverable documents must be submitted in typed, professional form and an on-line version should be available as well. Late deliverables will not be accepted. Start your projects early.
  • The project implementation and test phase will be evaluated on-line by a team demonstration given to the customer. Be prepared to answer questions, demonstrate, and defend the work of your team.
  • There will be no programming instruction in this course. Now that you have reached this point in the curriculum, you should be able to use the programming skills you already acquired, or, if new programming skills are needed, you should be able to learn them on your own.
  • In general, for the project, all team members will be assigned identical grades for the team's deliverables. However, such grades are subject to adjustment by the instructor, based on his own evaluation of individual contributions. Students who expect their teammates to "carry" them through the project will have their grades adjusted accordingly. Students can even be fired by their teammates. Each student is required to submit self and peer evaluations after each major project phase, as well as an overall peer evaluation at the end of the course.
  • Team meetings attendance is mandatory. Students who miss 4 or more scheduled team meetings will automatically receive an F in the course.
• Mandatory Office Visits : The first mandatory office visit must occur during the first week of the semester. The second office visit must occur mid-semester. Schedule an appointment if formal office hours are not convenient. You must also fill out and submit by email the questionnaires (found at the class Web page) before coming for your mandatory visits. Note: submit your filled questionnaires by email and only come to the office if asked by the instructor.
• Academic Integrity: Unless stated otherwise by your instructor, individual work is expected.  Anything you turn in with your name on it must be your own work, that is, written or coded by you and not copied from anyone or anywhere else. You must do anything you turn in with your name on it individually. You may consult with other students and the course instructor to clarify points of confusion and share ideas. Copying from others is expressly forbidden. Allowing others to copy from you is expressly forbidden. For programming assignments, allowing others to look at your code is expressly forbidden. If you use materials that you've obtained on the Internet, from a book, etc., you must include an appropriate reference. To use such materials without proper attribution is a form of plagiarism. The violation of these rules will result in an F for the course, effective immediately, and a letter to the Office of the Dean. Team projects must be original.   By registering in this course, each one of you is explicitly agreeing to abide by and adhere to the above statements on academic integrity.

  Rowan University academic integrity policy

• Attendance Policy: Class attendance will be taken by your instructor at the beginning of each lecture. As a student at Rowan University, you are expected to attend all the classes. Please inform the instructor in advance, preferably by e-mail, if you must be absent from a class. Excessive absences (as judged by the instructor) may lower your grade. If you miss a class, make sure that you obtain the notes from someone in the class, as you are always responsible for finding out what has happened in the class. A zero grade will be issued if you miss an exam or a quiz, unless you inform your instructor beforehand and you can present a documented excuse. Students who miss more than 4 meetings will be reported to the Dean of Students and will receive an F in the course.

  Rowan University attendance policy

• Withdrawal: There are three deadlines for withdrawal during the semester. Each deadline further into the semester demands one more signature and is more difficult to get. If you are thinking of withdrawing, timely action is necessary. The university's policy on course withdrawals during the last four weeks of the semester is that a student may withdraw only if there are circumstances beyond his/her control which prevent him/her from completing the course requirements.
• Policy Concerning Students with Disabilities: In compliance with Rowan University policy and applicable laws, appropriate academic accommodations are available to you if you are a student with a disability. All requests for accommodations must be supported by appropriate documentation / diagnosis and determined reasonable by Rowan University. Students with documented disabilities (physical, learning, psychological) who may need academic accommodations are advised to make an appointment with the Office of Specialized Services/Disability resources in Savitz 339 (x4233). Students with disabilities are encouraged to speak with their instructor as early in the semester as possible about their needs for special accommodations. Late notification will delay requested accommodations.
• Important Dates :
  • Labor Day (no classes): Monday 09/07
  • Final Exam (if applicable): N/A.

lecture0   lecture1   lecture2   lecture3   CMM   lecture4   lecture5   Exam 1 Review   lecture6   lecture7   lecture8   lecture9   lecture10   Design Review   lecture11   Exam 2 Review  
   

Sample Projects   Team Homework   Sample Team Log   In-Class Phase 1   Real-World Phase 1   Sample Phase 1   Phase 2   Sample Phase 2   Phase 3   Sample Phase 3   Sample Brochure   Sample Agenda   Sample User Manual  
   

questionnaire   Dismissing a Team Member   Peer Evaluation   Self Evaluation   Midterm Evaluation