Sample PE SWR302 v1.0 Long
Sample PE SWR302 v1.0 Long
requirements in software requirements specification before they do the design and coding. They
describe the software requirements by using text, formulas, drawing models and table description. The
software tools department at FPT University want to develop a new software tool named EduNext
website to allow students to learn many courses in the constructivism way. Following the constructivism
way, the students will build up their knowledge more actively by searching content on the internet,
reading text books, interacting with other students in the same group or in the same class. The EduNext
website need to have many functions which allow importing data about student list from FAP system,
displaying the list of students, updating the list of students, adding questions, updating questions,
listing questions, creating student groups in the same class by teacher, answering the questions by
students, voting answers by students, voting answers by teacher, signing in EduNext by using
@fpt.edu.vn email accounts of students or teachers. Besides, EduNext can record data of the interaction
processes between students when students at FPT University post the answers of the questions, reply
or comment the answers of other students, vote the answers of other students or even chat with other
students. Use case approach is one of the most effective ways to describe the software requirements.
All the answers must be in English and reflect this exam paper. If your answers of the questions in this
exam paper have any keywords not related to this exam paper, the answers of the questions will get
ZERO.
Question 1: Complete all parts of the first page of the software requirements specification. (1 point)
Software Requirements
Specification
for
<Project>[Student must
replace this line by the name
of project in the exam paper]
(0.25 point)
Version 1.0 approved
<date created> [Student must replace this line by the date you take
the exam] (0.25 point)
Question 2:
Use case diagram is an effective way to visualize the interaction between actors and the
software system. One Use case diagram need one rectangle which represents one system or
one software application. One oval represents one use case. The name of the use case must
begin with the verb and follow by an object.
1. In this exam paper, the name of the rectangle is: ………( 0.1 point) EduNext
2. The actor may be human, other software systems or devices. In this exam paper, list the
name of >= 3 actors is: ……..(0.6 point) lecture, student, admin, staff
3. In this exam paper, list the name of >= 5 use cases are: …….(1 point) answer questions,
vote answer, create question, import data, update question
4. The actors are inside or outside of the rectangle? ……… (0.1 point) The actors are
outside of the rectangle
5. The ovals represent the use cases are inside or outside of the rectangle? ………(0.1 point)
The ovals represent the use cases are inside of the rectangle
The ovals represent the use cases are inside of the rectangle
6. The primary actor of the use case add new question is: teacher(0.2 point)
7. The secondary actor of the use case add new question is: staff (0.2 point)
8. Based on the fact you already used EduNext website. The use cases in this exam paper
may have relationship.
8.a List the name of two use cases that have extend relationship: view question and
answer question (0.3 point)
8.b The name of base use case (in 8.a) is: view question (0.2 point)
8.c The name of included use case (in 8.a) is: answer question (0.2 point)
8.d The dashed line with an arrow that points to which use case? View question (student
write the name of use case) (0.1 point)
9. Based on the fact you already used EduNext website, the use cases in this exam paper
may have relationship.
9.a List the name of two use cases that have include relationship: Create student
group, add student(0.3 point)
9.b The name of based use case (in 9.a) is: Create student(0.2 point)
9.c The name of extend use case (in 9s.a) is: Add student(0.2 point)
9.d The dashed line with an arrow that points to which use case? Add student
(student write the name of use case) (0.2 point)
Question 3: Writing detail one use case, the use case adds (+) new question in the following format. (4
points)
1. UC ID and Name: Create question (0.1 point) the UC – 1 and the use case name here.
2. Created By: lethanhbinh6122003@gmail.com The name of your email account.
3. Date Created: 27/04/2024. The date you take the exam.
4. Primary Actor: Teacher(0.2 point) the name of the actor that initiate use this use case.
5. Secondary Actors: Student (0.2 point) The name of actor that use the data of the primary actor.
6. Trigger: The teacher wants to create question for students to help them clarify learning problem
(0.3 point) the events that occur and then this use case will run.
7. Description: (0.1 point)
8. Preconditions: User must login with the role as a teacher. (0.3 point) The preconditions that
must be true or must be done before this use case can run. 8.1 …., 8.2 …., 8.3 ….. may be more
or less, depending on your ability to define. Don’t need to write all 8.1 …., 8.2 …., 8.3 ….. items.
8.1 User must login with the role as a teacher.
9. Postconditions: (0.3 point) Describe the things must be done after the actors interact with this
use case. 9.1 …., 9.2 …., 9.3 ….. may be more or less, depend on your ability to define. Not
always need to writing all 9.1 …., 9.2 …., 9.3 ….. items.
10. Normal Flow: 0.7 point) Describe the sequence of steps in normal case that must be performed
by the actors or the system responses. 10.1 …., 10.2 …., 10.3 …..10.4 … 10.5 … may be more or
less, depend on your ability to define. Not always need to writing all 10.1 …., 10.2 …., 10.3
…..10.4 … 10.5 … items.
13. Priority: Normal (0.1 point) Priority level will help better plan when implement.
14. Frequency of Use: Teachers frequently use this case (0.1 point) The more frequency of use, the
more important
15. Business Rules: Question must be less than 750 characters. (0.2 point) All things in software
related to data. The business rules should be specific for design and coding.
16. Other Information: (0.1 point) may describe the quality here for more info.
17. Assumptions: (0.1 point) The assumptions about the data related to this use case.