-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathMSanchezUpdates.html
executable file
·75 lines (74 loc) · 6.77 KB
/
MSanchezUpdates.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
<!DOCTYPE html>
<html>
<head>
<link rel="stylesheet" href="main.css" type="text/css">
</head>
<body>
<div id="Mauricio Sanchez Weekly Logs" class="container">
<div class="header">
<h1>Mauricio Sanchez Weekly Logs</h1>
</div>
<br><br><br>
<div class="content">
<div class="links">
<a href="index.html">Home</a>
<br><br>
<a href="introduction.html">Introduction</a>
<br><br>
<a href="requirements.html">Requirements</a>
<br><br>
<a href="updates.html">Updates</a>
<br><br>
<a href="schedule.html">Schedule</a>
<br><br>
<a href="design.html">Design</a>
<br><br>
<a href="testing.html">Testing</a>
<br><br>
<a href="useCases.html"> Use Cases</a>
<br><br>
<a href="designAndImplementation.html">Design Considerations/Implementation Issues</a>
<br><br>
<a href="enhancementsMaintenance.html">Future Enhancements/Maintenance</a>
<br><br>
<a href="conclusions.html">Conclusions</a>
<br><br>
<a href="installation.html">Installation</a>
<br><br>
<a href="references.html"> References</a>
<br><br>
</div>
<div class="text">
<h2>April 16 - April 22, 2018</h2>
<p>
This week, we met on April 22nd to work on the final report and add final functions to the web application and fix some UI bugs. I worked on making sure the buttons worked for every browser because some browsers were incompatible with the way the web app was coded. Once I fixed those issues, I fixed a somewhat major problem where the article list table would exceed its width on the webpage. It was displaying erratically with each click so I worked on that for a while. Once that was fixed, I worked on adding additional pages to the final report website, which include the designAndImplementation.html, enhancementsMaintenance.html, installation.html, and conclusions.html pages. After that, I fixed some issues with the testing.html page according to Pual Piwowarski's assessment of it.
</p>
<h2>April 9 - April 15, 2018</h2>
<p>
This week I added some more cosmetics to the web application, such as a restart button on the homepage and on articles' display pages. We met up as a group on Sundary April 15 and we worked on the practice presentation for April 16. I wrote about the evolution of the project, including things such as the steps we took to get the point we are at today. I wrote about how we started out with the customers' list of the goals they wanted to be completed by the end of the semester, and included details about how helpful the other groups' projects were to us. A different section that I wrote about is the "Expectations vs Reality" section which involves a discussion about the goals that we ideally wanted to be completed, but due to time constraints as well as the loss of a group member, we were unable to complete.
</p>
<h2>April 2 - April 8, 2018</h2>
<p>
This week, I worked more on the UI of the web application. I added a source bar on the side, where the user can choose which sources to display from. Then, I also added a display of the articles in the form of a table. The table has button for each article. When the user clicks on an article, it redirects to a php file where the article text is displayed and associated attributes such as word count and images.
</p>
<h2>March 5 - April 1, 2018</h2>
<p>
Over the past 4 weeks, I have worked on the UI of the web application and helped with the test plan. We met in the library on March 25 and worked on the whole project for around 3 hours. I was able to set up a php script page for when the user submits their search form. It is still in progress. The index page of the web application is simple but functional right now; it contains the title, and a form submission template. Once the server was set up to host the page, I was able to visually check everything. On March 26, we met with Justin Wedeking to discuss our progress. He was pleased to hear that the host was set up and the fetching script was working properly. For the rest of the UI, I will be using some snippets of code from the previous group, since they have a reliable way to connect to and retrieve information from the database; the commands are very similar, and this will save a lot of time and effort. I will be working towards a more simplified and straighforward appearance, however, so the customers will be able to navigate through the application faster. This past week, we met again as a group on March 30 to discuss the test plans for the project. We will include Unit, Integration, System, and User testing. What I will focus on is User testing, and some unit testing for the functions of the php script which will retrieve information from the database. Some of the user test cases will be boundary testing, trying to test for as many outliers as possible. For the php script, I must ensure that the function calls are correct and that the return values are accurate to what the user wants and what the database sends back. On April 1, we finished up the test plan page on the project website; I added the sections I was responsible for, noted above, focusing on the user testing.
</p>
<h2>February 26 - March 4, 2018</h2>
<p>
This week, I met with the group on Monday with the instructor to discuss the state of the project and the knowledge the customers have on it. On Wednesday, we met to begin work on the presentation. I helped with some of the slides, writing out the introduction slide, as well as adding several small points to other slides as needed. On Thursday, I went to the eStudio with the group and we gave a practice presentation to one of the workers there. He gave us a lot of helpful pointers on how to improve the presentation.
</p>
<h2>February 12 - February 18, 2018</h2>
<p>
This week, I met up with the team in the library, where we discussed the webpage requirements for this week, adding the work estimation for each requirement and adding a calendar tool, Google Calendar. The tools and languages that will be used were also included in the updated page. An API key was acquired, and we'll be using an account in Linode for cloud hosting.
</p>
<h2>February 4 - February 11, 2018</h2>
<p>
This week I made a basic layout of the webpage, starting with the index.html file and adding a short introduction of the project, as well as making a requirements.html file with a list of all the requirements the customer provided us in an email. I also looked at some of the code and brainstormed some ideas about the approach we would take. We have decided to work in Python, since it contains a really useful library for filtering news articles about the Supreme Court for example.
</p>
</div>
</div>
</div>
</body>
</html>