1. MOSS Final Presentation -Senior Project-

2. MOSS Presentation Agenda Project Definition Requirements Analysis System Design Project Plan Code Cop Screen Shots Questions / Answers

3. MOSS Team Members Rhonda Schuyler – Web Developer, Lead Tester Ryan Riebeling – Lead Programmer Keith Gorrell – Lead Analyst Al Gillis – Project Coordinator, Editor

4. MOSS Organizational Plan Upper Management Bryon Ehlmann Project Coordinator Al Gillis Lead Programmer Ryan Riebeling Lead Analyst Keith Gorrell Web Dev / Tester Rhonda Schuyler Client Steve Klien

5. MOSS Current SIU Problem Believe it or not, there are some CS students at SIU that do NOT code their own programming assignments. Instructors need a way to check multiple programming assignments for similarity. Doing this by hand takes way too long. There exists an application hosted by U.C. at Berkeley called MOSS (Measure Of Software Similarity) that compares programs, but currently, the process of requesting MOSS services is not convenient.

6. MOSS Current MOSS Problems Command line interface to run a Perl script for UNIX. Not integrated with SIU student drop boxes. No GUI or MOSS I/O automation. 2 week lifetime of MOSS reports. No locality of MOSS reports.

7. MOSS Requirements Analysis

8. MOSS Requirements Analysis Client interview sessions. Perl script analysis and functional decomposition. Prototype of MOSS service requests. Subsequent review of MOSS reports. Constant review with client.

9. MOSS http://moss.cs.berkeley.edu/~moss/results/675443542 View Results within 14 days Current View of MOSS Reports

10. MOSS RISK Create attachments from file groups made from user selections. Automatically send MOSS requests via email with attachments. Automatically retrieve, open, and parse MOSS reports. Automatically web tunnel into MOSS reports URL. Automatically store MOSS reports to local web page. MOSS Risk Mitigation Items

11. MOSS Our Solution The Code Cop System requirements: Easy to use GUI. Automated MOSS I/O. Integrate student drop boxes into the system. Integrate with instructor class spreadsheets. Thin client / 100% Web hosted functionality. Local archive of MOSS reports.

12. MOSS Development Platform Windows 2000 because: Client requirements. Our groups programming skill set. Readily available development tools. SIU Web pages are hosted on MS IIS.

13. MOSS Functional Requirements Instructors: Can create, edit, or delete courses. Can add, edit, or delete students from courses. Can switch students between sections. Can bundle MOSS requests from multiple sections. Can specify base files to be sent to MOSS. Local archive of MOSS reports. MOSS reports posted to Web site. Student uploads are filename constrained. Set homework deadline.

14. MOSS Functional Requirements Administrator: Can add, edit, or delete users. Can add, edit, or delete courses. Student: Can submit their programs via a Web interface. Can view the status of their directory.

15. MOSS MOSS Report Use Case

16. MOSS Administrator Use Case

17. MOSS Student Use Case

18. E-R Model

19. Assignment NameAssignmentIDAssignmentKeyDueDateClassKeyInstructorKey Class ClassIDClassKeyYearSemesterSectionNumberCourseKeyInstructorKey Course CourseIDNameCourseKey DropBox NameLocationBoxKeyBoxIDInstructorKey Files FileIDFileKeyNameIsBaseStudentKeyAssignmentKeyBoxKey Instructor UserNameInstructorKeyLastNameFirstNamePasswordHasResultPrivilege PlacedIn BoxKeyFileKey Program Results InstructorKeyClassKeyLocationIsNewResultsID Student StudentKeyLastNameFirstNamePasswordStudentIDPrivilegeUserName Takes StudentKeyClassKey UploadsTo UploadTimeUploadDateStudentKeyBoxKeyStudentIDBoxIDAssignmentKeyFileKey

20. MOSS System Design

21. MOSS System Overview MOSS Server System 1. MOSS Application 2. Email Server 3. Email Client SIU-E Code Cop System 1. SIU-E Code Cop Application 2. FTP Drop Box 3. WEB Server (IIS) 4. Database (Access2000) 5. Zip, Tar, UUEncode, UUDecode 6. Email Client 7. Email Server From Home 1. IE5 From School 1. IE5 INTERNET

22. MOSS Deployment Modularity Internet MS Internet Information Server Mail Server Storage SIU-E Code Cop Computer SIU-E Users SIU-E Student Drop Box Element Functions Interface Storage CC Login.ASP JVM SQL I/O MS Drive Mapping MS Access DB ZIP Engine JET DB Engine Code Cop Application Mail Server UUE Mail Client MOSS Application Storage MS Internet Information Server MS Drive Mapping FTP Drop Box Login MOSS StorageIE5 / Netscape Mail Client File I/O

23. User Browser Communication Subsystem Functional Interface Send / Receive MOSS Services Ethernet Code Cop System Physical Interface MOSS Email Services Client/Server Web Services HTTP Tunnel DB Services SQL/Access File I/O Services Drop Box Runtime Services VBS / COM / JVM / DLL Communication Subsystem Student Services DB Admin Services Instructor Services File I/O Services Functional Interface Ethernet Physical Interface Communication Subsystem Service Requests Report Notification HTTP Results MOSS Interface Diagram

24. MOSS Code Cop User Interfaces Four Main User Interfaces 1.Login Page 2.Instructor Menu 3.Student Menu 4.Administrator Menu

25. Web Site Organization MOSS

26. Administrator

27. Administrator

28. Instructor

29. Instructor

30. Student

31. Student

32. Design Logic Between Modules Session Variables in ASP. Querystrings used to pass information from one page to another.

33. MOSS Project Plan

34. MOSS Hardware/Languages 1.Hardware Decisions: Windows 2000 dedicated server 2.Languages: ASP, HTML, SQL, Visual Basic, Java

35. MOSS Implementation Requirements Resources: Code Cop will require space on the CSFS2 server. Must have Internet access. Requires an email account to send/receive info. Microsoft Access database. Microsoft Internet Information Server.

36. MOSS Development Tools / Software Microsoft Visual Studio 6.0 Enterprise Edition Third Party Components: ASPMail 4.0 – used for sending email messages using SMTP JMail – used for receiving email messages using POP3

37. MOSS Test Plan The Lead Tester is responsible for developing a system of testing which includes: Lo-fi and Hi-fi prototyping at the early stages of development. Making sure that all features agreed upon are in the application. Debugging and Testing of all Routines.

38. MOSS Test Plan (cont.) Documentation will include: Why the test is being conducted How the test will be conducted Where the test will be conducted When the test will be conducted Who will conduct the test Every test will be documented

39. MOSS Deployment Plan Installation on CS Dept. Windows 2000 Server Entire CodeCop application will be in one place Training Client and other instructors will need to learn the UI Student Web Interface (optional per Instructor)

40. MOSS Deployment Plan (cont.) Operation (continued) CodeCop System will need very little maintenance Requires server to be up and running Requires server to maintain a connection to network

41. MOSS Code Cop Project Lifecycle Contract signed by client CS425 final presentation CS499 final presentation

42. Everyone Keith Alan Ryan Everyone Rhonda

44. Requirements Met? All user interfaces Web based Student uploads filename controlled Student uploads are time constrained No student project build capability from drop box Instructor override of all student constraints Instructor / Administrator control of all user accounts Windows based MOSS interface MOSS bundling of multiple class sections Automatic background processing of MOSS transactions Permanent / local archive of all MOSS reports MOSS

45. Code Cop Screen Shots

52. MOSS Questions / Answers