CODEPAINTER Revolution Trainer Course - PowerPoint PPT Presentation

About This Presentation
Title:

CODEPAINTER Revolution Trainer Course

Description:

They do not have database tables. ... Library Management. Trainer Course. Max Vizzini Zucchetti International Operation. COFFEE BREAK ... – PowerPoint PPT presentation

Number of Views:50
Avg rating:3.0/5.0
Slides: 34
Provided by: maxvi6
Category:

less

Transcript and Presenter's Notes

Title: CODEPAINTER Revolution Trainer Course


1
CODEPAINTER RevolutionTrainer Course
  • Max Vizzini
  • Zucchetti International Operation

2
Software Engineering
  • CODEPAINTER METHODOLOGY

3
What is Software Engineering all about?
4
Software Engineering
The Mythical Man-Month?
  • Go to the essence!

REUSE!!!
5
CODEPAINTER Methodology
  • Template-Based source code generation
  • Object-Oriented programming
  • Rapid Prototyping

REUSE
6
DOMAIN ANALYSIS
YOU DO NOT HAVE TO DO IT. WE DID IT FOR YOU!!!
7
MASTER FILE
  • Contains a Form for data entry and a Database
    Table.
  • Use it when records must be processed one by one
    (i.e. Each record is processed on its own).

8
MASTER/DETAIL
  • Contains a Form and two database tables (Master
    Table and Detail Table).
  • Master table contains all unrepeated fields.
  • Detail Table contains all repeated fields.
  • The primary key of the Detail Table is formed by
    the primary key of the Master Table plus all
    attributes constituing a key for the Detail Table.

9
DETAIL FILE
  • Costituted by a Database Table and a Form.
  • All the unrepeated fields are part of the primary
    key.
  • The primary key must also contain repeated field.
  • Usually this entity has a Parent/Child
    Relationship with a Master File.

10
ROUTINE
  • They do not have an user interface
  • They can represent functions, procedures and
    batches
  • They use a meta-language that is portable between
    different programming languages.

11
DATABASE TABLE
  • They do not have an user interface
  • They are usually linked with Routine and Dialog
    Window Entities.
  • They are used as working table or to store
    historical data.

12
DIALOG WINDOW
  • They do not have database tables.
  • They are usally connected with other entities
    with database tables.
  • They contain variables ONLY and they are quite
    used as Option Windows.

13
OUTPUT
  • They represent output like Zooms, Graphs,
    Reports, MS Word Documents, and MS Excel
    SpreedSheets.
  • These entities are defined during run-time using
    the Visual Framework generated with the
    application.

14
HOW ALL ENTITIES INTERACT AND EXCHANGE DATA?
LINKS
15
LINKS
  • Relationship
  • Parent/Child
  • Dataflow
  • Event
  • Read data ... from

16
Relationship Link
  • It establishes a referential integrity between
    the two tables belonging to the connected
    entities.
  • Some data can be read from one table to another.
  • Some back updates can be specified.
  • It has a direction (from Entity A to Entity B).

17
Parent/Child Link
  • It establishes a link between a Parent Entity
    and a Child Entity.
  • The Child Entity Primary key must be made with
    the Parent one.
  • Referential integrity is established between the
    two database tables.
  • When a row is deleted in the Parent ALL related
    rows are deleted in the Child.

18
Dataflow Link
  • It represents the flow of data between entities.
  • A Routine Entity must be placed at one link end.
  • No code is generated. Documentation purpose ONLY.

19
Event Link
  • This link establishes a triggering event for a
    given Entity.
  • The Database Table Entity cannot be triggered by
    an event.
  • The list of Events is not customizable.

20
Read data ... From ... Link
  • It shows how Routine, Dialog Window and Output
    Entities read data from other entities.
  • It is used for documentation purpose ONLY.
  • No code is generated.

21
Cardinalities Relationship Link
0,1
0...N
0,1
0...N
0,1
0...N
22
Cardinalities Parent/Child Link
0,1
1
0...N
1
0...N
1
23
Questions?
24
Example
Customer Requirements
Manage a Warehouse so that it is possible to add
/ modify / delete items, and place purchasing
orders. In particular, each item must have a
V.A.T. code, and a set of price lists associated.
25
Solution
Items
Orders
Price Lists per Item
26
Solution 2
Price Lists
V.A.T. Rates
Items
Orders
Price Lists per Item
27
Items Entity
  • ITEMS
  • ItemCode Char(8) Primary Key
  • ItemDescr Char(40) Secondary Key
  • ItemVAT Char(8)
  • ItemStock Num(10)

28
Price Lists VAT Rates Entities
  • PRICE LISTS
  • PLCode Char(8) Primary Key
  • PLDescr Char(40) Secondary Key
  • VAT RATES
  • VATCode Char(8) Primary Key
  • VATDescr Char(40) Secondary Key

29
Orders Entity
  • ORDERS
  • OrderCode Char(8) Primary Key
  • OrderDate Date
  • CPROWNUM Num(8) Rep. Primary Key
  • OrderItem Char(8) Rep.
  • OrderQty Num(10) Rep.

30
Price Lists Per Item Entity
  • PRICE LISTS PER ITEM
  • PLIItem Char(8) Primary Key
  • PLICode Char(8) Rep. Primary Key
  • PLIPrice Char(8) Rep.

31
Links
VATCode ?(R) ItemVAT
PLCode ?(R) PLICode
ItemCode ?(R) OrderItem
ItemCode ?(P/C) PLIItem
ItemStock ?(R) lt-- OrderQty ()
32
EXERCISELibrary Management
33
COFFEE BREAK
Write a Comment
User Comments (0)
About PowerShow.com