Use Cases for Mapping Between Various E-Business Standards (BHD)
Discussion (BHE)
- On the 1st iteration, let's keep it simple. I suggest we capture a use case with a very simple, even text-only (diagrams optional) format, by: (BHF)
- (BHG)
- 1. Naming the Use Case; (BHH)
- 2. identifying its "Goal" and "Primary Actor(s)" (BHI)
- 3. describing its primary scenario (successful end) as a sequence of numbered steps; (BHJ)
- 4. describe alternative scenarios (including failed end) and others, as variations on the above sequence; (BHK)
- 5. optionally, make a top-level use case diagram. (BHL)
this should be a short (1 page) draft just to quickly document the ideas and to ensure top level alignment of the interpretation of those ideas among the parties involved. This follows the example shown on Figure 3-1 (p.40) of Martin Fowler's "UML Distilled (2nd Edition)" may be a good reference for us. (see UseCasesSimpleTextExample) (BHM)
- On the 2nd iteration, may I suggest we will follow the framework set out in Alistair Cockburn's Sample Requirements Document Chapter 2. (BHN)
- also refer to UseCasesDocumentTemplate (BHO)
- Before writing up this use case, we may have to decide on which two eBusiness standards (or maybe even a small number of them) that this use case will be applied to. (BHP)
- May I suggest that, for this Use Case, we employ the UBL-Ontology to enable semantic interoperability between two disparate e-business standards, e.g. sending a Purchase Order between a RosettaNet-based buyers to a UDEF-based seller (this needs deliberation, please suggest and substantiate that suggestion) through mapping into our UBL-Ontology (assuming we already have one.) (BHQ)
Iteration-1: Quick Capture of the Draft Use Cases (BHR)
- Use Case Name: Mapping Between Standards (BHS)
- Goal: (BHT)
- Primary Actors: (BHU)
- Primary Scenario (successful end): (BHV)
- Alternative Scenario-n (failed end): (BHZ)
- step nn. (BI0)
- Alternative Scenario-n (failed end): (BI1)
- step nn. (BI2)
- Use Case Diagram (optional) (BI3)
Iteration-2: Documenting the Use Cases (BI4)
- Mapping Between Standards (BI5)
2a. The Primary Actors and their General Goals (BI6)
- List Actors, along with a breif description of the roles of each of them. (BI7)
2b. The Business Use Cases (BI8)
- Tabulate Outermost Goals, with the following columns: (BI9)
- Tabulate Task Level Goals, with the following columns: (BIE)
2c. The System Use Cases (BIJ)
- Use Case 1: name primary use case (BIK)
- Use Case Diagram(s) (BJ1)
- Use Case n: name use case (BJS)
- Use Case n: name use case (BK2)
3. The Terms Used / Glossary (BKC)
Work in Progress (BKF)
Notes from Task Team Conference Calls 2003-04-23 12:00pm-1:00pm PDT Conference Call (BKG)
- Attendance: SueProbert / JohnYunker / PeterYim (BKH)
- Purpose : To establish "what exactly" would we want to do in writing up the use cases: (BKI)
- 3. Mapping Across Different Standards --JohnYunker / PeterYim / SueProbert, and (BKJ)
- 2. Proper Address Format driven by Context --SueProbert / PeterYim. (BKK)
- AOB (BKL)
- Sue, please help introduce us at the UBL London F2F (BKM)
- Notes / Draft for Use Case 3. (BKN)
- JohnYunker's comment: (BKO)
- understanding of the role of context and information building blocks in successful execution of the use case would be essential (BKR)
- SueProbert: controlled vocabulary (and the mapping of such) will be important (BKS)
- Parallel efforts: ebXML work under TBG and its domain groups (BKT)
- UBL identifying document structures (BKU)
- UN/CEFACT CC (group or element) -- identification of properties, context qualifiers and object name; and the library that contain it (BKV)
- UN/CEFACT Harmonization (coordinated with a similar UBL effort); maintains the properties that is used across domain (BKW)
- UN/CEFACT CCSD (BKX)
- SueProbert: in need of a repository; possibly a distributed one (BKY)
- SueProbert: important that the work stays OPEN (BL0)
- JohnYunker: ability to capture the object state (shared by processes) will be important (BL1)
- JohnYunker: our work will be to establish a framework for classification of elements of an ebusiness standard in terms of the CC/BIE/Document/Object/ContextQualifier ontologies and guidelines for using this classification to filter candidate UBL elements for construction of the mapping. (BL2)
- Notes / Draft for Use Case 2. (BL3)