Design and Implementation of a
Pluggable Fault Tolerant CORBA Infrastructure
W.Zhao,L.E.Moser and P.M.Melliar-Smith
Department of Electrical and Computer Engineering
University of California,Santa Barbara,CA93106
wenbing@https://www.doczj.com/doc/e114463811.html,,moser@https://www.doczj.com/doc/e114463811.html,,pmms@https://www.doczj.com/doc/e114463811.html,
Abstract
In this paper we present the design and implementation of a Pluggable Fault Tolerant CORBA Infrastructure that provides fault tolerance for CORBA applications by uti-lizing the pluggable protocols framework that is available for most CORBA ORBs.Our approach does not require modi?cation to the CORBA ORB,and requires only mini-mal modi?cations to the application.Moreover,it avoids the dif?culty of retrieving and assigning the ORB state, by incorporating the fault tolerance mechanisms into the ORB.The Pluggable Fault Tolerant CORBA Infrastructure achieves performance that is similar to,or better than,that of other Fault Tolerant CORBA systems,while providing strong replica consistency.
1Introduction
Several different approaches have been developed to pro-vide fault tolerance for distributed applications based on the Common Object Request Broker Architecture(CORBA) standard[14]promoted by the Object Management Group (OMG).Early research efforts to enhance CORBA with fault tolerance took an integration approach,with the fault tolerance mechanisms implemented inside the ORB[2,6]. That approach requires extensive modi?cations to both the ORB core and the applications and,therefore,is regarded as an intrusive https://www.doczj.com/doc/e114463811.html,ter research efforts adopted a non-intrusive approach that is either service-based[4,7,12] with fault tolerance provided through service objects above the ORB,or interception-based[9,10,11]with the fault tol-erance mechanisms implemented underneath the ORB(in a different address space).
In1998the OMG issued a Request For Proposals for Fault Tolerant CORBA(FT CORBA)with the aim of stan-This paper was published in Proceedings of the International Parallel and Distributed Processing Symposium,Fort Lauderdale,FL,April2002.dardizing these efforts.The speci?cation of FT CORBA was?nalized by the OMG in April2000[13].FT CORBA de?nes a set of service interfaces and underlying mecha-nisms that provide fault tolerance for CORBA applications through object replication,fault detection and noti?cation, and logging and recovery.The FT CORBA standard man-dates strong replica consistency for the replicated applica-tion objects.
To maintain strong replica consistency,some degree of integration of the fault tolerance mechanisms and the ORB is necessary to retrieve and assign the ORB state properly during the recovery of a replica and the transfer of state from a primary replica to the backup replicas[9,10,11]. In this paper,we present a new approach that incorporates the fault tolerance mechanisms into the ORB,while provid-ing maximum transparency to both the ORB and the appli-cation.It uses the Pluggable Protocols Framework[5]that comes with many modern CORBA ORBs.
The Pluggable Protocols Framework(PPF)separates the messaging and network protocols from other parts of the ORB core and from the application objects.The PPF allows the network protocol to be replaced,and may also allow the messaging protocol to be replaced.Thus,the PPF makes it possible to develop CORBA applications for,and to deploy them in,environments for which the standard IIOP proto-col is not appropriate[5].The PPF also provides CORBA applications with improved quality of service by enabling the use of customized protocols that are tailored to those applications and their environments.
In this paper we present the design and implementation of a FT CORBA compliant infrastructure,the Pluggable FT CORBA Infrastructure,that is based on the PPF.We replace only the network protocol and not the messaging protocol. The Pluggable FT CORBA Infrastructure achieves perfor-mance that is similar to,or better than,that of existing FT CORBA systems[12,19],while providing strong replica consistency and supporting a wider range of applications.
Multicast Messages
Figure1.The Pluggable FT CORBA Infrastructure.
2The Pluggable Protocols Framework The Pluggable Protocols Framework(PPF)is now pro-vided by many CORBA ORBs,including Orbix2000from Iona,ORBacus from Object Oriented Concepts,VisiBroker (real-time version)from Highlander Engineering,ORBex-press from Objective Interface Systems,TAO from Wash-ington University,St.Louis,and e*ORB from Vertel,just to name a few.Although the PPFs differ slightly from one ORB to another,most of them are based on similar reactor-based design patterns[17].
The PPF provides a set of abstract base classes for the ORB-level transport interfaces.For example, the ORB-acus PPF provides Connector Factory, Connector,Transport,Acceptor Factory and Acceptor interfaces).The protocol plug-in must inherit from these classes in order to provide a concrete implemen-tation for a speci?c protocol.The PPF provides concrete classes for the Factory Registry interfaces.Concrete implementations of the Factory classes register with the cor-responding Factory Registries in order to be loaded into the ORB runtime.
3Fault Tolerant CORBA
The Fault Tolerant(FT)CORBA standard de?nes inter-faces and mechanisms for object replication,fault detection and noti?cation,and logging and recovery.
The FT CORBA standard de?nes a Replication Manager that handles the creation,deletion and replication of appli-cation objects.Although each replica of an object has an individual object reference,the Replication Manager fabri-cates an Interoperable Object Group Reference(IOGR)for the replicated server object(object group)that clients use to contact that replicated server.The IOGR contains a pro-?le for each of the replicas in the server object group.The Replication Manager inherits several interfaces for the pur-pose of fault tolerance property management,and replica group management.
The FT CORBA standard also speci?es interfaces and mechanisms for hierarchical fault monitoring and noti?ca-tion at the object,type and/or location(e.g.,host)level.To enable the health of its replica to be checked,an application object must inherit the FT::PullMonitorable inter-face,which allows the object to be pinged.
To enable the recovery of a replica that has failed,the FT CORBA standard de?nes interfaces for checkpointing that are inherited by each application object and that are used to retrieve and assign an application object’s state.To allow its state to be transferred in this manner,an application object must inherit the FT::Checkpointable interface.
4The Pluggable FT CORBA Infrastructure The Pluggable Fault Tolerant(FT)CORBA Infrastruc-ture is shown in Figure1.On the server-side,fault tolerance is provided by the FT protocol plug-in(described in Section 4.1),the Totem group communication system[8]and the Replication Manager,Fault Noti?er and Fault Detectors (described in Section3).The Replication Manager and the Fault Noti?er are implemented as CORBA objects running as separate processes,and are replicated using the active replication style.The Fault Detector that detects faults at the object level is implemented as a component of the FT protocol plug-in.
To accommodate the FT protocol plugged into the ORB, we have rewritten the process group layer of Totem[8].In addition to providing the reliable totally-ordered multicast
https://www.doczj.com/doc/e114463811.html,ponents of the server-side FT
protocol plug-in.
service,Totem also serves as a process-level and host-level fault detector.A fault report is created by Totem once it has detected a fault,and then delivers the report to the Fault Noti?er.Totem also conveys the fault reports generated by the object-level fault detector to the Fault Noti?er.
Unreplicated clients connect to the replicated servers through passively replicated gateways that provide access into the fault-tolerance domain that contains the replicated servers.The client-side failover mechanisms speci?ed by the FT CORBA standard are also implemented as a proto-col plug-in.
4.1Server-Side FT Protocol Plug-in
The server-side Fault Tolerant(FT)protocol is plugged into the ORB using the pluggable protocols framework.As shown in Figure2,the server-side FT protocol plug-in con-sists of the following components:FT Adaptor,Duplicate Filter,Recovery Manager,Property Manager,State Man-ager,Operation Scheduler and FT ORB Transport.
4.1.1FT Adaptor
The FT Adaptor handles the connection to Totem,passes incoming messages to the Duplicate Filter,and routes out-going messages to Totem.Currently,a Unix socket is used to connect the FT Adaptor and Totem.
The FT Adaptor attaches a FT protocol header to all mes-sages.Totem uses the FT protocol header information to de-multiplex the messages that are received and to deliver them to the correct FT Adaptor.The FT protocol header also con-tains information that is needed to detect and suppress du-plicate invocations and responses,as explained later.
The FT Adaptor sends and receives two different types of messages:(1)the GIOP messages that the CORBA ap-plication objects use,and(2)the control messages that the FT Adaptor uses.An example of such a control message is the disconnection indication message that the FT Adap-tor sends,when the ORB destroys the Transport instance, to ensure that the peer Transport instance is shutdown and garbage collected properly.
4.1.2FT ORB Transport
The FT ORB Transport component implements the mandatory interfaces speci?ed in the PPF for each ORB.For ORBacus,it includes the implementation of the Connector Factory,Connector,Transport, Acceptor Factory and Acceptor interfaces.The Pluggable FT CORBA Infrastructure retains the GIOP mes-saging protocol and changes the transport protocol.Instead of using TCP/IP,all of the transport instances share the same connection from the FT Adaptor to Totem.Synchroniza-tion mechanisms are built into the component based on the pthread library interfaces.
The instances of the concrete classes in the FT ORB Transport component,including the Connector, Transport and Acceptor,are owned by the ORB run-time.The Transport instances may be created either di-rectly by the ORB runtime,or by the FT protocol during the setting of the ORB-level state in which case they are subse-quently handed over to the ORB runtime.The FT Adaptor registers callbacks with these Transport instances to re-ceive noti?cation of the creation and deletion events.For these creation and deletion events,the FT Adaptor sends connection and disconnection indication control messages so that the FT protocol plug-in can take appropriate actions.
Each Transport instance has a de?nite role as a server or a client during its lifetime.A client Transport in-stance is used by a Connector instance to send request messages to a remote server and to receive the correspond-ing reply messages.A server Transport instance is used by an Acceptor instance to receive request messages from a remote client and to send the corresponding reply messages.
Each Transport instance is assigned a unique trans-port id that consists of a4-tuple(source group id,destination group id,connection sequence number,role)by the FT protocol.The?rst two identi?ers represent the identities of the sending and receiving groups,respectively.The connection sequence number n,which is determined by the client process that initiates the connection,indicates that this Transport instance is created for the n th connection requested by the particular client.The Transport instance on the
server-side,that is created on a connection request from a client,uses the same connection sequence number as that used by the corresponding Transport instance on the client-side.
4.1.3Duplicate Filter
The Duplicate Filter detects and suppresses duplicate mes-sages,and passes only non-duplicate messages to the Re-covery Manager.
For the purpose of duplicate detection,each Transport instance contains a message filter id,which counts the number of messages sent through a connection.In the FT protocol,duplicate incoming mes-sages can occur only if they arrive for the same Transport instance(identi?ed by the transport id).The Duplicate Filter stores the transport ids that it has seen,and also the last message?lter id for each transport id(this suf?ces because the message?lter id increases monotonically).The Duplicate Filter checks the transport id and the message ?lter id in the message header against its record.A message is deemed to be a duplicate if the Duplicate Filter?nds a record with the same transport id but with a higher(or identical)message?lter id.The Duplicate Filter drops a duplicate message once it has detected that the message is a duplicate.
For outgoing message duplicate detection,the Pluggable FT Infrastructure exploits the fact that the delivery of invo-cations on each Transport instance is serialized,regardless of the degree of concurrency that the ORB uses.For an outgoing reply message,if the Duplicate Filter?nds that a new invocation has arrived for the Transport instance,it drops the outgoing reply message.For an outgoing(nested) request message,if the Duplicate Filter?nds that the reply for the request message has already arrived,it drops the re-quest message.
4.1.4Recovery Manager
The Recovery Manager implements the Logging and Re-covery Mechanisms.The log used by the Recovery Man-ager consists of two message queues,one for request mes-sages and the other for reply messages.Non-duplicate re-quest messages are stored in a total order in the request queue,and non-duplicate reply messages are stored in a total order in the reply queue.The log is used to guar-antee the local single thread of control needed to achieve strong replica consistency,and it is also used for recovery. If only one queue were used,the request and reply messages would be interleaved and a linear search would be required to?nd and deliver a request or reply message to the ORB Transport.By using two separate message queues,one for requests and one for replies,the Operation Scheduler can retrieve a message simply from the top of each queue and deliver it to the ORB Transport.
During recovery,the Recovery Manager retrieves both the application-level state and the ORB-level state from the State Manager,fabricates a single message that con-tains both kinds of state,and multicasts the message using Totem.The Recovery Manager at a backup replica(for pas-sive replication)or a newly started replica(for passive,ac-tive or semi-active replication)forwards the aggregate state transfer message to the State Manager.The State Manager then decomposes the state transfer message,recreates the FT Transport instances,if necessary,sets the message?lter id for each Transport instance,and applies the application-level state.Once the application-level state and the ORB-level state are set at the recovering replica,the Recovery Manager replays the queued messages that it received after it had initiated the state transfer.
4.1.5Property Manager
The Property Manager stores the fault tolerance properties, such as the replication style,the fault monitoring interval, and the checkpoint interval,for each object replica in the process.It also stores the information as to whether or not the local replica is the primary.
4.1.6State Manager
The State Manager implements an interface with a method that allows the application to register its factory object.This factory object implements the FT::GenericFactory interface.The State Manager delegates the cre-ation/deletion request from the Replication Manager to the application factory object.It keeps track of the object ids and the object references for the application objects that have been created and not yet deleted.The State Man-ager retrieves the application-level state by invoking the FT::Checkpointable::get state()method of the application objects(using the stored object references). For the FT::Checkpointable::set state() method,the State Manager?rst creates new application ob-jects in the recovering process using the application factory object(the object ids are used for this purpose),if necessary, and then assigns the application-level state to each object by invoking the FT::Checkpointable::set state() method.In addition,the State Manager is responsible for collecting the ORB-level state,most of which is stored in the ORB Transport component that is part of the FT protocol plug-in.
4.1.7Operation Scheduler
The Operation Scheduler retrieves the request and reply messages from the respective message queues managed by
the Recovery Manager.Except in some special cases where optimization is possible,the Operation Scheduler enforces a single-thread of control by delivering a new request mes-sage to the Transport component only after the process has no pending request unserviced.
4.1.8Object-Level Fault Detector
The object-level fault detector is implemented as a C++ object.CORBA application objects that are monitored must inherit the FT::PullMonitorable interface.The object-level fault detector uses a pool of threads to pull monitor each registered CORBA object.Based on the user-speci?ed Fault Monitoring Interval property,the FT::PullMonitorable::is alive()method is in-voked periodically.If the invocation does not return within a speci?ed timeout period,or if it returns CORBA::FALSE, the Fault Detector determines that the monitored object is faulty.
The object-level fault detector is,in turn,monitored by Totem,which schedules special events periodically on each node in a deterministic manner.Whenever such a special event occurs,Totem sends a fault monitoring control mes-sage to the FT protocol plug-in.The object-level fault de-tector responds to this control message immediately,if it is alive.If the Fault Detector determines that a monitored CORBA application object is faulty,it indicates this fact in its response to the control message.If Totem receives a re-sponse with a faulty indication,or if it does not receive a response from the object-level fault detector within a spec-i?ed timeout period,it shuts down the faulty process and fabricates a fault report to the Fault Noti?https://www.doczj.com/doc/e114463811.html,ually,one faulty object will affect a number of objects in the same process.Therefore,it is practical to shutdown the entire process when a faulty object is detected.
The Fault Monitoring Granularity property,de?ned by the FT CORBA standard,supports hierarchical fault detec-tion by allowing the user to select object,location or loca-tion and type as the value of that property.The location value restricts the monitoring to a particular representative object at the given location(process,processor,network, etc),and the location and type value restricts the monitor-ing further to a particular representative object at the given location of the given type.Thus,regardless of the value of the Fault Monitoring Granularity,the object-level fault de-tector can be used.
4.2FT Protocol Plug-in for Unreplicated Clients
The client-side fault tolerance mechanisms required by the FT CORBA standard can be implemented using the PPF for the ORBs that do not yet provide such support.The architecture of the client-side FT protocol plug-in is shown in Figure3.
https://www.doczj.com/doc/e114463811.html,ponents of the client-side FT
protocol plug-in.
The FT Adaptor makes connections and communicates directly with the primary gateway of the fault tolerance do-main using TCP/IP.The FT ORB Transport component uses the interfaces provided by the Message Handler to send and receive GIOP messages.The connections to the servers are separated from the FT ORB Transport component so that it is not aware of any lost connections that occur.The Mes-sage Handler inserts a fault tolerance service context into each outgoing message and delivers incoming replies to the FT ORB Transport.
The application must register the server Interoperable Object Group Reference(IOGR)with the Gateway Pro?le Manager,because the ORB itself is likely to keep only the ?rst IIOP pro?le contained in the IOGR.The Failover Man-ager runs on a separate thread in order to heartbeat the pri-mary gateway.If the Failover Manager determines that the primary gateway has crashed,it instructs the FT Adaptor to shutdown the current connection and to reconnect to the new primary gateway.The new primary gateway is found by cycling through the pro?les in the IOGR that the Gate-way Pro?le Manager maintains.No exception is thrown back to the application object unless all pro?les in the IOGR have been tried and have failed.
4.3Optimization and Practical Considerations 4.3.1Semi-Active Replication Style
For active replication,duplicate messages in the network traf?c are one of the major sources of overhead.
Duplicate detection at the sender is necessarily best-effort,because of the asynchronous nature of the replicas’concurrent sending of the same messages.Only the Dupli-cate Filter at the receiver can be guaranteed to capture and suppress duplicates.
Figure4.Interactions of object groups using
the semi-active replication style.
Duplicate messages have the following negative effects: (1)they compete for network bandwidth,(2)they incur additional processing and transmission for reliable totally-ordered message delivery,and(3)they incur extra process-ing for duplicate?ltering at the receiver.The negative ef-fects of duplicate messages are more pronounced for large messages and for high replication degrees.
To address these negative effects,we advocate the use of semi-active replication,to eliminate duplicate messages under fault-free conditions and to provide fast recovery in the event of a fault.As shown in Figure4for the semi-active replication style,all replicas in each object group receive requests and replies from the other object groups with which they are interacting,but only one replica in each group(the primary replica)issues outgoing messages(replies or nested invocations).All outgoing messages from the secondary replicas are suppressed within the ORB.
In the semi-active replication style,
All replicas within an object group process incom-ing messages in the same order;therefore,after each message has been processed,the states of the repli-cas within the group are consistent.Moreover,under fault-free conditions,all outgoing messages from the secondary replicas are suppressed.
State transfer from the primary replica to the secondary replicas is not necessary.If the primary fails,one of the secondary replicas is elected as the new primary.
The new primary starts by sending the last logged out-going message.This works,by default,because the FT protocol plug-in enforces a single logical thread of control.
In general,semi-active replication achieves better per-formance in terms of round-trip latency than
–Active replication,because it eliminates dupli-
cate messages
–Passive replication,because it eliminates peri-
odic state transfer messages from the primary
replica to the backup replicas.
With semi-active replication,the failure of the primary replica results in a brief hiatus in service.The factors that contribute to this delay include the fault detection time and the time to multicast a short control message.
The control message informs the surviving replicas of the failure of the primary and the decision as to which replica is to serve as the new primary.In general,for semi-active replication,the delay is shorter than that for passive replication because,in passive replication, the new primary must process the logged invocations after the last checkpoint.
4.3.2Flow Control for Active Replication
With active replication,?ow control problems can arise, even if there are only slight variations in the processing speeds of the processors hosting the replicas,if those pro-cessors are loaded heavily and running close to their maxi-mum processing capacities.In such a case,the progress of the clients is determined by the fastest server replica;as a consequence,the arrival rate of the incoming messages will exceed the processing capacity of the slow replicas.The message queues(i.e.,log)on the slow replicas will?ll up due to either a pre-set limit on the number of messages al-lowed or a limit imposed by the?nite physical memory of the processor.Eventually,the slow replicas will stop func-tioning,which defeats the purpose of active replication.
To avoid this backlog buildup problem at the slow repli-cas,the Pluggable FT CORBA Infrastructure employs sev-eral?ow control mechanisms.Each FT protocol plug-in maintains two thresholds.The Recovery Manager checks the number of messages in the log against these two thresh-olds.If the Recovery Manager?nds that the number of mes-sages in the log exceeds the upper threshold,it asks the FT Adaptor to multicast a control message to the other replicas in the group.Upon receiving this control message,the FT protocol plug-in checks if the number of messages in the log is below the lower threshold.If so,the FT Adaptor slows down the rate of handling new messages until the number of messages in the log rises above the lower threshold.
Note that these?ow control mechanisms are best-effort, in that the mechanisms cannot eliminate the over?ow of the log at the slow replicas in all circumstances.The reason is that the FT protocol plug-in supporting the fastest replica is not aware of the situation and cannot take any action until it receives the control message.In the meantime,the incom-ing messages might have already caused the log over?ow at the slow replicas.
5Performance
We have implemented a prototype of the Pluggable FT CORBA Infrastructure using ORBacus4.0.4[15]and e*ORB2.1[18]and the C++programming language.In this paper we provide experimental results for the pluggable protocol infrastructure based on ORBacus.
The experiments were performed on six Pentium III PCs over a100Mbps local-area network.Each PC is equipped with a1GHz CPU,256MB of RAM,and runs the Mandrake Linux7.2operating system.
A simple client/server application was developed for the experiments.The server contains a method that takes a se-quence of octet and returns an identical sequence of octet to the client,so that the request message is similar in length to the reply message,thus re?ecting the round-trip nature of the messages.
For the active and semi-active replication styles,we fo-cused on two performance measures:(1)runtime overhead, and(2)fault detection and recovery time.We investigated the runtime overhead as a function of payload length and replication degree.We measured the fault detection time for each process crash fault,the recovery time of loading a new replica as a function of state size,and the recovery time of the primary replica fault for the semi-active replica-tion style.
5.1Round-Trip Latency
For the overhead measurements,we ran one or more un-replicated clients on one PC and replicated servers on the other PCs,each on a distinct PC.The average latency for two-way invocations was read at the client-side.
5.1.1Message Length Dependency
The FT protocol plug-in is layered underneath the GIOP messaging protocol and,therefore,does not parse or inter-pret the GIOP message body.Consequently,the overhead of the FT protocol depends on the lengths of the messages, rather than on the complexity of the data types or the signa-tures of the methods that are invoked across the network.
Figure5shows the average latency for synchronous re-mote invocations with various payloads for a three-way replicated server using both the active and semi-active repli-cation styles,and also for the unreplicated client/server case.
The overhead of the Pluggable FT CORBA Infrastruc-ture is due primarily to the following aspects of active repli-cation:
The Totem reliable totally-ordered multicast protocol involves signi?cant CPU usage(10%+)and takes ad-ditional network bandwidth.In our experimental con-
1
2
3
4
5
6
7
8
0246810 R
o
u
n
d
T
r
i
p
L
a
t
e
n
c
y
i
n
m
i
l
i
s
e
c
o
n
d
Payload Length in kilobytes
Active Replication
Semi-Active Replication
No Replication
Figure5.Round-trip latency as a function of payload length.
?guration,the network bandwidth taken by the rotating token of Totem is about4Mbps.
With active replication on identical processors,the du-plicate?ltering mechanisms cannot effectively sup-press duplicate outgoing messages.Therefore,most of the duplicate messages show up in the Totem network traf?c,wasting the processing power and the network bandwidth.
As Figure5shows,semi-active replication exhibits a sig-ni?cant performance gain over active replication,particu-larly for large messages.
5.1.2Replication Degree Dependency
Figure6shows the round-trip latencies for two different payload sizes as a function of replication degree for the ac-tive and semi-active replication styles.
The Totem single-ring protocol uses a token rotating around a logical ring to order messages[8].The ring size (i.e.,the number of processors running Totem)increases with the degree of replication,given that the replicas run on different processors.Therefore,as the degree of repli-cation increases,the latency overhead increases because(1) the token rotation time increases,(2)the collective process-ing time at a node increases,and(3)for active replication, the number of duplicate messages in the network that must be delivered reliably and in order increases.
As Figure6shows,by eliminating the duplicate mes-sages in the network for semi-active replication,the latency is reduced signi?cantly over active replication,especially for invocations with large payload and for a high degree of replication.
0.5
1
1.5
2R o u n d T r i p L a t e n c y i n m i l i s e c o n d s
Replication Degree
(a)
1
2
3
4
5
12345678
R o u n d T r i p L a t e n c y i n m i l i s e c o n d s
Replication Degree
(b)
1
2
3
4
5
Figure 6.Round-trip latency as a function of replication degree for a payload size of (a)1KByte,and (b)8KByte.The dark shaded bars represent active replication,and the light shaded bars represent semi-active replication.
5.2Fault Detection and Recovery Time
We also measured the time for Totem to detect a process crash fault.In the experiment,we select one of the pro-cesses on the same node as the victim.We record a start time before we send a kill signal to the process,and an end time when the noti?cation regarding the lost socket event is received from its reactor.The process crash fault detec-tion time is the difference between the end time and the start time.On average,the process crash fault detection time is about 3ms.
Next,we measured the recovery time for adding a new replica into an existing group.To obtain a clear picture of the cost of recovery at various stages,we measured the re-covery time using a number of metrics:
Application.The time interval between the start of the
application replica as indicated by the start of the main()function and the completion of the set state()method invocation.This time is clos-est to the time perceived by the end user (only the time spent in loading the application is not counted).This time includes the cost of initializing the ORB and the application.Totem.The time interval between the detection of the join
of a new replica and the completion of writing the SET STATE protocol message to the replica (the re-ply of the set state()invocation is not written to Totem).This metric best re?ects the actual cost of the Pluggable FT Infrastructure for application recovery.It does not include the cost of initializing the ORB or the application.SET STATE Transmission Time.The time interval be-tween the receiving of the GET STATE protocol mes-
sage and the completion of the set state()method invocation on the application object,measured at the application process.Assuming that the exist-ing replicas and the newly started replica receives the GET STATE protocol message almost at the same time,this time approximates the cost of retrieving and setting the application-level state,the ORB-level state and the infrastructure-level state,and the transmission and delivery of the SET STATE message.In our ex-periments,the cost of retrieving and setting the differ-ent levels of state is negligible;therefore,the cost of the SET STATE message transmission dominates.The results of the recovery time measurements are shown in Figure 7.As expected,the recovery time us-ing the ?rst metric (application)is signi?cantly larger than the time measured for the other two metrics (Totem and SET STATE Transmission Time).The recovery time for the second and third metrics show a nice linear dependency on the application-state size.For an application with a state as large as 100KByte (the ORB-level and infrastructure-level state is negligible compared with an application state of this size),the recovery time is about 100ms,40ms and 10ms,for the three metrics respectively.
The time needed to recover from the failure of the pri-mary replica for the semi-active replication style is also measured.To avoid the need for clock synchronization,both the primary replica and a secondary replica (to be pro-moted to primary)are run on the same processor.We send a signal to the primary replica.The primary replica then records a time and exits.The loss of the primary replica is detected and the secondary replica is promoted to be the new primary replica.The time at which the secondary replica is promoted is then recorded.The difference be-tween the two recorded times is regarded as the recovery
20
40
60
80
100
120
R e c o v e r y T i m e i n m i l i s e c o n d
State Size in kilobytes
Figure 7.Recovery time as a function of state size using different metrics.
time from the primary replica fault.This recovery time in-creases with the replication degree and the Totem ring size.In the case of four processors,the recovery time is approxi-mately 10ms.
6Related Work
Three Fault Tolerant CORBA systems that implement all or part of the FT CORBA standard are DOORS [12],Eter-nal [9,10,11]and IRL [7].All three systems use a non-intrusive approach.On top of an interception-based fault tolerance infrastructure,Eternal implements the Replica-tion Manager,the Fault Detector and the Fault Noti?er as CORBA objects to provide fault tolerance services to ap-plication objects.By using CORBA’s portable interceptors,IRL embeds a set of CORBA objects that implement mech-anisms for transparent reinvocation and redirection,and for duplicate detection and suppression,into the application ad-dress space.
Although the Pluggable FT CORBA Infrastructure de-scribed in this paper bears some similarities to the intercep-tion approach used by Eternal,in that messages are routed through a group communication system,it is more similar to the integration approach because the fault tolerance mecha-nisms are incorporated into the ORB.Of course,some man-agement components (namely,the Replication Manager and the Fault Noti?er)are implemented as CORBA services,which the FT CORBA standard requires.
Embedding the fault tolerance mechanisms into the ORB facilitates the transfer of ORB-level state,as well as application-level state,in an accurate and ef?cient manner.This approach also provides the opportunity for improved quality of service for the applications by allowing differ-ent protocols to be plugged into the ORB.To retrieve and
assign the ORB-level state properly,the interception-based and the service-based FT CORBA systems involve propri-etary interfaces to be supplied by the ORB vendors.
Nevertheless,the Pluggable FT CORBA Infrastructure differs from the integration-based systems in several re-spects:
The Pluggable FT CORBA Infrastructure enters the ORB address space by using the PPF provided by the ORB,with no modi?cation to the ORB core.The integration-based systems require extensive modi?ca-tions to the ORB to accommodate the fault tolerance mechanisms.
Because the PPFs offered by different CORBA ORBs follow similar object-oriented design patterns,the Pluggable FT CORBA Infrastructure can be easily ported from one ORB to another,whereas integration-based systems must be tightly integrated into a partic-ular ORB.
The Pluggable FT CORBA Infrastructure requires only minimal modi?cation to the application program for loading the FT protocol plug-in if the PPF (e.g.,ORBacus 4.0or e*ORB)allows the user to select the particular protocol by invoking an API within main(),or no modi?cation at all (other than those required by the FT CORBA speci?cation)if the PPF (e.g.,ORBacus 4.1)allows the ORB to load the par-ticular protocol at runtime.Like the interception-and service-based approaches,the Pluggable FT CORBA Infrastructure provides fault tolerance to applications in a transparent manner,whereas for integration-based systems the applications program fault tolerance di-rectly using their own interfaces.
A performance comparison between the Pluggable FT CORBA Infrastructure and other Fault Tolerant CORBA systems is dif?cult because of platform differences for the measurements and/or the lack of data for those systems.Because a well-engineered group communication system,such as Totem,has better performance than multiple point-to-point TCP/IP communications for the same group size,the Pluggable FT CORBA Infrastructure outperforms exist-ing service-based Fault Tolerant CORBA systems in terms of run-time overhead.Moreover,the Pluggable FT CORBA Infrastructure,based on Totem,achieves performance that is similar to,or better than,that of the interception-based Eternal system [19]for active replication.
Delta-4[16]introduced semi-active replication,which has since been used in several other systems [1,3].These systems differ from the Pluggable FT CORBA Infrastruc-ture in that they use semi-active replication for handling non-determinism,rather than for performance considera-tions.By using semi-active replication,the Pluggable FT
CORBA Infrastructure and other fault-tolerant systems that are based on group communication can achieve better per-formance than if they use active replication,because dupli-cate messages that might otherwise appear on the network are eliminated.Semi-active replication also provides faster recovery from faults than passive replication.
7Conclusion
We have described the design,implementation and per-formance of the Pluggable FT CORBA Infrastructure,a fault-tolerant CORBA system based on the pluggable proto-cols framework.Applications can achieve higher reliability and availability by plugging in the FT protocol with mini-mal modi?cations to their existing code.The Pluggable FT CORBA Infrastructure has the advantages of both the intru-sive(integration-based)and non-intrusive(serviced-based and interception-based)approaches,while overcoming the drawbacks of each.It achieves performance that is simi-lar to,or better than,that of existing FT CORBA systems, while providing strong replica consistency and supporting a wider range of applications.
References
[1]S.Bestaoui,A.M.Deplanche,and Y.Trinquet.Redundancy
management in the SCEPTRE2real-time executive.In Pro-ceedings of the IEEE International Conference on Systems, Man and Cybernetics,volume1,pages373–378,Le Tou-quet,France,October1993.
[2]M.Cukier,J.Ren,C.Sabnis,W.H.Sanders,D.E.Bakken,
M.E.Berman,D.A.Karr,and R.Schantz.AQuA:An adaptive architecture that provides dependable distributed objects.In Proceedings of the IEEE17th Symposium on Re-liable Distributed Systems,pages245–253,West Lafayette, IN,October1998.
[3] A.M.Deplanche,P.Y.Theaudiere,and Y.Trinquet.
Implementing a semi-active replication strategy in Cho-rus/ClassiX,a distributed real-time executive.In Proceed-ings of the18th IEEE Symposium on Reliable Distributed Systems,pages90–101,Lausanne,Switzerland,October 1999.
[4]P.Felber,R.Guerraoui,and A.Schiper.The implementation
of a CORBA object group service.Theory and Practice of Object Systems,4(2):93–105,1998.
[5] F.Kuhns,C.O’Ryan,D.C.Schmidt,O.Othman,and J.Par-
sons.The design and performance of a Pluggable Protocols Framework for Object Request Broker middleware.In Pro-ceedings of the IFIP Sixth International Workshop on Pro-tocols For High-Speed Networks,pages81–98,Salem,MA, August1999.
[6]https://www.doczj.com/doc/e114463811.html,ndis and S.Maffeis.Building reliable distributed sys-
tems with CORBA.Theory and Practice of Object Systems, 3(1):31–43,1997.
[7] C.Marchetti,M.Mecella,A.Virgillito,and R.Baldoni.
An interoperable replication logic for CORBA systems.In Proceedings of the International Symposium on Distributed Objects and Applications,pages7–16,Antwerp,Belgium, September2000.
[8]L.E.Moser,P.M.Melliar-Smith,D.A.Agarwal,R.K.
Budhia,and C.A.Lingley-Papadopoulos.Totem:A fault-tolerant multicast group communication https://www.doczj.com/doc/e114463811.html,muni-cations of the ACM,39(4):54–63,April1996.
[9]L.E.Moser,P.M.Melliar-Smith,and P.Narasimhan.Con-
sistent object replication in the Eternal system.Theory and Practice of Object Systems,4(2):81–92,1998.
[10]P.Narasimhan.Transparent Fault Tolerance for CORBA.
PhD thesis,Department of Electrical and Computer Engi-neering,University of California,Santa Barbara,December 1999.
[11]P.Narasimhan,L. E.Moser,and P.M.Melliar-Smith.
Strong replica consistency for fault-tolerant CORBA appli-cations.In Proceedings of the IEEE6th Workshop on Object-Oriented Real-Time Dependable Systems,Rome,Italy,Jan-uary2001.
[12] B.Natarajan,A.Gokhale,S.Yajnik,and D.C.Schmidt.
DOORS:Towards high-performance fault-tolerant CORBA.
In Proceedings of the International Symposium on Dis-tributed Objects and Applications,pages39–48,Antwerp, Belgium,September2000.
[13]Object Management Group.Fault Tolerant CORBA(?nal
adopted speci?cation).OMG Technical Committee Docu-ment ptc/2000-04-04,April2000.
[14]Object Management Group.The Common Object Request
Broker:Architecture and speci?cation,2.4edition.OMG Technical Committee Document formal/2001-02-33,Febru-ary2001.
[15]Object-Oriented Concepts,Inc.ORBacus for C++and Java,
1998.
[16] D.Powell,editor.Delta-4:A Generic Architecture for
Dependable Distributed Computing,volume1.Springer-Verlag,1991.
[17] D.Schmidt,M.Stal,H.Rohnert,and F.Buschmann.Pattern-
oriented software architecture,volume2.John Wiley& Sons,Ltd,2000.
[18]Vertel Corporation.e*ORB C++User Guide,December
2000.
[19]W.Zhao,P.Narasimhan,L.E.Moser and P.M.Melliar-
Smith.Experimental evaluation of a fault-tolerant CORBA system.In Proccedings of the International Conference on Parallel and Distributed Processing Techniques and Appli-cations,pages390–396,Las Vegas,NV,June2001.
---------------------------------------------------------------最新资料推荐------------------------------------------------------ 多媒体演示文稿的设计与制作 多媒体演示文稿的设计与制作( 初级)策勒县策勒乡托帕学校图尔荪江麦提尼亚孜通过对多媒体演示文稿的设计与制作(初级)课程的学习,我已经掌握了多媒体演示文稿的设计与制作基本知识及制作方法,收获颇多,现就自己的学习谈谈学习体会.一、知识点： 1、创建演示文稿；2、插入多媒体资源；3、多媒体资源的搭配； 4、播放和调用文稿。 二、应用1、PowerPoint 中有多种创建演示文稿的方法，对于一个初学者想要快速制作一个演示文稿可以根据内容提示向导创建演示文稿。 内容提示向导是创建演示文稿最快捷的一种方式，在内容提示向导的引导下，不仅能帮助使用者完成演示文稿相关格式的设置，而且还帮助使用者输入演示文稿的主要内容。 2、在多媒体演示文稿的页面中插入有关的文本、图片等多媒体资源需以下几个步骤： 选择要插入的多媒体资源；调整插入对象的位置和大小；3、（1）配色方案： 配色方案就是由多媒体演示文稿软件预先设计的能够应用于幻灯片中的背景、文本和标题等对象的一套均衡搭配的颜色。 通过配色方案，使多媒体演示文稿色彩绚丽，多呈现的内容更加生动，进行配色时需完成以下几个步骤： 1 / 3
选择配色方案；应用配色方案；（2）利用版式搭配多媒体资源：版式是PowerPoint2003 软件中的一种常规排版的格式，通过幻灯片版式的应用可以对文字、图片等等更加合理简洁完成布局，通常PowerPoint2003 中已经内置文字版式、内容版式等版式类型供使用者使用，利用版式可以轻松完成幻灯片制作和运用。 运用版式搭配多媒体资源需要以下几个步骤： 选择版式；应用版式；（3）、图形组合： 图形组合是 PowerPoint 软件中的一种图形处理功能，可以将多个独立的形状组合成一个图形对象，然后对组合后的图形对象进行移动、修改大小等操作，操作步骤如下： 选择图形；组合图形；4、播放和调用文稿： （1）、自定义播放： 由于一个演示文稿中可能有很多张幻灯片，有些时候我们不需要全部播放出来，这时就需要对演示文稿中的幻灯片设置自定义播放。 自定义播放演示文稿需以下几步： 选择要播放的演示文稿；设置自定义播放；（2）、打包演示文稿：演示文稿制作完成后，往往不是在一台计算机上播放，有时会出现演示文稿中所插入的视音频等资源不能顺利播放的情况。 如张老师把在家做好的演示文稿拿到教室播放，在排除连线、播放软件问题等因素后，演示文稿中插入的资源仍不能播放，请教计算机老师后，计算机老师建议可以通过以下两种方式解决：打包演示文稿；用 U 盘把 PowerPoint 中的所有资源拷到教室重
多媒体演示文稿的设计与制作学习心得体会 杨保政 作为一名小学数学年教师，我对教学媒体和资源总是充满了兴趣。在上课的时候，我更喜欢利用多媒体，来引导学生学习新知识。但有的时候上课的效果却不尽如人意。这次能参加全员培训中我学到制作演示文稿的时候，清新的ppt 演示，实用的制作技巧，让我眼前一亮，制作攻略更是让我热血沸腾，我终于认识到了我以前为什么很用心的制作PPT，但是效果却不好的原因了，那就是没有人会对着密密麻麻的知识点感兴趣的，不由得想到了初中时候的自己，和他们不是一样的吗？ 在本次培训中制作演示文档的部分，我对它进行了简单的总结： 攻略一：少即是多：每页一个主题；巧用备注栏；字少图大；提炼关键词句。呆板无趣的知识点会让学生们昏昏欲睡，如果将知识点精炼再加上图片会提升学生学习的兴趣，而且也减轻了学生的负担，让他们在快乐中获取知识。甚至在PPT中我可以恰当使用高桥法，醒目的字眼跃然眼帘，再不用老师来反复强调这是重点啊重点啊！ 攻略二：：换位思考：文字不小于24号；及时回顾总结；文字和背景反差鲜明；从学生的角度来思考一堂课的教授方
法，没有那么多过目不忘的学生，怎么讲课才能使学生印象深刻呢？看来我要在这方面多下功夫了。 攻略三：逻辑清晰：顺序播放；逻辑主线简明；格式一致；思想要点图表化。 攻略四：形象表达：适当运用全图型PPT；图表图形化；精心设计封面和目录；用声音烘托气氛。一幅好图胜过一千句话，无关的美景干扰主题；过多的插图分散注意；过于复杂的画面增加认知负荷；插图与背景混杂 攻略五：动静结合：控制长度；加快速度；明确目的；聚焦内容 在本次学习中，有一句话令我印象深刻，一堂课是否精彩，关键是教师而不是工具！是啊，无论ppt做得多么华丽，内容是多么深刻。但是一堂课的精彩与否，还是得靠教师来把握，路漫漫其修远兮，吾将上下而求索！
多媒体演示文稿的设计 与制作学习心得体会 This model paper was revised by LINDA on December 15, 2012.
多媒体演示文稿的设计与制作 学习心得体会 通过这次培训学习，使我进一步地掌握了制作和应用ppt等网络教学的知识和技能，增长了见识，理论水平、操作水平也有所提高。基本上掌握多媒体教学演示文稿的制作方法，主要有以下几个方面内容： （一）创建多媒体教学演示文稿； （二）编辑幻灯片； （三）编辑超级链接； （四）播放并调试幻灯片； （五）使用动画效果； 对我们教师来说，PowerPoint课件是最早接触的。利用PowerPoint可以创建出非常漂亮的幻灯片文稿，这些幻灯片中既可以有文字，还可以包含图画、表格、统计图表、组织结构图，甚至可以有声音、乐曲和动画效果，还可以为这些幻灯片设计出统一或不同的背景。利用PowerPoint可通过各种形式放映幻灯片，既可以在完全没有人工干预的情况下自动放映，也可以由使用者手工控制播放，可以令每张幻灯片从不同的角度，以不同的方式切入到屏幕上，使得放映效果生动有趣。这次网络研修，主要学习了Powerpoint基础操作、基本编辑；音、视频处理；演示文稿中动画的设置，设置不同的背景，艺术字与自选图形等。通过学习我对制作课件有了新的认识，制作课件既要讲究精美又要讲究实用。不同的制作软件具有不同的特点，在制作课件时，应根据需要选择合适的制作软件。制作课件是一个艰苦的创作过程，优秀的课件应融教育性、科学性、艺术
性、技术性于一体，这样才能最大限度地发挥学习者的潜能，强化教学效果，提高教学质量。 在这一次的学习中，我通过对每个章节的仔细学习，才知道平时经常用的ppt有如此强大的教学课件制作功能，可以说我之前所掌握的只是ppt课件制作功能的冰山一角。 在现代教育教学中多媒本技术在教育教学上的运用越来越多，多媒体以它更直观、更灵活、更易让学生理解的特点，使它成为许多教师教学方法的首选。而之前我只是对ppt课件的制作有一点认识，通过教师深入浅出的讲解和鲜活的实例，让我对ppt课件有了更深的认识，在今后的课件制作方面，我会把所学的制作技能运用其中，制作出更加实用、高效的教学课件。 通过学习，使我更加深刻地了解了多媒体课件制作的方法及技巧，认识到多媒体课件制作为教师专业化的成长提供了一个平台，同时也让我明确了本次学习的目标、内容、使自己由传统化教师向现代化教师发展。 张三
第5章演示文稿设计与制作 第1节认识演示文稿第1课时（共2课时） 一、教学目标： 1、知识与技能： （1）掌握“ wps演示”的启动和退出方法 （2）了解“ wps演示”窗口的组成和使用 （3）初步掌握“ wps ”基本操作 2、过程与方法：通过观看、欣赏“ WPS演示”范例作品，激发学习兴趣，结合任务认识“WPS 演示”的窗口，掌握标题幻灯片的制作方法，在实践过程中达成技能的形成。 3、情感态度与价值观：知道“ WPS演示”是一种展示、汇报工具软件，知道能用“WPS 演示”制作一些作品来展示自己的风采、想法等，感受信息技术的魅力和价值。 二、教学重点： 知道演示文稿的编辑 三、教学难点： 演示文稿的编辑 四、教学方法： 任务探究，体验学习，实验学习 五、教学过程： （一）情境导入 同学们，大家好！今天老师带了件礼品给大家，想看看吗？看完后请你说一说看到了什 么？听到了什么？ 师向学生展示介绍学校的演示文稿。 刚才老师向大家展示的作品是一个演示文稿，它可以将文字、图片、视频和音乐等素材 整合起来。演示文稿在我们的生活中用处可大啦，如产品介绍、自我介绍、辅助教学等。制 作这样的作品，需要专业的软件，你知道有哪些软件可以制作演示文稿呢？今天向大家介绍一款专门用于制作演示文稿的软件一一“WPS演示”。 今天这节课我们就一起来认识“ WPS演示”软件。（板书：第5章第1节认识演示文稿）（二）、新授 自主学习： 1、一个完整的演示文稿一般由___________________________________________________ 构成。 2、演示文稿中包含的素材一般有_________________________________________________ 等。 3、演示文稿的设计包括__________________________ 。 合作探究： 1、任务一：新建演示文稿 学生自学，打开“ wps演示”窗口，新建一个“ wps演示”文档。 2、任务二：新建“封面标题页” 下面我们来新建第一页幻灯片。 单击右侧的“版式”按键，打开“幻灯片版式”任务空格，在“母版版式”中选择“空 白” 3、任务三：插入字标题 插入“中国元素”艺术字 4、任务四：插入背景图片 插入“中国元素背景 1 ”并设置“叠放次序”为“置于底层”
多媒体演示文稿的设计与制作 ——基于网络环境下任务驱动教学单元教学案例设计 山西省运城市康杰中学赵红冰 【课时安排】8课时 【年级】高一年级 【学习目标】 ◆知识与技能： ①掌握多媒体演示文稿中幻灯片的基本制作方法。 ②熟练掌握幻灯片的自定义动画、幻灯片切换、放映方式等设置。 ③掌握多种媒体的插入方法与超级链接设置。 ④能够对幻灯片进行打包并解包放映。 ⑤能够利用多种途径搜集表现主题所需要的多媒体素材，并能进行筛选规类。 ⑥能利用网络教学软件提交作业。 ◆过程与方法： ①通过作品的制作过程提高学生综合处理多种媒体技术的能力。 ②通过幻灯片版面的整体布局和设计以及背景、色彩的搭配提高学生的艺术表现力和审美能力。 ③通过创建超级链接培养学生对作品的控制能力和交互能力。 ◆情感态度与价值观： ①图文声像并茂，激发学生学习兴趣。 ②友好的交互环境，调动学生积极参与。 ③丰富的信息资源，扩大学生知识面。 ④超文本结构组织信息，提供多种学习路径。 【学习重点】 确定主题并围绕主题搜集、筛选、分类整理素材。 幻灯片版面的设计与布局。 【学习难点】 色彩的搭配与风格的统一、独特。 【学习平台】 基于互联网的多媒体网络教室. 【学习方法】 基于“任务驱动教学方法”下的自主、协作、探究、创新的学习方法。 一、任务设计 （一）、任务描述： 学习完PowerPoint办公软件，我们已了解了这是一个集多种媒体的演示性文稿，通过多媒体的组合可以对主题的表达更形象、生动、丰富多彩。请同学们利用已掌握的制作演示文稿的多种技术来表达一个主题，制作出图文并茂、形象生动的电子演示文稿。 （二）、任务要求： 1、主题要求 自由命题：主题鲜明、内容健康，富有个性。 可参考以下方向： 宣传科普知识或环保知识；介绍本地区旅游资源；介绍本校风貌；介绍本班情况；
多媒体演示文稿的设计与制作学习心得体会通过这次培训学习，使我进一步地掌握了制作和应用ppt等网络教学的知识和技能，增长了见识，理论水平、操作水平也有所提高。基本上掌握多媒体教学演示文稿的制作方法，这次培训学习心得体会如下： 一、知识点： 这次培训学习主要有以下几个方面内容： （一）创建演示文稿 （二）插入多媒体资源 （三）多媒体资源搭配 （四）播放和调试文稿 二、内容呈现： 1.创建课件页 （1）新建文稿 启动PowerPoint，在"新建演示文稿"对话框中选择"空演示文稿"。 （2）选择版式 默认的是“标题幻灯片”。课根据自己的需要进行选择； （3）输入文本 选择"插入"菜单中"文本框"中"文本框"命令后，在编辑区拖动鼠标，绘出文本框，然后输入相应文字或者粘贴上你所需要的文字。 （4）格式化文本 与其它字处理软件（如WORD）相似 （5）调整文本位置 通过调整文本框的位置来调整文本的位置。先选中要调整的文本框，使其边框上出现8个控制点，然后根据需要拖动控制点，文本框随之改变大小。当鼠标指针放在文本框边上的任何不是控制点的位置时，鼠标指针附带十字箭头，这时拖动鼠标可调整文本框的位置。 通过调整文本框的位置来调整文本的位置。先选中要调整的文本框，使其边框上出现8个控制点，然后根据需要拖动控制点，文本框随之改变大小。当鼠标指针放在文本框边上的任何不是控制点的位置时，鼠标指针附带十字 箭头，这时拖动鼠标可调整文本框的位置。
2、编排与修改 2.1 插入图片 （1）选择"插入"-"图片"，选取合适的图片，然后单击"插入"按钮。 2.2 选取模板 单击"格式"菜单中的"幻灯片设计…"命令，选择合适的模板，也可在幻灯片上单击右键，通过快捷菜单选择"幻灯片…"命令。 2.3 应用背景 如果不想对课件页添加模板，而只是希望有一个背景颜色或者是图片，可以单击"格式"菜单中的"背景"命令，在"背景"对话框中，打开下拉列表框，或单击"其他颜色…"选择合适的颜色，也可以选择"填充效果" 2．4影片、声音 执行“文件——插入——影片和声音”选择文件中的影片或者文件中的声音进行操作，为了防止课件到拷贝其他电脑无法获取文件，可将声音或影片文件与幻灯片文件放在同一文件夹下 三、学以致用： 1、PowerPoint中有多种创建演示文稿的方法，对于一个初学者想要快速制作一个演示文稿可以根据内容提示向导创建演示文稿。“内容提示向导”是创建演示文稿最快捷的一种方式，在“内容提示向导”的引导下，不仅能帮助使用者完成演示文稿相关格式的设置，而且还帮助使用者输入演示文稿的主要内容。 2、在多媒体演示文稿的页面中插入有关的文本、图片等多媒体资源需以下几个步骤：选择要插入的多媒体资源；调整插入对象的位置和大小； 3、（1）配色方案：配色方案就是由多媒体演示文稿软件预先设计的能够应用于幻灯片中的背景、文本和标题等对象的一套均衡搭配的颜色。通过配色方案，使多媒体演示文稿色彩绚丽，多呈现的内容更加生动，进行配色时需完成以下几个步骤：选择配色方案；应用配色方案；（2）利用版式搭配多媒体资源：版式是PowerPoint2003软件中的一种常规排版的格式，通过幻灯片版式的应用可以对文字、图片等等更加合理简洁完成布局，通常PowerPoint2003中已经内置文字版式、内容版式等版式类型供使用者使用，利用版式可以轻松完成幻灯片制作和运用。运用版式搭配多媒体资源需要以下几个步骤：选择版式；应用版式；（3）、图形组合：图形组合是PowerPoint软件中的一种图形处理功能，可以将多个独
多媒体演示文稿的设计与制作 学习心得体会 最近参加了Powerpoint2010培训，学到了很多的ppt制作相关理论和ppt课件制作技巧，真是受益匪浅。对我们教师来说，PowerPoint课件是最早接触的。利用PowerPoint 可以创建出非常漂亮的幻灯片文稿，这些幻灯片中既可以有文字，还可以包含图画、表格、统计图表、组织结构图，甚至可以有声音、乐曲和动画效果，还可以为这些幻灯片设计出统一或不同的背景。 利用PowerPoint可通过各种形式放映幻灯片，既可以在完全没有人工干预的情况下自动放映，也可以由使用者手工控制播放，可以令每张幻灯片从不同的角度，以不同的方式切入到屏幕上，使得放映效果生动有趣。这次培训，主要学习了在Powerpoint基础操作、基本编辑、音、视频处理、演示文稿中动画的设置，设置不同的背景，艺术字与自选图形，表格等。通过培训我对制作课件有了新的认识，制作课件既要讲究精美又要讲究实用。不同的制作软件具有不同的特点，在制作课件时，应根据需要选择合适的制作软件。制作课件是一个艰苦的创作过程，优秀的课件应融教育性、科学性、艺术性、技术性于一体，这样才能最大限度地发挥学习者的潜能，强化教学效果，提高教学质量。在这一次的学习中，我通过对每个章节的仔细学习，才知道平时经常用的
ppt有如此强大的教学课件制作功能，可以说我之前所掌握的只是ppt课件制作功能的冰山一角。现代教育教育多媒本技术在教育教学上的运用越来越多，多媒体以它更直观、更灵活、更易让学生理解的特点，使它成为许多教师教学方法的首选。而之前我只是对ppt课件的制作有一点认识，通过教师深入浅出的讲解和鲜活的实例，让我对ppt课件有了更深的认识，在今后的课件制作方面，我会把所学的制作技能运用其中，制作出更加实用、高效的教学课件。 通过学习，使我更加深刻地了解了多媒体课件制作的方法及技巧，认识到多媒体课件制作为教师专业化的成长提供了一个平台，同时也让我明确了本次学习的目标、内容、使自己由传统化教师向现代化教师发展。
《多媒体演示文稿的设计与制作（初级）》学习心得最近参加了多媒体演示文稿的设计与制作的学习培训，学到了很多的ppt制作相关理论和ppt课件制作技巧，真是受益匪浅。 对我们教师来说，PowerPoint课件是最早接触的。利用PowerPoint可以创建出非常漂亮的幻灯片文稿，这些幻灯片中既可以有文字，还可以包含图画、表格、统计图表、组织结构图，甚至可以有声音、乐曲和动画效果，还可以为这些幻灯片设计出统一或不同的背景。 利用PowerPoint可通过各种形式放映幻灯片，既可以在完全没有人工干预的情况下自动放映，也可以由使用者手工控制播放，可以令每张幻灯片从不同的角度，以不同的方式切入到屏幕上，使得放映效果生动有趣。这次培训，主要学习了在Powerpoint基础操作、基本编辑、音、视频处理、演示文稿中动画的设置，设置不同的背景，艺术字与自选图形，表格等。通过培训我对制作课件有了新的认识，制作课件既要讲究精美又要讲究实用。不同的制作软件具有不同的特点，在制作课件时，应根据需要选择合适的制作软件。制作课件是一个艰苦的创作过程，优秀的课件应融教育性、科学性、艺术性、技术性于一体，这样才能最大限度地发挥学习者的潜能，强化教学效果，提高教学质量。在这一次的学习中，我通过对每个章节的仔细学习，才知道平时经常用的 ppt有如此强大的教学课件制作功能，可以说我之前所掌握的只是ppt课件制作功能的冰山一角。现代教育教育多媒本技术在教育教学上的运用越来越多，多媒体以它更直观、更灵活、更易让学生理解的特点，使它成为许多教师教学方法的首选。而之前我只是对ppt课件的制作有一点认识，通过教师深入浅出的讲解和鲜活的实例，让我对ppt课件有了更深的认识，在今后的课件制作方面，我会把所学的制作技能运用其中，制作出更加实用、高效的教学课件。 通过学习，使我更加深刻地了解了多媒体课件制作的方法及技巧，认识到多媒体课件制作为教师专业化的成长提供了一个平台，同时也让我明确了本次学习的目标、内容、使自己由传统化教师向现代化教师发展。我还有很多不懂的，继续学习，继续努力。 虞城高中杨金华
第 5 章演示文稿设计与制作 第 1 节认识演示文稿第 1 课时（共 2 课时） 一、教学目标： 1、知识与技能： （1）掌握“wps 演示”的启动和退出方法 （2）了解“wps 演示”窗口的组成和使用 （3）初步掌握“wps”基本操作 2、过程与方法：通过观看、欣赏“WPS 演示”范例作品，激发学习兴趣，结合任务认识“WPS 演示”的窗口，掌握标题幻灯片的制作方法，在实践过程中达成技能的形成。 3、情感态度与价值观：知道“WPS 演示”是一种展示、汇报工具软件，知道能用 “WPS 演示”制作一些作品来展示自己的风采、想法等，感受信息技术的魅力和价值。 二、教学重点： 知道演示文稿的编辑 三、教学难点： 演示文稿的编辑 四、教学方法： 任务探究，体验学习，实验学习 五、教学过程： （一）情境导入 同学们，大家好！今天老师带了件礼品给大家，想看看吗？看完后请你说一说看到了 什么？听到了什么？ 师向学生展示介绍学校的演示文稿。 刚才老师向大家展示的作品是一个演示文稿，它可以将文字、图片、视频和音乐等素 材整合起来。演示文稿在我们的生活中用处可大啦，如产品介绍、自我介绍、辅助教学等。制作这样的作品，需要专业的软件，你知道有哪些软件可以制作演示文稿呢？今天向大家 介绍一款专门用于制作演示文稿的软件——“WPS演示”。 今天这节课我们就一起来认识“WPS演示”软件。（板书：第5章第1节认识演示文稿） （二）、新授 自主学习： 1、一个完整的演示文稿一般由______________________________________________构成。 2、演示文稿中包含的素材一般有___________________________________________等。 3、演示文稿的设计包括________________________。 合作探究： 1、任务一：新建演示文稿 学生自学，打开“wps 演示”窗口，新建一个“wps 演示”文档。 2、任务二：新建“封面标题页” 下面我们来新建第一页幻灯片。 单击右侧的“版式”按键，打开“幻灯片版式”任务空格，在“母版版式”中选择“空 白…… 3、任务三：插入字标题 插入“中国元素”艺术字 4、任务四：插入背景图片
精品教育 第5章演示文稿设计与制作 第1节认识演示文稿第1课时（共2课时） 一、教学目标： 1、知识与技能： （1）掌握“wps演示”的启动和退出方法 （2）了解“wps演示”窗口的组成和使用 （3）初步掌握“wps”基本操作 2、过程与方法：通过观看、欣赏“WPS演示”范例作品，激发学习兴趣，结合任务认识“WPS 演示”的窗口，掌握标题幻灯片的制作方法，在实践过程中达成技能的形成。 3、情感态度与价值观：知道“WPS演示”是一种展示、汇报工具软件，知道能用“WPS演示”制作一些作品来展示自己的风采、想法等，感受信息技术的魅力和价值。 二、教学重点： 知道演示文稿的编辑 三、教学难点： 演示文稿的编辑 四、教学方法： 任务探究，体验学习，实验学习 五、教学过程： （一）情境导入 同学们，大家好！今天老师带了件礼品给大家，想看看吗？看完后请你说一说看到了什么？听到了什么？ 师向学生展示介绍学校的演示文稿。 刚才老师向大家展示的作品是一个演示文稿，它可以将文字、图片、视频和音乐等素材整合起来。演示文稿在我们的生活中用处可大啦，如产品介绍、自我介绍、辅助教学等。制作这样的作品，需要专业的软件，你知道有哪些软件可以制作演示文稿呢？今天向大家介绍一款专门用于制作演示文稿的软件——“WPS演示”。 今天这节课我们就一起来认识“WPS演示”软件。（板书：第5章第1节认识演示文稿） （二）、新授 自主学习： 1、一个完整的演示文稿一般由______________________________________________构成。 2、演示文稿中包含的素材一般有___________________________________________等。 3、演示文稿的设计包括________________________。 合作探究： 1、任务一：新建演示文稿 学生自学，打开“wps演示”窗口，新建一个“wps演示”文档。 2、任务二：新建“封面标题页” 下面我们来新建第一页幻灯片。 单击右侧的“版式”按键，打开“幻灯片版式”任务空格，在“母版版式”中选择“空白…… 3、任务三：插入字标题 插入“中国元素”艺术字
《制作演示文稿》教学设计 一、教材分析 本节选自滇人课标版初中信息技术七年级第10册第四单元第14课《制作演示文稿》，本节课的主要内容有制作封面幻灯片、制作演示文稿中的其他幻灯片、应用设计模板、自己设计模板组成。 本节课的内容是以搜集多媒体素材和加工多媒体素材为基础，学习演示文稿的制作，并对前面学到的知识巩固的升华。通过小组制作自己感兴趣的主题的作品如：我的校园生活、我喜欢的明星等，学习演示文稿的的版面设计、添加文字、插入图片、插入声音视频等操作，提高学生知识和技能的综合应用能力，激发学生学习兴趣，培养小组协作能力及欣赏水平。在制作演示文稿中体会乐趣，认识到自己的不足与优势，在学的过程中提高情感、态度与价值观。 二、学情分析 本节内容是针对七年级学生设计的，七年级的学生开始进入少年期（12-15岁），他们的身体形态发生着显著的变化，心理也相应的发生变化。在这个时期，学习者积极的向上心理和强烈的求知欲望，喜欢新鲜感的刺激，是塑造良好性格的最佳时期。通过小组协作和自主学习及他们多多媒体的新鲜感，来激发他们的创造性。 学生对PowerPoint有了初步的认识学会了一些基本操作，对本节的内容提前做了预习及素材准备。 学生对新鲜的事物有很强的好奇感，积极地探索精神。喜欢信息技术课程，享受网上学习的乐趣。合作与竞争性都十分明显，乐于小组合作且彰显自己的个性。 三、教学目标分析 1.知识与技能 （1）掌握制作封面幻灯片的基本步骤及要求。 （2）掌握制作幻灯片的基本步骤。 （3）学会根据设计风格合理应用幻灯片模板。
（4）掌握自己设计模板的方法。 2.过程与方法 （1）学会设计自己的模板。 （2）熟悉制作多媒体演示文稿的方法。 3.情感态度与价值观 （1）通过小组合作制作自己的模板，增强同学的组织能力和团队合作意识。（2）通过学生亲自提高电脑操作水平并且激发学生学习的兴趣。 （3）通过作品展示，增强学生的审美意识，激发学生的求知欲。 四、教学重难点 1.教学重点 （1）熟练掌握制作幻灯片的基本操作。 （2）学会应用设计幻灯片模板。 2.教学难点 （1）幻灯片制作的合理布局。 （2）有创意的设计小组主题的幻灯片。 五、教法与学法的设计 1.教法设计 （1）多媒体演示法，学生提前预习本节课的内容，已经有充分的基础知识准备。教师快速的应用多媒体形象直观的演示多媒体演示文稿的制作，解决预习中遇到的问题。 （2）启发教学，创设问题情境，使学生在教师的启发下通过对问题情境的分析，从而理解和解决问题。 （3）任务驱动法，学生分小组完成任务，激发学习兴趣，提高实践操作能力和合作学新能力。 2.学法设计 （1）协作学习法，以学生为中心，小组协作完成任务，对小组完成的作品欣赏评价，进一步巩固所学知识且提高了欣赏评价能力。
多媒体演示文稿的设计与制作学习心得体会 通过这次培训学习，使我进一步地掌握了制作和应用ppt等网络教学的知识和技能，增长了见识，理论水平、操作水平也有所提高。基本上掌握多媒体教学演示文稿的制作方法，这次培训学习心得体会如下： 一、知识点： 这次培训学习主要有以下几个方面内容： (-)创建演示文稿 (二)插入多媒体资源 (三)多媒体资源搭配 (四)播放和调试文稿 二、内容呈现： 1 ?创建课件页 (1)新建文稿 启动PowerPoint,在〃新建演示文稿〃对话框中选择〃空演示文稿〃。 (2)选择版式 默认的是“标题幻灯片”。课根据自己的需要进行选择； (3)输入文本 选择〃插入〃菜单中〃文本框〃中〃文本框〃命令后，在编辑区拖动鼠标，绘出文本框，然后 输入相应文字或者粘贴上你所需要的文字。 (4)格式化文本 与其它字处理软件(如WORD相似 (5)调整文本位置 通过调整文本框的位置来调整文本的位置。先选中要调整的文本框，使其边框上出现8 个控制点，然后根据需要拖动控制点，文本框随之改变大小。当鼠标指针放在文本框边上的任何不是控制点的位置时，鼠标指针附带十字箭头，这时拖动鼠标可调整文本框的位置。 通过调整文本框的位置来调整文本的位置。先选中要调整的文本框，使其边框上出现8 个控制
点，然后根据需要拖动控制点，文本框随之改变大小。当鼠标指针放在文本框边上的任何不是控制点的位置时，鼠标指针附带十字 箭头，这时拖动鼠标可调整文本框的位置。 2、编排与修改 2. 1插入图片 (1)选择〃插入〃-〃图片〃，选取合适的图片，然后单击〃插入〃按钮。 2. 2选取模板 单击〃格式〃菜单中的〃幻灯片设计，〃命令，选择合适的模板，也可在幻灯片上单击右键， 通过快捷菜单选择〃幻灯片，〃命令。 2.3应用背景 如果不想对课件页添加模板，而只是希望有一个背景颜色或者是图片，可以单击〃格式〃菜单中的〃背景〃命令，在〃背景〃对话框中，打开下拉列表框，或单击〃其他颜色，〃选择合适的颜色，也可以选择〃填充效果〃 2. 4影片、声音 执行“文件一一插入一一影片和声音”选择文件中的影片或者文件中的声音进行操作，为了防止课件到拷贝其他电脑无法获取文件，可将声音或影片文件与幻灯片文件放在同一文件夹下 三、学以致用： 1、PowerPoint中有多种创建演示文稿的方法，对于一个初学者想要快速制作一个演示文稿可以根据内容提示向导创建演示文稿。“内容提示向导”是创建演示文稿最快捷的一种方式，在“内容提示向导”的引导下，不仅能帮助使用者完成演示文稿相关格式的设置，而且还帮助使用者输入演示文稿的主要内容。 2、在多媒体演示文稿的页面中插入有关的文本、图片等多媒体资源需以下几个步骤：选择要插入的多媒体资源；调整插入对象的位置和大小； 3、(1)配色方案：配色方案就是由多媒体演示文稿软件预先设计的能够应用于幻灯片中的背景、文本和标题等对象的一套均衡搭配的颜色。通过配色方案，使多媒体演示文稿色彩绚丽，多呈现的内容更加生动，进行配色时需完成以下几个步骤：选择配色方案；应用配色方案；(2)利用版式搭配多媒体资源：版式是PowerPoint2003软件中的一种常规排版的格式，通过幻灯片版式的应用可以
<<多媒体演示文稿的设计与制作>>(初级)学习心得玉林市茂林镇中学梁海玲 通过对<<多媒体演示文稿的设计与制作>>(初级)课程的 学习,我已经掌握了多媒体演示文稿的设计与制作基本知识及 制作方法,收获颇多,现就自己的学习谈谈学习体会. 一、知识点 1、创建演示文稿； 2、插入多媒体资源； 3、多媒体资源的搭配； 4、播放和调用文稿。 二、应用 1、PowerPoint中有多种创建演示文稿的方法，对于一个初学者想要快速制作一个演示文稿可以根据内容提示向导创建演示文稿。“内容提示向导”是创建演示文稿最快捷的一种方式，在“内容提示向导”的引导下，不仅能帮助使用者完成演示文稿相关格式的设置，而且还帮助使用者输入演示文稿的主要内容。 2、在多媒体演示文稿的页面中插入有关的文本、图片等多媒体资源需以下几个步骤：选择要插入的多媒体资源；调整插入对象的位置和大小；
3、（1）配色方案：配色方案就是由多媒体演示文稿软件预先设计的能够应用于幻灯片中的背景、文本和标题等对象的一套均衡搭配的颜色。通过配色方案，使多媒体演示文稿色彩绚丽，多呈现的内容更加生动，进行配色时需完成以下几个步骤：选择配色方案；应用配色方案；（2）利用版式搭配多媒体资源：版式是PowerPoint2003软件中的一种常规排版的格式，通过幻灯片版式的应用可以对文字、图片等等更加合理简洁完成布局，通常PowerPoint2003中已经内置文字版式、内容版式等版式类型供使用者使用，利用版式可以轻松完成幻灯片制作和运用。运用版式搭配多媒体资源需要以下几个步骤：选择版式；应用版式；（3）、图形组合：图形组合是PowerPoint 软件中的一种图形处理功能，可以将多个独立的形状组合成一个图形对象，然后对组合后的图形对象进行移动、修改大小等操作，操作步骤如下：选择图形；组合图形； 4、播放和调用文稿：（1）、自定义播放：由于一个演示文稿中可能有很多张幻灯片，有些时候我们不需要全部播放出来，这时就需要对演示文稿中的幻灯片设置自定义播放。自定义播放演示文稿需以下几步：选择要播放的演示文稿；设置自定义播放；（2）、打包演示文稿：演示文稿制作完成后，往往不是在一台计算机上播放，有时会出现演示文稿中所插入的视音频等资源不能顺利播放的情况。如张老师把在家做好的演示文稿拿到教室播放，在排除连线、播放软件问题等因素后，演示文
多媒体演示文稿的设计与制作学习心得通过对<<多媒体演示文稿的设计与制作(初级)>>课程的学习,我已经基本掌握了多媒体演示文稿的设计与制作基本知识及制作方法,收获颇多,现就自己的学习谈一下几点. 一、知识点 1、创建演示文稿； 2、插入多媒体资源； 3、多媒体资源的搭配； 二、技能应用 1、PPT中有多种创建演示文稿的方法，对于一个初学者想要快速制作一个演示文稿可以根据内容提示向导创建演示文稿。“内容提示向导”是创建演示文稿最快捷的一种方式，在“内容提示向导”的引导下，不仅能帮助使用者完成演示文稿相关格式的设置，而且还帮助使用者输入演示文稿的主要内容。 2、在多媒体演示文稿的页面中插入有关的文本、图片等多媒体资源需以下几个步骤：选择要插入的多媒体资源；调整插入对象的位置和大小； 3、（1）配色方案：配色方案就是由多媒体演示文稿软件预先设计的能够应用于幻灯片中的背景、文本和标题等对象的一套均衡搭配的颜色。通过配色方案，使多媒体演示文稿色彩绚丽，多呈现的内容更加生动，进行配色时需完成以下几个步骤：选择配色方案；应用配色方案；（2）利用版式搭配多媒体资源：版式是PowerPoint2003软件中的一种常规排版的格式，通过幻灯片版式的应用可以对文字、图片等等更加合理简洁完成布局，通常PowerPoint2003中已经内置文字版式、内容版式等版式类型供使用者使用，利用版式可以轻松完成幻灯片制作和运用。运用版式搭配多媒体资源需要以下几个步骤：选择版式；应用版式；（3）、图形组合：图形组合是PowerPoint 软件中的一种图形处理功能，可以将多个独立的形状组合成一个图形对象，然后对组合后的图形对象进行移动、修改大小等操作，操作步骤如下：选择图形；组合图形； 三、内容展示 1.创建课件页 （1）新建文稿 启动PowerPoint，在"新建演示文稿"对话框中选择"空演示文稿"。 （2）选择版式 默认的是“标题幻灯片”。课根据自己的需要进行选择； （3）输入文本 选择"插入"菜单中"文本框"中"文本框"命令后，在编辑区拖动鼠标，绘出文本框，然后输入相应文字或者粘贴上你所需要的文字。 （4）格式化文本 与其它字处理软件（如WORD）相似 （5）调整文本位置 通过调整文本框的位置来调整文本的位置。先选中要调整的文本框，使其边框上出现8个控制点，然后根据需要拖动控制点，文本框随之改变大小。当鼠标指针放在文本框边上的任何不是控制点的位置时，鼠标指针附带十字箭头，这时拖动鼠标可调整文本框的位置。 通过调整文本框的位置来调整文本的位置。先选中要调整的文本框，使其边框上出现8个控制点，然后根据需要拖动控制点，文本框随之改变大小。当鼠标指针放在文本框边上的任何不是控制点的位置时，鼠标指针附带十字
演示文稿设计与制作 第1节认识演示文稿第1课时温宿县第二小学王新生 一、教学目标： 1、知识与技能： （1）掌握“wps演示”的启动和退出方法 （2）了解“wps演示”窗口的组成和使用 （3）初步掌握“wps”基本操作 2、过程与方法：通过观看、欣赏“WPS演示”范例作品，激发学习兴趣，结合任务认识“WPS 演示”的窗口，掌握标题幻灯片的制作方法，在实践过程中达成技能的形成。 3、情感态度与价值观：知道“WPS演示”是一种展示、汇报工具软件，知道能用“WPS 演示”制作一些作品来展示自己的风采、想法等，感受信息技术的魅力和价值。 二、教学重点： 知道演示文稿的编辑 三、教学难点： 演示文稿的编辑 四、教学方法： 任务探究，体验学习，实验学习 五、教学过程： （一）情境导入 同学们，大家好！今天老师带了件礼品给大家，想看看吗？看完后请你说一说看到了什么？听到了什么？ 师向学生展示介绍学校的演示文稿。 刚才老师向大家展示的作品是一个演示文稿，它可以将文字、图片、视频和音乐等素材整合起来。演示文稿在我们的生活中用处可大啦，如产品介绍、自我介绍、辅助教学等。制作这样的作品，需要专业的软件，你知道有哪些软件可以制作演示文稿呢？今天向大家介绍一款专门用于制作演示文稿的软件——“WPS演示”。 今天这节课我们就一起来认识“WPS演示”软件。（板书：第5章第1节认识演示文稿） （二）、新授 自主学习： 1、一个完整的演示文稿一般由______________________________________________构成。 2、演示文稿中包含的素材一般有___________________________________________等。 3、演示文稿的设计包括________________________。 合作探究： 1、任务一：新建演示文稿 学生自学，打开“wps演示”窗口，新建一个“wps演示”文档。 2、任务二：新建“封面标题页” 下面我们来新建第一页幻灯片。 单击右侧的“版式”按键，打开“幻灯片版式”任务空格，在“母版版式”中选择“空白…… 3、任务三：插入字标题 插入“中国元素”艺术字 4、任务四：插入背景图片
围绕A3演示文稿设计与制作的文本阅读心得体会 我是一名小学数学教师，要适应现代教育教学工作的需要，就应该具备现代教育技术的素质。通过这次培训学习，使我进一步地掌握了制作和应用ppt等网络教学的知识和技能，增长了见识，理论水平、操作水平也有所提高。现就自己的学习谈谈学习体会. 一、知识点 1、创建演示文稿； 2、插入多媒体资源； 3、多媒体资源的搭配； 4、播放和调用文稿。 二、应用 1、PowerPoint中有多种创建演示文稿的方法，对于一个初学者想要快速制作一个演示文稿可以根据内容提示向导创建演示文稿。 2、在多媒体演示文稿的页面中插入有关的文本、图片等多媒体资源需以下几个步骤：选择要插入的多媒体资源；调整插入对象的位置和大小； 3、（1）配色方案：配色方案就是由多媒体演示文稿软件预先设计的能够应用于幻灯片中的背景、文本和标题等对象的一套均衡搭配的颜色。 （2）利用版式搭配多媒体资源：版式是PowerPoint2003软件中的一种常规排版的格式，通过幻灯片版式的应用可以对文字、图片等等更加合理简洁完成布局，通常PowerPoint2003中已经内置文字版
式、内容版式等版式类型供使用者使用，利用版式可以轻松完成幻灯片制作和运用。 （3）、图形组合：图形组合是PowerPoint软件中的一种图形处理功能，可以将多个独立的形状组合成一个图形对象，然后对组合后的图形对象进行移动、修改大小等操作，操作步骤如下：选择图形；组合图形； 4、播放和调用文稿： （1）、自定义播放：由于一个演示文稿中可能有很多张幻灯片，有些时候我们不需要全部播放出来，这时就需要对演示文稿中的幻灯片设置自定义播放。 （2）、打包演示文稿：演示文稿制作完成后，往往不是在一台计算机上播放，有时会出现演示文稿中所插入的视音频等资源不能顺利播放的情况，可以通过打包演示文稿；用U盘把PowerPoint中的所有资源拷到教室重新做链接的方式解决； （3）、PowerPoint放映格式：我们一般都习惯将多媒体演示文稿保存为默认的演示文稿格式，其实还有很多保存格式可供我们选择。 三、内容呈现 PowerPoint课件是最早接触的。利用PowerPoint可以创建出非常漂亮的幻灯片文稿，这些幻灯片中既可以有文字，还可以包含图画、表格、统计图表、组织结构图，甚至可以有声音、乐曲和动画效果，还可以为这些幻灯片设计出统一或不同的背景。利用PowerPoint可通过各种形式放映幻灯片，既可以在完全没有人工干预的情况下自动
我是一名小学数学教师，要适应现代教育教学工作的需要，就应该具备现代教育技术的素质。通过这次培训学习，使我进一步地掌握了制作和应用ppt等网络教学的知识和技能，增长了见识，理论水平、操作水平也有所提高。现就自己的学习谈谈学习体会. 一、知识点 1、创建演示文稿； 2、插入多媒体资源； 3、多媒体资源的搭配； 4、播放和调用文稿。 二、应用 1、PowerPoint中有多种创建演示文稿的方法，对于一个初学者想要快速制作一个演示文稿可以根据内容提示向导创建演示文稿。 2、在多媒体演示文稿的页面中插入有关的文本、图片等多媒体资源需以下几个步骤：选择要插入的多媒体资源；调整插入对象的位置和大小； 3、（1）配色方案：配色方案就是由多媒体演示文稿软件预先设计的能够应用于幻灯片中的背景、文本和标题等对象的一套均衡搭配的颜色。 （2）利用版式搭配多媒体资源：版式是PowerPoint2003软件中的一种常规排版的格式，通过幻灯片版式的应用可以对文字、图片等等更加合理简洁完成布局，通常PowerPoint2003中已经内置文字版式、内容版式等版式类型供使用者使用，利用版式可以轻松完成幻灯片制作和运用。 （3）、图形组合：图形组合是PowerPoint软件中的一种图形处理功能，可以将多个独立的形状组合成一个图形对象，然后对组合后的图形对象进行移动、修改大小等操作，操作步骤如下：选择图形；组合图形； 4、播放和调用文稿： （1）、自定义播放：由于一个演示文稿中可能有很多张幻灯片，有些时候我们不需要全部播放出来，这时就需要对演示文稿中的幻灯片设置自定义播放。 （2）、打包演示文稿：演示文稿制作完成后，往往不是在一台计算机上播放，有时会出现演示文稿中所插入的视音频等资源不能顺利播放的情况，可以通过打包演示文稿；用U盘把PowerPoint中的所有资源拷到教室重新做链接的方式解决；