MINISTRY OF EDUCATION & TRAINING

HO CHI MINH CITY UNIVERSITY OF ECONOMICS AND FINANCE

FINAL PROJECT
Course: : Software Engineering
Course code: ITE1125E

NEWSPAPER SELLNG MANAGEMENT

Members Name : Do Anh Duy – 215050916

Nguyen Tran Quoc Tinh - 215050518
Pham Viet Tinh – 215051799
Nguyen Lam Hoang Long - 215051700

Class: A03E

Ho Chi Minh city - 04/2024

 MINISTRY OF EDUCATION & TRAINING
HO CHI MINH CITY UNIVERSITY OF ECONOMICS AND FINANCE

FINAL PROJECT
Course: Software Engineering
Course code: ITE1125E

E-STORE MANAGEMENT

Members Name: : Do Anh Duy -215050916

Nguyen Tran Quoc Tinh - 215050518
Pham Viet Tinh – 215051799
Nguyen Lam Hoang Long – 215051700

Class: A03E
Instructor: Nguyen Thi Thanh Truc

Ho Chi Minh city - 04/202

TABLE OF CONTENTS

I. Software Requirements Specification document...................2

1. Introduction............................................................................................2
2. Overall Description...............................................................................2
3. Specific Requirements.........................................................................3

II. SOFTWARE DETAIL DESIGN..................................................4

1.1. Use case diagram.................................................................................4
1.1.1. Use case specification.................................................................4
1.1.1 UC01.............................................................................................5
1.1.2 UC02.............................................................................................5
1.1.3 UC03.............................................................................................6
1.1.4 UC04.............................................................................................7
1.1.5 UC05.............................................................................................8
1.1.6 UC06.............................................................................................8
1.1.7 UC07.............................................................................................9
1.1.8 UC08...........................................................................................10
1.1.9 UC09...........................................................................................10
1.2. Sequence Diagram............................................................................12
1.2.1. Login...........................................................................................12
1.2.2. Order............................................................................................12
1.2.3. StaffInfor.....................................................................................13
1.2.4. ItemInfor......................................................................................13
1.2.5. CreateBill.....................................................................................14
1.2.6. Report..........................................................................................14
1.2.7. Delivery.......................................................................................15
1.3. State diagram....................................................................................15

-i-
 1.3.1. Order............................................................................................15
1.3.2 Manage Order..............................................................................16
1.4 Activity Diagram...................................................................................16
1.4.1 Manage Order..............................................................................17
1.5 Class.......................................................................................................18
1.6 Database................................................................................................19
1.7 USER INTERFACE.............................................................................19

III. TASK ASSIGNMENT TABLE................................................22

- ii -
I. Software Requirements Specification document

1. INTRODUCTION

Purpose

The purpose of this document is to specify the requirements for the Newspaper
Management Software. This document will be used by the development team to
design and implement the software.

Scope

The software will provide a comprehensive suite of features to manage all aspects
of the newspaper business, including:

 Subscription management
 Distribution management
 Financial management

2. OVERALL DESCRIPTION

This project focuses on developing a system to improve the management

and efficiency of newspaper sales. It aims to streamline processes for both
print and potentially digital subscriptions, while considering the role of
advertising revenue.

2.1 System Architecture

The software will be a desktop application.

2.2 System Interfaces

The software will have the following interfaces:

 User interface: The user interface will allow users to interact with the
software.
 Database interface: The database interface will allow the software to
access and store data.

2.3 Hardware and Software Requirements

The software will require the following hardware and software:

 Hardware:

- iii -
 o A computer with a Intel proccesor or AMD.
o An internet connection.
 Software:
o A PDF reader
o Microsoft SQL.

2.4 Security Features

The software will have the following security features:

 User authentication and authorization

 Data encryption
 Secure payment processing

3. SPECIFIC REQUIREMENTS

3.1 Functional Requirements

The software will provide the following functional requirements:

 Subscription management:
o Allow users to create, edit, and cancel subscriptions
o Process payments for subscriptions
o Manage customer accounts
 Distribution management:
o Manage the distribution of newspapers to subscribers and
newsstands
o Track delivery status

3.2 Non-Functional Requirements

The software will meet the following non-functional requirements:

 Usability: The software will be easy to use and understand.

 Performance: The software will be responsive and efficient.
 Reliability: The software will be available 24/7.
 Scalability: The software will be able to handle a large number of users and
transactions.
 Security: The software will be secure and protect user data.

- iv -
II. SOFTWARE DETAIL DESIGN

1.1. USE CASE DIAGRAM

Use case, Use case specification, Sequence diagram, Activity diagram, State,
Class diagram, ERD. Context diagram (FDD) UI (User Interface) - Databse (ERD) -
SRS (software Requirement Specification)

1.1.1.

Use case specification

-v-
1.1.1 UC01

Use Case ID UC01

Use Case ViewItems

Description Can view all information of items in application

(Actor) Customer

Pre-conditions  Have a device installed application and connect

with wifi
(Flow) (Basic)

1. Select item
2. View this item

 (Alternative)
 2. Reload if can’t view this item
(Exception)

 1. If view button not working just show message

“error”
 2. If can’t load the information of item just show
message “over load”

Post-conditions Access successfully

View all of item

1.1.2 UC02

Use Case ID UC02

Use Case Log in

Description Login to become member for order if you want

(Actor) Customer

- vi -
 Pre-conditions Already have account

(Flow) (Basic)

1. Click on button login

2. Type information account
3. Confirm

 (Alternative)
 2. If not have account, you have to sign up
 2.1 Need to type username, password, email,
phone number, address
 2.2 Get OTP code from phone number to confirm
 2.3 Confirm sign up
Ngoại lệ (Exception)

 2. Wrong information
 3. Loss internet
Post-conditions Login successfully

Can order items

1.1.3 UC03

Use Case ID UC03

Use Case Order

Description Order item to own this item

(Actor) Customer

Pre-conditions Already have account

(Flow) (Basic)

1. Select item and quantity

2. Chose payment method

- vii -
 3. Confirm

 (Alternative)
 1. If not enough quantity of this items, show
message
 2. Select cash or card
 2.1 If cash, call to customer for confirm and pay
when the item was delivered
 2.2 If card, get OTP code for confirm payment
Ngoại lệ (Exception)

 2.1 Not confirm

 2.2 Not enough money
Post-conditions Ordered successfully

Can view order information

1.1.4 UC04

Use Case ID UC04

Use Case CreateOrder

Description Make an order from customer

(Actor) Manager

Pre-conditions Must have manager account

(Flow) (Basic)

1. Chose “order form” on UI application

2. Select the order by customer
3. Approve this order
(Alternative)

(Exception)

1. Not login manager account

 3. Not approve

- viii -
 Post-conditions Make order successfully

Can view order information

1.1.5 UC05

Use Case ID UC05

Use Case ItemsInfo

Description Manage item, can edit item information

(Actor) Manager

Pre-conditions Must have manager account

(Flow) (Basic)

1. Chose “items form” on application

2. Select the items to view information or edit
(Alternative)

2. If edit finish, click “confirm” button to save new

information

(Exception)

1. Not login manager account

Post-conditions Edited successfully

1.1.6 UC06

Use Case ID UC06

Tên Use Case StaffInfo

Description Manage and edit staff information

(Actor) Manager

Pre-conditions Must have manager account

- ix -
 (Flow) (Basic)

1. Chose “Staff form” on UI application

2. Select staff information to view or edit
(Alternative)

2. If edit finish, click “confirm” button to save new

information

(Exception)

1. Not login manager account

Post-conditions Edited successfully

1.1.7 UC07

Use Case ID UC07

Use Case Delivery

Description Delivery to customer by the order code from manager

(Actor) Manager

Pre-conditions Already have an order code from manager

(Flow) (Basic)

1. Call to customer for confirm

2. Repare items for delivery
3. Delivery
4. Payment
(Alternative)

4.1 If cash payment, get enough money and

confirm

-x-
 4.2 If card payment, just delivery confirm
(Exception)

1. Not confirm
2.1 Not enough money
Post-conditions Delivered successfully

1.1.8 UC08

Use Case ID UC08

Use Case CreateBill

Description Staff make a receipt base on order from manager

(Actor) Staff

Pre-conditions Must have staff account

In a work time

(Flow) (Basic)

1. Chose “Order form” on UI application

2. Select order want to make receipt
3. Confirm
(Alternative)

(Exception)

3. Not confirm

Post-conditions Made receipt successfully

1.1.9 UC09

Use Case ID UC09

- xi -
Use Case Report

Description Report revenue and quantity were sell of day

(Actor) Staff

Pre-conditions Must have staff account

In a work time

(Flow) (Basic)

1. Close the shift

2. Input money cash on system
3. Confirm
4. Print report
(Alternative)

4.Can print anytimes you want

(Exception)

1. Not close the shift

2. Money cash must to correct with total turnover on
system
3. Not confirm

Post-conditions Check revenue and quantity were sell

- xii -
 1.2. SEQUENCE DIAGRAM

1.2.1. Login

1.2.2. Order

- xiii -
1.2.3. StaffInfor

1.2.4. ItemInfor

- xiv -
1.2.5. CreateBill

1.2.6. Report

- xv -
1.2.7. Delivery

1.3. STATE DIAGRAM

1.3.1. Order

- xvi -
 1.3.2 Manage Order

1.4 ACTIVITY DIAGRAM

 1.4.1 Order

- xvii -


1.4.1 Manage Order

- xviii -
1.5 CLASS

- xix -
1.6 DATABASE

1.7 USER INTERFACE

- 20 -
 LOGIN FORM

PRODUCT MANAGER FORM

- 21 -
BILL OUTPUT FORM

- 22 -
III. TASK ASSIGNMENT TABLE

Position FULL NAME TASK

Number
1 Do Anh Duy - User Interface design.
- Complete final report.
- State Diagram design.
2 Pham Viet Tinh - Class design
- Presentation design
3 Nguyen Tran Quoc Tinh - Sequence diagram
design
4 Nguyen Lam Hoang Long - Backend coding.
- Database design
- Use case design

- 23 -