SDPCoordinatorDr.AbzetdinAdamov
Director,CenterforDataScienceResearch&TrainingSchoolofIT&Engineering
SeniorDesignProject- 2
Content
• SDP– IIDescription• Prerequisites• Objectives• EvaluationandDeliverables• ResourcesandPresence• Meetings• FinalProjectReport• FinalProjectPresentation• Timeline• DocumentsandForms
ImportantTerms
• ProjectTopic• ProjectTeam• ProjectAdvisor• IndustryMentor(CompanySponsor)• SDPCommittee• ProgressReport• FinalReport
IntroductiontoSeniorDesignProject(SDP)– II
SeniorDesignProject-IIisthesecondoftwosemestercoursethatfocusedofdefinition,analysis(SDP-I),implementationanddocumentationofprojecttopic(SDP-II).SDP-IIconsistsofthefollowingmilestones:thedesign,implementation,evaluation,documentationandpresentationoftheproject,conductedbystudentteams(of3-4members)formedatthebeginningofSDP-I.SDP-IIwillbeconcludedwithpublicpresentation.Completedprojectswillbeevaluatedbypanelthatwillconsistofprojectadvisors,facultyandindustryprofessionals.Theevaluationwillbedonebasedongeneralcriteriaforallprojects(Originality,Relevance,Practicality),aswellasprojectspecificones(Overalllifecycle,Usefulness,Functionality,Sustainability,Aesthetics).
PrerequisiteforSeniorDesignProject(SDP)– II
SITE4790- SeniorDesignProjectI
SeniorDesignProjectconsistsoftworelatedcourses:• SITE-4790SeniorDesignProjectI(Fall)
oPhase1:ProposaloPhase2:Requirements&Design(DraftReport)
• SITE-4890SeniorDesignProjectII(Spring)oPhase3:FinalReportoPhase4:Prototype/Implementation
Whatisdifferentaboutthisclass
Unlikeothercourses,thiscoursedoesnotintendregularparticipationinclass,insteaditisindependentstudy/research.MeetingsarescheduledwiththeProjectAdvisor(facultymentor)fortheparticularSeniorDesignProject.EachProjectTeamwillmeettogetherweekly,keepingdetailedminutesofthemeetings.
SDP– IILearningObjectives
• facilitatingthetransitionfromacademicstudytoanindustryor/andresearchcareer• learningtoaddresschallengingproblemsdefiningscopeandstatement,designing,developingandmanaginglife-cycleofend-userproducts• developingrapidlearningskillsofnewtechnologies,software,hardwareandtools• developingdocumentation,demonstrationandoralpresentationskills
SDP– IIEvaluationandDeliverables
1. Weeklymeetingsandteamprogressreview[15%]2. EvaluationofDraftwrittenreportandpre-finalprototype[15%]
(February- 7thweek)3. FinalReport[30%](April- 12thweek)4. FinalProjectPresentations- demo[40%](April- 14thweek)5. Bonus:Scientificpapersubmission[10%]6. Bonus:Publicseminarpresentation(March– 7-10thweek)[10%]
LateDeliveryofDeliverables
EachevaluationcomponenthaspredefineddeadlineandlatesubmissionsareNOTwelcome.Latedeliverables(documents,reports,code,etc.)willbeacceptedwithinstructor’spermissiononly.Penaltyforlatesubmissionforeachdeliverableis10%pointsdeductionperday.Exceptionsmaybemadeforteamswithvalid,documentedexcuses.
SDP– IIProjectWEBSITE
EachprojectteamisrequiredtopreparemandatorywebsitededicatedtotheirSeniorDesignProject.Websitemustincludeatleastfollowingpages:• home-pagewithgeneralinformation(title,logo,description),• team(withtheroledescriptionofeachmember),• deliverables,• acknowledgement,• documents(allforms/reportsmustbeavailableatthissection:projectproposal,progressreport,finalreport,etc.).
Dependingonthespecificproject,websitemayincludeotherpagesaswell.Itisrecommendedtousewordpress.comorblogger.com tohostyourprojectwebsite.
SDP– IIProjectGITHUB
Dependingontypeoftheproject(mainlyforprojectsthoseincludesoftwaredevelopmentcomponent),itisrecommendedtomaintaintheGithub page/repositorythatincludesnon-confidentialinformation.
SDP– IIProject.SCIENTIFICPAPERPUBLISHING
ProjectTeamsarehighlyencouragedtopublishoutputsandscientificfindingsoftheirprojectasapapersinanyscientificconferenceorjournal.Teamswhomanagedtosubmitapaperandreceivedletterofacceptancecanearnfortheadditional10%bonustobeaddedtofinalgradeoftheSDP-II.
SDP– IIProjectLOGBOOK
ItisrecommendedtoeachteamtomaintainLogBook wheretheprogressoftheprojectadvancementisreflected.TheLogBook willhelpyoutoprepareyourProgressReportseasilyandquickly,totrackcontributionofeachteammember,towriteFinalReportandprepareDemo.
WeeklyProjectAdvisorMeetings
Eachteamisexpectedtomeetprojectadvisoratleastonceperweektodiscussadvancementsinprojectduringpreviousweek,accomplishmentsbyeachteammember,tasksplannedforthenextweek,possibleproblemsinadvancement.ForeachmeetingteamshouldprepareWeeklyProgressReport(AppendixA.)thatconsistsofprogresshasbeenmadeduringpreviousweekanddefinesplansforthenextweek.Itistheprojectteam`sresponsibilitytosetupweeklymeetingswiththeprojectadvisor.Allmembersmustparticipateinthesemeetingsandbepreparedtoelaborateontheiractivities.ProjectAdvisorwilluse"APPENDIXA– ProjectAdvisorMeetingLogSheet"tologkeypointsofthemeeting.
WeeklyTeamMeetings
Weeklyteammeetingswhereteammembersmeeteachotherareareactivitiesrequiredfortheprojectsuccess.Itisrecommendedtohaveatleasttwoteammeetingsperweektodiscusstheprojectandworkjointly.Thiscanbeeitherbeforeoraftertheweeklyadvisormeetings.Butyouareencouragedtohaveoneteammeetingbeforethemeetingwithyouradvisorinordertobepreparedtomakethebestuseofthetime.Eachteamisrequiredtofilluptheform"APPENDIXA– Team’sWeeklyProgressReport"foreachmeetingwithProjectAdvisor.
FinalProjectPresentation
FinalslidesoftheprojectpresentationmustbesubmittedtotheProjectAdvisoratleastoneweekbeforepresentationdate.Timing:Maximumtimeallocationforeachpresentationis20min+15minforQ&A.Don'tincludeintoyourpresentationmorethan20slides.Ifyoudon'tcompleteyouroralpresentationin20min,itmayaffectyourgrade.PresentationFormat:Responsibilityandcontributionofeachteammembersshouldbeclearlyaddressed.
FinalProjectPresentation
Presentationcanlogicallydividedintothreeparts/sections:1st:Generalinformationwithouttechnicaldetailsdescribinghowusefulandimportantyouridea.Usemorepicturesandlesstextualinformation.Don'tallocatemuchtimetothissection.2nd:Mostlytechnicalinformationshouldbeprovided.Avoidgeneralinformation.Whatyoudidtoimplement/releaseyouridea?Howdidyoudevelopthesolution?Youexpectedtoclearlydemonstratethatyouunderstandtheproblemandsolution.3rd:Futureplanestoensuresustainabilityoftheproject.
FinalProjectPresentation
Eachpresentationmustincludefollowingsections:1. Coverpagewithprojecttitle,logo,graphics2. Teammembers,theirresponsibilitiesandroles,advisor,acknowledgments3. Motivation/ProblemStatement4. Research/DevelopmentChallenges(Methodology/Software/Hardware)5. Diagram/Architecture/Model/Flowchartthatbestdescribeyoursystemand
itsfunctionality6. Timeline/GanttChartoftheproject,includingfutureplans(possibly,including
commercialisation plans)7. Social,cultural,environmentalimpactexpectedfromtheproject8. Risksforthesuccessoftheproject(orrisksresultedbytheproject- ifany...)9. References(includingSDPProjectwebsite,Github,etc.)
TimelineJanuary/February:• Teamsregularlymeetprojectadvisorandindustrymentor• Teamsbegin tobuildprototypeorsimulationmodel (February - 7thweek)March:• Teamsregularlymeetprojectadvisorandindustrymentor• Teamssubmitadraftwrittenreporttotheprojectadvisor(March- 10thweek)• Teamsrefine, testandcompleteprototypeorsimulationmodelandexecutefinalenhancements (March-10thweek)
April:• Teamsregularlymeetprojectadvisorandindustrymentor• Teamsdevelopposters,oralpresentations,anddemonstrations forSeniorDesignProjectsDemoDay• TeamsgetapprovalfromtheProjectAdvisor regardingcompletionoftheproject(April - 12thweek)• Teamspresentfinal, completewrittenandoralpresentationtopanel(April - 14thweek)
SDP– IIForms
• AppendixA:Team’sWeeklyProgressReport• AppendixB:ProjectAdvisorMeetingLogSheet• AppendixC:ProjectAdvisor’sApprovalsForm• AppendixD:FinalPresentationReadinessFormbyAdvisor• AppendixE:FinalPresentationReadinessFormbyIndustryMentor
ExampleofGuntt Chart
Task Weeks
1-2 3-4 5-6 7-8 8-9 9-10 10-11 11-12 12-13 14-15
1. ……..
2. ……….
3. ……….
4. ……….
5. ……..
6. ………
7. ………
Q&A ?Abzetdin Adamov,Assoc Prof.Emailmeat:[email protected]:@Linktomeat:www.linkedin.com/in/adamovVisitmyblogat:aadamov.wordpress.com