Team Meeting - Final Weeks

In the following weeks the team will be in charge of:

• Redacting the Final Report
• Taking part in Open Capstone
• Preparing the Final Presentation

Client Meeting

The team met with our current client Virginia Figueroa. Some changes that resulted from this meeting were:

Activities

• Add "Activity Dynamic" field where users can specify the dynamic of the activity.
• Add "Attendees" field (to be filled after the activity has concluded) where users can specify how many people attended the activity.
• Add "Activity Major" field where users can specify the major inn which the activity focuses.
• Add "Target Population" field where users can specify the student population (K-6, 7-9, 10-12) to which the activity is targeted.

Users

• Add "Removal Reason" field where administrators can specify the reason why they are removing a certain user.

Reports

• Should be able to be generated for any specific semester and must included any pertinent information regarding activities, including all the new fields that have been previously specified.

Team Meeting - Integration

During the following weeks, up until November 24th, the team will be in charge of fixing any remaining bugs in the system as well as uploading the project to the server in preparation for our final evaluation.

Team Meetings - Implementation

During the following weeks, up until November 5th, the team will be meeting in order to carry out full system implementation and testing.

Team Meeting - Implementation #6

Having switched the course project to a Git repository the development of the interaction modules of our web portal were divided and assigned:

Adalgisa

• Users (Add, View, Edit, Remove)
• Resources (Add, View, Edit, Remove)
• Search (Global and Advanced)

Mark

• Schools (Add, View, Edit, Remove)
• Outreach Entities (Add, View, Edit, Remove)
• Notes (Add, View, Edit, Remove)

César

• Activities and Media (Add, View, Edit, Remove)
• Units (Add, View, Edit, Remove)
• Feedback (Add, View, Edit, Remove)

Some changes to the database were agreed upon and carried out in the manner of unifying the Outreach Entities with the users into one single table (User) holding common fields while all extra information being contained in separate tables (OutreachEntityDetail and UserDetail, respectively)

Team Meeting - Implementation #5

Due to faults in Team Foundation Server the team decided to switch the course project over to a Git repository hosted in GitHub. The meeting entailed researching how to carry out this switch as seamlessly as possible.

Team Meeting - Implementation #4

Began efforts of generating Entity Framework (an open source object-relational mapping framework for ADO.NET, part of .NET Framework) to use with our project as well as figuring out how to add it to the Team Foundation Server source control.