Welcome to CIS 487 Software Engineering

¯ Tentative Schedule ¯ Class Policies/Guidelines Course Syllabus Instructor/Course Information

Week	Lecture Topics and Special Days/Events	Suggested Readings	Assignments/Projects/Quizzes
01/09-01/13	Introduction and syllabus. Explain course website and course policies. The process of writing a simple application. Introduction to software engineering. Project. Process. People. Product. Modeling and models. Example team projects. A reasonably-sized Java-based system of your choice. Online homework submission system. Message board/chat room. GUI-based (non-trivial) computer game. Tiny language compiler for a simple language. ... 1/9/12 Mon In Person Add/Drop and Late Registration (Late Fee Applies), 9:00 am-4:00 pm, Ikenberry Hall - Consult Advisor. New Students must register in person. 1/13/12 Fri Last Day to Add/Drop via RAIL, through 4:00 pm, or in Ikenberry Hall 9:00 am-4:00 pm - Consult Advisor.	Chapter 1, 2	Project teams will be formed. All projects will be team projects. Presentations will be scheduled to demonstrate project progresses and results.
01/16-01/20	Functional and non-functional requirements. Importance of documentation in the software process. Generic software process models. The waterfall model. Iterative models. The RUP model. Agile models. Component-based models. Attributes of a good software. 1/16/12 Mon Martin Luther King's Birthday - Holiday - University Closed.	Chapter 3	Each team will present a short description of the term-long project. Please document all important team activities.
01/23-01/27	1/23/12 Mon Last Day to Change a Course from Credit to Pass/Fail Status. User/software requirements. Requirement engineering. Introduction to UML. Use cases and use case diagrams. Introduction to Office Visio.	Chapter 4 -5 UML online references (Official Site) Office Visio References (Official Site)	Write requirements document and draw use case diagrams for your project. You can consider this phase as the "Inception Phase" in RUP. Team presentation. Quiz 1 on Next Tuesday (1/31). Please review concepts covered through this week.
01/30-02/03	1/30/12 Mon Last Day to Change a Course from Credit to Audit Status. Summer research opportunity from Alabama. Use case conditions and scenarios. Use case diagram “includes” and “extends” dependencies. Critical systems. Project management and risk management. Please note team project documentation and presentation is the critical part of your project, which will be 50% of your grade. Also, “Graduation” is not a valid reason to pass this class or receive a certain grade. Please do not ask.	Chapter 4 - 5	Team work and presentation on detailed requirement documents, diagrams, prototypes, project plans, risk analysis etc. There should be little “ambiguity” in your requirements document at this time since our projects are small.
02/06-02/10	Prototyping and iterative development. System analysis using developer’s language. System modeling. Distributed systems. System design. Class diagrams. 2/10/12 Fri Last Day to Withdraw from First Half-Semester Class - See Advisor by Noon.	Chapter 2, 5, 6	Every team – Please turn in requirement documents by 2/7. Team work and presentation cont. Analysis activities. Start static structure design.
02/13-02/17	System design revisit – goals, aspects, and management. Object-oriented design review. Design patterns. Definitions, categories, and applications. Examples of design patterns. In-class team presentation on design patterns.	Chapter 6 - 8	Every team – Please turn in preliminary analysis and design documents by 2/21. You may include description of system models, system and data structures, class diagrams, and any document relevant to your project.
02/20-02/24	2/20/12 Mon First Day of Midterm Exams. 2/24/12 Fri Last Day of Midterm Exams. Last Day to Apply for August or December 2012 Graduation, Registrar's Office. Note about your midterm grade on RAIL – This grade (A, B, C, D, F, or IF) is based on assignments/projects (50%), quiz (15%), and midterm exam (35%). Although this grade will not show on your transcript, it is an important indicator of your progress for the first half of this class. If you have missed significant amount of work, you may get an F or IF. Please do spend time to improve.	Chapter 6 - 8	Team work and presentation on initial design of system. In-class midterm exam. 2/21. Tuesday. One page of notes allowed.
02/27-03/02	· Dynamic behavior modeling. Sequence diagrams. · Real-time systems. · User interface and interaction design and testing. · Rational Unified Process revisit. Please note that you build models because they give you a much better understanding of your system before you implement it, especially when the system is big. Keep the house-building analogy in mind.	Chapter 2, 8, 9	Team work on system design. Every team should have a relatively mature design of your system so coding and testing become straightforward. Please work on sequence diagrams as well as user interface/interaction design to improve the look and feel of your system.
03/05-03/09	· Map design models to code. · Forward and reverse engineering. Reengineering. · Implementation issues. · Testing activities – unit, integration, and system. · Acceptance test. · White box and black box tests.	Chapter 10, 11	Quiz 2 on Tuesday (3/6). Design concepts. Team presentation on “final” version of system design. Please present new items such as sequence diagrams and user interface/interaction design. Start team work on coding and testing – favorite part of most teams, when you consider those earlier activities such as drawing diagrams and writing documentations.
03/12-03/16	Spring Recess Week. Have a nice break!
03/19-03/23	· Coding and testing cont. 3/19/12 Mon First Day of Summer 2012 RAIL Registration for Continuing Students; Overrides and Schedule Time Conflicts, Office of the Registrar, 9:00 am-4:00 pm. 3/21/12 Wed First Day of Academic Advisement for Continuing Students for Fall 2012.		Quiz 3 will be awarded to the attendance of the final four weeks of team works on coding and testing.
03/26-03/30	3/30/12 Fri Last Day to Withdraw from a Full Semester Class - See Advisor by Noon.		Please manage time in or outside class to finish most planned features in your system. Your team may need to gather together and/or communicate after class to finish your project.
04/02-04/06	4/2/12 Mon First Day of Fall 2012 RAIL Registration for Continuing Students; Overrides and Schedule Time Conflicts, Office of the Registrar, 9:00 am- 4:00 pm. 4/4/12 Wed Last Day of Academic Advisement for Continuing Students for Fall 2012.
04/09-04/13	4/11/12 Wed Last Day to Withdraw from Second Half-Semester Class -- See Advisor by Noon. 4:15pm – NASA Day presentations in Byrd Science 108. 4/12/12 Thu First Day of Spring Weekend Recess (if no snow days used). 4/13/12 Fri Second Day of Spring Weekend Recess (if no snow days used).
04/16-04/20	4/20/12 Fri McMurran Scholars Convocation. Last Day of Classes. Last Day to Withdraw from Full Semester - See Advisor by Noon.		Planned final team presentations.
04/23-04/27	Final Exam Week. Final exam. Time: 3 – 5pm on Thursday, April 26th. Room: SN 227. Please note there is no makeup for the final exam for any reason. Final exams were scheduled by the University at http://www.shepherd.edu/register/finals_schedule.html (Please copy and paste this link to your browser if needed). Any change of time requires the consensus from all students in the class and the approval from the VPAA, and the new time cannot create conflict with other exams. Please note: Your final letter grade is based on your assignment, quiz, midterm exam, and final exam grades. After the final exam week, the registrar's office will make grades available to students on RAIL.