SENG 691Q: System Integration and ECommerce: An Overview for Software Engineers WVU MS Software Engi

1
SENG 691Q System Integration and E-Commerce
An Overview for Software EngineersWVU MS
Software Engineering August 21,
2007Instructor Michael Evanoff
(evanoffm_at_mantech-wva.com) Use SENG 691Q in
subject of ALL emails!!!
2
Adminstrative Info
3
Software Engineering Program Information
For Advanced Students Fall 2007
Save these notes for future reference!
4
SENG Program Info
Program Coordinator Jim Mooney Lane Dept. of
CSEE Rm 941 ESB PO Box 6109 Morgantown WV
26506-6109 [phone] X2562 jdm_at_csee.wvu.edu
5
SENG Program Info
SENG Program website http//www.lcsee.cemr.wvu.ed
u/grad/degree-info.php?degreemsse
Check this site for up-to-date program
information. This is your primary reference! If
you find anything incorrect or missing please let
me know!
6
SENG Program info
Whats on the website?
1. General information about the program

• Admission Requirements
• Application Procedures
• Program Requirements
• Graduation Procedures

7
SENG Program info
Whats on the website?
2. Course information

• Course Info and syllabi (general course info for
  current and upcoming semesters)
• Current Classes (link to current class slides and
  web resources, password protected)

8
SENG Program info
Whats on the website?
3. Online forms

• Plan of Study (download and edit)
• Transfer from Non-degree status (complete online)
• Certificate Request (complete online)

9
SENG Program info
Registration reminders

• Register online using the STAR system
• E-mail me courses you are planning to take
• I will e-mail you your PIN number
• A new PIN is needed every term, but summer and
  Fall PINs are the same.
• E-mail me in case of any problems.

10
SENG Program info
Registration reminders

• Allow enough time -- request your PIN early!
• You cannot register online after classes start!

11
SENG Program info
Registration notes
Out-of-state students can pay in-state fees only
if you register exclusively for web-based course
sections! For questions on costs, tuition, fees
and payments, etc. contact Extended Learning
(1-800-2LEARN2). I do not have answers to other
financial questions.
12
SENG Program info
Experiential Learning

• Experiential Learning is an independent study
  (term paper)
• Appropriate for students currently working in the
  software development field
• Should be taken after most other courses are
  completed.

13
SENG Program info
Notes on the SENG Certificate

• Most useful for those who do not plan to complete
  the MSSE, or want interim certification of
  progress.
• Probably not useful to you at the time of
  graduation.
• Do not request the certificate on your Plan of
  Study unless you actually want it!

14
SENG Program info
Experiential Learning

• TOPIC Discuss the ways in which the courses you
  have taken have changed the way that you are
  doing your job.
• See the syllabus on the program website.
• If you have questions, contact Jim Mooney.

15
SENG Program info

• Is this your graduation semester?
• If so, dont forget
• You must be registered for at least one credit
  hour in your graduation semester.
• You must submit an Application for graduation to
  Linda Cox, CEMR Graduate Records Officer, Room
  141 ESB, with a check for 30 payable to WVU, by
  the deadline date (to be announced soon).

16
SENG Program info

• Is this your graduation semester (cont.)?
• 3. You must submit to me your Plan of Study form
  as found on the MSSE website, filled out (typed)
  and signed by you. If you are in the coursework
  option, I am your committee chair. I will obtain
  the other signatures and submit this form to
  Linda Cox.

17
SENG Program info

• Is this your graduation semester (cont.)?
• After the above steps are completed, you must
  sign the Final Approval form and complete the
  Exit Survey which Linda Cox will provide you. Be
  sure you use only the Final Approval Form
  designed for the coursework only option!

18
SENG Program info

• Is this your graduation semester (cont.)?
• Steps 2 and 4 must be arranged with Linda Cox
  directly. She can be reached at 304-293-4821
  X2219 or Linda.Cox_at_mail.wvu.edu. You should ask
  for the final approval form and exit form when
  applying for your diploma.

19
SENG Program info
Good Luck! Save these notes! Use the website!
Most common questions will be answered there!
20
SENG 691Q System Integration and E-Commerce
An Overview for Software EngineersWVU MS
Software Engineering August 21,
2005Instructor Michael Evanoff
(evanoffm_at_mantech-wva.com) Use SENG 691Q in
subject of ALL emails!!!
21
Introductions

• Mike Evanoff, Technical Director ManTech
• DoD Enterprise Integration e-Commerce
  Background
• Individual Introductions
• Name, occupation / title, related experience
• Expectations for this course

22
Preliminary Information

• Class Procedures
• Attendance, Questions Answer time, breaks, etc.
• Course Description and Objectives
• Course Outline
• Assignments (20), Projects (40), Tests (40)
• Note The course grade will be based on
  assignments, projects, midterm and final exams.
• The grading scale will follow the standard
  90-80-70 measure.

23
Course Description

• This course will provide a working understanding
  of the origins, development and future of the
  E-Commerce and System Integration technologies,
  tools, and standards. The role of key enabling
  technologies like EDI, Java, XML, metadata, SOAs,
  et. al. will be highlighted. The course will
  shed light on both the technical and business
  implications of the changes being generated by
  E-Commerce and Systems Integration.

24
Course Description

• The course will provide an understanding of the
  dynamics of innovation and the organizational
  consequences of moving business and information
  to a Net-Centric environment. The course will
  provide an evolutionary "roadmap to the future"
  for e-enabled applications and related tools and
  technologies. Lastly, the course will provide an
  overview of the technical, cultural,
  organizational, and geo-political issues
  impacting the future of E-Commerce and System
  Integration technologies.

25
Course Objectives

• Expose you to core e-Business standards /
  specifications
• From a functional service view and from a
  business operations view
• Define e-Business (Overview, Process Components,
  etc.)
• Define e-Business System Architecture
• Run time
• Design time (BPEL, Orchestration, Workflow, etc.)
• Define e-Business Enterprise Framework

26
Course Objectives

• Expose you to commercially available e-Business
  tools
• Delineate between design / development time vs.
  run time functions
• Several Homework assignments (four to five)
  assessing leading vendors / tools for each layer
  of services
• Project(s)- expose you to core e-Business
  infrastructure enablers
• Compare contrast emerging architectures as
  platforms for building an e-Business applications
• Provide you with an in-depth example of a real
  live e-Business systems from design time to
  runtime
• Final project will bring together every facet of
  this course
• Develop a use cases, requirements spec systems
  architecture for industry e-Business application

27
Text Books

• 1. "Enterprise SOA Service-Oriented
  Architecture Best Practices (The Coad Series),
  Prentice Hall PTR ISBN 0131465759 .
• 2. "e-Business 2.0 Roadmap for Success, 2/e", by
  Ravi Kalakota and Marcia Robinson is a 2nd
  edition and is published by Addison-Wesley Pub
  Co ISBN 0201721651.

28
Course Outline / Schedule
29
Course Outline / Schedule
30
Course Outline / Schedule
31
Lecture One Agenda
Definitions / History - EB/EC/EDI Defined Part
One - EDI Concepts Part Two - How EDI Works -
Transaction sets/Messages, data segments,
data elements, composite/components Part Three -
How EDI Works - Interchange/Envelope
structures Part Four - How EDI Works -
Translation Part Five - How EDI Works -
Security Part Six - Summary - Putting It All
Together
32
Definitions

• E-Business (EB)
• The application of electronic commerce techniques
  and solutions to the business processes of an
  organization.
• E-Commerce (EC)
• Transacting business via electronic means. This
  includes all forms of electronic media such as
  FAX, E-mail and EDI. Electronic Commerce is NOT
  restricted to EDI only.

33
Definitions

• Electronic Data Interchange (EDI)
• The automated exchange of transaction data
  between two or more interoperating application
  program the computer-to-computer transmission of
  (business) data in a standard format.
• C-Commerce, Evolving Commerce, etc
• E-Commerce can be a very blurry topic

34
E-Commerce History

• The foundations on which electronic commerce is
  based started 125 years ago with the use of
  telegraph technology to relay information
  concerning the transfer of funds, such as the
  stock ticker and Western Union's Money Transfer
  system.
• Payment for goods with payment instruments and
  representations thereof, namely the advent of
  credit cards in 1914, revolutionized commerce for
  consumers, as needs for efficiency and ease of
  transactions were met.
• Mainframe-based e-Commerce application systems
  emerged in the early 1960s
• The Internet was conceived in 1969, E-Mail 1972,
  WWW early 1990s

35
Part One
EDI Concepts
36
What is EDI? Electronic Data Interchange is the
exchange of standardized business documents from
computer to computer. Documents such as purchase
orders and invoices are transmitted from one
computer to another in a mutually agreed upon
electronic (paperless) format.
37
EDI The Definition
Purchase Order ------------------------
Company A
Company B

• EDI is a critical part of Electronic Commerce
  because it enables computers to exchange data
  electronically, which is much faster, cheaper,
  and more accurate that paper-based systems. To
  gain the maximum benefits of EDI, an
  organizations systems must have two
  characteristics
• the flow of information must be integrated
• the automated business management systems must
  be intelligent.
• These systems must be able to automatically
  process routine transactions according to those
  limits defined by the businesses conducting trade.

38
EDI System Components
Knowing the standards and having an EDI
translator is not enough. EDI cannot be done
efficiently without being integrated with other
components.
39
EDI System Components SOFTWARE
The application interface software is the
software bridge developed to facilitate the
interface between the automated business
management system software and the standards
translation software.
40
EDI System Components COMMUNICATIONS

• Value Added Network (VAN)
• Value Added Service (VAS)
• Internet (www)
• Direct Dedicated Connection

What's the difference between a VAN and a VAS?
A VAN is only responsible for moving your
transaction through a network to the addressee.
A VAS, however, normally provides translation
services, conversion from FAX or Internet to EDI,
security, reports, troubleshooting, etc. Some,
but not all, VANs are also VASs.
41
EDI System Components HARDWARE

• Workstations
• LANs
• Mainframes/Servers
• Routing Devices
• Intranets
• Gateways

42
EDI System ComponentsSTANDARDS

• ASC X12 Transaction Sets
• American National Standards Institute (ANSI),
  Accredited Standards Committee X12
• Data descriptions of business functions
  (invoicing, purchasing, applications, etc.)
• UN/EDIFACT
• United Nations rules for Electronic Data
  Interchange For Administration, Commerce and
  Transport
• Comprise a set of internationally agreed
  standards, directories and guidelines for the
  electronic interchange of structured data

Please note that X12 and EDIFACT terms will be
used interchangeably throughout this presentation.
43
EDI System ComponentsSTANDARDS

• What is an Implementation Convention??
• An Implementation Convention or IC is a subset
  of a standard which represents an agreement among
  EDI Trading Partners on how transaction sets or
  messages will be used in a specific business
  context.
• Different conventions in use today are being
  consolidated into a common convention that will
  represent the Single Face to Industry concept.
• FEDORDER would be one example of an UN/EDIFACT
  Implementation Convention for the ORDERS message

44
The Business of Paper
Business is buried in paper. Decisions are
delayed by it. Mistakes are made because of
it. Costs are incurred in transmitting it, not to
mention to costs of creating it in the first
place.
45
So how is it that after over 35 years of modern
computing, and an even longer experience of
modern data communications, business is still
buried under a mountain of paper? Why
is it such a problem to communicate between
computer applications?
46
In a word...
STANDARDS
47
Hello?
Bonjour?
Bon Jour!
There can be no doubt that standards are a
desirable prerequisite for commerce - especially
international trade and communications. However,
the standards of which we are most concerned
revolve around communication protocols and
document standards.
48
EDI Standards

• EDI Standards facilitate Electronic Data
  Interchange by providing
• Rules of syntax
• Definition of the data organization
• Editing rules and conventions
• Published public documentation
• Mutually defined transmission protocols
• What is the objective in using EDI Standards?
• Simply to develop an agreed upon structure of
  communicating the data in ordinary business
  documents in a machine readable format.
• Standards prescribe the framework for how a
  specific EDI message is formatted.

49
Origins of EDI Standards

• 1960s - several industries invented their own
  sets of standardized data formats including
  Transportation Data Coordinating Committee (TDCC).

• 1970s - grocery industry developed Uniform
  Communication Standard (UCS).

• 1979 - TDCC and the Credit Research Foundation
  achieved official sanction from the American
  National Standards Institute (ANSI) to establish
  the Accredited Standards Committee X12 for
  Electronic Data Interchange (ASC X12), primarily
  used for American domestic trade.

• 1987 - Electronic Data Interchange for
  Administration, Commerce, and Transport
  (UN/EDIFACT) was announced for international
  trade.

• 1992 - ASC X12 members approve adoption of
  UN/EDIFACT as the single EDI standard, although
  alignment of X12/EDIFACT is not yet popularly
  embraced by the Western business world in 1999.

• Late 1990s - XML/EDI in development.
• Early 2000s Web Services based on Next
  Generation EDI

50
Why Use EDI??

• EDI Direct Benefits
• Eliminate duplicative efforts such as re-keying
• Reduce mailing and copying costs
• Improve cash management
• Reduce storage of paper documents
• Control operational costs
• Sanity

• Implementing EDI will often give companies an
  opportunity to review current business practices,
  and identify ineffective or inefficient
  processes.
• Stock holdings are ultimately reduced and better
  managed within user companies.
• Information about present and forecast business
  activities can be shared
• Companies are better able to respond efficiently
  to changing customer demands and expectations.

51
Why Use EDI??

• EDI Indirect Benefits
• common standard
• streamlined process
• centralized data and access
• reduced requirements
• improved customer relations
• quality control
• optimization
• competitiveness

52
How EDI Works
Part Two

• Transaction Sets/Messages
• Data Segments
• Data Element
• Composite/Components

53
Transaction Set/Messages
As previously noted, EDI is the electronic
exchange of business information using standard
machine-processible data formats. A standardized
formatted message is called a transaction set
(ASC X12) or message (UN/EDIFACT), which is the
electronic equivalence of a paper
document. Example transaction set/message

54
Transaction Set/Messages, contd.
Transaction sets provide the structure of the
segments to be used including
55
EDI Data Dictionary

• The definitions of all Data Elements contained in
  a Transaction Set are contained in a Data Element
  Dictionary provided with each Transaction Set
  standard.
• A Data Element Dictionary identifies the
  reference designator, title, reference number,
  requirement designator, type, and length of each
  Data Element contained in each transaction set
  standard.
• The user can look up the definitions of specific
  Data Elements from this dictionary.

56
Transaction Set/Messages, contd.
57
Transaction Set/Messages Structure Explanation
The Header area of a transaction set contains
preliminary information that pertains to the
entire document, such as the date, company name,
address, and terms. The Detail area or line item
area of a transaction set encompasses the
business transaction and includes information
such as quantities, descriptions, and prices. The
Summary area contains control information and
other data that relate to the total
transaction. In EDI, each line of data is called
a segment, and each item within the segment
becomes a data element. To facilitate an
electronic transmission, data is converted to an
EDI document format and appropriate element
separators and terminators are applied as agreed
upon with your trading partners.
58
Data Segments
Each transaction set is made up of a collection
of data segments- the 2 or 3 character
abbreviation used as reference in the Segment
Directory. Data segments, also known as Segment
Tags, begin each line or record in an EDI data
string. Similar to a postal address, NAD would be
an example data segment, reporting geographic
location, and including the data elements for a
city name, a state or province code, a postal
code, and a country code. Data segments
logically relate data elements in a defined
sequence. An example of how the NAD segment
might be used is as follows NADSTKAFB160Kee
sler Air Base14 Fish StreetKeesler AFBMS

39534US
59
N1 (Name) X12 Data Segment example
objective to identify a party by type or
organization, name and code
60
Data Elements

• Data elements, the smallest unit of information
  in a transaction set/message, represent a
  qualifier, a value, or text and are identified by
  a reference number in the Data Element
  Dictionary, defining the specifications for each.
• Data elements have three principal attributes
• Condition designator (mandatory, conditional,
  optional)
• Type of data element (ID, alphanumeric, numeric
  or decimal, etc.)
• Character length (minimum/maximum length)

Example Data Element 654 - Discount Base Qualifier
61
Composite/Component Data Structures

• UN/EDIFACT and newer versions of ASC X12 may use
  two separate pieces of data in a single data
  element. The complete data element is called a
  composite data element. The pieces of the
  composite are called components.
• The structure of many data segments includes one
  data element for a value and a second data
  element for a qualifier. A composite data
  structure, on the other hand, contains within a
  single data element both a qualifier and a value.
  A data dictionary would be required to define the
  qualifier.
• When composites are used with variable type
  data, the First component is
• typically the value being qualified. The second
  component is typically the
• qualifier, which defines what the first component
  (the value) means.
• CTAICPurchJohn Smith

Composite Data Element
Component Data Element
62
Composite/Components (cont.)
CTA Segment
COM Segment
CTAICPurchJohn Smith COM3045551212TE (Te
lephone) CTAICSalesBob Evans COM3045551213
FX (Fax) CTAICAcctMary Jones COMmaryjones
_at_juno.comEM (email)
CTA/COM Data String Example
63
How EDI Works
Part Three

• Interchange/Envelope Structures

64
The Envelope, Please...
When mailing a letter, paper purchase order,
invoice, statement or other form of paper
document, one would first enter the necessary
data, double-check the integrity of the data,
print the documents and place into an envelope.
If the document(s) consisted of multiple pages,
ordinarily they would be assembled together in a
logical order by type, page number, or
recipient. The envelope would be completed with a
return name and address, a delivery address, and
postage. Once at the post office, the envelope
information would be validated, then routed and
delivered to the recipient. Just as paper
documents would be completed, similarly would
electronic documents.
65
Structure of an EDI Interchange
In the world of EDI, an electronic transmission
of enveloped, formatted data is known as an
interchange. An interchange is the set of
information transferred as a whole which contains
an EDI message(s) and may be functionally
grouped, or separated by document type (i.e. POs,
Invoices, Ship Notices, etc.) As previously
noted, at the beginning and end of an
interchange, header and trailer information is
provided with general information about the EDI
messages being interchanged, including addressing
information. Note that if the EDI messages are
functionally grouped, then each of these
functional groups will also have a header and
trailer. Imagine a large, outer envelope
containing one or more smaller envelopes, each of
these containing different documents an envelope
for orders, one for invoices, possibly another
with price information. Each of these inner
envelopes would have routing or forwarding data
printed on the outside. In this same manner, so
is the objective of the EDI Interchange.
66
Structure of an EDI Interchange, contd

• An interchange header contains the following
  information
• An interchange trailer contains
• Count of messages or functional groups in the
  interchange
• Unique interchange reference (identical to the
  value in the header)

67
Structure of a Functional Group

• A functional group header contains
• Identifier for type of message held in the
  functional group
• Application sender identifier
• Application recipient identifier
• Date and time of preparation
• Unique functional group reference
• Agency responsible for specification of
  structure message type (X12, EDIFACT, etc.)
• Message type version
• Password
• A functional group trailer contains
• Count of messages within the functional group
• Unique functional group reference (Identical to
  value in header)

68
ASC X12 and UN/EDIFACTInterchange Structure
comparison
69
EDI Envelope Structurewith one Functional Group
Purchase Order Data Segments
Example ASC X12 850 Purchase Order
70
EDI Envelope Structurewith multiple Functional
Groups
850
Purchase Orders
850
Invoice
810
Price/Sales Catalog
832
71
Part Four
How EDI Works
Translation
72
Translation Validation

• The translation process involves reading a file
  of data through a translation program, during
  which the program will perform a check for
  compliance (to a given standard) against
  predetermined criteria, if not completed by the
  application system. Some of the validation
  checks for
• Minimum/maximum field size in a given document
  type
• Mandatory fields contain data
• Optional and conditional requirements of the
  data are met
• Data sequence - by element, segment, data set or
  document
• Correct data types in fields (alphabetic,
  numeric, alphanumeric, ID)
• .

73
Translation Validationcontd
The translation software matches batch/document
control numbers, destination, and the trading
partners numbers against internal tables and
either validate or reject the batch/documents. Fun
ctional acknowledgments may be generated by the
translation software. Data is translated
according to rules, syntax and data dictionaries,
with appropriate data segment terminators and
data element separators. The data is then
compressed and organized into one continuous data
string and surrounded by the communication
protocol envelope for data transmission
74
Part Five
How EDI Works
Security
75
Security Against What?
EDI Security consists of ensuring that your
messages reach their authorized destination, on
time, complete, and unread by any unauthorized
persons or computer. Banks insist on security
procedures to ensure that funds transferred reach
the right accounts on time, and if they go
astray, they can be retrieved. Armed forces,
aware that many routine procurement instructions
can inform potential opponents of operational
strength and location at a given time, insist on
security. Many commercial and government
enterprises are adopting the same techniques for
security of which Financial institutions are
using. Everyone involved with data processing and
data communication is concerned with security of
data. Defense not only need be just effective,
but also cost effective.
76
Security Against What?contd

• At the moment, there are three main security
  techniques for EDI
• Data encryption
• Message authentication
• Use of token technologies/electronic signatures

77
How EDI Works
Part Six

• SUMMARY
• Putting it All Together

78
EDI Concepts - Summary

• So far, weve learned the following about EDI
  Concepts
• What EDI Is
• System Components
• Standards
• the Paperless Environment
• Benefits in using EDI
• Then weve seen how EDI Works
• Transaction sets
• Data segments and data elements Data elements
• Composite/component elements
• EDI Envelope structures and Interchanges
• Security
• Now, lets take a look at how we put it all
  together for transmission...

79
Application Interface Outbound

• AIS Automated Information System (i.e. back
  end system)
• UDF User Defined File

80
Flow of EDI Document - Outbound
81
EDI Communications -VAN and/or Direct Dial-up
82
Flow of EDI Document - Inbound
83
Application Interface Inbound
84
(No Transcript)
85
In Conclusion...

• E-Commerce, for all of the pioneering work that
  is being done, is still in its infancy. Over the
  next several years or so the number of users /
  agents will climb an order of magnitude.
• We are moving into the second generation of EDI,
  a generation made possible by the new
  technologies, tools, and standards.
• The final message is that although EDI is an old
  standard, it is well founded and it continues to
  gain use across industry it is the cause of a
  new breed of e-Business applications,
  particularly with advances relative to the World
  Wide Web and Internet technologies.

86
Assignment 1

• For next class submit a report via email that
  includes the following items (follow this
  format)
• Your Name
• Your Primary Email for this class
• Your Occupation / title
• Description of your E-Commerce / Systems
  Integration background
• On the job experience with Service Oriented
  Architecture (SOA), Web Services, XML,
  Biometrics, or other related areas.
• Write-up of your expectations for this course

87
Next Class

• We will discuss the role of specifications and
  standards as they apply to E-Commerce
• We will discuss how the Web and Internet are
  impacting and reshaping EDI
• We will identify some of the key standards body
  organizations and their roles
• Identify and describe e-Business
• General Business Process Building Blocks
• System Architecture
• Enterprise Framework
• Horizontal / Vertical
• Inward looking / Outward looking
• Get books start reading chapters one thru five
  of the e-Business 2.0 Roadmap for Success,
  2/e book