Student Outcome Assessment Documentation

Computer Science Degree

University of Utah Departmental Student Outcome Assessment Documentation. Computer Science Degree

COMPUTER SCIENCE DEGREE 4500 Software Engineering Laboratory (3,S) Prereq: C P S C 3500, C P S C 3510, senior standing in Computer Science. Development of significant software systems by small student groups, with emphasis on applying sound, disciplined software engineering practice. CS 4500 EMCB 102 MWF 3:00-4:00 Instructor: Thomas C. Henderson Announcements Week 15 • CS 4500 2005 Demo Day Brochure Week 10 • CS4500 2004 Demo Day Brochure • CS4500 2005 Demo Day Team Locations in Lab (gif) • CS4500 2005 Demo Day Team Locations in Lab (ppt) Week 2 • There is a FAQ link now for the class. • There is a management meeting schedule link for the class; look at it and make sure you show up at my office the day and time scheduled. Every team member is required to be at the weekly meeting; please send email to teach-cs4500 if there are any absences. • We plan to get you something back by Wednesday noon in terms of the first week's work, including the bids. Industry partners are looking at them, too. Watch your email, as it may be useful to schedule a meeting with the team (these will be during class time). Week 1 • Teams must be formed by the end of the first class (10 Jan 2005) • Subscribe to cs4500. • Send the name of the team and team members to tch by Wedensday (12 Jan). • Tom and Brandt will be available in class on Wednesday (12 Jan). • Bids for projects are due by 14 Jan 2005 (midnight). Overview of Course / Links • Course Objectives • Prerequisites • Course Description • Software Used to Support Class • Assignments • CS 4500 FAQ • Team Management Meeting Schedule • Guidelines for Documents and Deliverables • Industry Sponsored Projects Information • Internally Sponsored Project • College Guidelines and Procedures Course Objectives Engineer (n): a designer or builder of engines Engineer (yr): to lay out, construct, or manage as an engineer Engineering (n): the art of managing engines This course is the senior software engineering lab course. According to the C S department class catalog this course involves: Development of significant software systems by small student groups, with emphasis on applying sound, disciplined software engineering practice. Because of the prerequisites for the course, we assume that you have had lots of opportunities to learn sound, disciplined software engineering practice. Now here's your chance to show off a little on a significant project. Show us what you can do! Instructor Thomas C. Henderson, Professor E-Mail: [e-mail] Phone: [phone] Fax: [phone] Office Hours: By appointment (arrange by email). Teaching Assistant TA: Brandt Erickson E-Mail: [e-mail] Phone: TBA Office Hours (MEB ): TBA You can contact us with questions by email at: teach-cs4500@cs Subscribe! to the class mailing list: cs4500@cs Prerequisites The prerequisite is successful completion of C S 3500. Course Description This offering of the course will be a little different from previous versions. It will be a little more structured in terms of deliverables. Teams Teams must have 3 or 4 members. Bids Each team must submit 2 or 3 bids on projects. Possible Projects There are 3 possible types of projects: Industry Sponsored: Descriptions given by local companies who act as clients (see project descriptions in industry) Internally Sponsored: Prof. Henderson needs a conference paper review system (see internal) Self Sponsored: A team may propose a project; this will require approval, and Prof. Henderson will act as client. Meetings Once teams are formed, and projects are picked, the rest of the course will be largely lecture-free. Instead, each group will schedule a weekly meeting with the advising professor. Attendance at these weekly update meetings will be mandatory and will be scheduled during class lecture hours. (Note: each student may miss a max of 2 of these meetings due to sickness or emergency -- but 2 is the limit!) Each team must turn in a Weekly Management Report at least 2 hours before the meeting. This should be done electronically as a PDF file sent by email. Deliverables In addition to the weekly update meetings, you will be required to turn in the following deliverables during the semester (details on formats of documents, etc. can be found in Guidelines link above): 1. Bids on 2 or 3 projects 2. Individual Logs detailing work on project 3. Project History Documents 4. Project Plan 5. SRS (Software Requirements Specification) 6. SDS (Software Design Specification; 2 versions: v1: high-level design and v2: detailed design) 7. VVP (Verification and Validation Planning) 8. VVR (Verification and Validation Results) 9. Stage 1 Release 10. Stage 2 Release 11. Stage 3 Release 12. Product Release 13. Final Report 14. Legacy Turn-In Materials Note that I am using specific document deliverables and formats (use the formats for this class - they are based on the class at Texas) but you must incorporate responses to the information required from the class text (Software Project Survivors Guide) Software Used to Support Class Students can use whatever platform they like to develop their projects. A UNIX environment is available in the CADE lab, and an NT environment is available in the NT lab. Your choice of platform and development environment should be justified in your group meetings. Assignments Each team will be assigned a project from their ordered list of preferences. Each of the sponsors will present their projects on the first day of class to help you choose your preferences. The schedule for assignments is as follows: Date Particularly Appropriate Reading Assignments Assignments Due Team meeting with prof every week Week 1: Jan 10-14 Chapters 1-4, 18 (1) Form team (2) Make bids (3) Read S P S G (all) (4) Start Project History (5) Start logs (6) Create project website (1) Team formed (2) Bids submitted (14 Jan by midnight) Week 2: Jan 17-21 (17 Jan is a holiday) Chapters 5-7 (1) Project Plan (2) S R S (1) Updates to logs (2) Updates to Project History Week 3: Jan 24-28 Chapters 8-9 (1) S D S (both versions) (2) VVP (1) Project Plan (Monday 24 Jan) (2) S R S , v1 (Friday 28 Jan) Week 4: Jan 31 - Feb 4 Chapters 10-13 (1) Planning Checkpoint Review (2) SDS, v1 (Friday 4 Feb) Week 5: Feb 7-11 Chapters 14-18 1 1 (1) VVR (2) Stage 1 Release (logs, history updates) Week 6: Feb 14-18 (1) SDS, v2 (Friday 18 Jan) Week 7: Feb 21-25 (21 Feb is a holiday) (1) VVP Week 8: Feb 28-Mar 4 (logs, history updates) Week 9: Mar 7-11 (1) VVR (2) Stage 1 Release Week 10: Mar 14-18 Have fun! Week 11: Mar 21-25 (1) VVR (2) Stage 2 Release (logs, history updates) Week 12: Mar 28 - Apr 1 (1) VVR (2) Stage 2 Release Week 13: Apr 4-8 (1) VVR (2) Stage 3 Release (logs, history updates) Week 14: Apr 11-15 (1) Product Release (1) VVR (2) Stage 3 Release (3) Formal Presentation to Industry Sponsor Week 15: Apr 18-22 (1) Legacy Turn-In (2) Final Report (3) Demo (1) Product Release Week 16: Apr 25-29 (1) Legacy Turn-In (2) Final Report (3) Demo (Thursday, 28 April) 28 April 2005 Demo Day Grade Weekly Meeting 20% Documents 20% Project Web Page 20% Final Project & Demo 40% Pointers to Projects Team 1: Lovelace ... Team 2: All Your Base Team 3: Whinot Team 4: Cool Team Name Team 5: Kano Entertainment Team 6: Star Wars Team 7: Cyber Ninjas Team 8: Design Bug L L C Team 9: Su-nami Team 10: Silent Mission Team 11: Inculpable, Inc Team 12: DocSoft Team 13: while(true) fork Team 14: MOKI • Team 15: HTMB • Team 16: TDO Design • Team 17: Seattle • Team 18: PADD • Team 19: TripleW • Team 20: Group 3D's • Team 21: Boomerang Class web: http://www.cs.utah.edu/classes/cs4500/ COMPUTER ENGINEERING 4710 Computer Engineering Senior Project (3,F) Prereq: C P S C / E L EN 3710, C P S C / E L EN 3720, senior standing in Computer Engineering. Crosslisted with EL EN 4710. Students design a microcomputer system that includes RAM, EPROM, and I/O devices. Capstone project for computer engineering majors. Formal written reports, one or more oral presentations. CS/CE4710 Senior Project Class Class Time: Tue & Thu 9:10 - 10:30 Class web: http://www.cs.utah.edu/classes/cs4710/ Location: EMCB124 for lectures, Senior Hardware lab 3143MEB for labs. Please check the website before class so that we all meet in the same place. Class Mail List: Please join [e-mail] Instructor: Bruce Boyes TA: Steven Wheeler UofU Office: Senior Hardware Lab, 3143MEB. At the moment, hours by appointment TA Office: TBD. Hours: Tue/Thu after class Work Office: Systronix Inc, 555 South 300 East, Tel: [phone] TA email: [e-mail] Instructor email: [e-mail] Fall 2003 calendar http://www.sa.utah.edu/regist/calendar/datesDeadlines/fall2003.htm Book: http://www.practicalembeddedjava.com/