A protocol processor is a programmable processor specifically designed to deal efficiently with protocols. The challenge in designing protocol processors is finding an architecture that is a good compromise between a general purpose processor and a custom, protocol-specific processor. We describe a methodology in which we design both a processor and a program for a network processing application. Our design flow is based on object oriented techniques and targets a TTA processor architecture. TTA is a special processor architecture whose instruction set can easily be tailored. It consists of a number of functional units that are implemented in hardware. One of the tasks in our methods is to identify such functional units. We explain the design flow steps with an IPv6 router implementation. Keywords: protocol processor, internet protocol version 6, IPv6 routing, UML, design flow, transport triggered architecture

Introduction The vast majority of embedded systems are control-dominated systems and traditionally designers specify them using only a state-oriented model, such as FSMs. However, real-time embedded systems are getting quite complex, which implies that a different approach is necessary. The system specification has to fulfil several requirements, namely support for concurrency, timing constraints, hierarchy, data and control flow, and distributed computations. Thus, for modelling more aspects of the systems (namely, data and function), it is important to consider genuine multiple-view models. There is also absolutely no doubt that IT organisations can improve efficiency and productivity if they share the same notation. In this context, the authors recommend the utilisation of some UML views to specify embedded systems, because it is a notation that covers the most relevant modelling aspects of systems and it is an OMG standard. Figure 1. The HIDRO lines. This paper

This paper presents a new Petri net (PN) meta-model, called shobi-PN v2.0, that can be used to specify the dynamic behaviour of concurrent systems, using object-oriented modelling concepts together with a generalised arc set capable of coping with the complexity of the current embedded systems. This new Petri net meta-model can also be used to support a component-based development approach in the design of generic and parametrisable control-oriented software components for embedded systems. 1.

The main aim of this paper is to present how the Unified Modeling Language (UML) can be used as the notation to specify the requirements of an embedded system. By using a relatively small, but real, system (a supervision application) as a running example, the paper illustrates the design flow that can be followed during the analysis phase of complex control applications. To assure the continuous mapping of the models, the authors propose some guidelines to transform the use case diagrams into a single object diagram, which is the main diagram for the next development phases (design and implementation). The Java programming language is used for developing a system's prototype, to allow the system's validation by the customers.

The Mo de Drive Approach (MDA) as supp orte bythe ObjeW Manage me t Group (OMG)deG)A. e the structural reuctural ts of aneWxxW6AOxW discipline whec mode.K insteW ofsource co de comprise the primary artifact. Mo de Drive nEngineOx.G (MDE), asoutline by StuartKe t, brings forththe dynamic asp ofe.PfiWzAOxGx wheP pro ceAadhezP.z and rigorouscommitme t to analysisare eesis important. As such, MDE has abroade scope than MDA. We discuss our position on MDE and its re quire6K ts on tools and te hnology,e speAKKGP consideOWfi the dynamics of a modeqWW.WA software de e.666 tmeGP d. We de.P6AOWW6 our approach with aneAqfi6z ofthe spe.fi6.fiAOW of an IPv6route targe6q to a customize proceAq6z architeW6WAO Keywords: MDA, Mode Drive EnginefiKAOK Mo de Transformation TUCS Laboratory Embe.qG Systeq and Software Construction Labs. 1

This paper presents a model-based approach that combines the data-flow and object-oriented computing paradigms to model embedded systems. The rationale behind the approach is that both views are important for modelling purposes in embedded systems environments, and thus a combined and integrated usage is not only useful, but also fundamental for developing complex systems. We also show that by using models we were able to implement automated transformations between different views of the system under design. We exemplify the approach with an IPv6 router case study. 1.

Abstract. In this paper, a methodology for integrating heterogeneous industrial information systems is presented. The methodology is strongly based on the extensive reuse of already-made components and is conceptually divided in three levels, one for each kind of designer that is typically involved in this type of projects. To accomplish a better integration of the activities and tools necessary to develop industrial information systems with the proposed methodology, three appropriate organizational configurations are adopted. 1

This paper presents a constructive algorithm for memory-aware task assignment and scheduling which is a part of the prototype system MATAS. The algorithm is well suited for image and video processing applications which have hard memory constraints as well as constraints on cost, execution time, and resource usage. Our algorithm takes into account code and data memory constraints together with the other constraints. It can create pipelined implementations. The algorithm finds a task assignment, a schedule, and data and code memory placement in memory. Infeasible solutions caused by memory fragmentation are avoided. The experiments show that our memory-aware algorithm reduces memory utilization comparing to greedy scheduling algorithm which has time minimization objective. Moreover, memory-aware algorithm is able to find task assignment and schedule when time minimization algorithm fails. MATAS can create pipelined implementations, therefore the design throughput is increased.

Abstract. The main aim of this paper is to present how to refine software logical architectures by application of a recursive model-based transformation approach called 4SRS (four step rule set). It is essentially based on the mapping of UML use case diagrams into UML object diagrams. The technique is based on a sequence of steps that are inscribed in a tabular representation that is used to derive the software architecture for a focused part of the global system. 1

Abstract: This paper presents a demonstration case on the successive application of a model-based technique to assist on the refinement of software logical architectures. The technique is essentially based on the transformation of use cases into object diagrams. The applicability of the technique is illustrated by presenting some results from a mobile application. For mobile software, the definition of the underlying service-oriented architecture must consider as user requirements the services themselves, the mobile operators entry points and the final clients interfaces, and use them to characterize the platform. Within the presented demonstration case, the specification of one service of the mobile application was obtained by successively applying the technique. 1.