1. Ashley Montebello – CprE Katie Githens – SE Wayne Rowcliffe – SE Advisor/Client: Akhilesh Tyagi

2. Problem Statement The ECpE department currently manually sends out emails containing review forms to graduate students and faculty to evaluate graduate student progress. This process is not very efficient and requires constant interaction in order to complete the review process between students, faculty, and the graduate committee.

3. Need Statement The ECpE department would like an automated system to complete gradate student reviews. Updates to the process will include: Automating the email process for students, faculty, and the graduate committee. Automating the user creation process by creating accounts from the College of Engineering database. Storing data to a database will make the review process much easier for the graduate committee (easily sort students and their progress for review)

4. System Description We have received the Computer Science department’s GProgress system as a starting point for our system Adapt current Computer Science GProgress system to fit Electrical & Computer Engineering department requirements General changes to forms to fit ECpE needs Replace current login process with IAState login system Create user accounts from College of Engineering database instead of manually Make changes to user interface to make system more user-friendly

5. Conceptual Diagram

6. Operating Environment Front-End Environment Access the system through a supported web browser Back-End Environment Apache Tomcat web server running Java SQL database

7. Non-Functional Requirements Security Use the IAState login system for user authentication Extensibility Integrate with College of Engineering graduate student database

8. Functional Requirements All Users Update account information Must login to the system to gain access to features Admin Add, edit, search and delete accounts, courses, reporting periods and rating scales Students Edit and submit evaluation Edit background information

9. Functional Requirements Faculty/Professors Edit and submit advisee rating View their students’ evaluations by reporting period Graduate Committee View student and professor ratings for each student

10. Assumptions & Technology Considerations Received code for GProgress provides a fully functional system Users have a web browser that can render the web pages Users know how to use the web browser to navigate pages Users are familiar with completing and submitting forms

11. Deliverables SQL Database to store necessary information JSP pages, Java classes needed to run the website User guides will be made part of the website System documentation

12. Tasks & Schedule

13. Risks & Mitigations RiskMitigation If GProgress system and code is not well documented it may take more time than expected to understand the code. 1)Get system documentation and code as early as possible 2)Begin reviewing code Fall semester so we can start development right away in the spring Depending on system design, it may be difficult to integrate with desired systems (IAState for login, CoE database) Do more research in this area to find alternatives. Worst case scenario: use system as it exists currently.

14. Cost Estimate Software – FREE (open source) Hours (400): $8000

15. Software Apache Tomcat 5.0 or above JRE 1.5.0 or above MySQL 5.1 or above

16. System Design Java Server Page (JSP) “View” component Apache Struts 1.2 Used to help keep MVC structure Hibernate 3.0 For mapping Java objects to the database

17. Apache Struts JSP serves as the “View” Controller Servlet is the “Controller” Controller manages communication between actions and action forms through struts-config.xml file Action Forms and ActionForm Beans are the “Model”

18. Hibernate Object-relation mapping (ORM) solution that maps Java objects to relational databases JavaBean classes mapped to corresponding table using XML mapping file hibernate.cfg.xml file is used to configure Hibernate

19. User Interface Specification Four different views Administrator Faculty Student Graduate Committee Depending on user’s permissions they will have access to various options in the system

20. User Login

21. New User Login

22. Admin Home Page

23. New Admin Home Page

24. Student Evaluation

25. New Student Evaluation

26. Testing Plan Login/Logout Make sure login uses the engineering servers correctly Make sure once logged in, a user has the proper privileges Make sure logging out clears the user’s information Form Submission Ensure that forms contain the desired information Ensure that the forms are saved to the server correctly Ensure that the user can see the relevant forms

27. Testing Plan Email Notifications Ensure that email notifications are sent when evaluation period begins Ensure that faculty are emailed when students submit their self-evaluation Ensure that the graduate committee is emailed when faculty have finished their evaluations

28. Testing Plan Security Test that private data requires the proper login/password to access Test against SQL injection Load Testing Test that the system can hold up to the expected load

29. Current Status Received source code from Computer Science department Working on understanding the given code to begin making changes to forms to fit ECpE department needs

30. Questions?