1. Pear Software http://oraserv.cs.siena.edu/~perm_pear/ e-SATA (The Electronic Spreadsheet Automated Teaching Assistant) Requirements Specification

2. 10/27/2006Requirements Specification - Pear Software2 Welcome Dr. Scott Hunter Professor of Computer Science Siena College Department of Computer Science Ms. Jami Cotler Professor of Computer Science Siena College Department of Computer Science

3. 10/27/2006Requirements Specification - Pear Software3 Team Members Matt Restivo.........................Team Leader James Rocco.......................Project Manager Colin Cubinski......................Librarian Justin Valentini.....................Webmaster Dan Nakhla..........................Systems Administrator

4. 10/27/2006Requirements Specification - Pear Software4 Agenda Introduction – Matt Restivo Use Cases – James Rocco Data Flow Diagrams – James Rocco Functional Requirements – Colin Cubinski Prototype Screens – Dan Nakhla Going Forward... – Matt Restivo

5. 10/27/2006Requirements Specification - Pear Software5 Review of Problem Clients need easier way of grading Excel spreadsheets. Looking for automatic feedback of graded files. Ability to manage a students grades and attendance.

6. 10/27/2006Requirements Specification - Pear Software6 Requirements Specification A highly detailed, client-oriented specification of criteria that an application must meet. Defines the required data structures. Details functional and non-functional requirements.

7. 10/27/2006Requirements Specification - Pear Software7 Agenda Introduction – Matt Restivo Use Cases – James Rocco Data Flow Diagrams – James Rocco Functional Requirements – Colin Cubinski Prototype Screens – Dan Nakhla Going Forward... – Matt Restivo

8. 10/27/2006Requirements Specification - Pear Software8 Use Cases Four types of users: 1.Student 2.Lab Instructor 3.Lecture Instructor 4.Course Administrator

9. 10/27/2006Requirements Specification - Pear Software9 Agenda Introduction – Matt Restivo Use Cases – James Rocco Data Flow Diagrams – James Rocco Functional Requirements – Colin Cubinski Prototype Screens – Dan Nakhla Going Forward... – Matt Restivo

10. 10/27/2006Requirements Specification - Pear Software10 Data Flow Diagram A graphical representation of the “flow” of data through an information system. It illustrates the processes, data stores, external entities, and data flows in a business or other system and the relationships between these things.

11. 10/27/2006Requirements Specification - Pear Software11 Data Flow Diagram Key

12. 10/27/2006Requirements Specification - Pear Software12 Context Free Diagram

13. 10/27/2006Requirements Specification - Pear Software13 Level 1

14. 10/27/2006Requirements Specification - Pear Software14 Level 2

15. 10/27/2006Requirements Specification - Pear Software15 Level 3 – Web Interface

16. 10/27/2006Requirements Specification - Pear Software16 Level 3 – Grading System

17. 10/27/2006Requirements Specification - Pear Software17 Agenda Introduction – Matt Restivo Use Cases – James Rocco Data Flow Diagrams – James Rocco Functional Requirements – Colin Cubinski Prototype Screens – Dan Nakhla Going Forward... – Matt Restivo

18. 10/27/2006Requirements Specification - Pear Software18 Functional Requirements Student: –Make submissions of pre-lab and lab files. –Resubmit pre-lab after feedback is received. –Feedback screen to provide comments on mistakes. –View their lab grades. –Allow missed labs to be made up. –Allow user to retrieve a lost password.

19. 10/27/2006Requirements Specification - Pear Software19 Functional Requirements Lab Instructor: –View profile of any student in a lab session. –Edit the students’ grades. –Override graded mistakes. –Get feedback on most frequent mistakes. –View feedback from other lab sessions. –Keep attendance using the application. –Ability to export grades as a spreadsheet.

20. 10/27/2006Requirements Specification - Pear Software20 Functional Requirements Lecture Instructor: –View their students’ grades. –View statistics and feedback from all lab sessions. Course Administrator: –View all grades from all lab sections. –Upload answer keys for automated grading. –Ability to export grades as a spreadsheet.

21. 10/27/2006Requirements Specification - Pear Software21 Non Functional Requirments User Friendly Interface Easy to read drop downs for new students Fast Grading Efficiently programmed

22. 10/27/2006Requirements Specification - Pear Software22 Agenda Introduction – Matt Restivo Use Cases – James Rocco Data Flow Diagrams – James Rocco Functional Requirements – Colin Cubinski Prototype Screens – Dan Nakhla Going Forward... – Matt Restivo

23. 10/27/2006Requirements Specification - Pear Software23 Login Prototype Screen

24. 10/27/2006Requirements Specification - Pear Software24 Forget Password

25. 10/27/2006Requirements Specification - Pear Software25 New User

26. 10/27/2006Requirements Specification - Pear Software26 Student – View Labs

27. 10/27/2006Requirements Specification - Pear Software27 Student – View Pre-Labs

28. 10/27/2006Requirements Specification - Pear Software28 Student – Submit Labs

29. 10/27/2006Requirements Specification - Pear Software29 Student – Feedback

30. 10/27/2006Requirements Specification - Pear Software30 Possible Feedback Error

31. 10/27/2006Requirements Specification - Pear Software31 Lab Instructor – Grading

32. 10/27/2006Requirements Specification - Pear Software32 Lab Instructor – Feedback

33. 10/27/2006Requirements Specification - Pear Software33 Possible Feedback Error

34. 10/27/2006Requirements Specification - Pear Software34 Lecture Instructor – Grading

35. 10/27/2006Requirements Specification - Pear Software35 Course Admin – Grading

36. 10/27/2006Requirements Specification - Pear Software36 Course Admin – Feedback

37. 10/27/2006Requirements Specification - Pear Software37 Course Admin - Answer Key

38. 10/27/2006Requirements Specification - Pear Software38 Agenda Introduction – Matt Restivo Use Cases – James Rocco Data Flow Diagrams – James Rocco Functional Requirements – Colin Cubinski Prototype Screens – Dan Nakhla Going Forward... – Matt Restivo

39. 10/27/2006Requirements Specification - Pear Software39 Where we stand…

40. 10/27/2006Requirements Specification - Pear Software40 Going Forward... What’s next? –Preliminary Design: Document: November 27, 2006 Presentation: November 29, 2006 Any questions?

41. 10/27/2006Requirements Specification - Pear Software41 Going Forward... What’s next? –Preliminary Design: Document: November 27, 2006 Presentation: November 29, 2006 Any questions?

42. 10/27/2006Requirements Specification - Pear Software42 Going Forward... What’s next? –Preliminary Design: Document: November 27, 2006 Presentation: November 29, 2006 Any questions?

43. 10/27/2006Requirements Specification - Pear Software43 Going Forward... What’s next? –Preliminary Design: Document: November 27, 2006 Presentation: November 29, 2006 Any questions?

44. 10/27/2006Requirements Specification - Pear Software44 Going Forward... What’s next? –Preliminary Design: Document: November 27, 2006 Presentation: November 29, 2006 Any questions?

45. 10/27/2006Requirements Specification - Pear Software45 Course Admin – Extra