Old site copied from Tigris

This is the old stale information copied from tigris.org. Expect a lot of links to not be working.

This used to be located at http://argopdf.tigris.org.
ArgoPDF - week reports

Week Reports

Week Report #11

  • Added sequence, collaboration and activity diagrams to the report
  • Started to implement deployment diagrams part of the report

My objectives on the next week:

  • Complete with deployment diagrams part of the report
  • Fix bugs

Week Report #10

  • Made some corrections in the report by Linus advices
  • Completed to add additional options to the class diagrams part of the report
  • Added statechart diagrams to the report

My objectives on the next week:

  • Add sequence and collaboration diagrams
  • Started to implement activity diagrams part of the report

Week Report #9

  • Almost completed the class diagrams part of the report (almost, because during class diagram part implementation i decided to add some more options of the the class diagram to the report)

My objectives on the next week:

  • Complete to add additional options to the class diagrams part of the report
  • Add statechart diagrams to the report

Week Report #8

  • Added detailed info for each element of the use case diagram. After discussion with Linus Tolke, some things, which need to be improved, was defined.
  • Started to implement the class diagram part of the report

My objectives on the next week:

  • Complete the class diagrams part of the report.

Week Report #7

  • Modified the report contents tree in the ArgoPDF dialog: moved all use cases in one folder.
  • Implemented UseCasesDiagramHelper class. This class contains utility methods, which help during report generation and working with Use Case diagrams.
  • Implemented ReportUtils class. This class contains general methods, which help during report generation.
  • Implemented the use case diagrams part of the report. Now, for each use case diagram, it includes an image of this diagram and a summary table. Summary table can include actors and use cases with its names and documentation.

The problems which i had had during these week:

  • I had a problem of inserting images in the report. But it was solved.

My objectives on the next week:

  • Add detailed info in the use case diagrams part of the report for every element of the use case diagram.
  • Start to implement the class diagrams part of the report.

Week Report #6

  • Designed the basic interface for the report and partly implemented it.
  • Explored Model subsystem API. Right now, i understand how to get access to ArgoUML data.
  • Designed and developed title page of the report. So, now, you can choose options for title page in ArgoPDF dialog and it will be generated.

The problems which i had had during these week:

  • The main problem was with the Model subsystem API. I have spent a lot of time exploring it for finding what i need.
  • Next small problem was with iText library. I have spent more time than i expected for implementing the generation of title page. My knowledge of using iText was not enought, so it was necessary to read "iText in Action" book. But now i am sure that the process of implementation the diagrams will be in a better way.

My objectives on the next week:

  • Continue to work on the reports. First of all, i want to make a possibility to generate Use Case diagrams (which i didn't do this week because of my problems with Model subsystem API and iText library).

Week Report #5

  • Designed and developed the ArgoPDF dialog.
  • Described in the documentation ArgoPDF dialog. You can find it here.

My objectives on the next week:

  • Continue to write ArgoPDF documentation.
  • Start to work on the report: design and develop title page and some other parts of the report. Write the basic prototype to understand how to extract information from the ArgoUML and to use it in the report.

Week Report #3, #4

  • Continued to write ArgoPDF documentation.
  • Ended to read ArgoUML cookbook.
  • Reviewed code of ArgoUML and understood the main concepts of creating modules for ArgoUML.

The problems which i had had during these two weeks:

  • The main problem is that i did't have enough time because of my university examinations.
  • Next problem is that i can't exactly define the structure of the report. I am sure this problem will be solved during discussion with developers of ArgoUML.

My objectives on the next week:

  • Continue to write ArgoPDF documentation.
  • Design, develop and describe in the documentation ArgoPDF dialog, which will be displayed when ArgoPDF starts from the ArgoUML.

Week Report #2

  • Solved my problems with compiling and running ArgoUML.
  • Almost finish to read ArgoUML cookbook.
  • Started to write documentation of the project. You can find it here.
  • Tryed to describe main components of the future reports i.e. what data from ArgoUML it will include. Draft variant can be found here.

My objectives on the next week:

  • Finish the reading of ArgoUML cookbook.
  • Continue to write ArgoPDF documentation.
  • Continue to explore ArgoUML and find out what information can be used for the reports.

Week Report #1

  • Applied for an Observer role in the argouml project
  • Linus and Ion created a separate project for ArgoPDF: argopdf.tigris.com
    Applied for Observer and Developer roles in this project
    Subscribed to the dev, commits, issues and users lists of argoPDF
  • I have read Manual of Subversion
  • I made work copy of ArgoUML and ArgoPrint
  • Start to read ArgoUML cookbook and review code.
  • I have read docs of ArgoPrint
  • My first problem was, when i tried to compile the source code of ArgoUML, i had errors in 4 files.
    I tried to find the problem, and found this.
    All what mvw did, was not working, because ToolBarFactory do not have public constructor. I was watching toolbar v1.3 and toolbar v1.4beta.
  • Next problem, When i returned the changes of mvw of this 4 files to compile ArgoUML, i tried to run it. And I had an exception: java.lang.AbstractMethodError. This is my logs.
  • Next point of what i almost did, is the first view of the architecture of ArgoPDF. I want to describe the main conceptions and how ArgoPDF will work. I planed to end it today, but by the reason of my troubles with compiling and running ArgoUML i didn't do it.

My objectives on the next week:

  • To find out, why changes, made by mvw, is not working (what solution is correct)
  • What is the reason of my failure in compiling and running ArgoUML
  • Finish to describe my first view of the architecture of ArgoPDF
  • Continue reading ArgoUML cookbook and review code to find out what will be useful for ArgoPDF