CS 3141: Team Software Project - Introduction

1. CS 3141:Team Software Project - Introduction Ali Ebnenasir Department of Computer Science Michigan Technological University Team Software Project - Ebnenasir - Spring 2008

2. Outline • Course info • Instructor info • Teaching philosophy • Grading • Homework • Exams Team Software Project - Ebnenasir - Spring 2008

3. Course Info. • Textbook: No textbook! • Additional resources (selected): • The Mythical Man-Month (Anniversary Edition with four new chapters) • Frederick P. Brooks. Jr. • Object-Oriented Modeling and Design with UML (2nd Ed.) • Michael Blaha and James Rumbaugh • Meeting time: Tuesdays / Thursdays 11:05- 12:20 • Meeting room: 117 Rekhi Hall • Prerequisite: CS 2141 and CS 2311 http://www.cs.mtu.edu/~aebnenas/teaching/spring2008/cs3141/index.htm Team Software Project - Ebnenasir - Spring 2008

4. Instructor Info. • Name: Dr. Ali Ebnenasir • Office: 206 Rekhi Hall • Phone: 487-4372 • E-mail: aebnenas@mtu.edu • Office Hours: Wed., 2:00 - 4:30, and by appointment. Team Software Project - Ebnenasir - Spring 2008

5. Teaching Philosophy • Interactive • Teaching is a process in which both the teacher and the students should be actively involved • I will not be the only speaker! You will be involved too! • Your participation in class discussions may earn you up to 5% additional points • Please do not be shy to ask questions! Other people may have the same questions as you! • Adaptive • The depth of class topics will be organized based on the average knowledge and enthusiasm of students Team Software Project - Ebnenasir - Spring 2008

6. Teaching Philosophy Absolutely, no working with your laptop in class! Team Software Project - Ebnenasir - Spring 2008

7. Grading • 15% In-class quizzes • 20% Reading assignments • 65% Term project • Requirements Analysis • Design • Implementation • Testing • Presentations • Teamwork (evaluated by peer reviews) • 5% class participation (discussions, presentations, etc.) • Remember, this is an extra credit! Team Software Project - Ebnenasir - Spring 2008

8. Grading - continued • Grade range: • 95% - 100%  A • 90% - 94%  AB • 85% - 89%  B • 80% - 84%  BC • 75% - 79%  C • 70% - 74%  CD • Less than 70%  D • Re-grading • All re-grade requests must be submitted 3 days after the receipt of your grade • Re-grades can go in either direction! Team Software Project - Ebnenasir - Spring 2008

9. In-Class Quizzes • Once in a while we will have a quiz • I will inform you beforehand • Make sure you understand what is presented in class Team Software Project - Ebnenasir - Spring 2008

10. Progress Reports • After each step of the project, each team should deliver a progress report • Example: • Analysis document • Design document • Implementation document • Your write up must be clear, easy to read, free of errors • Please hand in typed documents • A template .tex file is available on the course website Team Software Project - Ebnenasir - Spring 2008

11. Notes on Reading Assignments • You will have some papers to read • I will give you some questions for each reading assignment that you need to address • If you feel you do not know some of the concepts in a paper, please ask questions in class Team Software Project - Ebnenasir - Spring 2008

12. Notes on Presentations • Each team has to present each step of their work in the frame of a 10-minute presentation • Prepare slides for your presentation • Always email me a copy of your presentation 2 days before you present • Only present concepts; avoid having formulas, and tables with numbers • Avoid undefined notations/concepts; define all basic concepts initially • Have very few text; use visual effect as much as possible • Do not read your slides; try to explain the concepts in simple words with concrete examples Team Software Project - Ebnenasir - Spring 2008

13. Notes on Presentations – Cont’d • Except for the implementation phase, there should be no code in your slides! • present abstract algorithms in pseudo code • Balance the amount of material in each slide; avoid crowded slides • Organize your material so you do not need to go back and forth; it is distracting • Have some back up slides for potential questions that may be raised Team Software Project - Ebnenasir - Spring 2008

14. Notes on Writing • You have to write progress reports for each step of the project • I will give you a template for your write up • Attach any analysis/design artifact to your report • E.g., diagrams • Discuss the outline and the quality of your report in a meeting before you present it Team Software Project - Ebnenasir - Spring 2008

15. Term Project • Step 1: • Analysis of a Web-based Student/Instructor Performance Tracking (SIPT) system • You will learn how to • analyze the requirement of a system, • create a conceptual model of a system, and • refine the conceptual model to design artifacts. • Use Computer Aided Software Engineering (CASE) tools • Modeling languages (e.g., Unified Modeling Language - UML) Team Software Project - Ebnenasir - Spring 2008

16. Term Project • Step 2: Design of SIPT system • Refine your conceptual model to design artifacts • Design data base tables • Step 3: Implementation of SIPT • Implement your system • Step 4: Testing of SIPT • Unit testing of your implementation Team Software Project - Ebnenasir - Spring 2008

17. Teaming Up for Project • Teams of 3 people • One person will be the project manager • You should first agree on the requirements • Develop a conceptual model for requirements • Team presentation: • Present every step of your project in class • Your work will be graded by • your teammates (peer-review grading) based on your contribution in each step of the project • your classmates based on your presentation Team Software Project - Ebnenasir - Spring 2008

18. Questions? Team Software Project - Ebnenasir - Spring 2008