Study On The Development Method Of Embedded Software Based On Embedded UML

Embedded System has been applied widely in the industrial, commercial, military field. As we known, Embedded System not only demand high reliability, low power, but also have a real-time requirement, which means that computing logic result and producing time need both the demand. System should response relevantly hi the given tune, which has to ensure the predictability in the tune. In late few years, since wireless communications have been applied widely and Internet have been populate rapidly. Embedded System has been requiring a new development space. For example, mobile telephone, Electrical product for consuming, informational Appliances etc. The situation offers a new challenge for the development of embedded software. When software functions become richer, the Internet have changed and multimedia information need more manage. Therefore a new way to develop the embedded software becomes more and more critical.The paper offers a new development way from the prospective of programmer. At first, It analyze the property of embedded software, introducing embedded UML, a kind of standard UML. Based on the methodology of real-time UML, it contains the methodology of hardware/software co-sign. In order to explain it, the paper illustrates an example of home alarm and other instances to the appliance process of embedded UML developing the software. Referring to two key concepts of PIM and PSM in the newest currently methodology MDA, embedded UML utilizes the mapping mechanism to develop the embedded software.Next, embedded Requirement analysis and modeling. According to the requirement taxonomy, It state heavily the different Quality of Services of hard real-time field and soft real-time field, which lead the development embedded software from the field of traditional industrial control to current the field of informational electrical product. After the require analysis and describe elaborately, embedded UML capture the system functional requirement, performance requirement and QoS requirement in the Scenario, Sequence Diagram, Statechart Diagram and Activity Diagram and relevant model. They are object instructional analysis modeling and object behavior modeling. In the formerchapter, it a key policy of identify objects, provide a way to find object attributes and a class. In the end of chapter, class diagram have access to model the structure. In the object behavior analyze, classify object behavior into three types. Defining object state behavior, Utilizing statechart diagram to model elaborately for state behavior. At last, it depicts a policy of the finite operation.Finally the overview of embedded software test, an example of home alarm to explain the process of modeling, it deploys home alarm into the system with the previous models. At last, It finishes with a lot sentiment and prospect as postscript.