Skip to content

Milestones

List view

  • Stage 4 - Presentation, Feedback and Finizlize

    Present your work in one of the 2 last lectures (~15 min. +10 min. Q&A), if you prepare slides or clips add them to the documentation and/or book. You are encourage to contribute back the modeling documentation or other help. Describe your interacion and contribution to the project (documentation, fixing or reporting bugs/ open issues, improve development process and even the chapter you wrote). Finish your book chapter, including a summary section discussing what you've learned from the course and the book project, how modeling contributed to your work (or how it got in the way..) and how you spent your time (an important habbit).

    Overdue by 10 year(s)
    •
    Due by June 22, 2016
    0% complete0 open0 closed

  • Stage 3 - Metrics, Variability and Quality Measures

    Describe how the project is coping with the pace of change commonly expected from software, e.g. testing, maintianability, and other means. Describe the applicability of a design metric tool (e.g. code climate) to the project code. Describe how at least 2 qualities are handled, especially, avalability and security (if the product is not a service define others)

    Overdue by 10 year(s)
    •
    Due by June 15, 2016
    0% complete0 open0 closed

  • Stage 2 - Views and Prespectives

    Fork the project's repository and add a documentation folder (consider developing it, e.g., according to this branching model, or the one required by the projcet's development process). add a link to your fork to the introduction section. Describe the given documentation and general source code structure. Analyze and describe the main requirements/features of the product (stakeholder view). Analyze and describe the major or important designs with UML diagrams and or other modeling means (e.g. sketeches (Calico), views, C4). Describe a few challenges for this project (e.g., a missing important feature, known bugs). Try to validate your analysis with the project team and report about it.

    Overdue by 10 year(s)
    •
    Due by June 8, 2016
    0% complete0 open0 closed

  • Stage 1 - Introducion

    Start your introduction section, including: General details about the project (homepage, repository, development team, communications) project fit for our book (why it was chosen?). Describe the model of the development process. Review availaibe resources, especially concerning modeling and architecture (repos, papers, posts, issues/bugs). Add a few images or diagrams to support the above.

    Overdue by 10 year(s)
    •
    Due by May 18, 2016
    •0/1 issues closed
    0% complete1 open0 closed