Skip to content

Software project (pathologo) anatomy


Building a demo for P-Explorer, I got a metaphor, If software project’s: architecture – is a skeleton; code is meat; then it’s blood is work items: new requirements, bugs, change requests. If you have no skeleton, you’ll most likely to get a slug… or a damn efficient octopus. Watch out not to get leukaemia – […]

Categorization in Requirements management


It turned out that a very productive idea — to use domain data scheme (sample) as a basic of requirements categorization — is already used. Moreover, idea is standardized in ISO-13250: Topic Maps. Wow. Though, some other, non-domain topics will appear: like nonfunctional requirements, GUI details, project specifics. But still I believe topic map is […]