AVQ SWISSC
Question from AVQ Academy Part 2 - Englisch und Deutsch gemischt
Question from AVQ Academy Part 2 - Englisch und Deutsch gemischt
Kartei Details
| Karten | 300 |
|---|---|
| Sprache | Deutsch |
| Kategorie | Informatik |
| Stufe | Andere |
| Erstellt / Aktualisiert | 11.03.2015 / 09.06.2017 |
| Weblink |
https://card2brain.ch/box/avq_swissc
|
| Einbinden |
<iframe src="https://card2brain.ch/box/avq_swissc/embed" width="780" height="150" scrolling="no" frameborder="0"></iframe>
|
There are four granted users permitted at one time.
No. We need to open a new change to modify the sources (to create new source versions).
When we create a change we indicate the database via the field Compilation DB"."
We cannot create a new source without creating a new change. (But as well it's possible to view a source without opening a change!)
Yes, we can. We do it via Gsearch.
False – The source is stored in the ENV database.
In ENV we have more source types.
It allows us to save and use PL/SQL code.
No, we should say that we can use Excel Files to produce the code that is going to parameterise an Avaloq instance.
Business Type Config (BTC)
BTC sources: They may have all kinds of very different parameterisations; this is why we call them unstructured"."
As many as we want.
Yes, we can.
No, Avaloq only proposes best practices"."
It depends on the workflow that the bank decided to implement.
False: Releases are a set of changes.
False: a service pack is of minor importance than a release.
Yes, it is.
Yes it does. It proposes, for example, a source versioning system.
Which parties are involved in an Avaloq project?
The following parties are involved: Bank, Avaloq and Implementation Partners.
Which phases a project usually goes through and what deliverables are expected at the end of each phase?
– Project initiation: Project Setup (Organisation, Project Plan etc.), Analysis & Design: Requirements specification, technical specification, Implementation & parameterisation: Source, finalised technical specification, Testing: Running System, Trans
What difference between a product customer and an evolution customer?
In contrast to the evolution customer, a product customer can go live with Avaloq based on the delivered CD and possible available Service Packs without requiring further functionality (gaps) to be developed.
How often and when does Avaloq rollout a new release of the Avaloq Banking System?
A new release of the Avaloq Banking System is rolled out to all customers every spring.
What are the stages of release upgrade projects?
Upgrade initialisation, installation clean–up, parameterisation adaptations, testing, cutover, post–cutover.
What are the responsibilities of a parameteriser?
– Parameterising the Avaloq Banking System., Discussing parameterisation issues with the bank's key business users and business analyst., Analysing functionality deltas within upgrade projects and defining migration scenarios to bridge them.
What are the deliverables of a parameteriser in a release upgrade project?
– Upgrade specification, Source code according to specification, Detailed technical specification, Input for test manager, use feedback of test manager to fix bugs etc., Input for communicating with Avaloq
What is the Avaloq community?
A 24/7 information portal and knowledge resource for the Avaloq professional
What do you need to be able to use the Avaloq glossary?
Have a valid username and login to the Avaloq community
How do you find out how many documents are currently published in the Documentation Tool?
Use search and submit without entering search criteria
How do you find out which is the newest Avaloq release covered within a document in the Community?
Use search and open the drop down field called Release""
What do you need to have to be able to use the Avaloq Documentation Tool?
Username and password
Where can issues related to Avaloq releases / functionality from clients projects be entered?
Avaloq Issue Tool on Avaloq community website.
Which kind of issues is relevant in which project phase?
– Evaluation: GAP, Initial Project and Upgrade Project: all other types of issues
Which issues can be entered by the parameteriser into the Issue Tool?
Bugs and Questions
You have a frame identifier like 01.00. Does the 01 in the frame identifier represent the type of object the source is assigned to?
No, it represents just a naming convention but it helps to find the labels of frames in the table OUT_TEXT.
Why is it for a frame identifier not recommended to use the INTL_ID instead of the ID as a reference for an object –type?
The maximum length of the form order is limited to up to ten characters. If you used the INTL–ID instead of the ID for an object type then you may exceed the number of ten characters.
Are the keys historised?
No, they are not.
Do you have to check the public ID range when parameterising keys?
No, I do not have to because the compiler assigns the ID in the public ID range.
What would be possibly necessary to parameterise additionally when you create a new key?
If not yet implemented it could be necessary to define a frame label in the table OUT_TEXT.
What sources are needed when parameterising client predefined values?
Client specific predefined values require editing more than one source (CODE_CONST_TYPE, CODE_CONST_.[Name of the addition], [the Addition on an object or on an order]).
