Device or tool used as part of the normal operation of an application (a modem, punch clock, pre-printed form or invoice, etc.). An accessory also provides a particular function not available in the application.
Refers to the reason of why or how an element was involved in a service order.
Group of actions or tasks (subactivities) which al together represent a project generated in response to a service order. An activity can be considered as planned (included in the initial project plan) or not planned (included in the project after the plan was deployed as definitive).
OLE documents attached to a service order as a supplement to its documentation.
Tip or note on part of the project manager for the project leader and specialists in charge of the development of a service order.
Short name or label used as an alternative reference for an application, process, program or file.
Refers to the time (age) since an application was installed.
Organized set of programs oriented to a particular function or common objective. These programs are organized in processes , a group of processes form an application. An application can also be known as a computer system.
System user in charge of maintaing, administering and monitoring the operation of an application.
Average or estimated number of minutes an element requires to execute its primary function.
In the context of an organization, it is a logical division of a company. Commonly an organization separates groups of people that have a common objective or task. For example: Information technology area.
Information related to the general principles or beginning of an application, referring to the personnel involved, software that was used, accessories, etc.
Purge process that moves all the finished or cancelled service orders to a historical database. This process is normally executed after a period pre-defined by the database administrator.
In reference to a set of cost centers in an organization grouped in a particular fashion (economic or geographic zone, administrative structure, etc.) with the purpose of following an established order.
It can also refer to a set of small businesses owned by a company.
Description of the cause for stopping the development or modification of an element.
Status of an element indicating that its development will not continue.
Service category for a request of a modification of a determined application.
Category in which a software can be under, based on its function.
Also called an observation, it is a text included with a particular object (program, process, service order, etc.) with the purpose of documenting.
Generally describes "What does it do?, Who wrote it?, Who changed it?, What are the suggestions?, etc.", even though it can include any text relevant to the object.
Free content text sent between users in Proaris.
Represents the collection of information entities and their relation, these are the basic building blocks of information representation and modeling.
Each information entity is normally implemented as a table or file in its minimum expression.
The person who is responsible of the integrity of the database, assignment of user permissions.
He is also responsible of defining the standard nomenclature to use in Proaris stored in the catalogs.
Order in which the month, year and day of any date is to be typed in.
Status of a activity, subactivity scheme of a service order, when the project leader deploys the plan as final, confirming it is no longer in the planning phase.
Within a context of a service order with a current status of "in-process", it refers to the number of days elapsed from the planned finish date and the current date (today).
Within the context of a service order in a "finished" or "cancelled" status, it refers to the number of days between the planned finish date and the real finish date.
Date when the service order was confirmed by the project leader as finished.
In-depth description of the objectives, functions, procedure and limitations of a particular element.
Refers to the scheme or concept under which an applications was developed, for example: commercial software, in-house development, out-source development, etc.
In-house or out-source personnel (programmers, designers, etc.) directly involved in the development of an application.
Name used in reference to a certain stage, phase or project in which an application is actually built.
Software involved or used in the construction of an application. Normally refers to a computer programming language.
Graphic representation of the relationship between applications, processes, programs or files.
Tool included in Proaris, which generates a graphical representation of existing relationships between applications, processes, programs, and interfaces between applications.
Category for a disk folder, commonly based on the contents it may have.
Category for a document, commonly based on its objective or contents.
Estimated monetary amount generated from the estimated man-hours involved for the development of a project, activity or subactivity.
Planned number of man-hours to start and finish a project (service order), activity or subactivity.
Date currently estimated for delivery of a certain project, activity or subactivity, this date is dynamic, when the element is under development it reflects the direct estimate of the people directly responsible of that element at that moment, this date can change in the next progress update when the estimate can be more certain.
Number of hours in which a subactivity responsible estimates he can finish his current workload.
Date planned for when a certain project, activity or subactivity is to start.
Consists of a simple grade of the services requested through a service order.
Function in Proaris which allows the transportation of data to an other format such as Ms-Excel or Ms-Word.
Represents the minimum storage for data in a file.
A file allows the storage of data in permanent storage device such as a hard disk or floppy disk.
Files are used by programs to accomplish their function, a file can be used by a program for input (read only), output (write) or input and output (read and write).
Their are different kind of files: database table, database, document, sheet, indexed file, etc.
System user, responsible for maintaining and administering a file (database table or document).
Operation of separating information based on one or more criteria expressions.
Operation that allows the search of a certain text in the current screen.
Unique identification number for a service order.
Refers to the purpose or objective an application, process or program must meet or fulfill.
Visual representation of the relationship between activities and subactivities, based on dates that can represent different stages of the project (estimated start date, planned finish date, real start date, real finish date, etc.).
Brief overview of a particular element describing its functions, objectives or limitations.
Global reference parameter for one of the different elements involved in the system. Normally these are represented through a specific data (percentage, sum), vital to the accomplishment of an objective.
Configuration setting that a database administrator defines to establish a desired behavior in the Proaris environment. For example: date format, logo image, etc.
Visual representation of the selected data.
External physical components around an application, including computer equipment, other devices: keyboards, monitor displays, mouse, printers, storage devices, cables, routers, and in general any device the application (software) requires to function the way it was designed .
Information relevant to a particular element that allows a reference of its behavior in the organization through the different service orders in which it has been involved.
Unique code (normally assigned automatically) in Proaris which allows a specific reference to a particular element.
File that is used as a read-only source in a program.
File used as a read and write source of data.
Date on which an application, process or program was first deployed into production in the organization.
Point of connection between two elements that can work together. Refers to the dynamic relation between two or more applications, processes, programs.
Description of the relationship between two applications.
Element (application, process, program) involved in a service order due to a modification the element has suffered during the development of that service order.
Person who was responsible for adding an application element that was created or modified during a project.
Database where an extract of the most critical information of a service order is stored when it has been finished.
Programming package or software used in the authoring of an application or program.
Date of the most recent modification of a certain element.
| E.D. |
Estimated Duration |
E.F.D
|
Estimated Finish Date |
E.H.F
|
Estimated Hours to Finish |
E.S.D.
|
Estimated Start Date |
ID.
|
Identifier |
L.U.
|
Last Update |
P.A.
|
Predecessor Activity |
P.S.
|
Predecessor Subactivity |
Prog. %
|
Progress % |
Q.A.
|
Quantity of Activities |
Q.S.
|
Quantity of Subactivities |
R.D.
|
Real Duration (Hrs.) |
R.A.
|
Responsible Authorization |
R.S.D.
|
Real Start Date |
Var.
|
Variance (Hrs) |
|
Size of a record in bytes, indicating the number of characters, digits or words conforming a data set.
Number of times a field has been redefined into other fields. a regular field will have a level of zero, the first division will have a level of one, and so on.
Place where a certain element resides. for example: a location for an application could be a city, region, geographic zone.
Process of signing-on for a user session in Proaris through a user session and a password.
Represents the symbol of an organization in form of a drawing or sketch identifying the line of business or commercial gender of a company.
Computer or equipment, where an application can be hosted or developed.
Name given to the area or group of people responsible of the implementation, flow and administration of information and information technology in an organization.
A Proaris data field considered as required, the set of mandatory fields is the minimum required by the D.B.A. as documentation for each of the elements.
Note or text sent in the system by the different users or Proaris in reference to a particular action.
Service category used for requesting non-existing processes, programs or even an application.
An activity that was not originally considered as part of the project plan and was added after the project had started.
Amount of days after a service order was finished in which it is liable to be transferred from the main Proaris database to a historic database.
Code generated in a program compile or linking, transforming a program's source code to executable code or pseudo-code.
The term commonly refers to the machine code a cpu can directly read and execute.
Number of times a field is divided into data slots, or instances.
A type of windows document that can be interchanged between windows applications.
Software in charge of managing the hardware resources such as: memory, cpu, hard disk space, devices.
Software layer between an application and the hardware.
Category that describes any kind of project not related to an application or one of its elements.
Generic project.
File that is used as a write-only destination of data.
Refers to those responsible of a specific application.
Preventive measure used to restrict access into the system. Character string requested to each user in order to grant entrance to all the options in Proaris.
Address or disk location where a file or program can reside.
Refers to the efficiency of execution of a certain procedure, function or program.
In the employee context, it refers to the efficiency of execution of the functions assigned to each one.
Amount of time between the first and the second execution of a process (Daily, Weekly, Monthly, etc.).
Privilege of access to a specific module or option.
Group of employees involved in a specific task and somehow are involved with an application.
Date planned for when a certain project, activity or subactivity is to be delivered.
Refers to hardware, software or a combination of both on which an application supports itself.
Function or post occupied by a person in an organization.
Element on which another element depends of its finish date in order to start.
It is an activity on which the execution or start of another activity depends. In other words, it is an activity that has to be finished first, before the current activity can start.
A predecessor activity is optional for each activity and is represented by a number.
It is a subactivity on which the execution or start of another subactivity depends. In other words, it is a subactivity that has to be finished first, before the current subactivity can start.
A predecessor subactivity is optional for each subactivity and is represented by a number.
Description of how a certain problem can be detected before it happens.
Urgency level for a service order given by the user who registers the request.
Service Category used by an end-user detects a fail in an application and requests a repair through a service order.
Category under which a problem can fall, recognized by the organization.
Set of programs organized in a coherent sequence of steps to fulfill a specific task or objective.
Also refers to a human procedure required to complete a specific task or objective.
Sequence of instructions to be executed by a computer.
A program normally includes all the statements, commands and files necessary for the execution a specific function, programs can be divided in two categories: Source and Object.
Percentage indicating the current status of the development of a service order, activity or subactivity.
Amount (percentage) of the current proportion of development or completion of a task.
Organized set of activities and subactivities required to develop in a certain sequence within a certain time frame. Generated in response of a service order.
Person in charge of the maintenance and good behavior of an application.
Also, he is the only one that can receive service orders directly related to an application, assign them and in some cases cancel them.
Normally he coordinates 1 or more project leaders (service order responsibles), and is for all means from the end-user point of view responsible of fulfilling a service request.
Tool included in Proaris that allows the visual representation of one or more projects with its activities and subactivities.
One of the tools included in Proaris that allows a visual representation of the projects and their activities and subactivities.
Consulting Screen.
Read only form, displaying data corresponding to a specific question or issue.
Final monetary amount generated from the actual man-hours involved during development of a project, activity or subactivity.
Current or final amount of man-hours involved towards the completion of a certain activity, subactivity or service order.
Date in which an activity, subactivity or project officially finished.
Date on which a certain project, activity or subactivity actually started, hopefully it should be the same as E.S.D.
Description of the causes an element was to be modified.
Date when a service order is received by the project manager.
User who receives a message.
Set of fields to be saved in a file.
An established Association between applications, processes, programs, files, etc.
Regarding to level of documentation for the various elements (applications, processes, programs, etc.) monitored in Proaris.
It Can also be regarded as the proportion of data that Proaris actually has against the total of data Proaris should have defined by the database administrator.
Respond to the user who originally sent the message.
Container in which a data modeled is stored with the definition of all the elements it is formed by.
Also known as a data dictionary.
Amount of hard disk space or other storage device a particular element requires to be installed.
Element or factor (software, hardware or accessories) needed by an application to work. In case they are not met, the application may not function appropriately or not function at all.
Category under which a service order of type "new requirement" can fall: new application, other (new program, process, etc.).
Refers to a Person or group of persons which have a duty over a determined element. for example: an application responsible, or a person responsible of a file, service order or activity, etc.
Confirmation of accomplishment from the project leader responsible of a certain service order.
Protection measures for access control and permissions to different levels of information inside Proaris.
User who sends a message.
Explanation of the service request.
Request for service, established and registered by a a certain user to resolve a problem, change, new requirement for a systems application or any other kind of project.
Person who registers a service order.
Project leader, person who takes direct responsibility of the development of a service order.
Description of why a service was requested or the purpose for the service request.
Category under which a service order falls in regard of how it will affect an application (problem, change, new requirement) or not affect an application at all (generic project).
Alias for an element.
Place of residence for a certain element.
Time Period between the finish of an activity and the start of the next dependent activity.
On a Gantt chart, the divisions or timer periods are known as Time scale bars. The small scale bars are grouped in large scale bars, you can configure what time period each of these bars can represent, for example:
|
Show Name on bar
|
Show Number on bar
|
Small scale
|
|
|
| Day |
M, T, W, T, F... |
14, 15, 16, 17... |
| Week |
2/9/97, 2/16/97, 2/23/97... |
7, 8, 9... |
| Month |
Feb, Mar, Apr... |
2, 3, 4... |
| Quarter |
Q-1, Q-2, Q-3, Q-4... |
1, 2, 3, 4... |
| Semester |
S-1, S-2, S-3... |
1, 2, 1... |
| Year |
not available |
not available |
|
Large scale
|
|
|
| Day |
not available |
not available |
| Week |
2/9/97, 2/16/97, 2/23/97... |
7/1997, 8/1997, 9/1997... |
| Month |
February, March, April... |
2/1997, 3/1997, 4/1997... |
| Quarter |
Q-1-1997, Q-2-1997, Q-3-1997 |
1/1997, 2/1997, 3/1997... |
| Semester |
S-1-1997, S-2-1997, S-1-1998... |
1/1997, 2/1997, 1/1997 |
| Year |
1997, 1998, 1999... |
Y-1, Y-2, Y-3... |
Refers to a certain development or productivity tool, programming language or a computer program in general required for an application to run, interact or author certain elements. It allows a mean of interaction with the computer hardware.
Description of how a problem can be resolved once it has happened.
Element containing the basic instructions for a certain task in an application, and normally cannot be executed or interpreted directly by a computer.
A query or report oriented to showing summarized data, normally through percentages, proportions, totals, etc.
Current condition of an element.
In the context of applications, it refers to the current state of availability within the organization: In-process, In-Maintenance, etc..
In the context of a documentation, it refers to the level of reliability: Obsolete, Up-to-date, Update-required, etc.
Refers to a specific task, a group of tasks form an activity.
Person who is responsible for a specific task in a project.
A division of an area with a more specific level of specialization on a certain task. For example: the IT area can be divided in development, research, technical support, etc.
Represents the title or main idea of a message.
Normally refers to a computer application.
Current date registered by the computer.
Text automatically generated by Proaris, normally as a warning.
A user that has permission to enter Proaris, performs a function within the information cycle and is allowed only to certain options that support that function.
Access granted to a user with which he may not only read the documentation of an application end its elements, but also modify it.
Process in Proaris executed by the database administrator to terminate a session of a particular user.
Process of authentication performed by Proaris to grant access and entrance to a user inside Proaris. Normally the user name and password is asked for the sign-on.
Unique system name for a user used by Proaris for identification purposes.
Category based on the tasks an individual performs in an organization, which also reflects the permissions and information access he can have in Proaris.
Refers to the variation (difference) between the planned man-hours and the final real man-hours required in the development of a project, activity or subactivity.
Identifier for a revision of an application.
It is the grouping of the residence elements of an application: machine, location, platform, site, business strategic unit, city, etc.
Distribution of service orders currently with "in-process" status. It is also a reference of the man-power involved and managed by those responsible of a service order, activity or subactivity, hence it is measured in man-hours.