Higher Nationals

Internal verification of assessment decisions – BTEC (RQF)

INTERNAL VERIFICATION – ASSESSMENT DECISIONS

Programme title BITEC Higher National Diploma in Computing
Mr. Kalum Sooriya
Assessor Internal
Archchi Verifier
Unit 30 – Application Development
Unit(s)
Inventory Control Application for BAUHINIA
Assignment title
Dikeshi Perumbadu Wickramasuriya
Student’s name
List which assessment Pass Merit Distinction
criteria the Assessor has
awarded.
INTERNAL VERIFIER CHECKLIST
Do the assessment criteria awarded
match those shown in the Y/N
assignment brief?
Is the Pass/Merit/Distinction grade
awarded justified by the assessor’s Y/N
comments on the 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 Y/N
criteria? Y/N
• Identifying opportunities for
improved performance? Y/N
• Agreeing actions?
Does the assessment decision need
Y/N
amending?
Assessor signature Date

Internal Verifier signature Date

Programme Leader signature (if
Date
required)
 Confirm action completed
Remedial action
taken
Give details:
Assessor signature Date
Internal
Date
Verifier
signature
Programme
Date
Leader signature
(if required)
 Higher Nationals - Summative Assignment
Feedback Form

Student Name/ID 008559

Dikeshi Perumabadu Wickramasuriya
Unit Title Unit 30 – Application Development

Assignment Assessor Mr. Kalum Sooriya

Number archchi
Date
Submission Date
Received 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 & P1 P2 M1
Distinction Descripts
LO2 Use design and development methodologies with tools and techniques associated
with the creation of a business application
Pass, Merit & P3 M2 D1
Distinction Descripts
LO3 Work individually and as part of a team to plan and produce a functional
business application with support documentation
Pass, Merit & P4 P5 M3 M4 D2
Distinction Descripts
LO4 Evaluate the performance of a business application against its Software Design
Document and initial requirements
Pass, Merit & P6 M5 D3
Distinction 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 LankaPage 11 of 16

Assignment Feedback

Formative Feedback: Assessor to Student

Action Plan

Summative feedback

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

 Feedback: Student to Assessor

Assessor signature Date

Student signature Date

Pearson Higher Nationals in

Computing

Unit 30 – Application Development

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

All rights reserved ©ESOFT Metro Campus, Sri LankaPage 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 LankaPage 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.

dikeshipw@gmail.com

Student’s Signature: Date:31/12/2021

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

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

All rights reserved ©ESOFT Metro Campus, Sri LankaPage 11 of 16
 Higher National Diploma in Business

Assignment Brief

Student Name /ID Number Dikeshi Perumabadu Wickramasuriya

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

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

Assignment Brief and Guidance:

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.
 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

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

  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 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 LankaPage 11 of 16

All rights reserved ©ESOFT Metro Campus, Sri LankaPage 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.
Table of contents

Activity 01

1.1 explore a business related problem and produce a well-defined problem

definition……………………………………………………………………………………
…03
1.2 analyze a business related problem using appropriate methods and produce a well-
structured software design document that defines a proposed
solution………………………………………………………………………………11
1.3 determine the area of applications ……………………………………………………15

Activity 02

2.1 use design and development methodologies with tools and techniques associated with the
creation of business application. ………………………………………………………….16

2.2 traditional system methodologies …………………………………………………….22

Activity 03

3.1 create a formal presentation that effectively reviews your business application, problem
definition statement, proposed solution and the development strategy …………………….32

Activity 04
4.1 review the performance of your business application against the problem definition statement
and initial requirements …………………………………………………………………….45
Activity 01

Explore a business related problem and produce a well-defined problem definition

statements supported by a set of user and system requirements

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.

Due to high demand of the products the BAUHINIA cannot handle their business process using
only social media platform. BAUHINIA is get the orders from the Facebook and Instagram but
they still using a manual system for processing the orders. Because of that difficult to cope up
with paperwork associated with inventory management due to the increased of number of orders
through message requests. With the manual system of BAUHINIA has facing the misplacements,
incorrect order details, harder to update new details, incorrect reports with the current manual
system of BAUHINIA.
 Bauhinia clothing industry requirements.

Bauhinia clothing systems are categorized in two types of system requirements. The new order
tracking system will replace the old paper-based system and is likely to include some of the
following functionalities. Such as:

- Functional requirements.

- Nonfunctional requirements.

Functional Requirement

 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.
 Create a monthly Income report- carried out of Chief Accountant.
Nonfunctional requirements.

1. Reliability, availability, maintainability. How often the system does experiences critical
failures.
2. Security –how are the system and its data protected agnist attacks.
3. Usability – how easy is it for a customer to use the system
4. Localization – does the system match local specifics?
5. Probability and compatibility – which hardware, operating system, browsers and their
versions does the software run on.

1.2 Determine any areas of risk related to the successful completion of your application

Risk 01

Quick Service

Bauhinia company Define main risk area is how quick service from the clothing inventory
company for the customers and how affected the business

RISK 02

Data lost

From the transaction from paper works, sometime lost the paper document there is more
probability about data lost from the risk area

RISK 03

Analysis The business

From the paper documents company, decision-makers are too difficult to Analysis their business
future.

RISK 04

Stock availability

Sales team and warehouse team have to communicate and update their stock level frequently. if
any issue of the communication stock level must be changed.

RISK 05

Competitor contest

Company main risk area is competitors contest. If competitors use modern technology Our
Company have to contest with them for the more sales.

RISK 06

Waste Time

Seller and buyers get more time to for one deal. For one sale get more time to verify the
Product and customer. in this company give the opportunity to creditworthy for the customers
and it gets too much time.

RISK 07

Decision making
For the company levels, they want to make some decisions for the future opportunities of the
clothing inventory company. From previous System they are too difficult to make some
decisions.

RISK 08

Cyber attacks

A cyber-attack is an assault launched by cybercriminals using one or more computers against

a single or multiple computers or networks. A cyber-attack can maliciously disable
computers, steal data, or use a breached computer as a launch point for other attacks.

RISK 10

Computer virus

A computer virus is a type of computer program that, when executed, replicates itself by
modifying other computer programs and inserting its own code. Company has a risk

RISK 11

Team Turnover

Some team members can be left with the project and Need to keep additional members to backup

RISK 12

Natural disasters may be disaster the Company through earth quack, floods, tsunamis, other
geologic processes. Change the Place to another location
RISK 13

Client Requirement Identify risks

Difficult to identify requirement of Clients 100%. Use Some survey methodology for recognize
the requirements such as questioners.

RISK PROBABILITY
Malware 45 %
Cyber attacks 60%
Data lost 13%
Spyware 70%
Stock availability 50%
Natural disaster 20%
Stock availability 10%
DDOS attack 15%
Client requirement identify 23%
Computer viruses 18%
BUHANIA clothing company have to determine any areas of risk related to the successful
completion of the new system. From considering the above company problems the author can
define the main area that company must update to the new business sales solution based on
new technology. And the author defines that company system analysis methods and company
sales strategy must become to one in new web-based software

1.3 analyze a business related problem using appropriate methods and produce a well-
structured software design document that defines a proposed solution. Include a relevant
details on requirements, system analysis, and system design. (Propose suitable language)

BAUHINIA
clothing software
design document
 1. Introduction
2. Purpose
3. Related persons for order tracking system
4. Overview of bauhinia company
5. Context
6. Metrics
7. Milestone chart
8. Current solution
9. Proposed solution
10. Alternative solutions
11. Scope of time line

Introduction

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.

Purpose.

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.
Problem definition

When consecrating business mainly author catch they use paperwork to tracking orders. This is
too hard option to do their business due to the increase in a number of orders. Because they are
findings it increasingly difficult to cope up with all of the paper work associated with tracking
orders due to increase of a number of orders. Bauhinia company the old paper based system and
its likely to include some of the following functionalities their for they got more time and they
have no arrangement.

Related Persons for clothing system

Software developer

Software developers are the creative minds behind computer system programs. Some develop
the applications that allow people to do specific tasks on a computer or another device. Others
develop the underlying systems that run the devices or that control networks.

Software developers involved to modify the software and fix errors. The developers always
involved with coding

Software designer
Computer software designers design, create and test software applications. Collecting the
requirements and responsible for creating new ideas and designing prepackaged and
customized computer software
Business analyst
A business analyst (BA) is someone who analyzes an organization or business domain (real or
hypothetical) and documents its business or processes or systems, assessing the business
model or its integration with technology. The Business Analyst Who Works particularly well
with computer technology a business need. Business system analysts determine which
technology upgrades and installations will improve workplace efficiency.

Requirements analysts
Requirements analysts form a bridge between clients and software developers. Their job is to
fully understand the needs of the client who is ordering software. They must ensure they know
exactly how the client needs the software to function and what kind of tasks they must be able
to perform.

Infrastructure Analyst
An infrastructure analyst finds and fixes problems within an organization’s computer
network. As an infrastructure analyst, your job duties include monitoring and assessing the
systems and finding areas that need upgrading or improvement.

Nontechnical stakeholders

Production Manager

Production managers ensure that manufacturing processes run reliably and efficiently.
Production manager's responsibility to Generate Reports of daily Dispatch orders. The main
role of a Production Manager is to oversee the manufacturing process within a company and
to ensure that production lines run without any problems and minimum downtime.

Inventory Handling Clerk

Add a new items to inventory, update existing item details. Monitors and maintains current
inventory levels processes purchasing orders as required , tracks orders and investigates
problems, records purchases , maintains database , performs physical count of inventory and
reconciles actual stock count to computer generated report.

Chief Accountant

The chief Accountant is in-charge of all accounting activities of both financial and
management accounting. They are responsible for preparing financial and performance
reports, assisting departments with annual budgets and reviews, internal control and tax
studies. Chief accountant Responsible for Generate Invoice to the Business customer and
responsibility to create final demand if the Business customer is not paid.

Overview of BAHUNIA order tracking system.

Bauhinia is a clothing brand in sir lanka founded in 2018.the package with the required item/
will be delivered to the customer’s doorstep within 3-5 working days after delivery. with
required The Managing Director is frustrated by the problems associated with previous
traditional 'waterfall' projects. He has decided that the clothing will use a company with agile
development experience to develop the software for a bauhinia inventory company.

Goals
Inventory Company wants to new clothing system and build new order tracking system for them
and success their business

Metrics

The bauhinia have to use metrics to measure the New system how much success and these are
the few metrics that can use as Gross profit margin, Return on investment (ROI), Customer
satisfaction, Actual cost, Schedule Variance, According to the metric, The bauhinia company
most useful and valuable Measure tools for New System and collect feedback collection

Milestones

Activity D ate

Begin End

Review company 2021-10-05 2021-10-10

Categories Fields 2021-10-10 2021-10-15

Design the project 202110-15 2021-10-25

Create Software 2021-11-25 2021-11-10

Testing and Review 2021-12-10 2021-12-20

Finalize the project 2021-11-20 2021-11-25

Current solution

Bauhinia company has used with the waterfall system, these are some features they did with
the current system such as Marks Order, update Orders, delete orders, Accept Bank payments.
for the more, they cannot access these features with their current system such as, cannot create
daily order dispatched report, cannot generate Invoice or Acknowledge copy to customers,
cannot accept payments through credit card, for the more, difficult to Track Order to new
clothing brand system was lower speed.

And less security.

Proposed solution
The author creates a proposed solution for the software design document as a Use case, DFD and
ER Diagram.

Use case diagram

DFD DIAGRAM
ENTITIY relationship
Alternative solutions

Bauhinia Company can buy Template web site Solution for this purpose .It usually comes
down to your business needs and personal preferences that will influence your choice
between a website template and custom web design.

Every business has different needs. If you want a website that is scalable, search engine-
friendly and unique, then a custom web design is an ideal choice. The added benefit of a
CMS is that it saves you some money on keeping your website updated and well
maintained. Although, it might take longer and cost you more, but you will get a website
according to your business needs and will deliver an exceptional user experience to your
website visitors.

Scope and timeline

Review Company
review old system
Collect data from employers

Categories Fields
divide company categories
Identify the User
requirements Determine the
requirements.
Recognize suitable function for system

Design the project UI

and UX
designing.

Create Software
Developing software
 Testing and Review
release beta
version Testing.
Review

Finalize the project

final Project
Designing
Release New Order tracking system

Activity 02

2.1 research the use of software development tools and techniques and identify any suitable
tools or technique that you may select for the development of this applications.

Traditional System Development Methodologies

Traditional project management is an established methodology where projects are run in a

sequential cycle. It follows a fixed sequence: initiation, planning, execution, monitoring, and
closure. The traditional project management approach puts special emphasis on linear
processes, documentation, upfront planning, and prioritization. As per the traditional
method, time and budget are variable and requirements are fixed due to which it often faces
budget and timeline issues.

Principles of Traditional Systems Development Life Cycle

The process of developing software consists of a number of phases.

These phases are arranged in a precedence sequence of when they start.

The sequence of phases represents the passage through time of the software development.

Phases can and do overlap as previous phases are revisited, when more information becomes
available.

The software becomes more complex and useful as the phases are followed.

Water fall model

The waterfall model is a classical model used in system development life cycle to create a system
with a linear and sequential approach. It is termed as waterfall because the model develops
systematically from one phase to another in a downward fashion. This model is divided into
different phases and the output of one phase is used as the input of the next phase. Every phase
has to be completed before the next phase starts and there is no overlapping of the phases.
Requirement Gathering and analysis: All possible necessities of the system increase and
record is combined on this phase to grow to be specific record. All feasible requirements of
the gadget to be developed are captured on this stage and documented in a requirement
assertion doc.

Systems Design: The requirement statement from first stage are studied in this stage and
also system layout is developed. It helps plenty of thing like specifying hardware and
machine necessities and defining overall gadget architecture. Project features and operations
are described in detail to consist of technical specifications, use of UML (while
required/suitable), process diagrams, and even prototype creation together with other
required documentation.

Implementation: With the inputs of machine layout, firstly the machine developed by using
small applications named gadgets. Which are integrated inside the next degree. Each and
every unit is ready and examined for its functionality. One of the priciest phases of the
SDLC for information systems. Shortfalls in Systems layout or necessities definition can
emerge as high-priced within the phase if no longer performed satisfactorily.

Testing: A common section that is under-funded by way of many corporate entities. In this
segment all of the undertaking additives are included and tested for mistakes and
interoperability in a special check surroundings. All of the devices are prepared in the
Implementation stage. And it's going to have integrated into a system after testing each and
each unit. In this degree the entire gadget is tested for any fault and failures.

Deployment of System: Software is deployed to the purchaser and starts conducting the
favored work. After the functional and Non-practical trying out are done, the product might
be established within the client surroundings otherwise it might be launched into the market.

Maintenance: After hand over the device, there will be some problems which come up in
the patron environment for that during this degree the ones problem patches are launched.
And also, to growth the product, some new variations might be released. This stage covers
all the ones changes in the client surroundings. The protection section of the SDLC can end
up a assignment in and of itself. Future software program upgrades, infection fixes, and
normal preservation are addressed all through this degree which can also or might not have
a well-described stop state.

Principle of waterfall model

The Prototyping Model may be a systems development method (SDM) during which a
prototype (an early approximation of a final system or product) is made, tested, then reworked
as necessary until a suitable prototype is finally achieved from which the entire system or
product can now be developed.

This is the model which became a well-liked software model, from this we ready to
understand customer requirements at a premature phase of development. From this model,
we will get valuable feedback from the customer and helps software designers and
developers comprehend what exactly is awaited from the merchandise under development.

It is a working model of software with some bordered functionality. The prototype doesn't
rottenly hold the actual logic utilized in the important software application and is a further
plan to be appraised under attempt evaluation. it's let the users evaluate developer
recommends and check them out before execution. It also helps understand the wants which
are user particular and should not are appraised by the developer throughout product design.
(Tryqa.Com, 2021)

Spiral model

Spiral Model may be a combination of a waterfall model and iterative model. the event team
in Spiral-SDLC model starts with a little set of requirements and goes through each
development phase for those set of requirements

It is joined the thought of continual development with the systematic, powered features of the
waterfall model. This model allows for step-by-step releases of the merchandise

This model is best used for giant projects which involves continuous enhancements. This
spiral model is been using when the project is large, where the software needs continuous
risk evaluation, requirements are a touch complicated and need continuous clarification, the
software requires significant changes, where enough time-frame is there to urge end-user
feedback and where releases are required to be frequent.(Tryqa.Com,2018)

It has four periods. A software project frequently moves through these periods in frequentation
called spirals.

Spiral Model Phases

The phase of the spiral model has four quadrants, and every of them represents some specific
stage of software development. The functions of those four quadrants are listed below:

Planning objectives or identify alternative solutions: during this stage, requirements are
collected from customers then the aims are recognized, elaborated also as analyzed at the
start of developing the project. If the iterative round is quite one, then an alternate solution is
proposed within the same quadrant.

Risk analysis and resolving: because the process goes to the second quadrant, all likely
solutions are sketched, then the simplest solution among them gets select. Then the various
sorts of risks linked with the chosen solution are recognized and resolved through the
simplest possible approach. Because the spiral goes to the top of this quadrant, a project
prototype is put up for the foremost excellent and certain solution.

Develop the next level of product: because the development progress goes to the third
quadrant, the well-known and most required features are developed also as verified with the
testing methodologies. As this stage proceeds to the top of this third quadrant, new software
or subsequent version of existing software is prepared to deliver.

Plan the next Phase: because the development process proceeds within the fourth quadrant,
the purchasers appraise the developed version of the project and reports if any longer
changes are required. At last, planning for the next phase is initiated.

When to use the Spiral model:

When costs and risk evaluation is important

For medium to high-risk projects
Long-term project commitment unwise due to potential changes to economic priorities
Users are unsure of their needs
Requirements are complex
 New product line
Significant changes are expected (research and exploration)

Prototype model

The prototype model requires that before carrying out the development of actual software, a
working prototype of the system should be built. A prototype is a toy implementation of the
system. A prototype usually turns out to be a very crude version of the actual system, possible
exhibiting limited functional capabilities, low reliability, and inefficient performance as
compared to actual software. In many instances, the client only has a general view of what is
expected from the software product. In such a scenario where there is an absence of detailed
information regarding the input to the system, the processing needs, and the output requirement,
the prototyping model may be employed.

Types of prototyping
 1. Rapid prototyping
2. Evolutionary prototyping
3. Incremental prototyping

Steps of prototyping

1. Requirement Gathering and Analyst

2. Quick Decision
3. Build a Prototype
4. Assessment or User Evaluation
5. Engineer Product

Agile methodology

Rapid software development is a set of software development methods based on repetitive

development, where needs and solutions evolve through collaboration between self-organizing
cross-functional groups. Encourages a disciplined project management process that typically
promotes fast-paced or agile processes, encourages frequent testing and adaptation, a leadership
vision that encourages teamwork, self-organization, and accountability, allowing high-quality
software to be distributed faster Engineering is a group of best practices. And a business
approach that combines development with customer needs and company goals. Agile
development is any development process that is in line with the concepts of agile expression. The
publication was prepared by a team of fourteen leading figures in the software industry,
reflecting their experiences on what works and what does not. Read more about the Agile
Manifesto. Did you know that Agile can also be used for hardware projects? Learn about
Crime’s revolutionary Agile for hardware framework.

Scrum
Scrum is an agile method for project management developed by Ken Schwaber. Its goal is to
dramatically improve productivity in teams by using paralyzed, process-laden methodologies.

Scrum is, undoubtedly, the foremost used of the many frameworks within the Agile
methodology. Scrum may be a software package for the event of cycles or stages of
development, referred to as sprints, and maximization of development time. it's usually
utilized in software development for development projects, but it also can be utilized in a
business-related context.

SCRUM is an agile methodology that's a more complex set of development principles. They
specialize in the management aspects of projects. Under this method, the owner of a given
product will collaborate with information technology teams and businesses to collectively
isolate and harness the functions of what's referred to as a product backlog. Assorted team
members will then distribute a software program in increments - this is often called a sprint,
and therefore the typical duration is one month. Upon delivery, an analysis is formed of the
merchandise backlog, and priorities are shifted to the specified cycle of every repetition.

As with XP, implementing SCRUM offers a mixture of advantages and disadvantages. On

one hand, this Agile methodology enables management teams to identify problems at the
event stage — SCRUM also promotes transparency among colleagues. However, SCRUM
also can end in slapdash programming and leave scant records for handover. As such, the
tactic is most appropriate for information technology businesses that specialize in products,
features, and delivery in partnership with management teams. an honest practice from
SCRUM is that the daily stand-up meetings – a time boxed daily event, where all team
members discuss work progress and possible obstacles.

SCRUM is one among the frameworks that revolutionized the software development
industry. It became popular due to its fast iterations and active collaboration between teams,
customers, and stakeholders. For the sake of higher collaboration, there are predefined team
roles:

Product Owner. The PO is responsible for understanding the business and market
requirements. After this, she / he needs to prioritize work, build a product backlog and make
sure that everyone understands the work items.
Scrum Master. The SM educates the team, the product owner, and the scrum processes on
the business. He / she is responsible for managing the workflow of the team and all the
resources required for each task.

Scrum Team. The team usually has people with different skills such as developers,
automation engineers, and testers. All team members have to support each other in order to
be successful. Most efficient scrum teams are usually 5 to 8 members of the size and co-
located.

Disciplined Agile Delivery (DAD)

Disciplined Agile Delivery (DAD) may be a people-first, learning-oriented hybrid agile

approach to that solution delivery. It a risk-value delivery lifecycle, is goal-driven, is
enterprise aware, and is scalable

Disciplined agile delivery (DAD) is that the software development portion of the disciplined
agile toolkit. DAD enables teams to create simplified process decisions around incremental
and iterative solution delivery. DAD builds on the various practices espoused by advocates
of agile software development, including scrum, agile modeling, lean software development,
and others.
Developed by Scott Ambler and Mark Lines, DAD is similar to SAFe (Scaled Agile
Framework) therein it uses Lean and Agile techniques. DAD’s framework has three phases:
Inception, construction, and transition (delivery). DAD also offers process guidelines for
every of 4 lifestyles.

These are:

Agile basic
Lean/advanced
Continuous delivery, and
Exploratory

The Agile/basic lifestyle falls within the construction phase and is adequate to Scrum. The
Lean/advanced lifestyle in DAD uses Kanab processes which maximizes flow and
minimizes work-in-process. Continuous delivery lifestyle stresses continuous integration,
DevOps, and a deployment process that has frequent delivery to users. The Exploratory
lifestyle has little early planning, but fast and frequent delivery. By having frequent releases
of small, viable product to the user, the goal is to realize feedback, then incorporating that
feedback immediately into subsequent delivery. the general goal of the exploratory lifestyle
is to “fail fast”, thereby saving tons of your time and money if it seems the project isn't
feasible. Within the exploratory lifestyle, the project is halted whenever the newest delivery
of the merchandise features a problem that's non-fixable.

DAD, instead of prescribing an in-depth list of procedures to follow, does offer guidance on
the sort of tools and processes you would possibly want to use counting on the sort of
project you're trying to finish. Up to now, adoption of DAD compared to SAFe has been
slow. this might be because to successfully implement DAD it's more likely experienced
consultants and coaches are going to be needed. This is often particularly the case if a
project is extremely large, or transitioning from a standard model is involved.

Lean Development (LD) Methodology

Change-tolerant software of the creation of Lean Development Focus. this system embodies
the dynamic stability of the notion which may be thought of as almost like how the scrum
embraces the controlled chaos.
Lean Development may be a methodology that comes directly from Lean Manufacturing,
created by Toyota, and applied to software development. This method offers a conceptual
framework and a group of values, principles and good development practices which will be
applied to an agile development approach.

There are seven essential principles: Deleting the items That don't Matter (Everything that
does not Bring Effective Value To The Customer's Project Is Deleted); Quality of
development (created by residuals of discipline and control); Creating knowledge (the team
is motivated to document the entire infrastructure and therefore the value which will be
retained later); Differing commitments (this point encourages the team to not focus an
excessive amount of on planning and anticipating ideas without having a priori and
complete understanding of the wants of the business); Fast delivery (deliver value to the
customer as soon as possible); Respecting the team (communicating and managing conflicts
are two essential points); Optimize the whole (the development sequence has got to be
perfected enough to be ready to delete errors within the code, so as to make a flow's true
value).

Kanban methodology

Kanban is an agile methodology that is not necessarily iterative. Kanban allows the software
be developed in one large development cycle. Despite this, Kanban is an example of an agile
methodology because it fulfils all twelve of the principles behind the agile manifesto,
because whilst it is not iterative, it is incremental.

Kanban is a method for managing the creation of products with an emphasis on continual
delivery while not overburdening the development team. Like Scrum, Kanban is a process
designed to help teams work together more effectively.
Activity 03

Create a formal presentation that effectively reviews your business application, problem
definition statement, proposed solution and the development strategy. Use this presentation as
a part of a peer-review and document any feedback given.

Presentation
Develop a functional business application based on specific software design document with
supportive evidences for using the preferred tools, techniques and methodologies.

Home page

Login interface
Customer registration form

Admin registration form

My profile page

Edit information page

List of item page

Add new item page

List of item page
List of customers
Request item to bauhinia clothing company

Information about page

Activity 04

Review the performance of your business application against the problem definition
statement and ital. requirements.

AKL software uses their problems with the previous system and the new system has been
developed to suit the needs of bauhinia clothing system clients. Also, the new system can work
efficiently and effectively. According to bauhinia company Previous, there are a number of
issues with their operations. They cannot monitor daily orders because it deals with paperwork
and they cannot manage multiple daily orders. AKL Development Order Management System
helps to easily add orders to the system. System control with customer and employer IDs. The
order handling clerk can easily handle the system when receiving a sales order via phone, fax,
mail or email. Easily inspect parts of the system. With the new system, warehouse activation will
make it easier to manage stocks and place orders when notified, manage stock and manage all
stock exchange notifications received by other employers. From this system they can easily get a
copy of the reception. In this AKL software development system the customer can easily check
the credit and easily manage all the payments. From this system the Product Manager can receive
a daily report on orders. The Chief Accountant can easily handle all the accounts, handle all the
manual processes performed by the system and give him the final requests to create an invoice
from the system. All risk areas are managed by the AKL system by considering the problem
definition statement.
References

Better Buys. (2019). Business Intelligence for Marketers Resource Guide. [online] Available
at: https://www.betterbuys.com/bi/business-intelligence-marketers/ [Accessed 26 Feb. 2020].

Bidur, B. (2015). 5 core business process | Business Process | Strategic Management. [online]
Scribd. Available at: https://www.scribd.com/document/258617131/5-core-business-process
[Accessed 26 Feb. 2020].

Conrad, Alainia. Future of Business Intelligence | Future of BI For 2020. 11 Nov. 2019,
www.selecthub.com/business-intelligence/future-of-bi/. Accessed 26 Feb. 2020.

Wood, Rob. “The Future of Business Intelligence – What’s Coming in 2018.” ClicData, 2018,
www.clicdata.com/blog/future-business-intelligence-coming-2018-beyond/. Accessed 26 Feb.
2020.

Stodder, David. “Five Emerging Trends in Business Intelligence and Analytics.” Transforming
Data with Intelligence, 2011, tdwi.org/articles/2011/11/09/feature-five-emerging-trends-
inbusiness-intelligence-and-analytics.aspx. Accessed 26 Feb. 2020.

Eiloart, J. (2019). Top 10 business intelligence trends for 2018. [online] ITProPortal.
Available at: https://www.itproportal.com/features/top-10-business-intelligence-trends-for-
2018/ [Accessed 27 Jan. 2020].

Financesonline.com. (2019). 15 Best Business Intelligence Tools For Small And Big Business -
Financesonline.com. [online] Available at: https://financesonline.com/15-best-
businessintelligence-tools-small-big-business/ [Accessed 27 Jan. 2020].

Framework, B. (2019). Data Types: Structured vs. Unstructured Data | Big Data Framework©.
[online] Big Data Framework©. Available at: https://www.bigdataframework.org/data-
typesstructured-vs-unstructured-data/ [Accessed 27 Jan. 2020].

GARCÍA ALLER, M. (2019). Zara: Technology and User Experience as Drivers of Business
| IE Insights. [online] IE Insights. Available at:
https://www.ie.edu/insights/articles/zaratechnology-and-user-experience-as-drivers-of-
business/ [Accessed 27 Jan. 2020].