190 likes | 206 Views
Explore how Sens4U streamlines environmental monitoring using wireless sensor networks. Learn about module-based WSN software configurations, application logic definitions, and more. Discover the ConfigKit for automatic software creation and tinyDSM for data storage. Dive into customer requirements, module roles, application logic, and the ideal configuration process. This system helps non-experts specify real-life system requirements and create optimized hardware and software configurations.
E N D
Sens4U: Wireless Sensor Network Applications for Environment Monitoring Made Easy Krzysztof Piotrowski and Steffen Peter
Agenda • Background • Use case • Extended module concept • Applicationlogicdefinition • Ideal configuration • Conclusions
Background • TwocomplementaryPhDtheses • ConfigKit – automaticcreationofmodule-based WSN softwareconfigurationsbased on securityrequirements • tinyDSM – configurabledatastoragefor WSNs witheventdetectionand user-defineddataitems, replicationandconsistency • Combinationofthesesupportsacceleratedapplicationdevelopment • Extensions in bothareasneeded • Extension oftheConfigKitconcepttosoftwareandhardwareandarbitrary (not securityonly) setofrequirements • Simplificationofmethodsallowingthedescriptionofapplicationlogicthatbecomesthe top-level softwaremodule • Environment monitoringapplicationsastheareaofthe Sens4U project
Usecase • Customer defines her requirements: • Locations, Measurements, Maintenance, Reliability • The integrator inputs these into the Planning tool • The Expert System combineschosenmodulesaccordingtotherequirements • The Verificationprocessmaytrigger additional loop, e.g., updatingthemodulepooloradjustingtherequirements • The chosenconfigurationisimplemented • Wefocus on environmentmonitoringscenarious
Y-chart analogy Module Pool
Roles in the development process • End user • Application designer • Integrator User Module Pool ComponentDeveloper FrameworkDesigner
Module Pool relations • includesdefinesthat a modulebelongsto a larger module, e.g., a µC belongsto a nodeplatform. • usesdefinestheinterfacesusedby a givenmodule • providesdefinesinterfacesprovidedby a givenmodule • has_parameterdefinesthevalueof a parameterfrom a providedinterfaceforthegivenmodule • requires_parameterdefinestherequiredvalue(s) of a parameterfrom an usedinterfaceforthegivenmodule
Applicationlogicdefinition • Transformation ofthe non-technicalrequirementsinto a setoftechnicalrequirements • The mosttrickypartofthesystem
Requirements • Requirements are: • Technical parameters and constraints • Description of environment • Description of participants (user, attacker) in the scenario • User requirements are often fuzzy and non-technical • Need for translation of user requirements to technical requirements • User selects and parameterizes properties from a requirement catalogue • They will be translated to technical requirements • Example: Requirements User Requirements Technical Requirements • - Application type (health care, home, industrial) • Required security attributes (concealment, integrity, robustness) • Parameters Attacker model and capabilities
Applicationlogicdefinition, cont • Possible on different detail/experiencelevels • Macroprogramming • Scripting • Pure moduleprogramming • Weidentifiedthemostcommonpatterns (requirementscatalogue) • Withthefocus on environmentmonitoring • Weprovide a GUI todefinetheapplicationlogic (Planning Tool) by: • Providing thegroundviewforthemonitoredarea • Definingcommunicationenvironmentandobstacles • Definingthemeasuringpoints,proceduresanddatadependencies • Prototype implementation will beavailablesoon
Methodology Find models to express properties as function between requirements and system Requirements components • Does the system under development satisfies the requirements? Models Component and system model • How to define requirements? • understood by users • Precise for the system SYSTEM Formal framework
Methodology: CompositionProcess RequirementsCatalog Property Repository Component Repository Requirements Working Model Composition Selection init Input für Selection Goal: Noconflicts Look forsuitable Components
The ideal configuration The configurationsthataregeneratedwiththetoolstheyinfluence
The ideal configuration Forexample: Interface A - Parameter A1 - Parameter A2 Interface B - Parameter B1 Interface C - Parameter C1 • Eachconfigurationconsistsofmodulesconnected via interfaces
Conclusions Wepropose a systemthat: • supports the non-WSN-experts in the specification of they real-life target system requirements, • provides a module description framework to support computer aided application development and module testing, • allows creating application specific/optimized software and hardware configurations, • does not only suggest software compositions, but also suggests hardware components with diverse granularity (platform, chip, module) and functionality (accelerators, sensors, actuators) to fulfill the given task, • utilizes an user and process model that emphasizes the applicability by non-WSN-experts.