1. TestFiles Life Cycle Architecture Chris Byszeski Ooi Hsu Han Amir Kouretchian Sachin Pradhan Quang Tran Peter Turschmid Nick Walker

2. Introduction – What is TestFiles? A web application targeted towards students Share and distribute old tests, quizzes, notes and homework assignments Easy access through intelligent searching over a variety of metadata: Class, title, type of test, instructor, etc Self-sustaining: provides incentive to contribute Not a social networking site, but will include a variety of creative personalized features

3. Functional Specification

4. Feature Set User account creation, authentication/login Personalized welcome screen for each user Search (basic & advanced) & Viewing/downloading testfiles Upload Rating of testfiles

5. Feature Set Dynamically generated document page Favorite users management (favorite uploaders) Quota system Uploader profile page Administrator/Maintenance Page Group control/test files access permissions Notification of new testfiles

6. Welcome Page Primary page, “feature gateway” Contains Advanced Search area List of recent downloads (for rating) Recommended testfiles Favorite user list, with recent uploads Most wanted testfiles Link to profile/settings editor Link to help page

7. Site Navigation Graph

8. Sample Use Case GoalTo download old midterms for a certain class Primary ActorThe user who is seeking for the old midterm PreconditionThe user has an account and is logged in. Successful PostconditionThe user is able to download/view the test, and rate it accordingly or get a notification that the user is restricted from downloading the test. Unsuccessful PostconditionNo relevant testfiles is displayed when there are relevant testfiles TriggerThe user searched for the testfiles Main Success Scenario Failure Scenario The user enters username and password The system verifies and logs the user in A personalized welcome screen is displayed User enters search criterion in search area of welcome page A list of testfiles matching the criterion are displayed along with its metadata. All restricted testfiles that the user does not have permission to does not display in search result. The user clicks on one of the search results The user can view/download the testfile, rate the testfile, flag the testfile as inappropriate, or add a comment about the testfile User authentication fails No relevant testfiles are displayed The user is restricted from downloading the testfile when the user is allowed to

9. System Architecture

10. Architecture Overview Microsoft IIS Server Microsoft SQL Server ASP.NET C# Basic, well known web application setup from databases class – standard in industry

11. Database Schema

12. Evolutionary Changes Database administrators use software for multiple colleges More advanced commenting on test Copyright issues and test file access control

13. Team Structure, Schedule, Tasks and Risk Assessment

14. Team Structure Division by proficiency ASP Frontend / UI: Nick, Peter Server Backend: Hsu Han Database Design / Data Management: Amir, Sachin, Chris Research of.NET Implementation Specifics: Quang

15. Schedule and Milestones Two Primary Milestones: Beta (May 9) Upload/Download, basic search User login, simple but functional user interface Final (May 30) Full ranking system, user account creation Administrator mode, file discussion system Favorite uploaders, full/advanced search Full welcome screen, finalized user interface

16. Risk Assessment Top Five Risks Implementation Difficulties Tool Setup and Use Feature Creep Schedule Conflicts Database Design Other Concerns Adherence to Project Methodology “Senioritis”

17. Testing and Documentation

18. Testing Strategy Two-prong approach: User testing Code testing

19. User Testing Have users test every build Note bugs and functional inadequacies Ensures stable progress Ensures UI is intuitive and easy to use Ensures proper functionality is being provided

20. Code Testing Unit testing EVERY DAY Do not leave to the last minute…write unit tests for every function Database testing Hard-code data and run queries to ensure correct data is being stored/returned

21. Builds and Documentation Nightly builds Ensure stable and promote clean and efficient code writing Code documentation DAILY Promotes clean and maintainable code User documentation After all features are implemented Use user-feedback during user testing