1. Survey Management System Phase Two Presentation by Team S1

2. Introduction The Survey Management System (SMS) is a java-based web application requested by ST Engineering. Its primary function is to enable users to create online surveys. The links to the surveys will be send via email to participants. Participants will respond to the survey. Users will be able to view and analyze the survey results.

3. Key design considerations Programming language is java. Database is MSSQL. Single-sign-on to Netweaver portal but no interface to SAP R3 systems. Interface with iReports, a free, open source report designer. Part of the system requires a small windows service application to send the survey emails.

4. System Diagram SMS EIP DBEmail Window Service Web Application iReport

5. Project Schedule (1) Phase One Tasks Completed

6. Project Schedule (2) Phase Two Tasks Completed

7. Project Schedule (3) Remaining Tasks

8. Management Issues ProblemResolution/Migration Busy schedule and demanding time commitment from team members makes it difficult to get everyone to met. Schedule meeting through online conference. Minutes of meetings that contains project decision and task assignment send to all team members. Limited manpower resources with a small 5 man team. Tightly monitor and control task progress. Each critical task has two team members assigned to ensure there is a backup in the event one of the members are unavailable.

9. Key Use Case Analysis 1: Create Survey (1) Create survey Create set Create question Create answers Is the use case which allows editors to create surveys. Is the primary functionality of the system. Survey Set Question Answer Question Answer Question Answer Set Question Answer Question Answer Question Answer

10. Key Use Case Analysis 1: Create Survey (2) Home Page Survey Management Page List Surveys Delete Surveys Survey Modification Page / Set Management Page Create Survey Modify Survey List Sets Delete Sets Set Modification Page / Question Management Page Create Set Modify Set List, Delete, Create, Modify Question List, Delete, Create, Modify Answer

11. Key Use Case Analysis 1: Create Survey (3)

12. Key Use Case Analysis 1: Create Survey (4)

13. Key Use Case Analysis 1: Create Survey (5)

14. Key Use Case Analysis 1: Create Survey (6)

15. Key Use Case Analysis 2: View Survey Results(1) View survey results Is also one of the essential functionality of the system. Basic tabulated result of all how many participants chose which answer for which question is shown. Has the function to be exported to MS Excel. No.QuestionAnswer 1Answer 2Answer 3Answer 4 1What is your favorite Drink? MiloTeaCoffeeMilk 5483 2What is your favorite movie? Toy StoryLord of the Rings: Return… 10

16. Key Use Case Analysis 2: View Survey Results(2)

17. 3 Layered Architecture Presentation Layer Business Layer Data Access Layer

20. Prototype IReport SSO to Ticket JSF EJB JPA Hibernate

21. Reason for Prototyping (1) IReport Easy to Design Report. Free tool. Third Party Component.

22. Reason for Prototyping (2) Single Sign On Requirement to enable Single Sign On for logged in user into Survey Management System.

23. Reason for Prototyping (3) JSF EJB JPA Hibernate To familiarize the team about the framework. To prove the feasibility of the proposed architecture.

24. Prototype on JSF EJB JPA Hibernate Company Prototype Create Company Delete Company Update Company View Company List

25. Prototype on IReport IReport is a Tool from Jaspersoft. SMS uses IReport tool for reporting. Report data is loaded through JNDI Datasource. Company Summary Report Prototype.

26. Prototype on SSO (1) ST Engineering uses SAP Netweaver as its internet portal. Single-sign-on to SAP Netweaver can be implemented using the SAP Logon Ticket. Reason to prototype is to test all external systems.

27. Prototype on SSO (2) UserEIP SMS 1. logs on to Logo n Ticke t 2. creates 3. clicks on link to SMS in 4. passes Logon Ticket to 5.decrypts 6. grants rights to