Higher Nationals in Computing

UNIT 30

APPLICATION DEVELOPMENT
ASSIGNMENT
No.1

Learner’s name: NAMES OF ALL STUDENTS IN A GROU{P –Dao Vu Gia Thuan, Cao Hoang
Hai Trieu, Vo Huynh Dang Khoa
Assessor name: Nam Lam
Class: GCS1007
Learner’s ID: GCS200821, GCS210640, GCS210751
Subject’s ID:
Assignment due: Assignment submitted
 ASSIGNMENT 1 FRONT SHEET

Qualification BTEC Level 5 HND Diploma in Business

Unit number and title Unit 30: Application Development

Submission date Date Received 1st submission

Re-submission Date Date Received 2nd submission

Cao Hoang Hai Trieu, Dao Vu

GCS210640, GCS200821,
Student Name Gia Thuan, Vo Huynh Dang Student ID
GCS210751
Khoa

Class GCS1007 Assessor name Lam Nguyen Trung Nam

Student declaration
I certify that the assignment submission is entirely my own work and I fully understand the consequences of plagiarism. I understand that
making a false declaration is a form of malpractice.

Student’s signature

Grading grid
P1 P2 P3 M1 M2 D1
 Summative Feedback:  Resubmission Feedback:

Grade: Assessor Signature: Date:

Internal Verifier’s Comments:

Signature & Date:

1
 Assignment Brief 1 (RQF)
Higher National Certificate/Diploma in Computing
Student Name/ID Number:
Unit Number and Title: Unit 30: Application Development
Academic Year: 2024
Unit Assessor: Nam Lam
Assignment Title: Analysis and Design solution for a given problem
Issue Date: 25 Mar 2024
Submission Date:
Internal Verifier Name:
Date:

Submission Format:

Format: The submission is in the form of two documents/files

● An individual SRS document in PDF format. Writing must be professional.

● An individual evaluation document in PDF format. Writing must be professional.

Submission

● Students are compulsory to submit the assignment on the due date and in a way requested by the
Tutor.
● The form of submission will be a soft copy posted on http://cms.greenwich.edu.vn/.
● Remember to convert the word file into a PDF file before the submission on CMS.
Note:

● The individual Assignment must be your work, and not copied by or from another student.
● If you use ideas, quotes, or data (such as diagrams) from books, journals, or other sources, you
must reference your sources, using the Harvard style.
● Make sure that you understand and follow the guidelines to avoid plagiarism. Failure to comply
with this requirement will result in a failed assignment.

Unit Learning Outcomes:

2
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

Assignment Brief and Guidance:

Scenario: FPT Long Chau is a chain of pharmacies. They have many stores which operate in many
provinces in Vietnam. In this regard, FPT Long Chau will be a web-based software system to aid
pharmacies (medicine) customers and owners to manage their drug (medicine) purchases and sales about
simplifying and speeding up the process of selection, ordering, and purchasing drugs for customers as
well as managing a database of users and a database of products for the owners. The attached document
can view the detailed description of those roles (Requirements.docx).

Tasks
You and your teammates (3 members/team maximum) need to prepare a software design document with
the following sections:
o A requirement specification that explores the problem by a set of user and system requirements,
as well as determines any risks related to the successful completion of your application. You are
advised to use an SRS template or modify one to complete this task.
o An evaluation section in which you research the use of software development tools and techniques
and identify any that have been selected for the development of this application. You should
compare them and justify your choices.
o A design section in which you use chosen tools from the previous step to produce design diagrams
for your solution based on the requirement specification.

3
Learning Outcomes and Assessment Criteria (Assignment 1):
Learning Outcome Pass Merit Distinction
LO1 P1 Explore a M1 Analyse a D1 Justify the tools
business-related business-related and techniques chosen
problem and produce problem using to realise a custom-
appropriate methods built website. Justify
a well-defined
and produce a well- your preferred
Problem Definition
structured Software selection of tools and
Statement supported Design Document that techniques in
by a set of user and defines a proposed deducing an
system requirements. solution and includes appropriate solution to
relevant details on a business-related
P2 Determine any requirements, system problem.
areas of risk related to analysis, system
the successful design, coding, testing
completion of your and implementation.
application.
LO2 P3 Research the use M2 Compare the
of software differences between
development tools and the various software
techniques and development tools and
identify any that have techniques researched
been selected for the and justify your
development of this preferred selection as
application. well as your preferred
software development
methodology.

4
 Table Of Content

Table of Contents
P1 Explore a business-related problem and produce a well-defined Problem Definition Statement
supported by a set of user and system requirements. ................................................................... 6
1. Introduction .................................................................................................................................. 6
1.1 Document purpose:.............................................................................................................................................6
1.2 Product scope: .....................................................................................................................................................6
1.3 Intended audience and document overview: ....................................................................................................6
1.4 Definitions, Acronyms and Abbreviations .......................................................................................................7
2. Overall description ........................................................................................................................ 7
2.1 Product overview ................................................................................................................................................7
2.2 Product functionality ..........................................................................................................................................8
3. Sprcific requirements .................................................................................................................... 8
3.1 Use case Model ....................................................................................................................................................8
3.2 Use case descroption ...........................................................................................................................................9
3.3 WireFrame ........................................................................................................................................................12

P2 Determine any areas of risk related to the successful completion of your application. .......... 17
P3 Research the use of software development tools and techniques and identify any that have
been selected for the development of this application. ............................................................... 17
Conclusion: ..................................................................................................................................... 18
Reference ................................................................................................................................ 20

5
 ASSIGNMENT 1 ANSWERS
P1 Explore a business-related problem and produce a well-defined Problem
Definition Statement supported by a set of user and system requirements.

1. Introduction

1.1 Document purpose:

The purpose of this document is to provide a detailed design for the FPT Long Chau software
system. This document will explain the system requirements in detail, including both user and
system requirements. It will also describe the tools and techniques chosen for application
development, along with the reasons for their selection. Finally, the document will provide detailed
design diagrams to illustrate how the system will operate and interact with users and other system
components.
The goal of this document is to ensure that the entire development team and stakeholders
understand the system requirements, the tools and techniques used, and the detailed design of the
application. It can also be used as a reference for future system deployment, maintenance and
expansion.
1.2 Product scope:
• Inventory Management: Efficient tracking and organization of pharmaceutical inventory,
including maintaining a comprehensive database of available medicines, their quantities,
expiration dates, and suppliers.
• Order Processing: Streamlined order management system allowing customers to browse a
catalog of available medicines, add items to their shopping carts, and proceed to checkout for
payment. Store owners can receive and process orders, update order statuses, and manage
delivery or pickup arrangements.
• Customer Management: Tools for managing customer accounts and profiles, including
registration, login, and access to order history. Customers can view and update their personal
information, track their orders, and receive notifications regarding order status and promotions.
• Shopping Cart and Checkout: User-friendly interfaces for customers to view their selected
items in the shopping cart, adjust quantities, and proceed to checkout. Secure payment
processing functionalities allow customers to complete transactions using various payment
methods, ensuring a smooth and secure checkout experience.
• Reporting and Analytics: Comprehensive reporting features for store owners to analyze sales
data, track inventory turnover rates, monitor customer preferences, and identify trends.
Customizable reports provide valuable insights for strategic decision-making and business
optimization.
• User and Product Databases: Centralized databases for storing user profiles, product
information, and transaction records. User profiles include authentication credentials, roles, and
permissions, while product databases contain details such as product names, descriptions,
prices, and availability.
1.3 Intended audience and document overview:
1.3.1 Intended Audience
Technical users:
+ The development team will provide software that satisfies the client's expectations if there is a
clear list of specifications. SRS will assist us in determining the project's scope and cost.

6
Additionally, it also helps programmers organize their tasks and offers them an understanding of the
technological stack they will require. SRS documents provide designers a sense of the project so
they can modify it for the use case. Testers are given advice on how to write test cases that are
appropriate for the demands of the company.
+ In our situation, the technical users are team members who will implement the system based on
the design from the SRS.
Non-technical users:
+ This section will include users, professors. It allows everyone to quickly become familiar with the
project and have a helicopter view of possible results, helping the end-user understand the
software’s functionality, and giving a clear picture of the entire project so they can understand the
app’s features and how they link to the project.
+ In our situation, the technical users are web users and professors who will give feedback for the
requirements and design.
1.3.2 Document Overview
These individuals will be responsible for creating user guides, help documentation, and support
materials for the web app. They will need a comprehensive understanding of the app's features and
functionalities.
1.4 Definitions, Acronyms and Abbreviations
• Cascading Style Sheets (CSS) - A style sheet language controlling the appearance of HTML
documents.
• Hypertext Transfer Protocol (HTTP) - The protocol for transmitting data over the World Wide
Web.
• HyperText Markup Language (HTML) - The standard markup language for web pages and
applications.
• JavaScript Object Notation (JSON) - A lightweight data format for exchanging information
between server and web app.
• Structured Query Language (SQL) - A language for managing and manipulating relational
databases. •User Interface (UI) - The visual elements and layout of a web application for user
interaction. •Uniform Resource Locator (URL) - An address used to access resources on the
internet.
• User Experience (UX) - The overall experience a user has while interacting with a web app.
2. Overall description

2.1 Product overview

The FPT Long Chau software system is a new, self-contained product designed to revolutionize the
management of pharmaceutical purchases and sales within the FPT Long Chau chain of
pharmacies. It is not a follow-on member of a product family or a replacement for existing systems
but rather a standalone solution tailored to meet the specific needs of pharmacy management.
Customer Sub-system
• Customer interface: Interface for customers to browse the drug list, add products to cart and
make payment.
• Account management: Manage customer accounts, including registration, login and personal
information management.
• Order management: Process customer orders, including placing orders, identifying orders and
tracking order status.

7
• Shopping Cart: Display and manage the customer's shopping cart, allowing to add/edit/delete
items in the shopping cart.
• Payment Processing: Payment processing for orders, including secure and trusted online
payment methods.
Administration Sub-system
• Inventory management: Medicine inventory management, including adding/deleting/editing
product information, tracking inventory and managing suppliers.
• Order Processing: Processing orders from customers, including order confirmation, delivery
and invoicing.
• Reporting and analytics: Provides tools to analyze sales data, revenue, profits, and other
revenue numbers.
• User management: User account management, including registration, login and user
information management.
• System configuration: System configuration, including installation management and system
setup.
2.2 Product functionality
- Manage inventory of pharmaceutical products.
- Allow customers to browse and search for medicines.
- Enable customers to add items to their shopping cart.
- Facilitate secure online payments for purchases.
- Provide order tracking and status updates for customers.
- Support account management for both customers and administrators.
- Generate reports and analytics on sales, inventory, and customer behavior.
- Administer user access and permissions.
- Process orders from customers, including order confirmation and fulfillment.
- Facilitate communication between customers and administrators, such as through messaging or
support tickets.
3. Sprcific requirements

3.1 Use case Model

8
 Figure1: Pharmacies Management System
3.2 Use case descroption
Use case 1: login
Pre-conditions: Users have registered an account
Post-conditions: User is redirected to Home Screen. Users can now access the profile page and
purchase medicine
Use case Normal steps:
Step
Actor System Notes
No.
Select Login link in the Home Display Login screen to the See user login screen
1
screen user layout design below.
Fill in username and Check username and password. See user home screen
password If they are correct, the system layout design below.
2 displays the user home screen.
If they are wrong, display a
warning.

9
Alternative 1: Register account

Step
Actor System Notes
No.
Select “Register a new Display Register Screen to the See register screen
1
account”. user. layout design below.
Fill in request information. Validate the user information See user home screen
at both front-end and back-end. layout design below.
Use that information to send a
query to the database to create
2 a new customer account.

Login the user to that new

account. Redirect the user to
the home page.

Use case 2: Purchase medicines

Pre-conditions: Users has already logged into a customer account
Post-conditions: An order will be recorded to the system database. User is redirected to the profile
page
Use case Normal steps:
Step
Actor System Notes
No.
Select “Add to Cart” button Add the medicine to the cart
1
from a medicine detail page. table in the database.
Select the “Cart” link in the Show the cart index with item
2
navigation bar. list and total price in the view.
Edit the amount of product or Use Ajax to change the The quantity is
remove ones. medicine quantity in the cart checked to not be
3 database. negative or exceed the
medicine’s stocked
quantity.
Click “Confirm” to purchase. Validate the item in the back- The medicine’s left
end. quantity will decrease
Create a new order in the based on the items in
4 database. the cart.

Redirect the user to the profile The cart is deleted

page. after this step.

Use case 3: Manage medicines

Pre-conditions: User has logged into a store owner account
Post-conditions: Changes are made in the madicine database
Use case Normal steps:
Step
Actor System Notes
No.

10
 Select the “Manage Get the medicine list from the See register screen
medicines” link. database. layout design below.
1
Display the list in a medicine
index page.
Select “Details”. Display the medicine detail See medicine detail
2
view layout design below

Alternative 1: Create new medicines

Step
Actor System Notes
No.
Select the “ Create new ”. Display the medicine creating See medicine create
1
view layout design below.
Fill in medication information Validate the medication See medicine index
information. Display error if layout design below
the input is not valid
2
Create a new medicine in the
database. Redirect to the
medicine index view.

Alternative 2: Edit medicines

Step
Actor System Notes
No.
Select the “ Edit ” . Display the medicine editing See medicine edit
1
view layout design below
Fill in medication information Validate the medication See medicine index
information. Display error if layout design below
the input is not valid

2 Edit this medication

information in the database.

Redirect to the medicine index

view.

Alternative 3: Delete medicines

Step
Actor System Notes
No.
Select “Delete”. Display the medicine deleting See medicine delete
1
view. layout design below.
Confirm delete Delete medication information See medicine index
2
in the database. layout design below.

11
 Redirect to the medicine index
view.

Use case 4: Make new category request

Pre-conditions: User has logged into a store owner account
Post-conditions: A new category request is added to the database
Use case Normal steps:

Step
Actor System Notes
No.
Select “Category request” in Display the category request See category request
1
the home page. view. layout design below.
Input category name and the Validate the category request.
description. Display error if the input is not
2 valid.
Create a new category request
in the database.

Use case 5: Approve new category request

Pre-conditions: User has logged into an admin account.
Post-conditions: A new category is added if the request is approved
Use case Normal steps:

Step
Actor System Notes
No.
Select “Category request” on Get the unapproved request list See category request
1 the home page. from the database. Display the approval layout design
list in the view. below.
Select “ Approve “ A new category is created in
the database.
2
The request status is changed
to “approved”.

Alternative 1: Disapprove category

Step
Actor System Notes
No.
Select “Deny”. The request status is changed
1
to “denied”.

3.3 WireFrame

12
Figure 2: Home screen

Figure 3: Product detail

13
Figure 4: Sign up page

Figure 5: Profile page

14
 Figure 6: Cart page

Figure 7: Manage account

15
Figure 8: Medicine manage

Figure 9: Sitemap

16
P2 Determine any areas of risk related to the successful completion of your
application.

List Additional Controls (if any -

Identify and list List Current Risk Risk where current controls are not
Hazards Controls Rating adequately managing the level of
risk)
1 Technical Regular security patches, Implement intrusion detection
vulnerabilities penetration testing Hight system
2 Low user User feedback collection, Medium Launch targeted marketing
engagement UI improvements campaigns
3 Payment processing Redundant payment Hight Establish manual payment backup
failure gateways, error monitoring procedures
4 Project timeline Detailed project planning, Medium Allocate extra resources for
delays frequent progress checks critical path tasks
5 Inadequate data Regular data backups, off- Medium Perform periodic data recovery
backups site storage drills
6 Integration Thorough integration Medium Collaborate with third-party
complexities testing, clear API support for troubleshooting
documentation
7 User experience Usability testing, iterative Medium Conduct focus groups for user
dissatisfaction UI enhancements feedback
8 Changes in the Monitor industry trends, Medium Stay up to date on industry trends
technology adapt to emerging
landscape technologies.
9 Incorrect or corrupt Data integration checks, Medium Establish regular data quality
data item data validation processes assessment and maintenance
routines

P3 Research the use of software development tools and techniques and identify
any that have been selected for the development of this application.

My assignment involves researching and identifying selected software development tools and
techniques for application development. Here are the specific steps and tasks I took:

Research Existing Tools and Techniques

- Conduct research on software development tools and techniques available on the market.
- Learn about the features, advantages, limitations, and suitability of each tool and technique in
the context of your project.

Identifying Selected Tools and Techniques

17
- Look up project documents or join a meeting with the development team to know the selected
tools and techniques.
- Identify a list of software development tools (IDEs, frameworks, version control, testing tools,
etc.) and techniques (Agile, Scrum, Waterfall, etc.)

Assessment of Suitability and Advantages of Tools and Techniques

- Evaluate the suitability of selected tools and techniques with project requirements.
- Identify the advantages that each tool and technique bring to the development process.

Limitations and Risks Analysis

- Assess limitations and risks associated with the use of selected tools and techniques.
- Consider potential issues that could impact performance, security, integration, and more.

Compare Options

- If multiple tools or techniques are considered, compare them based on criteria like performance,
integration, community support, etc.
- Make a comparison table to help make an informed decision about the final choice.

Making Reports and Proposals

- Generate reports on the results of your research on selected tools and techniques.
- Recommend the use of specific tools and techniques for the project, including reasons and detailed
explanations.

Sharing Information with the Development Team

- Present research findings and recommendations to the development team, so that they have an
overview of the tools and techniques to be used. Support in the Deployment Process
- Provide support to the development team in implementing and using selected tools and
techniques. This assignment helps me gain insight into the tools and techniques that will be used
in the software development process, thereby ensuring harmony and efficiency in the project
implementation.

Conclusion:

After performing and analyzing tasks related to research and identifying software development
tools and techniques, I was able to learn several important things:

I will gain a better understanding of the software development tools and techniques available in the
market, as well as how they work, the advantages and limitations of each type of tool and
technique. I already know how to assess which tools and techniques are best suited to the specific
requirements and context of the project or application you are working on. I have developed the
ability to compare and evaluate different options. This helps me make decisions based on a deep
understanding of the factors involved. Learn how to create reports with technical information in a
specific and easy to understand way. This skill will be useful in presenting ideas and suggestions to

18
colleagues or management. On how to work effectively with a team and achieve common goals.
Communicating information clearly and effectively is also an important skill. During the research
process, challenges and risks may arise. Ability to cope and find solutions to overcome these
difficulties. The knowledge and skills I learn from studying tools and techniques can be directly
applied to my project or work. This enhances practicability and improves work performance.

19
Reference

Perforce. (n.d.). How to Write a Software Requirements Specification (SRS) Document. Retrieved
from https://www.perforce.com/blog/alm/how-write-software-requirements-specification-srs-
document (Accessed: 15 April 2024 )

ScienceDirect. (n.d.). User Requirement. In Encyclopedia of Electrical and Electronics Engineering.

Retrieved from https://www.sciencedirect.com/topics/engineering/user-requirement (Accessed:
15 April 2024 )

Wikipedia. (n.d.). System Requirements. Retrieved from

https://en.wikipedia.org/wiki/System_requirements (Accessed: 15 April 2024 )

Creately. (n.d.). UML Diagram Types with Examples. Retrieved from

https://creately.com/blog/diagrams/uml-diagram-types-examples/ (Accessed: 15 April 2024 )

StayStaffed. (n.d.). Web-Based Software. Retrieved from https://www.staystaffed.com/web-

based-software/ (Accessed: 15 April 2024 )

ScienceDirect. (n.d.). User Requirement. In Encyclopedia of Electrical and Electronics Engineering.

Retrieved from https://www.sciencedirect.com/topics/engineering/user-requirement (Accessed:
15 April 2024 )

Tara AI. (n.d.). Software Design Documents Template. Retrieved from

https://blog.tara.ai/software-design-documents-template/ (Accessed: 15 April 2024 )

Investopedia. (n.d.). Risk Analysis. Retrieved from https://www.investopedia.com/terms/r/risk-

analysis.asp (Accessed: 15 April 2024 )

Guru99. (n.d.). Top 20 Software Development Tools. Retrieved from

https://www.guru99.com/software-development-tools.html (Accessed: 15 April 2024 )

Synopsys. (n.d.). Top 4 Software Development Methodologies. Retrieved from

https://www.synopsys.com/blogs/software-security/top-4-software-development-
methodologies/ (Accessed: 15 April 2024 )

20