Exam Review Sheet - Software Engineering Methodology | COMP 410, Study notes of Software Engineering

Material Type: Notes; Professor: Wong; Class: SOFTWARE ENGINEERING METHODOLOGY; Subject: Computer Science; University: Rice University; Term: Fall 2007;

Typology: Study notes

Pre 2010

Uploaded on 08/16/2009

koofers-user-lyq-1
koofers-user-lyq-1 🇺🇸

9 documents

1 / 2

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Thoughts on different points:
1. Hosting Plans
a. Look at this link to web hosting offered through something as bland as GoDaddy.com.
This is fairly standard from what I have seen. This would be an acceptable go-by.
i. https://www.godaddy.com/gdshop/hosting/shared.asp?ci=9009
1. Towards the bottom of this page, select the “windows” plan.
2. “Do you want wiki-type tools that would allow community driven content? Wjo has ownership
of the information? Can others fix faulty information?
a. I have had some thoughts on this subject:
i. The deliverable is two-fold:
1. Insight from one person on how they would do something
2. Insight from a community on how they would do something
ii. The individual model should not be editable, but I am still thinking about the
community model.
1. There are two possibilities for the community model as I see them:
a. A wiki page where everyone can edit and the viewer sees one
page presenting a complete topic. That topic may have 50
authors, but the viewer doesn’t know that, nor do they
particularly care.
i. The upside is that this format is probably the easiet to
understand, and people already see this type of format
on Wikipedia
ii. The downside is that you may lose something of value
from different perspectives not being offered.
b. A group blog (or something like that), where you see a history of
input from different users.
i. The upside is that you can see all the users, band
potentially capture the perspective of different people
ii. The downside is the value of the differing perspectives
could be lost in trying to sift through all the segmented
pieces of input.
b. Conclusion: I think we may want to have a blended model that allows for both formats,
allowing the users to pick which format is preferable to them.
i. Part of the page just has to do with authored content
ii. Another part of the page (different tab) has to do with a wiki covering the topic
area discussed showing a community based perspective.
iii. The author links the content to the topic area, which is linked to the wiki.
3. People establishing their identity: Possible solution – peer reviewed content
pf2

Partial preview of the text

Download Exam Review Sheet - Software Engineering Methodology | COMP 410 and more Study notes Software Engineering in PDF only on Docsity!

Thoughts on different points:

  1. Hosting Plans a. Look at this link to web hosting offered through something as bland as GoDaddy.com. This is fairly standard from what I have seen. This would be an acceptable go-by. i. https://www.godaddy.com/gdshop/hosting/shared.asp?ci= 1. Towards the bottom of this page, select the “windows” plan.
  2. “Do you want wiki-type tools that would allow community driven content? Wjo has ownership of the information? Can others fix faulty information? a. I have had some thoughts on this subject: i. The deliverable is two-fold: 1. Insight from one person on how they would do something 2. Insight from a community on how they would do something ii. The individual model should not be editable, but I am still thinking about the community model.
  3. There are two possibilities for the community model as I see them: a. A wiki page where everyone can edit and the viewer sees one page presenting a complete topic. That topic may have 50 authors, but the viewer doesn’t know that, nor do they particularly care. i. The upside is that this format is probably the easiet to understand, and people already see this type of format on Wikipedia ii. The downside is that you may lose something of value from different perspectives not being offered. b. A group blog (or something like that), where you see a history of input from different users. i. The upside is that you can see all the users, band potentially capture the perspective of different people ii. The downside is the value of the differing perspectives could be lost in trying to sift through all the segmented pieces of input. b. Conclusion: I think we may want to have a blended model that allows for both formats, allowing the users to pick which format is preferable to them. i. Part of the page just has to do with authored content ii. Another part of the page (different tab) has to do with a wiki covering the topic area discussed showing a community based perspective. iii. The author links the content to the topic area, which is linked to the wiki.
  4. People establishing their identity: Possible solution – peer reviewed content

a. In the academic community, it is an established model that before an article can be published; it must be reviewed by peers of similar or elevated caliber. The idea is that the community approves learning and evolves as a whole i. This could be beneficial to the question we face. IF we allow those that are creating profiles to label themselves as differing levels of proficiency (amateur/semi-pro/professional/star), to retain that proficiency they would have to post content that is judged by others to be of that quality.

  1. This sort of rescinds my previous position, that someone could not be “harmed” in position by the community, but at this point I don’t see another way.
  2. The benefit is that to stay on the community, or rather, to establish identity, the author has to be “voted in” by the community at large
  3. This still doesn’t entirely solve the problem of starting the community. a. We could hand out proficiency levels initially, and then take those away over time b. The problem with that is that giving away position in the network destroys value. c. The whole concept is that the stature you are in real life can be mimicked online. The only difference is accessibility. b. Another thought entirely – we ditch labels altogether, and people’s value is established by downloads of their material and peer review of their content, completely aside from branding of stature. i. This would solve the start up problem ii. It would also keep the community honest iii. This would be far simpler to implement. c. I need some input here guys. Each method has its quirks.