Programming in C#

1. Programming in C# Product Presentation Group 6

2. Name of the Presenter • Yu Gao • Ryan Orth • Kenta Sugimoto • Ayan Chowdhury

3. Navigation Yu Gao

4. Testing Kenta Sugimoto

5. Requirements • Internet Explorer 4.0+ or Netscape 6.0+ • Internet Explorer6.0+ or Netscape 6.0+ • Java Runtime Environment 1.4.0 • 800 x 600 and 1024 x 768 resolution

6. Testing Plan • Target: Web contents (textual) • Tester: Research Group • Test on: • Spelling & Grammar • Amount allocation of contents per one page • Check whether quiz answer is correct • Chapter independency • Definition check for Glossary

7. Testing Plan • Testing Result: • Several but minor spelling and grammatical mistakes

8. Testing Plan • Target: Power point files • Tester: Power Point Group • Test on: • Spelling Error • Grammatical Error • Table value missing • Layout Review • Color Consistency Check • Font Resizing

9. Testing Plan • Testing Result: • Some table values were missing • Some table representation are changed

10. Testing Plan • Target: Web Design • Unit: Web design group • Test on: • Link Coverage • Xenu's Link Sleuth (TM) • HTML Validation • Online html validation • Browser (Loading Applet) • IE 6.0 and mozilla 1.2.1 • XML, XSD, XSLT well-formed, validation check • Xml spy 4.4 • PHP • Try & error

11. Testing Plan • Testing Result: • Link Coverage • No broken links so far • HTML Validation • Several enterprise specific tag error • Browser (Loading Applet) • Works fine for both IE 6.0 and mozilla • XML well-formed, validation check • Xml are both well-formed and validated • PHP • No fatal error

12. Testing Plan • Threading Applet • White-box Testing • Too few inputs to test • Check for Unused function and only-once used function • Black Box Testing • Pressing button by clicking mouse • Peer’s Pressure by posting on I-help • Feedback comments form classmates

13. Testing Plan • Testing Result: • White-box Testing • No unused function • Black Box Testing • Properly functioning

14. Testing Plan • Quiz Applet • White-box Testing • Too few inputs to test • Check for Unused function and only-once used function • Black Box Testing • Check correctness on quiz answer and score • Peer’s Pressure by posting on I-help • Feed back comments from classmates

15. Testing Plan • Testing Result: • White-box Testing • No unused function • Black Box Testing • quiz answer and score are correct

16. Testing Plan • Target: Documentation • Unit: Documentation group • Test on: • Spelling & Grammar

17. Testing Plan • Testing Result: • Minor grammatical and spelling errors

18. Project Management Ayan Chowdhury

19. Projects RisksImpact 1: Catastrophic 2: Critical 3: Marginal 4: Negligible

20. Example of group Communication We communicate with our group members by: • I-Help • e-mail • phone I-Help Metrics:

21. Project Risks cont’Impact 1: Catastrophic 2: Critical 3: Marginal 4: Negligible

22. Project Tasks Definition T13. Writing XML schema T14. Writing XSLT T15. Writing XML Document T16. Applet Implementation T16.1. Threading Applet T16.2. Byte Code Applet T16.3. Remote Access Applet T16.4. Quiz Applet T17. Integrate Website Content T18. Complete Project Testing Milestone 3 Product Presentation

23. Updated Task Network T4 T5 T16.2 T10.1 T16 T19 T10 T20 T10.2 T16.1 T16.3 T8 T1 T3 T11.3 T16.4 T23 T13 T21 T12 T11 T2 T7 T14 T17 T11.2 T6 T9 T11.1 T22 T24 T15 T18 End M1 M2 M3

24. Current Task Network 2nd P R E S E N T A T I O N T16.2 T16.3 Final P R E S E N T A T I O N T17 T16 T16.1 T16.4 T18 Critical Path T13 T14 T15

25. Project Tasks Definition T19. Add more Website Content T20. Add one new Applet T21. Complete Project Documentation T22. Review Tutorial after getting Feedback T23. Final Integration T24. Final Testing Submit Final Project

28. Time Table

29. Questions ???