term project cs3141 fall 2012. project #1 a calendar software –core functions multiple user access...
TRANSCRIPT
![Page 1: Term project CS3141 Fall 2012. Project #1 A Calendar Software –Core Functions multiple user access –control other user to read/modify your calendar event](https://reader036.vdocument.in/reader036/viewer/2022082612/56649ea05503460f94ba3eae/html5/thumbnails/1.jpg)
Term project
CS3141
Fall 2012
![Page 2: Term project CS3141 Fall 2012. Project #1 A Calendar Software –Core Functions multiple user access –control other user to read/modify your calendar event](https://reader036.vdocument.in/reader036/viewer/2022082612/56649ea05503460f94ba3eae/html5/thumbnails/2.jpg)
Project #1• A Calendar Software
– Core Functions• multiple user access
– control other user to read/modify your calendar• event management• meeting management
– Schedule meeting– Invite people to the meeting– Check people‘s availability automatically – Allow individual to Deny/access meeting
• Display and print as day/month view– Example:
• Google calendar – www.google.com/calendar
• Zimbra calendar – https://huskymail.mtu.edu/zimbra
• Microsoft outlook
![Page 3: Term project CS3141 Fall 2012. Project #1 A Calendar Software –Core Functions multiple user access –control other user to read/modify your calendar event](https://reader036.vdocument.in/reader036/viewer/2022082612/56649ea05503460f94ba3eae/html5/thumbnails/3.jpg)
Project #2
• Galaxy Sleuth– Core functions
• multiply players • Internet based• Game logic – similar to board game Clue
![Page 4: Term project CS3141 Fall 2012. Project #1 A Calendar Software –Core Functions multiple user access –control other user to read/modify your calendar event](https://reader036.vdocument.in/reader036/viewer/2022082612/56649ea05503460f94ba3eae/html5/thumbnails/4.jpg)
Project #3,4 …
• Any other project that you’ve been wanted to do?– Other games
• Monopoly• Texas Hold’em Poker
– Course Scheduler– Exam Master
![Page 5: Term project CS3141 Fall 2012. Project #1 A Calendar Software –Core Functions multiple user access –control other user to read/modify your calendar event](https://reader036.vdocument.in/reader036/viewer/2022082612/56649ea05503460f94ba3eae/html5/thumbnails/5.jpg)
Choose a project
• Project size is important– Not too big, not too small
• Doable for 4-6 team member to finish it within – 8 hours/wk * 10 wk * # persons
• Motivated is critical– switch to another team if necessary
• Comprising is needed– do you best to fit into the team
![Page 6: Term project CS3141 Fall 2012. Project #1 A Calendar Software –Core Functions multiple user access –control other user to read/modify your calendar event](https://reader036.vdocument.in/reader036/viewer/2022082612/56649ea05503460f94ba3eae/html5/thumbnails/6.jpg)
Class Structure
• Limited Lectures– Team work guidelines– Large software development guidelines
• Waterfall• Agile
• Group work time– Monday is the group meeting time– W,F : the first 5 minutes, quick update
![Page 7: Term project CS3141 Fall 2012. Project #1 A Calendar Software –Core Functions multiple user access –control other user to read/modify your calendar event](https://reader036.vdocument.in/reader036/viewer/2022082612/56649ea05503460f94ba3eae/html5/thumbnails/7.jpg)
Team Leader
• Responsible– Track the team’s progress– Meeting organizer– Bridge between the team and the instructor
• One for each group– Instructor assigned
• based on personal interest, previous experience
– Can rotate between iterations.
![Page 8: Term project CS3141 Fall 2012. Project #1 A Calendar Software –Core Functions multiple user access –control other user to read/modify your calendar event](https://reader036.vdocument.in/reader036/viewer/2022082612/56649ea05503460f94ba3eae/html5/thumbnails/8.jpg)
Waterfall
• Software life cycle– Requirement analysis– Design– Implementation– Release
![Page 9: Term project CS3141 Fall 2012. Project #1 A Calendar Software –Core Functions multiple user access –control other user to read/modify your calendar event](https://reader036.vdocument.in/reader036/viewer/2022082612/56649ea05503460f94ba3eae/html5/thumbnails/9.jpg)
Agile development
• Many iterations – Each iteration is short ( 1, 2, 3 weeks, or a month) – small piece of the product is DONE after each iteration
• Tested• Documented• Can be released
• Some agile practices– Common work room – Daily Standup meeting
• Test driven• Pair programming
– More oral communication, less written documentation upfront.
![Page 10: Term project CS3141 Fall 2012. Project #1 A Calendar Software –Core Functions multiple user access –control other user to read/modify your calendar event](https://reader036.vdocument.in/reader036/viewer/2022082612/56649ea05503460f94ba3eae/html5/thumbnails/10.jpg)
Which process for your project?
• With stable requirements– Do extensive requirement analysis and design
upfront is a very good choice• But it is not easy for inexperienced software engineers• And the design will have to be changed • But again, it is much better than no design, no planning
– You are strongly encouraged to spend significant time to focus on designing before coding