1. YouTube Duplicate Finder Group 4 Members : Brian Kelly Darryl Parulan Vanessa Kellawan Diana Gonzalez Natoya Higgins

2. Project Description  Problem YouTube search returns multiple postings of the same video clip (unnecessary) YouTube search returns multiple postings of the same video clip (unnecessary) Due to different users posting the same video Due to different users posting the same video Example: Example: The Simpson's searchThe Simpson's searchThe Simpson's searchThe Simpson's search  Solution – YouTube Duplicate Video Finder User inputs search terms into web app User inputs search terms into web app App returns search from YouTube and displays to user App returns search from YouTube and displays to user Redundancy decreased by categorizing similar videos Redundancy decreased by categorizing similar videos

3. Concept of Operations  Users YouTube users YouTube users  Operational Scenario User opens application User opens application Search page is displayed Search page is displayed User types in video title User types in video title Search returns videos grouped together on results page Search returns videos grouped together on results page

4. Software Requirements Specifications  Stakeholders Gary Stein Gary Stein Our main clientOur main client Our point of contact for requirementsOur point of contact for requirements YouTube Viewers YouTube Viewers Anyone interestedAnyone interested Dr Damla Turgut Dr Damla Turgut Handed out assignmentHanded out assignment

5. SRS Continued  Product Assumptions Written in C# Written in C# The user is on a Windows platform with.NET 2.0 framework The user is on a Windows platform with.NET 2.0 framework The user has access to the internet The user has access to the internet The software will communicate to the user through a web browser The software will communicate to the user through a web browser The program will communicate with YouTube through the developer API they provide The program will communicate with YouTube through the developer API they provide YouTube Viewers

6. SRS Continued  Specific Requirements The system shall gather a user search query The system shall gather a user search query The system shall gather each video’s title, link, and thumbnail The system shall gather each video’s title, link, and thumbnail The system shall do a thumbnail based image comparison to find similar videos The system shall do a thumbnail based image comparison to find similar videos The system shall display a report to the user showing video similarities The system shall display a report to the user showing video similarities

7. Project Management Plan  C# coding standard  Document standard Arial, 12 pt Arial, 12 pt Header with team name, group number, class prefix Header with team name, group number, class prefix Table of contents, lists of figures and tables, modification history Table of contents, lists of figures and tables, modification history New versions uploaded to website and saved on author’s pc New versions uploaded to website and saved on author’s pc

8. PMP Continued  Team Organization Democratic approach Democratic approach Documentation and coding done by all membersDocumentation and coding done by all members Chief programmer approach Chief programmer approach Brian Kelly (technical advisor)Brian Kelly (technical advisor)

9. PMP Continued  Software Life Cycle Waterfall Model Waterfall Model Feedback loops and documentationFeedback loops and documentation Faults can be detected earlyFaults can be detected early Development Maintenance Waterfall Life Cycle

10. PMP Continued  Configuration Management Version control handled through subversion application Version control handled through subversion application Darryl Parulan is the configuration analyst Darryl Parulan is the configuration analyst  Quality Assurance Source code checks Source code checks Logic, compilation, and runtime errorsLogic, compilation, and runtime errors Verification and validationVerification and validation Documentation checks Documentation checks Clarity, completeness, and correctnessClarity, completeness, and correctness

11. PERT Chart

12. Test Plan  OBJECTIVE To verify and ensure the basic functionalities of the software based on the clients requirements To verify and ensure the basic functionalities of the software based on the clients requirements Identify software defects early in the software's life cycle to save time, money, and company’s image. Identify software defects early in the software's life cycle to save time, money, and company’s image.  TEST ENVIRONMENT Code will be tested on our own pc utilizing the current Windows XP operating system Code will be tested on our own pc utilizing the current Windows XP operating system Testers will be the developers and fellow computer engineering students (beta testing) Testers will be the developers and fellow computer engineering students (beta testing)

13. Test Plan Continued  What should be tested? Reliability Reliability Ex. Chances of software crashEx. Chances of software crash Utility Utility Ex. Software being user friendlyEx. Software being user friendly  Test Cases Test cases to be performed during the first iteration of the software development Test cases to be performed during the first iteration of the software development

14. Test Plan Continued  STOPPING CRITERIA Allocated Resource – two testers to do rigorous system testing of the software during and after development Allocated Resource – two testers to do rigorous system testing of the software during and after development Bugs are prioritized from being a showstopper (application crashed!) to a low priority Bugs are prioritized from being a showstopper (application crashed!) to a low priority Bug fixing will take place after it has been reviewed and prioritized Bug fixing will take place after it has been reviewed and prioritized