CMSC 345, Fall CMSC 345 Software Design and Development Fall 2003 Section 0101 Ms. Susan Mitchell Leave Your Ego at the Door!
CMSC 345, Fall First Assignment Read through the course web site: /345/fall03/mitchell Fill in the Availability worksheet Read “See You in Court,” January 2003, Software Development Online:
CMSC 345, Fall 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, Fall This Course Will Be... different eye opening fuzzy frustrating time consuming fun
CMSC 345, Fall You Will... think plan communicate participate negotiate code write, write, write
CMSC 345, Fall Class Format Lectures Discussions In-class work time Outside of class work time Speakers –UML –Working in teams –Capability Maturity Model (CMM) –Software implementation (programming, integration) –Software testing Post mortem exercise (Thursday, 12/11, 10:30-12:30)
CMSC 345, Fall 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, Fall 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 ( ) Your choice of language, interface type, etc., but be careful (risk!)
CMSC 345, Fall 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, Fall 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, Fall Textbook and Other Resources Text: none Other sections: Software Engineering, Ian Sommerville References posted on course web site (Software Engineering Resources link) Articles from “Software Development Magazine” will be used: