Pharmacy Management System Software Design Document, Assignments of Web Application Development

The pharmacy management system is a comprehensive web-based application designed to streamline the operations of fpt long chau, a chain of pharmacies. This software design document outlines the key features and functionalities of the system, including order processing, customer management, and reporting and analytics. It serves as a guide for the development team and stakeholders to ensure a cohesive and efficient implementation of the system.

Typology: Assignments

2023/2024

Uploaded on 07/29/2024

khoa-vo-2
khoa-vo-2 🇻🇳

16 documents

1 / 22

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
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
pf3
pf4
pf5
pf8
pf9
pfa
pfd
pfe
pff
pf12
pf13
pf14
pf15
pf16

Partial preview of the text

Download Pharmacy Management System Software Design Document and more Assignments Web Application Development in PDF only on Docsity!

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: GCS 1007 Learner’s ID: GCS200821, GCS210640, GCS 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 Student Name Cao Hoang Hai Trieu, Dao Vu Gia Thuan, Vo Huynh Dang Khoa Student ID

GCS210640, GCS200821,

GCS

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 D

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:

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.

Table Of Content

Table of Contents

  • supported by a set of user and system requirements. P1 Explore a business-related problem and produce a well-defined Problem Definition Statement
      1. Introduction
      • 1.1 Document purpose:
      • 1.2 Product scope:
      • 1.3 Intended audience and document overview:
      • 1.4 Definitions, Acronyms and Abbreviations
      1. Overall description
      • 2.1 Product overview
      • 2.2 Product functionality
      1. Sprcific requirements
      • 3.1 Use case Model
      • 3.2 Use case descroption
      • 3.3 WireFrame
  • P2 Determine any areas of risk related to the successful completion of your application.
  • been selected for the development of this application. P3 Research the use of software development tools and techniques and identify any that have
    • Conclusion:
  • Reference

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

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 No. Actor System Notes 1 Select Login link in the Home screen Display Login screen to the user See user login screen layout design below. 2 Fill in username and password Check username and password. If they are correct, the system displays the user home screen. If they are wrong, display a warning. See user home screen layout design below.

Select the “Manage medicines” link. Get the medicine list from the database. Display the list in a medicine index page. See register screen layout design below. 2 Select “Details”. Display the medicine detail view See medicine detail layout design below Alternative 1: Create new medicines Step No. Actor System Notes 1 Select the “ Create new ”. Display the medicine creating view See medicine create layout design below. 2 Fill in medication information Validate the medication information. Display error if the input is not valid Create a new medicine in the database. Redirect to the medicine index view. See medicine index layout design below Alternative 2: Edit medicines Step No. Actor System Notes 1 Select the “ Edit ”. Display the medicine editing view See medicine edit layout design below 2 Fill in medication information Validate the medication information. Display error if the input is not valid Edit this medication information in the database. Redirect to the medicine index view. See medicine index layout design below Alternative 3: Delete medicines Step No. Actor System Notes 1 Select “Delete”. Display the medicine deleting view. See medicine delete layout design below. 2 Confirm delete Delete medication information in the database. See medicine index layout design below.

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 No. Actor System Notes 1 Select “Category request” in the home page. Display the category request view. See category request layout design below. 2 Input category name and the description. Validate the category request. Display error if the input is not 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 No. Actor System Notes 1 Select “Category request” on the home page. Get the unapproved request list from the database. Display the list in the view. See category request approval layout design below. 2 Select “ Approve “ A new category is created in the database. The request status is changed to “approved”. Alternative 1: Disapprove category Step No. Actor System Notes 1 Select “Deny”. The request status is changed to “denied”. 3.3 WireFrame

Figure 4 : Sign up page Figure 5 : Profile page

Figure 6 : Cart page Figure 7 : Manage account

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

application.

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