Computer Science Department
CS517
formerly
|
Objectives | General Information | Course Materials | Schedule | Assignments |
Projects | Exams | Modeling Session | Grading | Useful links |
Send the instructor your email address and postal address. I will maintain an email list of all the CSUN students so that I can send them information about each lecture the same day.
All CS 517 students (including CSUN studnets) need to have a WebCT account. Your login and password from your Holly account will work for WebCT. Get an account on Holly here if you don't have one.
All lecture notes, assignments, projects and grades will be made available through WebCT. Announcements will be made through the bulletin board in WebCT. You can set up discussion groups and chat-rooms for the course using WebCT.
Click here to go to the password protectd CS517 WebCT page.
Click here for instructions on using WebCT.
Prerequisite: CS414 and CS314 (or their equivalent courses) or consent of instructor.
This course is about systematic, disciplined, multi-person development of complex program systems. Rigorous techniques for modeling, analyzing, and constructing complex systems will be emphasized. The course focusses on the principles underlying rigorous software development techniques. Technology (i.e., specific tools, methods and procedures and languages) will be discussed in terms of how it can be used to incorporate SE principles into processes and products.
At the end of the course students should be familiar with:
The following topics will be covered in the course:
Jan 15 Holiday
|
Jan 17 Overview of Software Engineering
|
Jan 19 Lifecycle models, software process
|
Jan 22 OO Analysis and Design Introduction to UML
|
Jan 24 Use cases Project Assigned Groups formed
|
Jan 26 Use Cases
|
Jan 29 Conceptual Models
|
Jan 31 Conceptual Models
|
Feb 2 Interaction Diagrams
|
Feb 5 Interaction Diagrams
|
Feb 7 Class Diagrams
|
Feb 9 Class Diagrams
|
Feb 12 Class Diagrams
|
Feb 14 Mapping Designs to Code
|
Feb 16 State Diagrams Modeling Session - I
|
Feb 19 Modeling Session - II
|
Feb 21 Modeling Session - III
|
Feb 23 MIDTERM EXAM IN CLASS |
Feb 26 Introduction to Design Patterns
|
Feb 28 Behavioral Pattern - Visitor Design Documents Due Homework 1 Assigned
|
Mar 2 Behavioral Pattern - Iterator - Observer
|
Mar 5 Spring break
|
Mar 7 Spring break
|
Mar 9 Spring break
|
Mar 12 MVC pattern
|
Mar 14 Creational Patterns Factory, Singleton
|
Mar 16 Broker Pattern
|
Mar 19 Introduction to CORBA
|
Mar 21 CORBA-I Homework 1 Due Homework 2 Assigned
|
Mar 23 CORBA-II
|
Mar 26 Introduction to Component Based Software Engineering
|
Mar 28 Patterns, Frameworks and Architectures
|
Mar 30 Examples of CBSE Techniques
|
Apr 2 Introduction to Software Architecture Envisioning architecture
|
Apr 4 Introduction to Software Architecture Creating and analyzing architectures
|
Apr 6 Software Architecture Case study
|
Apr 9 Introduction to Concurrent Programming Concurrent OO programming
|
Apr 11 Introduction to Concurrent Programming Exclusion Homework 2 Due Homework 3 Assigned
|
Apr 13 Introduction to Concurrent Programming State Dependence
|
Apr 16 Introduction to Concurrent Programming Creating threads
|
Apr 18 Designing Concurrent Programs
|
Apr 20 Real-time Java
|
Apr 23 Refactoring
|
Apr 25 Refactoring
|
Apr 27 Refactoring Project Due
|
Apr 30 eXtreme Programming
|
May 2 eXtreme Programming Homework 3 Due
|
May 4 Course Review
|
May 7 Finals week
|
May 9 Finals week
|
May 11 Finals week
|
There are 3 homework assignments in this course. Each involves programming with Java. Each homework is worth 10% of the grade. Assignments will be made available through WebCT.
# | Name | Assigned | Due |
1 | Programming using Visitor Pattern | February 28 | March 21 |
2 | CORBA application | March 21 | April 11 |
3 | Concurrent Java | April 11 | May 2 |
Each student is expected to work in a group to develop a software system. Each group is expected to produce a project plan, a requirements document, a design document and code for their project. The project is worth 30% of the final grade. Project demos will be held in the week of April 30 - May 4. Project descriptions will be available through WebCT
# | Task | Date | Grade |
1 | Project assigned | January 24 | |
2 | Groups formed | January 24 | |
3 | Design Documents due | February 28 | 20% |
4 | Project code due | April 27 | 10% |
There are two exams: one midterm exam (in class) and one final exam (final's week).
Exam | Date |
Midterm exam: | February 23 in class |
Final exam: | May 9, 7:00 am - 9:00 am |
Homework: | 30% |
Project: | 30% |
Midterm exam: | 15% |
Final exam: | 25% |
Final letter grades will be based on the relative distribution of total scores and not on any preset numerical grade. Click here to see your grades.
Last modified: Feb 12, 2001.