comp730:MeAndYou Spring 2017 Joshua Quigley Log


 * Home
 * MeAndYou
 * Semesters
 * Spring 2017

Week Ending March 28, 2017
Build out the user interactions we have with our Use Case diagram using Activity diagrams for each one. Each team member was assigned one to do.
 * Task:

I created an activity diagram for the Login Help subsystem, that allows returning users to reset their password if they have forgotten their original password.
 * Results:

I also started a document for Testing on what functionality should I be looking for in each area, as well as what nonfunctional requirements should the front-end meet?

I spent 6 hours on Sunday, familiarizing myself with PHP via codecademy.org. I have never programmed in PHP before and am not a strong programmer to begin with so this time was valuable to build up some basic knowledge of PHP syntax, loops, and functions.

Grad Student Meeting 3/27 4pm-5pm

Patrick, Andry, Tiffany, and Myself - We met online via Zoom. We discussed the crows foot chart created by William Jones and Patrick. We discussed the existing SQL and how Patrick tuned it up and got it working. We also talked about populating the project with mock data, suggested to look into Mockaroo. Architects met at the end of last class and decided on the attributes for the project. Big question is sustaining data changes such as a change in last name. Proposed idea to have an administrator login which will require a new interface to display an administrator panel. Finally, we discussed the front end design further. We all agree the big milestone for the week is to finalize a data model.

Team:
 * Plan:

Meet on Wednesday and review the assigned activity diagrams.

Help Yashna load Graphics software to begin work on the icons.

Identify our priorities and changes to the interface.

Independently:

Spend time next weekend reviewing HTML/CSS on codecademy.org as it's been 5 years since i've done any web development.

Is the assigned work getting done?
 * Concerns:

Are team members motivated and buying in to the project?

I feel like our group is a bit rutter-less at the moment. Everyone in our group is new to software development and project management, and there is no designated group leader.

Week Ending April 4, 2017
Researched RDP limits of Windows Server that it's limited to 2 instances unless one pays for Remote Desktop Services and the required number of CALs for each additional user.
 * Task:

Figured out how to access the VisualSVN server from outside. Setup user accounts for the entire software team as well as all the grad students to use to login and upload materials.

Setup XAMP to run on my personal machine to run the Demo from last year and make changes without having to be on the server.

Started with looking at the color scheme for the website. Modifying the CSS stylesheet to try out different color schemes, patterned backgrounds, and trying to get the header into a fixed position. Input back from the team appears to be stick with original color scheme.


 * Results:

Data Model design was finalized after class, going with the keep it simple approach.

Spending time on codecademy.org familiarizing myself with HTML/CSS

Set the site header to remain fixed at the top in the custom.css style sheet, so when the user scrolls to the bottom of the page they'll still see the header and nav-bar at the top.

Started development of the Forgot Password page. HTML is done, waiting for the database to be completed to test the PHP.


 * Plan:

Graduate Student Meeting 4/4 at 4pm and 7pm via Zoom

4pm meeting: Josh, Patrick, Andry, Bill, Mac

Setup My Dashboard view to show user's account page with all the attributes they can fill out.

Tab stops on registration page should be left to right

Registration of the demo system works (however upon completion it should redirect to account page).

Still trying to iron out data model on which the new database will be built. This will allow the front end and software teams to make the correct calls. The plan is to finalize for the next class.

7pm meeting: Josh Patrick, Andry, William R.

Create Administration console page

What should an admin see?

Redesign Registration Page layout - ryan

Add security questions

Create forgot password page -- this is what i'll start work on immediatley. Enter email If User found display security questions if right user can create a new password, verify, and submit.

Create notifications page -Zack start the html layout for this

Create a link to the account edit page that already exists - Will R

Manage searches and view matches needs to be redone but will have to wait for the new database

this will include sending emails via the Mercury server when a match is found. which system triggers the email? Sounds like softwares job to me.


 * Concerns:

The task of getting the infrastructure up and running to even make changes to the demo has taken a considerable amount of time.

Staying focused on one task at time as a large group is challenging.

Front End group are in a bit of a holding pattern waiting for the database to be ready so that we can code the php portions against it. (I've also heard similar remarks from the Software group).

Week Ending April 11, 2017
Create Mock-ups using HTML for the manage searches page and view matches page.
 * Task:

Update the group wiki with what I've contributed, new screen shots, and diagrams.


 * Results:

Mock-up creation was successful and positive feedback from the team members who are active on Slack.

Cleaned up the User Interface Notes Wiki, added our groups Use Case and Activity Diagrams, added some new images, added captions to all the images. Removed the last classes group task logs and started ours by filling in what we've each been assigned and done so far.

Grad Student Meeting Tuesday 4/11 4pm & 7pm

Discussed the status of front end development and the plan going into the next week to bring all the HTML development together and begin work on integrating the new database with the assistance of the database team.


 * Plan:

Meet in class Wednesday and upload all the new and modified HTML pages as well as the new images the front end group members have been working on to the server.

Begin the PHP coding to pull data from the new database, recently completed by the database group


 * Concerns:

Week Ending April 18, 2017

 * Task:

Work on setting up SVN for the class

Look at mobile responsiveness of the site, and see where we can make improvements

Help where possible to switch PHP to the new database and debug


 * Results:

Setup SVN on my computer, connected to the repository and uploaded our latest front end folder. Then helped colleagues configure SVN on their end, and download the folder into XAMPP so that they can run the site locally, make changes and then commit them to the server.

Set min-widths for various CSS elements which allows the site to disregard some of the formatting (mostly margins and width settings) on small screen sizes. Also eliminated the padding for the navbar so that it maximizes the amount that can render in the header. This allows the site to render more information (such as larger text boxes) in the smaller space, making it easier for mobile users to access the site when on the go. Used the iOS simulator in Xcode to run a mobile browser to test locally.



Meeting in Durham 4/15

Will R, Patrick, Andry and Myself

Updated the About Us page to include authors from 2016 and 2017 -Josh

Worked together to overhaul the register, controller, and model files, so that they all insert correctly into the new database. Register page now successfully registers users to the new database. The account page now pulls from the new database, and is editable. The forgot password page now successfully updates the password in the new database. Updated the statistics on the homepage to pull actual data from the new database. Worked on troubleshooting the login page and its non-existent password authentication, so that it now checks the hashed password the user enters against what it is currently stored for that user in the database.


 * Plan:

Work on PHP calls

Look at Admin page, Forgot Password function, and Mobile Responsiveness.

Integrate the new database and get it working


 * Concerns:

Definitely in the deep end of the pool now when it comes to PHP and how the demo site worked and getting it to work with the new database but I'll keep working on it.

Week Ending April 25, 2017

 * Task:

Wrap up development.

Start Testing and debugging with the current version of MeAndYou2 running on the Lamp server.

Document, Document, Document!


 * Results:

Added the new slogan to the index page, and added a change password button to the account page that links the user to the forgot password page.

Updated the GUI group notes page specifically for the the forgot password. Uploaded new screenshot, updated diagram, and updated the notes and added a page description. Uploaded new screenshots for start a search, manage searches, and dashboard.

Worked on fixing small bugs, such as middle name and nick name being required when they're not supposed to be on registration. And the link on the logo back to home/index missing on a few pages.

Grad Student Meeting 4/25 7pm via zoom:

Software group is focused on testing at this point. Discussion about data model for searches vs registered users.

Team wide focus for class this week is to update the stakeholder (Prof. Jonas) on the system progress and document any change requests for the next iteration of the project for future classes.

Version updates
 * Edit Searches are now possible
 * Notifications are working
 * Phone numbers are successfully working in the 3-3-4 format

Changes
 * Should we add a privacy policy or terms of use?
 * Missing a few Spring 2016 authors for the about us page
 * Account page - shift edit button next to change password button so that they're on the same line.


 * Plan:

Keep updating documentation

Work on breaking the system in the name of testing


 * Concerns:

Version control has been difficult. It was hard to implement and not simple to install and setup for all users, therefore not all team members had it setup.

Week Ending May 2, 2017

 * Task:

Continue work on Updating Project Documentation

All eyes on Testing.

Try to break it, document and report bugs.


 * Results:

Created first version of Gantt chart using a free trial of SmartSheet software for the front end team and uploaded to the GUI Notes Wiki. I referred back on Meeting notes, my Grad Student logs, and group task lists to fill in events and corresponding dates.

Added missing authors from 2016 class to the about us page.

Added a link at the bottom of the about us page to the USNH privacy policy.

Testing - Found errors when editing account details, documented and reported to the team. Found errors when changing password, documented and reported to the team. Both issues were due to a corrupt account, fixed by deleting account and reregistering. Found errors when editing search details, documented and reported to the team. This error only occurs in Chrome, the workaround is to use Firefox for the prototype. Documented a CSS rendering issue in Internet Explorer 11 reported by another team member and fixed it by increasing the z-index for the header in the custom.css file.


 * Plan:

Deep dive on testing the functionality of the system. Monitor non-functional requirements.


 * Concerns:

Do we have a working prototype? Further development introduces new bugs.

Week Ending May 9, 2017

 * Task:

Wrap up Documentation

Keep on Testing

Searching is now working. Submitted multiple searches both valid and invalid. Getting mixed results so far, Some completions. Will keep testing.
 * Results:

Tested v8.5 before final software changes set for Monday. Made new searches, modified account, and changed password without issue.

Test v8.5 after software changes, identified a bug with DOB format, verified, and documented in the GUI testing wiki. Identified a potential bug in the software with matching where the first searcher doesn't get a match even though the second searcher does, and documented.


 * Plan:

Leave the front-end in a good place for future developers to work-on


 * Concerns:

Project is winding down, people want to quit, got to keep going until the end.