Use Cases for Context Driven Address Formatting (B9Z)
Discussion (BA0)
- Writing up the use case: (BA1)
- (BA2)
- 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: (BA3)
- 1. Naming the Use Case; (BA4)
- 2. identifying its "Goal" and "Primary Actor(s)" (BA5)
- 3. describing its primary scenario (successful end) as a sequence of numbered steps; (BA6)
- 4. describe alternative scenarios (including failed end) and others, as variations on the above sequence; (BA7)
- 5. optionally, make a top-level use case diagram. (BA8)
- 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: (BA3)
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)" (see UseCasesSimpleTextExample) (BA9)
- (BAA)
- On the 2nd iteration, may I suggest we will follow the framework set out in Alistair Cockburn's Sample Requirements Document Chapter 2. (BAB)
- (BAC)
- also refer to UseCasesDocumentTemplate (BAD)
- The UBL LCSC (Libarary Content Sub-committee) is addressing the same context related address formatting issue (BAE)
- TimMcGrath (UBL-lcsc Chair) has provide some examples of different addresses based on the context of country. It is based on the work of the OASIS CIQ group. (BAF)
- See: http://ontolog.cim3.net/file/reference/UBL-ebXML/UBL_Library_AddressContexts--w-CIQ-examples_TimM_20030513.xls (BAG)
Iteration-1: Quick Capture of the Draft Use Cases (BAH)
- Use Case Name: Context Driven Address Formatting (BAI)
- Goal: enable the system to present its user with the right addressing format, given a context (which, in this case, is the country of the addressee) (BAJ)
- Primary Actors: (BAK)
- Primary Scenario (successful end): (BAN)
- step 1. user is presented a screen with fields for: (BAO)
- (a) PartyName, (BAP)
- (b) AddressCountry (which can be the name of the country, properly spelled out, or in the form of a country code), and (BAQ)
- (c) an option for the user to specify whether the entery being made is in: (BAR)
- (i) English, or (BAS)
- (ii) Local Language of the AddressCountry. (BAT)
- step 2. user types in the information and submits it (to the system) (BAU)
- step 3. system queries the ontology based on the AddressCountry input and selects the correct addressing format for that country (BAV)
- step 4. system presents an address input screen, to the user, (BAW)
- (a) with PartyName and AddressCountry already filled out, (BAX)
- (b) in the language specified, and (BAY)
- (c) with the appropriate fields and format (relevant to the country and language choice/context) for user to enter the PartyAddress information (BAZ)
- step 1. user is presented a screen with fields for: (BAO)
- Alternative Scenario: "More than one official language used in AddressCountry" (BB0)
- step 5. The multiple option is presented to the user for manual selection. On user submission of the choice, process continues with step 3. (BB1)
- Alternative Scenario: "Country not found" (in ontology) (BB2)
- step 6. system presents an address input screen to the user, with (a) PartyName and AddresCountry already filled out, and (b) the default (generic UBL) fields for user to enter the PartyAddress information (BB3)
- Use Case Diagram (optional) (BB4)
Iteration-2: Documenting the Use Cases (BB5)
- Context Driven Address Formatting (BB6)
2a. The Primary Actors and their General Goals (BB7)
- List Actors, along with a breif description of the roles of each of them. (BB8)
2b. The Business Use Cases (BB9)
- Tabulate Outermost Goals, with the following columns: (BBA)
- Tabulate Task Level Goals, with the following columns: (BBF)
2c. The System Use Cases (BBK)
- Use Case 1: name primary use case (BBL)
- Use Case Diagram(s) (BC2)
- Use Case n: name use case (BCT)
- Use Case n: name use case (BD3)
3. The Terms Used / Glossary (BDD)
Recap of work sessions (BDG)
- Phone Conference 2003-05-22_09:00~10:00 (BDH)
- Attendees: SueProbert, TimMcGrath, JohnYunker & PeterYim (BDI)
- Tim started off by decribing the OASIS-CIQ TC's work, who works on the vocabulary of name and addresses (BDJ)
- Sue also brought up "Primary Role" and "Secondary Role" context within the business process (BDM)
- John points out that the use of ontology will shine in some of these cases because it does not pigeon-hole things as much as the other methodologies would force us to. (BDP)
- Tim cited another context: "jurisdiction" (legal addresses, registered address, ... etc.), or when tax schemes are involved. (BDQ)
- Peter asked the group to indicate whether we want to scope this use case with the focus on "formatting" or "context" (BDR)
- Tim: (a goal) I would want to see a richer vocabulary, instead of just better structure (BDS)
- John brought up that we could also assign "context" to the use cases ("administration" as opposed to "eCommerce", ... etc.) (BDT)
- Tim: use of the "qualifier" could help in some of this assignment (BDU)
- John proposed, the distinction, for example, between: (BDV)
- John: Ontologically layer "Activity", "Organization", "Person", "Role" onto "Address" could be an approach (BDZ)
- Sue: we should investigate whether the ubl implementation has actually constrained context driven extension (BE0)
- Going to Mapping between standards (BE1)
- Tim: we could assume that "presentation" would be taken care of (and is out of scope in our problem here.) (BE4)
- Peter reiterated that this present exercise is JUST to sync up through writing up the particular use case. We only define the problem here. We will definitely be working on designing the ontology and the solutions later, but not now. (BE5)
- Sue and Peter both agreed that the order of the day is to get the deliverable (the use case write-up) out and ino the hands of the rest of the ubl-ontology project group. (BE6)
- participants agreed to continue this discussion over email, and reconvene again in a week's time. (BE7)
- call adjourned 2003-05-22_10:10am PDT (BE9)