Scribd
Upload
10 views16 pages

Analysis

The analysis section should include a detailed description of the problem being investigated, clear evidence that research has been performed, and a clear set of objectives that will guide later sections of the project. Specifically, it should describe the problem, review current solutions, propose the student's solution based on research, outline user requirements, provide an introductory design, discuss hardware/software requirements and limitations, and establish measurable objectives. The objectives will be used to guide the project and evaluate whether the goals were achieved.

Uploaded by

ch.sohaibnasir1289
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
10 views16 pages

Analysis

The analysis section should include a detailed description of the problem being investigated, clear evidence that research has been performed, and a clear set of objectives that will guide later sections of the project. Specifically, it should describe the problem, review current solutions, propose the student's solution based on research, outline user requirements, provide an introductory design, discuss hardware/software requirements and limitations, and establish measurable objectives. The objectives will be used to guide the project and evaluate whether the goals were achieved.

Uploaded by

ch.sohaibnasir1289
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 16

ANALYSIS

ANALYSIS
In the analysis section we are looking for:

• A detailed description of the problem / investigation

• Clear evidence that research has been performed (dialogue)

• A clear set of objectives that will be useful across the later sections of the project

• Modelling of the proposed solution that will be of use to later design work

? Having read the analysis stage:


Do you understand what the project is going to do?
Has the student set clear objectives that are detailed enough?

2 Copyright © AQA and its licensors. All rights reserved.


MARK SCHEME
CONTENTS
1. Background (story) of the computational problem/topic and how you intend to solve this.

2. Current/similar solutions or systems – researched and documented.

3. Your solution based on the research you have discovered.

4. User requirements / interactions.

5. Introductory design of your system.

6. Hardware / Software requirements and limitations.

7. Objectives (Success Criteria).


1. BACKGROUND STORY
CONTENTS

• 1 page
• What current problems are there surrounding your topic area?
– Limitations
– User interaction problems
– Real time
– Exist but not efficient??

• Brief introduction to a possible solution to the problem (you’ll discuss this in more technical
detail later, but a short introduction will help the mark see the direction your taking with your
project)
CONTENTS
CONTENTS

2. CURRENT – SIMILAR SYSTEMS /


SOLUTIONS
- 1 page per researched system
- Research a range of different systems and analyse their success (approx. 3 – 1 page for each).
- For each system:
1. Discuss how the system works computationally.
2. User interaction with the system.
a. How do they communicate / interact with the user?
b. Could complete questionnaire / focus group and feedback on the results of that.
3. Analyse its strengths and weaknesses.
a. Strengths – Why are they strengths? Could you implement these strengths into your
system? If so, why?
b. Weaknesses – Identify them. Why are they weaknesses? How will you avoid these
weaknesses?
** Use diagrams or images of the current systems to support your arguments.
** Make sure the points you make refer back to / are relevant to your project.
3. YOUR SOLUTION
CONTENTS

• 1 page
• This is where you will introduce your proposed solution to the marker.
• The solution must be based on the problems you earlier identified and the research you partook
in.
• Try to keep this discussion as technical as possible and veer away from aesthetics i.e. talk about
the way you are going to program it and how this code will improve or solve problems that
currently exist.
CONTENTS
4. THE USER
CONTENTS

• ½ page
• Identify the user.
• Discuss how the user will interact with the system.
• May want to include a brief idea of variables / inputs / outputs as a result of the user
interaction.
CONTENTS
CONTENTS

5. INTRODUCTORY
DESIGN
• Aim is to see how the system
will work at first glance.
HARDWARE / SOFTWARE
CONTENTS

/LIMITATIONS
• 1 page for all
• Identify and describe the hardware and software requirements for your proposed solution.
• Limitations – It is ok to identify possible limitations of your system as long as they don’t have
a negative affect of your program (i.e. if they make it look worse than what’s already out
there!).
5. OBJECTIVES

• A really important part of your Analysis.


• These objectives will be used throughout the whole of your coursework, hence they must be
measurable i.e. you can test against them when running your program.
BAD EXAMPLE
• - Not enough.
• - Doesn’t identify clearly if the
objective is an input, process or
output.
• - A single objective can cover
several objectives e.g. no9.
5. OBJECTIVES – WHAT TO CONSIDER
1. Make sure they are a measurable.
2. Make sure a single objective covers a single point (e.g. “The user can input a username and
password and store these details on a database”- this one sentence can actually broken down into
at least 3 objectives).
3. Make sure these objectives are evident in your work. You will be testing against these in later
sections so if they don’t exist, they need to be either implemented or not included.
4. Try and include objectives that relate to your research, e.g. if in your research you found a system
that doesn’t store usernames for later use, include and objective that does this.
5. Categorise the objectives into sections e.g. “Welcome Page” , “User Options”, “Level 1”,
“Customers Table” etc etc. This will help you when you come to evidence your work in the
Development section.
*Number your objectives, so you can refer back to them during design, development, testing, eval.

You might also like