bounswe/bounswe2016group10

CmpE 352/451 Group Project

bounswe2016group10's Issues

Assignment 5 - Peer Review for Group 5

Class Diagram

1. For the system class, you can add list of comments and list of tags. If you have searchByTag function in the system, it is forgotten in the class. Otherwise, what is the purpose of the tag?
2. For the registered user, getName and getPassword functions may be helpful. Also, unfollow topic and user methods are needed.
3. Similarly, for the comment, rating, message and tag classes, getById method may be helpful.
4. Comment class is linked to tag and rating but not on topic. Should it be linked also on topic? And maybe on quiz?
5. There may be an “answer” class if you have quiz class.
6. “Edit topic” and “edit quiz” methods can be added.

Use Case Diagram
I think it is clear and simple, which is good. However some points are confusing:

1. "Write comment" is linked to "create a topic" and it sounds like one can only comment on the topic that she created. (As well as "report comment" and "delete comment").
2. "Edit profile" should also be linked to registered user.

Activity Diagram

1. The decision boxes are special for their diamond shape. So you do not need to write "decision".
2. After the home page, it can send the user to a decision box.
3. After "create new topic" and "edit profile page", an arrow should lead to a decision box and it should show the possible actions.

Sequence Diagram
The "registration" sequence has a different manner than the other ones and they are not consistent. For example, the backward arrows should be "kesikli" and names interface types should be defined(Like the other ones.)

Give a brief tutorial to team members about Project Libre

This tutorial shoul include topics like "how to do ... in Project Libre in order to ..."

Check out these videos!

A) Watch the following videos and document your observations on GitHub:

1. Scrum in Under 10 Minutes : 1
2. Patrick Lencioni: Five Dysfunctions Of a Team 2

Optional videos:

1. Toyota Production System - 5S Just, Just in Time, Kaisen : 3
2. Dan Pink: The puzzle of motivation : 4

Assignment 5 - Peer Review for Group 5

USE CASE DIAGRAM

The diagram is very readable and understandable but some improvements can be done in order to handle some ambiguities.

• It would be better if the sentences in the circles have verbs in them. For example, "Registration" can be replaced by "Register".
• "Forget Password" term can be misunderstood. "Retrieve Forgotten Password".
• An administrator user type can be added to system so that administrative functions can be introduced well.

These are just small things that can enhance the understandability of diagram.

USE CASES

Use cases are shown step by step and the steps are minimal enough to show process clearly. Template for use cases are chosen to be explain functionality well.

SEQUENCE DIAGRAM (Create New Topic)

There are some major mistakes:

• Functions look like sentences more than function names.
• Conditions shall be shown on the arrows not as subprocesses.

Other than these faults, overall diagram is very clear and understandable.

ACTIVITY DIAGRAM

• There should be only one outgoing arrow from an activity node. There are many activity nodes that have more than one outgoing arrow.
• Every activity should be split into different activities if the activity contains more than one. For example, changing and adding personal information are different activities, that's why they should be split.

(P.S. : Please increase the resolution of the diagram or give a link.)

CLASS DIAGRAM

Class diagram includes nearly everything that should be explained for the project. Some classes, such as material, can be added in order to clarify whole project. There is a addMaterial(URL) function but I can't understand what a material is composed of.

Upload the milestone report to wiki for Customer Meeting

Until: 20.10.2016 23:59:59

Signup Implementation

Customer meeting

Prepare a Domain Analysis Document

As mentioned in Assignment 2 Part 2 on Piazza
Document it on wiki and place a link for it on project homepage

Documentation target->>

Meeting Todos:

• Refine requirements
• Refine mockups
• Choose the milestones and refine planning according to the recommended calendar
• Make a research for development environment and prepare computers
• Update Wiki

Some suggestions for the meeting:

• Since we are one of the most crowded groups, It's hard to accomplish something in the meeting or decide to big issues.
• We can do a brief talk in first 15 minutes, something like a catch up.
• Then, it would be helpful to divide into groups of 2-3 people. One group refining requirements, the other for mockups, another for planning and so on...
• After 45 minutes of working in seperate groups, we can come together again to show us what we have done. 30 minutes will be enough for that.
• Set up the development environments on computers.

Login Implementation

Create/Draw a "Class Diagram" for the project

• Remember to declare all possible Classes with names, functions and variables
• Remember to show the relational model between these classes (many-to-one, one-to-one, many-to-many)
• Remember to show the actions between these classes
• Remember to show the hierarchi between these classes in terms of "extension" if needed

Create software Requirement Specification

1. Introduction
   1.1 Purpose
   1.2 Document conventions
   1.3 Intended audience
   1.4 Additional information
   1.5 Contact information/SRS team members
   1.6 References
2. Overall Description
   2.1 Product perspective
   2.2 Product functions
   2.3 User classes and characteristics
   2.4 Operating environment
   2.5 User environment
   2.6 Design/implementation constraints
   2.7 Assumptions and dependencies
3. External Interface Requirements
   3.1 User interfaces
   3.2 Hardware interfaces
   3.3 Software interfaces
   3.4 Communication protocols and interfaces
4. System Features
   4.1 System feature A
   4.1.1 Description and priority
   4.1.2 Action/result
   4.1.3 Functional requirements
   4.2 System feature B
5. Other Nonfunctional Requirements
   5.1 Performance requirements
   5.2 Safety requirements
   5.3 Security requirements
   5.4 Software quality attributes
   5.5 Project documentation
   5.6 User documentation
6. Other Requirements
   Appendix A: Terminology/Glossary/Definitions list
   Appendix B: To be determine

Mockups

"They aim to show how your application will work to address the customer’s needs. For example, content creation, content searching, semantic annotation, etc."

Learn how to use Project Libre and Create a Project Plan using this tool

Remember to give a tutorial about "How to Use Project Libre" to your team members

Initial Demo 17th Nov

• Core system functionality

Make a Communication Plan for lifetime of project development

• Establish the goals for your communication plan
• Define the key audiences
• Developing materials for your plan (like tools, tactics...)
• Specify a timeline (period/frequencies of plans, actions etc..)
• Considerations for communications with audience (bunları öngörmek)

Remember to declare for ecah plan

• Audience
• Objectives
• Message
• Channel
• Timing

Assignment 5 - Peer Review for Group 5

Use Case Diagram and Use Cases

• The design of the use case diagram pretty well. We can easily understand what registered and unregistered user can and cannot do.
• Use cases are also well designed.
• Design is generally well but registered and unregistered user is not enough for a use case diagram, you might also take into consideration the admin.

Class Diagram

• The content of the class diagram is enough and the charts are understandable.
• I think the design of class diagram is a little bit complicated. Sometimes it's difficult to follow the arrows and you may get confused.

Sequence Diagram

• Your first sequence diagram which is about registration is well defined and easy to understand.
• But the other ones are not defined well and it is confusing. To undertand them you should read them very carefully and you should be really focused on it.

Activity Diagram

• The diagram for registered user is explained with enough detail as I can read(it is really difficult to read, you should fix it.)
• But the diagram for unregistered users is too simple than it should be. You should some more information on it according to your use cases.

Write and document "Use Cases" on wiki

Write at least one use case for each persona

Write at least 30 User Stories using the Persona Models

• Do not forget to add the features of a user story.
• Remember to define the acceptance criteria for critical user stories when neceassary

Documentation target->>

Create a list of themes and features related to the Project

Document it whereever you wish so that we can go over them in the meeting and later on

Documentation target->>

Milestone report

Open discussion about videos on Piazza

For Homework D part

deneme

deneme

Assignment 5 - Peer Review for Group 5

Assignment 5 - Peer Review for Group 5

Use Cases

• Observe that none of your steps include a system-side step except Use Case 4 Login (Sign In), user will be just aware of what s/he sees, not of a background process.
• How about trying to be more spesific about actors and characterizing them. Don't you think dividing all actors into just 2 categories (Registered/Unregistered Users) is not well descriptive.
• Not an important issue but in Use Case 11 Post Conditions, the term "banned" should be related with administrators. The term "blocked" fits better in this case.

Class Diagram

• If missing something special about your project, sorry about that; however I could not understand the logic behind that a topic should be related with at least 2 tags (Donot forget that It can be your own design aiming something different that I can't understand, but stating this just with curiosity)
• How about retrieving the reports(I mean the getters of Report class). Yes, while users are able to report topics and contents, will your system use these reports somewhere or not? None of 4 core classes (Registered/Unregistered User, Topic and Content) doesnot have reports field or getReports method.

Sequence Diagram

• In Registration, directly accessing from application to database may cause some security problems.

Activity Diagram

• Well done! Looks nice, describes the overall functinality of your system. If you ensured they are consistent with your requirements and project description, nice job

As I observed you worked in details, and working in details brings a disadvantage of making some mistakes. As a whole, you designed your diagrams very descriptive and they are well designed. Do not forget this review shows respect to your work and also helps you to find some possible mistakes or wrong assessments by using a third person's deep analysis. Keep doing well.

Create/Draw "Use Case Diagrams" for the project

All use cases, at least 2 substantial(critical, core parts of the project) cases that are elaborated with actors, description, data, stimulus, response, and comments.

Push the first Tag Life Android Application to GitHub

Project has been created on local, just push it to GitHub as an android project

HW2 Notice

For the homework 2 beside watching some videos, which is trivial, i think we should think on part B which is

B) Explore related material on team work, communication, lifecycles, good practices & bad practices. > Put references and comments about your findings on your project repository.

Graph Requirements

Works with nodes and links
node refers to topic
link refers to relation between 2 topics
link weight is about the number of relation connected to those 2 topics in last assigned hours
node size is about the number of contents committed in topic in last assigned hours
node color is related to link weight start with highest link in map by assigned color related to site color and continue with light color of assigned color through all nodes

It's one of what we talked in pop-up meeting. We wonder whether these are okey or not for you?

Create a List of Personas for the Project

These list should at least has length of 10 Personas

Documentation target->>

Deploying python backend to cloud server

Make a Software Development Project Plan

Estimations will be probably within 1 year length (Because of CmpE451)

Research on teamwork

"Explore related material on team work, communication, lifecycles, good practices & bad practices. Put references and comments about your findings on your project repository."

These are from the resources tab on piazza:

• The software engineer’s guide to asserting dominance in the workplace
• 9 Websites That Will Challenge Programmers!

Create/Draw "Sequence Diagrams" for the project

At least 3 sequence diagrams for adding new content, semantic tagging, and searching.

Creating backend project in Github

Group wikipage should be updated

Due date: 17/02/16

Update your wiki page with basic information of this repository

Updated personal Wiki Page

Find a tool or create one where we can store User Stories in a well-structured shape

All ideas below please...

Assignment 5 - Peer Review for Group 5

Use Case Diagram

The work on Use Case Diagram is really high quality. The clear design of diagram increases readability. Abilities of Guest and Registered user are successfully connected and What user can do or cannot is really easy to follow on that diagram. However, the first thing should be noticed on that diagram is that should not be the extension of creating a comment because it must be a crucial point to determine what the system will recommend to user. Moreover, commenting should not be extended from creating a topic. Therefore, the topic adding part should be reevaluated in order to make distinction between topics and comments clear.

User Cases are generally well-designed. The focus of each cases is made sufficiently atomic. That's why, the point that case leads is satisfied on steps and the result of how system should response to these step is explained carefully in post condition.

Class Diagram

In general, Class diagram is hard to follow but still understandable. Hidden type of user is kind of controversial topic. I did not mention above because class diagram is more suitable perspective to discuss that issue. The aim of project should be that people can reach information,not less or not more. However, hidden profile lead the system to hide every interaction made by the user of profile. There is a dilemma for that project. On the other hand, searching with tags should be a fundamental objective to us. The reason why this is that searching without a tags makes tags pointless. Still, the system will use that information coming from the tags in recommending but, for user, adding tags makes no sense.

Sequence Diagram

Sequence Diagram is not understandable without focusing on it very carefully. The reason behind this is that there is no explanation about what this is before pictures. Giving some conditions and adding goals and characters make it searchable. Nevertheless, after close examination on these diagrams, these are well-scheculed. Conditions and other parts on diagram are designed like what it should be. The topics they choose are upmost important fields for project.

Assignment 5 - Peer Review for Group 5

Use Cases

• I think first of all you should reconsider actors in your project when design use cases. Having only 2 actors(registered, unregistered user) is a big drawback.
• Subcases are extended only from "Create a topic" case. This may lead ambiguity in the minds of readers. Maybe you can consider having a general extension block.
• As i look your project, i can see diversion in the diagram from your project description because, one who has no idea about your project, couldn't understand that this project is learning platform( first of all you don't have teacher actor in the diagram.)

Class Diagram

• Classes are defined mainly. You should add some more functions reflecting your system specifications better. For example basically i couldn't see 'addComment' funciton also 'addQuestion'. Beside this i think the diagram includes main perspectives of the system.

Activity Diagram

• First of all upload the picture in high resolution please).
• I think your diagram doesn't satisfy general principles of Activity Diagram. For example consider adding thick bars in activity options.
• I think either you should cut the diagram to pieces in detail or adding more activities to this 'Registered User Activity Diagram'. Because there should be more activities in the system for sure.

Sequence Diagram

• I can easily say that there is inconsistency between your Class Diagram and the Sequence Diagram. Because, for example you don't have 'search' class in your Class diagram.
• I think order of actors should be reviewed. For example in the 'S.Diagram for Searching' "searchrequest" actor starts sequence but "registereduser" takes place in the end who doesn't make the request.( also unregistered users can also search according to your use cases.)
• Also separate instances and objects so that your design can be generic.

Assignment 5 - Peer Review for Group 5

Create a Responsibility Assignment Matrix(RAM) for the project

Define the tasks, and responsibility types then associate the team members with those tasks with a specific responsibility related to it.

Initial Plan Review & Update

Specify the milestones and update the calendar

Arrange a meeting with all team members on Monday 07.03.2016 at 17:00

Meeting place will be announced.

What should we discuss at meeting?

I guess its a good idea to make list about topics for our first meeting to make our meeting efficient.

1. Wiki pages will be hot topic :)

Customer Presentation 20th Oct

• Explain the product clearly
• Show the mock-ups and scenarios(Several mockups, one per each group member)
• Talk about milestones & semesterly plan

"Look at good examples of Github Wikis for good ideas"

Arrange a metting with all team members on Monday 15.02.2016 at 17:00

Activity Diagram

Furkan ve Korhan

Find a name for our Project

Please write your suggestions as comments. Engish or Turkish is preferred