final project software engineering

VIETNAM GENERAL CONFEDERATION OF LABOUR TON DUC THANG UNIVERSITY FACULTY OF INFORMATION TECHNOLOGYFinal ProjectSoftware EngineeringAdvised by: MSc NGUYEN NGOC PHIENStudent: HUYNH THINH H

VIETNAM GENERAL CONFEDERATION OF LABOUR

TON DUC THANG UNIVERSITY FACULTY OF INFORMATION TECHNOLOGY

Final Project Software Engineering

Advised by: MSc NGUYEN NGOC PHIEN

Student: HUYNH THINH HUNG – 522H0023

DUONG NHUT KHUONG – 522H0014 NGUYEN NGOC THIEN – 522H0047 TRAN THI YEN PHUONG – 522H0084 PHAN THIET TRUNG – 522H0071

Course : 26

VIETNAM GENERAL CONFEDERATION OF LABOUR

TON DUC THANG UNIVERSITY FACULTY OF INFORMATION TECHNOLOGY

Final Project Software Engineering

Advised by: MSc NGUYEN NGOC PHIEN

Student: HUYNH THINH HUNG – 522H0023

DUONG NHUT KHUONG – 522H0014 NGUYEN NGOC THIEN – 522H0047 PHAN THIET TRUNG – 522H0071 TRAN THI YEN PHUONG – 522H0084

Course : 26

We extend our sincere appreciation to MSc Nguyen Quoc Binh for his expert guidance and steadfast support during the crafting of this report His extensive knowledge and insights have significantly enhanced our understanding and methodology in the study of Software Engineering We are profoundly thankful for his dedication, patience, and the considerable time he has devoted to us

THE PROJECT WAS COMPLETED AT

TON DUC THANG UNIVERSITY

I hereby declare that this is my project product and is guided by MSc Nguyen Ngoc Phien; The research content and results in this essay are honest and have not been published in any form before The data in the tables for analysis, comments, and evaluation were collected by the author from different sources and clearly stated in the reference section

In addition, the essay also uses a number of comments, assessments as well as data from other authors and other organizations, all with citations and source notes

If any fraud is discovered, I will take full responsibility for the content of my essay Ton Duc Thang University is not involved in copyright violations caused by me during the implementation process (if any)

Ho Chi Minh city, 14 April 2024 th

The author (Sign and write full name)

Huynh Thinh Hung

INSTRUCTOR VERIFICATION AND

EVALUATION SECTION

Confirmation from the instructor

Ho Chi Minh city, , 12 May 2024 th (Sign and write full name)

The teacher's evaluation part marks the test

Ho Chi Minh city, , 12 May 2024 th

SUMMARY

TABLE OF CONTENT

ACKNOWLEDGMENTS 3

INSTRUCTOR VERIFICATION AND EVALUATION SECTION 5

SUMMARY 6

1 Introduction 9

1.1 Purpose and Scope 9

1.1.1 Purpose 9

1.1.2 Scope 9

1.2 Product Overview 9

1.3 Structure of the Document 10

In this document: 10

1.4 Terms, Acronyms, and Abbreviations 10

2 Project Management Plan 11

2.1 Project Organization 11

2.2 Lifecycle Model Used 11

2.3 Risk Analysis 11

2.4 Hardware and Software Resource Requirements 11

2.5 Deliverables and Schedule 11

2.6 Monitoring, Reporting, and Controlling Mechanisms 11

2.7 Professional Standards 11

2.8 Evidence all the artifacts have been placed under configuration management 11

2.9 Impact of the project on individuals and organizations 11

3 Requirement Specification 11

3.1 Stakeholders for the system 11

3.2 Use case model 11

3.2.1.1 Use case Register 11

3.2.2 Usecase Description for each use case 11

3.3 Functional requirements 11

3.4 Non-functional requirements 11

4 Architecture 11

4.1 Architectural style(s) used 11

4.2 Architectural model 11

4.3 Technology, software, and hardware used 11

4.4 Rationale for your architectural style and model 11

5 Design 12

5.1 Database design 12

5.2 Static model – class diagrams 12

5.3 Dynamic model – sequence diagrams 12

5.4 Rationale for your detailed design model 12

5.5 Traceability from requirements to detailed design model 12

6 Test Plan 12

7.1 Requirements/specifications-based system level test cases 12

7.2 Traceability of test cases to use cases 12

7.3 Techniques used for test generation 12

7.4 Assessment of the goodness of your testsuite 12

7 Demo 12

1 Introduction

1.1 Purpose and Scope

1.1.1 Purpose

The main purpose preparing these document is to give a general insight into the analysis and requirements of the existing system or situation and for determing the operating characteristics of the system The proposed software will solve all the problem they are facing now This software is designed such way that it will generate the bill automatically every order in time So there not much worries This software also equipped with to the enter the details of each employee in the organization, it helps them to track each employee This being a Desktop based application is very easy to access Data and Records are managed in centralized database Data is secure and easy to retrieve, store, and analysis, so chances of

muscalculations and occurance of error are very less

1.1.2 Scope

This system will help to manage and run the coffee shop systematically In this management system, we will provide an app that can be used by cafe’s employee to take order So that the owner

of shop can evaluates the whole system This will ultimately lead to hire less waiters and create an opportunity to appoint more chefs and better shop to serve coffee faster Employee can take payment which will managed into the software

The Coffee Shop Management System is a comprehensive software solution designed to automate and manage the various

operations of a coffee shop Developed in C#, a modern, object-oriented programming language, this system provides a user-friendly interface and robust backend functionalities

Technical Overview:

The Coffee Shop Management System is developed in C#, leveraging the NET framework’s power and flexibility It uses a SQL Server database to store and manage data, ensuring high performance and security The system follows the Model-View-Controller (MVC) architecture, promoting organized and efficient code structure

1.3 Structure of the Document

In this document:

1.4 Terms, Acronyms, and Abbreviations

Database An organized collection of data stored and

accessed electronically from a computer system Class Diagram A class diagram is a structural diagram that

describes the structure of a system by showing the system's classes, their properties, operations, and relationships between objects

Usecase Diagram A use case diagram is a graphical depiction of a

user's possible interactions with a system Activity Diagram An activity diagram is a behavioral diagram to

describe the dynamic aspects of a system ERD Entity Relationship Diagram

2 Project Management Plan

2.1 Project Organization

2.2 Lifecycle Model Used

2.3 Risk Analysis

2.4 Hardware and Software Resource Requirements 2.5 Deliverables and Schedule

2.6 Monitoring, Reporting, and Controlling Mechanisms 2.7 Professional Standards

2.8 Evidence all the artifacts have been placed under configuration management

2.9 Impact of the project on individuals and organizations

3 Requirement Specification

3.1 Stakeholders for the system

3.2 Use case model

3.2.1.1 Use case Register

3.3 Functional requirements

3.4 Non-functional requirements

4 Architecture

4.1 Architectural style(s) used

4.2 Architectural model

4.3 Technology, software, and hardware used

4.4 Rationale for your architectural style and model

5 Design

5.1 Database design

5.2 Static model – class diagrams

5.3 Dynamic model – sequence diagrams

5.4 Rationale for your detailed design model

5.5 Traceability from requirements to detailed design model

6 Test Plan

7.1 Requirements/specifications-based system level test cases

7.2 Traceability of test cases to use cases

7.3 Techniques used for test generation

7.4 Assessment of the goodness of your testsuite

7 Demo

References