DSDN142: Ben Manu
Monday, 30 May 2011
Thursday, 26 May 2011
Project 3 - Write Up
I have chosen Objects as my coding concept, focusing on how an Object is built from its Class. I have chosen this concept because it is a key element of object oriented programming and by providing people with a clear understanding of how Objects are treated by a program will hopefully give them a better understanding of this style of coding. An Object is an entity created by a predefined coded Class, allowing a program to build objects when required. The coded Class provides a blue print which the program uses to build an Objects initial State. Think of a Class as a Cookie Cutter, it provides the shape for the Cookie, and the Object is the Cookie once cut. By using a Class to create Objects it provides the program the ability to easily create multiple Objects with same or similar attributes. My exhibition piece demonstrates the process of building Objects from its Class by showing multiple paper block models as Objects in their constructed state, and the single blueprint of these Objects as the paper stencil used to cut out and fold to make the models, between which lies some deconstructed pieces of the models, allowing a person to take the role of the program to construct their own Object.
Monday, 23 May 2011
Project 3 - update
changed from model to one of thessse due to time and cost constraints. and these will be easy for people to make.
Sunday, 22 May 2011
Project 3 - update
instead of using models looking at using cubecraft, due to time constraints and cost factors and ease of use
Monday, 16 May 2011
Project 3 - 17/05
--my coding concept is objects, focusing on how its built from it's class.
--the class is like a blueprint, so i had the idea of showing the building process of an object through a flow chart, from its blueprint to the finished object.
--after thinking a bit more on this idea i thought it was a bit too straight forward in showing the process.
--after brainstorming more i remembered model plane kits, how its like a blueprint, can take it apart and build the plane.

--my idea is to create a model kit, to represent building an object from it's class
time/cost -- allocate time to design the kit, cost of materials- cardboard, printing
--the class is like a blueprint, so i had the idea of showing the building process of an object through a flow chart, from its blueprint to the finished object.
--after thinking a bit more on this idea i thought it was a bit too straight forward in showing the process.
--after brainstorming more i remembered model plane kits, how its like a blueprint, can take it apart and build the plane.

--my idea is to create a model kit, to represent building an object from it's class
time/cost -- allocate time to design the kit, cost of materials- cardboard, printing
Wednesday, 11 May 2011
Project 3 - Preliminary
The programming concept that I'm going to use is Objects, I have chosen this because It's an integral part of Object Oriented Programming.
Seeing as the idea of an Object is quite literal I'm going to focus on how an Object is built from its Class and Sub-Classes creating the Objects State, and how an Objects Behavior is affected with Functions.
With this in mind I've put the development of Objects into steps and have thought of design ideas around this. The first step being defining the Class, the second step affecting the Class Attributes and Behavior, and the third step the output of the Object.
1st Idea - Cookie Cutter
Class - Cookie cutter
Attributes - Icing
Object - Cookies
*has no behavior
2nd Idea - Object Program
Class - Ball
Attributes - Velocity, direction, colour, size
Object - Moving ball
*time consuming
3rd Idea - Blueprint -> Flowchart Diagram -> Image
Class - Blueprint image (vehicle)
Sub-Class - Blueprint image (different types of vehicles)
Attributes - Flowchart (Color-coded for State Attributes and Behavior Attributes)
Object - Image of Selected vehicle
*a path showing the selection process from Class to Object
*got to come up with attributes
Would like to incorporate the flowchart into a program but time constraints
time management plan - get it done by the 27th
cost/equipment - wall to stick paper on, paper printed on
Seeing as the idea of an Object is quite literal I'm going to focus on how an Object is built from its Class and Sub-Classes creating the Objects State, and how an Objects Behavior is affected with Functions.
With this in mind I've put the development of Objects into steps and have thought of design ideas around this. The first step being defining the Class, the second step affecting the Class Attributes and Behavior, and the third step the output of the Object.
1st Idea - Cookie Cutter
Class - Cookie cutter
Attributes - Icing
Object - Cookies
*has no behavior
2nd Idea - Object Program
Class - Ball
Attributes - Velocity, direction, colour, size
Object - Moving ball
*time consuming
3rd Idea - Blueprint -> Flowchart Diagram -> Image
Class - Blueprint image (vehicle)
Sub-Class - Blueprint image (different types of vehicles)
Attributes - Flowchart (Color-coded for State Attributes and Behavior Attributes)
Object - Image of Selected vehicle
*a path showing the selection process from Class to Object
*got to come up with attributes
Would like to incorporate the flowchart into a program but time constraints
time management plan - get it done by the 27th
cost/equipment - wall to stick paper on, paper printed on
Monday, 9 May 2011
Project 3 - pre 5
program that allows the user to fill in variables to make an object act in different ways. shows the modularity of objects
Subscribe to:
Posts (Atom)