arc42 / quality.arc42.org-site Goto Github PK

something with "the product" and some stakeholders (users, management, operator/administrator, dev-team, tester

done already

[ ] find a privacy-friendly analytics platform, which enables a minimum of insight into user and access counts

[ ] Add corresponding paragraph to privacy-page

imho all volere qualities should be included by now... therefore I close this

Integrity on Mac, or https://www.site24x7.com/link-checker.html

e.g. all example-scenarios tagged with "reliable" shall be listed on the corresponding tag-page...

in home.md the counter is wrong:

On this site you find explanations to (currently 92) qualities of software systems and -architectures.

count only qualities, not examples/scenarios

when reading the wikipedia page (again), I decided that this quality is a minor subset of fault-tolerance (which we already cover).

It's imho enough to add a link to byzantine-fault-tolerance there...

• add SEO-Tag plugin https://github.com/jekyll/jekyll-seo-tag/blob/master/docs/installation.md
• add SEO sitemap plugin https://github.com/jekyll/jekyll-sitemap

siehe auch http://vdaubry.github.io/2014/10/21/SEO-for-your-Jekyll-blog/

something like the greenish color from the requirements-scenario headings shall also be available as background, similar to the arc42-help class.

We need something like that:

<div class="quality-requirement" >
</div>

where:

• markdown is enabled per default (so we don't need the "markdown=1" in all occurences)
• bullet-list text has the same size as normal text
• bullet-lists have proper indentation, like shown here, especially follow-up lines in multi-line text does not left-aligh, but respect the indentation of the first line. See image for an example.

all terms are either completed or in todo, so I close this issued

Currently it's not possible to distinguish between a "quality" and an "example". It would be nice to have a visual style (css), so that examples get a different background

on tags page, "reliable" is a duplicate!!

"code-readability" is already there, but additional qualities could be:

• low coupling
• high cohesion
• modularity
• adequate code complexity
• test coverage
• ?? others?

not sure if this would be an improvement

with several intro articles