[comp.software-eng] Request for SDE Usage Scenarios

gt@hpfcmr.HP.COM (George Tatge) (02/10/89)

I'm working with CIS (CASE Integration Services, a heterogeneous group
of software vendors, hardware vendors and users) which is focussed on
generalized integration technologies for software development.

A part of the requirements working group (RWG) effort is looking at scenario
analysis.  In simple terms, the question is, "if we had one of these
sophisticated environments, what would we do with it?"

Could anyone interested please post or e-mail me your ideas on
SPECIFIC SCENARIOS of activities that a fully integrated, 
object-oriented, distributed, heterogeneous, cradle to grave,
etc, etc, software development environment would be employed in?

In other words, if you had the "ideal" SDE, as a developer, project mgr.
R&D mgr., CEO, etc., what PRECISELY would you do with it?

Eg.--> R&D mgr comes in on Monday morning and queries as to source
object changes which occured over the weekend.  Notes that "Chainsaw"
Jane the notorious hacker has altered 112 source code objects in the
new missle launch control system which is on its way to final test
this week.  R&D mgr. then uses system to evaluate net worth of all
stocks and options, cashes out automatically, pulls up the resignation
letter she already has written and e-mails it to the appropriate people...

Anyway, you get the idea.  I'm looking for good, tough but reasonable
scenarios.  Thanks for any help!

g (Software, just say no) t

George Tatge
Software Engineering Systems Division
Hewlett Packard Company
Mail Stop 81
3404 E. Harmony Rd.
Ft. Collins CO, 80525-9599
(303) 229-3585
hplabs!hpfcla!gt
gt@hpfcses.hp.com

gt@hpfcmr.HP.COM (George Tatge) (02/10/89)

If you do not have scenarios in mind, how about example queries?

Given a system with the following generic properties (assume any
specific details are implemented or allowed as you desire), what
are the QUERIES you might wish to make of such a system and what
types of OBJECTS, RELATIONSHIPS, TASKS, METHODS, ABSTRACTIONS, might
you like to create and what would you like to do to/with them?

System Characteristics:

* Fine grain object repository

* System and user defined, typed relationships which are both uni and
bi directional and may be of any arity.

* User definable methods.

* Whatever else you need within three year technology reach.

----------------cut here-----------------

QUERIES:

;(examples)  
; "What percentage of system requirements are implemented in the current
;  release version of the system?"

; "Which project team member will be able to start on this part of the
;  design soonest?"

; "What is the cost-to-date for system test development?"

; "How much code do I have left to write to finish this requirement section?"

OBJECTS:

RELATIONSHIPS:

ABSTRACTIONS:

METHODS:

TASKS:

------------------cut here---------------

Thanks!

g (i should be in Maui) t


George Tatge
Software Engineering Systems
Hewlett Packard Company
3404 E. Harmony Rd.
Ft. Collins CO, 80525-9599
(303) 229-3585
hplabs!hpfcla!gt
gt@hpfcses.hp.com