Giter Site home page Giter Site logo

bounswe2015group9's People

Contributors

atalayyirik avatar basriyilmazturk avatar burakcoskun avatar busebuz avatar dependabot[bot] avatar googlecodeexporter avatar omermtemel avatar suzan-uskudarli avatar thegufte avatar umutuz7 avatar uskudarli avatar zmelce avatar

Watchers

avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar

bounswe2015group9's Issues

User Story 

You should write 2 user stories. Deadline is March 8th, Sunday at 23:00
Details are below:

1) You are expected to write user stories that describe the functionalities
of the software that you are going to develop, primarily from a user's
perspective. User stories are basically short and simple descriptions of
the features that are desired in the final outcome of the project. A rough
user story format is as follows:

As a <type of user>, I want <some goal> so that <some reason>.

User stories are generally written in an informal manner, facilitating the
ease of sharing ideas about the intended system, without the need for
sticking to a strict format. We advise you to get together as a team and
write as many of such stories as you can. It is important that the user
stories you come up with describe your system in a comprehensive manner,
covering all the important features.

Further information can be found in the following sites:

http://en.wikipedia.org/wiki/User_story
http://www.mountaingoatsoftware.com/agile/user-stories

User stories will form the basis of the requirements, which is the third
phase of this homework.

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

Merging group 9 and 10 

Please merge pages of group 9 and 10.
 * Personal information pages
 * Research pages
 * Meeting notes

Original issue reported on code.google.com by basriyilmazturk on 24 Feb 2015 at 6:48

Research on Crowdsourcing applications 

Prepare a document about crowdsourcing and put it into project home.

The document should contain the following parts:
-Description
-History
-Recent Examples

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

User Story 

You should write 2 user stories. Deadline is March 8th, Sunday at 23:00 
Details are below:

1) You are expected to write user stories that describe the functionalities of 
the software that you are going to develop, primarily from a user's 
perspective. User stories are basically short and simple descriptions of the 
features that are desired in the final outcome of the project. A rough user 
story format is as follows:

As a <type of user>, I want <some goal> so that <some reason>.

User stories are generally written in an informal manner, facilitating the ease 
of sharing ideas about the intended system, without the need for sticking to a 
strict format. We advise you to get together as a team and write as many of 
such stories as you can. It is important that the user stories you come up with 
describe your system in a comprehensive manner, covering all the important 
features.

Further information can be found in the following sites:

http://en.wikipedia.org/wiki/User_story
http://www.mountaingoatsoftware.com/agile/user-stories

User stories will form the basis of the requirements, which is the third phase 
of this homework.

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

Meeting Note 

Creating meeting note on the Use Case and its diagram.

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

User Story 

You should write 2 user stories. Deadline is March 8th, Sunday at 23:00
Details are below:

1) You are expected to write user stories that describe the functionalities
of the software that you are going to develop, primarily from a user's
perspective. User stories are basically short and simple descriptions of
the features that are desired in the final outcome of the project. A rough
user story format is as follows:

As a <type of user>, I want <some goal> so that <some reason>.

User stories are generally written in an informal manner, facilitating the
ease of sharing ideas about the intended system, without the need for
sticking to a strict format. We advise you to get together as a team and
write as many of such stories as you can. It is important that the user
stories you come up with describe your system in a comprehensive manner,
covering all the important features.

Further information can be found in the following sites:

http://en.wikipedia.org/wiki/User_story
http://www.mountaingoatsoftware.com/agile/user-stories

User stories will form the basis of the requirements, which is the third
phase of this homework.

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

User Story 

You should write 2 user stories. Deadline is March 8th, Sunday at 23:00 
Details are below:

1) You are expected to write user stories that describe the functionalities of 
the software that you are going to develop, primarily from a user's 
perspective. User stories are basically short and simple descriptions of the 
features that are desired in the final outcome of the project. A rough user 
story format is as follows:

As a <type of user>, I want <some goal> so that <some reason>.

User stories are generally written in an informal manner, facilitating the ease 
of sharing ideas about the intended system, without the need for sticking to a 
strict format. We advise you to get together as a team and write as many of 
such stories as you can. It is important that the user stories you come up with 
describe your system in a comprehensive manner, covering all the important 
features.

Further information can be found in the following sites:

http://en.wikipedia.org/wiki/User_story
http://www.mountaingoatsoftware.com/agile/user-stories

User stories will form the basis of the requirements, which is the third phase 
of this homework.

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

User Story 

You should write 2 user stories. Deadline is March 8th, Sunday at 23:00 
Details are below:

1) You are expected to write user stories that describe the functionalities of 
the software that you are going to develop, primarily from a user's 
perspective. User stories are basically short and simple descriptions of the 
features that are desired in the final outcome of the project. A rough user 
story format is as follows:

As a <type of user>, I want <some goal> so that <some reason>.

User stories are generally written in an informal manner, facilitating the ease 
of sharing ideas about the intended system, without the need for sticking to a 
strict format. We advise you to get together as a team and write as many of 
such stories as you can. It is important that the user stories you come up with 
describe your system in a comprehensive manner, covering all the important 
features.

Further information can be found in the following sites:

http://en.wikipedia.org/wiki/User_story
http://www.mountaingoatsoftware.com/agile/user-stories

User stories will form the basis of the requirements, which is the third phase 
of this homework.

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

User Story 

You should write 2 user stories. Deadline is March 8th, Sunday at 23:00
Details are below:

1) You are expected to write user stories that describe the functionalities
of the software that you are going to develop, primarily from a user's
perspective. User stories are basically short and simple descriptions of
the features that are desired in the final outcome of the project. A rough
user story format is as follows:

As a <type of user>, I want <some goal> so that <some reason>.

User stories are generally written in an informal manner, facilitating the
ease of sharing ideas about the intended system, without the need for
sticking to a strict format. We advise you to get together as a team and
write as many of such stories as you can. It is important that the user
stories you come up with describe your system in a comprehensive manner,
covering all the important features.

Further information can be found in the following sites:

http://en.wikipedia.org/wiki/User_story
http://www.mountaingoatsoftware.com/agile/user-stories

User stories will form the basis of the requirements, which is the third
phase of this homework.

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

User Story 

You should write 2 user stories. Deadline is March 8th, Sunday at 23:00 
Details are below:

1) You are expected to write user stories that describe the functionalities of 
the software that you are going to develop, primarily from a user's 
perspective. User stories are basically short and simple descriptions of the 
features that are desired in the final outcome of the project. A rough user 
story format is as follows:

As a <type of user>, I want <some goal> so that <some reason>.

User stories are generally written in an informal manner, facilitating the ease 
of sharing ideas about the intended system, without the need for sticking to a 
strict format. We advise you to get together as a team and write as many of 
such stories as you can. It is important that the user stories you come up with 
describe your system in a comprehensive manner, covering all the important 
features.

Further information can be found in the following sites:

http://en.wikipedia.org/wiki/User_story
http://www.mountaingoatsoftware.com/agile/user-stories

User stories will form the basis of the requirements, which is the third phase 
of this homework.

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

User Story 

You should write 2 user stories. Deadline is March 8th, Sunday at 23:00
Details are below:

1) You are expected to write user stories that describe the functionalities
of the software that you are going to develop, primarily from a user's
perspective. User stories are basically short and simple descriptions of
the features that are desired in the final outcome of the project. A rough
user story format is as follows:

As a <type of user>, I want <some goal> so that <some reason>.

User stories are generally written in an informal manner, facilitating the
ease of sharing ideas about the intended system, without the need for
sticking to a strict format. We advise you to get together as a team and
write as many of such stories as you can. It is important that the user
stories you come up with describe your system in a comprehensive manner,
covering all the important features.

Further information can be found in the following sites:

http://en.wikipedia.org/wiki/User_story
http://www.mountaingoatsoftware.com/agile/user-stories

User stories will form the basis of the requirements, which is the third
phase of this homework.

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

Domain Analysis 

Please look at the similar websites and report info about them

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

Semantic Tagging Research 

Please create semantic tagging research page.

Original issue reported on code.google.com by basriyilmazturk on 22 Feb 2015 at 2:15

Create scenarios 

Please write 3 scenarios that include the name, actor and the goal of the 
scenario.

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

User Story 

You should write 2 user stories. Deadline is March 8th, Sunday at 23:00 
Details are below:

1) You are expected to write user stories that describe the functionalities of 
the software that you are going to develop, primarily from a user's 
perspective. User stories are basically short and simple descriptions of the 
features that are desired in the final outcome of the project. A rough user 
story format is as follows:

As a <type of user>, I want <some goal> so that <some reason>.

User stories are generally written in an informal manner, facilitating the ease 
of sharing ideas about the intended system, without the need for sticking to a 
strict format. We advise you to get together as a team and write as many of 
such stories as you can. It is important that the user stories you come up with 
describe your system in a comprehensive manner, covering all the important 
features.

Further information can be found in the following sites:

http://en.wikipedia.org/wiki/User_story
http://www.mountaingoatsoftware.com/agile/user-stories

User stories will form the basis of the requirements, which is the third phase 
of this homework.

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

User Story 

You should write 2 user stories. Deadline is March 8th, Sunday at 23:00 
Details are below:

1) You are expected to write user stories that describe the functionalities of 
the software that you are going to develop, primarily from a user's 
perspective. User stories are basically short and simple descriptions of the 
features that are desired in the final outcome of the project. A rough user 
story format is as follows:

As a <type of user>, I want <some goal> so that <some reason>.

User stories are generally written in an informal manner, facilitating the ease 
of sharing ideas about the intended system, without the need for sticking to a 
strict format. We advise you to get together as a team and write as many of 
such stories as you can. It is important that the user stories you come up with 
describe your system in a comprehensive manner, covering all the important 
features.

Further information can be found in the following sites:

http://en.wikipedia.org/wiki/User_story
http://www.mountaingoatsoftware.com/agile/user-stories

User stories will form the basis of the requirements, which is the third phase 
of this homework.

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

Use Case and Use Case Diagram 

Use cases and use case diagram. 
The use cases must cover all the major functionalities of the system. Remember 
that the names of the use cases must be in verb format. The use case diagram is 
a single diagram that includes all the use cases you have prepared. Also make 
sure you use the <<extends>> and <<includes>> keywords in the use case diagram, 
wherever applicable. (Deadline: March 15th, 23:00)

Original issue reported on code.google.com by [email protected] on 14 Mar 2015 at 1:51

HW#3 Part3b 

Spesifications of the homework is given here: 
https://piazza.com/class/i5pbxkrwyq0741?cid=66

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

User Story 

You should write 2 user stories. Deadline is March 8th, Sunday at 23:00
Details are below:

1) You are expected to write user stories that describe the functionalities
of the software that you are going to develop, primarily from a user's
perspective. User stories are basically short and simple descriptions of
the features that are desired in the final outcome of the project. A rough
user story format is as follows:

As a <type of user>, I want <some goal> so that <some reason>.

User stories are generally written in an informal manner, facilitating the
ease of sharing ideas about the intended system, without the need for
sticking to a strict format. We advise you to get together as a team and
write as many of such stories as you can. It is important that the user
stories you come up with describe your system in a comprehensive manner,
covering all the important features.

Further information can be found in the following sites:

http://en.wikipedia.org/wiki/User_story
http://www.mountaingoatsoftware.com/agile/user-stories

User stories will form the basis of the requirements, which is the third
phase of this homework.

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

User Story 

You should write 2 user stories. Deadline is March 8th, Sunday at 23:00 
Details are below:

1) You are expected to write user stories that describe the functionalities of 
the software that you are going to develop, primarily from a user's 
perspective. User stories are basically short and simple descriptions of the 
features that are desired in the final outcome of the project. A rough user 
story format is as follows:

As a <type of user>, I want <some goal> so that <some reason>.

User stories are generally written in an informal manner, facilitating the ease 
of sharing ideas about the intended system, without the need for sticking to a 
strict format. We advise you to get together as a team and write as many of 
such stories as you can. It is important that the user stories you come up with 
describe your system in a comprehensive manner, covering all the important 
features.

Further information can be found in the following sites:

http://en.wikipedia.org/wiki/User_story
http://www.mountaingoatsoftware.com/agile/user-stories

User stories will form the basis of the requirements, which is the third phase 
of this homework.

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

Create scenarios 

Please create a new scenario page and write 4 scenarios that include the name, 
actor and the goal of the scenario.

Original issue reported on code.google.com by [email protected] on 14 Mar 2015 at 5:30

User Story 

You should write 2 user stories. Deadline is March 8th, Sunday at 23:00
Details are below:

1) You are expected to write user stories that describe the functionalities
of the software that you are going to develop, primarily from a user's
perspective. User stories are basically short and simple descriptions of
the features that are desired in the final outcome of the project. A rough
user story format is as follows:

As a <type of user>, I want <some goal> so that <some reason>.

User stories are generally written in an informal manner, facilitating the
ease of sharing ideas about the intended system, without the need for
sticking to a strict format. We advise you to get together as a team and
write as many of such stories as you can. It is important that the user
stories you come up with describe your system in a comprehensive manner,
covering all the important features.

Further information can be found in the following sites:

http://en.wikipedia.org/wiki/User_story
http://www.mountaingoatsoftware.com/agile/user-stories

User stories will form the basis of the requirements, which is the third
phase of this homework.

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

User Story 

You should write 2 user stories. Deadline is March 8th, Sunday at 23:00 
Details are below:

1) You are expected to write user stories that describe the functionalities of 
the software that you are going to develop, primarily from a user's 
perspective. User stories are basically short and simple descriptions of the 
features that are desired in the final outcome of the project. A rough user 
story format is as follows:

As a <type of user>, I want <some goal> so that <some reason>.

User stories are generally written in an informal manner, facilitating the ease 
of sharing ideas about the intended system, without the need for sticking to a 
strict format. We advise you to get together as a team and write as many of 
such stories as you can. It is important that the user stories you come up with 
describe your system in a comprehensive manner, covering all the important 
features.

Further information can be found in the following sites:

http://en.wikipedia.org/wiki/User_story
http://www.mountaingoatsoftware.com/agile/user-stories

User stories will form the basis of the requirements, which is the third phase 
of this homework.

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

User Story 

You should write 2 user stories. Deadline is March 8th, Sunday at 23:00 
Details are below:

1) You are expected to write user stories that describe the functionalities of 
the software that you are going to develop, primarily from a user's 
perspective. User stories are basically short and simple descriptions of the 
features that are desired in the final outcome of the project. A rough user 
story format is as follows:

As a <type of user>, I want <some goal> so that <some reason>.

User stories are generally written in an informal manner, facilitating the ease 
of sharing ideas about the intended system, without the need for sticking to a 
strict format. We advise you to get together as a team and write as many of 
such stories as you can. It is important that the user stories you come up with 
describe your system in a comprehensive manner, covering all the important 
features.

Further information can be found in the following sites:

http://en.wikipedia.org/wiki/User_story
http://www.mountaingoatsoftware.com/agile/user-stories

User stories will form the basis of the requirements, which is the third phase 
of this homework.

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

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.