The assessments and accommodations designed for Phases II and III of this study will be conducted through a computerized system. The computer system for Phase II will input information from schools, teachers and students in order to assign appropriate accommodations to students. The system starts by collecting student background information through a class roster that is sent to teachers electronically. The background information includes student state test score on English language arts, mathematics, English language proficiency (CELDT) and ELL status, the test administration starts with a short reading test called TIMER. The system will score TIMER test and based on the student performance on this test and other pertinent student background information, assigns students to different accommodation conditions.

Below is more information regarding technical aspect of the system.

The first step in a proper system design is to determine the general number of pages and the how the system will flow. The initial first round of the UI and UX was also started here. A sitemap was delivered to the research team and was subsequently approved. 

Once the sitemap was approved there was further refinement to the UI and UX. Each page was laid out and its content was determined with emphasis on being user friendly and functional. A wireframe was delivered and approved. 

Once the number of pages (site map), content (wireframe), UI/UX (wireframe) was approved work began on the graphic component on every page. An emphasis was put on sleek and modern look while making sure the design was responsive to different screen sizes as well as being graphic friendly to older computers. An important aspect in this stage is to ensure proper functionality given school computer monitors have lower resolutions, smaller monitors, and older processors. This can present a problem for sites with any sort of content where the design can get in the way of functionality i.e., content is buried under large and unresponsive designs. 

Server Setup
We have also setup the development servers. These are the servers that initial testing will be on. To keep costs to a minimum we have used machines with lower specifications to start development. In this stage, only the programming and testing team will have access to the servers. Our hardware is monitored 24/7 and will have almost 100% uptime so there is little concern for machine error or data loss. 

Database Setup
The system’s data schema has also been created. All possible potential user data as well as groupings of questions were discussed at this stage. The schema was normalized to ensure data integrity as well as maintaining high system performance. In this process we have also built in a level of scalability by taking into account potential future schema changes. This will allow us to maintain data integrity without redoing the entire database or reprogramming large sections of code.

Software Framework
All potential programming frameworks were installed on our development machines. These will greatly aid in minimizing programming and coding costs. An emphasis was placed on choosing open source products, which again contribute to lower costs, gives greater stability and increases security.

Once the server and frameworks were setup work on system security began. The following security measures are in place:
- We will use SSL to transmit the data to servers.
- Database data will be encrypted.
- Database will only accept connections from approved sources.
- Access to servers will only accept encrypted authentication keys, no passwords.
- Firewalls are in place to only allow web, ssh, and ssl access.
- Physical access to servers is limited to a secure facility in the Amazon AWS server farm.
- Perform regular security audits.
- Ensure all server software is up-to-date.
- Monitor server logs for anomalies.
- Single point of access to data for administrators and that is encrypted and password protected.

With the approval of the mockups and the hardware/software being ready, work has begun on the front and backend programming. The final product will be developed here. Once the programming is done alpha and beta testing will be done to work out the bugs, ensure proper data integrity, browser compatibility issues, and system performance.