Assignment of Computer Fundamentals
Assignment of Computer Fundamentals
Assignment of Computer Fundamentals
= A72E16
= A × 163 + 7 × 162 + 2 × 161 + E × 160
= 4279810
Applying transitions
There are five broad transition categories:
1. Fades and dissolves
2. Wipes
3. Push and Cover
4. Stripes and bars
5. Random
To apply slide transitions
1. Click on View tab > presentation views (subgroup) - Click on the Slide
Sorter icon.
2. Slides will be displayed in the slide sorter view. This view makes it easy to
select, organize and manipulate individual slides.
3. Select the individual slide that you want to apply the transitions to from the
slide sorter view.
4. Click on Animations tab > transition to this slides (subgroup). Click on the
drop down arrow of the gallery (green circle). A drop down menu appears
with all the various types of transitions.
5. Select the desired transitions. The transitions are applied to the selected
slides. A live preview is available each time a transition is selected.
NOTE: to apply transitions to all the slides, click on the Apply to all icons on
the Transition to this slide subgroup.
Using Animation
In addition to transitions, animations can be added to the slide. Animations
are not added to a SLIDE as a whole as are transitions. Instead animations are
added to individual elements within a slide for example, text boxes, pictures,
text place holders, drawings etc
Applying animations
1. Click on View tab > Presentation views (subgroup) – select normal view.
2. Click on the Animations tab on the ribbon.
3. On the slide, click on the element that you would like to apply animation to.
The selected element is enclosed in a rectangular box.
4. Under the animations (subgroup), click on the Animate: drop down menu. A
user can select from one of the options.
5. Alternately, a user can define their own animation by clicking on the custom
animation icon in the animations subgroup.
6. When a user clicks on the custom animation icon, a task pane appears on
the right hand side of the window.
SET – 2
ANS04. The two design strategies for Software System Design are of the
following:
1. Functional design: The system is designed from a functional view point,
starting with a high-level view and progressively refining this into a more
detailed design. The System State is centralized and shared between the
functions operating on that state. Methods such as Jackson Structured
Programming (extension of the Jackson Structured Programming (JSP)
method. JSP, developed by Michael Jackson) and the Warnier-Orr method (The
technique is based on only a few simple principles of design that are very easy
to learn and to apply) are techniques of functional decomposition where the
structure of the data issued to determine the functional structure used to
process that data.
2. Object-oriented design: The system is viewed as a collection of objects
rather than as functions. Object-oriented design is based on the idea of
information hiding and has been described by Meyer, Booch, and Jacobsen.
And many others. JSD is a design method that falls somewhere between
function-oriented and object-oriented design.
In an object-oriented design, the System State is decentralized and each object
manages its own state information. Objects have a set of attributes defining
their state and operations, which act on these attributes. Objects are usually
members of an object class whose definition defines attributes and operations
of class members. These may be inherited from one or more super-classes so
that a class definition need only set out the differences between that class and
its super-classes. Objects communicate by exchanging messages; an object
calling a procedure associated with another object achieves most object
communication.
There is no ‘best’ design strategy, which is suitable for all projects and all
types of application. Functional and object-oriented approaches are
complementary rather than opposing techniques. Software engineers select
the most appropriate approach for each stage in the design process. In fact,
large software systems are complex entities that different approaches might
be used in the design of different parts of the system.
An object-oriented approach to software design seems to be natural at the
highest and lowest levels of system design. Using different approaches to
design may require the designer to convert his or her design from one model
to another. Many designers are not trained in multiple approaches so prefer to
use either object-oriented or functional design.
The four quality measures for building software are of the following:
Correspondence – measures how well the delivered system matches
the needs of the operational environment, as described in the original
requirements statement.
Validation – task of predicting correspondence.
Correctness – measures the consistency of the product requirements
with respect to the design specification.
Verification – exercise of determining correctness.
Validation begins as soon as the project starts, but verification can begin only
after a specification has been accepted.
Four quality measures for building software.