1 / 12

Final Team Project

Final Team Project. ITIS 3110 Lab 6. Final Team Project Schedule. End of Lab 6: Self-select teams 3-5 members Prefer 4 per team Team name selection Work on defining project Rough scope and schedule Turn in Team Name Form One per team Team Name Rough project idea Signatures

chastity-preston
Download Presentation

Final Team Project

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Final Team Project ITIS 3110 Lab 6

  2. Final Team Project Schedule • End of Lab 6: • Self-select teams • 3-5 members • Prefer 4 per team • Team name selection • Work on defining project • Rough scope and schedule • Turn in Team Name Form • One per team • Team Name • Rough project idea • Signatures • Moodle (everyone) • Team Name • Start of Lab 7 • Turn in project proposal form • One per team • Project Name • Final Project Definition • Final Project Schedule • Signatures • Moodle (everyone) • Project Name

  3. Project Basics • Include at least 4 IT items from 2110/3110 lecture or labs • Two may be from 2110 • Two must be from 3110 • Must have one new concept • May be something not done in a lab • E.g. VNC if done in a sophisticated manner • Must be security oriented • Should be the equivalent of 3-4 labs of work • Will be demonstrated at Lab 14

  4. Project ideas • Wireless over long distance (> ¼ mile) • Send a secure video transmission • Use Kerberos and LDAP do implement another service other than one done in class • Use Cisco 5505 security appliance • Implement a Monitoring/IDS/IPS tool and demonstrate • Implement an effective SNMP environment • Do some active monitoring/management • Anything non-trivial (discuss with instructor)

  5. Project Grade • 3110Project.htm • 100 pts • 60 pts • Final Project Criteria • Project report grade • Everyone gets this grade • 40 pts • Peer evaluation • 4 areas for 0-10pts

  6. 3110 Team Evaluations Only one 10 may be given for each category. Give a 10 (if deserved) to the major Contributor in that category • Attended Group Meetings • Attended scheduled group meetings • Gave previous notice if could not attend • Assumed Reasonable Load • All work does not need to be equal • Delivered on Time • Met commitments • Gave early warning and reasons (not excuses) if not able • Group Contribution • Overall contribution • Filled a valuable role for the team • Good leader, documenter, tester, etc. • Criteria • 10 – Excellent (only one per category) • 9 – Major contributions • 8 – Consistent contributor • 7 – Did the job • 6 – Barely met assignment • 5 – Missed major deadlines/tasks • 4 – Major problems • 3 – Barely there • 2 – Got something in eventually • 1 – Breathed • 0 - Absolutely no contribution

  7. Team Evaluations • Confidential between submitter and me • Optional comments • For ratings of 6 or lower: • Explanation of why • Not: • Fred was always late for meetings • Fred never did anything • Good: • The group had 3 meetings planned: 11/22, 11/30, and 12/4. Fred missed the 11/22 and 12/4 meeting without informing the group • Fred's main task was to test the xyz module with test cases 1 through 15. The group did not get the data by the target date.

  8. Teamwork • Choose a captain • Exchange • Telephone #s • eMail IDs • Some method to reliably communicate • Select several commonly available works times • Develop a schedule • Modify as needed • Establish communication protocol • How/when to contact • Consider a Collaboration tool • Wiki? • Google collaboration tools?

  9. Deliverables • End of Lab 6 • One project team name form (printed) – 1 per team • Use proper form with: • Team name • Rough project idea • Identify elements to be implemented • Security implemented • This can change for the proposal due on next lab • Signatures • Everyone in Moodle • Team name • Must match the above Team Name • The above done properly will get Lab 6 first credit (10 pts) • Team Captains • Upload a copy of form with names typed in to Moodle • Bonus point for completing properly • If there is a major problem I see I will discuss with captain

  10. Deliverables • Beginning of Lab 7 • Complete project proposal – 1 per team • Use proper form • Project Name • Add to the proposal form • Complete proposal and schedule • Clearly identify elements to be included in project • Identify security to be implimented • Signatures • Project name in Moodle (all) • 10 pts for completing the from correctly filled and correct name in Moodle • Team captains • Upload proposal to Moodle • The latest completed proposal • Team names typed in • bonus point for captain • I will review during lab and discuss as appropriate with team captain

  11. Overview • Team name due today • Signatures on form and team name in Moodle • High level description of project • This may change for the project proposal • Team proposal due next lab • Signatures on form and project name in Moodle • Detailed description of project • Deliverables • 4 old elements and the new element • Checkpoint dates • Project should consist of: • Integrated four IT items learned in lab • Two may be from 2110 • One new element not covered by a lab • Security aspect

  12. Start • Gather as teams • Identify who is not on a team • Assimilate!

More Related