-
Cùng tham gia nhóm của FuOverflow trên Facebook https://www.facebook.com/groups/nvh2fuoverflow
1. I agree with using Extreme Programming (XP) for this project, because:
- Main practices of XP align well:
+ Pair programming: Our team has 3–5 experienced developers, making this very effective.
+ Test-driven development (TDD): Fits perfectly since we need frequent testing from small to large units.
+ Continuous integration: Helps us handle changes easily, which is important since requirements might evolve.
+ Small releases: XP supports fast iterations, which matches our 3–6 month release target.
+ Collective code ownership: Boosts team productivity, anyone can fix/improve code without waiting.
+ Coding standards: Keeps our codebase clean and maintainable.
+ Sustainable pace (40-hour week): Prevents burnout and ensures consistent delivery quality.
+ On-site customer: We have direct support from department staff who can answer questions immediately.
- Project characteristics:
+ It's a brand-new system → XP is ideal for new development projects.
+ Requirements are likely to change → XP is built for flexibility.
+ The team is experienced → XP expects mature developers.
+ We need fast results → XP encourages frequent, working releases.
For the above reasons, Extreme Programming (XP) is a very good fit for this project.
2. - Unit Testing: Focuses on verifying the program’s internal structure (individual modules).
+ Unit Tests → based on code.
- Integration Testing and System Testing: Focus on verifying the system’s functional requirements.
+ Integration Test: Test the integration between modules.
+ System Test: Test the entire system according to the function.
3. Functional Requirements:
- Customers can select types of steel and place an order.
- Customers can track their order status.
- Customers can track payment status for their orders.
- Customers can view their order history.
- Sales staff can accept or reject customer orders.
Security Requirements:
- Sensitive information like customer details and payments must be encrypted.
- User activities must be logged for tracking and auditing purposes.
Performance Requirement:
- The system should efficiently manage large datasets, optimizing memory and CPU usage.
Usability Requirements:
- Users should be able to use the system by simply reading a manual, without needing a training course.
- Training time for users should be close to zero.
- Main practices of XP align well:
+ Pair programming: Our team has 3–5 experienced developers, making this very effective.
+ Test-driven development (TDD): Fits perfectly since we need frequent testing from small to large units.
+ Continuous integration: Helps us handle changes easily, which is important since requirements might evolve.
+ Small releases: XP supports fast iterations, which matches our 3–6 month release target.
+ Collective code ownership: Boosts team productivity, anyone can fix/improve code without waiting.
+ Coding standards: Keeps our codebase clean and maintainable.
+ Sustainable pace (40-hour week): Prevents burnout and ensures consistent delivery quality.
+ On-site customer: We have direct support from department staff who can answer questions immediately.
- Project characteristics:
+ It's a brand-new system → XP is ideal for new development projects.
+ Requirements are likely to change → XP is built for flexibility.
+ The team is experienced → XP expects mature developers.
+ We need fast results → XP encourages frequent, working releases.
For the above reasons, Extreme Programming (XP) is a very good fit for this project.
2. - Unit Testing: Focuses on verifying the program’s internal structure (individual modules).
+ Unit Tests → based on code.
- Integration Testing and System Testing: Focus on verifying the system’s functional requirements.
+ Integration Test: Test the integration between modules.
+ System Test: Test the entire system according to the function.
3. Functional Requirements:
- Customers can select types of steel and place an order.
- Customers can track their order status.
- Customers can track payment status for their orders.
- Customers can view their order history.
- Sales staff can accept or reject customer orders.
Security Requirements:
- Sensitive information like customer details and payments must be encrypted.
- User activities must be logged for tracking and auditing purposes.
Performance Requirement:
- The system should efficiently manage large datasets, optimizing memory and CPU usage.
Usability Requirements:
- Users should be able to use the system by simply reading a manual, without needing a training course.
- Training time for users should be close to zero.
4. As a customer, I want to select types of steel and place an order, so that I can buy products online.
As a customer, I want to track the status of my orders, so that I know where my purchases are.
As a customer, I want to track payment status, so that I can confirm my payments are complete.
As a sales staff member, I want to accept or reject customer orders, so that I can manage incoming requests.
As a customer, I want to view my past orders, so that I can review what I have purchased before.
5. a, What is Velocity?
Velocity is the amount of work (measured in Story Points) that a team can complete in one iteration.
b) What is a Story Point?
A Story Point measures the complexity or effort required for a user story.
c) How many iterations are needed to complete the project?
Total Story Points = 120
Velocity = 20 Story Points per iteration
So that, Number of iterations = 120 ÷ 20 = 6 iterations.
6. A. Activities and User Tasks
1. Place Order
1.1 Select steel type
1.2 Enter order quantity
1.3 Submit order
2. Track Order
2.1 View order status
2.2 View payment status
Accept/Reject Order
3.1 View order details
3.2 Accept order
3.3 Reject order
B. Releases
Release 1:
1.1.1 Select steel type from catalog
1.2.1 Input quantity for each steel type
1.3.1 Submit order to system
2.1.1 View status: pending/approved/rejected
2.2.1 View payment: unpaid/paid
3.1.1 View order details (customer info, order info)
Release 2:
3.2.1 Accept order and update order status
3.3.1 Reject order and notify customer
As a customer, I want to track the status of my orders, so that I know where my purchases are.
As a customer, I want to track payment status, so that I can confirm my payments are complete.
As a sales staff member, I want to accept or reject customer orders, so that I can manage incoming requests.
As a customer, I want to view my past orders, so that I can review what I have purchased before.
5. a, What is Velocity?
Velocity is the amount of work (measured in Story Points) that a team can complete in one iteration.
b) What is a Story Point?
A Story Point measures the complexity or effort required for a user story.
c) How many iterations are needed to complete the project?
Total Story Points = 120
Velocity = 20 Story Points per iteration
So that, Number of iterations = 120 ÷ 20 = 6 iterations.
6. A. Activities and User Tasks
1. Place Order
1.1 Select steel type
1.2 Enter order quantity
1.3 Submit order
2. Track Order
2.1 View order status
2.2 View payment status
Accept/Reject Order
3.1 View order details
3.2 Accept order
3.3 Reject order
B. Releases
Release 1:
1.1.1 Select steel type from catalog
1.2.1 Input quantity for each steel type
1.3.1 Submit order to system
2.1.1 View status: pending/approved/rejected
2.2.1 View payment: unpaid/paid
3.1.1 View order details (customer info, order info)
Release 2:
3.2.1 Accept order and update order status
3.3.1 Reject order and notify customer
Chỉnh sửa lần cuối:
không dùng được form User Involvement, Customer Involvement, Requirements characteristics, Team’s skill and experience, Project deliverables, Top management commitment: à a
form nào
)))
thaihbvn218
FPT Student
chữa PE theo form mới. Cái form mà SP25 PE anh dùng mỗi câu đúng được 0.3 điểmform nào
t đã đc nhìn cái form mới như nào đâu
))) bài SP25 kia khách điểm có thấp đâu nhỉMespeace811
FPT Student
cho em hỏi c1 em trl không đồng ý và chọn scrum như này thì được bnhieu điểm ạ:
a) requirements:
_ Flexibility: requirements are not totally defined at the beginning, they can be changed, added, or removed at any time during the development process
_ Good Management: requirements are broken down into smaller user stories, making them easier to implement within short time frames (Sprint) in order to
improve project management
_ Customer satisfaction: Because of the customer's attendacne during the project, requirements can be continuously adjusted in order to fit as
well as possible with the customer's expectations for the product
b) Development teams:
_ Structure: small team, normally consisting of 5 to 9 members
_ Cross Functional: strong coding skills and extensive experience in project management
_ Communication: team members who join in the project communicate and collaborate frequently to drive the project progress
_ equality: all members share responsibility for the final product
a) requirements:
_ Flexibility: requirements are not totally defined at the beginning, they can be changed, added, or removed at any time during the development process
_ Good Management: requirements are broken down into smaller user stories, making them easier to implement within short time frames (Sprint) in order to
improve project management
_ Customer satisfaction: Because of the customer's attendacne during the project, requirements can be continuously adjusted in order to fit as
well as possible with the customer's expectations for the product
b) Development teams:
_ Structure: small team, normally consisting of 5 to 9 members
_ Cross Functional: strong coding skills and extensive experience in project management
_ Communication: team members who join in the project communicate and collaborate frequently to drive the project progress
_ equality: all members share responsibility for the final product
tôi cũng ko đồng ý và chọn scrum
)) t cướp hồi môbạn được bao nhiêu điểm thế ạ
A. Activities and User Tasks
1. Place Order
1.1 Select steel type
1.2 Enter order quantity
1.3 Submit order
2. Track Order
2.1 View order status
2.2 View payment status
Accept/Reject Order
3.1 View order details
3.2 Accept order
3.3 Reject order
sao đoạn này lại làm cả 3 cái trong đề hỏi 2 cái v ạ
1. Place Order
1.1 Select steel type
1.2 Enter order quantity
1.3 Submit order
2. Track Order
2.1 View order status
2.2 View payment status
Accept/Reject Order
3.1 View order details
3.2 Accept order
3.3 Reject order
sao đoạn này lại làm cả 3 cái trong đề hỏi 2 cái v ạ
Đề này câu 1 k xài XP mà xài Lean được không ạ
Eliminate watse: Focus on feature customer need
Build quality in: Focus on the quality of each module, not when we finished all and testing
Defer commitment: Making the decision as low as we can, to collect all data and request to change the process if needed, lead to better outcome
Delivery fast: Fast delivery important feature to the customer when this project have short time (3 months), could change based on feedback
Create knowledge: Share the knowledge of experience developers from the IT department with developers in development team
Optimize the whole: focus on the entire stream rather than individual components to ensure the improvement benefit of all process
Amplify learning: continuous improving and learning from outcome and feedback
Eliminate watse: Focus on feature customer need
Build quality in: Focus on the quality of each module, not when we finished all and testing
Defer commitment: Making the decision as low as we can, to collect all data and request to change the process if needed, lead to better outcome
Delivery fast: Fast delivery important feature to the customer when this project have short time (3 months), could change based on feedback
Create knowledge: Share the knowledge of experience developers from the IT department with developers in development team
Optimize the whole: focus on the entire stream rather than individual components to ensure the improvement benefit of all process
Amplify learning: continuous improving and learning from outcome and feedback
Similar threads
Đề Thi FE
SWE201c - SP 2025 - FE
