Latest Tutorials| Questions and Answers|Ask Questions?|Site Map



Home Answers Viewqa Java-Beginners read xml using java
Login         

View Questions and Answers by Category

Advertisements


 
Have Programming Question? Ask it here!
 
 
 


muniraju
read xml using java
1 Answer(s)      3 years and 9 months ago
Posted in : Java Beginners


<p>to read multiple attributes and elements from xml in an order....
ex :component name="csl"\layerinterfacefile="poo.c"\interface type=""\level="0"\source_file="ppp" etc as wise each attribute n element to b printed...
here is the xml code......................</p>

<p><?xml version="1.0" encoding="utf-8" ?> 
- <components date="10/8/2010 2:49:41 PM">
- <component name="CSL" longname="" level="0">
  <description><u>Responsible Architect:</u> Joerg Cunz, CES for CSW Christian Sussmann, CES for DDS Dirk Froehlich CHS, for EPB <u>Rationale:</u> The Customer Software integration Layer (CSL) was introduced to provide a stable set of interfaces to "foreign" software parts, especially with focus on Functional Safety related items, e.g. to handle all external software in a protected safety task. <u>Description:</u> The CSL consists of the customer software, the deflation detection and the electrical parking brake. Furthermore customer specific application software (CSW) resides here.</description> 
  <layer_Interface_file>csl<em>epb</em>service_handling.c</layer_Interface_file> 
  <layer_Interface_file>csl<em>epb</em>variant_handling.c</layer_Interface_file> 
  <layer_Interface_file>csl<em>epb</em>variant_nonrelease.c</layer_Interface_file> 
  <layer_Interface_file>csl<em>epb</em>service_handling.h</layer_Interface_file> 
  <layer_Interface_file>csl<em>epb</em>variant_handling.h</layer_Interface_file> 
  <layer_Interface_file>csl<em>epb</em>ebs_synchronisation.he</layer_Interface_file> 
  <layer_Interface_file>csl<em>ipb</em>fram.he</layer_Interface_file> 
  <layer_Interface_file>csl<em>ipb</em>fsre.he</layer_Interface_file> 
  <layer_Interface_file>csl<em>epb</em>signal_layer.he</layer_Interface_file> 
  <layer_Interface_file>csl<em>dds</em>mode.he</layer_Interface_file> 
  <layer_Interface_file>csl<em>dds</em>dia.he</layer_Interface_file> 
  <layer_Interface_file>csl_dds.he</layer_Interface_file> 
  <layer_Interface_file>csl<em>tpm</em>mode.he</layer_Interface_file> 
  <layer_Interface_file>csl_tpmpstat.he</layer_Interface_file> 
  <interface type="Provided" kind="function" name="DDS_INIT_SOFTWARE" /> 
  <interface type="Provided" kind="macroFunction" name="Get_dds_warn_active" /> 
  <interface type="Provided" kind="macro" name="Dds_warn_reason_not_available" /> 
  <interface type="Provided" kind="globalVar" name="IPB_FAILURE_RAM" /> 
- <component name="CSW" longname="Customer Software" level="1">
  <description>Customer Software = Audi XDS NIRA TPI</description> 
  <interface type="Provided" kind="macro" name="CSW_WHL_BACKWARDS" /> 
- <component name="ComSigSupMisc" longname="CommonSignalSupportMisc" level="2">
  <description>Component Architect: Component's Responsible Developer: Description: Rationale: -- Notes: Change History: Date: Author: Changes:</description> 
  <interface_file>sig_ini.h</interface_file> 
  <interface_file>csi_alia.h</interface_file> 
  <interface_file>csisensc.h</interface_file> 
  <interface_file>csi_con.h</interface_file> 
  </component>
- <component name="CswCore" longname="CswCoreFunctionalities" level="2">
  <description>Component Architect: Component's Responsible Developer: Description: Rationale: -- Notes: Change History: Date: Author: Changes:</description> 
- <component name="CswConfig" longname="CswConfiguration" level="3">
  <description>Component Architect: Component's Responsible Developer: Description: Rationale: -- Notes: Change History: Date: Author: Changes:</description> 
  <source_file>csw_conf.he</source_file> 
  </component>
- <component name="CswRes" longname="CswResources" level="3">
  <description>Component Architect: Component's Responsible Developer: Description: Rationale: -- Notes: Change History: Date: Author: Changes:</description> 
  <source_file>csw_ram.c</source_file> 
  <source_file>csw_ram.h</source_file> 
  <source_file>csw<em>ram</em>includes.h</source_file> 
  <source_file>csw_ram1.c</source_file> 
  <source_file>csw_ram2.c</source_file> 
  <source_file>csw_ram3.c</source_file> 
  <interface_file>csw_ram.he</interface_file> 
  </component>
- <component name="CswState" longname="CswStateHandler" level="3">
  <description>Component Architect: Component's Responsible Developer: Description: Rationale: -- Notes: Change History: Date: Author: Changes:</description> 
  <interface_file>csw_state.he</interface_file> 
  </component>
- <component name="CswStruct" longname="CswStructure" level="3">
  <description>Component Architect: Component's Responsible Developer: Description: Rationale: -- Notes: Change History: Date: Author: Changes:</description> 
  <source_file>link.lnk</source_file> 
  </component>
  </component>
- <component name="TPI" longname="Tire Pressure Indicator" level="2">
  <description>Component Architect: Component's Responsible Developer: Description: Rationale: -- Notes: Change History: Date: Author: Changes:</description> 
  </component>
- <component name="XDS" longname="Cross Differentialsperre" level="2">
  <description>Component Architect: Component's Responsible Developer: Description: Rationale: -- Notes: Change History: Date: Author: Changes:</description> 
  </component>
  </component>
- <component name="DDS" longname="Deflation Detection System" level="1">
  <description>Function model DDS. DDS detects if a tire is deflated by evaluating mainly the ABS sensor signals ("Raddrehzahlsensoren"). If a deflated tire is detected, this information has to be given to the driver. The routing of this information is provided by other function models, i.e. COA, DIA and BUS.</description> 
  <interface type="Provided" kind="macro" name="Get_dds_eol_modus" /> 
  <interface type="Provided" kind="Function" name="DDS_RUNNING_CHECK" /> 
  <interface type="Provided" kind="macroFunction" name="Get_dds_acknowledge" /> 
- <component name="DdsCore" longname="DdsCoreFunctionalities" level="2">
  <description>Component Architect: Component's Responsible Developer: Description: Rationale: -- Notes: Change History: Date: Author: Changes:</description> 
  <configuration>DDS_CFG</configuration> 
  <source_file>ifc_pdo.c</source_file> 
  <source_file>idp_dds.c</source_file> 
  <source_file>dds_whel.c</source_file> 
  <source_file>dds_time.c</source_file> 
  <source_file>dds_tcsw.c</source_file> 
  <source_file>dds_swit.c</source_file> 
  <source_file>dds_stat.c</source_file> 
  <source_file>dds_side.c</source_file> 
  <source_file>dds_sens.c</source_file> 
  <source_file>dds_samp.c</source_file> 
  <source_file>dds_ram.c</source_file> 
  <source_file>dds_prot.c</source_file> 
  <source_file>dds_perc.c</source_file> 
  <source_file>dds_nois.c</source_file> 
  <source_file>dds_no.c</source_file> 
  <source_file>dds_main.c</source_file> 
  <source_file>dds_lsq.c</source_file> 
  <source_file>dds_lern.c</source_file> 
  <source_file>dds_lamp.c</source_file> 
  <source_file>dds_io.c</source_file> 
  <source_file>dds_init.c</source_file> 
  <source_file>dds_gear.c</source_file> 
  <source_file>dds_gate.c</source_file> 
  <source_file>dds_filt.c</source_file> 
  <source_file>dds_eep.c</source_file> 
  <source_file>dds<em>d</em>m.c</source_file> 
  <source_file>dds_div.c</source_file> 
  <source_file>dds_dete.c</source_file> 
  <source_file>dds_curv.c</source_file> 
  <source_file>dds_crc.c</source_file> 
  <source_file>dds_comp.c</source_file> 
  <source_file>dds_bls.c</source_file> 
  <source_file>dds_bdrd.c</source_file> 
  <source_file>dds_axle.c</source_file> 
  <source_file>dds_ave.c</source_file> 
  <source_file>dds2tpms.c</source_file> 
  <source_file>dds_whel.h</source_file> 
  <source_file>dds_var.h</source_file> 
  <source_file>dds_time.h</source_file> 
  <source_file>dds_tcsw.h</source_file> 
  <source_file>dds_swit.h</source_file> 
  <source_file>dds_strp.h</source_file> 
  <source_file>dds_stat.h</source_file> 
  <source_file>dds_side.h</source_file> 
  <source_file>dds_sens.h</source_file> 
  <source_file>dds_samp.h</source_file> 
  <source_file>dds_ramc.h</source_file> 
  <source_file>dds_prot.h</source_file> 
  <source_file>dds_perc.h</source_file> 
  <source_file>dds_nois.h</source_file> 
  <source_file>dds_math.h</source_file> 
  <source_file>dds_main.h</source_file> 
  <source_file>dds_lsq.h</source_file> 
  <source_file>dds_lern.h</source_file> 
  <source_file>dds_lamp.h</source_file> 
  <source_file>dds_io.h</source_file> 
  <source_file>dds_init.h</source_file> 
  <source_file>dds_gear.h</source_file> 
  <source_file>dds_gate.h</source_file> 
  <source_file>dds_filt.h</source_file> 
  <source_file>dds_eep.h</source_file> 
  <source_file>dds<em>d</em>m.h</source_file> 
  <source_file>dds_div.h</source_file> 
  <source_file>dds_dete.h</source_file> 
  <source_file>dds_curv.h</source_file> 
  <source_file>dds_crc.h</source_file> 
  <source_file>dds_con.h</source_file> 
  <source_file>dds_comp.h</source_file> 
  <source_file>dds_bls.h</source_file> 
  <source_file>dds_bdrd.h</source_file> 
  <source_file>dds_axle.h</source_file> 
  <source_file>dds_ave.h</source_file> 
  <source_file>dds2tpms.h</source_file> 
  <source_file>dds.h</source_file> 
  <source_file>tom_warn.c</source_file> 
  <source_file>tom_init.c</source_file> 
  <source_file>tom_eval.c</source_file> 
  <source_file>tom_pdet.c</source_file> 
  <source_file>tom_proc.c</source_file> 
  <source_file>tom_dete.c</source_file> 
  <source_file>tom_main.c</source_file> 
  <source_file>tom_lern.c</source_file> 
  <source_file>tom_temp.c</source_file> 
  <source_file>tom_prot.c</source_file> 
  <source_file>tom_gate.c</source_file> 
  <source_file>tom_rom.c</source_file> 
  <source_file>tom_freq.c</source_file> 
  <source_file>tom_ppee.c</source_file> 
  <source_file>tom<em>plaus</em>check.c</source_file> 
  <source_file>tom_filt.c</source_file> 
  <source_file>tom_chck.c</source_file> 
  <source_file>dds_warn.c</source_file> 
  <source_file>tom_strc.h</source_file> 
  <source_file>tom_strp.h</source_file> 
  <source_file>tom_cnst.h</source_file> 
  <source_file>tom_lern.h</source_file> 
  <source_file>tom_temp.h</source_file> 
  <source_file>tom_macr.h</source_file> 
  <source_file>tom_fnct.h</source_file> 
  <source_file>tom_xdep.h</source_file> 
  <source_file>tom_var.h</source_file> 
  <source_file>tom.h</source_file> 
  <source_file>dds_warn.h</source_file> 
  <source_file>vds_velo.c</source_file> 
  <source_file>vds_subt.c</source_file> 
  <source_file>vds_stdd.c</source_file> 
  <source_file>vds_proc.c</source_file> 
  <source_file>vds_main.c</source_file> 
  <source_file>vds_init.c</source_file> 
  <source_file>vds_fft.c</source_file> 
  <source_file>vds_eval.c</source_file> 
  <source_file>vds_eerw.c</source_file> 
  <source_file>vds_chck.c</source_file> 
  <source_file>vds_calc.c</source_file> 
  <source_file>vds_var.h</source_file> 
  <source_file>vds.h</source_file> 
  <source_file>ifc_vds.h</source_file> 
  <source_file>tpm_whel.c</source_file> 
  <source_file>tpm_ram.c</source_file> 
  <source_file>tpm_prot.c</source_file> 
  <source_file>tpm_main.c</source_file> 
  <source_file>tpm_io.c</source_file> 
  <source_file>tpm_init.c</source_file> 
  <source_file>tpmsalarm.c</source_file> 
  <source_file>tpmpstat.c</source_file> 
  <source_file>tpm_var.h</source_file> 
  <source_file>tpm_prot.h</source_file> 
  <source_file>tpmsalarm.h</source_file> 
  <source_file>ifc_tpm.h</source_file> 
  <interface_file>dds_idp.he</interface_file> 
  <interface_file>dds_mode.he</interface_file> 
  <interface_file>dds_dia.he</interface_file> 
  <interface_file>dds.he</interface_file> 
  <interface_file>tpm_mode.he</interface_file> 
  <interface_file>tpmpstat.he</interface_file> 
  <interface_file>tpms_def.he</interface_file> 
  <layer_Interface_file>csl<em>dds</em>mode.he</layer_Interface_file> 
  <layer_Interface_file>csl<em>dds</em>dia.he</layer_Interface_file> 
  <layer_Interface_file>csl_dds.he</layer_Interface_file> 
  <layer_Interface_file>csl<em>tpm</em>mode.he</layer_Interface_file> 
  <interface type="Provided" kind="function" name="DDS_TRANSFER_PREPARATION" /> 
  <interface type="Provided" kind="globalVar" name="Dds_idp_transfer_table" /> 
  <interface type="Provided" kind="macroFunction" name="Get_dds_odometer_status" /> 
  <interface type="Required" kind="macroFunction" name="DABS" /> 
  <interface type="Required" kind="macro" name="True" /> 
  <interface type="Required" kind="function" name="CRC16_CITT" /> 
  <interface type="Required" kind="globalVar" name="ABS_REFERENCE_VELOCITY" /> 
  <interface type="Required" kind="globaldirect" name="CLOCK" /> 
- <component name="DdsConfig" longname="DdsConfiguration" level="3">
  <description>Component Architect: Component's Responsible Developer: Description: Rationale: -- Notes: Change History: Date: Author: Changes:</description> 
  <source_file>global_straptest.he</source_file> 
  </component>
- <component name="DdsRes" longname="DdsResources" level="3">
  <description>Component Architect: Component's Responsible Developer: Description: Rationale: -- Notes: Change History: Date: Author: Changes:</description> 
  <source_file>dds<em>prio1</em>ram.c</source_file> 
  <source_file>dds<em>prio2</em>ram.c</source_file> 
  <source_file>dds<em>prio3</em>ram.c</source_file> 
  <source_file>dds<em>private</em>ram.c</source_file> 
  <source_file>dds_ram.c</source_file> 
  <source_file>dds_ram.h</source_file> 
  <interface type="Required" kind="macro" name="Dds_time_channel_main_group1" /> 
  </component>
- <component name="DdsState" longname="DdsStateHandler" level="3">
  <description>Component Architect: Component's Responsible Developer: Description: Rationale: -- Notes: Change History: Date: Author: Changes:</description> 
  </component>
- <component name="DdsStruct" longname="DdsStructure" level="3">
  <description>Component Architect: Component's Responsible Developer: Description: Rationale: -- Notes: Change History: Date: Author: Changes:</description> 
  <source_file>dds_init.c</source_file> 
  <source_file>dds_init.h</source_file> 
  <source_file>link.lnk</source_file> 
  <interface type="Required" kind="macro" name="Dds_time_channel_main_group1" /> 
  <interface type="Required" kind="globalVar" name="DDS_NOISE_COUNTER_DIAG_TQ" /> 
  <interface type="Required" kind="function" name="DDS_INIT_EEPROM_FSM" /> 
  <interface type="Required" kind="macroFunction" name="Dds_plus_off" /> 
  </component>
  </component>
  </component>
- <component name="EPB" longname="ElectricalParkingBrake" level="1">
  <description>Component's Responsible Developer: Description: Electrical Parking Brake (EPB) The RAM consumption shall not exceed 4 kByte The ROM consumption shall not exceed 100 kByte The EEPROM consumption shall not exceed 230 Byte The Runtime of the software shall not exceed 900 ?µs Rationale: This function model contains all electrical parking brake related functionalities. Notes: Change History: Date: 04.02.2009 Author: Thomas Merker Changes: Component description</description> 
- <component name="EPBMainTask" longname="EPBMainTask" level="2">
  <description>Component Architect: Component's Responsible Developer: Description: The MainTask implements the whole functionality of the electrical parking brake (ECR, ERR, DAR, KOA, ?) Rationale: -- Notes: Change History: Date: Author: Changes:</description> 
- <component name="AC" longname="Actuator_Control" level="3">
  <description>Component Architect: Component's Responsible Developer: Description: The actuation controller implements the control strategy for the underlying hardware to reach the desired control target. The actuation controller generates the the motor control request. The actuation controller stops the actuation by active braking when control target has been reached. The actuation controller stops the actuation by disabling the HBridge when a stop request is received or when the brake target has been reached successfully. The actuation controller generates actuation state. The actuation controller is neither responsible for monitoring the actuation result nor for autonomous failure acting. The RAM consumption shall not exceed 120 Byte The ROM consumption shall not exceed 16000 Byte Rationale: -- Notes: Change History: Date: Author: Changes:</description> 
  <source_file>actuator_control.c</source_file> 
  <source_file>actuator_control.h</source_file> 
  <source_file>actuator<em>control</em>cfg.h</source_file> 
  <interface_file>signal_layer.h</interface_file> 
  <interface type="Required" kind="macro" name="GDcub_ACT_ABILITY_TYPE" /> 
  </component>
- <component name="AVE" longname="Actual_Value_Evaluation" level="3">
  <description>Component Architect: Component's Responsible Developer: Description: The Actual Value Evaluation is responsible for coordinating the evaluation of the actual values related to the actuation. It provides an interface to the actual values which are at least required by the actuation controller. As the semantics of the actual data depends on the concrete actuation controller the actual value controller shall at least provide the concrete actual values. Depending on the context there might be the necessity that the actuation controller has to signalize something to the actuation value controller (e.g. request for starting current profile analysis). The actual value controller shall provide an interface for receiving signals from the actuation controller. Furthermore it might be possible that the actual value controller produces derived signals (e.g. data from model) that are required by the actuation controller to verify its results. For that reason the actual value controller shall provide an interface for reading derived signals. The Actual Value Evaluation component calculates: - motor current, motor voltage, motor direction - rotor temperature, stator temperature - several internal motor values The RAM consumption shall not exceed 700 Byte The ROM consumption shall not exceed 7500 Byte Rationale: -- Notes: Change History: Date: Author: Changes:</description> 
  <source_file>actual<em>value</em>evaluation.c</source_file> 
  <source_file>actual<em>value</em>evaluation.h</source_file> 
  <source_file>actual<em>value</em>evaluation_cfg.h</source_file> 
  <interface_file>signal_layer.h</interface_file> 
  </component>
- <component name="DAR" longname="Drive_Away_Release" level="3">
  <description>Component Architect: Component's Responsible Developer: Description: The DAR module handles the clutch and gear estimation (for maual transmission velicles) and generates the DAR Request, depending on several input signals. The RAM consumption shall not exceed 300 Byte The ROM consumption shall not exceed 6200 Byte Rationale: -- Notes: Change History: Date: Author: Changes:</description> 
  <source_file>drive<em>away</em>release.c</source_file> 
  <source_file>drive<em>away</em>release.h</source_file> 
  <interface_file>signal_layer.h</interface_file> 
  <interface type="Required" kind="macro" name="ER_REVERSED_GEAR_PLAUSIBILTY" /> 
  <interface type="Required" kind="function" name="ER_vSetError" /> 
  </component>
- <component name="DIA" longname="EPB_Diagnosis" level="3">
  <description>Component Architect: Component's Responsible Developer: Description: EPB Diagnosis provides EPB specific diagnosis requests. The RAM consumption shall not exceed 50 Byte The ROM consumption shall not exceed 1400 Byte Rationale: -- Notes: Change History: Date: Author: Changes:</description> 
  <source_file>diagnosis.c</source_file> 
  <source_file>diagnosis.h</source_file> 
  <source_file>diagnosis_cfg.h</source_file> 
  <interface_file>signal_layer.h</interface_file> 
  <interface type="Required" kind="macro" name="ER_IPB_UNDERVOLTAGE" /> 
  </component>
- <component name="DS" longname="Driver_State" level="3">
  <description>Component Architect: Component's Responsible Developer: Description: The driver state builds the information if the driver is present in dependency of the vehicle conditions. Output of the Driver State Module is the Driver State for static release (SAR<em>DRV</em>STATE) and the Driver State for Drive Away Release (DAR<em>DRV</em>STATE). The RAM consumption shall not exceed 50 Byte The ROM consumption shall not exceed 1000 Byte Rationale: -- Notes: Change History: Date: Author: Changes:</description> 
  <source_file>driver_state.c</source_file> 
  <source_file>driver_state.h</source_file> 
  <source_file>driver<em>state</em>cfg.h</source_file> 
  <interface_file>signal_layer.h</interface_file> 
  </component>
- <component name="EC" longname="EPB_Control" level="3">
  <description>Component Architect: Component's Responsible Developer: Description: The EPB Control evaluates the driver request, the vehicle condition, ..., and triggers an actuation to the actuator modules: -static apply -static release -dynamic apply. The EPB Control generates the Driver Class State (DRV<em>CLASS), the Combined Actuator State (COMBI</em>ACT<em>STATE) and the system state (SYS</em>STATE). The RAM consumption shall not exceed 250 Byte The ROM consumption shall not exceed 16500 Byte Rationale: -- Notes: Change History: Date: Author: Changes:</description> 
  <source_file>epb_control.c</source_file> 
  <source_file>epb_control.h</source_file> 
  <source_file>epb<em>control</em>cfg.h</source_file> 
  <interface_file>signal_layer.h</interface_file> 
  <interface type="Required" kind="macro" name="ER_IPB_CRAZY_DRIVER_FAULT" /> 
  </component>
- <component name="EPBSW" longname="EPB_Switch" level="3">
  <description>Component Architect: Component's Responsible Developer: Description: The Switch module processes the hard wired input signals in meaning of decoding the customer specific patterns, debounce and filters the signal and set errors if necessary. The RAM consumption shall not exceed 30 Byte The ROM consumption shall not exceed 2500 Byte Rationale: -- Notes: Change History: Date: Author: Changes:</description> 
  <source_file>epb_switch.c</source_file> 
  <source_file>epb_switch.h</source_file> 
  <source_file>epb<em>switch</em>cfg.h</source_file> 
  <interface_file>signal_layer.h</interface_file> 
  <interface type="Required" kind="macro" name="ER_SWITCH_FAULT" /> 
  </component>
- <component name="ER" longname="Error_Manager" level="3">
  <description>Component Architect: Component's Responsible Developer: Description: The error manager collects and processes all errors according their configuration. Processing includes the masking mechanism and the healing mechanism. "Masking" means "do not inform the indication module about an present error under certain circumstances, e.g. during motor start". "Healing" means "hold the already not present error in the active state until a certain event appears". If any module reports a "PRESENT" error and no masking event is present, the error gets "ACTIVE". If any module reports a "NOT PRESENT" error and the healing condition is present, the error gets "NOT ACTIVE". The RAM consumption shall not exceed 120 Byte The ROM consumption shall not exceed 1500 Byte Rationale: -- Notes: Change History: Date: Author: Changes:</description> 
  <source_file>error_manager.c</source_file> 
  <source_file>error<em>manager</em>cfg.c</source_file> 
  <source_file>error_manager.h</source_file> 
  <source_file>error<em>manager</em>cfg.h</source_file> 
  <interface_file>signal_layer.h</interface_file> 
  </component>
- <component name="ESM" longname="ECU_State_Manager" level="3">
  <description>Component Architect: Component's Responsible Developer: Description: The ECU State Manager is the interface to the COA state handling (including Soft Reset). It controls the startup/shutdown behaviour of all EPB software modules and is able to wake the rest of the ECU. The RAM consumption shall not exceed 30 Byte The ROM consumption shall not exceed 5000 Byte Rationale: -- Notes: Change History: Date: Author: Changes:</description> 
  <source_file>ecu<em>state</em>manager.c</source_file> 
  <source_file>ecu<em>state</em>manager.h</source_file> 
  <source_file>ecu<em>state</em>manager_cfg.h</source_file> 
  <interface_file>signal_layer.h</interface_file> 
  <interface type="Required" kind="function" name="MCH_vInit" /> 
  <interface type="Required" kind="macroFunction" name="Time_stamp_create_channel_env" /> 
  <interface type="Required" kind="macro" name="Time_stamp_channel_group_epb" /> 
  </component>
- <component name="HBC" longname="Hydraulic_Brake_Control" level="3">
  <description>Component Architect: Component's Responsible Developer: Description: This module handles the interface to the hydraulic control of the EBS software. The RAM consumption shall not exceed 50 Byte The ROM consumption shall not exceed 2500 Byte Rationale: -- Notes: Change History: Date: Author: Changes:</description> 
  <source_file>hydraulic<em>brake</em>control.c</source_file> 
  <source_file>hydraulic<em>brake</em>control.h</source_file> 
  <source_file>hydraulic<em>brake</em>control_cfg.h</source_file> 
  <interface_file>signal_layer.h</interface_file> 
  </component>
- <component name="ISENS" longname="Inclination_Sensor" level="3">
  <description>Component Architect: Component's Responsible Developer: Description: The inclination sensor generates an inclination value (RSLOPE) based on the longitudinal acceleration value and the vehicle reference velocity. Based on the generated inclination value the inclination sensor also generates the road slope state (RSL_STATE). Input for this Module are the CAN or an analog voltage from a real sensor or the longitudinal acceleration and the vehicle speed. The RAM consumption shall not exceed 30 Byte The ROM consumption shall not exceed 1500 Byte Rationale: -- Notes: Change History: Date: Author: Changes:</description> 
  <source_file>inclination_sensor.c</source_file> 
  <source_file>inclination<em>sensor</em>cfg.c</source_file> 
  <source_file>inclination_sensor.h</source_file> 
  <source_file>inclination<em>sensor</em>cfg.h</source_file> 
  <interface_file>signal_layer.h</interface_file> 
  </component>
- <component name="MCH" longname="Monitoring_Channel" level="3">
  <description>Component Architect: Component's Responsible Developer: Description: The monitoring channel is responsible for supervising the actuation. Therefore the Monitoring Channel checks the actuation context dependant abortion criterias during the entire actuation cycle. Due to the fact that the abortion criterias depend on the actuation context the Monitoring Channel shall provide context related Monitoring Strategies. For selecting the right strategy the Monitoring Channel requires on the one hand information about the actuation request type generated by the Nominal Value Evaluation component. On the other hand the Monitoring Channel requires information about the output of the Actuation Controller (especially the motor control request) because it could happen that the Actuation Controller comes to the decision that for the execution of the actuation request more complex steps would be necessary. Each strategy may require different signals for supervising its abortion criterias. Those signals are provided by the Actual Value Evaluation component. The monitoring strategy shall detect the following abortion criterias Before defining the monitoring states it is necessary to define the abortion criterias of an actuation. - motor current exceeds maximum current threshold value - motor current exceeds minimum current threshold value - power dissipation exceeds maximum threshold value - standstill of the motor during an actuation The RAM consumption shall not exceed 100 Byte The ROM consumption shall not exceed 4500 Byte Rationale: -- Notes: Change History: Date: Author: Changes:</description> 
  <source_file>monitoring_channel.c</source_file> 
  <source_file>monitoring<em>channel</em>cfg.c</source_file> 
  <source_file>monitoring_channel.h</source_file> 
  <interface_file>signal_layer.h</interface_file> 
  <interface type="Required" kind="macro" name="ER_IMAX_0" /> 
  </component>
- <component name="NVE" longname="Nominal_Value_Evaluation" level="3">
  <description>Component Architect: Component's Responsible Developer: Description: The Nominal Value Evaluation provides the following functionality: - initializiation of all subcomponents contained in the Nominal Value Evaluation - prepare all subcomponents for shutdown - coordinating and synchronizing action requests from the EPB control dependant on the actuation state - generating actuation request for each actuator separately - generation of the nominal values for the actuation controller - acting on actuation states and failures caused by the actuation controller - evaluation of actuation state and failure states caused by the actuation controller and the monitoring channel - generating the actuator state The RAM consumption shall not exceed 120 Byte The ROM consumption shall not exceed 4500 Byte Rationale: -- Notes: Change History: Date: Author: Changes:</description> 
  <source_file>nominal<em>value</em>evaluation.c</source_file> 
  <source_file>nominal<em>value</em>evaluation_cfg.c</source_file> 
  <source_file>nominal<em>value</em>evaluation.h</source_file> 
  <source_file>nominal<em>value</em>evaluation_cfg.h</source_file> 
  <interface_file>signal_layer.h</interface_file> 
  </component>
- <component name="PM" longname="Power_Monitoring" level="3">
  <description>Component Architect: Component's Responsible Developer: Description: The Power monitoring monitors the KL30. The main functionality is to detect under- and overvoltage. The RAM consumption shall not exceed 20 Byte The ROM consumption shall not exceed 1800 Byte Rationale: -- Notes: Change History: Date: Author: Changes:</description> 
  <source_file>power_monitoring.c</source_file> 
  <source_file>power_monitoring.h</source_file> 
  <source_file>power<em>monitoring</em>cfg.h</source_file> 
  <interface_file>signal_layer.h</interface_file> 
  <interface type="Required" kind="macro" name="ER_IPB_OVERVOLTAGE" /> 
  </component>
- <component name="SA" longname="Signal_Layer_Adaption" level="3">
  <description>Component Architect: Component's Responsible Developer: Description: The Signal Adaption provides communication services to the EBS software and to the Safety Task. The RAM consumption shall not exceed 50 Byte The ROM consumption shall not exceed 11000 Byte Rationale: -- Notes: Change History: Date: Author: Changes:</description> 
  <source_file>signal<em>layer</em>adaption.c</source_file> 
  <interface_file>csl<em>epb</em>signal_layer.he</interface_file> 
  <interface_file>signal_layer.h</interface_file> 
  <layer_Interface_file>csl<em>epb</em>signal_layer.he</layer_Interface_file> 
  <layer_Interface_file>csl<em>ipb</em>fram.he</layer_Interface_file> 
  <layer_Interface_file>csl<em>ipb</em>fsre.he</layer_Interface_file> 
  <interface type="Required" kind="macro" name="ERcub_EVENT_FAILED_BIT_ARRAY_SIZE_MAX" /> 
  <interface type="Required" kind="function" name="CSL_GET_EPB_SERVICE_REQ" /> 
  <interface type="Required" kind="macroFunction" name="Get_fs_unreliable_velo_calc" /> 
  <interface type="Required" kind="globalVar" name="SLrst_NVM_CycleInfoBlock" /> 
  </component>
- <component name="SEM" longname="System_Environment_Manager" level="3">
  <description>Component Architect: Component's Responsible Developer: Description: The system environment manager distributes the following system states or events: -Initialization -Under/Overvoltage -Startup/Shutdown -Engine start -Ignition -Diagnosis The RAM consumption shall not exceed 100 Byte The ROM consumption shall not exceed 1000 Byte Rationale: -- Notes: Change History: Date: Author: Changes:</description> 
  <source_file>system<em>environment</em>manager.c</source_file> 
  <source_file>system<em>environment</em>manager.h</source_file> 
  <source_file>system<em>environment</em>manager_cfg.h</source_file> 
  <interface_file>signal_layer.h</interface_file> 
  </component>
- <component name="SGS" longname="Signal_Generation_Safetytask" level="3">
  <description>Component Architect: Component's Responsible Developer: Description: This module generates signals needed in the safety task. The safety task could generate these signals itself, but to keep it clean from any customer specific code, they are generated here and handed to the safety task via standard interfaces. The RAM consumption shall not exceed 20 Byte The ROM consumption shall not exceed 750 Byte Rationale: -- Notes: Change History: Date: Author: Changes:</description> 
  <source_file>signal<em>generation</em>safetytask.c</source_file> 
  <source_file>signal<em>generation</em>safetytask.h</source_file> 
  <source_file>signal<em>generation</em>safetytask_cfg.h</source_file> 
  <interface_file>signal_layer.h</interface_file> 
  </component>
- <component name="SL" longname="Signal_Layer" level="3">
  <description>Component Architect: Component's Responsible Developer: Description: The signal layer provides the functionality of a data store to other interacting modules, as communication is only allowed to take place using this layer. The data stored is composed of the signal state and the signal value. The functions are split up into three general categories: - init function - SET functions for writing data to the signal layer - GET functions for reading data from the signal layer. The interface for the init function is described here within this chapter. The SET and GET functions are only described in their basic principles, the interface definition is made in each module which uses the signal layer. The RAM consumption shall not exceed 1300 Byte The ROM consumption shall not exceed 7000 Byte Rationale: -- Notes: Change History: Date: Author: Changes:</description> 
  <source_file>signal_layer.c</source_file> 
  <source_file>signal<em>layer</em>cfg.c</source_file> 
  <source_file>signal_layer.h</source_file> 
  <source_file>signal<em>layer</em>cfg.h</source_file> 
  <interface_file>signal_layer.h</interface_file> 
  <interface type="Required" kind="function" name="memcpy" /> 
  <interface type="Required" kind="macro" name="ERcub_EVENT_FAILED_BIT_ARRAY_SIZE_MAX" /> 
  </component>
- <component name="VEM" longname="Vehicle_Environment_Manager" level="3">
  <description>Component Architect: Component's Responsible Developer: Description: The Vehicle Environment Manager evaluates the vehicle speed from certain wheel speed signals and generates the vehicle reference speed (VREF, VREF<em>STATE). Other functionalities are the generation of the Vehicle State (VEH</em>STATE), the Engine Speed Acceleration (ENGSP<em>ACC), the Engine State (ENG</em>STATE)and the Wheel Slips (WHL<em>SLIP</em>X, WHL<em>SLIP</em>XT_X). The RAM consumption shall not exceed 80 Byte The ROM consumption shall not exceed 3000 Byte Rationale: -- Notes: Change History: Date: Author: Changes:</description> 
  <source_file>vehicle<em>environment</em>manager.c</source_file> 
  <source_file>vehicle<em>environment</em>manager.h</source_file> 
  <source_file>vehicle<em>environment</em>manager_cfg.h</source_file> 
  <interface_file>signal_layer.h</interface_file> 
  </component>
  </component>
- <component name="EPBSafetyTask" longname="EPBSafetyTask" level="2">
  <description>Component Architect: Component's Responsible Developer: Description: The SafetyTask checks if motor actions are allowed in the actual situation, with an reduced and independant impelemented set of algorithms. Without the agreement of the SafetyTask the EPB can never change the actual acutator positions or perform any request. Rationale: -- Notes: Change History: Date: Author: Changes:</description> 
- <component name="SCS" longname="Safety_Case_Supervision" level="3">
  <description>Component Architect: Component's Responsible Developer: Description: This module calculates the agreement to motor or hydraulic actions requested be the maintask. The RAM consumption shall not exceed 50 Byte The ROM consumption shall not exceed 4500 Byte Rationale: -- Notes: Change History: Date: Author: Changes:</description> 
  <source_file>safety<em>case</em>supervision.c</source_file> 
  <source_file>safety<em>case</em>supervision.h</source_file> 
  <source_file>safety<em>case</em>supervision_cfg.h</source_file> 
  <interface_file>safety<em>signal</em>layer.h</interface_file> 
  </component>
- <component name="SESM" longname="Safety_ECU_State_Manager" level="3">
  <description>Component Architect: Component's Responsible Developer: Description: It controls the startup/shutdown behaviour of all safety task software modules. The RAM consumption shall not exceed 20 Byte The ROM consumption shall not exceed 600 Byte Rationale: -- Notes: Change History: Date: Author: Changes:</description> 
  <source_file>safety<em>ecu</em>state_manager.c</source_file> 
  <source_file>safety<em>ecu</em>state_manager.h</source_file> 
  <source_file>safety<em>ecu</em>state<em>manager</em>cfg.h</source_file> 
  <interface_file>safety<em>signal</em>layer.h</interface_file> 
  <interface type="Required" kind="macroFunction" name="Time_stamp_create_channel_env" /> 
  <interface type="Required" kind="macro" name="Time_stamp_channel_group_epb" /> 
  </component>
- <component name="SSA" longname="Safety_Signal_Adaption" level="3">
  <description>Component Architect: Component's Responsible Developer: Description: The Safety Signal Adaption provides communication services to the EBS software and to the Main Task. The RAM consumption shall not exceed 40 Byte The ROM consumption shall not exceed 1200 Byte Rationale: -- Notes: Change History: Date: Author: Changes:</description> 
  <source_file>safety<em>signal</em>adaption.c</source_file> 
  <source_file>safety<em>signal</em>adaption.h</source_file> 
  <source_file>safety<em>signal</em>adaption_cfg.h</source_file> 
  <interface_file>csl<em>epb</em>signal_layer.he</interface_file> 
  <interface_file>safety<em>signal</em>layer.h</interface_file> 
  <layer_Interface_file>csl<em>epb</em>signal_layer.he</layer_Interface_file> 
  <interface type="Required" kind="function" name="CSL_GET_VARCODE_EPB_ENCODED" /> 
  <interface type="Required" kind="globalVar" name="HBRSV" /> 
  <interface type="Required" kind="macro" name="UNCHANGED_WHEEL_VELOCITY1" /> 
  <interface type="Required" kind="macroFunction" name="Get_fs_unreliable_velo_calc" /> 
  </component>
- <component name="SSL" longname="Safety_Signal_Layer" level="3">
  <description>Component Architect: Component's Responsible Developer: Description: The safety signal layer provides the functionality of a data store to other interacting modules, as communication is only allowed to take place using this layer. The data stored is composed of the signal state and the signal value. The functions are split up into three general categories: - init function - SET functions for writing data to the signal layer - GET functions for reading data from the signal layer. The interface for the init function is described here within this chapter. The SET and GET functions are only described in their basic principles, the interface definition is made in each module which uses the safety signal layer. The RAM consumption shall not exceed 100 Byte The ROM consumption shall not exceed 800 Byte Rationale: -- Notes: Change History: Date: Author: Changes:</description> 
  <source_file>safety<em>signal</em>layer.c</source_file> 
  <source_file>safety<em>signal</em>layer.h</source_file> 
  <source_file>safety<em>signal</em>layer_cfg.h</source_file> 
  <interface_file>safety<em>signal</em>layer.h</interface_file> 
  <interface type="Required" kind="function" name="SSA_vCalcPCUactivateCmdCrypt" /> 
  </component>
- <component name="SVS" longname="Safety_Vehicle_Speed" level="3">
  <description>Component Architect: Component's Responsible Developer: Description: This module generates the speed permission. The RAM consumption shall not exceed 20 Byte The ROM consumption shall not exceed 1000 Byte Rationale: -- Notes: Change History: Date: Author: Changes:</description> 
  <source_file>safety<em>vehicle</em>speed.c</source_file> 
  <source_file>safety<em>vehicle</em>speed.h</source_file> 
  <source_file>safety<em>vehicle</em>speed_cfg.h</source_file> 
  <interface_file>safety<em>signal</em>layer.h</interface_file> 
  </component>
  </component>
- <component name="EbsEpbCom" longname="EbsEpbCommunication" level="2">
  <description>Component Architect: Component's Responsible Developer: Description: Rationale: -- Notes: Change History: Date: Author: Changes:</description> 
  <configuration>CFG<em>ACTUATOR</em>IPB</configuration> 
  <source_file>epb<em>ebs</em>synchronisation.c</source_file> 
  <source_file>csl<em>epb</em>service_handling.c</source_file> 
  <source_file>csl<em>epb</em>variant_handling.c</source_file> 
  <source_file>csl<em>epb</em>variant_nonrelease.c</source_file> 
  <interface_file>csl<em>epb</em>service_handling.h</interface_file> 
  <interface_file>csl<em>epb</em>variant_handling.h</interface_file> 
  <layer_Interface_file>csl<em>epb</em>ebs_synchronisation.he</layer_Interface_file> 
  <layer_Interface_file>var_cod.hdb</layer_Interface_file> 
  </component>
- <component name="EpbCore" longname="EpbCoreFunctionalities" level="2">
  <description>Component Architect: Component's Responsible Developer: Description: Rationale: -- Notes: Change History: Date: Author: Changes:</description> 
- <component name="EpbConfig" longname="EpbConfiguration" level="3">
  <description>Component Architect: Component's Responsible Developer: Description: Rationale: -- Notes: Change History: Date: Author: Changes:</description> 
  <source_file>epb<em>cust</em>conf_ford.h</source_file> 
  <source_file>epb<em>cust</em>conf_none.h</source_file> 
  <source_file>epb<em>cust</em>conf_vw.h</source_file> 
  </component>
- <component name="EpbRes" longname="EpbResources" level="3">
  <description>Component Architect: Component's Responsible Developer: Description: Rationale: -- Notes: Change History: Date: Author: Changes:</description> 
  </component>
- <component name="EpbState" longname="EpbStateHandler" level="3">
  <description>Component Architect: Component's Responsible Developer: Description: Rationale: -- Notes: Change History: Date: Author: Changes:</description> 
  </component>
- <component name="EpbStruct" longname="EpbStructure" level="3">
  <description>Component Architect: Component's Responsible Developer: Description: Rationale: -- Notes: Change History: Date: Author: Changes:</description> 
  <source_file>link.lnk</source_file> 
  </component>
  </component>
  </component>
  </component></p>

Advertisement
View Answers

February 14, 2011 at 11:24 AM


Please visit the following link:

Read XML data



Related Tutorials/Questions & Answers:
Read XML using Java
of all i need to read xml using java . i did good research in google and came to know...Read XML using Java  Hi All, Good Morning, I have been working.../xmlParsing/java-xml-parsing-using-sax.shtml http://www.roseindia.net/xml/sax
read xml using java
read xml using java  <p>to read multiple attributes and elements from xml in an order.... ex :component name="csl"\layerinterfacefile="poo.c...;   Please visit the following link: Read XML data
Advertisements
how to read and write an xml file using java
how to read and write an xml file using java  Hi Can anyone help me how to read and write an xml file which has CData using java
How to read value from xml using java?
How to read value from xml using java?  Hi All, I want to read value from following xml using java.. In <Line>,data is in format of key and value pair.. i want to read only values..could u plz help me in this?Thanks
read XML file and display it using java servlets
read XML file and display it using java servlets  sir, i can't access Xml which is present in my d drive plz can u should go through my code n tell me the things where i went wrong java servlet program protected void
Read XML in java - XML
Read XML in java  Hi Deepak, I want to read a xml file which have only one element with multiple attributes with same tag name. here is my file... a solution.my java code is given below. import java.io.File; import
Read Complex XML using DOM/SAX Parser.
Read Complex XML using DOM/SAX Parser.  I have a XML file which is having two types of Items. I want to extract all details of a type only. My XML goes something like this <Movie> <Bollywood> <Actor> Shah Rukh
how to read values from java in xml?
how to read values from java in xml?  how to read values from java in xml
Read the value from XML in java
Read the value from XML in java  Hi, i have an XML with the following code. I need to get the path("D... the permissions on that file.So how can i read that value. This is little urgent
read xml elements
read xml elements  i want read xml data using sax parser in java. but is there any classes or methods to read xml elements
read xml elements
read xml elements  i want read xml data using sax parser in java. but is there any classes or methods to read xml elements
read xml
read xml   hi all, i want to ask about how to read an xml in java ME.. here is the xml file <data> <value> <struct> <member> <name> User_Name
accessing xml using java
accessing xml using java  I need to retrieve some elements in xml file using java   Hi Friend, Please visit the following links: http://www.roseindia.net/xml/Listingnode.shtml http://www.roseindia.net/xml/getting
XML parsing using Java - XML
XML parsing using Java  I'm trying to parse a big XML file in JAVA..." in element "MIRate"(THE XML code is below).once he enters coverage rate I need... for it skipping all the elements in Table 1. I'm usin using saxparser, startelement
can't read my xml file in java
can't read my xml file in java  i've a xml file like this : <...(); } the codes can't read the xml file bcz i want to append the whole xml in my gui. seems the problems is all xml tag must be enum. can you suggest me how to read
can't read my xml file in java
can't read my xml file in java  i've a xml file like this : <...(); } the codes can't read the xml file bcz i want to append the whole xml in my gui. seems the problems is all xml tag must be enum. can you suggest me how to read
can't read my xml file in java
can't read my xml file in java  i've a xml file like this : <...(); } the codes can't read the xml file bcz i want to append the whole xml in my gui. seems the problems is all xml tag must be enum. can you suggest me how to read
can't read my xml file in java
can't read my xml file in java  i've a xml file like this : <...(); } the codes can't read the xml file bcz i want to append the whole xml in my gui. seems the problems is all xml tag must be enum. can you suggest me how to read
can't read my xml file in java
can't read my xml file in java  i've a xml file like this : <...(); } the codes can't read the xml file bcz i want to append the whole xml in my gui. seems the problems is all xml tag must be enum. can you suggest me how to read
can't read my xml file in java
can't read my xml file in java  i've a xml file like this : <...(); } the codes can't read the xml file bcz i want to append the whole xml in my gui. seems the problems is all xml tag must be enum. can you suggest me how to read
read string - using loops in Java
read string - using loops in Java  Write a program to read a string composed of an unknown number of words, then count the number of words in the string, and Display the longest and shortest words, with first letter Uppercase
how to read this xml file - XML
how to read this xml file  i want to read this xml file using java(using struts2 or using jsp) and i want result as name=admin menu=user... read i have tried lot more , but i am not able to read this xml file
XML- read Text Mode - Java Error in Windows - reg. - Java Beginners
XML- read Text Mode - Java Error in Windows - reg.  Dear All I'm creating the code as read the XML file in BufferedReader method. Here I pasted the code below:. (*) First read the XML file using FileInputStream
read/write to Windows Registry using Java
read/write to Windows Registry using Java  read/write to Windows Registry using Java
Data read. - XML
Data read.  How to store or read data in XML from Struts.Plz give me example. Thanx
simple code to write an read and write the login detail to a xml file using javascript ( username and password )
simple code to write an read and write the login detail to a xml file using... to write and read the login details (username and password )into a xml file using javascript. (XML database
xml file reading using java
xml file reading using java  hi deepak I want to read some data from xml file and send that output to particular email address using java   import org.w3c.dom.*; import org.w3c.dom.Node; import javax.xml.parsers.
To read & write a excel file using the core java
To read & write a excel file using the core java  Hai, I'm new to JavaProgram.But now i need java program to read & write a excel file so, can anyone help me to learn the above mentioned topic(link for the portion
xml Converting to java using JDOM
xml Converting to java using JDOM  Hello , I am new to java and JDom so i make a Xml file and i need help to read it from java using objects , my... should be inside a student object i will include the java code and xml code and i
Read Header/Footer Margin size using Java
Read Header/Footer Margin size using Java  Hi, Is it possible to read the "Header from Top" and "Footer from bottom" properties of a MS word document in Java? I have been searching the web for hours now, POI's and several other
Read Header/Footer Margin size using Java
Read Header/Footer Margin size using Java  Hi, Is it possible to read the "Header from Top" and "Footer from bottom" properties of a MS word document in Java? I have been searching the web for hours now, POI's and several other
 

 

 

DMCA.com