| Contact Information | Course Description | Course Materials |
| Course Outline | Calendar | Assignments |
| Grading | Attendance and Participation | Viruses |
| Dishonesty |
Contact Information
| Professor | Richard J. Povinelli, Ph.D. |
| Richard.Povinelli@mu.edu (checked late evening or early morning) | |
| Homepage | http://povinelli.eece.mu.edu |
| Bulletin Board | http://bb.mu.edu |
| Turnitin | http://www.turnitin.com |
| Phone | 288-7088 with voice mail |
| Office Hours | |
| Office | EN224 |
| Lab | EN523, EN388 |
| TA | Jack Szeto |
| TA Office Hours | Wed: 12-3pm; Fri: 10am-12pm in EN379 |
Course Description and Prerequisites
- Fundamental issues:
- Engineering process of software development, process models, process management, and quality control
- Concepts of object orientation; design of classes and objects
- Software requirement analysis, use cases, software architectural design, detailed design, implementation and testing
- Advanced topics:
- Rational Unified Process
- Unified Modeling Language (UML)
- Introduction to software design patterns, e.g. "gang-of-four"
- Computer Aided Software Engineering (CASE) tool, e.g. ROSE
- Features:
- Focusing on object-oriented analysis and design
- Not only learn about software engineering, but actually practicing software engineering
- Using today's most widely accepted approach
Prerequisites: COEN 030
Course Outline
| What | When |
| Introduction | wk 1 |
| Modeling with UML | wk 2 |
| Requirements Elicitation | wk 2-3 |
| Analysis | wk 3-4 |
| Project Organization and Communication | wk 5 |
| System Design | wk 6-7 |
| Object Design | wk 7-8 |
| Mapping Models to Code | wk 9 |
| Testing | wk 10 |
| Rationale Management | wk 11 |
| Configuration Management | wk 12 |
| Project Management | wk 13 |
| Software Life Cycle | wk 14 |
| Methodologies: Putting It All Together | wk 15 |
Calendar
| Week | Month | Mon | Wed |
| 1 | Jan |
|
|
| 2 | Jan | 19 |
|
| 3 | Jan |
|
|
| 4 | Feb |
|
|
| 5 | Feb |
|
|
| 6 | Feb |
|
|
| 7 | Feb |
|
|
| 8 | Mar |
|
|
| Mar | 8 |
|
|
| 9 | Mar |
|
|
| 10 | Mar |
|
|
| 11 | Mar |
|
|
| 12 | Apr |
|
|
| 13 | Apr | 12 |
|
| 14 | Apr |
|
|
| 15 | Apr |
|
|
| May | 3 |
|
| No Class |
NOTE: All dates and numbers are subject to change as deemed necessary!
Course Materials
Required Text
- Oriented
Software Engineering: Using UML, Patterns and Java, 2/E, by Bernd
Bruegge and Allen
H. Dutoit, Prentice Hall,
2003.
Grading
| What | Number | Value per | Total |
| Assignments | ~10 | 10 | 100 |
| Final Exam | 1 | 300 | 300 |
| Projects | 3 | 200 | 600 |
| Total | 1000 |
NOTE: All dates and numbers are subject to change as deemed necessary!
Grade Scale
| 93+ | A |
| 89-93 | AB |
| 85-89 | B |
| 81-85 | BC |
| 77-81 | C |
| 74-77 | CD |
| 70-74 | D |
The grading scale is the most stringent one you will be held to, i.e. I can give you a higher letter grade than shown on the scale, but never a lower one.
Late Assignments
I will deduct 25% for assignments up to one day late, 50% for two days late, and 75% for up to three days late. I will not accept work later than 3 days. The weekend will count as 1 day. Assignments are due at the beginning of class. They are late after that.
Attendance and Participation
I have always enjoyed teaching classes where the students actively participate - a conversation is more fun than a monologue! Although there is no specific credit assigned for attending, it is still expected. I reserve the right to withdraw a student for more than five absences.
Assignments
Undergraduates should expect to spend, on average, from six (6) to nine (9) hours per week on preparation for this class. Graduate students should expect to spend an additional three hours per week. This time is in addition to the three (3) hours of lecture you are expected to attend every week.
Assignments are due only electronically before class via Turnitin. I will be using Turnitin mainly for its electronic tools for grading and managing assignments. However, Turnitin is primarily a site to detect plagiarism. I will be taking advantage of this capability also. Your assignments become a permanent part of the Turnitin.com database. The use of your assignments by Turnitin.com will be exclusively for the purpose of detecting future plagiarism.
All assignments are due according to the the times specified in the calendar.
Assignments
Reading, problems, and programming exercises will be assigned on a regular basis.
Project
There will be one (2) project. This will be a large effort using software engineering to solve some reasonably complex problem.
Exams
There will be two exams for this course. One will be a midterm and the other a final.
Academic Integrity
College of Engineering Policy and Procedure - Academic Dishonesty (Make sure you read this)
Marquette University Policy - Academic Dishonesty (Make sure you read this)
My Policy
ACADEMIC DISHONESTY OF ANY FORM WILL NOT BE TOLERATED IN THIS CLASS. ANY STUDENT FOUND TO BE PERFORMING ANY ACT OF ACADEMIC DISHONESTY WILL BE SUBJECT TO THE MAXIMUM PENALTY FOR THE PARTICULAR OFFENSE.
I will use Turnitin.com as a tool for maintaining academic integrity.
Viruses
Any assignment turned in in electronic format that contains a virus will receive a zero.