1 / 21

T2.4: Business Process Re-engineering

T2.4: Business Process Re-engineering. Four viewpoints: Business (process): T1.6 Information system (functions, macroscopic flows): T2.4 Software systems (software, component, project,…): T2.2 Physical systems: Infrastructure and enterprise network elements (hardware machines, …): T2.2.

kevork
Download Presentation

T2.4: Business Process Re-engineering

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. T2.4: Business Process Re-engineering

  2. Four viewpoints: Business (process): T1.6 Information system (functions, macroscopic flows): T2.4 Software systems (software, component, project,…): T2.2 Physical systems: Infrastructure and enterprise network elements (hardware machines, …): T2.2 Global vision Business representation FLUX Zone 2 Zone 3 Zone 1 IS representation Software systems representation Physical infrastructure representation REGNET review

  3. Objectives (1/2) • Complete and detailed specifications of the selected processes to be implemented in the version 2 of REGNET System. PARTNERS : • MUSEUM : TINC and MUS. • ARCHIVE and LIBRARY : IMAC and AIT. • ART GALLERY : ICCS . REGNET review

  4. Objectives (2/2) • Translation of the specifications provided in UML language (class diagram). • Prepare ebXML deployment PARTNER : • UML Modelling : VALT. REGNET review

  5. Methodology (1/3) • The previous step - Business Processes Modelling :In the WP1 (task T1.6), we defined, organised and mapped (use case diagram) the business of the cultural heritage domain.This organizational context for the system is presented in the deliverable D3. REGNET review

  6. Methodology (2/3) • The 1st step – The detailed specifications use cases of REGNET’s System : • The content providers selected the use cases to be implemented in the version 2 of REGNET. • Then, for each use case or sub use case, the workflow of the dialog between the actors and the REGNET’s System was expressed. REGNET review

  7. Methodology (3/3) • 2nd step : the object oriented model. • From the use cases specifications, the domain (or sub-domain) model is built.Class diagram which could be completed by collaboration diagrams. REGNET review

  8. Museum domain The Museum Domain has been splitted into 5 sub-domains For each sub-domains Use Cases have been specified REGNET review

  9. Use Case Specifications REGNET review

  10. From Use Case to Class Diagram ( i.e. : Loan Category) Attribut Concept Association REGNET review

  11. From Class Diagram to Category REGNET review

  12. Example of Categories identified from Collection Management Use Cases Holds information about the objects in the collection, including: cataloguing, registration, location, valuations Tracks incoming and outgoing loans, and links directly to Constituents and Objects categories. Arrangements for moving objects from one location to another, linked directly to Loan and Exhibition Categories REGNET review

  13. T2.4 - Business PROCESS (Re-engineering). • Next step: integration of Business Processes into ebXML registry REGNET review

  14. Museum X Request ebXML specifications 1 2 ebXML specifications detail ebXML Repository Register scenarios and implementation details Register company business profile ebXML Software 4 ebXML BO Library 5 Confirm profile and scenarios accepted 3 ebXML BP Model Specifications Build local system implementation Profiles Query about Company X 12 7 Accept CPA 9 Scenarios Company X’s Profile Submit CPA 8 6 Request Company X’s Scenario 11 Company X’s Scenario 10 ebXML Software ebXML BO Library Museum Y REGNET review ebXML BP Model

  15. Borrower Lender UN/CEFACT UMM: Business Process as activity diagram REGNET review

  16. Conversion UML -> XML Business process definitions XML Schema and DTD generation Populate classification scheme XML Schema XML Process Definition Transformation Rules XMI (MOF.DTD) Populate Classification Scheme REGNET review

  17. BPSS: XML version <?xml version="1.0" encoding="UTF-8"?> <!-- edited with XML Spy v4.3 U (http://www.xmlspy.com) by Dubois (Valtech) --> <ProcessSpecification version="1.0" uuid="" name="Simple" xmlns="http://www.ebxml.org/BusinessProcess" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.ebxml.org/BusinessProcess D:\Projets\CPPETB~1\ebBPSS.xsd"> <BusinessDocument name="Loan Application Form Request"/> <BusinessDocument name="Loan Application Form"/> <BusinessDocument name="Request ACK"/> <BusinessDocument name="Loan ACK"/> <BusinessDocument name="Loan rejection"/> <BusinessDocument name="Object Information Request Form"/> <BusinessDocument name="Object Description"/> <BusinessDocument name="Loan Agreement"/> <BusinessDocument name="Loan Agreement Receipt ACK"/> <BusinessDocument name="Loan Agreement ACK"/> <BusinessDocument name="Receipt Schedule"/> <BusinessDocument name="Receipt Schedule ACK"/> <BusinessDocument name="Shipment Notification"/> <BusinessDocument name="End of business Document"/> <!--**** The Binary Collaborations ****--> <BinaryCollaboration name="BorrowLend"> <InitiatingRole name="Borrower"/> <RespondingRole name="Lender"/> <BusinessTransactionActivity name="Request Loan Application Form" businessTransaction="Request Loan Application Form" fromAuthorizedRole="Borrower" toAuthorizedRole="Lender"/> <BusinessTransactionActivity name="Request Loan" businessTransaction="Request Loan" fromAuthorizedRole="Borrower" toAuthorizedRole="Lender"/> <BusinessTransactionActivity name="Analyse Loan Request" businessTransaction="Analyse Loan Request" fromAuthorizedRole="Lender" toAuthorizedRole="Borrower"/> <BusinessTransactionActivity name="Query Object Information" businessTransaction="Query Object Information" fromAuthorizedRole="Borrower" toAuthorizedRole="Lender"/> <BusinessTransactionActivity name="Sign and Send Loan Agreement" businessTransaction="Sign and Send Loan Agreement" fromAuthorizedRole="Borrower" toAuthorizedRole="Lender"/> …… REGNET review

  18. CPP <?xml version="1.0" encoding="UTF-8"?> <!-- edited with XML Spy v4.3 U (http://www.xmlspy.com) by Dubois (Valtech) --> <tp:CollaborationProtocolProfile xmlns:tp="http://www.ebxml.org/namespaces/tradePartner" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" tp:schemaLocation="http://www.ebxml.org/namespaces/tradePartner D:\Projets\CPPETB~1\cpp-cpa-v1_0.xsd"> <tp:PartyInfo> <tp:PartyId>123456789</tp:PartyId> <tp:PartyRef/> <tp:CollaborationRole tp:id="N00"> <tp:ProcessSpecification tp:name="BorrowLend" xlink:type="simple" xlink:href="http://www.MuseumURL/BorrowLend.xml"/> <tp:Role tp:name="Borrower"/> <tp:ServiceBinding tp:channelId="N04" tp:packageId="N0402"> <tp:Service>IssueRequestForLoan</tp:Service> </tp:ServiceBinding> </tp:CollaborationRole> <tp:Certificate tp:certId="N03"> <ds:KeyInfo/> </tp:Certificate> <tp:DeliveryChannel tp:channelId="N04" tp:transportId="N05" tp:docExchangeId="N06"> <tp:Characteristics/> </tp:DeliveryChannel> <tp:Transport tp:transportId="N05"> <tp:SendingProtocol>HTTP</tp:SendingProtocol> <tp:ReceivingProtocol>HTTP</tp:ReceivingProtocol> <tp:Endpoint tp:uri="http://www.museumURL/servlets/ebXMLHandler"/> </tp:Transport> <tp:DocExchange tp:docExchangeId="N06"> <tp:ebXMLBinding/> </tp:DocExchange> </tp:PartyInfo> <tp:Packaging tp:id="N0402"> <tp:ProcessingCapabilities tp:parse="true" tp:generate="true"/> <tp:SimplePart tp:mimetype="text/xml"/> </tp:Packaging> </tp:CollaborationProtocolProfile> REGNET review

  19. ebXML Registry • Registry systems can give you information about many types of ebXML and even non-ebXML documents. - CPP’s and CPA’s - Business Process Documents (BPSS, others) • Core Components and CC Aggregates • Business Information Entities and Aggregates • DTD’s and Schemas (Assembly documents) • Programming artifacts REGNET review

  20. Negotiating an agreement • Find registry and search for partners • Examine CPP • Ascertain compatibility of business process and technical specifications • Produce Collaboration Protocol Agreement • Conditions under which two partners will conduct business transactions together • Modify application REGNET review

  21. ebXML registry deploiement • We have deployed ebxmlrr registry (open source initialy from SUN): http://ebxmlrr.sourceforge.net • Preliminary populated by some business processes • One of the first implementation in Europe REGNET review

More Related