Office: ECSS 3.204, ECS, UTD
Web page: (NOT webCT!)
Office hours: T 1:00-2:30pm, 5:00-5:30pm, or by appointment
Lectures: TR 5:30-8:00pm, ECSS2.201
Textbook: Object-Oriented Software Engineering: Using UML, Patterns and Java, Second Edition, Bernd Bruegge and Allen H. Dutoit, Prentice Hall, 2003. http://wwwbruegge.in.tum.de/OOSE/
§ The Unified Modeling Language User Manual, G. Booch, J. Rumbaugh and I. Jacobson, Addison-Wesley, 1998.
Prerequisites: CS 5303, CS 5333
Concurrent Prereq course required CS 5343
This course is intended to provide an extensive hands-on experience in dealing with various issues of software development. It involves a semester-long group software development project spanning analysis of requirements, construction of software architecture and design, implementation, and quality assessment.
You can obtain a trial version of Rational Rose to run the program(s) on your home PC from http://www.rational.com/tryit/index.jsp, demo and online tutorial from http://www.rational.com/tryit/rose/seeit.jsp . A student version is also available.
If you wish, you can use the facilities at UTD too (ES2.104 on the ground floor in ECS). All PC’s in the labs of UTD are installed with Rational Rose. There are several open access labs: http://www.utdallas.edu/ir/tcs/labs/locations.htm. You will need to get a user ID for the lab, https://netid.utdallas.edu. Need help? 972-883-2911, email@example.com, http://www.utdallas.edu/ir/tcs
Project: There will be a multi-phase project (see a Summary of Report_of_the_Inquiry_Into_The_London_Ambulance_Service). Each project phase should be submitted by the expected due date in the beginning of the class that day – one hardcopy per team and all the softcopies should be available on the team web site. Project phases should be submitted with team name; team URL; and for each member of the team: student name, student ID and student email address; project phase #, and class/section written on the first page.
The project will be done by teams of 5-7 students (More specifics on this in class). All students in a team will get the same mark for the work they do unless they unanimously agree (in writing) to an unequal division. You are to choose your own team members. An orphan will be assigned to a team by the instructor.
For each deliverable, there should be a team leader, who coordinates communication and deliverable submission. Each team should select one or two team leaders, on a rotating basis, for each phase of sub-phase of deliverable.
Project I under development needs to be presented. Project II need to be presented in the last week of class.
Tests: There will be two tests, one in the middle (test 1) and the other at the end (test 2) of the course.
Late work: Any assigned work will have 10 points deducted for each week passed.
Project (5 x 7)
Important Dates (could be agile):
1. May 26 (Tuesday) - First day of class for this course
June 4 (Thursday) – Deliverable 0.0: Preliminary Project Plan (Team organization, Team leaders/deliverable, Team web site URL, Tools, etc.) http://wwwbruegge.informatik.tu-muenchen.de/twiki/bin/view/OOSE/SoftwareProjectManagementPlanTemplate some samples
2. June 16 (Tuesday) – Deliverable 1: Requirements Specification (and Deliverable 0.1) [This could be submitted together with Deliverable 2, if needed]
(Omit: 3.4.3 Object model; 3.4.4 Dynamic model; and possibly 3.4.5 User interface —navigational paths and screen mock-ups)
3. June 23 (Tuesday) – Deliverable 2: Analysis (and Deliverable 0.2)
(Include: 3.4.3 Object model; 3.4.4 Dynamic model; and 3.4.5 User interface —navigational paths and screen mock-ups)
4. June 25 (Thursday) – Test 1
5. July 7 (Tuesday) – Deliverable 3: Architecture Specification
6. July 16 (Thursday) – Deliverable 4: Component/Object Specification [This could be submitted together with Deliverable 5 & 6, if necessary]
7. July 23 (Thursday) – Test 2
8. July 28 (Tuesday) – July 30 (Thursday) – Final Project submission and a demo. This should include
§ Deliverable 5: Code;
§ Deliverables 1-4; and
§ Deliverable 0 - the final version,
With the traceabilities among them, all in one document.
Each team should set up a time with the TA to do a demo; A hardcopy should be submitted at the time of the demo.
9. May 26 (Tuesday) – July 30 (Thursday): communications and revisions of the project plan
The University of Texas System Policy on Academic Honesty (The Regents and Regulations, Part One, Chapter VI, Section 3, Paragraph 3.22):
Any student who commits an act of scholastic dishonesty is subject to discipline. Scholastic dishonesty includes but is not limited to cheating, plagiarism, collusion, the submission for credit of any work or materials that are attributable in whole or in part to another person, taking an examination for another, any act designed to give unfair advantage to a student or the attempt to commit such acts.
layer hidden off the screen
Topics Approx. duration
Preliminary 1 week
UML Overview 1 week
Coding (Forward Engineering) 1 week
Priorities: Class Discussions !!, Lecture Notes !, Textbook and References!!!
Presentations – Summer 2007
Ambulance Dispatch System – Some Articles