476 reputation
27
bio website edward.de.leau.net
location Amersfoort, The Netherlands
age 43
visits member for 4 years
seen Nov 18 at 21:27

see http://edward.de.leau.net for more info about me.


Nov
22
comment VPS versus Shared Hosting
I think this can be be best continued in the chat. for the record I use both multiple shared accounts and vps. (put stuff where handiest).
Nov
22
awarded  Commentator
Nov
22
comment Tools to produce & manage specifications/requirements (not ticket trackers)
I only scratch the surface.
Nov
22
comment Tools to produce & manage specifications/requirements (not ticket trackers)
changes in multiple relations to that use case you tracing to. Another example is e.g. splitting of release functionality. You want to select those 150 functional requirement and with one click assign them to another release so that the whole "tree" under it also automatically gets transferred to the other release INCLUDING the automatic changes in the workorders in the change system (due to the integration). Another issue is reporting: a RM tool includes a lot of reporting options for reporting on requirements and impact you need to write all that here yourself.
Nov
22
comment Tools to produce & manage specifications/requirements (not ticket trackers)
you need to manage all those relations going out and in that wiki page. E.g. one requirement changes and now you need i assume in a table underneath to check each outgoing requirement e.g. non functional requirement 1 (for e.g. network architect), non functional requirement 2 (e.g. for security officer) for status of progress so you would probably check them off in a table or something to keep track of the progress. Another example with impact analysis is doing scenario's: what happens if I change this: you want impact matrices in a tree structure since a relation to 1 use case could lead to
Nov
22
comment Tools to produce & manage specifications/requirements (not ticket trackers)
@Tim: thank you for replying. This is no the core issue it is about managing that traceability so these relations e.g. in a spreadsheet you can number each requirement. You put the numbers in your bugs and have some code in the spreadsheet scan the bug database to update the lines (or in a random database application). Apart from having to write that not only for bug databases but for a lot of other tool: your modeling tool (e.g. dragging e.g. in eclipse requirements to parts of your model - need eclipse plugin etc... ) IF something changes in that relation OR if you need to do impact analysis
Nov
21
revised Tools to produce & manage specifications/requirements (not ticket trackers)
deleted 421 characters in body
Nov
21
revised Tools to produce & manage specifications/requirements (not ticket trackers)
added 1351 characters in body; added 773 characters in body
Nov
21
revised Tools to produce & manage specifications/requirements (not ticket trackers)
added 949 characters in body
Nov
21
revised Tools to produce & manage specifications/requirements (not ticket trackers)
added 631 characters in body
Nov
21
answered Tools to produce & manage specifications/requirements (not ticket trackers)
Nov
21
comment Tools to produce & manage specifications/requirements (not ticket trackers)
You can not do requirements management with a wiki. Requirements Management is not Document Management... You need bi directional traceability this is one of the properties of requirements management. Requirement Management can trace to documentation but is not the documentation etc...
Nov
21
comment Tools to produce & manage specifications/requirements (not ticket trackers)
Putting your requirements in documents is NOT requirements MANAGEMENT. Read the requirements for requirements management... You need bi directional traceability between your atomic requirements. To be able to do impact analysis, phase out, phase in requirements. Trace them all the way down, etc... So maybe you do "requirements management" as "i manage something" but this is NOT requirements management.
Nov
21
comment How do you deal with over-the-head APIs/technology
en dan willen ze ook nog de exacte server specs van te voren....
Nov
21
comment How do you deal with over-the-head APIs/technology
if the initial project planning starts, as indicated in the question, it means that the go for the project has already been given thus it has ALREADY been sold to the customer. So... if there is no "prototyping" and that costs in hours is taken into this WBS then there is no prototpying in place. Ideally you would want this to take place before even selling the solution. So before one or more projects role out of it. So long before that project you want to put "prototyping" as part of the hours needed and some evaluation. This is hard with most customers since they want a solution.
Nov
21
comment VPS versus Shared Hosting
Even if your production site is `a wiki with some custom development´ on a $10 p month dreamhost shared you can sell it after some time for $25.000 e.g. flippa.com/auctions/94049/… so... it really depends on what your requirements are. For site flipping these kind of sites shared is ideal to dump a lot of domains on.
Nov
21
comment VPS versus Shared Hosting
@JoshK, yeah thats the disadvantage of shared, i put it under #4. i was e.g. thinking of dreamhost and mediatemple: shell access is there but ofcourse running tomcat etc requires vps. working around it... yes could spend TIME on that but i think most would go then to vps or dedicated. If your DEVELOPMENT is `doing php around wordpress´ ... shared is good enough for most simple sites.
Nov
21
revised How do you deal with over-the-head APIs/technology
added 196 characters in body; deleted 2 characters in body; added 2 characters in body; deleted 9 characters in body
Nov
21
answered How do you deal with over-the-head APIs/technology
Nov
21
awarded  Supporter