MIDTERM EXAM COVER SHEET

Student Information (Please state names of all members) Grade/Marks

Name ID
Tran Thanh Dat MAMAIU17036
Tran Viet Hang MAMAIU18079
Le Nguyen Dang Khoa MAMAIU19008
Nguyen Minh Quan MAMAIU19036
Nguyen Tran Duy Tan MAMAIU18031
Module/Subject Information Office
Acknowledgement
Module/Subject Code MAFE390IU
Module/Subject Name Software Engineering
Lecturer Dao Tran Hoang Chau
10.05 am
Due Date
1st November, 2021 Date/Time

Note:

1) The attachment of this statement on any electronically submitted assignments will be

deemed to have the same authority as a signed statement.

2) The group leader submit this document on Blackboard on behalf of all members.
SECTION A - Question 1
(10pts) Describe the waterfall model and explain its main drawbacks.
Answer:
Start your answer from here

- Waterfall model is one kind of processes, which is used for developing large systems. This kind of
model has separate phases:

§ Requirement definitions: the period that collecting what customers want;

§ System and software design: after having the collections of customers’ requirements then we will
use it to prepare the system design and defining the overall system architecture;

§ Implementation and unit testing: after having the system design, for each input in the system design,
we will develop a small system and call it a unit. Then we test the functionalities of each unit;

§ Integration and system testing: After develop and test every single unit, we integrate it together and
test whole system;

§ Operation and maintenance: We release to the market after testing. If there are any issues, the better
versions should be released (update).

- The waterfall model, since it has the processes of completing the system phase by phase, it is difficult
to change after the process is underway. If there are difficulties to respond changing customer
requirements, the process has to be start over again from the first stage. Therefore, it is quite inflexible
and not desirable for complex projects whose requirements change frequently. Besides, because testing
phase occurs late in the process, it takes a lengthy time for developers and testers to complete the
document. Furthermore, client’s feedback cannot be included in the ongoing development phase since
the project is totally dependent on the project team with little client involvement.
SECTION A - Question 2
(20pts) Distinguish between functional and non-functional requirements with examples.
Answer:
Functional requirements are features that enable the system to perform its functions, describe
how the system should react and behave in particular situations. They also define what the
system should not do. We take Zalo as an example. When we log in Zalo successfully, we can
make a call, send online messages, post images, transfer money to our friends, etc. These
features are called functional requirements.

Non-functional requirements are properties that define system behaviour, features and general
characteristics that affect the user experience. For instance, International University has 5000
students and they have to use Edusoftweb to register courses in the upcoming semester. To
help students do it conveniently, Edusoftweb has to have a sufficiently high bandwidth that
allow 5000 students to access at the same time. Moreover, it needs to load relatively fast and
stable. Those requirements are called non-functional requirements.
SECTION B - Question 1
(30pts) Create a use case diagram.
Answer:
Paste your use case diagram here.
SECTION B - Question 2
(40pts) Select 2 use cases and describe them with both brief and step-by-step description.
SECTION B - Question 2
(continued)