0% found this document useful (1 vote)
1K views15 pages

Unit 30-Application Development-Reworded-2021

Uploaded by

Jimmy Cyrus
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (1 vote)
1K views15 pages

Unit 30-Application Development-Reworded-2021

Uploaded by

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

Higher Nationals

Internal verification of assessment decisions – BTEC (RQF)


INTERNAL VERIFICATION – ASSESSMENT DECISIONS
Programme title BITEC Higher National Diploma in Computing

Assessor Internal Verifier


Unit 30 – Application Development
Unit(s)
Inventory Control Application for BAUHINIA
Assignment title

Student’s name
List which assessment criteria Pass Merit Distinction
the Assessor has awarded.

INTERNAL VERIFIER CHECKLIST

Do the assessment criteria awarded match


those shown in the assignment brief? Y/N
Is the Pass/Merit/Distinction grade awarded
justified by the assessor’s comments on the Y/N
student work?
Has the work been assessed
Y/N
accurately?
Is the feedback to the student:
Give details:
• Constructive? Y/N
• Linked to relevant assessment criteria? Y/N
• Identifying opportunities for Y/N
improved performance?
• Agreeing actions? Y/N
Does the assessment decision need
Y/N
amending?

Assessor signature Date

Internal Verifier signature Date


Programme Leader signature (if required)
Date
Confirm action completed
Remedial action taken
Give details:

Assessor signature Date


Internal Verifier
signature Date
Programme Leader
signature (if required) Date
Higher Nationals - Summative
Assignment Feedback Form
Student Name/ID
Unit 30 – Application Development
Unit Title
Assignment Number Assessor
Date Received
Submission Date 1st submission
Date Received 2nd
Re-submission Date submission
Assessor Feedback:
LO1 Produce a Software Design Document by analysing a business-related problem and deduce an
appropriate solution including a set of initial requirements
Pass, Merit & Distinction P1 P2 M1
Descripts
LO2 Use design and development methodologies with tools and techniques associated with the creation
of a business application
Pass, Merit & Distinction P3 M2 D1
Descripts
LO3 Work individually and as part of a team to plan and produce a functional business application with
support documentation
Pass, Merit & Distinction P4 P5 M3 M4 D2
Descripts
LO4 Evaluate the performance of a business application against its Software Design Document and
initial requirements
Pass, Merit & Distinction P6 M5 D3
Descripts

Grade: Assessor Signature: Date:

Resubmission Feedback:

Grade: Assessor Signature: Date:

Internal Verifier’s Comments:

Signature & Date:

* Please note that grade decisions are provisional. They are only confirmed once internal and external moderation has taken place and grades
decisions have been agreed at the assessment board.

All rights reserved ©ESOFT Metro Campus, Sri Lanka Page 11 of 16


Assignment Feedback
Formative Feedback: Assessor to Student

Action Plan

Summative feedback

Feedback: Student to Assessor

Assessor Date
signature

Student signature Date

All rights reserved ©ESOFT Metro Campus, Sri Lanka Page 11 of 16


Pearson Higher Nationals in
Computing
Unit 30 – Application Development

All rights reserved ©ESOFT Metro Campus, Sri Lanka Page 11 of 16


General Guidelines

1. A Cover page or title page – You should always attach a title page to your assignment. Use previous
page as your cover sheet and make sure all the details are accurately filled.
2. Attach this brief as the first section of your assignment.
3. All the assignments should be prepared using a word processing software.
4. All the assignments should be printed on A4 sized papers. Use single side printing.
5. Allow 1” for top, bottom , right margins and 1.25” for the left margin of each page.

Word Processing Rules

1. The font size should be 12 point, and should be in the style of Time New Roman.
2. Use 1.5 line spacing. Left justify all paragraphs.
3. Ensure that all the headings are consistent in terms of the font size and font style.
4. Use footer function in the word processor to insert Your Name, Subject, Assignment No, and
Page Number on each page. This is useful if individual sheets become detached for any reason.
5. Use word processing application spell check and grammar check function to help editing your
assignment.

Important Points:

1. It is strictly prohibited to use textboxes to add texts in the assignments, except for the compulsory
information. eg: Figures, tables of comparison etc. Adding text boxes in the body except for the
before mentioned compulsory information will result in rejection of your work.
2. Avoid using page borders in your assignment body.
3. Carefully check the hand in date and the instructions given in the assignment. Late submissions will
not be accepted.
4. Ensure that you give yourself enough time to complete the assignment by the due date.
5. Excuses of any nature will not be accepted for failure to hand in the work on time.
6. You must take responsibility for managing your own time effectively.
7. If you are unable to hand in your assignment on time and have valid reasons such as illness, you
may apply (in writing) for an extension.
8. Failure to achieve at least PASS criteria will result in a REFERRAL grade .
9. Non-submission of work without valid reasons will lead to an automatic RE FERRAL. You will then
be asked to complete an alternative assignment.
10. If you use other people’s work or ideas in your assignment, reference them properly using
HARVARD referencing system to avoid plagiarism. You have to provide both in-text citation and a
reference list.
11. If you are proven to be guilty of plagiarism or any academic misconduct, your grade could be
reduced to A REFERRAL or at worst you could be expelled from the course

All rights reserved ©ESOFT Metro Campus, Sri Lanka Page 11 of 16


Student Declaration

I hereby, declare that I know what plagiarism entails, namely to use another’s work and to present it as
my own without attributing the sources in the correct form. I further understand what it means to copy
another’s work.

1. I know that plagiarism is a punishable offence because it constitutes theft.


2. I understand the plagiarism and copying policy of Edexcel UK.
3. I know what the consequences will be if I plagiarise or copy another’s work in any of the
assignments for this program.
4. I declare therefore that all work presented by me for every aspect of my program, will be my own,
and where I have made use of another’s work, I will attribute the source in the correct way.
5. I acknowledge that the attachment of this document signed or not, constitutes a binding
agreement between myself and Edexcel UK.
6. I understand that my assignment will not be considered as submitted if this document is not
attached to the assignment.

Student’s Signature: Date:


(Provide E-mail ID) (Provide Submission Date)

All rights reserved ©ESOFT Metro Campus, Sri Lanka Page 11 of 16


Higher National Diploma in Business
Assignment Brief
Student Name /ID Number

Unit Number and Title Unit 30: Application Development

Academic Year 2021/22


Unit Tutor

Assignment Title

Issue Date

Submission Date

IV Name & Date

Submission format

The submission should be in the form of an individual written report. This should be written in a
concise, formal business style using single spacing and font size 12. You are required to make use
of headings, paragraphs and subsections as appropriate, and all work must be supported with
research. You must provide in-text citations and the reference list using Harvard referencing
system.

The recommended word count is 4,000–4,500 words excluding annexures..


Minimum word count – 4,000
Maximum word count – 4,500
Unit Learning Outcomes:

LO1 Produce a Software Design Document by analysing a business-related problem and deduce an
appropriate solution including a set of initial requirements.
LO2 Use design and development methodologies with tools and techniques associated with the
creation of a business application.
LO3 Work individually and as part of a team to plan and produce a functional business application
with support documentation.
LO4 Evaluate the performance of a business application against its Software Design Document and
initial requirements

Assignment Brief and Guidance:

All rights reserved ©ESOFT Metro Campus, Sri Lanka Page 11 of 16


BAUHINIA is a clothing brand in Sri Lanka,
founded in 2018, which has come a long way,
offering Sri Lankans with great designs of a variety of clothing. Currently,
BAUHINIA is handling orders through social media networks such as
Facebook and Instagram. Customers can message BAUHINIA requesting an
item/s by sending the item code, size and required quantity. If the item is
available, the customer is required to send the delivery address, contact
number to confirm the order. The package with the required item/s will be
delivered to the customer’s doorstep within 3 to 5 working days, after
which he/she must pay cash on delivery.
Over the years, BAUHINIA has grown steadily mainly due to its popularity
over social media. However, they are finding it increasingly difficult to cope
up with paperwork associated with inventory management due to the
increased of number of orders through message requests. The Managing
Director is frustrated by the problems associated with inventory
management and has decided that BAUHINIA will consult a Software
Development Company to automate the workflow of BAUHINIA Clothing.
AKL Software (AKL) is a software development consultant. AKL has purpose-
built rooms for Facilitated Workshops and Agile software development
projects. The Managing Director of BAUHINIA has decided to contract AKL
for the development of the new order tracking system using an Agile
development approach.

The new online solution will replace the old approach and is likely to
include some of the following functionality:
 Customer Registration and sign-in : Allow customers to
register free. At the time of registration, customers need to provide
name, email address, delivery address, password and two working
telephone numbers. Registered customers can sign-in using email
address and password.
 Browse for products: through product catalog, check
availability and add products to cart.
 Checkout products: Total amount to be paid will be shown.
Customer will be redirected to confirm billing details: Name, delivery
address, email address, two contact numbers. Payment method will
be cash on delivery.
 Staff registration and sign-in.
 Create a daily report of orders that have been requested –
carried out by the Production Manager.
 Create a daily report of product availability- carried out by
Production Manager.

All rights reserved ©ESOFT Metro Campus, Sri Lanka Page 11 of 16


 Add new items to inventory, update
existing item details – carried out by
Inventory handling Clerk.
 Create a monthly Income report- carried out of chief
Accountant.

The new online solution should have the following levels of access:
 Report only
 Update only
 Update and delete
 Complete system access

Activity 1

1.1 Produce a well-defined Problem definition statement supported by a


set of user and System requirements for the above scenario. Identify areas
(if any) of risk that might affect the successful completion of the
application.

1.2 Produce a well-structured Software Design Document that defines a


proposed solution for BAUHINIA by exploring and analyzing their business
problem. Include relevant details on requirements, system analysis, system
design. (propose a suitable language)

Activity 2

Investigate the use of software development tools and techniques for the
chosen software solution. Compare the investigated tools and techniques
and justify the chosen tools, technique and methodology that you may use
for the development of an Inventory Control Application for BAUHINIA .

Activity 3

3.1 Create a presentation to review followings;


 Business application
 Problem definition statement
 Proposed solution
 Development strategy

Conduct a peer-review and identify opportunities that were not previously


considered by interpreting the recorded feedback.

3.2 Develop a business application with support documentation, based on


the Software Design Document produced in activity 1, along with

All rights reserved ©ESOFT Metro Campus, Sri Lanka Page 11 of 16


supportive evidence for using the preferred
tools, techniques and methodologies
investigated in activity 2. Assess new ideas or possible improvements to
the system developed while justifying the reasons for including/not
including them in the application developed.

Activity 4

Conduct a critical review for the design, development, and testing stages of
the Inventory Control application by analyzing the factors that influence its
performance against the problem definition statement and initial
requirements. Conclude the review by reflectively discussing the risks
identified at the beginning and critically evaluating the strengths and
weaknesses of the application developed. Identify and justify the
opportunities for improvement and further development of the application
you developed.

All rights reserved ©ESOFT Metro Campus, Sri Lanka Page 11 of 16


Grading Criteria Achieved Feedback

LO1 Produce a Software Design Document by analysing a


business-related problem and deduce an appropriate
solution including a set of initial requirements.
P1 Explore a business related problem and produce a well-
defined Problem Definition Statement supported by a set of
user and system
requirements.
P2 Determine any areas of risk related to the successful
completion of your application.

M1 Analyse a business related problem using appropriate


methods and produce a well-structured Software Design
Document that defines a proposed solution and includes
relevant details on requirements, system analysis, system
design, coding, testing and implementation.

LO2 Use design and development methodologies with


tools and techniques associated with the creation of a
business application.
P3 Research the
use of software
development tools and techniques and identify
any that have been selected for the
development of this application.
M2 Compare the differences between the
various software development tools and
techniques researched and justify your
preferred selection as well as your preferred
software development methodology.

LO1 & LO2


Justify your solution to a business-related
problem and your preferred software
development methodology, by comparing
between the various software development
tools and techniques researched.

LO3 Work individually and as part of a team


to plan and produce a functional business
application with support documentation.

P4 Create a formal presentation that effectively


reviews your business application, problem
definition statement, proposed solution and
development strategy. Use this presentation as
part of
a peer-review and document any feedback
given.
P5 Develop a
functional business
application with support documentation based
on a specified business problem.
M3 Interpret your peer review feedback and
identify opportunities not previously
considered.

M4 Develop a functional business application


based on a specific Software Design Document
with supportive evidence of using the preferred
tools, techniques and methodologies.
D2 Evaluate any new insights, ideas or potential
improvements to your system and justify the
reasons why you have chosen to include (or not
to include) them as part of this business
application.

LO4 Evaluate the performance of a business


application against its Software Design
Document and initial requirements.

P6 Review the performance of your business


application against the Problem Definition
Statement and initial requirements.

M5 Analyse the factors that influence the


performance of a business application and use
them to undertake a critical review of the
design, development, and testing stages of your
application. Conclude your review by reflectively
discussing your
previously
identified risks.
D3 Critically evaluate the strengths and
weaknesses of your business application and
fully justify opportunities for improvement and
further development.

You might also like