Unit 30: Application Development Guide
Unit 30: Application Development Guide
Higher Nationals
Internal verification of assessment decisions – BTEC (RQF)
INTERNAL VERIFICATION – ASSESSMENT DECISIONS
Programme title BITEC Higher National Diploma in Computing
Student’s name
List which assessment criteria Pass Merit Distinction
the Assessor has awarded.
Programme Leader
signature (if required) Date
Resubmission Feedback:
* 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.
Assignment Feedback
Formative Feedback: Assessor to Student
Action Plan
Summative feedback
Assessor Date
signature
Student Date
signature
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.
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.
1. The font size should be 12 point, and should be in the style of Time New Roman.
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.
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.
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
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.
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.
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
BAUHINIA is a clothing brand in Sri Lanka, founded in 2018, which has come a long way, offering Sri
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.
Add new items to inventory, update existing item details – carried out
by Inventory Handling Clerk.
The new online solution should have the following levels of access:
Report only
Update only
Update and delete
Complete system access
Activity 1
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
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.
13 | P a g e
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.
14 | P a g e
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.
15 | P a g e
16 | P a g e
Acknowledgment
17 | P a g e
Table of content
Activity 01.....................................................................................................................................19
1.1 Problem Definition Statement for BAUHINIA Company.......................................................19
What is this problem?.........................................................................................................20
What is the reason of this problem?..................................................................................20
1.2 What is Risk Management?.....................................................................................................20
BAUHINIA Company Risk Management.............................................................................21
Technical risk...................................................................................................................21
Client risk.........................................................................................................................22
Legal Risk.........................................................................................................................22
Cost Risk..........................................................................................................................22
User and System Requirements of the BAUHINIA Company......................................................22
Analyzing the Problem in BAHUNIA Company...................................................................24
SWOT analysis............................................................................................................................24
VMOST analysis..........................................................................................................................25
PEST analysis..............................................................................................................................25
Activity 02.....................................................................................................................................26
Software Development Tools.........................................................................................................26
Different types of programming languages........................................................................26
Java Language.................................................................................................................27
PHP Language..................................................................................................................27
Selecting the PHP language as the appropriate programming Tool for.........................................27
Software Development Techniques...............................................................................................28
Waterfall Development Methodology............................................................................28
Agile Development Methodology.................................................................................29
Advantages of Agile Methodology........................................................................................30
Disadvantages of Agile Methodology....................................................................................30
Rapid Development Methodology..................................................................................30
18 | P a g e
Prototype Methodology..................................................................................................31
Advantages of Prototyping....................................................................................................31
Disadvantages of Prototyping................................................................................................31
Selecting the Agile Methodology as the appropriate programming Techniques for......................32
BAUHINIA inventory system......................................................................................................32
Activity 03.....................................................................................................................................33
Problem definition statement.................................................................................................33
Proposed solution...................................................................................................................33
Development strategy............................................................................................................34
Business application..............................................................................................................34
Home page..........................................................................................................................35
Login page...........................................................................................................................37
Register page......................................................................................................................37
Admin order list..................................................................................................................38
Admin product list..............................................................................................................38
Admin Inventory list............................................................................................................39
Database.............................................................................................................................39
Feedback Forms..................................................................................................................40
Summary of BAUHINIA Company Clothing Management system.............................................41
Activity 04.....................................................................................................................................43
Review the performance of your business application against the Problem Definition Statement
and initial requirements.................................................................................................................43
Evaluate the performance of a business application against its Software.....................................43
Critically evaluate the strengths and weaknesses of your business application and justify
opportunities for improvement and further development..............................................................44
Strengths....................................................................................................................................44
Weakness...................................................................................................................................45
Bibliography..................................................................................................................................46
19 | P a g e
Figure List
Figure 1-Waterfall Development Methodology............................................................................29
Figure 2-Agile Development Methodology..................................................................................30
Figure 3-Rapid Development Methodology..................................................................................31
Figure 4-Prototype Methodology..................................................................................................31
Figure 5-Problem definition statement..........................................................................................34
Figure 6-Proposed solution............................................................................................................34
Figure 7-Development strategy.....................................................................................................35
Figure 8-ER diagram.......................................................................................................................35
Figure 9-home page.......................................................................................................................36
Figure 10-home page.....................................................................................................................36
Figure 11........................................................................................................................................37
Figure 12-oders..............................................................................................................................37
Figure 13-Login page......................................................................................................................38
Figure 14-register page..................................................................................................................38
Figure 15-admin order list page....................................................................................................39
Figure 16-admin product list..........................................................................................................39
Figure 17-Admin Inventory list.......................................................................................................40
Figure 18-database........................................................................................................................40
Figure 19........................................................................................................................................41
Figure 20........................................................................................................................................41
Figure 21........................................................................................................................................42
Figure 22........................................................................................................................................42
Figure 23........................................................................................................................................43
20 | P a g e
Activity 01
BAUHINIA is a Sri Lankan clothing brand launched in 2018 and has since come a long way,
offering a wide range of designs to Sri Lankans. BAUHINIA now accepts orders through
social media platforms such as Facebook and Instagram. Due to its popularity on social
media, BAUHINIA has been growing steadily over the years. This has made it difficult for
BAUHINIA to accept orders through social media.
BAUHINIA accepts orders through social media sites such as Facebook and Instagram.
Customers can request an item by assigning the item code, size and quantity to BAUHINIA.
If the item is available, send the delivery address and phone number to the customer to
confirm the order. Within 3 to 5 working days, the goods will be delivered to the customer's
door. However, as the number of orders sent through message requests increases, it becomes
more difficult to deal with inventory management paperwork. The Managing Director is
frustrated with the inventory management challenges and has chosen to enlist the help of a
software development business to streamline customer performance. This is the question we
are looking for in our business research.
The main reason for this problem is that as BAUHINIA's popularity grows, so does the
number of orders. BAUHINIA has received large orders from customers which it has not
been able to fulfill. This is the root cause of BAUHINIA's problems. We look at the problem
with this statement as well as the root cause of the problem. We have developed a solution to
21 | P a g e
this problem that improves the efficiency of the business and facilitates the overall
performance of the company. This method has the ability to solve the problem correctly.
The process of discovering, assessing, and controlling threats to an organization's capital and
profitability is known as risk management. Financial uncertainties, legal liabilities, technological
challenges, and strategic management blunders are all potential causes of risk.
Risks connected with completing the application successfully Any application's development
process is in jeopardy. We all know that even the most well planned endeavor may go wrong.
Regardless of how well-developed the developers are, their project is bound to run across
unanticipated issues, causing unneeded delays. A multitude of obstacles can arise, including a
lack of resources, cultural issues, legal issues, and so on. Developers detect potential issues in
their projects and investigate how they can arise. They then take steps to mitigate the risks you
encounter and reduce the impact of the issues we produce. Any unplanned occurrence or
situation that has an impact on the application development process is referred to as a risk. Risk
management systems are intended to do more than only identify and mitigate current threats. A
precise threat administration model should also quantify uncertainties and forecast their impact
on a firm. As a result, a willingness to accept or reject danger emerges. Acceptance or rejection
of danger is determined by the tolerance levels established by the company. Risk management
structures can be utilized if a company is set up to see and address risk management as a
disciplined and continuous activity. To assist in the development of alternative hazard
mitigation methods.
22 | P a g e
Technical risk
Completing an external application comes with a variety of technological hazards. Technical
risk is the most common risk associated with completing an application. As we all know,
while loading programs, there might be issues with the computers used to design the system,
internet connection issues, software issues, storage issues, and electrical issues. As far as we
can tell, these issues can be avoided. It is created as an online web application that should
allow clients to use it from beginning to end because they can complete all of the activities
independently.
Client risk
When designing BAHUNIA website site requirements for minor demands, we need to stay in
touch with clients. As we all know, this device is made to fit the needs of the user. So relax
and let go. The client is fully aware of the equipment that will be delivered at some point.
Customers may experience issues with the machine if this is not done, and this may cause
extra issues for the developers. As a result, at every stage of the design process, we must be
able to educate the customer. As we all know, we must speak with the customer in order to
obtain feedback and learn about their expectations.
Legal Risk
We employ criteria to investigate a system's criminal history when building it. When working
on another project, for example, you should consider the code's copyright. Failure to consider
causes issues when it comes to terminating the planning process for various forms of criminal
heritage. As a result, we must locate all prisons and avoid such dangers in order to efficiently
complete the utility for BAHUNIA.
23 | P a g e
Cost Risk
Unexpected value modifications can also occur during the creation of a machine. When
designing utilities on a tight timeline, this is a common issue. Additional expenditures for
overtime work may be incurred by developers, and these prices may vary based on the
software program, the cost of hardware failures, and the cost of raw supplies. A price range
must be purposefully defined for the development phase to avoid a price dilemma.
The user requirements for the BAUHINIA Inventory System are as follows: These are the user
and system requirements that we identified in the proposed solution to the BAUHINIA
challenge. These are the user and system requirements for the suggested solution to the
BAHUNIA firm problem that we have discovered. As far as we know, this application should
provide free access to the system to all users. We can design a system that will assist many
individuals get rid of the transaction system through social media and make their orders more
efficient and cost effective based on these recognized user and system demands. This
application, as we all know, requires four levels of system access. Each entry level has its own
set of features that aid in system development. The reports are all that is required for the Chief
Accountant to complete the final request and invoice. As a result, the Chief Accountant has
restricted access to the report. An accountant, as we all know, does not require any access. As
the customer must add a new order and delete it after reviewing the customer's credit, the order
handling clerk assists in updating and removing orders. They are restricted by the record since
they do not need to make one; as we all know, the warehouse operator's main job is to confirm
the stock order and issue a receipt for the sales order, thus the warehouse operator is permitted
access to update. Copy the welcome message. The user who has access to all levels of this
program is the Product Manager.
24 | P a g e
We can analyze the situation using a variety of approaches. Problem assessment, as we all
know, is a series of tasks. As we all know, we can use, test, and manage to acquire profitable
consequences when we employ a method that we prefer to examine a problem because it is
valid. As we all know, studying and determining the current condition of the business
25 | P a g e
SWOT analysis.
Strengths, weaknesses, opportunities, and threats are all part of the SWOT analysis. Internally,
your organization's strengths and weaknesses are aspects that can manipulate and change it. For
example, your patents and intellectual property, as well as your location capabilities and threats,
are all external - things that happen in the broad market outside of your organization, regardless
of who is on your team. You may seize opportunities and defend yourself against
threats, but you cannot trade them. Competitors, unfinished fabric prices, and buyer buying
habits are all examples.
VMOST analysis.
VMOST Analysis is a tool that allows a business to evaluate its core technologies in terms of
whether or not they support the strategy's actions. The five main elements of vision, mission,
goals, methods, and strategies are examined in VMOST Analysis to address this question. There
are five sorts of factors in the VMOST evaluation technique. Each component is evaluated
based on how well it fits within a conventional commercial enterprise plan, in my opinion.
VMOST analytics is frequently used to describe a company's current and future strategies,
organizational units, functions, and applications. Employees, both men and women, can
appreciate the use of this technology as part of the business.
PEST analysis.
26 | P a g e
Activity 02
Software Development Tools
A software development tool is any software program that assists designers to create, edit,
debug, maintain, and improve a given task. A programming tool is often referred to as a
software development tool. When evaluating software program development tools, we must
select the appropriate programming language, IDE, and UI and UX design tool. The ultra-
modern world. There are many tools and approaches to choose from. Developing systems use
specialized languages to perform specific functions. As we all know, in determining which
language to use for PCW utility development, the functions that specify programming language
compatibility should be compared.
Programming languages for computers provide instructions in a language that the computer
understands. There are many computer programming languages and many human based
languages. Programmers can communicate with computers. Binary is a component of a
27 | P a g e
C Language.
Java Language.
PHP Language.
The PHP programming language is used to create web pages and is also utilized as a scripting
language. This language is intended to assist you in moving a website forward more quickly,
with capabilities such as making it easy to construct HTTP headers and link to databases. As a
scripting language, it consists of a set of features that make it easy for a programmer to speed
up. It does, however, have more modern object orientation features.
28 | P a g e
Looking at all the above languages, PHP is the most suitable language for this inventory
system. PHP (Hypertext Preprocessor) is a general working language that can be used to
develop dynamic and interactive websites. It was one of the first client-language languages to
be able to embed into HTML, making it easy to add functionality to web pages without having
to call external files for data. Its use has evolved over the years, adding regular improvement
features and opening up new possibilities. Easy-to-Use Essential Motivation PHP is known for
its ease of use. Even if you do not currently have extensive information or experience on the
Internet, many people in development can create a large web page in a short time with a single
PHP file.
This feature also appeals to companies that help with net price management. It supports all
major net servers and is easy to install on a wide range of structures and platforms with
minimal system costs. There are many tutorials, FAQs and tips for new PHP Developers. Those
who constantly push the limits that the language can reach through regular updates. It's Quick
and Safe Two things every business owner should do to protect their website or app are fast and
secure. When PHP uses a new game, its personal memory competes faster and faster. Although
PHP has security issues in the past, it is important to note that they are no longer inherently less
or less secure than the various programming languages.
Software development techniques are nothing more than one-of-a-kind product employer
strategies for streamlining your software development process. Each strategy has its own set of
advantages and disadvantages, and it performs differently at different times. As a result, in
order to successfully manage the problem of upgrading your specific software, you must select
the appropriate software program development approach that will ensure a smooth
29 | P a g e
The waterfall system Methodology is a rigid linear model with goals, requirements, design,
implementation, verification, and maintenance stages. Each step must be completed before
proceeding to the next. This shows that the technology of the waterfall model cannot be
changed for any reason. Waterfall access is often used by design-oriented groups who have a
clear understanding of the scope of the project. On the other hand, the waterfall model can be
used by development teams that are not affected by the diversity and mobility of current
systems.
Agile system Methodology is the science used to create a structured software program
management process. This software program development approach is a systematic framework
for implementing a number of software program engineering projects. Each line lasts a few
weeks, during which time staff members are on the lookout for a distribution list. At the end of
Sprint with Scrum Master, members of the Accelerated Development team test that feature. If
30 | P a g e
More flexible.
Product get to market faster.
Better communication.
Hard to predict.
Final product is not released first.
Documentation gets left behind.
31 | P a g e
Prototype Methodology
32 | P a g e
alterations in advance. This strategy allows for the understanding of software development
criteria as well as the implementation of useful market research. The most important feature of
Advantages of Prototyping
In today’s world, technologies are changing faster than ever and software companies need to
work in a rapidly changing environment. Companies create alternatives in an ever-changing
environment, usually it can’t all come together. Requirements and explanations when starting a
development. Clearly, standard software maneuvers can be very difficult when studying
requirements other than these. Like a waterfall model, it depends entirely on the complete
specifications of the system. Requirements, model and tests. This type of fashion will no longer
be noticed. Faster software program development process. As a result, these standard software
enhancement styles fail to deliver the desired product. This is Agile position. Agile model is
essentially designed primarily for mannequin so we can retail at this point. Deal with such
33 | P a g e
Activity 03
34 | P a g e
Problem definition
Proposed solution
Development strategy
35 | P a g e
Business application
36 | P a g e
Home page
37 | P a g e
Figure 11
Figure 12-oders
38 | P a g e
Login page
Register page
39 | P a g e
40 | P a g e
Database
Figure 18-database
41 | P a g e
Feedback Forms
Figure 19
Figure 20
42 | P a g e
Figure 21
Figure 22
43 | P a g e
Customers provided the responses shown above. According to those responses, each customer
found the system to be useful. This is also user-friendly. They also understood that this strategy
would not result in any losses in terms of payment or delivery of goods. BAUHINIA Workers
at the business have been told that this makes their jobs easier. It's simple to handle big
numbers of orders without missing any.
Activity 04
Review the performance of your business application against the
Problem Definition Statement and initial requirements.
As more people turned to internet operations, the quantity of orders for this business grew. It
got more difficult to handle commodities through social media as a result of this increase. As a
result, we are in a really difficult situation. For this reason, a system called garment inventory
management system was created. The company is debating whether or not to acquire quick
upgrade skills in order to increase the PC code for an existing order tracking machine. This
BAUHINIYA business's system is compatible with mobile phones, PCs, and laptops. This is
where goods were ordered and handled. Item ordering, updates, editing, deletion, and product
documentation are all available through the system. This system's functionality was simple to
use for both customers and employers.
Examine a business application's performance in relation to its software design document and
basic requirements. The previous couple years. The company grew steadily over time, and
44 | P a g e
into the system and reviews the daily records. Another downside of this strategy is that
capitalists only consider delivering the client an invoice.
Preparing an invoice for the client took a long time. The major bourgeoisie will respond by
clicking on its order range and date to generate shape. They've progressed. This technology
enables it to function as a server-based Internet payment system. It makes the organization's
work easier. This indicates that the client is unconcerned about payments. The designed method
eliminates issues with creating invoices for orders. Another possible benefit is that it is known
and can be used in places other than the pipe system. The customer will be prepared to make an
online payment.
The strengths and drawbacks of this clothes management system, which was developed for the
BAUHINIA business, must always be kept in mind. This program has the potential to have a
45 | P a g e
Strengths
Weakness
46 | P a g e
Bibliography
Guru99. 2022. What is Waterfall Model in SDLC? Advantages and Disadvantages. [online]
Available at: <[Link] [Accessed 10
April 2022].
47 | P a g e
48 | P a g e