Q1:
I don’t agree with <> methodology. I recommend using Agile/Scrum(hoặc thuộc cùng type với Agile).
This is my explain for my choice:
a) Requirements Characteristics:
-Reliability:
+ The project requirements are well-defined and possible
+ It can run after project finished
=>The project is expected to be highly reliable
-Type and number of requirement:
+ This project have two type of requirements: N functional requirement and N Non-Functional
Requirement How often the requirements can change:
+ The requirements are well-defined , but not enough
=> So, this project should be use Agile methodology
-Determination of requirements at an early stage:
// Nếu như đề nói : Hệ thống chưa có bất kì hệ thống giống và tồn tại trước đó
<Tên hệ thống đang phát triển> is a new development system, so, this is the first time the
development team do this project. So, dev team need employees to join the project to support
project completion with high quality
// Nếu như đề đéo nói:
<Tên hệ thống đang phát triển>is a good system, with many functions like <Liệt kê 1 số chức năng
vui vẻ…>, this system help …
b)Development team:
<4 month: small ( 4 developers)
6 - 8 month: medium ( 6 developers)
8+ month: large ( 8 developer)
+ Team size:
The development team participating in the project will include N developers
This is <<Mức độ>> project
(5 -> 8 : Medium
8+ -> …: Large)
+ Level of understanding of user requirements by the developers:
The development team participating in the project will include extensive experience and skills
developer
<<Lụm ở đề đưa vào>> (ai supports)
=> My team easily understands the req in this project.
c) User involvement:
- Our team is supported by the IT department in FU. Also other departments commit to sending
employees to join the project to support our team.
=> The organization can provide additional resources and information when needed. The user
involvement is high.
- In conclusion, I agree to use <<Agile/Scrum( hoặc thuộc cùng type với Agile)>> methodology for this
project. This is a <<Mức độ>> project, so development team need to design the project into smaller
part to be more easily. Also, this project can be change easily due to the new system and change
user requirement. (Có ai hổ trợ thì mới đứa đoạn này vào ) Our team is supported by <<Thằng nào
hổ trợ>>. Also other departments commit to sending <<…>> to join the project to support out team.
Q2:
1. Type and level/stage of testing to meet customer's requirements:
Acceptance Testing – to verify customer needs
System Testing – to test the whole system
Integration Testing – to check module interactions
Unit Testing – to test individual components
2. Who performs testing at each level/stage?
Unit Testing: Developers
Integration Testing: Developers/Testers
System Testing: QA/Testers
Acceptance Testing: End-users/Clients
Q3:
Liệt kê các funtional requirement, non-functional requirement ( performence, usability, security,.. là
biến thể của non).
Dấu hiệu nhận biết:
-Performence: có chữ perform hoặc đồng nghĩa
- usalbility:liên quan đến giao diện, đa ngôn ngữ, mang đến trải nghiệm cho người dùng,...
-security: có tính bảo mật như nào….
Q4:
As a <Role>, i want to <Feature> , so I can <Explain>
(chỉ chọn functional requirement)
Q5: DẠNG METHOD
Predictive Models
-Waterfall Model
Step-by-step phases: requirements → design → coding → testing → maintenance..
Simple to control but not flexible.
-V-Model (Validation & Verification)
An improved Waterfall model with testing planned at each stage.
Focuses on testing early.
-Incremental Model
The system is made in small pieces (increments).
Each piece brings new features.
-Spiral Model
Mixes planning and early versions with risk checking.
Best for big and complex systems.
-Prototyping Model
Create fast examples (prototypes) to understand what is needed.
The final system is made after getting feedback.
Adaptive Models
-Agile Model
Short cycles with constant feedback.
Quick results and high customer involvement.
-Scrum
An Agile method with set roles (Scrum Master, Product Owner).
Work is done in “sprints” (2–4 weeks).
-Extreme Programming (XP)
Focuses on coding methods: coding in pairs, testing all the time.
Improves software quality and flexibility.
-Crystal Methodology
Simple and focused on people.
Changes based on team size and how serious the project is.
-Feature-Driven Development (FDD)
Makes software by focusing on useful features.
Planning and design are done before coding.
Q6:
*DẠNG: theo đề FALL2024 (KHÁC DẠNG ĐỂ SU24 TRỞ VỀ TRƯỚC) là có giống với SU24
ko
Template đã cho sẵn trong đề
A. Activities and User task:
1. Activities N : (đề yêu cầu)
1.1 : User task: (tìm trên đề các chức năng liên quan, tìm các từ đồng nghĩa , tầm 3
cái thôi)
B. Release
1.Release N:
1.1: Activities N:
1.1.1: UserStory: As a <Role> , i want to <đưa chức năng từ usertask xuống>
*DẠNG: theo đề RE SP24 (làm theo CRUD) (DUME ĐỌC TỚI ĐÂY THÌ NHỚ ĐỌC LƯU Ý)
DẤU HIỆU NHẬN BIẾT: có UPDATE, DELETE, EDIT,..
LƯU Ý: DẠNG NÀY CHỈ PHÒNG HỜ, VÌ NÓ TỪ SP24, CÒN LẠI CỨ FOLLOW THEO DẠNG
ĐẦU TIÊN, VẪN PHẢI BẮT BUỘC FOLLOW THEO TEMPLATE DẠNG 1