Assessment Feedback Sheet
Overall Assessment
Grade Achieved
Learner Name
Assessor Name
Qualification Title BTEC Level 3 National Extended Diploma in Computing
Unit/Module No./Title Unit 23: System Methodology
Assignment No./Title Unit 23 – Principals of system methodology
Learning Aim(s) A: Investigate the principles of systems methodology and systems
techniques used to solve computing problems
Issue Date Planned Submission Date Actual Submission Date
First/Second Submission
Criteria Criteria Assessor’s Feedback Your feedback should include:
Achieved What the learner has done well. (Knowledge, skills, etc.)
What the learner has not achieved and what was missing.
Information or guidance available to the learner they could have drawn on (e.g. class
notes; handouts; resources in assignment brief etc.)
P1
Explain the stages of the software
development lifecycle. ☐
P2
Explain the principles of systems
methodologies used in the
☐
problem solving process.
M1
Compare the use of the applied
software development life cycle ☐
model and systems methodology
in the problem-solving process
against alternative options.
Evaluate the use of the applied
software development life cycle
model and systems methodology ☐
in the problem-solving process.
BTEC Rules
All resubmissions must be authorised by the Lead Internal Verifier. Only one resubmission is possible per assignment, providing:
The learner has met initial deadlines set in the assignment, or has met an agreed deadline extension.
The tutor considers that the learner will be able to provide improved evidence without further guidance.
Evidence submitted for assessment has been authenticated and accompanied by a signed and dated declaration of authenticity by the learner.
Any resubmission evidence must be submitted within 10 working days of receipt of results of assessment (BTEC only)
Wider Skills (Linked to Positive Futures) Comment on the quality of the learner work, the learner’s process and practice during assessment, research
skills, presentation, general behaviour and conduct, meeting deadlines, etc.
I certify that, to the best of my knowledge, the evidence submitted for this assignment/assessment is the learner’s own. I
Assessor Declaration understand that false declaration is a form of malpractice.
Assessor Signature: Date:
, I certify that the evidence submitted for this assignment/assessment is my own. I have clearly referenced any sources
Learner Declaration used in the work. I understand that false declaration is a form of malpractice.
09/01/23
Learner Signature: Date:
Learner Actions
Actions linked to
Learner’s Targets/Actions
the following
What needs to be developed to improve future work?
Positive
Futures outcomes
☐ Confidence
☐ Commitment
☐ Collaboration
☐ Resilience
, Student ID Number:
Name of teacher:
Word Count:
Unit 23 – Systems Methodology Assignment
Unit 23 – Systems Methodology
SECTION 1: INTRODUCTION
Systems methodology is a framework used in software development to structure each development
stage. Systems methodology (framework) helps you to formulate and structure thinking about a
problem scenario by providing an action-oriented process of inquiry and taking action to improve it.
I will be learning about systems methodology approaches used by engineers to solve complex
problems and then myself research into the principles of systems methodology and the tools and
techniques used to solve a complex problem. I will select and apply different systems methodologies
to solve a formulated problem, and reflect and review on my skills and performance afterwards.
3
,Table of Contents
Section 1: Introduction.............................................................................................................................................3
Section 2: Learning Aim A – Investigate the principles of systems methodology and systems techniques used to
solve computing problems.......................................................................................................................................5
References..............................................................................................................................................................39
4
,SECTION 2: LEARNING AIM A – INVESTIGATE THE PRINCIPLES OF SYSTEMS
METHODOLOGY AND SYSTEMS TECHNIQUES USED TO SOLVE COMPUTING
PROBLEMS
Task 1 (A1): The Software Development Life Cycle
A: Explain the stages of the Software Development Life Cycle
Section Intro:
Software Development Life Cycle (SDLC) is a ontological process used by the software industry to
plan, design, develop, test, maintain and complete high-quality software in the shortest possible
production time and cost estimates. The primary goal of SDLC is to meet or exceed client
expectations, whilst following the ISO 12207 (which is the international standard for software lifecycle
processes. {By providing guidelines to ensure quality assurance.})
The idea behind SDLC originated in the 1950s-1960s; when computer science progressed rapidly and
the as a result the complexity and the scale of programming grew too. This in turn led to the concept
of structured programming. With time, structured programming needed more professional and tactical
development models to create high quality software(s) and this sparked the beginnings of the SDLC.
Figure 1.0 shows a graphical representation of the stages involved in a typical SDLC.
Key Drivers
As they say there is a reason for everything, Systems Analysis also has a solid reason or sometimes
reasons for it to take place. These reasons are known as Key Drivers and there are a variety of key
drivers. For example:-
Need for Business Growth: Organisations use Systems Analysis when they decide that they have
reached a point where they can expand their business and seek additional profits. This can be done
digitally by upgrading their systems to make them more efficient and productive or it can be physically
which is to expand their business locally or internationally.
5
, This typically happens by a systems analyst who gives advice on systems upgradation (depending on
the budget and resources available) and also provides business tactics and strategies.
Almost all the known companies have gone through this process, for example let’s take the tech giant
Apple. It started in Steve Jobs’ (CEO) house garage and now it’s hard to find anywhere without an
Apple product.
Company Acquisition: This is heavily dependent on rivalry and chemistry in companies; when
companies decide to merge together (i.e. to get ahead at competition in the market) or some other
reason.
This is done by a systems analyst who checks for any compatibility issues in the two (or more)
companies and then makes suggestions based upon it.
A prime example of this is Pendleton College which now comes under Salford City College which is
an organisation that also takes responsibility over other sixth form colleges such as Eccles Sixth form
College.
Productivity Rate: The emerging trend of 2021. Although there are many ways to increase
productivity in an organisation or even as a individual but one that really stands out is using
Technology to work for you. This process is known as automation. Time and time again automation
has proven to exponentially increase productivity rates and save businesses. For example, in the mid
1800s cash theft from the counter was a common problem, receipts could be easily altered or
discarded and there were no cameras, and no software to keep an eye on your employees. This is
when Henry Patterson, a resident in Ohio opened up a business of coal mines in Ohio. There was
little competition and the flow of customers was steady, but his still business was struggling to stay
afloat in the market. This is when he realized his money was being stolen from him. To get around
this, he discovered a new invention of his time called Ritty’s Incorruptible Cashier. It was the first ever
cash register and it automatically locked the cash register after transaction took place and thus
receipts couldn’t be altered with. This resulted in the business not only running smooth but also saving
$5,000, equivalent of $100,000 today! A good systems analyst would always ask themselves if the
task can be automated.
Legal Requirements: There might be a need for systems analysis for existing businesses, whose
owners/managers need to make sure that they are meeting all the legal requirements of the country
they are operating in. For instance, a company that wants to expand their business internationally, (in
this case in the UK) then they would have to make sure that there company meets the criteria for legal
requirements like the General Data Protection Act.
Stages of the Software Development Life Cycle Model
In this section, I will explain the stages and their purposes: -
Stage 1: Planning and Requirement Analysis
The planning phase in a typical SDLC is about specialist(s) collecting precise requirements from the
client(s) to first identify and later on form a fine-tuned solution to their needs, as well as identifying
potential risks. This is typically done through getting the client to fill in questionnaires specific to the
project, and if this stage is reviewed in another iteration of the cycle then the existing documents are
reviewed to see how the project is progressing.
From a Business point of view, the three fundamentals to be vitally collected from the client are:-
♦ Time
♦ Resources
♦ Budget/Costs
After collecting the specific needs, financial and availability estimates from the client, the specialists
can then move onto the final phase of this stage, which is to conduct the feasibility study of the
6
