11AOF - AS91880 - DIGITAL MEDIA
VISUALISE YOUR ARCHITECTURE
Click this link to open the architecture project data sheet - add your info & share it with your client for them to add their project info.
Use this info to inform your project design - you are the architect designing to your clients needs/wants.
Use this info to inform your project design - you are the architect designing to your clients needs/wants.
ARCHITECTURE PROJECT DATA SHEET
ASSESSMENT: AS91880 - Develop a digital media outcome
ACHIEVEMENT STANDARD: nzqa.govt.nz/ncea/AS91880
NZ CURRICULUM AREA: Digital Technologies
CREDITS: 4
ASSESSMENT TITLE: Visualise your architecture using digital technology
ASSESSMENT BRIEF: Create digital media content to visualise your ideas for an architecture project
DESCRIPTION: Use drawings, physical & 3D models & digital images to visualise the development of your architecture project
ACHIEVEMENT STANDARD: nzqa.govt.nz/ncea/AS91880
NZ CURRICULUM AREA: Digital Technologies
CREDITS: 4
ASSESSMENT TITLE: Visualise your architecture using digital technology
ASSESSMENT BRIEF: Create digital media content to visualise your ideas for an architecture project
DESCRIPTION: Use drawings, physical & 3D models & digital images to visualise the development of your architecture project
KEY IDEAS FOR ASSESSMENT: seniorsecondary.tki.org.nz/Technology/Digital-technologies/Assessment
ASSESSMENT CLARIFICATIONS: nzqa.govt.nz/ncea/subjects/digital-technologies/clarifications/level-1/as91880
ITERATIVE IMPROVEMENT: nzqa.govt.nz/ncea/subjects/digital-technologies/clarifications/level-1/iterative
ASSESSMENT CLARIFICATIONS: nzqa.govt.nz/ncea/subjects/digital-technologies/clarifications/level-1/as91880
ITERATIVE IMPROVEMENT: nzqa.govt.nz/ncea/subjects/digital-technologies/clarifications/level-1/iterative
NZQA ASSESSMENT MARKING SCHEDULE - LINK
DEFINITIONS OF ASSESSMENT
"Digital media" is the digital technology tools & outcomes that learners use to develop their architecture project.
The digital media tools learners use are: The Internet, Google Docs, Google Earth, Google Maps, Sketchpad, Sketchup or Minecraft or Tinkercad, Navidia Guagan AI images, Photoshop or Pixlr, Google Drive/C:Drive, camera to take photos of drawings.
The digital media tools learners use are: The Internet, Google Docs, Google Earth, Google Maps, Sketchpad, Sketchup or Minecraft or Tinkercad, Navidia Guagan AI images, Photoshop or Pixlr, Google Drive/C:Drive, camera to take photos of drawings.
- The Internet > research & saving images of architecture > using these images as design inspiration.
- Google Earth > explore site locations > taking screenshots > using the scribble tool to annotate screenshots.
- Google Maps > explore site locations > taking screenshots or making location gif animations with Screencastify.
- Doing drawings to develop ideas > taking photos of your drawings > using these photos to show iterative design improvement.
- Sketchpad > doing online drawings of your architecture project > using these images in your Pecha Kucha
- Navidia Gaugan AI > doing AI drawings of landscapes > using these images in your Pecha Kucha.
- Making a physical model of your architecture project > taking photos of the model > adding these photos to your Pecha Kucha.
- Sketchup, Minecraft or Tinkercad 3D modeling software > 3D model your architecture from your drawing ideas.
- Photoshop or Pixlr > create an image showing your architecture in its site location > add this image to your Pecha Kucha.
- Google Drive/C:Drive > organise your files used during the project > 'data integrity'. digital.school.nz/project-information.
- Google Earth > explore site locations > taking screenshots > using the scribble tool to annotate screenshots.
- Google Maps > explore site locations > taking screenshots or making location gif animations with Screencastify.
- Doing drawings to develop ideas > taking photos of your drawings > using these photos to show iterative design improvement.
- Sketchpad > doing online drawings of your architecture project > using these images in your Pecha Kucha
- Navidia Gaugan AI > doing AI drawings of landscapes > using these images in your Pecha Kucha.
- Making a physical model of your architecture project > taking photos of the model > adding these photos to your Pecha Kucha.
- Sketchup, Minecraft or Tinkercad 3D modeling software > 3D model your architecture from your drawing ideas.
- Photoshop or Pixlr > create an image showing your architecture in its site location > add this image to your Pecha Kucha.
- Google Drive/C:Drive > organise your files used during the project > 'data integrity'. digital.school.nz/project-information.
OBJECTIVES
The objective of this 11AOF assessment is for you to experience using digital technology to develop a digital media outcome by visualising an architecture design suitable for the 'end user' (client who your designing for)
Below are the assessment key words & definitions you need to consider for your architecture project.
-Develop: Design an architecture project for a client. Consider, places, spaces & culture when developing your design ideas.
-Digital media: The digital technologies as described above.
-Outcome: Your final architecture project & the Pecha Kucha documents that showcase your project development.
-Use design elements: Colour, shape, space, form, texture, geometry, proportion, materials.
-Design for purpose & end users: An architecture for your client.
-Apply data integrity: File & data management of the content you create digital.school.nz/project-information.
-Testing procedures: Self review, friend review & learning leader feedback to improve your project by testing your ideas with others.
-Describing relevant implications: Write about the Aesthetics & End-user considerations of your project.
-Iterative improvement throughout design/development/testing process: How you evolve your design from first to final concept.
-Applying design elements effectively: Considering the 8 design elements throughout your project to make your architecture better.
Below are the assessment key words & definitions you need to consider for your architecture project.
-Develop: Design an architecture project for a client. Consider, places, spaces & culture when developing your design ideas.
-Digital media: The digital technologies as described above.
-Outcome: Your final architecture project & the Pecha Kucha documents that showcase your project development.
-Use design elements: Colour, shape, space, form, texture, geometry, proportion, materials.
-Design for purpose & end users: An architecture for your client.
-Apply data integrity: File & data management of the content you create digital.school.nz/project-information.
-Testing procedures: Self review, friend review & learning leader feedback to improve your project by testing your ideas with others.
-Describing relevant implications: Write about the Aesthetics & End-user considerations of your project.
-Iterative improvement throughout design/development/testing process: How you evolve your design from first to final concept.
-Applying design elements effectively: Considering the 8 design elements throughout your project to make your architecture better.
DESIGN ELEMENTS
NZQA define 'design elements' as colour, texture, shape, geometry, space, form, proportion, materials.
How have you incorporated design elements into your architecture project?
Example of colour: w3schools.com/colors/colors_picker.
Example of texture: concrete house textures dezeen.com/texture-concrete-living-rooms-interiors.
Example of shape + geometry: these images are descriptions of 2 dimensional shapes/geometry
STAGES
ACHIEVED - MERIT - EXCELLENCE
ACHIEVED
*Using appropriate tools, techniques & design elements for the purpose & end users
*Applying appropriate data integrity & testing procedures in the development of the outcome
*Describing relevant implications
1. Use most of the tools & techniques as described above to "visualise your architecture"
2. Design elements are colour, shape, space, form, texture, geometry, proportion, materials.
How have you incorporated design elements in your architecture project?
3. End users (your client) are who your designing your architecture for. As you develop your project you need to do drawings to visualise your ideas and regular feedback from your client to improve your design.
For Merit or Excellence grade you need to document their feedback & say how you improved your project based on their feedback - this is part of "iterative design improvement".
4. Applying appropriate Data integrity how you use your Google Drive &/or your C:Drive to save images, project information documents, Minecraft or Sketchup files, photos etc you create during your project digital.school.nz/project-information.
Name your files & docs & data properly in folders so its easy to find. Are you using an 11AOF file system on your computer?
Take a screenshot of your data integrity & add it to your Pecha Kucha to show you using correct data integrity.
5. Testing procedures is "self review, friend review & learning leader feedback to improve your project by testing your ideas with others". Add a page to your Pecha Kucha & write about how you tested your ideas throughout your project.
6. 'Describing relevant implications' is about the Aesthetics & End-user considerations of your project.
Add pages at the end of your Pecha Kucha & write about the aesthetics & end user considerations of your architecture.
Aesthetics definition: "appreciation of beauty & artistic taste"
- Write about the design aesthetics of your architecture.
- You can refer to your 4 inspirational architecture document or the characteristics of the design era you researched.
- How did you incorporate the 8 design elements into your architecture project to make it more aesthetic?
End-user considerations:
- What does you client think of your final design?
- How does your architecture meet the needs of your client?
END USER FEEDBACK FORM
*Using appropriate tools, techniques & design elements for the purpose & end users
*Applying appropriate data integrity & testing procedures in the development of the outcome
*Describing relevant implications
1. Use most of the tools & techniques as described above to "visualise your architecture"
2. Design elements are colour, shape, space, form, texture, geometry, proportion, materials.
How have you incorporated design elements in your architecture project?
3. End users (your client) are who your designing your architecture for. As you develop your project you need to do drawings to visualise your ideas and regular feedback from your client to improve your design.
For Merit or Excellence grade you need to document their feedback & say how you improved your project based on their feedback - this is part of "iterative design improvement".
4. Applying appropriate Data integrity how you use your Google Drive &/or your C:Drive to save images, project information documents, Minecraft or Sketchup files, photos etc you create during your project digital.school.nz/project-information.
Name your files & docs & data properly in folders so its easy to find. Are you using an 11AOF file system on your computer?
Take a screenshot of your data integrity & add it to your Pecha Kucha to show you using correct data integrity.
5. Testing procedures is "self review, friend review & learning leader feedback to improve your project by testing your ideas with others". Add a page to your Pecha Kucha & write about how you tested your ideas throughout your project.
6. 'Describing relevant implications' is about the Aesthetics & End-user considerations of your project.
Add pages at the end of your Pecha Kucha & write about the aesthetics & end user considerations of your architecture.
Aesthetics definition: "appreciation of beauty & artistic taste"
- Write about the design aesthetics of your architecture.
- You can refer to your 4 inspirational architecture document or the characteristics of the design era you researched.
- How did you incorporate the 8 design elements into your architecture project to make it more aesthetic?
End-user considerations:
- What does you client think of your final design?
- How does your architecture meet the needs of your client?
END USER FEEDBACK FORM
MERIT
*Using information from testing procedures to improve the quality & functionality of the outcome
*Addressing relevant implications
1. Go into greater detail about how you used testing procedures to improve the quality & functionality of your design.
For example: You can use images of your drawings compared to screenshot images of your 3D modeling to show improvement.
For example: How do the key features of your design relate to an era of architecture you researched at the start of the project?
For example: Get more than one person to give you feedback throughout your project, keep detailed feedback notes & describe how you improved the 'quality & functionality' of your design based on the feedback by others.
2. For an Achieved grade you need to 'describe' relevant implications. For a Merit grade you need to 'address' relevant implications. Addressing relevant implications is explaining in greater detail how you think about Aesthetics & End-user considerations.
*Using information from testing procedures to improve the quality & functionality of the outcome
*Addressing relevant implications
1. Go into greater detail about how you used testing procedures to improve the quality & functionality of your design.
For example: You can use images of your drawings compared to screenshot images of your 3D modeling to show improvement.
For example: How do the key features of your design relate to an era of architecture you researched at the start of the project?
For example: Get more than one person to give you feedback throughout your project, keep detailed feedback notes & describe how you improved the 'quality & functionality' of your design based on the feedback by others.
2. For an Achieved grade you need to 'describe' relevant implications. For a Merit grade you need to 'address' relevant implications. Addressing relevant implications is explaining in greater detail how you think about Aesthetics & End-user considerations.
EXCELLENCE
*Iterative improvement throughout the design, development & testing process
*Applying design elements effectively
1. 'Iterative improvement' is a design method based on constant prototyping, testing, analyzing, refining, testing & feedback by others throughout the design process. "Iteration" of a design occurs when changes & refinements are made throughout this process.
This process is intended to ultimately improve the quality & functionality of a design.
For Excellence in this assessment you need to document "iterative improvement" of the design of your architecture project.
This is NZQA's description of "iterative improvement". www.nzqa.govt.nz/ncea/subjects/digital-technologies/clarifications/level-1/iterative
For Excellence in 91880, iterative improvement requires that the learner develop a functional outcome using documented cycles of improvement. This may include adding features to the outcome. This needs to be shown through deliberate cycles of improvement based on testing and trialling rather than just incremental development. Iterative improvement is more than just debugging or correcting errors in a non-functioning outcome. It is expected that students will produce a functioning outcome for an Achieved grade. Iterative improvement should be aimed at making a better product. This evidence needs to be provided for moderation. Students may be able to provide sufficient evidence of the development of the outcome using, for example, annotated screenshots, ‘commit’ messages, commenting within the source files of the outcome. They may not need to submit all the previous versions of the outcome.
2. 'Applying design elements effectively' is justifying the design decisions you made throughout the process of your project.
*Iterative improvement throughout the design, development & testing process
*Applying design elements effectively
1. 'Iterative improvement' is a design method based on constant prototyping, testing, analyzing, refining, testing & feedback by others throughout the design process. "Iteration" of a design occurs when changes & refinements are made throughout this process.
This process is intended to ultimately improve the quality & functionality of a design.
For Excellence in this assessment you need to document "iterative improvement" of the design of your architecture project.
This is NZQA's description of "iterative improvement". www.nzqa.govt.nz/ncea/subjects/digital-technologies/clarifications/level-1/iterative
For Excellence in 91880, iterative improvement requires that the learner develop a functional outcome using documented cycles of improvement. This may include adding features to the outcome. This needs to be shown through deliberate cycles of improvement based on testing and trialling rather than just incremental development. Iterative improvement is more than just debugging or correcting errors in a non-functioning outcome. It is expected that students will produce a functioning outcome for an Achieved grade. Iterative improvement should be aimed at making a better product. This evidence needs to be provided for moderation. Students may be able to provide sufficient evidence of the development of the outcome using, for example, annotated screenshots, ‘commit’ messages, commenting within the source files of the outcome. They may not need to submit all the previous versions of the outcome.
2. 'Applying design elements effectively' is justifying the design decisions you made throughout the process of your project.
DIGITAL MEDIA PROJECT EXAMPLE
Develop your project with drawings, models & images to visualise your architecture project.
This is an example project I created called SnakeTower that shows the
'iterative design development' process to create digital media for this assessment.
A full description of this example project is at architectureschool.co.nz/snaketower
'iterative design development' process to create digital media for this assessment.
A full description of this example project is at architectureschool.co.nz/snaketower
Iterative drawings of a snake
Design inspiration board
Drawings & physical model
Colour studies
3D model
Photoshop images of SnakeTower on the site
