COMPUTER ENGINEERING DEPARTMENT Course CMPE 133 SE 133 Software Engineering II Semester Spring 2007 Instructor Dr M E Fayad Computer Engineering College of Engineering San Jose State University Web page http www engr sjsu edu fayad Course Title Software Systems Engineering Course Code CmpE 133 SE 133 Sections 1 Class Hours Location Friday 6 00 p m to 8 50 p m 18 00 to 19 50 ENGR 337 Labs will be taken place in the ENGR 337 Refer to Lab Schedule Office Hours Thursday 3 50 p m 5 50 p m Friday 3 50 p m 5 50 p m Other times Send an e mail to schedule an appointment Office Location ENG 283I Office Phone 408 924 7364 E mail m fayad sjsu edu Preferred Contact Through e mail Department Fax 408 924 4153 http www engr sjsu edu fayad current courses cmpe133spring2007 Course Web Page 1 of 7 COMPUTER ENGINEERING DEPARTMENT 2 Course Description a Course Overview and Description Course Catalog Description Software Architecture Software Technical Metrics evaluating products processes and resources improving predictions products processes and resources Advanced topics such as Formal Methods Software Reuse Reengineering Client Server Software Engineering Computer Aided Software Engineering Team Based Projects Prerequisite CmpE 135 Co requisite CmpE 133L Misc Lab Lecture 2 hours lab 3 hours b Prerequisites instructor consent c Required Textbooks Required SWEBOK is an official service mark of the IEEE http www swebok org A project of the IEEE Computer Society Professional Practices Committee SWEBOK Guide to the Software Engineering Body of Knowledge 2004 d Required Textbooks Optional Ian Sommerville Software Engineering 7th Edition Addison Wesley 6 edition May 10 2004 ISBN 0321210263 6th Edition will also do Or Ghinwa Jalloul UML by Example 2nd edition Cambridge University Press ISBN 0521008816 e Required Articles Columns Case Studies and Patterns will be posted on the web later Materials will be provided for each lecture check Weekly Schedule Other Resources Instructor notes will be available on the course web page f Course Learning Objectives 1 Have the ability to perform software development tasks from a systems point of view 2 Have the ability to generate artifacts for implementers to construct software systems 3 Course Requirements a Projects 2 of 7 COMPUTER ENGINEERING DEPARTMENT The class will be divided into groups of 3 4 four preferred for team projects Students will be responsible for forming groups Students of the best 3 or 4 teams projects will give final presentations of their project work if asked Grading criteria and project ideas will be posted in a project Web page Project 1 Process Documentation Project 2 This project will focus on Modeling UML diagrams Project 3 Optional This project is an advanced project and it is based on creating several Stable Software Patterns Project 4 Optional This project is an advanced project and it is based on creating a knowledge map or pattern Language for an assigned domain or implement a pattern and you must signed for it On occasion students take advantage of group work letting other members perform the bulk of the work while they reap the benefits of a good grade and can spend more time on other classes This happens only occasionally but it will not be tolerated in this course Two policies will help prevent this 1 Twice during the semester group members will be asked to fill out a detailed peer assessment for group members per project This assessment will be based on four scales Assessment Zero D C B A Meaning Doesn t do anything 25 effort Attends 25 of the meetings Doesn t participates in the discussion Does a poor job 50 effort Attends 50 of the meetings Participates rarely in the discussion Does a so so job 75 effort Attends 75 of the meetings Participates partially in the discussion Does an okay job 100 effort Attends all the meetings Participates effectively in the discussion Does an excellent job Correspondence Get a Zero on the project Get a 25 of the project s grade Get 50 of the project s grade Get 75 of the project s grade Get 100 of the project s grade Merely attending meetings won t be enough Group members must be prepared for meetings make good suggestions perform their share of the work and work well with other members The grading criteria for peer assessment is as follows a Has the group member attended meetings 3 of 7 COMPUTER ENGINEERING DEPARTMENT b Has the group member been prepared for group meetings I e was he she aware of assignment requirements performed her his duties able to speak intelligently about the project etc c Has the group member participated positively in meetings d Has the group member performed their share of the work as assigned e Rate the quality of this group member s input to group discussions and design issues f Has the group member been able to work well with others g Rate the overall value of this group member to the project h Rate the level of initiative this group member has exhibited in the project i Other comments 2 Groups experiencing problems with a student should let me know there s a problem Do this early in the semester My experience is that group members wait until it s too late to take action My objective is to ensure that each group member has the opportunity to succeed I will handle the situation and ensure there is no animosity while resolving the problem Usually a brief discussion will clear the matter up entirely and without further problems b Exams Two exams of equal weight see grading There will be no make up tests c Class Lab Attendance Participation Important Class lab attendance is mandatory If you have more than four unexcused absences then you will be dropped from the class d Essay Check essays requirements e Practical Problems Check practical problems requirements f Lab Work Check lab and design sessions assignments lab schedule 4 Tentative Course Calendar a Weekly Schedule See weekly schedule on the course webpage b Lab Schedule See lab schedule on the course webpage c Due Dates Important Late extra assignments practical problems essays and team projects are NOT ACCEPTABLE In this case the grade of any late extra assignments or any late projects will be assigned a zero mark See Due dates on the course webpage If you accept an assignment you must do it otherwise you will lose an equal weight of the grade of the assignment 5 Grades a Grading Policy Your grade in this course will be based on your performance on written homework test and team projects 4 of 7 COMPUTER ENGINEERING