- If something is hard to understood, there will be a need for team to come to client''''s place to study the client''''s side system properly to avoid this problem Trang 20 18 2 Scope is re
Software project management Project: Beauty&Spa Store Management Application Class: E18CN02 Group Member: - Dương Hoàng Vũ - Hoàng Duy Đạt - Ngô Đăng Thái - Đỗ Xuân Hiếu Table of Contents I) Member’s distribution: II) SOW and project charter: III) WBS: IV) Scheduling: 10 V) Risk management: 14 VI) Communication management: 24 VII) Human resource management: 27 VIII) Quality management: 32 IX) Configuration management: 34 I) Member’s distribution: STT Name Đỗ Xn Hiếu Hồng Duy Đạt Ngơ Đăng Thái Work SOW and project charter document Configuration management document WBS Scheduling Human resource management documet Quality management document Power point creating Risk management document Dương Hoàng Vũ Communication management document Presenting II) SOW and project charter: 1) Statement of work (SOW): Statement of Work A Introduction Project name: Beauty&Spa Store Management Application Client: A Beauty&Spa store B Objectives This project will construct an application which will be installed in employee computer and running on web browser This application will have GUI that easy-to-use and provide functions that make store management easier, reduce the workload for manager, more convenient and more exactly C Scope Of Work Arcording to customer’s requirement above, propose an application with following feature: - This is a web application which will be internally used inside a store This application could be installed on many computers of the store employees However, the database is stocked on the store server This application supports the management for only one store Only used by types of employees • Store manager • Receptionist - Include: • Import product management • Check in • Payment • Statistic by revenue • Statistics by imported products - Not include: • Infrastructure management • Working days management • News showing • Internet connection The project is expected to start in 01/09/2021 and complete in 01/12/2021 2) Project charter: Project Charter Project Overall Project name: Beauty&Spa Store Management Application Project manager: Date of Project Authorization: 01/09/2021 Stakeholder: Sponsor: VNPT Client: A Beauty&Spa store User: Employees of the store Business adviser: Store owner Project Team: No Role PM BA Developer Tester Number Project Objective This project will construct an application which will be installed in employee computer and running on web browser This application will have GUI that easyto-use and provide functions that make store management easier, reduce the workload for manager, more convenient and more exactly It helps the manager to manage all information of bills, customer, employee, service and control product in warehouse It also provide functions which help receptionist to counter staff like receive customers and make a payment automatically Project Scope – Deliverables - Web application with following functions: • Import product management ▪ Search engine ▪ Add/edit/delete ▪ Print out invoice • Check in ▪ Search engine ▪ Add/edit/delete • Payment ▪ Search engine ▪ Payment ▪ Print out invoice • Statistic by revenue ▪ Statistic ▪ Order by date ▪ Order by money ▪ View detail revenue of each service • Statistic by imported products ▪ Statistic ▪ Order by date ▪ Order by amount ▪ View detail imported product of each product - Not include: • Infrastructure management • Working days management • News showing • Internet connection - Instruction - Install database system to store’s server - Install environment - Maintenance Document continues be Discover more from: Tổng hợp TH2021/22 Học viện Công nghệ Bưu… 528 documents Go to course BÀI TẬP Phrasal Verbs Idioms allal Tổng hợp 94% 14 150 TRẮC NGHIỆM VỀ Thàn NGỮ TIẾNG ANH- KEYS Tổng hợp 92% ho-so-tre-khuyet-tat 10 Tổng hợp [Hồ Thức Thuận] - Đáp án đề phát triển đề minh họa Câu 40 Tổng hợp 100% 100% 500 Idioms - Tổng hợp nhữ câu phần đồng nghĩa trái… Tổng hợp 100% BỘ ĐỀ LUYỆN KĨ NĂNG PT ĐO 26 Trích SÔNG ĐÀ văn lớp 12 Tổng hợp 100% Project Schedule Event Estimated time Projected Date Completed Comment Date Project Management days 01/09/2021 03/09/2021 Requirement gathering days 06/09/2021 13/09/2021 Analysis 13 days 14/09/2021 30/09/2021 Design 21 days 01/10/2021 29/10/2021 Implementation 12 days 01/11/2021 16/11/2021 Testing days 17/11/2021 24/11/2021 Deployement days 25/11/2021 30/11/2021 - The first version will be release and implement on store employee’s computer on 01/12/2021 - Assumptions This will be a web-based application System will run on existing networking and computer resources The front-end will be built using Angular 10 The back-end will be built using Spring framework Our in-house development team will the work All import data will be available in JSON format We will partner with a third-party company to create the security system Database Management System will be MySQL Server Project Approval & Signatures Name Title Project Manager Project Sponsor Client Signature Date III) WBS: WBS 0.0 Beauty&Spa Store Management Application 1.0 Project Management (3 days) 2.0 Requirement gathering 2.1 Unified Modeling Language (3 days) 3.0 Design and Analysis 3.1 Analysis 3.1.1 UML Structure Diagrams (3 days) 3.1.2 Making scenario (3 days) 3.1.3 Static analysis (3 days) 3.1.3.1 Entity class (3 days) 3.1.3.2 Module class diagram 3.1.3.2.1 Create class diagram for manager’s modules (2 days) 3.1.3.2.2 Create class diagram for receptionist’s modules (2 days) 3.1.3.2.3 Create class diagram for client’s modules(2 days ) 3.1.4 Dynamic analysic 3.1.4.1 Sequence diagram 3.1.4.1.1 Create Sequence diagram for manager’s modules (2 days) 3.1.4.1.2 Create Sequence diagram for receptionist’s modules (2 days) 3.1.4.1.3 Create Sequence diagram for client’s modules(2 days ) 3.1.4.2 State diagram 3.1.4.2.1 Create State diagram for manager’s modules (2 days) 3.1.4.2.2 Create State diagram for receptionist’s modules (2 days) 3.1.4.2.3 Create State diagram for client’s modules(2 days ) 3.1.5 Review (1 days) 3.2 Design 3.2.1 Class diagram 3.2.1.1 Design class diagram for System(2 days) 3.2.1.2 Design class diagram for manager’s modules (2 days) 3.2.1.3 Design class diagram for receptionist’s modules (2 days) 3.2.1.4 Design class diagram for client’s modules(2 days ) 3.2.2 Database diagram (3 days) 3.2.3 Static design 3.2.3.1 Interface design 3.2.3.1.1 Design interface for manager’s modules (2 days) 3.2.3.1.2 Design interface for receptionist’s modules (2 days) 3.2.3.1.3 Design interface for client’s modules(2 days ) 3.2.4 Dynamic design 3.2.4.1 Activity diagram (3 days) 3.2.4.2 Sequence diagram 3.2.4.2.1 Sequence diagram for manager’s modules (2 days) 3.2.4.2.2 Sequence diagram for receptionist’s modules (2 days) 3.2.4.2.3 Sequence diagram for client’s modules(2 days ) 8 Ngo Dang Thai Nguyen Thi Hanh Bui Kim Quyen Do Van Thanh Nguyen Tri Tai Male Quality assurance Female Programmer ngodangthai228@gmail.com Male Programmer quyenbuikim@gmail.com Male UI Designer Thanhvd@gmail.com Male Client(Beauty Store representative) Tritainguyen@gmail.com hanhthing@gmail.com 2 4 4 2 - : 1-2 years of experience - 2: 3-4 years of experience - 3: 5-6 years of experience - 4: 7-8 years of experience - 5: above years of experience 28 Network Database Design QA tester Java Javascript SQL HTML Duong Hoang Vu Hoang Duy Dat Do Xuan Hieu Ngo Dang Thai Nguyen Thi Hanh Bui Kim Quyen Do Van Thanh * Note : Analyst Full name III Skill Matrix IV Personal position in the project Team Analysis & Design team Leader Member Programming team Backend Frontend Deployment team Member 4.Project Manager Quantity/Position responsibility Total:2 Hoang Duy Dat Do Xuan Hieu Total :3 Bui Kim Quyen Nguyen Thi Hanh Do Van Thanh Total: Ngo Dang Thai Duong Hoang Vu V Organizational chart Project Manager Analysis & Design team Leader Member Programming team Backend VI Work assignment 29 Frontend Deployment team Member 1.0 2.0 Project Management Requirement gathering 2.1 Unified Modeling Language 3.0 Analysis 3.1 UML Structure Diagrams 3.2 Making scenario 3.3 Static analysis 3.4 Dynamic analysis 4.0 Design 4.1 Class Diagram 4.2 Database Diagram 4.3 Static Diagram 4.4 Dynamic Diagram 4.5 Package Diagram 5.0 Implementation 5.1 Frontend 5.1.1 Create HTML 5.2 Backend 5.2.1 Database implementation 5.2.2 Java development 5.2.2.1 manager’s modules 5.2.2.2 receptionist’s modules 5.2.2.3 client’s modules 6.0 Testing L L C C/R L A/R A/R Client Ngo Dang Thai Do Van Thanh Nguyen Thi Hanh Bui Kim Quyen Do Xuan Hieu Hoang Duy Dat Description Duong Hoang Vu WBS R L L L L L S C L L L L L L R A/R R L L A S C L C C C C R L 30 6.1 7.0 7.1 7.2 Junit Test Deployment Set up environment for customer Record user instructions R C R C L C C C L L L L * Note: - A: Approval - L: Leading team - S: Secondary (Responsible for replacing the leader if the leader is absent) - C: Contributor - R: Reviewer 31 VIII) Quality management: Measurement standards - Interface Availability: friendly interface, simple and easy to use, the functions of the application must meet the requirements of the customer - Safety and security: ensure data security, the application must be divided into many separate modules according to each function and easily integrated with each other -Stabilization: The application runs stably, without errors when the system and software have some changes, can be easily maintained and modified Testing method -Periodic functional testing: Functions will be tested periodically to ensure smooth operation and no significant errors during operation -Test by customer: Give the design to the customer to get the customer's opinion -Check the code: Experienced programmers check the code to see if it is secure or not Quality control parties Number Full Name Ngô Đăng Thái Position Quality assurance Nguyễn Trí Tài Dương Hồng Vũ Client (Beauty Store representative) Project Manager Mission - Create a strategy to improve quality - Make quality reports from time to time Evaluate and comment on project quality -Monitoring and supporting quality management Make a quality management plan Number Quality standards Interface Data Satisfaction condition -friendly interface, simple and easy to use -Provide enough information for users -Interface according to customer requirements -Fast database access speed -Data is not lost or changed Security Project documents analysis phase Design phase document Complete system functions -Good security against attacks -Evaluation of document quality -UML diagram -Class Diagram -Database Design -Ensure full functionality and stable operation Quality control Time 3/09/2021 Jobs Complete project planning documents 13/09/2021 Complete the requirement definition phase: - Documentation of business requirements - Document system requirements Complete analysis phase document: - UML diagrams - Scenarios - Relevant documents - Technology selection Complete the design phase with the materials: - System design document - Document design of subsystem/details 30/09/2021 29/10/2021 16/11/2021 -Complete system and database modules -Complete software product 24/11/2021 -Complete test documentation 30/11/2021 Install on client computer system 33 Targets -Possibility -Accuracy -Completed on time -Accuracy -Completed on time -User-friendly interface, correct function - Completed on time -Design of system components -Design the database suitable for the system -Document easy to read and understand - Completed on time -Code is exactly as in the design, easy to read and understand -Complete on time -Functions work correctly -No data loss when accessing Complete on time -Can be installed and working on the client machine -Complete on time Note IX) Configuration management: Acronym Definition ADD Architecture Design Document CC Infrastructure Configuration Controller CI Configuration Item CM Configuration Management CSCI Computer Software Configuration Items DDD Detail Design Document PM Project Manager PTL Project Technical Leader PIC Person in Charge QA Quality Assurance Officer SRS Software Requirement Specification Source Source Code URD User Requirement Document TP Test Plan TC Test Case WIP Work in Progress WP Work product Note 1) CI Identification & Naming convention CSCI Project Management Requirement & Design Build Configuration Items Naming conventions Proposal _Proposal_version number PP _Project Plan_version number Source Owner Security level CI Baseline Crite Customer Customer, PM Internal use Approved by OM (as pe RADIO) PM PM Internal use Approved by OM (as pe RADIO) CM Plan _CMPlan_version number PM PM Internal use Approved by PM Customer Requirement Document _URD_version number Customer, Development Team Customer, Development Team Confidential Agreed by PM and Cust Analysis Document _AD version number Development Team Development Team Confidential Approved by PM Design Document _DC_version number Development Team Development Team Confidential Approved by PM Screen _GUI_version number Development Team Development Team Confidential Approved by PTL Source _BSMA_YYYYMMDD Development Team Development Team Internal use Approved by QA Module Import Product Approved by PTL Module Check In Approved by PTL Module Payment Approved by PTL Module View Statistic By Revenue Approved by PTL Module View Statistic By Imported Product Approved by PTL Support Documents Instruction _Instruction_version number Development Team Test 35 Customer, Development Team Confidential Approved by PM System Test Plan _System Test Plan_version number Test Team Test Team Confidential Approved by PM Integration Test Plan _Integration Test Plan_version number Test Team Test Team Confidential Approved by PM Unit Test Plan _Unit Test Plan_version number Test Team Test Team Confidential Approved by PM System Test Case _System Test Case_Module name_version number Test Team Test Team Confidential Approved by Test Lead Integration Test Case _Integration Test Case_Module name_version number Test Team Test Team Confidential Approved by Test Lead Unit Test Case _Unit Test Case_Module name_version number Test Team Test Team Confidential Approved by PTL Test data _Test Data_version number Test Team Test Team Confidential Approved by Test Lead Test Team Test Team Confidential Approved by PTL Development Team Development Team Result of Test case execution Infrastructure _Test Report_version number Development Environment Server Window 10 Approved by PM Window Window 10 Approved by PM MySQL Server 8.0.25 DBMS Approved by PM Java Development language for backend Approved by PM HTML/CSS/JS Development language for frontend Approved by PM Spring Boot 2.5.6 Development framwork for backend Approved by PM Angular 10 Development frameword for frontend Approved by PM Intellij IDEA 2021.2 Development IDE for backend Approved by PM Development IDE for frontend Approved by PM Visual Studio Code 1.61.2 36 Visual Pardigm 16.3 Tool to draw diagram Test Environment Approved by PM Development Team Testing Team Window Window 10 Approved by PM MySQL Server 8.0.25 DBMS Approved by PM Java Development language for backend Approved by PM HTML/CSS/JS Development language for frontend Approved by PM Spring Boot 2.5.6 Development framwork for backend Approved by PM Angular 10 Development frameword for frontend Approved by PM Intellij IDEA 2021.2 Development IDE for backend Approved by PM Visual Studio Code 1.61.2 Development IDE for frontend Production Environment Approved by PM Development Team Customer Server Window Server 2022 Approved by customer, Win Window 10 Approved by customer, MySQL Server 8.0.25 DBMS Approved by PM Java Development language for backend Approved by PM HTML/CSS/JS Development language for frontend Approved by PM Spring Boot 2.5.6 Development framwork for backend Approved by PM Angular 10 Development frameword for frontend Approved by PM Intellij IDEA 2021.2 Development IDE for backend Approved by PM Development IDE for frontend Approved by PM Visual Studio Code 1.61.2 37 2) Directory structure & Access right Promotion Areas Area Develop Area Release Area Purpose Area for different users to store his/her owned items To store the items ready for release and all released versions of items Users get the most recent items for their usage from this area To archive all released versions of each CI Archive Area Archive area is a protected area for project baselines where all the CIs can not be changed by any member Directory structure Main Folder Working Sub Folder Purpose Access right Requirement Store all CIs that are delivered to customer, be possible to add date to folder name Modify: PM, CC Analysis Store documents of Analysis phase Modify: PM, CC, PIC Design Store documents of Design phase Implement Store source code Requirement Store all CIs that are delivered to customer, be possible to add date to folder name Modify: PM, QA Analysis Store Guidelines/Standards/Forms/Templates/Ch ecklist specified for the project Modify: PM, QA Design Documents of Design phase Modify: PM, QA Implement Store source code Testing Store document of approval or error in document or application Modify: Tester To released versions of CIs at baselines Modify: PM, CC Read: All Read: All Modify: PM, CC, PIC Read: All Modify: PM, CC, PTL Read: All Releasing Read: All Read: All Read: All Modify: PM, QA Read: All Archieve Read: All Read: All Version controller: Using git to manage the process of the project 3) CI Baseline Procedure For Document and source code 4) Change control Using Waterfall Model to handle change 39 Change Control Management Where is the change request logged? RM Sheet.xls Who logs the change request? Any team members Who reviews the change request? PM, BA, QA or CC (depend on whose works are affected by the change) Who approves the change request? PM by default OM/SM if: - Changes to project scope - Changes in targeted value of project QPPO - Changes in delivery plan of project deliverables - Changes to assignment for key roles (PM, PTL) QA if: - Changes to project quality Implementation team leader if: - Changes to implementation phase BA if: - Change to requirements of customer Change Control Activities Phase Description Creation of the event registration The event registration is created, and the event is described Analysis of the event registration Configuration item(s) affected by possible changes are determined, and the extensiveness of these changes is estimated After that, the reviewer determines to accept or reject the event Rejection or acceptance of the event registration If the event registration is accepted, a change request is created for each configuration item affected The change request initiates a new configuration item A new configuration item is identified and created, and the change is implemented In the course of accepting the new item and placing it in storage, feedback is given to the configuration control board Closing of the change request The change request can be closed when the change has been implemented and accepted Closing of the event registration The event registration can be closed when all corresponding change requests are closed 40 5) Backup strategy Storage Area to be Backed up Git repository Items to be Backed up GIt repository Backup To Google Drive, One Drive, Other Git repository 41 Backup Type Incremental Backup Frequency Twice a week PIC CC