19 November 2007

Week 23 - Sparx Enterprise Architect & SysML

I purchased two software applications to create SysML diagrams (there are 9 diagram types in this UML profile to choose from; UML 2.0 has 13 profiles, which is a criticism of its complexity). The software was installed on the CSC Thinkpad T60issued to me earlier this year. I've finished all the CBTs on Skillsoft that are related to UML. It was a good refresher in a number of topics since my first introduction to OOAD in the Air Force's 5-course curriculum for their Software Professional Development Program (circa 1997).

I feel confident I can create meaningful structural and behavorial diagrams for the nHand mobile application I described in the proposal. I think of nHand as a service to those who want instant access to their human body, earthly possessions and manufactured goods including finanical securities. I expect there will be a few design iterations as I create something, forget about it for a couple of days then revisit my creations, wondering what I was thinking (I'll use the documentation features extensively).

I've created a short list of manufacturers (10) to contact with my short list of questions about their products' design artifacts. I have a similiar list for service providers (10). Thinking about this, I will find each of the ten industrial sector's association or federation to ask the question of X3D exports for consumers of there products and services. I'll try to answer the question, "what's in it for me?" in the letter because if I was to receive an unsolicit letter from a researcher, I would want to know what's in it for me to respond with my thoughts on the questions asked.

I'll take a few paragraphs to brainstorm Blue Ocean business models here because I need to solicit feedback from investors, manufacturers and service providers to move forward on a business strategy in the grant report. The context is at least two dimensional (i.e., time and object type). The letters in the nine cells are placeholders for software applications that serve that market. nHand software, assuming the ubiquity of X3D models for your pieces of earth, your bodily images (all modalities) and your products, will have features that assist reviewing (past), monitoring (now) and planning (future) in these areas.

earth body products

past A B C

now D E F

future G H I

The letters represent the set of companies with solutions in these broad category for the individual. For example, E can be a body and body fat mesurements from a Tanita scal3. We finished then


People first, the X3D format has to be branded as a life-lasting presentation standard for our changing world. This will take millions of advertising and marketing dollars [$] along with word-of-mouth multiplier effects to get the same level of awareness and expectations as say, HTML or PDF in cyberspace. Extant products and services in the marketplace without its X3D implmentation needs it and someone has to run the export feature if available or someone has to reverse engineer it and sell [$] it or give it away. This means more digital storage [$]. Products and services in development with CAD/CAE/CAM documents for all parts, components need to be X3D exportable via CAD...tool upgrades. Someone has to write and sell [$] an X3D export add-on. Finally, for unstarted product developments, X3D formatting has to be a project requirement [$] that is not waived or deviated at any decision point. This means executives need to understand the value of producing X3D versions for all there offerings--they have to a trend of profits in the price chosen to deliver the X3D implementation with real thing and not negatively affect sales. While specifying this is like specifying all extant printed text be implemented in PDF via scanners or retyped by OCR/typists for the powerful features of searching the text etc., I know this will never happen in its entirety because of differences in value of the texts to potential owners and readers. It's only the majority that matters in this enterprise. What you read wasn't a business model but a bunch of tasks and thoughts about making X3D as ubiquitous as packaging that encapsulates the product inside it. I just about having an fleet of mobile 3D scanners making a business of working off the backlog of unavailable X3D models in residents' homes and small businesses by scanning their objects multispectrally for the kind of application I'm attempting to specify and partially design.

Second business model, More X3D software [$], more X3D data transfered [$], more storage required for X3D worlds [$], more processing power for database-driven X3D worlds [$], more energy consumption for X3D interactity, more information integration and summation, more behavior modification, more

Technically, X3D has nodes (~209 now, not including the volumetric proposal for medical apps) for modeling the elements of earth, humand bodies and manufactured items but not everything (100s of thousands) in each of these broad categories, especially the myriad of dynamics between them. For example, humans bleeding, soil saturation from rain, and rusting car metal do not have computationally efficient nodes for a digital content creator.

Nonetheless, Valuation of VR models of real consumer products has happened but not on a large-scale. Just imagine the Global Trade Item Numbers (GTIN) (ie., Universal Product Codes, European Article Numbers and Japanese Article Number) including an X3D model for everything that gets a code assignment and it being free!

The basic market transformation that has to occur is the wholesale availability of real objects' X3D models in virtual worlds for people to claim as their own and configure their life's possessions in VR for a better management of their future.

I came across the term life-logging today while surfing www.virtualworldsmanagement.com and wondered what that meant. In the VR/VW context it probably means having your avatar's every event logged for review at some point--motion, speech, text, intercourse, location, etc. For an enterprise the analagous term might be business logging.

No comments: