bounswe/bounswe2015group4

Automatically exported from code.google.com/p/bounswe2015group4

bounswe2015group4's Issues

Create the description for Oğuz Erdoğmuş

Create description for yourself.

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

create a description about yourself

description

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

create a description about yourself

Creating a description

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

User-Stories needs to be written

We need to write user-stories specifying the basic requirements of the system 
from a user perspective and in a informal language

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

[deleted issue]

[deleted issue]

Research "Semantic Tagging" and "searching"

These topics are about the project we are going to start about. So a 
pre-research is decided to be done. The topics will be documented.

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

Update the domain analysis page

Our customer gave a feedback to our project's wiki page. Update the domain 
analysis section with respect to the feedback

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

HW1-3 Feedback

HW 1

Find a name for your project!
I would appreciate if you could add a photo to your personal pages (for those 
who haven’t added already).
There is a typo in the link for Levent’s personal page. (just saying… :))

HW 2

I do not see how virtual reality applications relate to your project.
The type of some of the issues are incorrect. Such research tasks are not 
actually defects.
I could not spot İsmail Enes Yılmaz and Buğrahan Şahin in any of the 
related issues.

HW 3

User Stories:
Nicely done!

Domain Analysis:
Similarities to other domains are missing.

HW 4

In the background section, it is important that you give some technical 
information about the architecture of your system. For instance, the system 
will have a web and a mobile app, it will have a client-server architecture, 
etc.
Requirements 1.2-1.7: The phrases like “groups shall let users…” are not 
always good. You must write most of the requirements from the users’ 
perspective, as you have done in section 1.1. For instance, Req. 1.2.1 may be 
revised as follows: The users shall be able to provide and edit textual 
information about a group. Req. 1.2.2 may stay as it is, since it is about a 
passive functionality, automatically maintained by the system. Moreover, the 
section titles do not necessarily denote the “who” of the requirements. For 
instance, Req. 1.1.7 may go in the section about groups (1.2).
Please add some requirements about semantic tagging, semantic search and 
recommending content to the users. These are important aspects of your system. 
Actually Req. 1.5.2. seems to be about semantic search, but you should provide 
more details on what “similar” means in the scope of you system. A little 
information about semantic search/tagging: Semantic search should also return 
content with semantically related tags. For instance, searching for the tag 
cappuccino should also bring content with the coffee tag. You must also add 
some requirements for allowing the users to supply such semantic relations 
(semantic tagging).
Section 1.4: Content is a very broad term. You should find a more specific term 
instead of content.
About non-functional requirements: As we have talked in the PS, the 
non-functional requirements should be quantifiable and measurable. In this 
regard, Reqs. 2.2.1, 2.2.2, 2.3.1, 2.3.2 and 2.3.5 are problematic. Also, Req. 
2.1.1. is kind of unrealistic. Instead, you might say that the maximum time to 
recover in case of failure will be x (whatever you like) hours.

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

Mockup for web

Create mockups for web version of the project

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

Preparing the requirements of the project

Work together with other team members and finish the requirments of the project 

Original issue reported on code.google.com by levent.oezmn on 7 Mar 2015 at 3:21

domain analysis

- researching about what is the difference between our web application and the 
other similar applications

- researching about what it the base point to generate an idea about which 
domain we should have

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

Create use cases and use case diagram.

Create every possible use cases of the system. This will show the major 
functionalities of the system. Then, draw the use case diagram.

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

[deleted issue]

[deleted issue]

create user stories

create user stories about the project.

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

create requirements page

create requirements page

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

Preparing class diagrams

Prepare the class diagram including class names, attributes and operations.

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

semantic tagging and searching research

Explore and learn about the topics semantic tagging and searching.

Original issue reported on code.google.com by [email protected] on 19 Feb 2015 at 6:06

General Research on Domain Analyisis

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


Please use labels and text to provide additional information.

Original issue reported on code.google.com by reklamkanali on 7 Mar 2015 at 4:53

Research on Android App Development

Do research about Virtual Reality Application Development and summarize it.

Original issue reported on code.google.com by levent.oezmn on 22 Feb 2015 at 10:17

Research on Building Android Application (Technology beyond it and Mobile Applications)

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


Please use labels and text to provide additional information.

Original issue reported on code.google.com by reklamkanali on 21 Feb 2015 at 9:15

Prepare sequence diagrams

Prepare sequence diagrams for the project

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

Update Requirements page

Some requirements will be revised and fixed.

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

Creating first version of Requirements

After the customer meeting, and group meetings, first draft of project 
requirements are to be written formally.

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

Create a member description for Osman Nuri KAR

Create the description about yourself.
After done, change the status of this issue as completed

Original issue reported on code.google.com by reklamkanali on 17 Feb 2015 at 8:13

Designing the class diagram

Designing the class diagram for the project

Estimated amount of work : 5 hours

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

domain analysis

- researching about what is the difference between our web application and the 
other similar applications

- researching about what it the base point to generate an idea about which 
domain we should have

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

create the description about yourself Berfu Büyüköz

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


Please use labels and text to provide additional information.

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

Create member description for Gercek Ilke Gultekin

Creating a wiki page for Gercek Ilke Gultekin and editing the members page to 
display the link for the wiki page

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

Create the description about yourself.

Create the description about yourself.

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

Create member description for Alper Ahmetoğlu

 .

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

Prepare some requirements

I prepared some requirements due to our project description, outcomes of our 
first meeting with costumer and our research.

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

Set Side Bar for Wiki

Side Bar Navigation provides a better view for wiki, so it would be good.

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

Research on Building Android Applications

Make research on using databases while building android applications.

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

Do a domain analysis

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

 * Customers and users

 * The enviornment

 * 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.

 * Similarities to other domains

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

Documenting presentation of one of our scenarios

The document for presentation of one of our inclusive scenarios.

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

Create member description for Mert Can Çüçen

There will be a profile summary for myself.

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

Research on Crowdsourcing

Research on Crowdsourcing

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

Domain Analysis

Performing a domain analysis of the project, adhering to the details specified 
in the piazza post

Estimated time : 3 hours

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

Domain Analysis and Research

 * Finding applications that have common properties with our project.
 * Providing informations about those applications about their key features, differences from our one.
 * Understanding how other people chose their domain according to feautures.
 * Listing best domains what are available.

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

I created some user stories, which are to interest of all types of roles.

These user stories are based on expected properties of the system by an 
arbitrary user (no matter what is their role is in CmpE department in Bogazici 
University).

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

Mockup for mobile

Create mockups for mobile version of the project

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

closing issues that are already fixed

seems in this project, there are a lot of fixed issues and still they are open. 
i think they should be closed, so other people don't confused.

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

Research on Crowdsourcing

Make research on Crowdsourcing and report it.

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

Create the description about yourself.

Create the description about yourself.

Original issue reported on code.google.com by levent.oezmn on 17 Feb 2015 at 7:33

Documenting the use cases and generating a use case diagram

Writing down use case scenarios and generating the corresponding use case 
diagram using online uml diagram tools

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

General Info About Android

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


Please use labels and text to provide additional information.

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

Writing Scenarious

- Writing part of scenarios 
- Deploying scenarios to google code

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

Preparing Scenarios

We need to prepare scenarios to see some of the actions in the project.

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

Research on semantic search

Research on semantic search

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

Crowd-sourcing concept needs to be researched

Crowd-sourcing concept needs to be researched 

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