<span class="text_page_counter">Trang 1</span><div class="page_container" data-page="1">

<b>ASS PROJECT REPORTSoftware Requirement Specification</b>

</div><span class="text_page_counter">Trang 2</span><div class="page_container" data-page="2">

3. Use Cases Diagram...5

4. Use Cases Details...5

4.6. Edit account information...12

4.7. View accounts list...13

4.8. Create business profile...14

4.9. View business profile...15

4.10. Edit business profile...15

4.11. Read e-invoice data...16

4.12. Extract e-invoice processing...17

4.13. Decompress file processing...18

4.14. Save invoice information...19

4.15. View e-invoice list...20

4.16. View e-invoice detail...21

4.17. Update an e-invoice status...22

4.18. Upload e-invoice file in mailbox...23

4.19. Import e-invoice files...23

4.20. Export e-invoice xml files...24

4.21. Search & filter invoices...25

</div><span class="text_page_counter">Trang 3</span><div class="page_container" data-page="3">

4.23. Read email content & get mail attachments...27

4.24. View assigned business list...28

4.25. View business detail...29

4.26. View businesses list...30

4.27. Upload tax declaration...30

4.28. Update tax declaration...31

4.29. Save history changes of tax declaration...32

4.30. View changes of tax declaration...33

4.31. Upload financial statement...34

4.32. Update financial statement...35

4.33. Save history changes of financial statement...36

4.34. View history changes of financial statement...37

4.35. Create business provider...37

4.36. Update business provider...38

4.37. Delete business provider...39

4.38. View list business provider...40

4.39. View system statistic for admin...41

4.40. View invoice statistic for business...41

4.41. View business provider statistic for business...42

VI. Functional Requirements...43

1. System Functional Overview...43

Title: A clear and descriptive title that represents the content and purpose of the document.

Document Version/Revision Number: If applicable, indicate the version or revision number of the document. This helps in tracking changes and ensuring everyone is referring to the latest version.

Date: The date when the document was created or last updated. This is important for reference and version control.

Author(s) or Team: The names or organization of the individuals or team responsible for creating the document. This provides accountability and a point of contact for queries.

</div><span class="text_page_counter">Trang 4</span><div class="page_container" data-page="4">

the specific project under discussion.

Logo or Graphic (Optional): If the document represents a specific organization or company, including its logo or a relevant graphic can enhance branding and recognition.

Abstract or Executive Summary (Optional): A brief summary of the document's key points, objectives, and scopecan be included on the first page to provide readers with an overview without delving into the details immediately.

Table of Contents: While the table of contents is already listed, it should be repeated on the first page for easy navigation, allowing readers to quickly locate specific sections within the document.

Use Cases Details: Comprehensive descriptions of specific use cases, outlining steps, interactions, and expected outcomes for each scenario.

Sign up: The process through which a user creates a new account on the system, providing necessary information for account setup.

Sign in: The action of logging into the system using valid credentials, granting access to user-specific functionalities.

Sign Out: The action of ending the user's session, ensuring secure disconnection from the system.

Reset Password: The procedure allowing users to regain access by resetting forgotten passwords through a secureverification process.

Create Account: The action of registering a new user or entity in the system, involving the provision of necessary information and account setup.

Edit Account Information: The functionality enabling users to modify their profile details, ensuring accurate and up-to-date information.

View Accounts List: The feature displaying a list of user accounts for administrative or reference purposes.Create Business Profile: The process of setting up a business profile within the system, including necessary business details and contact information.

View Business Profile: The functionality allowing users to access detailed information about a specific business profile.

Edit Business Profile: The action of modifying or updating information within a business profile.

Read E-invoice Data: The functionality to retrieve electronic invoice data from the system for further processing.Extract E-invoice Processing: The process of extracting relevant information from electronic invoices for analysisand storage.

Decompress File Processing: The action of unpacking compressed files, typically used for handling attachments or uploaded files.

Save Invoice Information: Storing invoice-related data securely within the system for future reference and keeping.

</div><span class="text_page_counter">Trang 6</span><div class="page_container" data-page="6">

help me provide accurate tax-related advice to my clients.

As a business provider, I want the ability to delete outdated or irrelevant information from my business profile. This will allow me to maintain the accuracy and relevance of my business data.

As a user, I want to easily search and filter electronic invoices based on specific criteria such as date, amount, or issuer. This will help me quickly find the information I need.

As a user, I want to receive confirmation emails after uploading important documents or making changes to my account. This will provide me with reassurance that my actions were successful.

As a support agent, I want a ticketing system that categorizes customer inquiries, allowing me to prioritize and address urgent issues promptly.

As a business owner, I want the ability to export financial statements and tax declarations in different formats, facilitating easy sharing with relevant stakeholders.

Q5. [1.5p]

Screen 1: Dashboard

Description: The dashboard screen is the main hub of the application, providing users with an overview of their key metrics and data. It presents summarized information and allows users to navigate to different sections.Components:

Graphs, charts, or visualizations showcasing important dataSummary of key metrics

Navigation menu or sidebar

Quick access links to frequently used featuresScreen 2: Project Details

Description: The project details screen displays specific information about a selected project. It allows users to view and manage project-related data, tasks, and progress.

Components:Project name and detailsProject timeline or Gantt chartList of tasks and milestonesProgress tracking and completion statusFile attachments and project documentationScreen 3: Calendar

Description: The calendar screen provides users with a visual representation of their schedule and upcoming events. It allows users to manage appointments, meetings, and deadlines.

Monthly or weekly calendar view

</div><span class="text_page_counter">Trang 7</span><div class="page_container" data-page="7">

Ability to add, edit, and delete eventsReminders and notificationsScreen 4: Document Library

Description: The document library screen organizes and displays a collection of files and documents. It allows users to browse, search, and manage their files effectively.

File directory or folder structure

List of files with details (name, size, date modified)Search and filter options

File preview or download functionalityScreen 5: Reports

Description: The reports screen presents users with analytical insights and data summaries. It allows users to generate, customize, and export reports based on their specific requirements.

Report templates or categoriesCustomization options (date range, filters)Visualization of data (charts, tables, graphs)Export options (PDF, Excel, etc.)

Please note that these are general examples, and the actual screen details may vary depending on the specific application or system requirements.Q6. [1p]

- Complete section IV Business rules

Q6. [0.5p]

Database Management System (DBMS):

Description: The ASS Project may interact with a specific database management system where user data, business profiles, invoices, and other relevant information are stored.

Purpose: To store, retrieve, and manage data efficiently for the application's functionalities.Email Services:

Description: The system might integrate with email services to send notifications, alerts, and communication to users.

Purpose: To notify users about account activities, invoice status updates, system changes, and other relevant information via email.

File Storage Services:

</div><span class="text_page_counter">Trang 8</span><div class="page_container" data-page="8">

invoices, and other files uploaded by users.

Purpose: To securely store and manage files, ensuring data integrity and availability.Tax Department API:

Description: An API provided by the tax department for exchanging tax-related information, verifying tax declarations, and ensuring compliance.

Purpose: To validate tax-related data, cross-check declarations, and ensure accuracy in tax-related transactions.Payment Gateways:

Description: Third-party payment gateways (e.g., PayPal, Stripe) for processing payments related to the system, such as subscription fees or transactions between businesses.

Purpose: To facilitate secure and seamless financial transactions within the application.Notification Services:

Description: External notification services (e.g., Twilio) for sending SMS notifications to users' mobile devices.Purpose: To notify users about urgent account activities, invoice approvals, or other time-sensitive events via SMS.

</div><span class="text_page_counter">Trang 9</span><div class="page_container" data-page="9">

data. Ensuring robust security measures will instill user confidence, maintain legal compliance, and protect against cyber threats.

Description: Reliability indicates the system's ability to perform consistently and accurately under various conditions. It involves minimizing downtime, ensuring data accuracy, and providing consistent performance.Explanation: Reliability is vital for the ASS Project as users rely on the system for critical tasks such as submitting tax declarations and managing financial data. A reliable system ensures that users can trust the platform for their business operations without disruptions.

Description: Performance relates to the system's responsiveness, speed, and efficiency. It involves optimizing response times, minimizing latency, and ensuring the system can handle multiple concurrent users without significant slowdowns.

Explanation: Performance is critical to providing a seamless user experience, especially during peak usage times. A high-performing system ensures quick data processing, swift responses to user actions, and overall user satisfaction.

Description: Scalability refers to the system's ability to handle increased loads, users, or data volume without compromising performance. It involves designing the system architecture in a way that allows it to scale horizontally or vertically as demands grow.

Explanation: Scalability is essential for the ASS Project as the user base and data volume may increase over time.A scalable system ensures that the platform can accommodate a growing number of users, handle larger datasets, and maintain optimal performance, ensuring long-term viability and user satisfaction.

</div><span class="text_page_counter">Trang 10</span><div class="page_container" data-page="10">

Sub-task: Verify accuracy of entered data.

Sub-task: Categorize the invoice (e.g., date, vendor, amount).Tax Department Integration (Swimlane: IT Department):

Task: Access Tax Department website.Sub-task: Download the required sheet files.Sub-task: Verify the authenticity of downloaded files.

Data Comparison (Swimlane: Accounting Department & IT Department):

Task: Compare e-invoices data (from email) with downloaded sheet files.Sub-task: Identify discrepancies (if any).

Sub-task: Generate a report of matched and mismatched data.Validation (Swimlane: Accounting Department & IT Department):

Task: Validate compared data for accuracy and consistency.

Sub-task: Resolve discrepancies (if any) between e-invoices and downloaded files.Sub-task: Document the resolution process.

Task: Process complete.

Sub-task: Archive the processed invoice and related documents.Notes:

Each swimlane represents a specific department or entity involved in the process: Email System, Accounting Department, and IT Department.

Tasks and sub-tasks within each swimlane represent the specific actions taken by the corresponding department.The flow of the process is indicated by arrows connecting the tasks and sub-tasks in sequential order.Validation and verification steps are included to ensure the accuracy and reliability of the data being processed.

Q9. [1p]

+---+ | Invoice |+---+ | | create V

</div><span class="text_page_counter">Trang 25</span><div class="page_container" data-page="25">

matched with the information they registered with the Government

<b>4.9.View business profile</b>

<b>Name:View business profile</b>

Description: This feature allows business manager view their business profile

Trigger: Business manager want to view their profile

Pre-conditions: - User has login as business manager role- User account has “active” status

Post-conditions: User view their business profile successfully

- User click on “Avatar icon” and choose “Cá nhân”- The system display the business profile information

<b>4.10. Edit business profile</b>

<b>Name:Edit business profile</b>

</div><span class="text_page_counter">Trang 26</span><div class="page_container" data-page="26">

Primary Actor: Business manager

Description: This feature allows business manager edit their business profile

- Business manager have not created their business profile

Pre-conditions: - User has login as business manager role- User account has “active” status

Post-conditions: User create their business profile successfully

- User click on “Avatar” icon and choose “Cá nhân”

- User click “Cập nhật” button and update business profile information- The system will update the edited information and show successful message

Exceptions: <b>The email is invalid</b>

● ASS website returns error message.

<b>The tax number is invalid (must be 10-14 digits)</b>

● ASS website returns error message.

<b> The required field is empty</b>

● ASS website returns error message.

Business Rules: - Invoice received email must be the email using for receiving e-Invoices of that business

- Name, English name, tax number, represent person name of business must be matched with the information they registered with the Government

OtherInformation:

</div><span class="text_page_counter">Trang 27</span><div class="page_container" data-page="27">

<b>Name: Read e-invoice information</b>

Description: This feature allows ASS system to read e-invoice information

Trigger: The system receive the new mail with xml file attachment

- Mail is filtered as e-invoice mail

Post-conditions: Read e-invoice information successfully

- The system receive new email with xml file attachment- The system get xml file and read data based on predefined structure- Read and get data successfully

Exceptions: <b>The xml file is not matched the predefined structure</b>

● ASS website will skip that xml file and record as no xml file attached

Business Rules: - XML file must comply the structure of invoice xml file according to the law announced by the Tax Department

<b>4.12. Extract e-invoice processing</b>

<b>Name: Extract e-invoice processing</b>

</div><span class="text_page_counter">Trang 28</span><div class="page_container" data-page="28">

Description: This feature allows ASS system to extract required e-invoice information

Trigger: The system has read the e-invoice xml file successfully

Pre-conditions: XML file is matched with predefined structure

Post-conditions: Extract e-invoice information successfully

- The system has read xml file - The system extract required e-invoice data - The system match the data from e-invoice to database

Exceptions: <b>The xml file is not matched the predefined structure</b>

● ASS website will skip that xml file and record as no xml file attached

Business Rules: - XML file must comply the structure of invoice xml file according to the law announced by the Tax Department

<b>4.13. Decompress file processing</b>

<b>Name: Decompress file processing</b>

Description: This feature allows ASS system to decompress file attachments in mail

</div>