bounswe/bounswe2015group5

Xplore: Connecting the dots

bounswe2015group5's Issues

add useful links about crowdsourcing

It will be good for other people who visit our crowdsourcing wiki page, if 
there are useful links to get idea of crowdsourcing in detail. 

#action: add links related crowdsourcing
#estimated time for that issue: 30 min (since I came across really informative 
sites)

Original issue reported on code.google.com by [email protected] on 3 Mar 2015 at 9:11

Write Requirements - Part 4

Prepare and write functional requirements for the following :

Contributions

Original issue reported on code.google.com by [email protected] on 6 Mar 2015 at 4:33

Create member description for Buket Yilmazel

Creation of description page in order to introduce myself to the other team 
members. 

Original issue reported on code.google.com by [email protected] on 16 Feb 2015 at 12:56

Write Requirements - Part 1

Prepare and write functional requirements for the following :

Guest Users

Original issue reported on code.google.com by [email protected] on 6 Mar 2015 at 4:32

Create member description for Mustafa Tuğrul Özşahin

Create a page which contains your personal information, to introduce yourself 
to the visitors. 

Original issue reported on code.google.com by [email protected] on 16 Feb 2015 at 11:35

Upload a photo to member page of Mehmet Burak Kurutmaz

Upload a photo to member page of Mehmet Burak Kurutmaz.

Original issue reported on code.google.com by [email protected] on 22 Feb 2015 at 4:08

Uploading photo to member description page for Ömer Ulusal

Add a photo on member description page.

Original issue reported on code.google.com by [email protected] on 22 Feb 2015 at 11:47

Research: Crowdsourcing Application - Part3

Make a research about Crowdsourcing Applications. Then open a page on the 
project wiki named "Crowdsourcing" (if not opened yet), and document your 
findings. If the page is already opened, add your findings to that page. 

Answering these questions:

- Describe the issues, problems, outcomes, and benefits of these applications. 
- What makes them different from ordinary applications?

First member who starts working on this issue, remember to set yourself as the 
owner. (edit issue).

Original issue reported on code.google.com by [email protected] on 17 Feb 2015 at 11:51

[deleted issue]

[deleted issue]

Review and Finalise Requirements

After all the requirements are written, enter a glossary explaining necessary 
abbreviations and terminology.

To help you, here is a definition from the homework assignment :
Glossary: A list of keywords that are used in the document. This list should be 
comprehensive. You must assume that the reader has no prior knowledge about 
your project or any other related software projects (Example: you must even 
explain what "user" means with respect to your system, even though you might 
think that everyone knows what a user is). If you use any abbreviations in your 
document, their explanations should also be here.

Original issue reported on code.google.com by [email protected] on 6 Mar 2015 at 4:08

Enter my aspects about our project to the google drive folder

Enter my aspects, something unclear for me to the Google drive folder so that 
my team mates can help me and see my opinions. 

Original issue reported on code.google.com by [email protected] on 4 Mar 2015 at 10:32

Creating the report of meeting#4

Create a wiki page which includes information about meeting #4.

Original issue reported on code.google.com by [email protected] on 7 Mar 2015 at 11:08

Review third meeting notes and add links to necessary pages

Review third meeting notes.
Add its links to front page.

Original issue reported on code.google.com by [email protected] on 7 Mar 2015 at 11:47

Research: Android Application Development - Part3

Make research about Android Application Development. Then open a page on the 
project wiki named "AndroidApplicationDevlopment" (if not opened yet), and 
document your findings. If the page is already opened, add your findings to 
that page. 

Answering these questions:

- Give examples of what kind of applications are available and popular.
- What are the benefits, or drawbacks of this kind of apps?
- Describe any other information you can get. 

Cite the resources you used, at the bottom of the page.

First member who starts working on this issue, remember to set yourself as the 
owner. (edit issue).

Original issue reported on code.google.com by [email protected] on 17 Feb 2015 at 12:07

Enter User Stories

Every contributor shall write several user scenarios for the project.

After enough contributions the owner of this issue will check and finalise the 
user story.

Original issue reported on code.google.com by [email protected] on 6 Mar 2015 at 4:00

[deleted issue]

[deleted issue]

User Stories - Bug fix

There are some user stories which have no 'so that' part.

From the lecture (09.03.15), we know that the situation of having user stories 
without a 'so that' part is a defect. Therefore it should be fixed.

(This issue is not assigned to anyone right now but you can accept and own the 
issue in order to fix all missing parts. Otherwise it will be a collective 
issue and anyone can partly contribute to missing user stories.)

Original issue reported on code.google.com by [email protected] on 10 Mar 2015 at 12:25

Research: Semantic Tagging and Searching - Part3

Make a research about Semantic Tagging and Searching. Then open a page on the 
project wiki named "SemanticTaggingSearching" (if not opened yet), and document 
your findings. If the page is already opened, add your findings to that page. 

Answering these questions: 

- Describe the issues, problems, outcomes, and benefits of semantic tagging and 
searching. 
- Describe any other information you could get. 

Cite the sources you make use of, at the bottom of the page. 
First member who starts working on this issue, remember to set yourself as the 
owner. (edit issue).

Original issue reported on code.google.com by [email protected] on 17 Feb 2015 at 11:58

Research: Android Application Development - Part2

Make research about Android Application Development. Then open a page on the 
project wiki named "AndroidApplicationDevlopment" (if not opened yet), and 
document your findings. If the page is already opened, add your findings to 
that page. 

Answering these questions:

- How one can develop an android application?
- What technologies/tools are used to develop?

Cite the resources you used, at the bottom of the page.
First member who starts working on this issue, remember to set yourself as the 
owner. (edit issue).

Original issue reported on code.google.com by [email protected] on 17 Feb 2015 at 12:04

create a report for meeting#3

Write a wiki page on our last meeting

Original issue reported on code.google.com by [email protected] on 3 Mar 2015 at 8:52

Perform Domain analysis - Part 2

Perform a domain analysis of your project. It involves reporting your research 
findings on the following topics.

1- Competing software (similar existing applications): Point out the 
differences of your project with respect to these applications. Provide a brief 
description of the existing applications, listing their key features, and 
finally, list the advantages that  your system will offer compared to the 
existing systems.

2 - Similarities to other domains

Original issue reported on code.google.com by [email protected] on 6 Mar 2015 at 4:04

Write Requirements - Part 2

Prepare and write functional requirements for the following :

Registered Users

Original issue reported on code.google.com by [email protected] on 6 Mar 2015 at 4:32

Review request for Issue 36:Write Requirements - Part 2

Could someone please review issue 36?, I completed my additions. If you do not 
want to add anything I want to close the issue. 
Thanks.

Original issue reported on code.google.com by [email protected] on 7 Mar 2015 at 11:32

[deleted issue]

[deleted issue]

Create member description for Hanefi

Create an issue for yourself.
State the task in the description.
Assign the task to yourself.
Do the task.
Change the status of the task to completed.

( I know that this issue description is recursive, and you have my respect if 
you realized it yourself )

Original issue reported on code.google.com by [email protected] on 16 Feb 2015 at 11:25

Research: Android Application Development - Part1

Make research about Android Application Development. Then open a page on the 
project wiki named "AndroidApplicationDevlopment" (if not opened yet), and 
document your findings. If the page is already opened, add your findings to 
that page. 

Answering these questions:

- Describe what is android (OS), and what is and android application.
- What separates them from ordinary software, like PC programs.

Cite the resources you used, at the bottom of the page.

First member who starts working on this issue, remember to set yourself as the 
owner. (edit issue).

Original issue reported on code.google.com by [email protected] on 17 Feb 2015 at 12:02

[deleted issue]

[deleted issue]

Perform Domain analysis - Part 1

Perform a domain analysis of your project. It involves reporting your research 
findings on the following topics.

1- General knowledge about the domain: The domain is the general field of 
business or technology in which the clients will use the software.

2 - Customers and users

3 - The environment

Original issue reported on code.google.com by [email protected] on 6 Mar 2015 at 4:02

Write Requirements - Nonfunctional

I will complete the nonfunctional section of the requirements part.

Original issue reported on code.google.com by [email protected] on 7 Mar 2015 at 2:43

Create a report for customer meeting

Create a wiki page which includes information about customer meeting #1.

Original issue reported on code.google.com by [email protected] on 7 Mar 2015 at 11:22

Create member description for Mehmet Burak Kurutmaz

Create a member description page which contains personal information of Mehmet 
Burak Kurutmaz.

Original issue reported on code.google.com by [email protected] on 17 Feb 2015 at 2:01

Research: Crowdsourcing Application - Part1

Make a research about Crowdsourcing Applications. Then open a page on the 
project wiki named "Crowdsourcing" (if not opened yet), and document your 
findings. If the page is already opened, add your findings to that page. 

Answering these questions:

- What is crowd sourcing. 
- What is a crowd sourcing application.


First member who starts working on this issue, remember to set yourself as the 
owner. (edit issue).

Original issue reported on code.google.com by [email protected] on 17 Feb 2015 at 11:48

Update requirements wiki page

Update requirements wiki page
Estimated time: 15 mins

Original issue reported on code.google.com by [email protected] on 8 Mar 2015 at 12:27

Write Requirements - Part 0

Write the beginning of requirements

1 - Summary: A brief description of your project.

2 - Background: In this section, you can give any information you want the 
readers to know before reading the requirements. Anything that will allow the 
users to understand your requirements better can go in this section. It can be 
a general description of the architecture of your system, small descriptions of 
the primary system components, or the key features of your system that may not 
be fully comprehensible by solely looking at the requirements.

Original issue reported on code.google.com by [email protected] on 6 Mar 2015 at 4:12

create a report for meeting#2

I will prepare a report for meeting 2 as soon as possible. 

Original issue reported on code.google.com by [email protected] on 21 Feb 2015 at 2:11

Create member description for Can Güler

Assign the task to myself. 
Do the task. 
Then change the status of the task to completed.

Original issue reported on code.google.com by [email protected] on 17 Feb 2015 at 12:48

Research: Semantic Tagging and Searching - Part2

Make a research about Semantic Tagging and Searching. Then open a page on the 
project wiki named "SemanticTaggingSearching" (if not opened yet), and document 
your findings. If the page is already opened, add your findings to that page. 

Answering these questions:

- In what type of software semantic tags and searching are used.
- Give examples of applications/systems which use semantic search, and for what 
purpose?

First member who starts working on this issue, remember to set yourself as the 
owner. (edit issue).

Original issue reported on code.google.com by [email protected] on 17 Feb 2015 at 11:56

Create member description for Ömer Ulusal

Create a page which contains your personal information, to introduce yourself 
to the visitors. 

Original issue reported on code.google.com by [email protected] on 18 Feb 2015 at 12:18

Research: Semantic Tagging and Searching - Part1

Make a research about Semantic Tagging and Searching. Then open a page on the 
project wiki named "SemanticTaggingSearching" (if not opened yet), and document 
your findings. If the page is already opened, add your findings to that page. 

Answering these questions: 

- Describe what is a tag, and what is a semantic tag, from software 
perspective. 
- Describe what is semantic search. What is the difference from ordinary search?

First member who starts working on this issue, remember to set yourself as the 
owner. (edit issue).

Original issue reported on code.google.com by [email protected] on 17 Feb 2015 at 11:54

Preperation of Use Cases

Everyone cc'd in this issue should prepare a genuine use case, and write it 
into the comments. After all of them are done, the owner of this issue will 
collect them, and close the issue. 

Remember that the use cases must cover all the fundamental functions of the 
system. For that reason, everyone who arrive in this issue should *read all the 
previously entered use cases here*, then point out a new use case which is not 
yet studied. 

Also keep in mind that the names of the use cases should be in verb format 
like: *case creation*, *registration*, *tagging*, *commenting*, *searching*, 
*exploration*, etc.. 

Check out : http://en.wikipedia.org/wiki/Use_case for the definition of use 
case where is also a good examle included.  

Original issue reported on code.google.com by [email protected] on 13 Mar 2015 at 4:38

Create member description for Hakan Şahin

Creation of member description page.

Original issue reported on code.google.com by [email protected] on 17 Feb 2015 at 3:00

Find a group logo

We need to find a project/group logo.

Original issue reported on code.google.com by [email protected] on 8 Mar 2015 at 6:10

Research: Crowdsourcing Application - Part2

Make a research about Crowdsourcing Applications. Then open a page on the 
project wiki named "Crowdsourcing" (if not opened yet), and document your 
findings. If the page is allready opened, add your findings to that page. 

- Give examples of well-known crowd sourcing applications.
- What are they used for?


First member who starts working on this issue, remember to set yourself as the 
owner. (edit issue).

Original issue reported on code.google.com by [email protected] on 17 Feb 2015 at 11:49

[deleted issue]

[deleted issue]

Reviewing Whole Research Topics

For further investigation of our project it is required that every team members 
have general knowledge about the research topics, please review related wiki 
pages:

 Semantic Tagging and Searching
 Crowd Sourcing
 Android Application Development

Before close this issue please ensure that you review and understand basics of 
all the topics given above.

#Issue Summary

Action: review all topics
Deadline: 09:00 Monday, 02/03/2015
Assigned to: all team members

Original issue reported on code.google.com by [email protected] on 26 Feb 2015 at 12:56

review report for meeting #3

There is a slight possiblity that i missed some points. I kindly ask some of 
you to review it

Original issue reported on code.google.com by [email protected] on 3 Mar 2015 at 9:04

[deleted issue]

[deleted issue]

uploading photo to my wiki page

I have no photo on my wiki page. In order to introduce myself to instructors 
and my team mates I will upload a photo. 

Original issue reported on code.google.com by [email protected] on 21 Feb 2015 at 2:05

Write Requirements - Part 3

Prepare and write functional requirements for the following :

Admin Users

Original issue reported on code.google.com by [email protected] on 6 Mar 2015 at 4:33

Write Requirements - Part 5

Prepare and write functional requirements for the following :

User Connections / Interactions

Original issue reported on code.google.com by [email protected] on 6 Mar 2015 at 4:34