The document outlines plans for launching the Model Community (MC1 and MC2), including key features, critical components, resources, and a quality assurance testing plan. MC1 will be a closed informational section, while MC2 will include additional social networking features and be open to the public. Critical components include the model manager, payment system, QuickBooks integration, and model community design. Testing will involve test cases, performance testing, exception handling, database optimization, backups, staging/production environments, and internal user testing. The estimated completion date is May 2nd if development starts on March 3rd.

1. IT Plan to Launch The Network

4. Critical Components Overview Component Hours Cost Resources Status Model Manager 70 $2,415 India, Darion Caio, Kevin Morland Pending Payment System 5 $250 Josh Hendrick Complete Quickbooks Integration 20 $1,200 Edmund Leung Pending Model Community x $1,000 + $399/mo. Invision Power In-Progress Model Community Design & Markup 50 $2,125 Darion Caio Complete Code Optimization & New Features 480 $2,500 India In-Progress QA & Performance Testing 3 weeks $3,000 Josh Hendrick, Will Truong, Network Staff In-Progress Bug Fixes 3 weeks $2,500 India Complete Hosting x x Amazon AWS ( See Next Page ) Pending Hosting Management Service x x Cloud Management Service ( See Next Page) Pending Total 410 $12,340

5. Resources Overview Resource Hours Per Week Available Skill Set India 140 JAVA, mySQL, HTML, CSS Kevin Morland 20 Flash, Actionscript, PHP, mySQL, Youtube API Josh Hendrick 30 PHP, mySQL, Software Testing Darion Caio 30 Design Will Truong 30 Software Testing / Quality Assurance Trevor Caesar 60 PM, Design, HTML, CSS, CMS Integration

6. Critical Components QA Testing Plan 1.) Test cases and Traceability Matrix: Plan out all test cases. ( 1 Week ) All positive use cases for Agency, Client, Super Admin, and Director Accounts have been written. Entire spectrum of use cases will be approached as development is underway. 2.) Performance Testing: Setup and run an automated tool for load and performance testing at various stress levels (10 users, 100 users, 1000 users, etc). Need to specifically decide on tools we will use. 3.) Strong Exception Handling: Prevention of page crashing, Tomcat errors, and a custom 404 error page so that all users will not have an interrupted experience. 4.) DB Optimization & MySQL Optimization: According to Josh - David Reckles has a great resource for this. 5.) DB Backup: A) Run a daily script that makes a .SQL dump of the database for disaster recovery. B) Currently we have DB settings to create a mirror copy. This mirror is a failsafe which will allow us to automatically transition to another DB in the event of a cash. 6.) Staging & Production Environment: Staging Environment: When we make any changes or bring new features to the site we will continue to test on the staging server. This copy is hosted on the same environment with a copy of the live DB. Any email interactivity to the user base and payment transactions will be disabled for this environment to aid in testing without interrupting business operations or user experience. Production Environment: Continuing the use of SVN – as post launch development tasks are completed we will be able to seamlessly update only files which have been modified. 7.) Internal Testing: A controlled group of users running different browsers on different operating systems will go through all of the use cases and will record their findings using a bug tracking software suite called FogBugz.

7. Estimate Completion Plan Currently, with all development tasks frozen – we are looking at 400+ hours of development including a 3 week Quality Assurance cycle. May 2 nd is the current target date. However, if we are planning on accepting payments by mid April then we need to plan accordingly. All development tasks will have to be completed and tested by this April date in order for us to begin accepting payments. Some items such as the model community and Quick Books Integration can be in development as we begin accepting payments. If development where to start on Wednesday March 3 rd – that would give us 29 days of development and 15 days for QA. Skillset Estimated Hours Timeline JAVA & mySQL 120 3 weeks Flash / Actionscript 25 3 weeks Design 45 3 weeks HTML & CSS 35 1 week Quality Assurance 75 3 weeks Other 60 2 weeks