Question 1:

a. Requirements characteristics
 Reliability:
+ It was stated clearly above that there is a problem that needs to be overcome,
and an application is required to solve this problem.
+ The project requirements are well-defined and possible.
+ It can immediately run while the project finished.

=> The project is expected to be highly reliable.

 Types and number of requirement:

+ The software requirements include both functional requirements and non-
functional requirements. All of them are defined clearly and are not confusing.
+ There are some requirements that was listed above.

=> Types and number of requirements defined this project is not too complex for our
team.

 Frequency of requirement may change:

+ The requirements that was mentioned above, is just some features of this
application.
+ In the process of project, some of features can be modified and changed to meet
with the requirements of customer.

=> The requirements may change regularly.

 Determination of requirements at an early stage

+ Some of requirements was defined above but it isn’t enough to build a
completed system.
+ The organization can be added or removed some of features in the process of
project.

=> It is well-defined but not enough.

b. Development team
 Team size:
+ The situation above mentioned our team have 9 people.
+ My team has 6 developers, 2 QA and a project owner who is me.

=> It is an average team size and enough to build a project that was not too complex.

 Level of understanding of user requirements by the developers:

+ All of requirements defined clearly above and with the leader from me our team
member can understand easily.
+ The organization can provide additional resources and information when
needed.

=> Our team can easy to understand and build an application absolutely satisfied by
user and owner .

c. User involvement
  The situation mentioned “The organization had contracted with a local company to
provide additional resources when needed.”
 We have a contact with the organization to exchange and give the feedback about the
project so that the product can meet the bests requirements early.

=> The user involvement is highly.

In short, I feel that Agile/Scrum methodology is the most suitable model for this project.
Because the information is exchanged frequently and many new features will be updated
every week, every month,… Due to the project relevants to fashion business so many big sale
day will be performed and many new items need to be updated frequently. And this
methodology can deliver new features to users more often and faster. Ther requirements
system is flexible so if using Agile we can change them easily, better with a start up company
so Agile specifically SCRUM is a good choice.

Question 2:
I suggest that the team use black-box testing because users would be involved in
evaluating the project's flaws and providing feedback, particularly regarding the system's
usability. We have both functional requirements and non-functional requirements is clear, it
helps testing process is easier and soon to prepare if not suitable for the needs of users.
Furthermore, this type of testing does not require specialized expertise from the analyst as
detailed technical knowledge of the system is not necessary.

Question 3:
 Four test case I would suggest the team do:
+ Functional testing: test functional if it appropriate or not.
+ Non-functional testing: Is mobile application and website fast, color acceptable,
easy to browse or not.
+ Unit testing: test class, method in code, is it running right or wrong.
+ System testing.

Question 4:
 The four functional requirements of system are:
+ Users can provide feedback on products and share their experiences with
others.
+ My online fashion platforms often provide styling suggestions and outfit
inspiration through curated looks or recommendations based on individual
items.
+ Users can share their purchases on social media platforms.
+ The platforms can send push notifications or email alerts to users about order
confirmations, shipment updates.
 The two non-functional requirements of system are:
+ Users data can record to receive discount to the next purchase.
 + Users must use device that have a camera to use the Virtual fitting rooms.

Question 5:
 The two user stories for this system are:
+ As a user, I want to view the license terms before purchasing so that I know
what I’m getting.
+ As a user, I want to payment by using credit card so that I can easily to pay
my purchase.

Question 6:

Question 7:
The three assumptions regarding the Virtual Fitting Room feature are:

 User’s space feature is low impact if wrong, high probability of it being wrong.
+ It is needed the space that have enough big and light.
+ It help users can see them more reality so decided but this item truely.
 Device feature is high impact if wrong, low probability of it being wrong.
+ Beside the space, user must have a good camera device to using.
 AR or VR technologies feature is high impact if wrong, high probability of it being
wrong.
+ If the technologies are not enough good, user will have so bad experience to
try on clothes.