• I will define it in the WIKIWord give me a little time ;-) - TimMiner 01 may 2002 Done, please see DualAndTrippleRedundancy?.-- TimMiner - 04 May 2002

• I will define it in the WIKIWord give me a little time ;-) - TimMiner 01 may 2002
• Done, please see DualAndTripleRedundancy.-- TimMiner - 04 May 2002

• Is that not already covered by massstorage? -- JonKnight - 01 May 2002 No its not BUT I did change MassStorage? to HighSpeedMassStorage? to beter differentiate the notions. --Main TimMiner? 01 May 2002

• Is that not already covered by massstorage? -- JonKnight - 01 May 2002 * No its not BUT I did change MassStorage? to HighSpeedMassStorage? to better differentiate the notions. --Main TimMiner? 01 May 2002

JK1 The system shall not dissipate its heat output into to the wearer's body tissue to the extent that it causes discomfort. -- JonKnight - 01 May 2002

JK1 The system shall not dissipate its heat output into to the wearer's body tissue to the extent that it causes discomfort. -- JonKnight - 01 May 2002

a. functional elements b. interconnected by PowerDistribution? and IntegratingNetwork? elements c. embedded within a vest-like undergarment d. with a HeadMountedColorDisplay? integrated with an IntegratedMicEarphone? function e. and having a OneHandKeyboardMouse? attached to the user's beltline.

Last TM-tag is 44 Last JK-tag is 4 Last RJ-tag is ??

• a. functional elements
• b. interconnected by PowerDistribution? and IntegratingNetwork? elements
• c. embedded within a vest-like undergarment
• d. with a HeadMountedColorDisplay? integrated with an IntegratedMicEarphone? function
• e. and having a OneHandKeyboardMouse? attached to the user's beltline.

• Last TM-tag is 44
• Last JK-tag is 4
• Last RJ-tag is ??

Please refer to a special requirements document StyleRecommendations page so your inputs fit the intended use of this document by developers.-- TimMiner - 04 May 2002

We will debate the merits of the listed requirements downstream in time. At this point we are gathering ALL ideas so do not delete someone elses even if ther is a conflict between them (as requirements). Say what it must do or be or have but do not say how it is to be implemented. --Main.TimMiner 01 May 2002.

We will debate the merits of the listed requirements downstream in time. At this point we are gathering ALL ideas so do not delete someone elses even if there is a conflict between them (as requirements). Say what it must do or be or have but do not say how it is to be implemented. --Main.TimMiner 01 May 2002.

• I will define it in the WIKIWord give me a little time ;-) - TimMiner 01 may 2002

• I will define it in the WIKIWord give me a little time ;-) - TimMiner 01 may 2002 Done, please see DualAndTrippleRedundancy?.-- TimMiner - 04 May 2002

* Please see the SystemPassport link and (hopefully) move your debate there. -- TimMiner - 04 May 2002

• It looks lilke you guys are seeing that you can do some requirements writing... great! Keep it up. Here is another "structured" thing: There is really no such thing as an optional requirement. If you think about it, putting an option into a design after it has reached the market involves a redesign and is usually called a product improvement. If it is writen into the spec as an option or optional item, any contractor in the world will completely ignore it in an effort to complete the contract on schedule. TM18 and TM39 are examples of requirements that create what the world calls options or optional items in the products they buy. We also need to not use the words "may" or "will" when we are writing a requirement for related semantic reasons. --Main TimMiner? 01 May 2002

• It looks lilke you guys are seeing that you can do some requirements writing... great! Keep it up.

Form polishing - Rick Jones 01 May 2002

• Rick, where does the "Main" come from? I tagged and numbered initial entries so others could refer to them and you removed them in your polishing. I restored some numbering in a form that I hope works for the WIKI. If not, please tell me how it should be done. It would be good if everyone could do (and did) this. Then we'll remove these comments. --Main TimMiner? 01 May 2002
• Sorry Tim, I thought they bulked up the discussion more than it needed. They should be in the original versions of this page.. open 2 webpages.. one to edit, the other to go to the past versions of the webpage(you'll see on the far right where you select to edit - it will say (ie v1.8, v1.7, v1.6, More) .. It's the "More" you want .. and select the first version. Also just a minor thing.. the last editing you did forgot the "." between "Main" and "TimMiner". Consequently the link wasn't made -- RickJones 02 May 2002

OK everybody, listen up. If we want people to participate with us, we have to let them speak without being flamed. This is a brainstorming session leading to collaboration and eventually consensus. Expressing agreement or disagreement is fine but sign it or state it as an issue or concern, please. What is most helpful is your alternative suggestion so put that in, please.

These pages are a NoFlamingZone.-- TimMiner - 04 May 2002

Also, I propose we keep some of the mutual education we just gave each other today as an example to future participants. I'll capture it and edit it into a short set of examples. OK with you Rick and Jon?

Expressing agreement or disagreement is fine but sign it or state it as an issue or concern, please. What is most helpful is your alternative suggestion so put that in, please.-- TimMiner - 04 May 2002

TM40 The system should be capable of running on 230 and 110V. -- MarcusWolschon 03 May 2002

MW1 The system should be capable of running on 230 and 110V. -- MarcusWolschon 03 May 2002 (Sorry I accidentally tagged this one as mine. fixed it -- TimMiner - 04 May 2002)

• Surely that's not something you can specify in the design? It depends on how successful the product is. -- JonKnight - 01 May 2002
• This definately cannot be specified.. this is something that has to develop from an established market base. -- RickJones - 01 May 2002
• Gentlemen, lets debate this in the UsedWearableMarket WIKIWord once it is defined. This is just not the place. I will move this debate as soon as I do that definition. --Main TimMiner? 01 May 2002

Moved debate -- TimMiner - 04 May 2002

TM2 This sysetm shall have an OpenSoftwareArchitecture.

TM2 This system shall have an OpenSoftwareArchitecture.

• But do not limit the choice of hardware to that what can execute Windows(as a well known company did) -- MarcusWolschon 03 May 2002

• Thus the boot-loader must be standardized(e.g. bootsector on IDE) or documented(e.g. inferno) - some potential to save engeneering work here(use a free boot-loader) -- MarcusWolschon 03 May 2002

TM5 This system shall have an ExtensibleHwSwArchatecture? that enables development of ExpansionCapabilities?.

TM5 This system shall have an ExtensibleHardwareAndSoftwareArchitecture? that enables development of ExpansionCapabilities?.

• Many people can live with 4-5h per battery-set however. -- MarcusWolschon 03 May 2002

TM10 This system shall have ZeroBodyEmPenitration? design to keep EM fields outside the volume of the user's body.

TM10 This system shall have ZeroBodyEmPenetration? design to keep EM fields outside the volume of the user's body.

TM12 This system shall have HardwareIntegrationArchatecture? that promotes the miniturization and combining of system modules.

TM12 This system shall have HardwareIntegrationArchitecture? that promotes the miniturization and combining of system modules.

TM40 The system should be capable of running on 230 and 110V. -- MarcusWolschon 03 May 2002

* I propose under High Level Requirements that this be separated into 2 subgroups : Hardware and Software(OS) -- RickJones 2 May 2002

* I propose under High Level Requirements that this be separated into 2 subgroups : Hardware and Software(OS).. also subdividing Hardware into Power Management, Interfaces and Other.-- RickJones 2 May 2002

• The above may be reduced to the capability of interchanging backup batteries as necessary or a battery runtime of 20-24 hours. In any case, the use of a power adapter should always be possible to minimize battery usage. -- RickJones 01 May 2002
• Then form your own requirements statement so we can debate them downstream. Here they can be side by side. - TimMiner 01 may 2002

RJ1 A run time with a battery pack will have a minimum run time of 8 hours for the system alone with a future target goal of a 20 hour run time minimum.

• This is to eventually have the system (including display) operate for 20 hours with 1-2 battery swaps (without excessive other equipment) - RickJones - 01 May 2002

Overview: The intent here is to identify traits of a "MinimumSystem" Wearable Computer System (WearComp?) suitable for a mass production, commercial and consumer applications, that will be consumer priced. List them individually as requirements. Main TimMiner? 01 May 2002.

Overview: The intent here is to identify traits of a "MinimumSystem" Wearable Computer System (WearComp?) suitable for a mass production, commercial and consumer applications, that will be consumer priced. List them individually as requirements. TimMiner 01 May 2002.

We will debate the merits of the listed requirements downstream in time. At this point we are gathering ALL ideas so do not delete someone elses even if ther is a conflict between them (as requirements). Say what it must do or be or have but do not say how it is to be implemented. --Main TimMiner? 01 May 2002.

We will debate the merits of the listed requirements downstream in time. At this point we are gathering ALL ideas so do not delete someone elses even if ther is a conflict between them (as requirements). Say what it must do or be or have but do not say how it is to be implemented. --Main.TimMiner 01 May 2002.

Here we need to concern ourselves with coming up with high level requirements (various design philosophy ideas), functional requirements, constraining requirements, performance requirements and system architecture alternatives (stated as requirements) --Main TimMiner? 01 May 2002.

Here we need to concern ourselves with coming up with high level requirements (various design philosophy ideas), functional requirements, constraining requirements, performance requirements and system architecture alternatives (stated as requirements) --Main.TimMiner 01 May 2002.

* I propose under High Level Requirements that this be separated into 2 subgroups : Hardware and Software(OS) -- RickJones 2 May 2002

The above 2 should be stated together - they are fundamentally the same issue. -- RickJones 01 May 2002 Perhaps, but we can not make that call at this early stage. - Main TimMiner? 01 may 2002

• The above 2 should be stated together - they are fundamentally the same issue. -- RickJones 01 May 2002
• Perhaps, but we can not make that call at this early stage. - TimMiner 01 may 2002

The above may be reduced to the capability of interchanging backup batteries as necessary or a battery runtime of 20-24 hours. In any case, the use of a power adapter should always be possible to minimize battery usage. -- RickJones 01 May 2002 Then form your own requirements statement so we can debate them downstream. Here they can be side by side. - Main TimMiner? 01 may 2002

• The above may be reduced to the capability of interchanging backup batteries as necessary or a battery runtime of 20-24 hours. In any case, the use of a power adapter should always be possible to minimize battery usage. -- RickJones 01 May 2002
• Then form your own requirements statement so we can debate them downstream. Here they can be side by side. - TimMiner 01 may 2002

Please define what you mean by this. -- RickJones 01 May 2002 I will define it in the WIKIWord give me a little time ;-) - Main TimMiner? 01 may 2002

• Please define what you mean by this. -- RickJones 01 May 2002
• I will define it in the WIKIWord give me a little time ;-) - TimMiner 01 may 2002

The system shall allow end users to disable ComponentRegistration? if they desire. -- JonKnight - 01 May 2002 I agree that this should be an optional feature. The lost and found/stolen issue is the only aspect of this I'd want, but I could do that by writing my own file. Not to mention I don't want to have to pay fees to transfer registration if I was ever to sell a system. -- RickJones - 01 May 2002

• The system shall allow end users to disable ComponentRegistration? if they desire. -- JonKnight - 01 May 2002
• I agree that this should be an optional feature. The lost and found/stolen issue is the only aspect of this I'd want, but I could do that by writing my own file. Not to mention I don't want to have to pay fees to transfer registration if I was ever to sell a system. -- RickJones - 01 May 2002

Most could implement this through a USB/Serial/Parallel or PCI/PC104/PC104+ device. -- RickJones 01 May 2002

• Most could implement this through a USB/Serial/Parallel or PCI/PC104/PC104+ device. -- RickJones 01 May 2002

This definately cannot be specified.. this is something that has to develop from an established market base. -- RickJones - 01 May 2002 Gentlemen, lets debate this in the UsedWearableMarket WIKIWord once it is defined. This is just not the place. I will move this debate as soon as I do that definition. --Main TimMiner? 01 May 2002

• This definately cannot be specified.. this is something that has to develop from an established market base. -- RickJones - 01 May 2002
• Gentlemen, lets debate this in the UsedWearableMarket WIKIWord once it is defined. This is just not the place. I will move this debate as soon as I do that definition. --Main TimMiner? 01 May 2002

* I think NOT! * I'd rather not have my wearable spying on me thanks. Turn that "shall" into an optional "may" or include "The system shall allow the SystemPassport capability to be turned off and/or removed" -- JonKnight - 01 May 2002

• I think NOT! * I'd rather not have my wearable spying on me thanks. Turn that "shall" into an optional "may" or include "The system shall allow the SystemPassport capability to be turned off and/or removed" -- JonKnight - 01 May 2002

Again yes.. this should be optional and removable(ie. compact flash card). -- RickJones - 01 May 2002 It looks lilke you guys are seeing that you can do some requirements writing... great! Keep it up. Here is another "structured" thing: There is really no such thing as an optional requirement. If you think about it, putting an option into a design after it has reached the market involves a redesign and is usually called a product improvement. If it is writen into the spec as an option or optional item, any contractor in the world will completely ignore it in an effort to complete the contract on schedule. TM18 and TM39 are examples of requirements that create what the world calls options or optional items in the products they buy. We also need to not use the words "may" or "will" when we are writing a requirement for related semantic reasons. --Main TimMiner? 01 May 2002

• Again yes.. this should be optional and removable(ie. compact flash card). -- RickJones - 01 May 2002
• It looks lilke you guys are seeing that you can do some requirements writing... great! Keep it up. Here is another "structured" thing: There is really no such thing as an optional requirement. If you think about it, putting an option into a design after it has reached the market involves a redesign and is usually called a product improvement. If it is writen into the spec as an option or optional item, any contractor in the world will completely ignore it in an effort to complete the contract on schedule. TM18 and TM39 are examples of requirements that create what the world calls options or optional items in the products they buy. We also need to not use the words "may" or "will" when we are writing a requirement for related semantic reasons. --Main TimMiner? 01 May 2002

I agree. TM

• I agree. TM

I don't completely disagree. --Main TimMiner? 01 May 2002

• I don't completely disagree. --Main TimMiner? 01 May 2002

JKxx The system shall not dissipate its heat output into to the wearer's

JK1 The system shall not dissipate its heat output into to the wearer's

JKxx The system shall provide the option to monitor the biomedical state of the wearer. -- JonKnight - 01 May 2002

JK2 The system shall provide the option to monitor the biomedical state of the wearer. -- JonKnight - 01 May 2002

JKxx The system shall provide the option to monitor and if possible control the user's temperature (personal air con). -- JonKnight - 01 May 2002

JK3 The system shall provide the option to monitor and if possible control the user's temperature (personal air con). -- JonKnight - 01 May 2002

JKxx The system may be packaged such that it can be implanted subdermally. -- JonKnight - 01 May 2002

JK4 The system may be packaged such that it can be implanted subdermally. -- JonKnight - 01 May 2002

Last JK-tag is xx

Last JK-tag is 4

• Sorry Tim, I thought they bulked up the discussion more than it needed. They should be in the original versions of this page.. open 2 webpages.. one to edit, the other to go to the past versions of the webpage(you'll see on the far right where you select to edit - it will say (ie v1.8, v1.7, v1.6, More) .. It's the "More" you want .. and select the first version. Also just a minor thing.. the last editing you did forgot the "." between "Main" and "TimMiner". Consequently the link wasn't made -- RickJones 02 May 2002

OK everybody, listen up. If we want people to participate with us, we have to let them speak without being flamed. This is a brainstorming session leading to collaboration and eventually consensus. Expressing agreement or disagreement is fine but sign it or state it as an issue or concern, please. What is most helpful is your alternative suggestion so put that in, please.

Also, I propose we keep some of the mutual education we just gave each other today as an example to future participants. I'll capture it and edit it into a short set of examples. OK with you Rick and Jon?

We will debate the merits of the listed requirements downstream in time. At this point we are gathering ALL ideas so do not delete someone elses even if ther is a conflict between them (as requirements). Say what it must do or be or have but do not say how it is to be implemented. Main TimMiner? 01 May 2002.

We will debate the merits of the listed requirements downstream in time. At this point we are gathering ALL ideas so do not delete someone elses even if ther is a conflict between them (as requirements). Say what it must do or be or have but do not say how it is to be implemented. --Main TimMiner? 01 May 2002.

Here we need to concern ourselves with coming up with high level requirements (various design philosophy ideas), functional requirements, constraining requirements, performance requirements and system architecture alternatives (stated as requirements) Main TimMiner? 01 May 2002.

Here we need to concern ourselves with coming up with high level requirements (various design philosophy ideas), functional requirements, constraining requirements, performance requirements and system architecture alternatives (stated as requirements) --Main TimMiner? 01 May 2002.

High level requirements: Say what the system must be or do or have but do not say how they are implemented.

High Level Requirements (System Philosophy):

1 This system shall have an OpenHardwareArchitecture.

TM1 This system shall have an OpenHardwareArchitecture.

2 This sysetm shall have an OpenSoftwareArchitecture.

TM2 This sysetm shall have an OpenSoftwareArchitecture.

3 This system shall be able to BootAlternative OS environments from storage media.

TM3 This system shall be able to BootAlternative OS environments from storage media.

4 This system shall preclude OS suppliers from defeating the ability to BootAlternative OS environments.

TM4 This system shall preclude OS suppliers from defeating the ability to BootAlternative OS environments.

Perhaps but we can not make that call at this early stage. - Main TimMiner? 01 may 2002

Perhaps, but we can not make that call at this early stage. - Main TimMiner? 01 may 2002

5 This system shall have an ExtensibleHwSwArchatecture? that enables development of ExpansionCapabilities?.

TM5 This system shall have an ExtensibleHwSwArchatecture? that enables development of ExpansionCapabilities?.

6 This system shall have the capability to HotSwapBatteries? while in an operational state and being powered by one or more other hot swappable batteries.

TM6 This system shall have the capability to HotSwapBatteries? while in an operational state and being powered by one or more other hot swappable batteries.

7 This system shall have a DualAndTripleRedundancy capability for users who wish to implement them for their own operational reasons.

TM7 This system shall have a DualAndTripleRedundancy capability for users who wish to implement them for their own operational reasons.

8 This system shall have a ComponentRegistration? capability to first embed serial numbers and track registrations and locate registered items.

TM8 This system shall have a ComponentRegistration? capability to first embed serial numbers and track registrations and locate registered items.

9 This system shall have a LowEmissions? design to power distribution, Module and chip EM emissions below TBD levels.

TM9 This system shall have a LowEmissions? design to power distribution, Module and chip EM emissions below TBD levels.

10 This system shall have ZeroBodyEmPenitration? design to keep EM fields outside the volume of the user's body.

TM10 This system shall have ZeroBodyEmPenitration? design to keep EM fields outside the volume of the user's body.

11 This system shall have StandardModuleAttach? scheme so developers can focus on the function being developed instead of designing from the bottom up in evry case.

TM11 This system shall have StandardModuleAttach? scheme so developers can focus on the function being developed instead of designing from the bottom up in evry case.

12 This system shall have HardwareIntegrationArchatecture? that promotes the miniturization and combining of system modules.

TM12 This system shall have HardwareIntegrationArchatecture? that promotes the miniturization and combining of system modules.

13 This system shall have SitAndCharge? capability in the event the user is deskbound (airplane bound?) that recharges batteries while the system is in use when AC power is available.

TM13 This system shall have SitAndCharge? capability in the event the user is deskbound (airplane bound?) that recharges batteries while the system is in use when AC power is available.

14 This system shall have a SitAndBeWired? capability that connects the user's wearable to high bandwidth copper or fiber for communications and networking in the event the user is deskbound with access to network and telecom ports.

TM14 This system shall have a SitAndBeWired? capability that connects the user's wearable to high bandwidth copper or fiber for communications and networking in the event the user is deskbound with access to network and telecom ports.

15 This system shall have local IrAndRf? network and communications for in-room and in-vehicle use.

TM15 This system shall have local IrAndRf? network and communications for in-room and in-vehicle use.

16 This system shall have PowerSaveFeatures? that minimize the drain on batteries when modules are in idle states.

TM16 This system shall have PowerSaveFeatures? that minimize the drain on batteries when modules are in idle states.

17 This system shall have a UsedWearableMarket and follow-on market support for 10 years after manufacture.

TM17 This system shall have a UsedWearableMarket and follow-on market support for 10 years after manufacture.

Gentlemen, lets debate this in the UsedWearableMarket WIKIWord once it is defined. This is just not the place. I will move this debate as soon as I do that definition. --Main TimMiner? 01 May 2002

18 This system shall have a SystemPassport capability that customs and law enforcement can use to track both the users and the status of the wearable computer.

TM18 This system shall have a SystemPassport capability that customs and law enforcement can use to track both the users and the status of the wearable computer.

19 This system shall have SecurityServices? such that users can grant access or monitoring privaledges to corporate or government security agents.

TM39 This SystemPassport capability shall be enabled or disabled by the user. Note: This is my 39th requirements entry. I am placing it here and not reordering the list. Jon or Rick could have done this instead of doing the debate thing. I did the entry as an example.

TM19 This system shall have SecurityServices? such that users can grant access or monitoring privaledges to corporate or government security agents.

1 The Basic or Minimum System shall have a ProcessorRamRom? function.

TM20 The Basic or Minimum System shall have a ProcessorRamRom? function.

2 The Basic or Minimum System shall have a RealTimeClock? function.

TM21 The Basic or Minimum System shall have a RealTimeClock? function.

3 The Basic or Minimum System shall have a GlobalPositioning? function.

TM22 The Basic or Minimum System shall have a GlobalPositioning? function.

It looks lilke you guys are seeing that you can do some requirements writing... great! Keep it up. Here is another "structured" thing: There is really no such thing as an optional requirement. If you think about it, putting an option into a design after it has reached the market involves a redesign and is usually called a product improvement. If it is writen into the spec as an option or optional item, any contractor in the world will completely ignore it in an effort to complete the contract on schedule. TM18 and TM39 are examples of requirements that create what the world calls options or optional items in the products they buy. We also need to not use the words "may" or "will" when we are writing a requirement for related semantic reasons. --Main TimMiner? 01 May 2002

4 The Basic or Minimum System shall have an IntegratedTelecom? function.

TM23 The Basic or Minimum System shall have an IntegratedTelecom? function.

I agree. TM

5 The Basic or Minimum System shall have a VehicularNetwork? function.

TM24 The Basic or Minimum System shall have a VehicularNetwork? function.

6 The Basic or Minimum System shall have a MassStorage? function.

TM25 The Basic or Minimum System shall have a HighSpeedMassStorage? function.

7 The Basic or Minimum System shall have a RemovableMedia? function.

TM26 The Basic or Minimum System shall have a RemovableMedia? function.

8 The Basic or Minimum System shall have a OneHandKeyboardMouse? function.

TM27 The Basic or Minimum System shall have a OneHandKeyboardMouse? function.

9 The Basic or Minimum System shall have a ColorDisplay? function.

*So, put 'em in as requirements. --Main TimMiner? 01 May 2002

TM28 The Basic or Minimum System shall have a HeadMountedColorDisplay? function.

* I like the thinking. Please do the honors. --Main TimMiner? 01 May 2002

10 The Basic or Minimum System shall have a IntegratedMicEarphone? function.

TM29 The Basic or Minimum System shall have a IntegratedMicEarphone? function.

11 The Basic or Minimum System shall have a ReadWriteOpticalMedia? function.

TM30 The Basic or Minimum System shall have a ReadWriteOpticalMedia? function.

* Is that not already covered by massstorage? -- JonKnight - 01 May 2002

* Is that not already covered by massstorage? -- JonKnight - 01 May 2002 No its not BUT I did change MassStorage? to HighSpeedMassStorage? to beter differentiate the notions. --Main TimMiner? 01 May 2002

12 The Basic or Minimum System shall have a PowerDistribution? function.

TM31 The Basic or Minimum System shall have a PowerDistribution? function.

13 The Basic or Minimum System shall have a IntegratingNetwork? function.

TM32 The Basic or Minimum System shall have a IntegratingNetwork? function.

TM42 All IntegratingNetwork? paths within the system shall have a set of 4 DetermanisticDataChannels?.

Constraining Requirements:

Constraining Requirements (quantified environment items):

1 The system shall operate normally between 0 and 60 degrees Celsius.

TM33 The system shall operate normally between 0 and 60 degrees Celsius.

* see where the STP format came from? --Main TimMiner? 01 May 2002

2 The system shall operate normally at 100 percent relative humidity.

TM34 The system shall operate normally at 100 percent relative humidity.

3 The system shall resist moisture and operate normally while the user & wearable endures a rain shower for 60 minutes.

TM35 The system shall resist moisture and operate normally while the user & wearable endures a rain shower for 60 minutes.

4 The system shall resist water penetration when emersed in 10 meters of sea water.

TM36 The system shall resist water penetration when emersed in 10 meters of sea water.

I don't completely disagree. --Main TimMiner? 01 May 2002

5 The system shall operate normally and resist twenty of each of the listed "events" where the duration is 5 minutes at each extreme then continue to operate normally for a period of 1 year.

TM37 The system shall operate normally and resist twenty of each of the listed "events" where the duration is 5 minutes at each extreme then continue to operate normally for a period of 1 year.

6 The system shall resist the moisture and salts produced by the body of the user over 65,000 hours of use.

TM38 The system shall resist the moisture and salts produced by the body of the user over 65,000 hours of use.

7 The system shall not dissipate its heat output into to the wearer's

JKxx The system shall not dissipate its heat output into to the wearer's

8 The system shall provide the option to monitor the biomedical state of the wearer. -- JonKnight - 01 May 2002

JKxx The system shall provide the option to monitor the biomedical state of the wearer. -- JonKnight - 01 May 2002

JKxx The system shall provide the option to monitor and if possible control the user's temperature (personal air con). -- JonKnight - 01 May 2002

9 The system shall provide the option to monitor and if possible control the user's temperature (personal air con). -- JonKnight - 01 May 2002

JKxx The system may be packaged such that it can be implanted subdermally. -- JonKnight - 01 May 2002 * I suggest we put this under HIgh Level Requirements. --Main TimMiner? 01 May 2002

10 The system may be packaged such that it can be implanted subdermally. -- JonKnight - 01 May 2002

Performance Requirements (quantified system measures):

Session 2 today TimMiner? - this isn't needed that's what the looking back through revisions is for wiki does this automatically

TM40 All IntegratingNetwork? paths within the system shall have a raw bandwidth of 400Mb/s, minimum.

TM41 All IntegratingNetwork? paths within the system shall have a protocal or format that transferes data, address and control information at an equivalent bandwidth of 350Mb/s, minimum.

TM43 All DetermanisticDataChannels? shall have a MaxLatency? of 100ms EndToEnd?.

System Architecture Alternatives (stated as requirements)

TM44 The MinimumSystem shall consist of the following: a. functional elements b. interconnected by PowerDistribution? and IntegratingNetwork? elements c. embedded within a vest-like undergarment d. with a HeadMountedColorDisplay? integrated with an IntegratedMicEarphone? function e. and having a OneHandKeyboardMouse? attached to the user's beltline.

Last TM-tag is 44 Last JK-tag is xx Last RJ-tag is ??

* Rick, where does the "Main" come from? I tagged and numbered initial entries so others could refer to them and you removed them in your polishing. Would you restore the numbering in some form that works for th WIKI or tell me how it should be done. It would be good if everyone could do ( and did) this. Then we'll remove these comments. TimMiner? 01 May 2002

* Rick, where does the "Main" come from? I tagged and numbered initial entries so others could refer to them and you removed them in your polishing. I restored some numbering in a form that I hope works for the WIKI. If not, please tell me how it should be done. It would be good if everyone could do (and did) this. Then we'll remove these comments. --Main TimMiner? 01 May 2002

NOTE: Initial entries by Tim Miner, except where otherwise noted. Please, notate which additions are yours.

Overview: The intent here is to identify traits of a "MinimumSystem" Wearable Computer System (WearComp?) suitable for a mass production, commercial and consumer applications, that will be consumer priced. List them individually as requirements. Main TimMiner? 01 May 2002.

We will debate the merits of the listed requirements downstream in time. At this point we are gathering ALL ideas so do not delete someone elses even if ther is a conflict between them (as requirements). Say what it must do or be or have but do not say how it is to be implemented. Main TimMiner? 01 May 2002.

Here we need to concern ourselves with coming up with high level requirements (various design philosophy ideas), functional requirements, constraining requirements, performance requirements and system architecture alternatives (stated as requirements) Main TimMiner? 01 May 2002.

Perhaps but we can not make that call at this early stage. - Main TimMiner? 01 may 2002

Then form your own requirements statement so we can debate them downstream. Here they can be side by side. - Main TimMiner? 01 may 2002

I will define it in the WIKIWord give me a little time ;-) - Main TimMiner? 01 may 2002

* Rick, where does the "Main" come from? I tagged and numbered initial entries so others could refer to them and you removed them in your polishing. Would you restore the numbering in some form that works for th WIKI or tell me how it should be done. It would be good if everyone could do ( and did) this. Then we'll remove these comments. TimMiner? 01 May 2002

* All connectors should be standard(PC104/104+, compact flash, PCMCIA, etc). Depending on what you mean by "Open Hardware" this may not be suitable for many manufacturers. -- RickJones - 01 May 2002

*Software is OS and unless compiled for each processor type - processor dependent. If someone wants to run windows, let them run windows and buy windows software.. or compile their own. -- RickJones 01 May 2002

I agree that this should be an optional feature. The lost and found/stolen issue is the only aspect of this.

I agree that this should be an optional feature. The lost and found/stolen issue is the only aspect of this I'd want, but I could do that by writing my own file. Not to mention I don't want to have to pay fees to transfer registration if I was ever to sell a system. -- RickJones - 01 May 2002

Most could implement this through a USB/Serial/Parallel or PCI device. -- RickJones 01 May 2002

Most could implement this through a USB/Serial/Parallel or PCI/PC104/PC104+ device. -- RickJones 01 May 2002

* One could also use a wireless network card to connect. -- RickJones 01 May 2002

* I think NOT! I'd rather not have my wearable spying on me thanks.

* I think NOT! * I'd rather not have my wearable spying on me thanks.

* I agree with Jon, sorry this would IMMEDIATELY turn me off. In my opinion, optional GPS is bad enough. -- RickJones - 01 May 2002

* I agree with Jon, sorry this would IMMEDIATELY turn me off. In my opinion, optional GPS is bad enough when it comes to potentially being "tracked". -- RickJones - 01 May 2002

* Some even what a full keyboard - Carol has stated this MANY times. The important thing is that one-handed, mobile keyboards be capable of the standard keyboard/mouse inputs (PS/2 or USB) -- RickJones 01 May 2002

* We need to maintain 640x480 for backward compatibility - RickJones - 01 May 2002

* We need to maintain 640x480 for backward compatibility (MicroOptical?,M1), but I agree 800x600 should be the expected minimum standard. - RickJones - 01 May 2002

* Capable of full duplex audio with Microphone and speaker jacks

* This should be a specially designed system specifically for scuba use (and work at greater depths). This is a REALLY difficult spec and will drastically raise the price of the system for all the features we're asking for. Besides does anyone know if there's a submergeable GPS on the market or for that matter a wireless network card that works underwater? -- RickJones - 01 May 2002

1 This system shall have an OpenHardwareArchatecture?.

1 This system shall have an OpenHardwareArchitecture.

2 This sysetm shall have an OpenSoftwareArchatecture?.

2 This sysetm shall have an OpenSoftwareArchitecture.

NOTE: Initial entries by Tim Miner, except where otherwise noted. Please, notate which additions are yours.

2003BDS-TimMiner1 This system shall have an OpenHardwareArchatecture?.

1 This system shall have an OpenHardwareArchatecture?.

2 This sysetm shall have an OpenSoftwareArchatecture?.

3 This system shall be able to BootAlternative OS environments from storage media. 4 This system shall preclude OS suppliers from defeating the ability to BootAlternative OS environments.

2003BDS-TimMiner2 This sysetm shall have an OpenSoftwareArchatecture?.

The above 2 should be stated together - they are fundamentally the same issue. -- RickJones 01 May 2002

2003BDS-TimMiner3 This system shall be able to BootAlternative OS environments from storage media.

5 This system shall have an ExtensibleHwSwArchatecture? that enables development of ExpansionCapabilities?.

2003BDS-TimMiner4 This system shall preclude OS suppliers from defeating the ability to BootAlternative OS environments.

6 This system shall have the capability to HotSwapBatteries? while in an operational state and being powered by one or more other hot swappable batteries.

2003BDS-TimMiner5 This system shall have an ExtensibleHwSwArchatecture? that enables development of ExpansionCapabilities?.

The above may be reduced to the capability of interchanging backup batteries as necessary or a battery runtime of 20-24 hours. In any case, the use of a power adapter should always be possible to minimize battery usage. -- RickJones 01 May 2002

2003BDS-TimMiner6 This system shall have the capability to HotSwapBatteries? while in an operational state and being powered by one or more other hot swappable batteries.

7 This system shall have a DualAndTripleRedundancy capability for users who wish to implement them for their own operational reasons.

2003BDS-TimMiner7 This system shall have a DualAndTripleRedundancy capability for users who wish to implement them for their own operational reasons.

Please define what you mean by this. -- RickJones 01 May 2002

2003BDS-TimMiner8 This system shall have a ComponentRegistration? capability to first embed serial numbers and track registrations and locate registered items.

8 This system shall have a ComponentRegistration? capability to first embed serial numbers and track registrations and locate registered items.

I agree that this should be an optional feature. The lost and found/stolen issue is the only aspect of this.

2003BDS-TimMiner9 This system shall have a LowEmissions? design to power distribution, Module and chip EM emissions below TBD levels.

9 This system shall have a LowEmissions? design to power distribution, Module and chip EM emissions below TBD levels.

2003BDS-TimMiner10 This system shall have ZeroBodyEmPenitration? design to keep EM fields outside the volume of the user's body.

10 This system shall have ZeroBodyEmPenitration? design to keep EM fields outside the volume of the user's body.

2003BDS-TimMiner11 This system shall have StandardModuleAttach? scheme so developers can focus on the function being developed instead of designing from the bottom up in evry case.

11 This system shall have StandardModuleAttach? scheme so developers can focus on the function being developed instead of designing from the bottom up in evry case.

2003BDS-TimMiner12 This system shall have HardwareIntegrationArchatecture? that promotes the miniturization and combining of system modules.

Most could implement this through a USB/Serial/Parallel or PCI device. -- RickJones 01 May 2002

2003BDS-TimMiner13 This system shall have SitAndCharge? capability in the event the user is deskbound (airplane bound?) that recharges batteries while the system is in use when AC power is available.

12 This system shall have HardwareIntegrationArchatecture? that promotes the miniturization and combining of system modules.

2003BDS-TimMiner14 This system shall have a SitAndBeWired? capability that connects the user's wearable to high bandwidth copper or fiber for communications and networking in the event the user is deskbound with access to network and telecom ports.

13 This system shall have SitAndCharge? capability in the event the user is deskbound (airplane bound?) that recharges batteries while the system is in use when AC power is available.

2003BDS-TimMiner15 This system shall have local IrAndRf? network and communications for in-room and in-vehicle use.

14 This system shall have a SitAndBeWired? capability that connects the user's wearable to high bandwidth copper or fiber for communications and networking in the event the user is deskbound with access to network and telecom ports.

2003BDS-TimMiner16 This system shall have PowerSaveFeatures? that minimize the drain on batteries when modules are in idle states.

15 This system shall have local IrAndRf? network and communications for in-room and in-vehicle use.

2003BDS-TimMiner17 This system shall have a UsedWearableMarket and follow-on market support for 10 years after manufacture.

16 This system shall have PowerSaveFeatures? that minimize the drain on batteries when modules are in idle states.

17 This system shall have a UsedWearableMarket and follow-on market support for 10 years after manufacture.

This definately cannot be specified.. this is something that has to develop from an established market base. -- RickJones - 01 May 2002

2003BDS-TimMiner18 This system shall have a SystemPassport capability that customs and law enforcement can use to track both the users and the status of the wearable computer.

18 This system shall have a SystemPassport capability that customs and law enforcement can use to track both the users and the status of the wearable computer.

* I agree with Jon, sorry this would IMMEDIATELY turn me off. In my opinion, optional GPS is bad enough. -- RickJones - 01 May 2002

2003BDS-TimMiner19 This system shall have SecurityServices? such that users can grant access or monitoring privaledges to corporate or government security agents.

19 This system shall have SecurityServices? such that users can grant access or monitoring privaledges to corporate or government security agents.

2003BDS-TimMiner20 The Basic or Minimum System shall have a ProcessorRamRom? function.

1 The Basic or Minimum System shall have a ProcessorRamRom? function.

2003BDS-TimMiner21 The Basic or Minimum System shall have a RealTimeClock? function.

2 The Basic or Minimum System shall have a RealTimeClock? function.

2003BDS-TimMiner22 The Basic or Minimum System shall have a GlobalPositioning? function.

3 The Basic or Minimum System shall have a GlobalPositioning? function.

Again yes.. this should be optional and removable(ie. compact flash card). -- RickJones - 01 May 2002

2003BDS-TimMiner23 The Basic or Minimum System shall have an IntegratedTelecom? function.

4 The Basic or Minimum System shall have an IntegratedTelecom? function.

2003BDS-TimMiner24 The Basic or Minimum System shall have a VehicularNetwork? function.

5 The Basic or Minimum System shall have a VehicularNetwork? function.

2003BDS-TimMiner25 The Basic or Minimum System shall have a MassStorage? function.

6 The Basic or Minimum System shall have a MassStorage? function.

2003BDS-TimMiner26 The Basic or Minimum System shall have a RemovableMedia? function.

7 The Basic or Minimum System shall have a RemovableMedia? function.

2003BDS-TimMiner27 The Basic or Minimum System shall have a OneHandKeyboardMouse? function.

8 The Basic or Minimum System shall have a OneHandKeyboardMouse? function.

2003BDS-TimMiner28 The Basic or Minimum System shall have a ColorDisplay? function.

9 The Basic or Minimum System shall have a ColorDisplay? function.

* We need to maintain 640x480 for backward compatibility - RickJones - 01 May 2002

2003BDS-TimMiner29 The Basic or Minimum System shall have a IntegratedMicEarphone? function.

10 The Basic or Minimum System shall have a IntegratedMicEarphone? function.

2003BDS-TimMiner30 The Basic or Minimum System shall have a ReadWriteOpticalMedia? function.

11 The Basic or Minimum System shall have a ReadWriteOpticalMedia? function.

2003BDS-TimMiner31 The Basic or Minimum System shall have a PowerDistribution? function.

12 The Basic or Minimum System shall have a PowerDistribution? function.

2003BDS-TimMiner32 The Basic or Minimum System shall have a IntegratingNetwork? function.

13 The Basic or Minimum System shall have a IntegratingNetwork? function.

2003BDS-TimMiner33 The system shall operate normally between 0 and 60 degrees Celsius.

1 The system shall operate normally between 0 and 60 degrees Celsius.

2003BDS-TimMiner34 The system shall operate normally at 100 percent relative humidity.

2 The system shall operate normally at 100 percent relative humidity.

2003BDS-TimMiner35 The system shall resist moisture and operate normally while the user & wearable endures a rain shower for 60 minutes.

3 The system shall resist moisture and operate normally while the user & wearable e