bounswe / bounswe2015group7 Goto Github PK

The mock-up for web application should be designed

Create a wiki page, and describe mehmet bilal yasar.

Meeting notes for 3rd customer meeting should be written so the others can see 
what's discussed.

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. 

First please update the numbering convention. Each requirement should be named 
as 1 , 1.1.1 , 1.4.5.1.1. In future references to the requirements, this 
convention makes referencing easier.  
In a lot of places in the document, wording does not follow requirements 
conventions. You should use the shall or should keywords in the following 
convention:

- Shall is used to indicate a requirement that is contractually binding, 
meaning it must be implemented, and its implementation verified.  

- Should is used to indicate a goal which must be addressed by the design but 
is not formally verified.

- Should or shall be able to: Functions that the user performs if he wishes. 
Like he/she shall be able to login but he/she shall login if he wants to submit 
content.

The use of any other keywords such as can is not acceptable

Regarding content, you have not described the necessary functions to organize 
and present content. You will have stories about many different types of 
artifacts such as artworks customs and your system should provide extended 
representation. You either need to organize and present the content in a 
meaningful way or let the users organize the content in a crowdsourcing manner. 

You should also look for ways to incorporate semantic information from external 
cultural heritage semantic databases to enhance your system as it still is one 
of your requirements . Think hard on how such information can benefit your 
system.

Add semantic tags: System should differentiate tags semantically. (I.E. when I 
tag something java it should clarify if I mean java the programming language or 
java the islandlike in wikipedia)

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.

There was an online meeting at 17:00 March 03 2015. Wiki page should be created.

There should be some research about semantic tagging and searching. After the 
research, a documentation about it should be written on Wiki section. 

At the Customer Meeting 2, the requirements are reviewed with the customer. 
There are some requirements should be added.

 * Semantic tagging and searching should be improved.
 * There should be more fields other than tags to give information about a story. Shuch as, location and timeline information.

testPower(MathematicalOperationsTest)  Time elapsed: 0 sec  <<< FAILURE!
java.lang.AssertionError: Use assertEquals(expected, actual, delta) to compare floating-point numbers
    at org.junit.Assert.fail(Assert.java:88)
    at org.junit.Assert.assertEquals(Assert.java:667)
    at org.junit.Assert.assertEquals(Assert.java:656)
    at MathematicalOperationsTest.testPower(MathematicalOperationsTest.java:49)

It'd be nice the see the meeting notes on the homescreen.

Use Case shall be design according the template below. While designing, members 
should consider glossary, requirements and the other members decisions about 
the cases.
**************************************************
Use Case #
Name : 
Actor : 
Goal : 
Preconditions
Postconditions
******************template*********************

Create member description for Ahmet Safa Orhan.

There should be some research about building mobile application on Android 
platform. After the research, a documentation about it should be written on 
Wiki section. 

The mock-up for mobile application should be designed.

At least 5 user scenarios should be created by March 18, 23:00.
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.

Hi I am Mustafa

A brief description of the project that we have.

Those take notes in customer meeting, please share your notes on this page.

https://code.google.com/p/bounswe2015group7/wiki/CustomerMeeting1

Do Assignment 1, Part B.

[deleted issue]

[deleted issue]

Scenarios: Good

Use Cases: Good

Use Case Diagram: 
- incorrect usage of include
- items should not be added in a sequence:  report, rate etc are all actions 
doable by the user and should be connected to his/her symbol.  
- recommendation (user does not recommend anything, he sees recommended posts)

Web Mockups: not following a scenario, no real content in some pages

Mobile Mockups : not following a scenario, no realistic data

Sequence Diagram: 
- not all use cases covered 
- classes not represented (user/interface /system not enough)
- you do not have a class called application in your class diagram

Class Diagram: Ok

Test Cases: tested requirements not specified

The project requirements page should be created. The template is committed on 
the wiki page.

Homework 5
2. Draw the main sequence diagrams for your user case scenarios. Your sequence 
diagrams should make the functionality of your system clear. Pay careful 
attention to the objects you select to represent in your diagrams, so that it 
is clear to the reader which objects are represented in the case.
Due: Monday, 23.03.2015 @ 19:00

The main sequence diagrams for the user case scenarios should be drawn. The 
document at the attachment may be helpful.

You can see use cases and scenarios at the wiki section.

I think it is best to use an online tool to draw diagram to make contributions 
easy.

Create member description for Emre Miraç Paksoy

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.

Create member description for Oğuzhan Murat Çakmak

First things first, members should introduce themselves.

Create member description for Fatih Doğan

Create member description for Narin Mahmuti

Homework 5
1. Draw a class diagram for your project. Your diagram should include the Class 
Names, Attributes, and Operations.
Due: Monday, 23.03.2015 @ 19:00

The class diagram of the project should be drawn. The document at the 
attachment may be helpful.

I think it is best to use an online tool to draw diagram to make contributions 
easy.

The requirements of the project should be revised. There are some points which 
are not mentioned enough, such as mobile application and nonfunctional 
requirements.
Also there are some user stories which is not used. They can be also included 
in the requirements.

The ones who accept this issue can use comment section to discuss requirements.

We need to start writing the user stories since they will be really helpful for 
writing the requirements.

Format:

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

Might be helpful:
http://en.wikipedia.org/wiki/User_story

Test cases should be designed.


Homework text:
"This weeks homework is to design use case tests. You need to create tests for 
use cases based on your design as we discussed in class. Refer to the lecture 
slides for detailed information.

You have to follow a tabular format and provide fields such as expected, 
actual, status, notes as well as pre and post conditions and so on as discussed 
in class and in slides.
At this stage of design, abstract test case steps such as the ones given below 
are satisfactory. 
Example:
Go to main page.                   URL.                                         
 See main page with a search field           
Enter a search term.               Kuru fasulye.                            See 
a list of kuru fasulye recipes with their authors
Select recipe from list.            Kuru fasulye by @buyemek.    See the 
nutritional information about kuru fasulye buyemek (calories:340, protein: 20, 
fat:15, vitamin ....

Due: March 29th, Sunday, 23:59"

Create member description for Cenk Temeloğlu

There should be some research about crowdsourcing application. After the 
research, a documentation about it should be written on Wiki section. 

[deleted issue]

One of the users should write the meeting notes on google code so others can 
see the discussed issues and outcomes.

[https://docs.google.com/document/d/1-D690kxJpAp10wpfbCyMwNCuPiGghQonLtDrqsaoCu8
/ Google Documents file]

The topic of the project is known. Thus, the home page should be updated.

Members should do a research on the domain of the project.

There is a Customer Meeting at March 3rd 2015 @ 19:30. We should prepare 
questions which will be asked to the customers. Everyone writes the questions 
in his/her mind in the Google Documents file. We will determine final questions 
at the meeting tomorrow before the Customer Meeting.

https://docs.google.com/document/d/1-D690kxJpAp10wpfbCyMwNCuPiGghQonLtDrqsaoCu8/