1. Trang chủ
  2. » Luận Văn - Báo Cáo

final project software engineering

12 0 0
Tài liệu đã được kiểm tra trùng lặp

Đang tải... (xem toàn văn)

Tài liệu hạn chế xem trước, để xem đầy đủ mời bạn chọn Tải xuống

THÔNG TIN TÀI LIỆU

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

Trang 1

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 – 522H0014NGUYEN NGOC THIEN – 522H0047TRAN THI YEN PHUONG – 522H0084PHAN THIET TRUNG – 522H0071

Course : 26

Trang 2

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 – 522H0014NGUYEN NGOC THIEN – 522H0047PHAN THIET TRUNG – 522H0071TRAN THI YEN PHUONG – 522H0084

Course : 26

Trang 3

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.

Trang 4

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 2024th

The author(Sign and write full name)

Huynh Thinh Hung

Trang 5

INSTRUCTOR VERIFICATION AND EVALUATION SECTION

Confirmation from the instructor

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

The teacher's evaluation part marks the test

Ho Chi Minh city, , 12 May 2024th

Trang 6

SUMMARY

Trang 7

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

3.1.Stakeholders for the system 11

3.2.Use case model 11

Trang 8

3.2.1.1 Use case Register 11

3.2.2 Usecase Description for each use case 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

Trang 9

This being a Desktop based application is very easy to access Data and Records are managed in centralized database Data is secureand 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

Trang 10

operations of a coffee shop Developed in C#, a modern, object-oriented programming language, this system provides a user-friendly interface androbust 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 andsecurity 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 systemClass 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

Trang 11

2 Project Management Plan

2.1 Project Organization2.2 Lifecycle Model Used2.3 Risk Analysis

2.4 Hardware and Software Resource Requirements2.5 Deliverables and Schedule

2.6 Monitoring, Reporting, and Controlling Mechanisms2.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 system3.2 Use case model

3.2.1.1 Use case Register

3.3 Functional requirements3.4 Non-functional requirements

Trang 12

5 Design

5.1 Database design

5.2 Static model – class diagrams5.3 Dynamic model – sequence diagrams5.4 Rationale for your detailed design model

5.5 Traceability from requirements to detailed design model

Ngày đăng: 08/05/2024, 16:24

Xem thêm:

w