| Title: | Europe-Swas-Artificial-Intelligence |
| Moderator: | HERON::BUCHANAN |
| Created: | Fri Jun 03 1988 |
| Last Modified: | Thu Aug 04 1994 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 442 |
| Total number of notes: | 1429 |
HELLO,
Here is a description of the PROJECTS DATABASE done by Jean-Michel
Grosgurin. The purpose of this database is to make available to eveybody
the list of projects done by the Ai community in the real world.
This database is still in enfancy in term of structure. Jean-Michel
is ready to listen to your inputs. So, feel free to comment on it.
Daniel
------------------------------------------------------------------------
COMPETENCY CIRCLES PROJECTS TRACKING SYSTEM
E/ACT - Valbonne
Introduction
1. Database description
2. Implementation issues
3. How to access the prototype
4. How to use the prototype
A. Appendix A : screens hardcopies
B. Appendix B : database design
INTRODUCTION
The idea of having a projects database comes from the need to know where new
technologies are beeing implemented at customers' sites, and eventually what are
the customers that can be used as reference accounts for a given technology.
If enough data can be gathered, it can be used as well for analyze purposes.
This document describes the information that could be tracked, and the way it
can be organized in a way that suits the query needs while preserving the
database flexibility.
What technology should be used to store and retrieve the data ?
There are several ways to keep track of reference accounts information :
a- Non structured
b- Poorly structured
c- Highly structured
a- Text information for each account : very easy to implement, good for
description, difficult to centralize, difficult to update, difficult to
access and retrieve
b- Videotex infobases : good for description, easy access and retrieval. Very
efficient in a network environment. Less structured data make it more
difficult to use complex criteria when searching information in the infobase
... unless you associate the infobase with a database
- Notesfiles : good for description, easy access and retrieval. Very
efficient in a network environment. Update possible only by adding new
information (historical approach) ==> retrieval and search more and more
difficult as time is going
- Text database : Good at all, but handling the quantitative metrics.
c- Relational database : Good at all, but handling large amounts of text data.
Not suitable to produce high quality documents. Very easy to handle complex
multi-criteria queries to find a reference. Very efficient in a network
environment provided that adequate front-end tools are used.
As the starting point was to keep track of Database and Transaction Processing
projects, the quantitative and multi-criteria aspects were very important. So
the relational database approach has been selected.
Moreover, if the Project Tracking System turns into a large scale project, it's
likely that TP tools will be used to front-end the database. This was another
reason why the database approach was selected.
1. DATABASE DESCRIPTION
A reference record is a set of information about one project. It's primarily
focused on one technology (for example : Transaction Processing), but the
database can keep track of projects for different technologies.
The information tracked is split into several parts :
a) KEY OF THE RECORD
Technology (T_ID), plus an internal number (REF_ID)
b) GENERAL INFORMATION
Account & project name, Office, Amount of business (HW, SW, Sces), country,
industry sector, development phase, mood of the customer, former vendor,
application description, account visitable or not, date of the last update and
extensive comments.
The information highlighted in sections a) and b) is to be controled in
reference tables, because it will be used to query the database (tables
TECHNOLOGY, COUNTRY, INDUSTRY, DEVT_PHASE, MOOD, VENDOR).
c) TECHNOLOGY SPECIFIC INFORMATION
This info is split into 3 parts, all allowing repeating groups :
- PRODUCT INFORMATION : for each technology, a set of products is defined in
reference table named PRODUCT. Amongst those, the products used in the project
tracked are listed and kept in a separate sub-table.
- KEYWORD INFORMATION : for each technology, a set of keywords is defined in a
reference table named KEYWORD. Amongst those, the keywords relevant for the
project tracked are listed and kept in a separate sub-table. Keywords associate
more high level concepts to the project tracked. They complement the product
information and give an alternate means to query the database (examples of
keywords : CLUSTER, 24/24, ...).
- QUANTITATIVE METRICS : for each technology, a set of metrics can be defined in
a reference table named METRIC. They consist in a metric short name and
description. If available, the metrics can be tracked for the project in order
to have an idea of the volumes involved (examples for Transaction Processing :
VUPS of the configuration, TPS, Database Size ...) and kept in a separate sub
table.
d) COMPETITIVE INFORMATION
For each project, the names of the competitors are tracked (and selected from a
reference table named VENDOR) and kept in a separate sub table.
e) DIGITAL CONTACTS INFORMATION
For each project, a list of the DIGITAL contacts is defined, with mention of
their EMAIL address, DTN number and function, and kept in a separate sub table.
The rule could be : if a project is tracked in the database with another
development phase than "JUST SOLD", "LOST" or "FAILED" then it can be mentioned
freely to customers. To organize a visit or have an udpate on the status of the
project, one has to go through the contacts.
Note :
This design gives a good flexibility, as operations like adding a new product,
a new keyword or a new metric only imply adding a new record in a table, and not
changing the database definition neither the front-end application.
Advanced ways of querying the database will make this design totally transparent
to the user. Questions such as : "Find me a project on TP, with more than 15
VUPS, more than 200 active users, a database size greater than 600 Mb, using
ACMS and Rdb in a CLUSTER environment and won over IBM or TANDEM" can be handled
easily.
2. IMPLEMENTATION ISSUES
a) ACCESS CONTROL
Access to the projects database can be controlled by an automatic sign in
mechanism using the username.
Noone can have access to the application front-ending the database unless he is
explicitely authorized to so and registered in a security table.
Having read access to the database allows to query the whole database, for all
projects and all technologies.
Having write access to the database allows to update/create information about
projects of :
- his own country
- the (one) technology he's responsible for at the country level.
b) APPLICATION LAYOUT
The front end-part of the application has mainly 2 parts :
- an update screen, allowing users that are granted write access to
create/update reference projects information. All the information that have to
be validated against reference tables (COUNTRY, INDUSTRY ...) can be selected
from pop-up windows.
- a query interface :
* a first screen allows to formulate requests to the database, filling in blancs
and picking up values from reference lists.
* when the answer to the request has been given, all the projects are displayed
in scrolling mode, with a subset of the available information. To browse all the
information, another screen can zoom on a particular project.
Some administration screens have obviously to be added to maintain the reference
tables of the database and the security access list.
c) DISTRIBUTED IMPLEMENTATION
The application has to be distributed in such a way that users can access the
database (centralized) through the network from remote locations.
d) PROTOTYPE
A prototype implementing the above mentioned ideas has been developped. His use
on a small scale should reveal whether or not such a system can be useful.
Information on how to access the prototype system and how to use it are given
here after. Hardcopies of screens and detailed information on the database
design are provided in Appendix A and B at the end of this document.
3 - HOW TO ACCESS THE PROTOTYPE
The prototype of the "Project Tracking System" is a RALLY application accessing
an Rdb database.
There are 2 ways of running this prototype :
a) SET HOST
A captive account has been created on HERON (HERON is the alias name of a
cluster of 2 VAX8550 in Valbonne)
The USERNAME is PROJECTS_CC, no password.
You will be asked to enter your badge number to identify yourself.
The first time you will use the application, you will be also asked for some
personal information (first name, last name) and for 2 important items :
- your country
- your technology
When you are finished with this screen, a registration request will be sent
automatically and you will be (later) granted read access to the database.
Should you have to update data belonging to your country and technology, then
send a mail as stated on the form and you will be granted write access.
Performance might not be ideal, depending on the speed of the links between your
location and Valbonne.
b) Local RALLY and Remote Rdb
Prerequisite : Have RALLY V2.1-A and RDB 3.0-B run time installed on your
system. Make sure that HERON is known from your local node.
Then copy from : HERON"PROJECTS_CC"::REF.SAV a save set containing :
REF_RUN.RGA the RALLY application file (no symbol table ==> not editable)
REF.COM a procedure assigning logical names and running the application
If you put those two files in your SYS$LOGIN, you an run the application as it
is by doing @REF.
If you do not put them in SYS$LOGIN, you have to change the LOCATION logical
name in the REF.COM command procedure, in order to have it point to the .RGA
file location. You can also define your preferred printer.
The behavior of the application will be exactly the same, but performance will
be better than if you use set host.
4 - HOW TO USE THE PROTOTYPE
Two functionalities are provided : a query interface to retrieve data from the
database, and an update interface to create/update data in the database
a) QUERY
Anybody that has access to the application can register and grant himself read
access to the database. After the prompt for the badge number, the query form is
displayed and allows to do multi-criteria queries to the database.
To move from a field to another in the query form, use Tab. or Return (next
field), and F12 (previous field).
In each field of the form, you can either :
- specify a value directly in the field (*) :
It means that you are interested only in records for which the field value is
EQUAL to the specified value.
- specify an "extended query" on the field by pressing Find key :
It means that you want to specify a query expression other than EQUAL.
When you have pressed the Find key in a field, a command line appears in the
left down corner of the form : Enter query expression
You can then use one of the following operators to specify the extended query :
- for NUMBER and DATE fields : > , >= , < , <= , =
- for CHAR fields : all above, plus STARTS, CONTAINS, MATCHES
You can combine these operators using the conjunctions AND and OR, and the
negation NOT. On line Help is available when in the command line (press Help).
To go back to the field once the query expression is entered, press Return.
(*) List of valid values are provided for a field each time the icon
GOLD L AVAILABLE is displayed in the right down corner of the form.
- To display the pop-up window in the middle of the screen, use GOLD L
- If you want to restrict the list of values to the values starting
with a character string, type in the string in the field and then
press GOLD L (this function is similar to the ALLIN1 GOLD L facility)
- To move within the list of values, use down arrow and up arrow to
scroll records, Next and Prev keys to scroll pages.
- To select a value from the list of values, press Select or Enter.
Examples of valid extended query expressions :
NUMBER : > 100
>= 5 and <= 10
< 15 or >= 24
(> 5 and < 10) or > 20
= 2 or >= 5
DATE : > 1-OCT-1989
> 20-OCT-1989 and <= 31-DEC-1989
CHAR : > C (case sensitive, upper case first)
STARTS A (case sensitive)
STARTS B or = BULL
NOT STARTS B
CONTAINS iBm (case insensitive)
MATCHES *BM* (case sensitive)
It's possible to specify query expressions (exact match or extended query) for
every field in the form. Note that all the query expressions are ANDed together.
There is *NO WAY* to do a logical OR across several fields (eg. COUNTRY = FRANCE
or INDUSTRY = MANUFACTURING).
In particular, when two products are specified, it means that you expect to get
back projects where both products are used together. Note that in this case, you
might also do a logical OR query on the field PRODUCT because only one field is
involved in the logical OR (PRODUCT = RDB or PRODUCT = ACMS can be specified as
an extended query on the field PRODUCT).
Finally, when all the query expressions have been specified, you execute the
query by pressing Enter.
When the records are pulled back from the database, you can :
- scroll through the collection of records using arrow keys (up and down),
- select one of the records to have more information about it using Select key.
In this case, another form is displayed giving detailed information on the
project selected, inclusing an extensive comment.
- reset the screen in order to make another query, using Find key.
In this case, the screen is cleared, and you can again specify query
expressions.
In case no matching records are found in the database, a message is issued :
+------------------------------------------------------------------------------+
| There is no matching record in the database. Press Return |
+------------------------------------------------------------------------------+
It means that your query was too restrictive : you have to drop some conditions
on the fields and execute the query again, until you have some records matching
all the conditions that you have required.
To drop a condition on a field, you have to do the following :
- in case of an exact match, clear the value specified in the field using key
F3, (same key as ALLIN1 for delete word)
- in case of an extended query, press Find key when in the field to go back to
the command line, and then clear the expression specified there using key F3
several times (until the line is blanked), or key F9 to clear the whole line
altogether.
To leave the query form and exit the application, press F8.
b) UPDATE
To be allowed to update the database requires to be granted write access (send a
mail to HERON::PROJECTS_CC as stated in the registration form).
When it's the case, you will be allowed to create/update records for your
country and the technology that you specified in the registration form.
After the prompt for your badge number, a menu with 3 choices appears :
1. Update the database
2. Query the database (function offered to read-only users - described above).
3. Exit
If you select the update option, then you are left browsing the collection of
records belonging to your country and your technology. The form layout looks
almost exactly like the detailed query form.
To scroll through the collection of records, use arrow keys (up and down).
If there are too many records and scrolling one record at a time becomes
tedious, you can query the database specifying query expressions in the same way
as you could do in the query form. List of values are available when the icon
GOLD L AVAILABLE is there, and work in the same way (*).
You can then update any visitable field and change its value.
When you leave a record either to scroll to another record, or to query the
database, all the changes made in the record that you are leaving are made
permanent in the database (they are 'committed').
(*) There is an enhancement for the list of values in the update form.
If you type in the first letters of a value in a field, and the string
uniquely identifies a value in the list, then if you press Return or
GOLD L, the value will automatically be picked up from the list.
If more than one value starts with the first letters specified, then
they are displayed in the list. You can pick up a value using Enter of
Select key, or quit the pop-up window using F8.
If no value matches, then you are left creating a new entry in the
reference table. Fill in the value there and press Enter to confirm.
This way you will have simultaneously created a new entry in the list,
and associated this value to the current record you are editing.
Finally, in case you made a simple GOLD L to browse the list, and then
realized that the value you would like is not there, you can still
create a new entry in the list using Insert key. To confirm and pick
the value press Enter or Select.
To create a new record, press Insert key. A reference number will automatically
be allocated to the record, and you will be left filling in the other fields.
Similarly, use Insert key to create new entries in the repeating groups :
- TECHNOLOGY SPECIFIC,
- PRODUCTS,
- KEYWORDS,
- COMPETITORS,
- DIGITAL CONTACTS.
To remove an entry from a repeating group, use Remove key.
When the cursor is in the top most part of the screen (above repeating groups),
using Remove key will remove the whole record from the database.
Think twice before doing it !
Anyway a Y/N menu will prompt you to confirm the removal in order to prevent
any mis-usage of the Remove key.
To exit from the update form making permanent in the database all the changes
made to the last record edited, press F10 or Enter.
To quit the form, discarding the changes made to the last record, press F8.
If you want to save the changes at any time, without exiting the form, press Do
key and type in the command line : commit.
If you want at any time abort the changes made to the top most part of the
current record, press Do key and type in the command line : rollback.
Last, if you want to edit comments about the current record (to give details
about the configuration, or any information that you could not enter in the
other fields), type Y in the last field of the form : a sub-form appears,
allowing you to type in 10 lines of text.
In this subform, use arrow keys to go up and down one line (Tab. / Return and
F12 work as well). To return to the main update form, type GOLD F12 from any
place in the subform. If you are in the last line, Return key will get you to
the next record in the database. If you are in the first line, key F12 or up
arrow will get you in the Y/N comment field.
c) HELP FACILITY :
On-line help is provided in the application (press Help key). It's a form
specific key reminder :
PROJECT TRACKING SYSTEM KEYS REMINDER UPDATE FORM
Move to next field : Tab. or Return
Back to previous field : F12
Move to last field : PF1 Return
Move to first field : PF1 F12
Exit the form (commit) : Enter
Quit the form (rollback): F8
Insert a new record : Insert here (previous updates are committed)
Delete a record : Remove (confirm menu appears)
Scroll to next record : Down arrow
Scroll to prev record : Up arrow
Scroll to next page : Next
Scroll to prev page : Prev
PROJECT TRACKING SYSTEM KEYS REMINDER QUERY FORM
Specify a criteria : Move along the fields using Tab. and F12
Execute a query : Enter
Scroll to next record : Down arrow
Scroll to prev record : Up arrow
Scroll to next page : Next
Scroll to prev page : Prev
Select one record : Select
Do another query : Find (it will reset the screen)
Quit any form : F8
How to specify complex query criteria :
- Criteria 'equals to' : Fill in the value in the field
- Other criteria : Press Find key when in the field.
Then, on the command line that appears, use one of the following operators in
order to specify the extended query expression :
< , <=, >, >= for NUMBER or DATE fields
starts, contains, matches for CHAR fields
Example :
After have pressed the Find key while in the field Former Vendor, type in :
Enter query expression : starts IBM
and you will get all the records in the database whose former vendor was IBM,
no matter what kind of hardware were there (AS400, 3090 ...)
APPENDIX 1 Hardcopies of screens
UPDATE SCREEN :
Before any information is filled in :
+--------------------------+-----------++------------------------------+-------+
| PROJECTS TRACKING SYSTEM |27-Nov-1989||Jean-Michel GROSGURIN | QUERY |
+--------------------------+-----------++------------------------------+-------+
+-------+------------------- ACCOUNT INFORMATION ----------------------------+
|Office | |Code TP FRANCE |
|Account| |Industry : |
|Project| |HW/SW/Sces(K$): / / |
|Visit ?| Mood: |Former vendor : |
+-------+--- Application Description ----+Devt Phase : |
| |
+--------------------------- TECHNOLOGY SPECIFIC ----------------------------+
| |
| |
+--------+---------------------------------------------------------------------+
|PRODUCTS| |
+--------+---------------------------------------------------------------------+
|KEYWORDS| |
+--------+------------++-----------------------------------+----------+--------+
| COMPETITORS || DIGITAL CONTACTS EMAIL address |Telephone |Function|
+---------------------++-----------------------------------+----------+--------+
| || |
| || |
+---------------------++-------------------------------------------------------+
Do you want to add a comment [Y/N] :
Screen after filling in the information :
+--------------------------+-----------++------------------------------+-------+
| PROJECTS TRACKING SYSTEM |27-Nov-1989||Jean-Michel GROSGURIN | UPDATE|
+--------------------------+-----------++------------------------------+-------+
+-------+------------------- ACCOUNT INFORMATION ----------------------------+
|Office | PARIS |Code TP1 FRANCE |
|Account| FICTIVE |Industry : MANUFACTURING |
|Project| Reseau d'Agences |HW/SW/Sces(K$): 10 / 10 / 10 |
|Visit ?| Y Mood: NEUTRAL |Former vendor : BULL DPS8 |
+-------+--- Application Description ----+Devt Phase : TESTING |
|Order entry sample application |
+--------------------------- TECHNOLOGY SPECIFIC ----------------------------+
| DBSIZE 600 NBTERM 150 TPS 5.5 |
| NBDISK 5 NBUSER 80 VUPS 15 |
+--------+---------------------------------------------------------------------+
|PRODUCTS|ACMS RALLY RDB |
+--------+---------------------------------------------------------------------+
|KEYWORDS|365 DAYS CLUSTER DATABASE DECTP |
+--------+------------++-----------------------------------+----------+--------+
| COMPETITORS || DIGITAL CONTACTS EMAIL address |Telephone |Function|
+---------------------++-----------------------------------+----------+--------+
|BULL DPS8 ||Pierre DUPONT @PAO 858-YYYY SALES |
|IBM 3090 ||Jean DURAND @PAO 858-XXXX SWAS |
+---------------------++-------------------------------------------------------+
Do you want to add a comment [Y/N] : N
QUERY INTERFACE
Screen as it appears when the user calls it :
+--------------------------+-----------++------------------------------+-------+
| PROJECTS TRACKING SYSTEM |27-Nov-1989||Jean-Michel GROSGURIN | QUERY |
+--------------------------+-----------++------------------------------+-------+
Number of accounts selected :
+------------------------------------------------------------------------------+
|Techn. : Updated: Country : |
|Account: Industry : |
|Project: Former Vendor: |
|Bus(K$): Mood: Devt Phase : |
+- Products -+--- Keywords ---+- Metrics Values -+-- Competitors ------+-------+
| | | | |Visit ?|
| | | | | (Y/N)|
+------------+----------------+------------------+---------------------+-------+
After the user has filled in some search criteria :
+--------------------------+-----------++------------------------------+-------+
| PROJECTS TRACKING SYSTEM |27-Nov-1989||Jean-Michel GROSGURIN | QUERY |
+--------------------------+-----------++------------------------------+-------+
Number of accounts selected : 0
+------------------------------------------------------------------------------+
|Techn. : TP Updated: Country : FRANCE |
|Account: Industry : |
|Project: Former Vendor: |
|Bus(K$): Mood: Devt Phase : |
+- Products -+--- Keywords ---+- Metrics Values -+-- Competitors ------+-------+
|ACMS |CLUSTER | TPS * | |Visit ?|
|RDB | | | |Y (Y/N)|
+------------+----------------+------------------+---------------------+-------+
* Enter Query Expression : > 10
After the user has received the answer from the database :
Note that the answer does not correspond to the query criteria, because
the sample database does not contain enough records.
+--------------------------+-----------++------------------------------+-------+
| PROJECTS TRACKING SYSTEM |27-Nov-1989||Jean-Michel GROSGURIN | BROWSE|
+--------------------------+-----------++------------------------------+-------+
Number of accounts selected : 4
+------------------------------------------------------------------------------+
|Techn. : TP1 Updated: 27-Nov-1989 Country : FRANCE |
|Account: FICTIVE Industry : MANUFACTURING |
|Project: Reseau d'Agences Former Vendor: BULL DPS8 |
|Bus(K$): 30 Mood:NEUTRAL Devt Phase : TESTING |
+- Products -+--- Keywords ---+- Metrics Values -+-- Competitors ------+-------+
|ACMS |365 DAYS | DBSIZE 600 |BULL DPS8 |Visit ?|
|ACMS |365 DAYS | DBSIZE 600 |BULL DPS8 |Y (Y/N)|
+------------+----------------+------------------+---------------------+-------+
+------------------------------------------------------------------------------+
|Techn. : TP2 Updated: 24-Nov-1989 Country : FRANCE |
|Account: Industry : MANUFACTURING |
|Project: Former Vendor: ICL |
|Bus(K$): 71 Mood:HAPPY Devt Phase : TESTING |
+- Products -+--- Keywords ---+- Metrics Values -+-- Competitors ------+-------+
|ACMS |DECTP | |IBM AS 400 |Visit ?|
|ACMS |DECTP | |IBM AS 400 |Y (Y/N)|
+------------+----------------+------------------+---------------------+-------+
+------------------------------------------------------------------------------+
|Techn. : TP4 Updated: 24-Nov-1989 Country : FRANCE |
|Account: Industry : |
|Project: Former Vendor: |
|Bus(K$): Mood: Devt Phase : |
+- Products -+--- Keywords ---+- Metrics Values -+-- Competitors ------+-------+
|ACMS |DECTP | DBSIZE 100 |BULL DPS8 |Visit ?|
|ACMS |DECTP | DBSIZE 100 |BULL DPS8 | (Y/N)|
+------------+----------------+------------------+---------------------+-------+
+------------------------------------------------------------------------------+
|Techn. : TP5 Updated: 27-Nov-1989 Country : FRANCE |
|Account: account Industry : AEROSPACE |
|Project: project Former Vendor: IBM AS 400 |
|Bus(K$): 60 Mood:VERY POSITIVE Devt Phase : JUST SOLD |
+- Products -+--- Keywords ---+- Metrics Values -+-- Competitors ------+-------+
|ACMS |AUTOMATS | DBSIZE 1000 |TANDEM |Visit ?|
|ACMS |AUTOMATS | DBSIZE 1000 |TANDEM |Y (Y/N)|
+------------+----------------+------------------+---------------------+-------+
After the user has selected the first project
to have more information
+--------------------------+-----------++------------------------------+-------+
| PROJECTS TRACKING SYSTEM |27-Nov-1989||Jean-Michel GROSGURIN | BROWSE|
+--------------------------+-----------++------------------------------+-------+
+-------+------------------ PROJECT INFORMATION -----------------------------+
|Office |PARIS |MANUFACTURING FRANCE |
|Account|FICTIVE |Former vendor : BULL DPS8 |
|Project|Reseau d'Agences |Business : K$ 30 (10 /10 /10 )|
|Visit |Y Mood: NEUTRAL |Dvt Phase : TESTING |
+-------+-------------------------------+--------------------------------------+
|Order entry sample application |
+--------------------------- TECHNOLOGY SPECIFIC ----------------------------+
| DBSIZE 600 NBTERM 150 TPS 5.5 |
| NBDISK 5 NBUSER 80 VUPS 15 |
+--------+---------------------------------------------------------------------+
|PRODUCTS| ACMS RALLY RDB |
+--------+---------------------------------------------------------------------+
|KEYWORDS| 365 DAYS CLUSTER DECTP |
+--------+------------++-----------------------------------+----------+--------+
| COMPETITORS || DIGITAL CONTACTS EMAIL address |Telephone |Function|
+---------------------++-----------------------------------+----------+--------+
|BULL DPS8 ||Pierre DUPONT @PAO 858-YYYY SALES |
|IBM 3090 ||Jean DURAND @PAO 858-XXXX SWAS |
+---------------------++-------------------------------------------------------+
Do you want to add a comment [Y/N] : N
APPENDIX 2 Database design
!-------------------------------------------------------------------------------
!
! ------- -------- ---------- -------- ------
! COUNTRY INDUSTRY DEVT_PHASE MOOD VENDOR
! ------- -------- ---------- -------- ------
! | | | | |
! | +-----------------+ | +---------+ |
! +-------------------------------+ | | | +--------- (former) ----+
! | | | | |
! v v v v V
! ---------
! +-----------------------(*)-------> REFERENCE
! | ---------
! | | | | | |
! | +-------------------------------+ | | | +--------------------+
! | | +-----------------+ | +-----------+ |
! | | | | | |
! | v v v v v
! | ----------- ----------- ----------- -------------- -----------
! | REF_PRODUCT REF_KEYWORD REF_METRIC REF_COMPETITOR REF_CONTACT
! | ----------- ----------- ----------- -------------- -----------
! | ^ ^ ^
! | | | |
! | | | |
! | ----------- ----------- -----------
! | PRODUCT KEYWORD METRIC
! | ----------- ----------- -----------
! | ^ ^ ^
! | | | |
! | | ----------- |
! | +---------- TECHNOLOGY ---------+
! +-------------- -----------
!
! (*) this link to exist if a reference is primarily single technology
!
!-------------------------------------------------------------------------------
!-------------------------------------------------------------------------------
! Database definition
!-------------------------------------------------------------------------------
!create schema file REFERENCE_DB ;
!-------------------------------------------------------------------------------
! Domains definition
!-------------------------------------------------------------------------------
create domain T_ID is CHAR (2) ; ! technology id
create domain TECHNOLOGY is CHAR (30) ; ! technology description
create domain METRIC is CHAR (6) ; ! metric (for each T_ID)
!***** possible values : VUPS, TPS, NBDISK, DBSIZE, NBTERM, NBUSER ...
create domain METRIC_DEFINITION is CHAR (30) ; ! metric definition
create domain METRIC_VALUE is INTEGER(2) ; ! metric value
create domain REF_ID is SMALLINT ; ! internal number
create domain ACCOUNT is CHAR (30) ; ! account name
create domain PROJECT is CHAR (30) ; ! project name
create domain DOLLAR is INTEGER ; ! $ made on a project
create domain VENDOR is CHAR (20) ; ! computer vendor name
create domain OFFICE is CHAR (30) ; ! DIGITAL office name
create domain EMAIL is CHAR (35) ; ! EMAIL address
create domain DTN is CHAR (10) ; ! Telephone DTN number
create domain FUNCTION is CHAR (5) ; !
!***** possible values : SALES, SWAS, MKTG, EDU ...
create domain COUNTRY is CHAR (20) ; ! Country name
create domain INDUSTRY is CHAR (20) ; ! type of industry
!***** possible values : to be defined
create domain DEVT_PHASE is CHAR (20) ; !
!***** possible values : JUST SOLD, DEVELOPMENT, TESTING, PRODUCTION
create domain MOOD is CHAR (20) ; ! how the cust. feels
!***** possible values : VERY POSITIVE, HAPPY, NEUTRAL, UNHAPPY
create domain BOOLEAN is CHAR (1) ; ! Y or N
create domain KEYWORD is CHAR (15); ! for each T_ID
!***** possible values : CLUSTER, DISTRIBUTED, 24/24, BENCHMARK,AGENT...
create domain PRODUCT is CHAR (10) ; ! for each T_ID
!***** possible values : ACMS, RDB, ...
create domain DESCRIPTION is CHAR (78) ; ! any description
create domain BADGE is CHAR (6) ; ! badge number
create domain NAME is CHAR (30) ; ! name
create domain USERNAME is CHAR (12) ; ! VMS username
create domain ACCESS is CHAR (5) ; ! READ , WRITE or CTRL
!
!
!-------------------------------------------------------------------------------
! Tables definition
!-------------------------------------------------------------------------------
create table TECHNOLOGY (
T_ID T_ID,
TECHNOLOGY TECHNOLOGY,
MAX_REF_ID REF_ID
) ;
create table PRODUCT (
T_ID T_ID,
PRODUCT PRODUCT
) ;
create table KEYWORD (
T_ID T_ID,
KEYWORD KEYWORD
) ;
create table METRIC (
T_ID T_ID,
METRIC METRIC
METRIC_DEFINITION
) ;
create table REFERENCE (
T_ID T_ID,
REF_ID REF_ID,
ACCOUNT ACCOUNT,
PROJECT PROJECT,
HARDWARE DOLLAR,
SOFTWARE DOLLAR,
SERVICES DOLLAR,
FORMER_VENDOR VENDOR,
OFFICE OFFICE,
COUNTRY COUNTRY,
INDUSTRY INDUSTRY,
APPL_DESCRIPTION DESCRIPTION,
DEVT_PHASE DEVT_PHASE,
MOOD MOOD,
VISITABLE BOOLEAN,
COMMENT DESCRIPTION,
COMMENT2 DESCRIPTION,
COMMENT3 DESCRIPTION,
COMMENT4 DESCRIPTION,
COMMENT5 DESCRIPTION,
COMMENT6 DESCRIPTION,
COMMENT7 DESCRIPTION,
COMMENT8 DESCRIPTION,
COMMENT9 DESCRIPTION,
COMMENT10 DESCRIPTION,
LAST_UPDATE DATE
) ;
!
create table COUNTRY (COUNTRY COUNTRY) ;
create table INDUSTRY (INDUSTRY INDUSTRY) ;
create table DEVT_PHASE (DEVT_PHASE DEVT_PHASE) ;
create table MOOD (MOOD MOOD) ;
create table VENDOR (VENDOR VENDOR) ;
create table REF_CONTACT (
T_ID T_ID,
REF_ID REF_ID,
CONTACT_EMAIL EMAIL,
CONTACT_DTN DTN,
CONTACT_TYPE FUNCTION
) ;
create table REF_PRODUCT (
T_ID T_ID,
REF_ID REF_ID,
PRODUCT PRODUCT
) ;
create table REF_COMPETITOR (
T_ID T_ID,
REF_ID REF_ID,
COMPETITOR VENDOR
) ;
create table REF_KEYWORD (
T_ID T_ID,
REF_ID REF_ID,
KEYWORD KEYWORD
) ;
create table REF_METRIC (
T_ID T_ID,
REF_ID REF_ID,
METRIC METRIC,
METRIC_VALUE METRIC_VALUE
) ;
create table ACCESS_RIGHT (
BADGE BADGE,
LAST_NAME LAST_NAME,
FIRST_NAME FIRST_NAME,
USERNAME USERNAME,
COUNTRY COUNTRY,
T_ID T_ID, !one person will update one technology
ACCESS ACCESS
) ;
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 171.1 | Some interesting news | HERON::GROSGURIN | Jean-Michel GROSGURIN E/ACT Valbonne | Fri Feb 09 1990 14:09 | 27 |
Pascal Coutier and I have sit down together this morning, and transfered all the AI references that previously were in Pascal's database into the Projects Tracking System database. So there are now 83 AI projects records in the database, Pascal will explain you in a reply to this note how we handled the AI specific details. An updated version of the user's guide is put in the next reply as well. Don't use the one Daniel placed in 171.0 any more. The following concerns only those who use the PROJECTS TRACKING SYSTEM in "client/server" mode (local RALLY, remote database). There have been modifications made in the kit, so please copy the new kit and use it : it now contains 3 files that supersedes the 2 previous ones. Each time there will be a new kit, it will of course be available over the net in the PROJECTS_CC directory, and I will put an entry here to advertise the new version. Now it seems that AI is leading this database, in terms of number of records !! Hope it will help, Regards Jean-Michel | |||||
| 171.2 | New version of the User's guide | HERON::GROSGURIN | Jean-Michel GROSGURIN E/ACT Valbonne | Fri Feb 09 1990 14:14 | 845 |
COMPETENCY CIRCLES PROJECTS TRACKING SYSTEM
E/ACT - VALBONNE
Introduction
1. Database description
2. Implementation issues
3. How to access the prototype
4. How to use the prototype
A. Appendix A : screens hardcopies
B. Appendix B : database design
Jean-Michel GROSGURIN
E/ACT - Valbonne
INTRODUCTION
The idea of having a projects database comes from the need to know where new
technologies are beeing implemented at customers' sites, and eventually what are
the customers that can be used as reference accounts for a given technology.
If enough data can be gathered, it can be used as well for analyze purposes.
This document describes the information that could be tracked, and the way it
can be organized in a way that suits the query needs while preserving the
database flexibility.
What technology should be used to store and retrieve the data ?
There are several ways to keep track of projects information :
a- Non structured
b- Poorly structured
c- Highly structured
a- Text information for each account : very easy to implement, good for
description, difficult to centralize, difficult to update, difficult to
access and retrieve
b- Videotex infobases : good for description, easy access and retrieval. Very
efficient in a network environment. Less structured data make it more
difficult to use complex criteria when searching information in the infobase
... unless you associate the infobase with a database
- Notesfiles : good for description, easy access and retrieval. Very
efficient in a network environment. Update possible only by adding new
information (historical approach) ==> retrieval and search more and more
difficult as time is going
- Text database : Good at all, but handling the quantitative metrics.
c- Relational database : Good at all, but handling large amounts of text data.
Not suitable to produce high quality documents. Very easy to handle complex
multi-criteria queries to find a reference. Very efficient in a network
environment provided that adequate front-end tools are used.
As the starting point was to keep track of Database and Transaction Processing
projects, the quantitative and multi-criteria aspects were very important. So
the relational database approach has been selected.
The database has been designed in a way allowing to track projects of different
technologies, though. The immediate pay-back for having a single database is
that horizontal types of queries (on products, industries ...) will be
supported and return answers spanning across several technologies.
Although not beeing able to take into account the specific items of a particular
technology as accurately as a technology specific design, it should be flexible
enough to cope with most of them.
1. DATABASE DESCRIPTION
A project record is a set of information about one project. It's primarily
focused on one technology (for example : Transaction Processing), but the
database can keep track of projects for different technologies.
The information tracked is split into several parts :
a) KEY OF THE RECORD
Technology (T_ID), plus an internal number (REF_ID)
b) GENERAL INFORMATION
Account & project name, Office, Amount of business (HW, SW, Sces), country,
industry sector, development phase (*), mood of the customer, former vendor,
application description, account visitable or not, date of the last update and
extensive comments.
The information highlighted in sections a) and b) is to be controled in
reference tables, because it will be used to query the database (tables
TECHNOLOGY, COUNTRY, INDUSTRY, DEVT_PHASE, MOOD, VENDOR).
c) TECHNOLOGY SPECIFIC INFORMATION
This info is split into 3 parts, all allowing repeating groups :
- PRODUCT INFORMATION : for each technology, a set of products is defined in
reference table named PRODUCT. Amongst those, the products used in the project
tracked are listed and kept in a separate sub-table.
- KEYWORD INFORMATION : for each technology, a set of keywords is defined in a
reference table named KEYWORD. Amongst those, the keywords relevant for the
project tracked are listed and kept in a separate sub-table. Keywords associate
more high level concepts to the project tracked. They complement the product
information and give an alternate means to query the database (examples of
keywords : CLUSTER, 24/24, ...).
- QUANTITATIVE METRICS : for each technology, a set of metrics can be defined in
a reference table named METRIC. They consist in a metric short name and
description. If available, the metrics can be tracked for the project in order
to have an idea of the volumes involved (examples for Transaction Processing :
VUPS of the configuration, TPS, Database Size ...) and kept in a separate sub
table.
(*) The development phase may be described using technology specific terms.
In that case, this item will turn into a technology specific one.
d) COMPETITIVE INFORMATION
For each project, the names of the competitors are tracked (and selected from a
reference table named VENDOR) and kept in a separate sub table.
e) DIGITAL CONTACTS INFORMATION
For each project, a list of the DIGITAL contacts is defined, with mention of
their EMAIL address, DTN number and function, and kept in a separate sub table.
Until any other rule is adopted, the information contained in the database is
for internal use. Only the contacts can tell whether a project can be quoted or
not.
Note :
This design gives a good flexibility, as operations like adding a new product,
a new keyword or a new metric only imply adding a new record in a table, and not
changing the database definition neither the front-end application.
Advanced ways of querying the database will make this design totally transparent
to the user. Questions such as : "Find me a project on TP, with more than 15
VUPS, more than 200 active users, a database size greater than 600 Mb, using
ACMS and Rdb in a CLUSTER environment and won over IBM or TANDEM" can be handled
very easily.
2. IMPLEMENTATION ISSUES
a) ACCESS CONTROL
Access to the projects database has to be controlled in order to protect data.
Noone can have access to the application front-ending the database unless he is
explicitely authorized to do so and registered in a security table.
Having read access to the database allows to query the whole database, for all
projects and all technologies.
Having write access to the database allows to update/create information about
projects of :
- his own country
- the (one) technology he's responsible for at the country level.
The competency circles coordinators will be able to update data of all the
countries for a particular technology.
If it happens that a single person is responsible for several technologies at
the country level, the database can be easily modified to handle this situation.
b) APPLICATION LAYOUT
The front end-part of the application has mainly 2 parts :
- an update screen, allowing users that are granted write access to
create/update reference projects information. All the information that have to
be validated against reference tables (COUNTRY, INDUSTRY ...) can be selected
from pop-up windows.
- a query interface :
* a first screen allows to formulate requests to the database, filling in blancs
and picking up values from reference lists.
* when the answer to the request has been given, all the projects are displayed
in scrolling mode, with a subset of the available information. To browse all the
information, another screen can zoom on a particular project.
Some administration screens have obviously to be added to maintain the reference
tables of the database and the security access list.
In addition, a mailing facility, that can be used within the application, is
provided in order to send by E-Mail to any addressee the logical content of a
screen ("logical" meaning that if the screen contains several pages of
information, they will all be part of the mail message).
c) DISTRIBUTED IMPLEMENTATION
The application has to be distributed in such a way that users can access the
(centralized) database through the network from remote locations.
d) PROTOTYPE
A prototype implementing the above mentioned ideas has been developped. His use
on a small scale should reveal whether or not such a system can be useful.
Information on how to access the prototype system and how to use it are given
here after. Hardcopies of screens and detailed information on the database
design are provided in Appendix A and B at the end of this document.
Section 3 & 4 focus on how to access and use the prototype.
3 - HOW TO ACCESS THE PROTOTYPE
The prototype of the "Project Tracking System" is a RALLY application accessing
an Rdb database.
There are 2 ways of running this prototype :
a) SET HOST
A captive account has been created on HERON (HERON is the alias name of a
cluster of 2 VAX8550 in Valbonne)
The USERNAME is PROJECTS_CC, no password.
You will be asked to enter your badge number to identify yourself.
The first time you will use the application, you will be also asked for some
personal information (first name, last name) and for 2 important items :
- your country
- your technology
When you are finished with this screen, a registration request will be sent
automatically and you will be (later) granted read access to the database.
Should you have to update data belonging to your country and technology, then
request it in the comments part on the registration form and you will be
granted write access. You can also send a mail to HERON::PROJECTS_CC
Performance might not be ideal, depending on the speed of the links between your
location and Valbonne.
b) Local RALLY and Remote Rdb
Prerequisite : Have at least RALLY V2.1-A and RDB 3.0-B run time installed on
your system. Make sure that HERON is known from your local node.
Then copy from : HERON"PROJECTS_CC"::REF.SAV a save set containing :
REF_RUN.RGA the RALLY application file (no symbol table ==> not editable)
REF_MACRO.RGM a utility file containing application defined functions
REF.COM a procedure assigning logical names and running the application
If you put those two files in your SYS$LOGIN, you an run the application as it
is by doing @REF.
If you do not put them in SYS$LOGIN, you have to change the LOCATION logical
name in the REF.COM command procedure, in order to have it point to the .RGA
file location. You can also define your preferred printer.
The behavior of the application will be exactly the same, but performance will
be better than if you use set host.
4 - HOW TO USE THE PROTOTYPE
Two functionalities are provided : a query interface to retrieve data from the
database, an update interface to create/update data in the database, on-line
help and a mailing facility to extract information from the database through
E-MAIL.
a) QUERY
Anybody that has access to the application can register and grant himself read
access to the database. After the prompt for the badge number, the query form is
displayed and allows to do multi-criteria queries to the database.
To move from a field to another in the query form, use Tab. or Return (next
field), and F12 (previous field).
In each field of the form, you can either :
- specify a value directly in the field (*) :
It means that you are interested only in records for which the field value is
EQUAL to the specified value.
- specify an "extended query" on the field by pressing Find key :
It means that you want to specify a query expression other than EQUAL.
When you have pressed the Find key in a field, a command line appears in the
left down corner of the form : Enter query expression
You can then use one of the following operators to specify the extended query :
- for NUMBER and DATE fields : > , >= , < , <= , =
- for CHAR fields : all above, plus STARTS, CONTAINS, MATCHES
You can combine these operators using the conjunctions AND and OR, and the
negation NOT. On line Help is available when in the command line (press Help).
To go back to the field once the query expression is entered, press Return.
(*) List of valid values are provided for a field each time the icon
GOLD L AVAILABLE is displayed in the right down corner of the form.
- To display the pop-up window in the middle of the screen, use GOLD L
- If you want to restrict the list of values to the values starting
with a character string, type in the string in the field and then
press GOLD L (this function is similar to the ALLIN1 GOLD L facility)
- To move within the list of values, use down arrow and up arrow to
scroll records, Next and Prev keys to scroll pages.
- To select a value from the list of values, press Select or Enter.
Examples of valid extended query expressions :
NUMBER : > 100
>= 5 and <= 10
< 15 or >= 24
(> 5 and < 10) or > 20
= 2 or >= 5
DATE : > 1-OCT-1989
> 20-OCT-1989 and <= 31-DEC-1989
CHAR : > C (case sensitive, upper case first)
STARTS A (case sensitive)
STARTS B or = BULL
NOT STARTS B
CONTAINS iBm (case insensitive)
MATCHES *BM* (case sensitive)
It's possible to specify query expressions (exact match or extended query) for
every field in the form. Note that all the query expressions are ANDed together.
There is *NO WAY* to do a logical OR across several fields (eg. COUNTRY = FRANCE
or INDUSTRY = MANUFACTURING).
In particular, when two products are specified, it means that you expect to get
back projects where both products are used together. Note that in this case, you
might also do a logical OR query on the field PRODUCT because only one field is
involved in the logical OR (PRODUCT = RDB or PRODUCT = ACMS can be specified as
an extended query on the field PRODUCT).
Finally, when all the query expressions have been specified, you execute the
query by pressing Enter.
When the records are pulled back from the database, you can :
- scroll through the collection of records using arrow keys (up and down),
- select one of the records to have more information about it using Select key.
In this case, another form is displayed giving detailed information on the
project selected, inclusing an extensive comment.
- reset the screen in order to make another query, using Find key.
In this case, the screen is cleared, and you can again specify query
expressions.
In case no matching records are found in the database, a message is issued :
+------------------------------------------------------------------------------+
| There is no matching record in the database. Press Return |
+------------------------------------------------------------------------------+
It means that your query was too restrictive : you have to drop some conditions
on the fields and execute the query again, until you have some records matching
all the conditions that you have required.
To drop a condition on a field, you have to do the following :
- in case of an exact match, clear the value specified in the field using key
F3, (same key as ALLIN1 for delete word)
- in case of an extended query, press Find key when in the field to go back to
the command line, and then clear the expression specified there using key F3
several times (until the line is blanked), or key F9 to clear the whole line
altogether.
To leave the query form and exit the application, press F8.
b) UPDATE
To be allowed to update the database requires to be granted write access.
When it's the case, you will be allowed to create/update records for your
country and the technology that you specified in the registration form.
A competency circle coordinator can update multiple countries, though.
After the prompt for your badge number, a menu with 3 choices appears :
1. Update the database
2. Query the database (function offered to read-only users - described above).
3. Exit
If you select the update option, then you are left browsing the collection of
records belonging to your country and your technology. The form layout looks
almost exactly like the detailed query form.
To scroll through the collection of records, use arrow keys (up and down).
If there are too many records and scrolling one record at a time becomes
tedious, you can query the database specifying query expressions in the same way
as you could do in the query form. List of values are available when the icon
GOLD L AVAILABLE is there, and work in the same way (*).
You can then update any visitable field and change its value.
When you leave a record either to scroll to another record, or to query the
database, all the changes made in the record that you are leaving are made
permanent in the database (they are 'committed').
(*) There is an enhancement for the list of values in the update form.
If you type in the first letters of a value in a field, and the string
uniquely identifies a value in the list, then if you press Return or
GOLD L, the value will automatically be picked up from the list.
If more than one value starts with the first letters specified, then
they are displayed in the list. You can pick up a value using Enter of
Select key, or quit the pop-up window using F8.
If no value matches, then you are left creating a new entry in the
reference table. Fill in the value there and press Enter to confirm.
This way you will have simultaneously created a new entry in the list,
and associated this value to the current record you are editing.
Finally, in case you made a simple GOLD L to browse the list, and then
realized that the value you would like is not there, you can still
create a new entry in the list using Insert key. To confirm and pick
the value press Enter or Select.
To create a new record, press Insert key. A reference number will automatically
be allocated to the record, and you will be left filling in the other fields.
Similarly, use Insert key to create new entries in the repeating groups :
- TECHNOLOGY SPECIFIC METRICS, PRODUCTS, KEYWORDS, COMPETITORS, DIGITAL CONTACTS
To remove an entry from a repeating group, use Remove key.
When the cursor is in the top most part of the screen (above repeating groups),
using Remove key will remove the whole record from the database. A Y/N menu will
prompt you to confirm the removal in order to prevent any mis-usage of the
Remove key.
To exit from the update form making permanent in the database all the changes
made to the last project edited, press F10 or Enter.
To quit the form, discarding the changes made to the last project, press F8.
If you want to save the changes at any time, without exiting the form, press Do
key and type in the command line : commit.
If you want at any time abort the changes made to the top most part of the
current record, press Do key and type in the command line : rollback.
Last, if you want to edit comments about the current record (to give details
about the configuration, or any information that you could not enter in the
other fields), type Y in the last field of the form : a sub-form appears,
allowing you to type in 10 lines of text.
In this subform, use arrow keys to go up and down one line (Tab. / Return and
F12 work as well). To return to the main update form, type GOLD F12 from any
place in the subform. If you are in the last line, Return key will get you to
the next record in the database. If you are in the first line, key F12 or up
arrow will get you in the Y/N comment field.
c) E-MAIL FACILITY :
In any form (query or update), an E-MAIL facility is provided. If you press F17,
a form appears to let you fill in an E-MAIL address and a comment. By default,
the address is yours, but it can be overriden. The mail sent will contain the
"logical" content of the screen (if the screen contains more than one page of
information, they will be all in the mail). To send the mail and return to the
original form, press Enter. To abort, press F8.
d) HELP FACILITY :
On-line help is provided in the application (press Help key). It's a form
specific key reminder :
PROJECT TRACKING SYSTEM KEYS REMINDER UPDATE FORM
Move to next field : Tab. or Return
Back to previous field : F12
Move to last field : PF1 Return
Move to first field : PF1 F12
Exit the form (commit) : Enter
Quit the form (rollback): F8
Insert a new record : Insert here (previous updates are committed)
Delete a record : Remove (confirm menu appears)
Scroll to next record : Down arrow
Scroll to prev record : Up arrow
Scroll to next page : Next
Scroll to prev page : Prev
Send the report via E-MAIL : F17
PROJECT TRACKING SYSTEM KEYS REMINDER QUERY FORM
Specify a criteria : Move along the fields using Tab. and F12
Execute a query : Enter
Scroll to next record : Down arrow
Scroll to prev record : Up arrow
Scroll to next page : Next
Scroll to prev page : Prev
Select one record : Select
Do another query : Find (it will reset the screen)
Quit any form : F8
Send the report via E-MAIL : F17
How to specify complex query criteria :
- Criteria 'equals to' : Fill in the value in the field
- Other criteria : Press Find key when in the field.
Then, on the command line that appears, use one of the following operators in
order to specify the extended query expression :
< , <=, >, >= for NUMBER or DATE fields
starts, contains, matches for CHAR fields
Example :
After have pressed the Find key while in the field Former Vendor, type in :
Enter query expression : starts IBM
and you will get all the records in the database whose former vendor was IBM,
no matter what kind of hardware were there (AS400, 3090 ...)
APPENDIX 1 Hardcopies of screens
UPDATE SCREEN :
Before any information is filled in :
+--------------------------+-----------++------------------------------+-------+
| PROJECTS TRACKING SYSTEM |27-Nov-1989||Jean-Michel GROSGURIN | QUERY |
+--------------------------+-----------++------------------------------+-------+
+-------+------------------- ACCOUNT INFORMATION ----------------------------+
|Office | |Code TP FRANCE |
|Account| |Industry : |
|Project| |HW/SW/Sces(K$): / / |
|Visit ?| Mood: |Former vendor : |
+-------+--- Application Description ----+Devt Phase : |
| |
+--------------------------- TECHNOLOGY SPECIFIC ----------------------------+
| |
| |
+--------+---------------------------------------------------------------------+
|PRODUCTS| |
+--------+---------------------------------------------------------------------+
|KEYWORDS| |
+--------+------------++-----------------------------------+----------+--------+
| COMPETITORS || DIGITAL CONTACTS EMAIL address |Telephone |Function|
+---------------------++-----------------------------------+----------+--------+
| || |
| || |
+---------------------++-------------------------------------------------------+
Do you want to add a comment [Y/N] :
Screen after filling in the information :
+--------------------------+-----------++------------------------------+-------+
| PROJECTS TRACKING SYSTEM |27-Nov-1989||Jean-Michel GROSGURIN | UPDATE|
+--------------------------+-----------++------------------------------+-------+
+-------+------------------- ACCOUNT INFORMATION ----------------------------+
|Office | PARIS |Code TP1 FRANCE |
|Account| FICTIVE |Industry : MANUFACTURING |
|Project| Reseau d'Agences |HW/SW/Sces(K$): 10 / 10 / 10 |
|Visit ?| Y Mood: NEUTRAL |Former vendor : BULL DPS8 |
+-------+--- Application Description ----+Devt Phase : TESTING |
|Order entry sample application |
+--------------------------- TECHNOLOGY SPECIFIC ----------------------------+
| DBSIZE 600 NBTERM 150 TPS 5.5 |
| NBDISK 5 NBUSER 80 VUPS 15 |
+--------+---------------------------------------------------------------------+
|PRODUCTS|ACMS RALLY RDB |
+--------+---------------------------------------------------------------------+
|KEYWORDS|365 DAYS CLUSTER DATABASE DECTP |
+--------+------------++-----------------------------------+----------+--------+
| COMPETITORS || DIGITAL CONTACTS EMAIL address |Telephone |Function|
+---------------------++-----------------------------------+----------+--------+
|BULL DPS8 ||Pierre DUPONT @PAO 858-YYYY SALES |
|IBM 3090 ||Jean DURAND @PAO 858-XXXX SWAS |
+---------------------++-------------------------------------------------------+
Do you want to add a comment [Y/N] : N
QUERY INTERFACE
Screen as it appears when the user calls it :
+--------------------------+-----------++------------------------------+-------+
| PROJECTS TRACKING SYSTEM |27-Nov-1989||Jean-Michel GROSGURIN | QUERY |
+--------------------------+-----------++------------------------------+-------+
Number of accounts selected :
+------------------------------------------------------------------------------+
|Techn. : Updated: Country : |
|Account: Industry : |
|Project: Former Vendor: |
|Bus(K$): Mood: Devt Phase : |
+- Products -+--- Keywords ---+- Metrics Values -+-- Competitors ------+-------+
| | | | |Visit ?|
| | | | | (Y/N)|
+------------+----------------+------------------+---------------------+-------+
After the user has filled in some search criteria :
+--------------------------+-----------++------------------------------+-------+
| PROJECTS TRACKING SYSTEM |27-Nov-1989||Jean-Michel GROSGURIN | QUERY |
+--------------------------+-----------++------------------------------+-------+
Number of accounts selected : 0
+------------------------------------------------------------------------------+
|Techn. : TP Updated: Country : FRANCE |
|Account: Industry : |
|Project: Former Vendor: |
|Bus(K$): Mood: Devt Phase : |
+- Products -+--- Keywords ---+- Metrics Values -+-- Competitors ------+-------+
|ACMS |CLUSTER | TPS * | |Visit ?|
|RDB | | | |Y (Y/N)|
+------------+----------------+------------------+---------------------+-------+
* Enter Query Expression : > 10
After the user has received the answer from the database :
Note that the answer does not correspond to the query criteria, because
the sample database does not contain enough records.
+--------------------------+-----------++------------------------------+-------+
| PROJECTS TRACKING SYSTEM |27-Nov-1989||Jean-Michel GROSGURIN | BROWSE|
+--------------------------+-----------++------------------------------+-------+
Number of accounts selected : 4
+------------------------------------------------------------------------------+
|Techn. : TP1 Updated: 27-Nov-1989 Country : FRANCE |
|Account: FICTIVE Industry : MANUFACTURING |
|Project: Reseau d'Agences Former Vendor: BULL DPS8 |
|Bus(K$): 30 Mood:NEUTRAL Devt Phase : TESTING |
+- Products -+--- Keywords ---+- Metrics Values -+-- Competitors ------+-------+
|ACMS |365 DAYS | DBSIZE 600 |BULL DPS8 |Visit ?|
|ACMS |365 DAYS | DBSIZE 600 |BULL DPS8 |Y (Y/N)|
+------------+----------------+------------------+---------------------+-------+
+------------------------------------------------------------------------------+
|Techn. : TP2 Updated: 24-Nov-1989 Country : FRANCE |
|Account: Industry : MANUFACTURING |
|Project: Former Vendor: ICL |
|Bus(K$): 71 Mood:HAPPY Devt Phase : TESTING |
+- Products -+--- Keywords ---+- Metrics Values -+-- Competitors ------+-------+
|ACMS |DECTP | |IBM AS 400 |Visit ?|
|ACMS |DECTP | |IBM AS 400 |Y (Y/N)|
+------------+----------------+------------------+---------------------+-------+
+------------------------------------------------------------------------------+
|Techn. : TP4 Updated: 24-Nov-1989 Country : FRANCE |
|Account: Industry : |
|Project: Former Vendor: |
|Bus(K$): Mood: Devt Phase : |
+- Products -+--- Keywords ---+- Metrics Values -+-- Competitors ------+-------+
|ACMS |DECTP | DBSIZE 100 |BULL DPS8 |Visit ?|
|ACMS |DECTP | DBSIZE 100 |BULL DPS8 | (Y/N)|
+------------+----------------+------------------+---------------------+-------+
+------------------------------------------------------------------------------+
|Techn. : TP5 Updated: 27-Nov-1989 Country : FRANCE |
|Account: account Industry : AEROSPACE |
|Project: project Former Vendor: IBM AS 400 |
|Bus(K$): 60 Mood:VERY POSITIVE Devt Phase : JUST SOLD |
+- Products -+--- Keywords ---+- Metrics Values -+-- Competitors ------+-------+
|ACMS |AUTOMATS | DBSIZE 1000 |TANDEM |Visit ?|
|ACMS |AUTOMATS | DBSIZE 1000 |TANDEM |Y (Y/N)|
+------------+----------------+------------------+---------------------+-------+
After the user has selected the first project
to have more information
+--------------------------+-----------++------------------------------+-------+
| PROJECTS TRACKING SYSTEM |27-Nov-1989||Jean-Michel GROSGURIN | BROWSE|
+--------------------------+-----------++------------------------------+-------+
+-------+------------------ PROJECT INFORMATION -----------------------------+
|Office |PARIS |MANUFACTURING FRANCE |
|Account|FICTIVE |Former vendor : BULL DPS8 |
|Project|R�seau d'Agences |Business : K$ 30 (10 /10 /10 )|
|Visit |Y Mood: NEUTRAL |Dvt Phase : TESTING |
+-------+-------------------------------+--------------------------------------+
|Order entry sample application |
+--------------------------- TECHNOLOGY SPECIFIC ----------------------------+
| DBSIZE 600 NBTERM 150 TPS 5.5 |
| NBDISK 5 NBUSER 80 VUPS 15 |
+--------+---------------------------------------------------------------------+
|PRODUCTS| ACMS RALLY RDB |
+--------+---------------------------------------------------------------------+
|KEYWORDS| 365 DAYS CLUSTER DECTP |
+--------+------------++-----------------------------------+----------+--------+
| COMPETITORS || DIGITAL CONTACTS EMAIL address |Telephone |Function|
+---------------------++-----------------------------------+----------+--------+
|BULL DPS8 ||Pierre DUPONT @PAO 858-YYYY SALES |
|IBM 3090 ||Jean DURAND @PAO 858-XXXX SWAS |
+---------------------++-------------------------------------------------------+
Do you want to add a comment [Y/N] : N
Using the mailing facility
+--------------------------+-----------++------------------------------+-------+
| PROJECT TRACKING SYSTEM |01-Feb-1990||Jean-Michel GROSGURIN | BROWSE|
+--------------------------+-----------++------------------------------+-------+
+-------+------------------ PROJECT INFORMATION -----------------------------+
|Office |PARIS |MANUFACTURING FRANCE |
|Account|FICTIVE |Former vendor : BULL DPS8 |
|Project|R�seau d'agences |Business : K$ 30 ( 10 / 10 / 10 )|
|Visit |Y Mood: 3 NEUTRAL |Dvt Phase : TESTING |
+----------------------------------------------------------------------------+
| MAILING FORM |
+----------------------------------------------------------------------------+
| Enter E-MAIL address (default is yours) and subject : |
| |
| LOCATION : VBO |
| FULL NAME : Jean-Michel GROSGURIN |
| SUBJECT : Projects Tracking System : Report issued on 01-Feb-1990 |
| |
|To quit press F8 Press Enter when completed |
+----------------------------------------------------------------------------+
| || |
+---------------------++-------------------------------------------------------+
Do you want to add a comment [Y/N] : N Transaction Processing
APPENDIX 2 BACHMAN DIAGRAM OF THE PROJECTS TRACKING DATABASE
+----------+ +--------+ +---------+ +----+ +------+
+--> |DEVT_PHASE| |INDUSTRY| | COUNTRY | |MOOD| |VENDOR|
| +----------+ +--------+ +---------+ +----+ +------+
| | | | | | |
| | +--------------+ | +----------+ | |
| +----------------------------+ | | | +-------- (former) ------+ |
| | | | | | |
| v v v v v |
| +---------+ |
| +---------------------------------->|REFERENCE| (master project record) |
| | +---------+ |
+---+ | | | | | |
| T | +----------------------------+ | | | +-----------------+ |
| E | | +------------------+ | +--------+ | |
| C | | | | | | |
| H | v v v v v v
| N | +-----------+ +-----------+ +-----------+ +----------+ +--------------+
| O | |REF_CONTACT| |REF_PRODUCT| |REF_KEYWORD| |REF_METRIC| |REF_COMPETITOR|
| L | +-----------+ +-----------+ +-----------+ +----------+ +--------------+
| O | ^ ^ ^
| G | | | |
| Y | +-----------+ | |
+---+--------------->| PRODUCT | | |
| | +-----------+ | |
| | +-----------+ |
| +----------------------------> | KEYWORD | |
| +-----------+ |
| +----------+
+--------------------------------------------> | METRIC |
+----------+
| |||||
| 171.3 | AI conversion effort | BONNET::COUTIER | Mon Feb 12 1990 10:32 | 13 | |
May I strongly suggest that, from now on, people use the database
described in the previous reply as their "reference database". Its user
interface is much friendlier than the one developed by Eric Lenci last
summer, and it can be more interactive.
Since this is a cross-technology database, Jean-Michel and I sat down
to figure out how to map the fields of the old database with the fields
found in his. Most AI-specific fields which did not exist in his
database could be easily handle with the "KEYWORD" field. The only AI
field of significance which had to be addressed during this "conversion
effort" was the "APPLICATION" field. Application types (diagnostic,
design, configuration,...) are now keywords and can be search using the
"KEYWORD" field.
| |||||
| 171.4 | Automatic copy of a new kit | HERON::GROSGURIN | Jean-Michel E/ACT Valbonne | Wed Mar 07 1990 09:09 | 21 |
For those of you who do not set host to PROJECTS_CC on HERON to use the Projects Tracking Database, but have copied the saveset REF.SAV allowing to run the RALLY application locally, you will not have to bother anymore about the fact that the kit you have might be obsolete. A new mechanism is provided that checks whether or not you are running the right version of the kit. If you are not, then a pop-up menu asks you to copy the new kit and to restore it the same way you did it the first time. It also allows someone that used to use set host,to decide to run the RALLY application locally without having to ask me for a change in the security file. The first copy will still have to be manual (refer to the documentation), but then the updates will be automated. Although the mechanism allows you to continue using your old version for READ ONLY access, you are strongly advised to take a new copy of the kit every time it's necessary. Hope this helps Jean-Michel | |||||
| 171.5 | Project Tracking System Broken? | KETJE::VANDEVYVER | I've been in the desert on a node with no name... | Wed Aug 07 1991 15:07 | 8 |
I tried accessing the Project Tracking System using the captive account @heron, but got : User authorization failure did something change or is the information in it obsolete?? Luc | |||||