Scribd
Upload
8 views5 pages

Swe Ans F

Fpt

Uploaded by

quansuper1508
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
8 views5 pages

Swe Ans F

Fpt

Uploaded by

quansuper1508
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 5

Question 1.

Based on the project description, I would suggest using the Agile software
development methodology for this project for the following reasons:

Project Characteristics:

Users: Student Service Staffs, Student Service Manager, Students, Landlords


Customer: FU
Team: Experienced 4-5 developers from FU’s IT department, support from
other departments
Requirements: Clear high-level requirements but likely to change during
development
Time: Expect first version in 3 months, complete in 7 months
Manager's expectations: Quick delivery of first version, accommodate
requirement changes

The Agile methodology is suitable because:

- Accommodates changing requirements through iterative development


- Allows early delivery of business value through incremental releases
- Encourages close collaboration between self-organizing cross-functional
teams
- Focuses on frequent inspection and adaptation in short iterations
- Well-suited for projects with experienced teams and uncertain requirements
- The iterative approach will allow us to deliver the first version quickly in 3
months to meet the tight timeline. The incremental builds will ensure
continuous delivery of business value throughout the project.The flexibility of
Agile will help accommodate the expected requirement changes. The
experienced team can work effectively in an Agile setting.

Question 2.
Level/Stage:

Unit Testing - Done by developers to test individual units/components


Integration Testing - Done by developers to test integration between
components
System Testing - Done by testers to test the complete system against
requirements
User Acceptance Testing (UAT) - Done by client users to validate if the
system meets needs

Types of Testing:

Functional Testing - Test system against functional requirements


Non-functional Testing
Performance Testing - Test system responsiveness and scalability
Security Testing - Test authorization, authentication, data security
Usability Testing - Test ease of use of user interface
Regression Testing - Test existing functionality after changes

The developers will do unit and integration testing during development. A


separate team of testers will carry out system testing. The client users like
Student Service Staffs, Student Service Manager, Students, Landlords will be
involved in UAT to validate the system. Security, performance and usability
testing will be done by both developers and testers. Regression testing will be
done across all levels to ensure no regression bugs.

Question 3.

Based on the project description, here are some functional and non-functional
requirements:

Functional Requirements:

- Allows Student Service Staff to put accommodation informations into system.


View, reply and respon to student requests.
- Student can find the available motels near FU, then register with motel
owners and submit a request for assistance to the Student Service Dept. View
or cancal the request.
- Allows motel owners to view, post and update motel information.
- Allows manager to minitor, track the support actities to ensure that every
student’s request must be solve and the manager can have a summary report
of support of support activities.
Non-Functional Requirements:

Security - Login with FU email accounts, ensure data security


Usability - Easy to use interface, minimal training required
Performance - Ensure high performance for all users (all student can find the
best motel for self)
Maintainability - System should be easy to find, post, maintain and update
The key functional requirements are around the core motel management
capabilities like scheduling, registration, cost tracking etc. for different user
roles.

The non-functional requirements are around security, usability, performance


and ability to change. These are critical quality attributes that need to be built
into the system.

Question 4.

Question 5.
- Four test case:
Test case 1:
+ Description : test performance of the system
+ Input : 1000 picture, status motel expensive in this time.
+ Expected: All student can place orders
+ Output: All information motel student can place orders
+ Exception: System inform error picture “Load Picture Fail"
Test case 2:
+ Description : Test layout for each web
+ Input : Open the screen of system in web
+ Expected: Display successfully different layout for websibe
+ Output: Display successfully different layout for websibe
+ Exception: The UI does not meet the requirements
Test case 3 :
+ Description : Test Upload Image Functional
+ Input: Upload image have the size larger than 1000 mb
+ Expected: The system informs error message “Size image exceeds size allow"
+ Output: The system informs error message “Size image exceeds size allow"
+ Exception: The system informs error message “Size image exceeds size
allow"
Test case 4:
+ Description : Test conecting Account
+ Input: Gmail and Passwork
+ Expected: The system informs error “Connecting"
+ Output: The system informs error “Connecting"
+ Exception: The system informs error message “Conneting"
--------------------------------------
+ Input : number phone, picture motel, name…. about motel when it still
loading and broken internet.
� Output : Information upload succesfull.

+ Input : Testing in non-cookie


� Output : Program still work correctly.

Question 6.
1. As a Student, I want to find motel FU so that I can live near my
university.
2. As an Landlords, I want to post more picture motel to web so that I can
help students easy to find motel for self.
Question 7.

You might also like