Nevertheless, few research projects address its automatic generation. User interface (UI) development, in the scope of data intensive interactive applications, is a time consuming but repetitive task. And so, the similarity can be utilized to generate requirements specification from DFD to UML Diagram. Furthermore, the factors involved in the similarities are found. Then, the method is tested with the case study of DFD and UML diagrams. Established along the similarity methods, this paper will define the syntax rules of DFD Level 0, DFD Level 1, UML Use Case Diagram and Sequence Diagram. This paper proposes a framework which is acquired from the syntax rules for DFD and UML. It is also serves as a documentation for the upcoming development of new systems. In the end, they produced a new UML diagram as a design material and the implementation of new systems. Most researches are concentrated on converting the existing DFD to UML diagram. Nowadays, there is an intensive research for model transformation, integrating and merging from structured to object-oriented approach. In SDLC, DFD (data flow diagram) specification is used, meanwhile UML (unified modelling language) specification is used for the object-oriented approach. During analysis and design, requirements specification can be documented using two (2) mostly methodologies which are SDLC (software development life cycle) and OOSAD (object-oriented system analysis and design). This situation needed software engineering to produce dependable and trustworthy systems economically and rapidly. Today, individual and society relies on innovative software systems. We exemplify the approach with an IPv6 router case study. In addition, model transformations have been specified and implemented to automate the process. The approach was integrated in a model-driven engineering process, where tool support for the models used was provided. The rationale behind the approach is that both views are important for modeling purposes in embedded systems environments, and thus a combined and integrated model is not only useful, but also fundamental for developing complex systems. More specifically, we present how the main modeling tool of the traditional structured methods, data flow diagrams, can be integrated in an object-oriented development strategy based on the unified modeling language. We discuss whether the object-oriented modeling paradigm, the predominant one to develop software at the present time, is also adequate for modeling embedded software and how it can be used with the functional paradigm. The main aim of this article is to discuss how the functional and the object-oriented views can be inter-played to represent the various modeling perspectives of embedded systems.
0 Comments
Leave a Reply. |