Group Project

Project Rules

1. 3-4 members per team—no exceptions.
2. You can email me preferences for team members and projects by Friday, Oct. 21. I assemble the teams and assign the projects.
• Send me your project preferences and optionally the names of preferred team members, starting with the one you like best and ending with the one you like least. Send it from the email address that you'd like your teammates to use.
• If you do not email me your preferences, you will likely end up with students of similar lack of initiative, and be assigned the least popular topic.
3. Each team member submits an individual report each Wednesday night in their private Git repo (in a directory project).
   • Each report has this format:

     Date time1-time2: What you worked on
     Date time1-time2: What you worked on
     ...
     Total hours this week:
     Total hours on project:

   • If you like, you can add any comments below
   • Name the reports week1.txt, week2.txt, and so on.
4. Put all other documentation in the Github/BitBucket Wiki
5. Use the issue tracker for work assignments. Each task has a single owner.
   If it's not on the issue tracker, I won't recognize it as an accomplishment.
6. Each team is prepared to give a brief progress report in class on Thursday, with every member present.
7. Each team makes a Git repo and adds me and the grader as collaborators
8. All project code is always on Git.
9. There is a build script that builds the program, runs test cases, runs CheckStyle, and javadoc.
10. It must build on my machine (and on yours).

Projects

You may choose from one of these projects:

ASCIIViolet

Use a text description to specify class and sequence diagram, similar to http://spinellis.gr/umlgraph, http://yuml.me, or https://www.websequencediagrams.com/.

Xiaofan Lin 
Tyler Laskey 
Hing Lum Lam (benny3946?)
Gideon Ubaldo
Repo
Presentation

CollabViolet

What if multiple people want to collaboratively edit a diagram? This too is an application of the command pattern. Commands are set to a server, which sends it to all participants, and the diagrams are kept in sync.

Daanish Husain 
Michael Sterpka 
Matthew Swerdon 
Repo
Presentation

Christopher Leung
Bing Liang
Paul Nguyen (maraudershields)
Ruiyang Wang (w851401530)
Repo
Presentation

RoundTripViolet

Usually, one draws UML, then writes code. How can one keep the diagrams in sync when the code changes? That is the holy grail of “round trip engineering”. In Java, you can use reflection to find out superclasses and the types of fields. Drawing all of them is going to be a mess, but you can ask programmers to use annotations to help you decide what to draw.

Micah Demong
Jiabao Qiu
Ee Yieng Zheng 
Repo
Presentation
 

UndoViolet

Violet 0.16 has no undo/redo. Your task is to add it, using the command pattern.

Craig Huff
Yuliang Pan
Qi Liu
Hengyi Shi 
Repo
Presentation

VioletDroid

Some way of doing some UML diagrams (at least class diagrams, maybe sequence diagrams) on an Android phone or tablet

Anique Davla
Parvati Menon
Vishaal Prasad 
Charlene Young 
Repo
Presentation


Lance Barrett 
Saifuding Diliyaer 
Weihang Xiao
Xin Yan
Repo
Presentation

VioletFX

Class and sequence diagrams with JavaFX

Ly Nguyen 
Khiem Pham 
Shariq Shah
Repo
Presentation

Week 1 Goals

• There is a Wiki document describing what features you believe you will be able to accomplish
• There is a set of “issues” for next week
• Some code is in Git and builds on the command line
• Each team member submitted their individual reports

Week 2 Goals

• There is some design documentation on the Wiki
• Each team member has made at least one commit
• Code builds on the command line, including javadoc and CheckStyle
• The issues are cleaned up. Each issue must be doable in ≤ 3 days and have a single person assigned to it.
• Each team member has closed at least one issue and has put the closed issue number(s) in their report.
• Each team member submitted their individual report, with weekly and total hours, in the correct place (individual repo/project/week2.txt)

Week 3 Goals

• Functional specification (what the project will do) is complete.
• There is some design documentation (key classes, mechanisms, protocols).
• There are sufficient issues to keep each team member busy for week 4.
• Each team member has closed at least two issues and has put the closed issue number(s) in their report.
• The project builds and does something useful. Put instructions for building and for trying out that useful feature on the wiki.

Week 4 Goals

• Design documentation lists all planned classes.
  For CollabViolet, describe the client/server protocol precisely. For ASCIIViolet, describe the input format precisely. For RoundTripViolet, describe the annotations and code generation rules precisely.
• There are sufficient issues to keep each team member busy for week 5. You need 2-3 issues per team member, each short and assigned to a single person.
• The project builds and does something significant. Put instructions for building and for trying out that significant feature on the wiki.
  In the coming weeks, add to the list of features that work.
• Every team member has multiple commits throughout the week.
• Keep your individual reports up as before.

Week 5 Goals

• There are sufficient issues to keep each team member busy for the remainder of the project.
• The project builds and accomplishes most of what is required, perhaps with some errors. If you don't have a status page yet, make one. It should have the build instructions and a list of features that work.
• There are no Checkstyle errors.
• Every team member has multiple commits throughout the week.
• Keep your individual reports up as before.

Week 6 Goals

• All issues that are required for successful completion of the project are on the issue list.
• The implementation is complete except for minor bugs.
• Documentation is substantially complete.
• Every team member has multiple commits throughout the week.
• Keep the status page and your individual reports up as before.

Week 6⅔ Goals (by Monday Dec. 5)

• Implementation and documentation is complete.
• Presentation slides are complete.
• Keep your individual reports up as before.