[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
Title: | DECmcc user notes file. Does not replace IPMT. |
Notice: | Use IPMT for problems. Newsletter location in note 6187 |
Moderator: | TAEC::BEROUD |
|
Created: | Mon Aug 21 1989 |
Last Modified: | Wed Jun 04 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 6497 |
Total number of notes: | 27359 |
930.0. "Requirements for an AM" by COLBIN::BARCLAY () Wed Apr 17 1991 14:16
THE QUESTION:
Does anyone know where, could point me to, identify the manual (and its
location), respond with a reply, etc. of a complete list of the typical
requirements and/or features that AMs might implement? Maybe an
existing Functional Spec for example?
THE REASON: (all the gory details on why I need this...)
We are working with a customer who maybe interested in developing or
contracting with our EIS organization to develop an AM for UB LANs.
They (as I am) are very new to DECmcc and VAX/VMS for that matter.
We are are currently in the following loop:
Cust: How much does it cost to write an AM for UB?
DEC: Depends on how sophisticated an AM you want?
Cust: What's the difference in cost and functionality between
a LOW, MEDIUM, and HIGH AM?
DEC: That depends on what all the stuff on your UB LAN can
do? What do you have?
Cust: Lots of things, what are my possibilities then?
DEC: If your stuff is as a good as our stuff, then you could
have an AM as rich as phase 4/5 of DECnet; or if you want
something simpler, but still good you could do something
like SNMP AM... Which one would you like?
Cust: What's the differrence in cost? What's the difference
in functionality?
< Its here that we start to loop + thrash ... >
The plan to CONTROL-Y out of this thing is:
1. Get a bullet type list of generic requirements starting from the
simplest to the more/most complex. The key is to develop a complete
list (we have many sources for 'something like' lists).
2. Work with the customer and inside or outside UB expert to determine
what UB equipment can do of the list.
3. Work with the resultant list and the customer to determine
priorities like:
- I just have to have it
- It be nice (and it would be foolish not to have it)
- It be great unless I have to pay for it or wait
4. Do an estimate hopefully involving those that know from Digital,
eg. the group that writes Access Modules for a living.
The point of the whole exercise is to get a decent estimate for
something truly useful that won't waste alot of DECmcc knowledgeable
DEC talent before the customer understands what they want...
Key to this plan is step #1.
Does anyone know where, could point me to, identify the manual (and its
location), respond with a reply, etc. of a complete list of the typical
requirements and/or features that AMs might implement? Maybe an
existing Functional Spec for example?
Any help you could offer would be greatly appreciated!
Regards,
Tom
T.R | Title | User | Personal Name | Date | Lines |
---|
930.1 | lots of places to start | TOOK::CALLANDER | | Wed Apr 17 1991 18:32 | 9 |
| The guide to programing a mangement module is the best place to start,
as well as getting a copy of the V1.1 SRM. Chapter 15 in the SRM goes
though and explains the "common" directives such as SET and SHOW. This
notes file is also a good source of information. The keywords are extensive
but you might start with the docs first. In this conference you will find
a pointer to all of the current documentation which is available on
WORDY.
Good luck
|