Functionality Schedule

1. Functionality Schedule

2. Phase I
Demo 0
 What to expect? Why? and How?
 Login page should be visually accessible.
 Display pseudo functionality
 Demonstrate how HTML Objects will work
 Manage static objects.

3. Phase I
1. Create a login page
2. Create a static background
environment
3. Create registration page

4. Phase I
1. Create a login page
2. Create a static
background
environment
3. Create registration
page
Create a Login Page
1. Performance of webpage,
expectations of user.
2. Liability - Hidden field for
password, (sub-system
server checking in system).
3. Case & character
specific.
4. Accuracy - completes
functionality within its role.

5. 1. Create a login page
2. Create a static
background
environment
3. Create registration
page
Create a static background
environment
1. Basic workspace for user
interaction.
2. Unchanging interface where
user can navigate.
3. Demonstration of changes
between objects with
visually highlight pointer.
4. Objects should be call
repeatedly.
Phase I

6. 1. Create a login page
2. Create a static
background
environment
3. Create registration
page
Create registration page
1. User should be able to switch
from user login to registration
page.
2. Security - How user
information is store (use of
private class that will be call
later to access user
information)
3. Case & character specific.
4. Accuracy - Subsystem server
should be checking if user
already exist, if does send to
login page.
Phase I

7. Phase II
Demo 1
What to expect? Why these? How?
 Implement process
 Populate white page with demo projection of
 Demonstrate capacity
 Actual demonstration of objects been drag & drop.
 Files will have generic name.
 Do not expect correlation.

8. Phase II
1. Create Dynamic HTML
Objects (DHO).
2. Create Drag & Drop coupling
with DHO.
3. Create compile Drop-Down
Button.

9. Phase II
1. Create Dynamic HTML Objects
(DHO).
2. Create Drag & Drop coupling with
DHO.
3. Create compile Drop-Down
Button.
Create Dynamic HTML Objects
(DHO)
1. Visualize partial front-end and
back-end HTML Objects.
2. Demonstrate function produced on a
static object.
3. Objects should display file name.
4. Traversing files.
5. Comparison on accuracy -
continuing changes between files
and the files that are been made
(populate, stay or change).
6. Auto Reload - Refresh page and
recognize changes.

10. Phase II
1. Create Dynamic HTML Objects
(DHO).
2. Create Drag & Drop coupling with
DHO.
3. Create compile Drop-Down
Button.
Create Drag and Drop
1. Pure back-end HTML objects.
2. Accuracy- Properly naming files
3. Correlation with DHO
1. demonstrate function produced
on static objects
2. objects should display file
name.
3. Auto-reload

11. Create compile Drop-Down
Button
1. Expect the button to have
the compile option in a
drop-down menu
2. Java, C, & C++ should be
highlight (visually show
distinct option)
Phase II
1. Create Dynamic HTML Objects
(DHO).
2. Create Drag & Drop coupling with
DHO.
3. Create compile Drop-Down
Button.

12. Phase III
Demo 2
What is expected?
 Should include DHO population for interface.
 Correct file names (Not generic)
 Interaction to demonstrate functionality between
objects; populating the other "zones".

13. Phase III
1. Create user working directory
2. Create function linked with
compile button.
3. Create 'Drag & Drop' function
for file upload/download.

14. Phase III
1. Create user working
directory
2. Create function linked with
compile button.
3. Create 'Drag & Drop'
function for file
upload/download.
Create User working
directory
1. Link HTML objects
with files in working
directory
2. Populate interface
with dynamic HTML
object (DHO).
3. Link "zones" to
interact with HTML
objects.

15. Phase III
1. Create user working
directory
2. Create function linked with
compile button.
3. Create 'Drag & Drop'
function for file
upload/download.
Compile button
1. Demonstrate server
functionality for pseudo
compile request. (Sending
to the server back-end
to support it).
2. Corresponding changes
to the file system, either
.ml generator, .class, or
makeFile, depending on
implementation.

16. Phase III
1. Create user working
directory
2. Create function linked with
compile button.
3. Create 'Drag & Drop'
function for file
upload/download.
Create Drag & Drop
Upload/Download
1. Demonstrate external
file upload and/or
download of files and
its corresponding
changes to file system
via DHO.
2. Files should be able to
interact in-between
the "zones".