Development in AB Suite - презентация, доклад, проект скачать

Нажмите для полного просмотра!

Содержание ▲

Вы можете ознакомиться и скачать презентацию на тему Development in AB Suite. Доклад-сообщение содержит 70 слайдов. Презентации для любого класса можно скачать бесплатно. Если материал и наш сайт презентаций Mypresentation Вам понравились – поделитесь им с друзьями с помощью социальных кнопок и добавьте в закладки в своем браузере.

Слайды и текст этой презентации

Слайд 1

Описание слайда:

Development in AB Suite

Слайд 2

Описание слайда:

Objective By the end of this module, you’ll be able to— Implement advanced concepts of AB Suite to develop an application

Слайд 3

Описание слайда:

Module Topics Model Hierarchy Keys Framework Methods Dictionaries Designing Presentations Class Diagrams Reference Elements Developer Security Documentation Working Effectively with Your Model

Слайд 4

Описание слайда:

Model Hierarchy

Слайд 5

Описание слайда:

Developing Model Hierarchy When you develop the hierarchy, keep the following in mind: Define relationships through inheritance and dependencies Instantiate classes through inheritance and reduce redundancy Use dictionaries to create common classes that are used throughout the model Group classes logically within folders for better maintainability Encapsulate the model elements using the Visibility property Document the model for easy interpretation on the model-business mapping

Слайд 6

Описание слайда:

Developing Model Hierarchy

Слайд 7

Описание слайда:

Keys

Слайд 8

Описание слайда:

Profile Keys What are keys? Keys provide an index to an ispec’s database records Keys help to uniquely identify individual database records Keys help in establishing the autolookup dependency between two ispecs Define the order that records are retrieved from the database. Only persistent attributes can be defined as keys

Слайд 9

Описание слайда:

Multi Keyed Classes You can specify more than one attribute as keys in an ispec. If more than one attribute forms the key, the combination of their values must be unique for each record. You can define multi keyed classes by: Using profiles and adding more than one key to a profile Setting the IsKey property for more than one attribute

Слайд 10

Описание слайда:

Multi Keyed Classes – Adding Keys to a Profile To define multiple keys in an ispec: Define attributes that you want to use as keys, but do not set the ‘IsKey’ property. Define a profile and add the required persistent attributes as keys in the appropriate sequence. You can specify the profile as the ‘default profile’ for an ispec.

Слайд 11

Описание слайда:

Framework Methods

Слайд 12

Описание слайда:

Framework Methods Framework methods are part of the runtime cycle of an element such as an ispec. The following flow shows how framework methods are invoked in the runtime cycle.

Слайд 13

Описание слайда:

Framework Methods Framework methods are: Construct, Prepare, and Main. Depending on the stereotype, the methods are invoked during the runtime cycle of an element such as an ispec or a report. Framework methods of ispecs with presentation can be overridden. For example, you can perform a specific validation check in the ispec’s Construct method. Framework methods might include variables to: Temporarily hold values Reference a specific instance of a class

Слайд 14

Описание слайда:

Dictionaries

Слайд 15

Описание слайда:

Dictionaries Dictionaries are useful for organizing classes that define attributes and variables in a model. When you add an element to the model, System Modeler will look for a dictionary item with the same name. If a match is found, the element's Inherits property will be set automatically to the item in the dictionary. When searching for a matching dictionary item System Modeler searches all dictionaries within scope, starting with the most local dictionary. The element definitions can be inherited across the model depending on the relative hierarchy where the dictionary is created.

Слайд 16

Описание слайда:

Dictionaries You can create dictionaries anywhere in your model. You can also create multiple dictionaries. A dictionary defined under a segment in System Modeler is available to all elements under the segment.

Слайд 17

Описание слайда:

Dictionaries

Слайд 18

Описание слайда:

Dictionaries A dictionary can also contain class definitions that may or may not have the Multiplicity set to = 0. This definition can then be inherited by an attribute in an Ispec or a report, or a variable under a method. In the following example, ACTION_LINE class is defined in the Classes dictionary. An attribute Action_Line within the PROD class automatically inherits from the dictionary definition to create an instance of that class.

Слайд 19

Описание слайда:

Designing Presentations

Слайд 20

Описание слайда:

Designing Presentations The Painter is used to design presentations or forms. A class can have a graphical presentation, a character-based presentation, or both. Report frames can only have a character-based presentation. PresentationType property of a class determines its presentation type.

Слайд 21

Описание слайда:

PresentationType Property The PresentationType property allows you to choose the type of presentation for a class. The choices are:

Слайд 22

Описание слайда:

Direction in Presentation Direction property of an attribute specifies how a control painted on a presentation passes data. Attributes with a Direction property value other than None are automatically painted on the presentation.

Слайд 23

Описание слайда:

Adding an Attribute to the Presentation To add a new attribute to the presentation you can drag the attribute from the class view to the painter.

Слайд 24

Описание слайда:

Adding New Controls to the Presentation You can add controls to the presentation by dragging them from the tool box.

Слайд 25

Описание слайда:

Working with the Grid Panel Grid Panels allow you to associate a set of group controls with one attribute. To create a Group control: Drag a Grid Panel from the ToolBox to the Painter. Drag the Group control from the Toolbox into the Grid Panel in the Painter. Repeat the controls for the number of occurrences required. For example, the following is a Grid Panel containing two Radio Buttons that represent one attribute - Question

Слайд 26

Описание слайда:

Moving Controls into a Grid Panel Using Ctrl key

Слайд 27

Описание слайда:

Moving Controls within a Grid Panel Using Alt key

Слайд 28

Описание слайда:

Synchronizing an Element With the Class View The Synchronize Class View option synchronizes the selected item with the Class View. You can also select Synchronize Class View option from the Edit menu. You can use this option to: View some of the properties of the primitive data type associated with the selected form objects such as button, check box, radio button, text field, password field, or text area View the properties of the element associated with the form Synchronize Class View can also be used in other views, such as the Members list, Search Results list, and Diagrams.

Слайд 29

Описание слайда:

Generalization in Presentation Generalization is an Object-Oriented concept that describes “is a” relationship between two classes With a generalization relationship between two classes, the common structure and behaviour are used from the specialized class to the generalized class

Слайд 30

Описание слайда:

Generalization in Presentation Example: Consider a class CUSTTAX that represents customers who pay tax that inherits from CUST

Слайд 31

Описание слайда:

Generalization in Presentation

Слайд 32

Описание слайда:

Composition in Presentation Composition is an Object-Oriented concept that describes a relationship between two objects where one object owns, or is made up of, other objects. A class with a presentation can be inherited by an object belonging to another class. This way some of the common presentation elements such as headers and footers can be reused and extended within a form.

Слайд 33

Описание слайда:

Composition in Presentation Example: Consider the CUST class that has an attribute named Action_Line that inherits from the ACTION_LINE class

Слайд 34

Описание слайда:

Composition in Presentation

Слайд 35

Описание слайда:

Logic Editor

Слайд 36

Описание слайда:

Logic Editor The Logic Status tab displays the list of methods. Double click a method to invoke its Logic Editor. The Logic Editor is used to add, edit, save, and validate logic.

Слайд 37

Описание слайда:

Logic Editor Highlights Dynamic Validation Immediately identify logic errors with the red squiggle Quick Actions Quickly and easily resolve logic errors Code Definition and Peek Definition View and edit logic without leaving the current method Personalize the experience Customize the look, feel, and features to suit your development style Debugger Conditional Breakpoints Break when logic conditions are met or hit counts are reached

Слайд 38

Описание слайда:

Logic Editor Settings The Logic editor options can be set from the Tools > Options menu. In the Options window, navigate to the LDL+ folder for setting Logic Editor features like Dynamic Validation, Quick Action, and Command Style.

Слайд 39

Описание слайда:

Class Diagrams

Слайд 40

Описание слайда:

Class Diagrams A diagrammatic representation of classes and their relationships. In this class diagram, the CUST ispec has an AutoLookUp dependency defined on the SREP ispec.

Слайд 41

Описание слайда:

Class Diagram Editor To create a class diagram: Add a diagram to an element in your model. Drag elements from the Toolbox or the Class View on to the Class Diagram editor.

Слайд 42

Описание слайда:

Modifying Class Specification To modify class specifications: In the Class Diagram editor, right-click the class entity and select Properties. Modify the required class entity properties.

Слайд 43

Описание слайда:

Defining Relationships

Слайд 44

Описание слайда:

Reference Elements

Слайд 45

Описание слайда:

Reference Elements A reference is used: To display an attribute that cannot be directly dragged onto the painter. For example, arrays, and attributes of other classes. To avoid the need for additional attributes and supporting logic to move values around.

Слайд 46

Описание слайда:

Reference Elements—Example

Слайд 47

Описание слайда:

Reference Elements—Example

Слайд 48

Описание слайда:

Developer Security

Слайд 49

Описание слайда:

Developer Security Developer Security is similar to Windows Explorer Security To set the security in Developer, the AccessControlled property must be set to true at the model level All elements in the model and the model itself can have security privileges applied to it You can control the security for either the entire model or individual elements within the model

Слайд 50

Описание слайда:

Developer Security AccessControlled property can be set by: Administrative users Model database owner (db_owner) Security admin of the model database (db_securityadmin) Security admin of the database server (securityadmin)

Слайд 51

Описание слайда:

Developer Security To set security for any element: From the View menu, select Class View to open the Class View window. Select an element in the Class View window. From the View window, select Properties Window. In the Properties window for the element, select the Security property. Click the ellipses button to the right of the window, to open the Windows Security dialog box.

Слайд 52

Описание слайда:

Developer Security In the Windows Security dialog box, you can add and remove users. Types of privileges you can set for the users: Full Control – Allows or denies the user to set the security information Read Logic – Allows or denies access to the logic of a method Build – Allows or denies access to perform a model build Write – Allows or denies access to modify any attributes of an element and all the privileges that applies to Read permission

Слайд 53

Описание слайда:

Developer Security The application user is denied write permission to the SampleDeploy folder. Select the Security option in the Build Comments Pages… dialog box. The Build Comments pages output displays the security options to help administer permissions to users.

Слайд 54

Описание слайда:

Documentation

Слайд 55

Описание слайда:

Build Comment Pages Used to create a detailed report of your AB Suite project Build the report of the entire model or Build a report on individual elements or classes Creates a hierarchical written display of your AB Suite project The report Lists the base class, all subclasses, and their members in the model. Identifies the name of the element, any description that you have provided for it, its member visibility, and the base class to which it belongs.

Слайд 56

Описание слайда:

Build Comment Pages Is displayed in the HTML Browser within Visual Studio after the report is generated as a file in a folder of your choice. Includes the security details of an element in the generated output

Слайд 57

Описание слайда:

Build Comment Pages

Слайд 58

Описание слайда:

Product Documentation Product Information Developer CD PI Only CD Online Help Unisys Support Web Site

Слайд 59

Описание слайда:

Product Documentation – PI Only CD All User Guides are published for a release Except Generator Customization Kit document Acrobat Reader display external to browser Search function of Reader Infopack

Слайд 60

Описание слайда:

Product Documentation – Online Help Functions available for Online help: Contents Index Favorites Find Context-sensitive help (F1)

Слайд 61

Описание слайда:

Readme Document AB Suite Readme document is supplied with every release of the product and provides information related to - New features and changes in the respective release Product limitations and known issues Installation specific instructions Readme document is updated for every Interim Correction (IC)

Слайд 62

Описание слайда:

Product Documentation – Unisys Support Web Site Documentation section https://www.support.unisys.com/common/epa/DocumentationLibraries.aspx?PLA=ABS&NAV=ABS

Слайд 63

Описание слайда:

Working Efficiently with Your Model

Слайд 64

Описание слайда:

Working Efficiently with Your Model Better ways to define: Insertables Group Attributes Ispecs Some points to remember

Слайд 65

Описание слайда:

Better Way to Define Insertables In AB Suite, an insertable stereotype is not required to define a common part of a screen. A class can have fixed, graphical, and print presentations. Presentation can be placed on ispec screens or frame layouts. Achieved by instantiating the class under the ispec or frame, and dragging the attribute onto the Painter.

Слайд 66

Описание слайда:

Better Way to Define Group Attributes A group stereotype is not required to visually group attributes. Attributes can be modelled under any class. Assignment between instances of the same class is allowed – this will perform a deep copy of all members. Groups are only required when moving an entire group to or from a string or another group with a different structure. Avoiding the group stereotype avoids generated code and memory used to express the whole group as a string.

Слайд 67

Описание слайда:

Better Way to Define Ispecs In AB Suite, it is possible to create a class with no stereotype which only has persistent members. The behavior will be identical to an ispec so long as no keys are defined. Ispec keys add a 1 character MAINT field to the table. Profiles can be added to any class with persistent members.

Слайд 68

Описание слайда:

Better Way to Define Global Attributes In AB Suite, you can avoid unnecessary declaration of global attributes. Alternatives are: You can declare parameters and variables to use with a method You can declare local attributes to ispecs and reports rather than declaring global attributes to be used in the application With the above two considerations, methods become ‘self-contained’ and do not depend on global items, enhancing the maintainability You can use global attributes where it makes sense and is necessary, for example, Latest_currency_value (banking application), Today’s_discount (retail store application).

Слайд 69

Описание слайда:

Points to remember... Understand the structure of your model and identify the elements from an object-oriented design perspective. Use the UML diagrams to create class diagrams. Use inheritance and dictionary elements to create new ispecs and attributes instead of copying and pasting them to reduce redundancy in your model. Use folders to logically group elements or build (generate) smaller sets of elements. Familiarize with the Painter tab, Toolbox, and various controls in Toolbox. Understand how attribute properties of the attributes influence the rendering on Painter.