Mc0069 Paper 1

7/31/2019 Mc0069 Paper 1

1/14

1.. Explain the four basic principles of modeling.

Although the mathematical modelling of aquatic ecosystems is not yet a common tool in the design and

operation of fish farms, the knowledge and quantitative evaluation of a system (the sources of nutrients

and their fate along the food chain) could, even today, provide for a better understanding of the

processes that are taking place. This knowledge and understanding may be the basis of exercising

control over the system that could provide for more efficient performance, the prediction of emergency

situations such as oxygen depletion and algal blooms, and the saving of fodder costs. These are only a

few of the probable advantages. As a general rule, the description of a system using quantitative terms,

and an investigation of the cause and effect or input-response relationships and interactions (instead of

relying only on qualitative data) will give more possibilities to the operator in controlling this system.

To elucidate these general statements let us examine a common situation. Due to increased input of

nutrients and organic matter, combined with high temperatures, the dissolved oxygen content of water

may drop drastically, resulting in severe effects such as fish kills. If one has a validated model that

describes oxygen depletion as a function of the organic matter present in the water and sediment, the

photosynthetic and respiration activity of algae, the wind velocity, the temperature and other affecting

factors, then one may be able to predict such situations in advance and take the necessary counter

measures of aeration, removal of organic sediment and decrease of external load. On the contrary, ifone only knows by qualitative experience that such situations may be developing on hot and windless

days, but does not know the other causes and interrelationships in quantitative terms, then one's action

may be too early or too late, or entirely ineffective.

This does not mean, of course, that experience is not of vital importance. Without experiments and

field measurements the best mathematical model will be only a mere game to play.

These notes do not intend to give full details of ecosystem modelling, since this could be the subject of

two or three semesters and not three lessons. They are intended to give a brief introduction into the

basic principle of such system viewing and model developments, on the basis of which those interested

may be able to start to read the relevant literature and to develop their respective models gradually,using their own measurement data.

2. How do model template classes in the UML?

Templates

In UML models, templates are model elements with unbound formal parameters that you can use to

define families of classifiers, packages, and operations.

A template is a parameterized model element that describes or identifies the pattern for a group ofmodel elements of a particular type. Because they represent types of elements, you cannot use

templates directly in your models. Instead, you must first instantiate the template by binding its

parameters to actual values. A binding between a template and a model element generates a new model

element based on the template. You can then use the bound element to model part of a system.

Instead of designing distinct model elements for each data type in your model, you can use templates to

design a single model element (a classifier, a package, or an operation) that works with different kinds

of data. For example, a template class provides a parameterized description of a class, specifying its

attributes and operations. By binding multiple classes to the template you can generate new classes

with the same characteristics as the template.

A template appears as a classifier with a dashed box in the upper right corner

3. explain the significance of aggregation with an example.

7/31/2019 Mc0069 Paper 1

2/14

Aggregation is a relationship between two classes that is best described as a "has-a" and "whole/part"

relationship. It is a more specialized version of theassociation relationship. The aggregate class

contains a reference to another class and is said to have ownership of that class. Each class referenced

is considered to bepart-ofthe aggregate class

Ownership occurs because there can be no cyclic references in an aggregation relationship. If Class A

contains a reference to Class B and Class B contains a reference to Class A then no clear ownership

can be determined and the relationship is simply one of association.

For example, imagine a Student class that stores information about individual students at a school.

Now let's say there is a Subject class that holds the details about a particular subject (e.g., history,

geography). If the Student class is defined to contain a Subject object then it can be said that the

Student object has-a Subject object. The Subject object also makes uppart-ofthe Student object, after

all there is no student without a subject to study. The Student object is therefore the owner of the

Subject object

Examples:

There is an aggregation relationship between Student class and the Subject class:

public class Subject {

private String name;

public void setName(String name)

{

this.name = name;

}

public String getName()

{

return name;}

}

public class Student {

private Subject[] studyAreas = new Subject[10];

//the rest of the Student class

}

4. discuss UMLs extensibility mechanisms.

UML is a very expressive language.[1]It is used as industry standard for visualizing, specifying,

constructing, and documenting the artifacts of a software-intensive system. [2] It is used to extend the

language's scope and viability.UML can be expressed inherently.This expressive property of UML

help to model enterprise information systems,distributed Web-based applications and real-time

embedded systems easily.

Introduction

The UML is process independent.UML is very powerful modeling language[1]It is easy to understand

and use.The UML is made simpler by using four mechanisms.They are specifications, adornments,

common divisions, and extensibility mechanisms. These mechanisms are applied throughout thelanguage.TheUML extensibility mechanisms helps to extend the language in controlled ways.[2]

5. Give a brief note on the UMLs five behavioral diagrams.

7/31/2019 Mc0069 Paper 1

3/14

Definition of: UML

(Unified Modeling Language) An object-oriented analysis and design language from the Object

Management Group (OMG). Many design methodologies for describing object-oriented systems were

developed in the late 1980s. UML standardizes several diagramming methods, including Grady

Booch's work at Rational Software, Rumbaugh's Object Modeling Technique and Ivar Jacobson's work

on use cases.

There are twelve diagrams supported under UML. Four are structural, five are behavioral and three are

used for model management, which include packages, subsystems and models. See XMI.

Structural Diagrams

The four structural diagrams are class, object, component and deployment. Following is an example of

the class diagram:

Class DiagramThis is one of the structural diagrams.User, User Terminal and Server are three classes that have attributes and operations. Anactor is a UML "stereotype" that is external to the system. Lines between classes are "associations." The asterisk means

"many," in this case, a many-to-one relationship between client and server.

Behavioral Diagrams

There are five behavioral diagrams: use case, sequence, activity, collaboration and state chart.

Following are examples of four of them:

7/31/2019 Mc0069 Paper 1

4/14

Use Case DiagramThis diagram shows a system's functions from a user's point of view, which in this case is pretty simple. All the followingdiagrams were created in the Telelogic Tau UML suite by Telelogic for this same example. Five of the nine possible diagrams

available in UML are shown below. The Component Diagram (software module interaction), Deployment Diagram (hardwarenodes) and the Activity Diagram (tasks) are not included. The Object Diagram (instantiations of classes) is rarely used. (All

diagrams courtesy of Telelogic, AB, www.telelogic.com)

Sequence DiagramLike an MSC (Message Sequence Diagram), the Sequence Diagram depicts the message flow between entities in the system.The items between double left/right arrows are UML "stereotypes." See MSC.

7/31/2019 Mc0069 Paper 1

5/14

Collaboration DiagramThis diagram emphasizes the structure of the relationships between entities. Note that the user is associated with the user

terminal in a session, and the terminal is associated with the server in a connection. The order of messages can be read by

interpreting the numbers prefixes.

7/31/2019 Mc0069 Paper 1

6/14

State ChartThis describes the finite states that take place in the system. The rectangles are the states, and the lines between them are the

transitions. The connection state shows three substates. The single circles are starting points, and the double circles are the ends.

6. Explain the necessary steps to reverse engineer an object diagram.

verview:

Object diagrams are derived from class diagrams so object diagrams are dependent upon class

diagrams.

7/31/2019 Mc0069 Paper 1

7/14

Object diagrams represent an instance of a class diagram. The basic concepts are similar for class

diagrams and object diagrams. Object diagrams also represent the static view of a system but this static

view is a snapshot of the system at a particular moment.

Object diagrams are used to render a set of objects and their relationships as an instance.

Purpose:

The purpose of a diagram should be understood clearly to implement it practically. The purposes of

object diagrams are similar to class diagrams.

The difference is that a class diagram represents an abstract model consisting of classes and their

relationships. But an object diagram represents an instance at a particular moment which is concrete in

nature.

It means the object diagram is more close to the actual system behaviour. The purpose is to capture the

static view of a system at a particular moment.

So the purpose of the object diagram can be summarized as:

Forward and reverse engineering.

Object relationships of a system

Static view of an interaction.

Understand object behaviour and their relationship from practical perspective

How to draw Object Diagram?

We have already discussed that an object diagram is an instance of a class diagram. It implies that an

object diagram consists of instances of things used in a class diagram.

So both diagrams are made of same basic elements but in different form. In class diagram elements are

in abstract form to represent the blue print and in object diagram the elements are in concrete form to

represent the real world object.

To capture a particular system, numbers of class diagrams are limited. But if we consider object

diagrams then we can have unlimited number of instances which are unique in nature. So only those

instances are considered which are having impact on the system.

From the above discussion it is clear that a single object diagram cannot capture all the necessary

instances or rather cannot specify all objects of a system. So the solution is:

First, analyze the system and decide which instances are having important data and association.

Second, consider only those instances which will cover the functionality.

Third, make some optimization as the numbers of instances are unlimited.

Before drawing an object diagrams the following things should be remembered and understood clearly:

Object diagrams are consist of objects.

The link in object diagram is used to connect objects.

Objects and links are the two elements used to construct an object diagram.

Now after this the following things are to be decided before starting the construction of the diagram:

The object diagram should have a meaningful name to indicate its purpose.

The most important elements are to be identified.

7/31/2019 Mc0069 Paper 1

8/14

The association among objects should be clarified.

Values of different elements need to be captured to include in the object diagram.

Add proper notes at points where more clarity is required.

The following diagram is an example of an object diagram. It represents the Order management system

which we have discussed in Class Diagram. The following diagram is an instance of the system at a

particular time of purchase. It has the following objects

Customer

Order

SpecialOrder

NormalOrder

Now the customer object (C) is associated with three order objects (O1, O2 and O3). These order

objects are associated with special order and normal order objects (S1, S2 and N1). The customer is

having the following three orders with different numbers (12, 32 and 40) for the particular time

considered.

Now the customer can increase number of orders in future and in that scenario the object diagram willreflect that. If order, special order and normal order objects are observed then we you will find that

they are having some values.

For orders the values are 12, 32, and 40 which implies that the objects are having these values for the

particular moment (here the particular time when the purchase is made is considered as the moment)

when the instance is captured.

The same is for special order and normal order objects which are having number of orders as 20, 30

and 60. If a different time of purchase is considered then these values will change accordingly.

So the following object diagram has been drawn considering all the points mentioned above:

Where to use Object Diagrams?

Object diagrams can be imagined as the snapshot of a running system at a particular moment. Now to

clarify it we can take an example of a running train.

Now if you take a snap of the running train then you will find a static picture of it having the

following:

A particular state which is running

A particular number of passengers. which will change if the snap is taken in a different time.

7/31/2019 Mc0069 Paper 1

9/14

So here we can imagine the snap of the running train is an object having the above values. And this is

true for any real life simple or complex system. In a brief, object diagrams are used for:

Making the prototype of a system.

Reverse engineering.

Modeling complex data structures.

Understanding the system from practical perspective.

7. Explain the terms context, objects and roles, links, messages

Data, context and interaction (DCI) is a paradigm used in computer software to program systems of

communicating objects. Its goals are:

To improve the readability ofobject-oriented code by giving system behavior first-class status;

To cleanly separate code for rapidly changing system behavior (what the system does) from

code for slowly changing domain knowledge (what the system is), instead of combining both in

one class interface;

To help software developers reason about system-level state and behavior instead of onlyobject state and behavior;

To support an object style of thinking that is close to peoples' mental models, rather than the

class style of thinking that overshadowed object thinking early in the history of object-oriented

programming languages.

The paradigm separates the domain model (data) fromuse cases (context) and roles that objects play

(interaction). DCI is complementary to modelviewcontroller(MVC). MVC as apattern languageis

still used to separate the data and its processing from presentation.

DCI was invented byTrygve Reenskaug, also the inventor of MVC. The current formulation of DCI is

mostly the work of Reenskaug andJames O. Coplien.

Description

Data

The data are "what the system is." The data part of the DCI architecture is its (relatively) static

data model with relations. The data design is usually coded up as conventional classes that

represent the basic domain structure of the system. These classes are barely smart data, and

they explicitly lack the functionality that is peculiar to support of any particular use case. These

classes commonly encapsulate the physical storage of the data. These data implement an

information structure that comes from the mental model of end users, domain experts,

programmers, and otherpeople in the system. They may correspond closely to the model

objects of MVC.

An example of a data object could be a bank account. Its interface would have basic operations

for increasing and decreasing the balance and for inquiring about the current balance. The

interface would likely not offer operations that involve transactions, or which in any way

involve other objects or any user interaction. So, for example, while a bank account may offer a

primitive for increasing the balance, it would have no method called deposit. Such operations

belong instead in the interaction part of DCI.

Data objects are instances of classes that might come from domain-driven design, and such

classes might use subtyping relationships to organize domain data. Though it reduces to classes

in the end, DCI reflects a computational model dominated by object thinking rather than class

thinking. Therefore, when thinking "data" in DCI, it means thinking more about the instances atrun time than about the classes from which they were instantiated.

Context

The Context is the class (or its instance) whose code includes the roles for a given algorithm,

scenario, oruse case, as well as the code to map these roles into objects at run time and to enact

7/31/2019 Mc0069 Paper 1

10/14

the use case. Each role is bound to exactly one object during any given use case enactment;

however, a single object may simultaneously play several roles. A context is instantiated at the

beginning of the enactment of an algorithm, scenario, oruse case. In summary, a Context

comprises use cases and algorithmsin which data objects are used through specific Roles.

Each context represents one or moreuse cases. A context object is instantiated for each

enactment of a use case for which it is responsible. Its main job is to identify the objects that

will participate in the use case and to assign them to play the Roles which carry out the use case

through their responsibilities. A role may comprise methods, and each method is some small

part of the logic of an algorithm implementing a use case. Role methods run in the context of

an object that is selected by the context to play that role for the current use case enactment. The

role-to-object bindings that take place in a context can be contrasted with the polymorphism of

vernacular object-oriented programming. The overall business functionality is the sum of

complex, dynamic networks of methods decentralized in multiple contexts and their roles.

Each context is a scope that includes identifiers that correspond to its roles. Any role executing

within that context can refer to the other roles in that context through these identifiers. These

identifiers have come to be called methodless roles. At use case enactment time, each and every

one of these identifiers becomes bound to an object playing the corresponding Role for this

Context.

An example of a context could be a wire transfer between two accounts, where data models(the banking accounts) are used through roles named SourceAccount and DestinationAccount.

Interaction

The Interaction is "what the system does." The Interaction is implemented as Roles which are

played by objects at run time. These objects combine the state and methods of a Data (domain)

object with methods (but no state, as Roles are stateless) from one or more Roles. In good DCI

style, a Role addresses another object only in terms of its (methodless) Role. There is a special

Role called self which binds to the object playing the current Role. Code within a Role

method may invoke a method on self and thereby invoke a method of the Data part of the

current object. One curious aspect of DCI is that these bindings are guaranteed to be in place

only at run time (using a variety of approaches and conventions; C++ templates can be used to

guarantee that the bindings will succeed). This means that Interactionsthe Role methodsaregeneric. In fact, some DCI implementations use generics or templates for Roles.

A Role is a stateless programming construct that corresponds to the end user's mental model of

some entity in the system. A Role represents a collection of responsibilities. Whereas

vernacular object-oriented programming speaks of objects or classes as the loci of

responsibilities, DCI ascribes them to Roles. An object participating in a use case has

responsibilities: those that it takes on as a result of playing a particular Role. Most modern

programming languages have a way to express Roles, and to express the injection of Role

methods into objects, and implementation techniques vary depending the language. The

injection can be fully dynamic at run-time in languages like Ruby and Python; it is more static

in languages like Smalltalk/Squeak, Scala and C++. The Qi4j programming environment offers

a way to express role method injection into Java objects.In the above money transfer use case, for example, The role methods in the SourceAccount and

DestinationAccount enact the actual transfer.

8. Explain the five parts of a transition.

Sonata form

From Wikipedia, the free encyclopedia

Jump to: navigation,search

For the Sonata as a complete multi-movement structure, and related musical forms, seeSonata.

7/31/2019 Mc0069 Paper 1

11/14

Simplest sonata form pattern and its relation to binary form.[1]

Sonata form is a large-scale musical structure used widely since the middle of the 18th century (theearlyClassical period). While it is typically used in the firstmovement of multi-movement pieces, it is

sometimes used in subsequent movements as wellparticularly the final movement. The teaching of

sonata form in music theory rests on a standard definition and a series of hypotheses about the

underlying reasons for the durability and variety of the forma definition that arose in the second

quarter of the 19th century[2]. There is little disagreement that on the largest level, the form consists of

three main sections: an exposition, a development, and a recapitulation;[3] however, beneath this, sonata

form is difficult to pin down in terms of a single model.

The standard definition focuses on the thematic and harmonic organization oftonal materials that are

presented in an exposition, elaborated and contrasted in adevelopment and then resolved harmonicallyand thematically in a recapitulation. In addition, the standard definition recognizes that an introduction

and a coda may be present. Each of the sections is often further divided or characterized by the

particular means by which it accomplishes its function in the form.

Since its establishment, the sonata form became the most common form in the first movement of works

entitled "sonata", as well as other long works of classical music, including the symphony,concerto,

string quartet, and so on.[3]Accordingly, there is a large body of theory on what unifies and

distinguishes practice in the sonata form, both within eras and between eras. Even works that do not

adhere to the standard description of a sonata form often present analogous structures or can be

analyzed as elaborations or expansions of the standard description of sonata form.

Defining 'sonata form' According to the Grove Dictionary of Music and Musicians, sonata form is "the

most important principle of musical form, or formal type, from theClassical period well into the20th

century".[4] As a formal model it is usually best exemplified in the first movements of multi-movement

works from this period, whetherorchestral orchamber, and has, thus, been referred to frequently as

"first-movement form" or "sonata-allegro form" (since the typical first movement in a three- or four-

movement cycle will be in allegro tempo). However, as what Grove, following Charles Rosen, calls a

"principle" a typical approach to shaping a large piece ofinstrumental music it can be seen to be

active in a much greater variety of pieces andgenres, from minuet toconcerto to sonata-rondo. It also

carries with it expressive and stylistic connotations: "sonata style", forDonald Tovey as for other

theorists of his time, was characterized by drama, dynamism, and a "psychological" approach to theme

and expression.[4]

Although the Italian termsonata often refers to a piece in sonata form, it is essential to separate the

two. As the title for a single-movement piece of instrumental musicthe past participle ofsuonare, "to

sound," as opposed to cantata, the past participle ofcantare, "to sing""sonata" covers many pieces

from the Baroque and mid-18th century that are not "in sonata form". Conversely, in the late 18th

century or"Classical" period, the title "sonata" is typically given to a work composed of three or four

movements. Nonetheless, this multi-movement sequence is not what is meant by sonata form, which

refers to the structure of an individual movement.

The definition of sonata form in terms of musical elements sits uneasily between two historical eras.

Although the late 18th century witnessed the most exemplary achievements in the form, above all fromJoseph Haydnand Wolfgang Amadeus Mozart, compositional theory of the time did not use the term

"sonata form". Perhaps the most extensive contemporary description of the sonata-form type of

movement may have been given by the theoristH. C. Koch in 1793: like earlierGerman theorists and

7/31/2019 Mc0069 Paper 1

12/14

7/31/2019 Mc0069 Paper 1

13/14

I have numerous role models, from my daughter, who reminds me what is really important in life, to my boss anddear friend, who encourages me to think and use the power of my voice and the strength of my fist. My motherhas always taught me that you can be anyone or anything you want to be and my sister showed me whatcourage really was. Jessica

I believe people who are role models know that they are, whether they like it or not. It is their behaviorthat people look up to. It is their leadership qualities that others want to see and model. It is the smilethat they give to others. It is the look you get. All of the above. (unattributed)

If you are out in the community, your community, you are being looked at. All the good things you do reflectyourself and your family. Who said life was fair? We are here to take care of one another and if it meansmodeling healthy behavior, then someone has to do it. Go for it. This is taught to us by our parents, respectedcommunity person or other family member, etc. Irma

To me I think a Good Role Model is a person who tells, or influences you to make the right choice in life.Like for example my mother she always tells me "youre not gonna get nowhere in life until you prove itto yourself" whatever that means (huh). But if I didn't have anyone like my mother to remind meeveryday. . . I might be that lazy, oh lazy young lady rocking in my chair, doing nothing for myself but,getting old. But YES my mother is the greatest role model for me. Why? The answer is that she believesin everyone has a dream like Dr.King said . . . My mother a fine role model for me and my sisters. Lina

I think role models have changed over the generations. People used to describe their role models as beingpeople they didn't know i.e. movie stars and athletes. Now, (evident by this discussion) people tend to find rolemodels that are in some way or another involved in their lives. I think this is great, and it emphasizes one of myfavorite sayings, "It takes a village to raise a child." Nikki

I think the other piece about a role model that is important is that it is not just someone who you look upto or is successful, but someone who has had to go through similar struggles/ challenges as we. Noa

I agree with everyones ideas about what a role model SHOULD be and what characteristics they SHOULDhave, but to give someone the label of being a role model is telling them that you are, or you would like to usethem as an example to young children and other people who "are not on the right track" and basically sayingthat you should "be like" or consider "following his/her foot steps". What I'm getting at is we need to take theother persons feelings into consideration for example: I would never consider myself a role model for the simplefact that I have problems of my own and I feel pressured, and I'm not perfect; it just so happens that I stumbledupon the most wonderful opportunity, and was empowered to make my own decisions in life to set my goals. Ifound my passion and I plan to build my future around my goals. In conclusion I would just like to encourage

people to not just slap a label on anyone. Regena

Whether you like it or not the choice you make or stumble upon make you who you are. YOU areMAKING those choices, whether they are right or wrong and it doesn't look like they are steering you inthe wrong directions. I always tell people, whether you like it or not people are looking at you, for betteror worse. Its hard, but somebodys got to do it. And when you fall, they will be there to say "I told youso." Good lesson learned and you keep right on going. Irma

Gena, I agree it's hard to label people a role model, but i just think of it as a friend we look up to or learn thingsfrom. Usually those are people who are a little older cuz they explain their insights so well, but then again mypeers are also role models, like you Gena, cuz it reminds me that young people like myself go thru problemssometimes and still keep goin. i think that as long as someone is honest and doesn't pretend to know all the

right things to say or do, then that's the best example!

Also, I have to mention my Beautiful Mother as my personal and all time shero. Everytime that I start to feelsorry for myself, I think of all the shit she's been thru and worked at, and put up with, and survived, andsacrificed, and accomplished. She had to come here to the U.S. only knowing my father and when my dadturned out to abuse alcohol and beat my mother, she had no where to go 'cuz he was the only person she knew

7/31/2019 Mc0069 Paper 1

14/14

and she was an "immigrant" so she just stuck it thru and slowly independized herself she learned to drive, savedmoney, established residency and finally left my dad with our support (me and my sisters). And even still, shehad to deal with my sisters and mine attitudes while growing up - I just love her so much and try to show her thateveryday a little more. Kaira

Points well taken! I guess it's just the Big word ROLE MODEL. I have to admit as much as I hate to labelpeople you grrls are right. I know people are watching me whatever I do. I guess that's why I strive sohard to be the best at whatever I do, I more so liked the word Kaira used "Example." Basically I thinkthat Role Model sounds so demanding, and example is making more of a statement like you can do it

too (more humble I guess). Regena