1. CMSC 345 Software Design and Development Spring Sections 0101 & 0201 Ms. Susan Mitchell Leave Your Ego at the Door!
CMSC 345, Spring 2004

2. First Assignment Read through the course web site:
/345/spring04/mitchell
Fill in the Availability worksheet for Thursday
CMSC 345, Spring 2004

3. Course Objectives
To understand and experience the software development life cycle
To experience working on a software development team (and being “egoless”)
To experience taking a leadership role in a software development team
To enhance written and verbal communications skills
To learn about professional ethics in computer science
CMSC 345, Spring 2004

4. Prerequisite: CMSC 341, Data Structures
CMSC 345, Spring 2004

5. This Course Will Be ... different eye opening fuzzy frustrating
time consuming
fun
CMSC 345, Spring 2004

6. You Will ... think plan communicate participate negotiate code
write, write, write
CMSC 345, Spring 2004

7. Class Format Lectures Discussions In-class work time
Outside of class work time
Speakers
Working in teams
UML
Capability Maturity Model (CMM)
Software testing ?
CMSC 345, Spring 2004

8. Class Format (con’t) Post mortem exercise
Section 0101: Thursday, 5/13, 10:30 -12:30
Section 0201: Thursday, 5/13, 1: :00
Attendance is mandatory.
CMSC 345, Spring 2004

9. The Teams 4 or 5 people chosen by the instructor
Team leader chosen by team
Phase leaders chosen by team (see job descriptions on web)
Requirements
Design
Implementation
Testing
Delivery
Faculty/staff customers assigned randomly
CMSC 345, Spring 2004

10. The Project Chosen by instructor
Minimal description (must elicit requirements from customer)
Past projects:
automated grade book
math tutor for elementary students
form letter generator
appointment calendar
examination generator
final grade distribution system ( )
laboratory scheduling system
CMSC 345, Spring 2004

11. The Project (con’t)
Your choice of language, but restricted to imperative and OO languages (e.g., C, C++, Java) unless otherwise approved by instructor
Your choice of interface type (text or GUI)
Your choice of platform (with customer approval)
CMSC 345, Spring 2004

12. Grading Attendance (5%) Personal journal (5%) Quizzes (10%)
Project artifacts (40%)
Systems Requirements Specification (10%)
System Design Document (10%)
Code Inspection Report (5%)
Test Report (5%)
User Manual (5%)
Administrator Manual (5%)
CMSC 345, Spring 2004

13. Grading (con’t) Customer satisfaction and biweekly status reports (5%)
Final product delivery and demo (10%)
5% individual grade
5% team grade
Final product (25%)
Other
participation
time sheets
verbal status reports
self evaluation
student survey
CMSC 345, Spring 2004

14. Textbook and Other Resources
Text: none
References posted on course web site (Software Engineering Resources link)
Articles from “Software Development Magazine” will be used:
CMSC 345, Spring 2004