You're in Wearforge -> Wearfore -> MinimumSystem
-- TimMiner - 30 Apr 2002
These pages are a NoFlamingZone.-- TimMiner - 04 May 2002
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
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
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 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.
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).. also subdividing Hardware into Power Management, Interfaces and Other.-- RickJones 2 May 2002
High Level Requirements (System Philosophy):
TM1 This system shall have an OpenHardwareArchitecture.
- 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
TM2 This system shall have an OpenSoftwareArchitecture.
- 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
- But do not limit the choice of hardware to that what can execute Windows(as a well known company did) -- MarcusWolschon 03 May 2002
TM3 This system shall be able to BootAlternative OS environments from storage media.
- 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
TM4 This system shall preclude OS suppliers from defeating the ability to BootAlternative OS environments.
- 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
TM5 This system shall have an ExtensibleHardwareAndSoftwareArchitecture? that enables development of ExpansionCapabilities?.
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.
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
- Many people can live with 4-5h per battery-set however. -- MarcusWolschon 03 May 2002
TM7 This system shall have a DualAndTripleRedundancy capability for users who wish to implement them for their own operational reasons.
TM8 This system shall have a ComponentRegistration? capability to first embed serial numbers and track registrations and locate registered items.
- 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
TM9 This system shall have a LowEmissions? design to power distribution, Module and chip EM emissions below TBD levels.
TM10 This system shall have ZeroBodyEmPenetration? design to keep EM fields outside the volume of the user's body.
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.
- Most could implement this through a USB/Serial/Parallel or PCI/PC104/PC104+ device. -- RickJones 01 May 2002
TM12 This system shall have HardwareIntegrationArchitecture? that promotes the miniturization and combining of system modules.
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.
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.
TM15 This system shall have local IrAndRf? network and communications for in-room and in-vehicle use.
- One could also use a wireless network card to connect. -- RickJones 01 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)
TM16 This system shall have PowerSaveFeatures? that minimize the drain on batteries when modules are in idle states.
TM17 This system shall have a UsedWearableMarket and follow-on market support for 10 years after manufacture.
Moved debate -- TimMiner - 04 May 2002
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.
- 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 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
* Please see the SystemPassport link and (hopefully) move your debate there. -- TimMiner - 04 May 2002
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.
Functional Requirements:
TM20 The Basic or Minimum System shall have a ProcessorRamRom? function.
TM21 The Basic or Minimum System shall have a RealTimeClock? function.
TM22 The Basic or Minimum System shall have a GlobalPositioning? function.
- The GlobalPositioning? function shall be optional. -- JonKnight - 01 May 2002
- The GlobalPositioning? function shall allow the use of DoD? GPS or alternative global positioning systems in the future. -- 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.
TM23 The Basic or Minimum System shall have an IntegratedTelecom? function.
- The IntegrateTelecom? function shall be modular to allow the use of different telecom technologies geographically and temporaly. -- JonKnight - 01 May 2002
- I agree. TM
TM24 The Basic or Minimum System shall have a VehicularNetwork? function.
- Can we make that a "may" rather than a shall? Not everyone has a car and so this should be optional. -- JonKnight - 01 May 2002
TM25 The Basic or Minimum System shall have a HighSpeedMassStorage? function.
TM26 The Basic or Minimum System shall have a RemovableMedia? function.
TM27 The Basic or Minimum System shall have a OneHandKeyboardMouse? function.
- Can we make "shall" a "may"? Some folk might want voice control/output and not want a one handed keyboard or mouse.
- 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
*So, put 'em in as requirements. --Main TimMiner? 01 May 2002
TM28 The Basic or Minimum System shall have a HeadMountedColorDisplay? function.
- The ColorDisplay? function should have a minimum resolution of 800x600 with 16bit colour. -- JonKnight - 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
- I like the thinking. Please do the honors. --Main TimMiner? 01 May 2002
TM29 The Basic or Minimum System shall have a IntegratedMicEarphone? function.
- Capable of full duplex audio with Microphone and speaker jacks
TM30 The Basic or Minimum System shall have a ReadWriteOpticalMedia? function.
- 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
TM31 The Basic or Minimum System shall have a PowerDistribution? 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 (quantified environment items):
TM33 The system shall operate normally between 0 and 60 degrees Celsius.
- The system shall operate normally between -20 and 60 degrees Celsius. Gotta take account of those folk in cold climates.
- see where the STP format came from? --Main TimMiner? 01 May 2002
TM34 The system shall operate normally at 100 percent relative humidity.
TM35 The system shall resist moisture and operate normally while the user & wearable endures a rain shower for 60 minutes.
TM36 The system shall resist water penetration when emersed in 10 meters of sea water.
- 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
- I don't completely disagree. --Main TimMiner? 01 May 2002
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.
TM38 The system shall resist the moisture and salts produced by the body of the user over 65,000 hours of use.
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
JK2 The system shall provide the option to monitor the biomedical state of the wearer. -- 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
JK4 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
Performance Requirements (quantified system measures):
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 4
- Last RJ-tag is ??
|
