BTEC IT - Unit 4, learning aim A / Assignment 1 (DISTINCTION)
33 views 1 purchase
Course
Unit 4 - Programming
Institution
PEARSON (PEARSON)
This is a completed assignment for BTEC IT. This is assignment 1 for Unit 4 programming (Learning aim A). This document was achieved to a distinction standard and includes a bibliography of sites used.
It is broken down into sections so that it is easier to see where the merit and distinction s...
,Introduction:
In this report I will be discussing the many programming principles that are required in order to create a successful solution. I will be covering aspects of computational
thinking, giving real life examples of software applications, discussing different programming languages and their features as well as analysing and evaluating these
different principles to determine how effective they are.
Decomposition:
The process of decomposition means to break down a problem into smaller sub problems that are much easier to manage. It is a crucial step, especially for much larger,
complex problems to ensure success by allowing you to focus on each individual problem and its details.
o Identifying and describing problems and processes:
When identifying and describing problems and processes, the terminology used needs to be relevant to the given problem. For example, if the problem was based
around creating a video game you would ideally want to use terms related such as graphics, interface, character etc.
o Breaking down problems and processes into distinct steps:
Although one large problem can be decomposed into smaller sub problems, we can break these sub problems down even more. For example, during the creation of a
video game the game may be broken down into smaller components such as Characters and maps, which are broken down once again into even smaller components
such as character appearance or map design. Typically, programmers implement a visual representation of this, through the top-down design, otherwise known as
stepwise refinement. An example of this is show below, where we can see how each problem is constantly broken down until it becomes a single task.
o Describing problems and processes as a set of structure steps:
Once this stage has been reached, you must ensure that the problems and processes that you have decomposed are noted down as a set of steps, like the diagram above.
This makes the entire problem straightforward for you and others to follow.
o Communicating the key features of problems and processes to others as relevant:
, o Identifying and interpreting common differences between problems and processes:
This is a similar process to the last one, however, instead of looking for similarities we are now aiming to discover differences. So, instead of recognising the features
as patterns, we recognise them as differences.
o Identifying individual elements within problems:
To point out the individual elements, we must examine the problem and identify inputs, outputs and processes (which include selection and iteration).
o Describing patterns that have been identified
After this, describe the patterns that have been identified. To be mor specific, you can describe what these reoccurring patterns are and what they do.
o Making predictions based on identified patterns:
Now that we have listed and described all patterns, predictions need to be made based on them. For every pattern, you need to aim to predict how they can be reused in
the future or how they might appear under similar circumstances.
Pattern generalisation and abstraction:
By computing definition, abstraction is the process in which you remove excessive details in order to keep the key features, allowing a programmer to have a feature
knowing exactly how it functions as the irrelevant pieces have been removed, or “abstracted”.
Abstraction has two parts when put into practice.
o Identifying information required to solve an identified problem:
Firstly, we need to group the information that we need before solving the problem. This is done by:
- Understanding what information is needed
- Having a reason as to why this information is required
- Knowing the format in which this information must be presented in
- Knowing how soon the information is needed to prevent the solution from being delayed
o Filtering out information required to solve an identified problem:
Now, this information needs to be filtered. In order to achieve this, we need to figure out:
- The information that is no longer needed, as it created distraction
- Justifying why you decided to exclude it
Representation of problem elements:
To represent the problem elements, we must list the:
The benefits of buying summaries with Stuvia:
Guaranteed quality through customer reviews
Stuvia customers have reviewed more than 700,000 summaries. This how you know that you are buying the best documents.
Quick and easy check-out
You can quickly pay through EFT, credit card or Stuvia-credit for the summaries. There is no membership needed.
Focus on what matters
Your fellow students write the study notes themselves, which is why the documents are always reliable and up-to-date. This ensures you quickly get to the core!
Frequently asked questions
What do I get when I buy this document?
You get a PDF, available immediately after your purchase. The purchased document is accessible anytime, anywhere and indefinitely through your profile.
Satisfaction guarantee: how does it work?
Our satisfaction guarantee ensures that you always find a study document that suits you well. You fill out a form, and our customer service team takes care of the rest.
Who am I buying this summary from?
Stuvia is a marketplace, so you are not buying this document from us, but from seller therezzo. Stuvia facilitates payment to the seller.
Will I be stuck with a subscription?
No, you only buy this summary for $11.67. You're not tied to anything after your purchase.
