SAD2 Integration (post your inquiries here)

Server Status:
> Setup not yet completed because of technical problems, will be continued on Tuesday, September 1
> Good News: our dean has expressed his desire to help us with the server configuration

Updates/Announcements about the Integrated Design:
> Each group is required to submit a "detailed" table definition for their subsystems. Please specify ALL fields needed, the primary key for each table, foreign keys, data types, and brief description of the table and fields. These are necessary to finalize the database design and identify all the fields required for common tables in the integrated system. (Not all groups have submitted this requirement yet.)
> Last Monday, August 24, the design team studied the behavior of drupal, particularly the way it stores data into the database. Upon tracing and analysis, we found out that drupal has a different way of referencing keys and storing data. It was eminent that the integrated database design that we proposed will be difficult to follow if we pursued with using drupal. Hence, today, August 28, the team came to agree upon starting over (as in from the beginning, as in from scratch) and hard-code the system. The following are some of the advantages we saw in hard-coding:
1. full control/ease of customization to meet database design requirements
2. clearer understanding of how the system will work, hence it will be easier to defend when the time comes
3. opportunity to learn new concepts and programming languages; encourage exploration and exchange of ideas/knowledge among project members
However, we do understand clearly that time is no longer on our side. That is why we need YOUR PARTICIPATION/COOPERATION.
> Today, August 28, we also presented the first attempt to the date algorithm that was required of us. Unfortunately, the result was not satisfactory . Another attempt will be made, this time, reducing the number of lines of code and possibly employing another algorithm to store the data. If anyone has any ideas, do voice them out or coordinate with Ronnie Biloy.

Scheduled Meetings/Milestones:
SEPTEMBER 1 (TUESDAY) - Group representatives are scheduled to meet at 8 am at the Engineering Lobby. This is will a whole day activity (possibly).
Agenda:
1. Finish server setup - by selected people
2. Submission of lacking requirements of every group (the table definitions)
3. Presentation of common template prototype - Person assigned: Thomas Tangian
4. Finalize module design - identification of common modules and critical modules
5. Designation of members for module development
6. If 1-5 are okay, then we can probably start the actual development

Expected Output from Development:
(The following outputs were set based on realistic expectations)
1. Simple yet complete and functional input forms
2. Prototype of integrated system

FINAL NOTE: The deadline is looming over our heads and we understand that deciding to hard-code everything at this time is a very drastic step. But this is exactly why we have to work together as a class. Resourcefulness, perseverance, determination and dedication are the keys to making significant progress with this project. That is why we ask ALL of YOU - Please find time to attend our project meetings because time will not find you(gets? ).

*end of sermon*

These are the updates from our meeting today, September 12, 2009 at 8:00 am.

The Final UI has been finished and presented. Those who were present all agreed to the UI. However, we are still waiting for RSG's comment. Below is a screenshot of the whole main page.



The color scheme was inspired by the USEP main website color, which is maroon. The color scheme chosen for the system is maroon with a tint of red and a white background for simplicity. The topmost panels are composed of the search feature, login and main navigation. Below the main navigation is the name of the system and an embedded flash of the description of the different services. This flash object is clickable.

Another navigation can be found in the middle of the page. This contains the main services, which are the Davao map and USEP map, services, help and info. There is also a large frame where all the systems will be displayed. All systems are listed under the SERVICES tab. Every time a user clicks on a service, that service will be displayed in the frame. Therefore, the whole page will not have to be reloaded. The footer contains another navigation panel.

Issues/Concerns raised:

1. After clicking a link on the topmost navigation panel, will the user have to scroll down to see the frame where the services will be displayed?

Answer/Solution: There is a snippet of code that will automatically make the page jump to the frame after clicking a certain link. We will make use of this solution to keep the users from having to scroll down all the time.

2. What if the main page of a particular service will not fit the frame and overflow?

Answer/Solution: To avoid this from happening, a standard page size will be set for all subsystems to follow.

3. Will the user have to scroll up all the time to get to the top of the page?

Answer/Solution: A "back to top" link will be added to every section of the page to provide easier navigation from key areas of the page to the top.

Another issue that we tackled during the meeting is the name of the system. We decided on the system's name through voting. The class raised suggestions for the name and explained the reason behind each one. Afterwards, a vote was conducted. Based on the results of the voting process, the name of the system will be "UnISys". UnISys stands for "University Integrated System". Since the system is a product of integrating different systems and answers some of the needs of the university, we found "UnISys" appropriate for the system. However, this is also waiting for RSG's approval.

For those who didn't get a copy of the layout sample, you may download it here.

NEW SCHEDULE/TARGET DATES!!!

NOVEMBER 2, 2009 : DEADLIEST DEADLINE FOR SAD2 INTEGRATED SYSTEM
The story behind: RSG has agreed to extend the deadline for the last and final time, after our meeting today, October 17, 2009. We are expected to submit a working and functional system on November 2, complete with documentation.

OCTOBER 19, 2009 - OCTOBER 30, 2009 : WHOLE CLASS WILL PARTICIPATE IN SYSTEM DEVELOPMENT, DOCUMENTATION, ETC. - ALL ACTIVITIES NEEDED IN ORDER TO FINISH THE PROJECT ON OR BEFORE NOVEMBER 2.

***We have submitted a letter to Sir Val requesting for the exclusive use of ICLAB1 from October 19-November 2 from 8:00 am to 5:00 pm. This is to facilitate the activities for SAD2 and help each other out... We are still waiting for approval. If approved, we will be meeting there EVERYDAY from 8 am to 5 pm and everyone is expected to be present. We are going to continue the development of our systems using the facilities in LAB1 - that is, IF approved.