ICSE 2011 Implementation Update Aaron Valdez Liane Nakamura Deeksha Malhotra Phase Manager: Max Mueller

Outline ICSE 2011 Project Overview Primary Requirements/Completed Tasks Project Plan Overview of Architecture Implementation and Test Plan Requirements/Design Cross Reference Demonstration of all primary functionalities

ICSE 2011 Website Overview We are making a framework for the International Conference on Software Engineering being held in 2011 in Hawaii. We are using the content management system of Drupal.

Completed Tasks Primary Requirements User Login Forum Basic Navigation (Max) Primary and Secondary Navigation News Reel (Liane) Syndicate (with RSS Feed) Program Events (Aaron) Calendar view with Event data type

Completed Tasks (cont.) Custom Data Types (Aaron) Types for each event in the Program. Program of Events (Aaron) View of the data types in the form of a Program of Events. Profile (Deeksha) Sample Profile

Completed Tasks (Cont.) Secondary Requirements Comments List of Attendees

Technical Issues Inability to upload pictures Troubleshooting Bill Cohen from the ICS help desk Suggestions and assistance from Kari Wrote on the Drupal support pages Still unable to solve the problem We will work on understanding and fixing the problem in the next Implementation phase.

Updated Project Plan New Risks Limitations of hosting Drupal on ICS servers Inability to solve a Drupal problem due to our lack of experience Issues that resulted… Blank module page Issues with uploading images

Risk Mitigation for the blank module page New Contact: Bill Cohen Director of Computing Support Helped troubleshoot errors Increased PHP memory limit from 16M to 32M Problems with permissions

Schedule Update We are on track!

Table The Architecture/Design phase took us much longer than previously thought because we had a to understand what each module is and how the modules interact. We also had to map each Drupal module to each functionality and make numerous diagrams detailing things such as the program of events and site navigation. The Implementation/1 st Demonstration phase took us longer than estimated because of all the technical issues we faced. Phase Estimated Time (in Hours) Actual Time (in Hours) Approximate % Difference Prospectus10 0 Requirements Architecture/Design Implementation/1 st Demonstration

Architecture Overview

Within the Site Hierarchy Module Example of Creating an Event

Test Plan for Event Test Case 3: Creating an event Purpose: Testing that the webmaster can create an event that will be displayed to all users. Item(s) being tested: This will test that the event page and calendar feature both work correctly. Input Specification: The input is the webmaster’s event information. Output Specification: The output should be that event is visible on the event page. The event should also be visible on the calendar. Test environment needs or special test procedures: N/A Test Results As shown on the website, the test case passes Failures detected: None Faults debugged: None Final Test Result The user can successfully create an event.

Table that maps the functionality to the Drupal modules needed

Website Demonstration