1. 07/21/97 MOSS Project Introduction and Definition -Senior Project-

2. 07/21/97 MOSS Al Gillis – Project Leader, Editor Rhonda Schuyler – Lead Tester, Web Developer Keith Gorrell – Lead Analyst Ryan Riebeling – Lead Programmer Team Members

3. 07/21/97 MOSS Client Steve Klein Users CS Instructors CS Students Code Cop System Audience

4. 07/21/97 MOSS Current Problem Believe it or not, there are some students at SIU-E that do not write their own code for programming assignments. Instructors need a way to check multiple sections of programming assignments for similarity. Doing this by hand takes way too long. There exists an application hosted by U.C. at Berkeley called MOSS to compare programs, but the process of submitting them is currently very inconvenient.

5. 07/21/97 MOSS Current MOSS Problems Command line Perl script for UNIX. No GUI or MOSS I/O automation. Not integrated with student drop boxes. 2 week lifetime MOSS reports.

6. 07/21/97 MOSS The Solution The Code Cop System Easy to use GUI Automated MOSS I/O Integrated with current student drop boxes Integrated with instructor class database Web hosted functionality Local archive of MOSS reports

7. 07/21/97 MOSS 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 MOSS / Code Cop System Overview

8. 07/21/97 MOSS Based on the client’s requirements for accessibility, group skills, and the availability of development tools, we chose a Windows NT platform running Internet Information Server.

9. 07/21/97 MOSS Based on the client’s requirements for accessibility, group skills, and the availability of development tools, we chose a Windows NT platform running Internet Information Server. Based on this platform choice we needed to see what we could or could not do in terms of talking to MOSS.

10. 07/21/97 MOSS Create attachment from file groups made from user selections and encode them Send email with attachment Retrieve the email which contains URL pointing to results Extract results from URL Populate MOSS statistical results into database RISK MOSS Automated I/O Risk Mitigation Effort

11. 07/21/97 MOSS The Risk Mitigation Effort has: Allowed us to make certain that we will be able to send/receive information to/from MOSS based on our platform choice

12. 07/21/97 MOSS The Risk Mitigation Effort has: Allowed us to make certain that we will be able to send/receive information to/from MOSS based on our platform choice Allowed us to define our approach for designing the system

13. 07/21/97 MOSS http://moss.cs.berkeley.edu/~moss/results/675443542

14. 07/21/97 MOSS http://moss.cs.berkeley.edu/~moss/results/675443542 Currently to View Results Need to manually click the URL http://moss.cs.berkeley.edu/~moss/results/675443542

15. 07/21/97 MOSS http://moss.cs.berkeley.edu/~moss/results/675443542 Currently to View Results Need to manually click the URL http://moss.cs.berkeley.edu/~moss/results/675443542

16. 07/21/97 MOSS http://moss.cs.berkeley.edu/~moss/results/675443542 View Results within 14 days Currently to View Results

17. 07/21/97 MOSS Analysis  Talking to Client  Reviewing data sent back by MOSS  Constant review with Client

18. 07/21/97 MOSS Three interfaces  Instructor  Admin  Student

19. 07/21/97 MOSS Instructors  Can add other instructors but can’t edit or delete them  Can create, edit, or delete courses  Can add, edit or delete students from courses  Can switch students between sections  Can send programs from single or multiple sections to MOSS  Can specify base file to be sent with programs

20. 07/21/97 MOSS  Can extend deadlines for students to submit programs  Can specify programming language of programs  Can send programs to special directory for grader Instructors (cont)  Can view results of analysis including statistical information  Can view up to five versions of programs turned in by students

21. 07/21/97 MOSS Instructors (cont)  Can view status of turned in assignments in a table format  Can archive students at the end of the semester in the database  Can delete students from database

22. 07/21/97 MOSS Administrator  Has access to the entire system  Can Add, Edit, Delete Instructors/Students Students  Can submit their programs via the web interface

23. 07/21/97 MOSS Code Cop System Model:

24. 07/21/97 MOSS Actors:

25. 07/21/97 MOSS Sample Scenario: Scenario nameInstructorAddsAssignment Participating Actor InstancesTerry: Teacher Flow of events1. Terry assigned a program to her third section of cs150 for the spring semester of 2001 that is due in one week. She activates the “Add Assignment” function of the Code Cop system. 2. Terry enters the assignment name and the due date. 3. Terry receives a message that acknowledges that the assignment has been successfully added.

26. 07/21/97 MOSS Sample Scenario: Scenario nameInstructorAddsInstructor Participating Actor InstancesTerry, Joe: Teacher Flow of events1. Terry is responsible for the new instructor, Joe. She activates the “Add Instructor” function of the Code Cop system. 2. Terry enters “Joe” as the instructor’s name. 3. Terry receives a message that acknowledges that Joe has been successfully added as an instructor.

27. 07/21/97 MOSS Code Cop System Use Case Diagram: