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.

Team Meeting - Implementation #3

The MVC Project was created, and the Stored Procedures were completed.

Team Meeting - Implementation #2

The team continued creating the stored procedures that will be used to manipulate the entities in our project from the web portal.

Team Meeting - Implementation #1

The topics discussed in this meeting were:

• Virtual Machine - The virtual machine that will be used in the development of the project has finally been set up. This will allow us to finally begin setting up our project in the server.
• Database - The database that will be used in our project was created in the server.
• Tables - The tables which will be used to gather all information  related to Outreach Entities and their efforts were created.
• Stored Procedures - The team begun creating the stored procedures that will tie the web portal with the project database.
• User Interface - Development on the user interface for the portal was begun.
• Project Description for Course Webpage - The project description that will be put up in the course webpage was discussed, redacted, and sent to the TA.
• Team Foundation Server - It was established that the team would research Team Foundation Server in order to use this tool as a repository for our project. Further discussions on this topic will be held in other team meetings.

Client Meeting

Met with Dr. Milagritos González, head of the Admissions and Retention Comittee, and Dr. José Perdomo, Dean of Student Affairs, in order to discuss the requirements for our project. Dr. Milagritos González provided us with the report of the study carried out by members of the UPRM Outreach Comittee on their meeting on June 10th, 2014.

Team Meeting - Progress Report

Began drafting the progress report for our project by delegating the parts included in its format.

Parts were distributed as follows:

Adalgisa

• Technical Progress
• Tasks Progress
• Bibliographic References
• User Requirements
• Analysis of Alternatives
• System Architecture and Interfaces
• Task Progress and Gantt Chart
• Testing Plan 

Mark

• Introduction
• Next Steps
• User Requirements
• System Specifications
• Testing Plan

César

• Expenditure Analysis
• Glossary
• User Requirements
• Mockups
• Economic Analysis

Team Meeting - Portal Design #4

Began detailing the class diagram for our project in accordance to the Unified Modeling Language (UML) standards established by the International Organization for Standardization (ISO).

Team Meeting - Portal Design #3

We sat down to discuss the mockups being developed for our system portal. It was established that some of screens developed required changes because they did not fully comply with the user requirements or the Web Content Accessibility Guidelines (WCAG 2.0) established by the World Wide Web Consortium (W3C).

Team Meeting - Portal Design #2

Finished the sequence diagrams for our system based on the final Use Case Diagram. Begun research on different technologies for implementation as well as standards applicable to our project.

Team Meeting - Database Design #4 & Portal Design #1

Finish the redaction of the Use Case Descriptions based on the diagram generated for our system. Begun the creation of the sequence diagrams for user interaction.

Team Meeting - Database Design #3

Begun the redaction of Use Case Descriptions for our system based on the final Use Case Diagram.

Team Meeting - Database Design #2

Created the preliminary data model for our database by establishing the tables involved and the relations between them. Also begun the preliminary use case diagram of our system.

Team Meeting - Database Design #1

Established the preliminary entities that will form part of our database as well as their attributes and the relations between them.

Team Meeting

There will be a team meeting tomorrow from 11:00am-12:00pm at Incadel to discuss the critique of the proposal draft as well as the upcoming presentation.

RUM Outreach Program Meeting

There will be a RUM Outreach Program meeting on Thursday August 21st, 2014 at Celis 009-010 from 10:30am-12:00pm. All members are required to attend.