|
|
|
|
Milestone #1 9/25/07
1. Name
|
| | Jeeyun Lim |
| | | 1 (8%) | |
|
|
| | Dave Eng |
| | | 1 (8%) | |
|
|
| | Derek Sessions |
| | | 1 (8%) | |
|
|
| | Kevin Le |
| | | 1 (8%) | |
|
|
| | Aaron Cottle |
| | | 1 (8%) | |
|
|
| | Rae Alty |
| | | 1 (8%) | |
|
|
| | Yuan Gao |
| | | 1 (8%) | |
|
|
| | Sohum Misra |
| | | 1 (8%) | |
|
|
| | Hubert Lee |
| | | 1 (8%) | |
|
|
| | Corey Shaw |
| | | 1 (8%) | |
|
|
| | Felipe Serrano |
| | | 1 (8%) | |
|
|
| | Brad Dodson |
| | | 1 (8%) | |
|
|
| | Matt Freeburg |
| | | 1 (8%) | |
|
|
Total: 13 |
2. Percentage complete
|
| | 70% |
| | | 1 (8%) | |
|
|
| | 90% |
| | | 2 (15%) | |
|
|
| | 25% |
| | | 2 (15%) | |
|
|
| | 75% |
| | | 1 (8%) | |
|
|
| | 100% |
| | | 2 (15%) | |
|
|
| | 85% |
| | | 1 (8%) | |
|
|
| | 80% |
| | | 2 (15%) | |
|
|
| | 10% |
| | | 1 (8%) | |
|
|
| | 50% |
| | | 1 (8%) | |
|
|
Total: 13 |
3. What milestone objectives were actually attained? Be specific!
|
| | We were able to create content module (which we may not keep around actually) that the web app uses to communicate with the backend. We create functions for retrieving metadata, as well as formatted data (HTML code in XML format) to be used. We weren't able to test this functionality because the backend is not complete. We could've made arbitrary data to test this, but this week we were focusing more on finalizing the architecture design as a whole.
It sounds as though you've written this code completely but haven't run it on any data. Testing is one thing, and debugging is another--I'm not sure I'd consider this complete if it hasn't been run on anything at all. The backend shouldn't need to be in place for you to run one or two small batches of data through. --Chelsea |
| | | 1 (8%) | |
|
|
| | The milestone objectives assigned to me were:
- Research about how eBay handles searches, including the "search within description" feature.
- Research on "box" solutions that are available for searching and indexing within a database.
And as a group we were assigned to:
- Construct a better definition on what types of data will be needed for the back-end to sort and collect.
- Think about the algorithms required to process the data into a useable form.
Completed were the following items:
- I was able to perform research on eBay and the search process that it uses. I came up with that it actually didn't use its own searching and indexing software for the longest time (approximately 7 years). In addition, in order to perform searching through description, it uses its indexer to create some cached file with words and their occurrence/relativity - all information was e-mailed to Rae
- I found many links related to box solutions to searching and indexing. The relevant data was e-mailed to Rae. Task is currently listed here, but is not listed as completed since (as of this writing) Rae has not had the time to look at it and respond whether or not it is sufficient.
- We (the searching and navigating group) met on Monday, and believe to have sufficiently answered this question. The notes can be found here
I don't really see a lot of answers to questions in that OneNote document. It seems like brainstorming went on, but what was the final conclusion?
|
| | | 1 (8%) | |
|
|
| | Milestone was to have a working content display system for text only.
The code is all there and compiles fine, with display pages, but is untested (since no back end implementations existed). I could have written my own test classes, however, as I wrote this I realized this entire section would need to be reworked on its original design, so I skipped testing since we're going to throw out the code anyway.
I'm not really sure how to respond on this week's milestone, since a change was announced but not made in time to transfer to milestones. --Chelsea |
| | | 1 (8%) | |
|
|
| | The template for creating profiles in web forms was fleshed out in CSS and web form controls and a two stage process. The fields and labels are present but unable to communicate with the server.
Was that the only objective for the week? Please link to the task list...thanks! |
| | | 1 (8%) | |
|
|
| | The interfaces were fleshed out, though we didn't define how tags and comments worked in the backend until after Tuesday. A rudimentry, proof-of-concept content retrieval object was created, which could have been enough for other groups to start programming against the backend interfaces.
The question is, was it created in time for the other teams to make use of it? --Chelsea |
| | | 1 (8%) | |
|
|
| | Group milestones:
G1. We looked into different types of data we'll need to figure trust, both global and local, as well as anything else we thought we needed for ranking results. This is essentially our answer to the first of our "milestone tasks" Next time, could you please put a link to any work that has been done and posted on Sharepoint? Thanks.
G2. We researched different options (Ebay searching, Amazon searching, Wikipedia searching) and assigned research of solutions for us ("box" solutions, research to be done by Dave) and got some ideas for how to search, but did not come up with any definate algorithms or the like. Although this fits the official milestone ("Begin to think about algoirthms to process data..."), it's not exactly complete. Still, this is a lot of the final goal, so truely completing it is not something to happen without being able to test (including tests on a database).
Personal milestones:
P1. Wikipedia relavence search research. I assume since this is under "milestone objectives obtained" that you did this, but could you please be more specific as to what you did?
P2. Talked with Brad to understand the architecture better. And did you?
P3. Talked to Aaron and figured out where the search code lies in the architecture. Talked a little with him about how our team will access information, and what that information will look like. As this is not fully defined for them, neither is it for us.
Next time, can you link to the task list so we can see what was assigned at the beginning of the week? Thanks.
|
| | | 1 (8%) | |
|
|
| | My first task is to write/find a WYSIWYG text editor.
Link
I found this website:
http://tinymce.moxiecode.com/
It's a nice open source text editor written in Javascript. It's very easy to integrate and cross-platform.
After this task I was assigned a new task which is development of "My Content" page.
Link
I made a page that can add/delete/move content boxes and store part of the information about the content boxes. |
| | | 1 (8%) | |
|
|
| | Personal milestones
- Research into Amazon.com searches and how they relate content to each other. Where did the results of this research go? Is it posted anywhere on Sharepoint?
- Research into SQL Server 2005 and how to use it so that when we have to start writing backend code, we are ready to go.
Group milestones
- Define the data that we are going to require.
- Think about algorithms that can be used to search and relate data to each other. Two of our group members attended the Google meeting which gave a good overview of a few algorithms.
- Define the very important feature that will be trust. And did you do this? I assume since this is under "objectives obtained" that you did, but please be more detailed as to what got accomplished. Links to the task list are also appreciated!
|
| | | 1 (8%) | |
|
|
| | Made database tables that reflected the interface defined by Aaron on the source control repository. My milestone specification can be found here. |
| | | 1 (8%) | |
|
|
| | Our milestone was:
• Get a user’s profile page from the server (given his or her id number), and display the information to the user.
• Get the metadata about a piece of content from the back-end and display it to the user.
• Load and display a piece of content from the back-end.
I believe we completed all of these objectives.
Please link to a task list for the week so we can see what was set out for everyone to do. Also, "I believe" seems to be a bit of a cop out statement. See comments below for "It's done, it just hasn't been tested." |
| | | 1 (8%) | |
|
|
| | I reinstalled everything on my machine and got VS and TFS up and running. I created a project for my team and uploaded some demo content for us to see. |
| | | 1 (8%) | |
|
|
| | This is tricky since I'm working from last tuesday's milestone I believe.
Firstly, what my goals were for the week (sorry about not posting these anywhere - I didn't realize that I should):
- Provide the a concrete goal for each team.
- Get everyone up to speed on using the repository.
- Improve our process as far as disseminating information through sharepoint, etc.
- Force the issue on integration of the pieces of code.
- Improve the process of handling team leader meetings, and customer meetings.
Later as the need arose, I additionally targeted the following goals.
- Clearly communicate our design decisions, and in so doing, also settle any disagreements about design.
- Assign clearer milestones.
Of these, I believe that I'd only attained 4 by last tuesday:
I believe everyone (at least most people) had successfully gotten the project from the repository and begun using tfs.
I also think that we significantly improved the running of team leader meetings since I had a much more specific agenda. Customer meetings still need some work (i like the suggestion of not having everyone there), but I felt our presentation was good.
I also think the communication about design decisions improved substantially after Monday's class, which led me to produce some design diagrams that forced the issue on a lot of decisions. We're still in flux about so many things, particularly the search/navigation stuff, but at least we made substantial progress (and I learned a lot).
Also, while we still don't disseminate information effectively, and the sharepoint is, in my opinion, a total mess, I still believe we've improved the situation dramatically over the original discussion list nightmare. (But look for more improvements soon!) |
| | | 1 (8%) | |
|
|
| | My milestone was here.
I completed the expected part of my milestone, but not the "if you have time" part. I consider that good progress, but not great or excellent. I didn't complete it until wednesday morning, but since we didn't get milestones until monday I don't think that is unreasonable. Had I not been sick I would have hoped to work on the database calls as well.
Specifically, I modified SimpleEntity and SimpleBackend to remove the exceptions thrown on their method calls and replace them with simple default return statements. Then I created a similar SimpleContent class also with default return statements. |
| | | 1 (8%) | |
|
|
Total: 13 |
4. What milestone items were left uncompleted? Be specific!
|
| | I originally understood the content module to be a general module that the front end uses to communicate with backend. So I had an implementation of a module that was used for loading user profile page, in which the user's information (name, email, etc) is retrieved from the backend to be displayed. However I later realized that the content module is for contents only and so I started on implementing a webpage that communicates directly to the backend for gettin the user's profile. It is not done, but I was told that the code I was writing may even be irrelevant, so I stopped on it now. We're progressing onto working with video content.
It's not clear how this confusion happened--I'm guessing procrastination combined with miscommunication. Strange to say it's lucky that your code turned out to be irrelevant, but that may be the case here. |
| | | 1 (8%) | |
|
|
| |
-
We did not complete number 4 on the list above. Well...technically we did, but the actual phrasing of the milestone was, "Begin to think about algorithms to process this data into useable form. I’m thinking that search indexing is something that will run as a background process, disconnected from any user effects, other than user actions that create new content to be added to the queue of things to look at. I think you should work from this model to decide how you will index data, and how you’ll use these indices to return search data in a performant way." We haven't yet found a complete solution to this problem (which is in all fairness a fairly large problem), but we are looking into it, looking at what "box" solutions might be available, and essentially define what we will be doing to complete this objective. So we have thought about it. But we haven't yet come up with anything concrete (hence the 90% completion). This milestone was very vaguely defined for us, which again poses the problem of deciding how complete this objective was.
|
| | | 1 (8%) | |
|
|
| | Code untested, but otherwise 'should' work. I put in 25% since I have gained knowledge on how to do the interfacing and stuff, but everything needs to be completely redone.
Thanks for the honesty and explanation of the percentage. |
| | | 1 (8%) | |
|
|
| | The code does not actually upload the information to the server, and as a result cannot retrieve information, nor edit an already existing profile as was intended this week. |
| | | 1 (8%) | |
|
|
| | The user ratings weren't defined at all. Automated DB creation ran into problems when I couldn't get SQL Server to install on either my tablet or my laptop, so I didn't create a process to deploy the databases. However, I did come to the conclusion that this may not be necessary if we all jointly use the Skynet SQL servers.
It's hard to tell exactly what your personal milestone for the week was, but it appears to have been setting up the interfaces and defining user ratings. If that's the case, I'd say you've only completed half of your milestone... |
| | | 1 (8%) | |
|
|
| | G2. We still do not have specific algorithms for processing the data. |
| | | 1 (8%) | |
|
|
| | For the first task, nothing left uncompleted.
For the second task, I don't know how to call C# functions in Javascript. The user can add/delete/move content boxes but the position information of the content boxes cannot be updated.
It appears that you haven't done much research on this subject, because you can't call functions in arbitrary languages from web browsers. Combining what you've said in these two sections, I can't tell how much you've actually done. Try to be more clear in future weeks. |
| | | 1 (8%) | |
|
|
| | Personal milestones
- Researching SQL Server was kind of difficult given that I only had SQL server 2005 express on my laptop. Also, the learning curve seems to be pretty steep especially with preliminary information (most of what I found had to do with making database processes more efficient). However, my MySQL experience does help a bit. Do you feel you did enough research to be "ready to go" when the backend needs to be written?
Group milestones
- Our additional milestone of getting a full text search working didn't make any progress because we were quite unsure about structural stuff (which seems to have been sorted out now)
|
| | | 1 (8%) | |
|
|
| | None |
| | | 1 (8%) | |
|
|
| | Without a working backend, we were unable to test the methods, so we're not sure if they actually work. Your classmates seem to think that there are ways to test without a backend. Also, you should NEVER say that something is working if it hasn't been tested. This will make Dr. Wong's head explode. Also, the code that we wrote uses XML, which we decided after the fact that we didn't want. We're okay with throwing this code away, however, as it served more as an exercise. Besides, using XML simply made things harder on us anyway - we should be able to just get the content and write it directly to the page.
Because of the lack of testing, and the defunct XML code, I marked only 80% completion, but I think we did as best as we could with what we had to work with. |
| | | 1 (8%) | |
|
|
| | All of what I had done for my actual milestone (which was to be able to upload text to the backend) was lost when my tablet broke. I had no working system at home and my priority was to get my tablet up and running again so most of my alloted 410 time went into getting that fixed.
That milestone has now been reassigned to Yuan who is working on uploading content to the server.
That's too bad about losing your work when Windows bit the dust. It's a sad day when you realize TFS is better than nothing. --Chelsea |
| | | 1 (8%) | |
|
|
| | The teams didn't complete nearly as much concrete as I'd hoped, due to a combination of lack of design understanding and lack of concreteness in milestones.
The pieces of code still (after almost a week after this milestone), aren't really integrated, although that WILL happen soon.
Assigning clearer milestones was a miserable failure for the first week, but hopefully we'll (meaning me and the team leaders) get better at it.
I think there's a lot of caveats to the other milestone items that are mostly complete, which I mention above. |
| | | 1 (8%) | |
|
|
| | The "if you have time" portion was to replace the default return statements with calls to the database and then a return of the appropriate value. So, instead of returning "name" for the Name value of SimpleContent, I would look up the name in the database and then return that. |
| | | 1 (8%) | |
|
|
Total: 13 |
5. Additional Comments
|
| | Next time, more well-defined milestones would be greatly appreciated. |
| | | 1 (11%) | |
|
|
| | This week, this part of the project has been removed from the milestone goals, so I'll be focused on other aspects of authoring.
It doesn't sound like you got a very early start on this milestone, judging by the amount completed, but you got lucky this week with all the code that got thrown out/milestones that got changed. Just make sure you get a quicker start next time. |
| | | 1 (11%) | |
|
|
| | I wholly failed at getting the team-specific milestones out soon enough. Much of the code that the backend team was expected to write didn't happen, and I put a large part of the blame on myself for poor directions to the rest of the team. My individual milestone was about 75% done, but in terms of the overall team, I'd rate our performance at closer to 35%.
Thanks for taking responsibility and for the estimation of your team's progress--does your team agree with the you on this estimation? It might help you know what to expect as a team lead if you can gauge what they consider the various percentages to mean. |
| | | 1 (11%) | |
|
|
| | It is hard to say exactly waht "percentage" complete we were (as a group), as by the wording of out group milestone, we have pretty much "completed" the task. Still, I feel we could have done more, and the underlying issues themselves are not complete. |
| | | 1 (11%) | |
|
|
| | I disagree that you've completed this milestone 100% based on your description. This week was a bit murky in terms of late milestone assignments (plus this is the first week), so there will be extra leniency, but try to be a bit more straightforward about your percentage in future weeks. It will help your team leader. |
| | | 1 (11%) | |
|
|
| | Next week's milestone will not be so easy.
Probably (hopefully) true. --Chelsea |
| | | 1 (11%) | |
|
|
| | This was quite a simple milestone, mainly because other groups had a lot of challenges just to get to a level of functionality that worked with this. I don't know about everyone else, but my team had its break and next week we're getting some serious work done. |
| | | 1 (11%) | |
|
|
| | We are moving along steadily this week in terms of milestones, but sadly I can't connect to the back end yet because tags are not being implemented yet.
Thanks for the honest about your percent complete. |
| | | 1 (11%) | |
|
|
| | I think your percentage accurately reflects what you've done. However, I'm not sure I'd agree with your statement about "good progress"...in all honesty, how long did it take to put in default return statements? I realize your sickness was a hindrance for which you will not be faulted, but it may be time to raise expectations of the backend team a bit. |
| | | 1 (11%) | |
|
|
Total: 9 |
|
|
|
|
|
|