Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A List of Tasks #3

Closed
reachspirit opened this issue Jan 15, 2016 · 0 comments
Closed

A List of Tasks #3

reachspirit opened this issue Jan 15, 2016 · 0 comments

Comments

@reachspirit
Copy link
Collaborator

Here are some tasks to do based on the requirements of the project:

  1. Clearly define PUTG and try to justify the definition:

P(problem): Why simple operations like copying and pasting may cause a problem to users? What are the most common behavior patterns that lead to these problems? What are the problems with existing clipboard managers(In what aspects they need to be improved)?

U(user group): What are the targeted users(How to category a user group)? Who are affected most by the problem we mentioned above? What are typical environments and what are the behavior patterns of the targeted users in that particular environment?

T(software tools): Eclipse IDE itself is a software tool. What are the features of the IDE? What specific design principles or rules we need to follow when developing the plug-in(How to make it consistent with the platform)? What is possible with the IDE and what may be impractical given the time? What tools are we going to use for the management of the project and why we choose them(Git-Github, shareLatex)?

G(goal): What functions will the plug-in include and what will not? How to define the usability of a clipboard manager? How to prove that our design is really better than other clipboard managers?

  1. Data collection:
    Were the review documents' inclusion and exclusion criteria described and appropriate?
    What's the relationship between our project to code clone and what's the difference?

Is the literature search likely to have covered all relevant studies(How can we prove that it's a thorough study of the problem)?

Did the reviewers assess the quality/validity of the included studies? (e.g. citations counts, recency)

Were the basic data/studies adequately described? Are we able to get the original data instead of second hand analysis?

  1. Start up exercise and competency proof:
    Create a Hello-World eclipse plug-in/plug-in extension and push it to the branch.
@cleebp cleebp added this to the February 1 Deliverable milestone Jan 30, 2016
@cleebp cleebp closed this as completed Feb 2, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants