Giter Site home page Giter Site logo

bounswe2015group8's People

Contributors

arslanbenzer avatar basakeskili avatar berksalmanoglu avatar bugrahan avatar burak-tepedelen avatar dorukkilitcioglu avatar gokcantali avatar goktugerce avatar googlecodeexporter avatar mrtysn avatar sinanharputluoglu avatar siray avatar

Stargazers

avatar avatar avatar

Watchers

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

Forkers

basakeskili

bounswe2015group8's Issues

Update UML diagram of use cases 

Update the use case diagram such that it will contain the following use cases: 
1) Follow other users
2) Unfollow other users
3) Tag posts

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

Background 

Give any information for the readers to know before reading the requirements.

I assume it will take an hour to do so.

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

About mock ups 

Started drawing some mock-ups using wireframe.cc
It looks like it will take 1-2 hours to complete.

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

Glossary of Requirements 

1. Read the requirements document and determine the words that need to be 
included in the glossarry.
2. Descripte these words.

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

Research on Semantic Tagging and Search 

Research about Semantic Tagging and Search. What is semantic tagging? What are 
some examples? What is its difference from traditional indexing? What is 
semantic search? How is it used?

Estimation of time was about 1 hours and it took 1 1/2 hours to complete the 
task.

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

Requirements Feedback 

Hi, here are a few problems i saw at a first glance on your requirements 
document. Please think on them and update them so that we can finalize the 
document by Wednesday. 

The overall format of the requirements document is satisfactory. 
However content wise, it does not seem to include much details on 
representation and organization of cultural heritage artifacts and stories. You 
will have stories about many different types of artifacts such as artworks 
customs and your system should provide extended representation.

For example you may wish to use separate types of representations for location 
of the actual event and the region or people the event belongs to (Indian 
wedding in Istanbul). Or between the concepts and the catalogue information of 
artworks (i.e. Leonardo’s Monna Lisa)

Add semantic tags: System should differentiate tags semantically. (I.E. when I 
tag something napoleon it should clarify if I mean napoleon the ruler of 
france, napoleon the book, napoleon the movie or napoleon orange like in 
wikipedia)

One of your requirements should be the incorporation of semantic information 
from external cultural heritage databases. Think hard on how such information 
can benefit your system.
Add semantic searching. i.e. return results tagged painting when I search 
drawings. Searching by tags does not provide that. 

Add a recommendation system. The system should display the user meaningful 
content. You should have an algorithm choosing what to display. When you have 
10k + entries, you can’t list them all on the homepage.

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

Research on Competing SWs 

Point out the differences of our project with respect to these applications.
Provide a brief description of the existing applications, listing their key 
features, and finally, list the advantages that  our system will offer compared 
to the existing systems.

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

Preparing Scenarios 

Following the format shown in the problem session, each scenario must have the 
name, actor and goal of the scenario as well as the actual steps of the 
scenario in an itemized fashion.

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

Create member description for Mert Yaşin 

0. Create an issue for adding information about Mert Yaşin to Wiki.
1. Assign the issue to Mert Yaşin.
2. Add information about Mert Yaşin to Wiki.
3. Mark this issue as completed.

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

Summary of the Project 

I will summarize the research for homework#3 with Başak Tuğçe Eskili.
Due date is 8th March

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

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.