150 likes | 266 Views
CIS541 - Software Engineering Project II. Dr. David A. Gustafson dag@cis.ksu.edu. Specific Goals of CIS541. Application project plans, cost estimation, earned value, engineering note-book (communication with TA/instructor) New Skills
E N D
CIS541 - Software Engineering Project II Dr. David A. Gustafson dag@cis.ksu.edu
Specific Goals of CIS541 • Application • project plans, cost estimation, earned value, engineering note-book (communication with TA/instructor) • New Skills • Post mortems, formal specifications (OCL), design, checklists, SQA plans, structural testing, presentations to public (open house), • Topics • Terminology, Ideas, Reading Articles, Proposals
Team Web Pages • Each team will maintain their web page • Team or individual picture(s) • Project documentation • object models, use-case, sequence diagrams • decision logs • Project Plan, EV Analysis, Ind Asgs and Time Logs - for each student and summary for team
Team Projects • Iterative Approach • Three working versions will be done • Each iteration will add functionality in everyarea • I will send a goal statement to each team • Week 2 (Jan20) • Teams will post planned functionality for each iteration by Friday, Jan 20th – deliverables must be clear • Week 4 (Jan 30-31 ) Initial Meeting • Presentation of functionality for iteration 1 • Precise definition of inputs, outputs, behavior • Schedules and estimates • 30 minutes, Powerpoint slides, etc • Not a formal presentation • Pres 4 – 2/27-28; Pres 5 – 4/3-4; Pres 6 – 5/1-2
Open House – April 7 and 8 • Projects will be in open house. • Goal will be “presenting to public” • Points for participating in 541 project in open house
Research & Presentation • Each team Or group of students • Research an assigned topic and produce proposal (for class or imaginary company) • Build web page • Definitions • Annotated bibliography • Other ref • Class presentations last three weeks • 5 or more Multiple Choice Questions
Course Grading for 540 and 541 • Individual (average percentages 540 and 541) • Exams, labs, assignments, PLQ, topic presentation • Minus 5*Unexcused absences • Lecture participation • Teams (average percentages 540 and 541) • Presentations, web pages, time logs, open house, installation and documentation • Times Weekly percentage • Average % grades for final course grades if each is above 70%
Late Assignments • Assignments are due at the beginning of the class period or as stated in the assignment • Unless special arrangements are made in advance, assignments will not be accepted after corrected assignments are returned • Late assignments will be penalized 10% per day plus 10% after start of class on due date
Academic Honesty • Plagiarism and cheating are serious offenses and may be punished • by failure on the exam, paper or project; • failure in the course; and/or • expulsion from the university. • For more information refer to the 'Academic Dishonesty' policy in Inside KSU.
CCI – continuing course improvement • Text : Pressman or Project Management book plus UML book? • Online Grades : keeping grades current vs accepting late assignments and grade challenges? • Some students still not doing PLQ • Email
Text • What material/information should come from text? I have been assigning less (shorter) in Pressman • Project management – scheduling, cost estimation • SoftEng – requirements, design, testing, metrics - Solved problems
Online Grades • I try to be “current” on grades – e.g. lab grades, wk team percentages, • Some assignments dribble in, e.g. team interviews • Some grades are “challenged” long after the assignment
PLQs • Useful for performance and reading guidance • Some students still not doing the PLQs on a regular basis
Emails • How to make emails more effective? • I think I am prompt on 80-90% of emails • Suggestions • 541 and issue in subject • One issue/topic per email • Questions at top of email
Next week’s topics • Iterative development & Post Mortems • 4 articles for Tues and Thurs • Royce, “Successful Software Management Style: steering and balance” IEEE Software, Sept/Oct 05 • Birk, etal “Postmortem: Never Leave a Project without it” IEEE Software, May/June 02 • Verner, etal “ What Project Management Practices Lead to Success”, IEEE Software, Jan/Feb 05 • Fairley, etal “Iterative Rework: the Good, the Bad, and the Ugly”, IEEE Computer, sep05 • IEEExplore (Hale Library)