Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - sargasso

Pages: 1 2 3 [4] 5 6 ... 94
46
Suggestions and Requests / Re: Rich text for use case scenario documenting
« on: September 06, 2007, 04:16:13 am »
Hiccups!

No I had a good long talk to myself about it and all three of us agreed (but one of us refuses to commit himself).


;D

bruce


47
Just to clarify... from my POV... as a general requirement

Bold      Mandatory
Italic    Mandatory
Underline Mandatory
Strikeout Mandatory
Preformat
Mandatory
[size=32]Size[/size] Not required
Font Optional
Colo(u)r Optional
Super Mandatory
Sub Mandatory
Code: [Select]
"Code" Desireable
  • List Very Desireable

http://Hyperlink Moderately Desireable
eMail@eMail.org Optional
;D Smiley  >:( Extremely undesireable


.. add your votes

There is (are?) a plethora of (ick) ActiveX (/ick) controls available to do this. There are even .. oh blah blah..

bruce

bruce

48
Suggestions and Requests / Re: Rich text for use case scenario documenting
« on: February 28, 2007, 04:33:10 pm »
Quote
While there's not been such a feature added yet, we live in hope..


I hope to live that long.

bruce :-X

49
Suggestions and Requests / Re: New Edge type: "Custom"
« on: September 05, 2007, 04:31:43 am »
Initially, ...
EEEEEEEEEEEEEEAAAAAAAAAAAAAAARRRRRRRRRGGGGGGGGHHHHHHHHHH!!!!!!
(refer to search +999 days re my thoughts on colored shirts)

...

on reflection, this is exactly what I was always talking about "edges are people too".

So, yes add my vote.

bruce

50
Suggestions and Requests / Re: Attaching diagrams to elements
« on: September 05, 2007, 04:37:51 am »
Reflecting elsewhere  ;)
Quote
All diagram objects should have "Add Diagram" and "Link to Diagram" commands on their context menu, making the "Composite Element" command redundant.


All diagram objects clearly (and umbiguously ((?sp)) )includes the word [glb]edges[/glb]. ... ... ???

bruce

51
Suggestions and Requests / Re: Attaching diagrams to elements
« on: September 01, 2007, 04:17:18 am »
Quote
In addition, I think you should be able to mark an element as composite without having to supply a diagram.  To me, isComposite is just a property of the element.  How the element is a composite can be shown in many ways - Class Diagram, Composite Structure Diagram etc...

In that case 150 votes.

bruce

p.s. re horses, yes!!! For Gordsake its the spring carival.
Champaign, pretty girls, speedy horses, pretty girls, more champaign... and what did we get "OrseFlu".... ... ... ...
apparently at last count its taken about 36mill out of the industry.

52
Suggestions and Requests / Re: A rose is a fish is an aardvaark
« on: August 31, 2007, 09:06:11 pm »
TEMP POST!  This is a question

Paolo,

I'm not sure what you are asking for.  

Is is a clear and unabiguous differentiation between diagram links and structurally decomposable elements?

bruce

p.s. I'm only here now due to horse flu.  >:(

53
Suggestions and Requests / Re: Wrap of concatenated mixed case
« on: August 22, 2007, 11:18:00 pm »
Hmm, mixed feelings.

SoftwareRequireme
ntsTestSpecificat
ion

indicates to me that the line is broken/wrapped,

SoftwareRequirements-
TestSpecification

also indicates wrapping but is harder to detect,

jmtcw
bruce

postthink

maybe
SoftwareRequirements...
TestSpecification

54
Suggestions and Requests / Re: German EA-Report
« on: July 31, 2007, 03:07:03 am »
Quote
No so much as against AustrALians


Watch out TK, I resemble that remark! Just because you live on the bottom of the world....

bruce

55
Suggestions and Requests / Re: Move dependencies between interfaces
« on: June 25, 2007, 11:54:56 pm »
TK,
AFAIK this has been a problem since the year dot.  The only quick way I've found around it is to use the zoom/pan tool to bring the node up to 300%+, select the dingo you want and zoom back out

hth
bruce

p.s. still as busy as a pup who's just discovered his tail.

56
Suggestions and Requests / Re: BPMN element improvements
« on: July 09, 2007, 03:27:43 am »
Me thoroughly too!
b

57
Suggestions and Requests / Re: Add an "assumptions" element
« on: July 06, 2007, 02:48:59 pm »
Reqt: The system shall model environmental (weather and or terrain) attenuation of the signal as zero.

This could properly trace to the correct element in the transmission chain of the simulator so that when, as I suspect you suspect, the requirement changes all affected elements can be identified.

I realise that this only addresses the specific example you mentioned.  It's just that I have never come across an assumption that "could not be resolved" to a fact one way or another.

bruce

58
Suggestions and Requests / Re: Add an "assumptions" element
« on: July 04, 2007, 03:43:39 am »
About 4 decades ago (seriously, this true) I was programminig the dreaded Olivetti teller machines.  I asked the client ( a building society ), "What is the MAXIMUM $value deposit you need to accept over the counter?".

The reply was, and I can probably remember the quote...

"Oh, most of them are pay packets and they are about $300"...

...

...

"Unless, of course, someone comes in and presents a property  settlement cheque and then it could be, oh, anywhere up to 3 million dollars"



AAAAAAAAAAAAAAAAAAARRRRRRRRRRRGGGGGGGGGGHHHHHHHH!!!!


bruce

59
Suggestions and Requests / Re: Add an "assumptions" element
« on: July 04, 2007, 03:24:21 am »
Quote
If an assumption imposes (generates) a constraint then, as you say, once deployed the constraint is what matters and should be traceable to the original assumption.


and on that I agree. If possible.  But then again ....
its just another excuse, not a solution.

bruce

60
Suggestions and Requests / Re: Add an "assumptions" element
« on: July 04, 2007, 03:17:05 am »
I disagree with the necessity to create a new element, stereotyped - or even categorised issue elements should give enough clarity to the nature of the issue ... that it is an assumption, which unless resolved to be false, given enough focus on it, remains <<default>> true.
And thus, the designers and developers will accept the assumption and design and develop accordingly.

Over thirty years in this game has given me enough (Oh how I hope) insight into the minds of the beasts that I react violently to the "silent acceptance of assumptions".

(YELLS) There is actually no such thing as an assumption! (/YELLS)

All "they" are, are an admission that some aspect of the requirement or environment hasn't been resolved.  They are at best, a question raised by the implementor of a system back towards the requirements, without (god forbid) another iteration of write/query/modify/confuse/assume/query ... at worst they are a pre-prepared limp wristed "excuse" that the  "project could not have possibly known that, and besides which, we told you we didn't know that, and we are so clever that having told you that we didn't know that we went on and spent 95% of the development budget grinning all the way that we have a pre-prepared excuse."  

I'M SORRY. THERE IS NO EXCUSE.

If an aspect of a project is recognised as being an "assumption" then it is behoven on the project management to  resolve it one way or the other. i.e. it is an ISSUE.

(Down and dirty)  "Assumptions" have only crept into reality as excuses - pre-prepared by lazy analysts, designers and project managers who can will not get out of their comfy blue chairs and FIND OUT THE ANSWER!!!  

Now if OTOH there is no answer, then perhaps the project should consider proceding to spend the shareholders money and the stakeholders interests under the ASSUMPTION that they are "Gods" and the customers/users/shareholders need not know the ways of gods      ........


There are no assumptions.  There are only unresolved issues.

bah!
bruce


Pages: 1 2 3 [4] 5 6 ... 94