0% found this document useful (0 votes)
12 views13 pages

EduNext Website Software Requirements

Uploaded by

hungnse173654
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
0% found this document useful (0 votes)
12 views13 pages

EduNext Website Software Requirements

Uploaded by

hungnse173654
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

lOMoARcPSD|22298344

Sample PE SWR302 v1.0 Long đáp án


90%

Software Requirement (Trường Đại học FPT)

Scan to open on Studocu

Downloaded by Nguyen Hung (K17 HCM)


Studocu is not sponsored or endorsed by any college or university

Downloaded by Nguyen Hung (K17 HCM)


In fact, when developing a new software, the software development team must describe the software
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 @[Link] 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.

note:

+ Tool named: EduNext website là project name (Màu xanh lá)


+ Actor phía trước của nó là các từ như from và by (Màu đỏ)
+ Use case (màu xanh dương) là danh từ + động từ là có đồồng tự thêm ing

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

EduNext website
Version 1.0 approved

Downloaded by Nguyen Hung (K17 HCM)


Prepared by Nguyen Van A, CE123456

FPT University Campus Can Tho

March, 27th , 2023

Question 2: Nội dung phầần này từ cầu 8a trở đi bắắt buột là hình dung (hoặc tự veẽ mầẽu) cái use case
nên rầắt khó

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: EduNext website( 0.1 point)
a. rectangle là cái hình vuồng bao gồồm các ovals
b. actor là người trong cái hình
c. ovals là cái hình tròn tròn

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)
+ FAP system
+ Teacher
+ Students
+ Administrator
3. In this exam paper, list the name of >= 5 use cases are: (1 point)
+ import data

Downloaded by Nguyen Hung (K17 HCM)


+ display the list of students
+ update the list of students
+ add questions
+ update questions
+ list questions
+ create student
+ vote answers
+ sign in EduNext
+ record data
note: bỏ ing
4. The actors are inside or outside of the rectangle? outside (0.1 point)
5. The ovals represent the use cases are inside or outside of the rectangle? inside (0.1
point)
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: Administrator or Student or
N/A. (0.2 point) N/A
note: cầu này hên xui
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: …….(0.3
point) note:
+ extend: không bắắt buộc phải làm
vd: mua hàng xong có thể feedback hoặc không feedback
+ include: bắắt buộc
vd: khi thanh toán thì bắắt buộc phải nhập thông tin cá nhân và chọn hình thức thanh
toán
- Answer question extends Create student group
- Vote answer by student extends Answer question

8.b The name of base use case (in 8.a) is: …..(0.2 point)
8.c The name of included use case (in 8.a) is: ……(0.2 point)
8.d The dashed line with an arrow that points to which use case? …..(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: …….(0.3 point)
9.b The name of based use case (in 9.a) is: …..(0.2 point)
9.c The name of extend use case (in 9s.a) is: ……(0.2 point)
9.d The dashed line with an arrow that points to which use case? …… (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: (0.1 point) the UC – 1 and the use case name here.

Downloaded by Nguyen Hung (K17 HCM)


2. Created By: (0.1 point) The name of your email account.
3. Date Created: (0.1 point) The date you take the exam.
4. Primary Actor: (0.2 point) the name of the actor that initiate use this use case.
5. Secondary Actors: (0.2 point) The name of actor that use the data of the primary actor.
6. Trigger: (0.3 point) the events that occur and then this use case will run.
7. Description: (0.1 point)

8. Preconditions: (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 …..
8.2 …..
8.3 …..
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.

9.1 ….

9.2 ….

9.3 ….

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. 10. 1 …..

10. 2 …..

10. 3 …..

10. 4 …..

10. 5 …..

11. Alternative Flows: (0.7 point) Describe the sequence of steps in different case that can be
performed by the actors or the system responses. 11.1 …., 11.2 …., 11.3 …..11.4 … 11.5 … may
be more or less, depending on your ability to define. Not always need to writing all 11.1 …., 11.2
…., 11.3 …..11.4 … 11.5 … items.
11. 1 …..
11. 2 …..
11. 3 …..
11. 4 …..
11. 5 …..
12. Exceptions: …..(0.3 point) Describe the sequence of steps that can be handled or implemented
when there are any exceptions.

Downloaded by Nguyen Hung (K17 HCM)


12. 1 …..

12. 2 …..

12. 3 …..

13. Priority: (0.1 point) Priority level will help better plan when implement.
14. Frequency of Use: (0.1 point) The more frequency of use, the more important
15. Business Rules: (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.

note: nên veẽ cái bảng trước sau đó copy nội dung trong bảng điêần vào phía trên

UC-01: adds (+) new question (tên của use case)

ID and Name: UC-1, Add new question

CreatedBy (Tên người Võ Duy Thanh Date Created: 27/03/2023


tạo):

Primary Actor(người Teacher Secondary Actors N/A


sử dụng chức năng (người thứ 2 sử dụng
này, có thể ghi 2 chức năng này):
actor):

Priority(mức độ ưu Medium Frequency of Usually


tiên): Use(Tâồn suâất sử dụng):

+ High
+ Medium
+ Low
+ One-time use
+ Usually

Trigger (khi nào thì The teacher wants to add a new question to the system
câồn sử dụng):

Downloaded by Nguyen Hung (K17 HCM)


Description(Miêu tả) : This use case allows Teacher to add a new question to the system

Preconditions(điêồu The teacher has logged in to the system.


kiện băất buộc khi sử
dụng ): The teacher has the necessary privileges to add questions to the
question bank.

The question bank already exists in the system.

Post-conditions(Hậu Success:
điêồu kiện):
● The new question is added to the question bank.
● The question bank is updated with the new question.
● The teacher can view the newly added question in
the question bank.

Fail: The system shows error message corresponding to error


code

Normal Flow(chức
năng cơ bản):
Step Actor Action

1 The teacher selects the "Add Question" option from


the question bank menu.

2 The system displays the "Add New Question" form.

Downloaded by Nguyen Hung (K17 HCM)


3 The teacher enters the question statement, answer
options, and correct answer.

4 The teacher submits the form.

5 The system validates the form and adds the new


question to the question bank.

Alternative ● If the teacher enters an invalid or incomplete form, the


Flow(chức năng system displays an error message and prompts the teacher
nâng cao): to correct the form.
● If the teacher cancels the form submission, the system
redirects to the question bank menu.
● If the teacher decides not to add a new question, the
system redirects to the question bank menu.

Exceptions: If the system encounters an error while adding a new question, it


displays an error message and prompts the teacher to try again.

If the teacher does not have the necessary privileges to add


questions to the question bank, the system displays an error
message.

The question statement should not exceed 500 characters.


Business Rules:
Each question must have at least two answer options.
The correct answer should be marked.

Downloaded by Nguyen Hung (K17 HCM)


The system has the necessary database to store the question
Assumptions(giả định):
bank.
giả định trong use case có
thể là các điêồu kiện The teacher has the required knowledge to formulate questions.
tiên quyêất câồn thiêất
để sử dụng use case.
Một trong sồấ đó là giả
định răồng dữ liệu nhập
vào đã được kiểm tra lồỗi
và chính xác đêấn mức đủ
để sử dụng trong use
case.

Tiêấng việt:

Diêỗn viên chính: Giáo

viên Diêỗn viên phụ:

Khồng có

Kích hoạt: Giáo viên muồấn thêm một câu hỏi mới vào ngân hàng câu hỏi.

Sự miêu tả:

Ca sử dụng này mồ tả quá trình giáo viên thêm một câu hỏi mới vào ngân hàng câu hỏi.

điêồu kiện tiên quyêất:

8.1 Giáo viên đã đăng nhập vào hệ thồấng.

8.2 Giáo viên có các đặc quyêồn câồn thiêất để thêm câu hỏi vào ngân hàng câu hỏi.

8.3 Ngân hàng câu hỏi đã có trong hệ thồấng.

hậu điêồu kiện:

9.1 Câu hỏi mới được thêm vào ngân hàng câu hỏi.

9.2 Ngân hàng câu hỏi được cập nhật câu hỏi mới.

9.3 Giáo viên có thể xem câu hỏi mới thêm trong ngân hàng câu hỏi.

Lưu lượng bình thường:

10.1 Giáo viên chọn tùy chọn "Thêm câu hỏi" từ menu ngân hàng câu hỏi.

10.2 Hệ thồấng hiển thị form “Thêm mới câu hỏi”.

10.3 Giáo viên nhập câu hỏi, phương án trả lời, đáp án đúng.

Downloaded by Nguyen Hung (K17 HCM)


10.4 Giáo viên nộp đơn.

10.5 Hệ thồấng xác thực biểu mâỗu và thêm câu hỏi mới vào ngân hàng câu hỏi.

Luồồng thay thêấ:

11.1 Nêấu giáo viên nhập biểu mâỗu khồng hợp lệ hoặc khồng đâồy đủ, hệ thồấng seỗ hiển
thị thồng báo lồỗi và yêu câồu giáo viên sửa lại biểu mâỗu.

11.2 Nêấu giáo viên hủy nộp đơn, hệ thồấng seỗ chuyển hướng đêấn menu ngân hàng
câu hỏi.

11.3 Nêấu giáo viên quyêất định khồng thêm câu hỏi mới, hệ thồấng seỗ chuyển hướng
đêấn menu ngân hàng câu hỏi.

Ngoại lệ:

12.1 Nêấu hệ thồấng gặp lồỗi khi thêm câu hỏi mới, hệ thồấng seỗ hiển thị thồng báo lồỗi
và nhăấc giáo viên thử lại.

12.2 Nêấu giáo viên khồng có các đặc quyêồn câồn thiêất để thêm câu hỏi vào ngân hàng
câu hỏi, hệ thồấng seỗ hiển thị thồng báo lồỗi.

Ưu tiên: Trung bình

Tâồn suâất sử dụng: Cao

Quy tăấc kinh doanh:

Câu hỏi khồng được vượt quá 500 ký tự.

Mồỗi câu hỏi phải có ít nhâất hai lựa chọn trả lời.

Câu trả lời đúng nên được đánh dâấu.

giả định:

Hệ thồấng có cơ sở dữ liệu câồn thiêất để lưu trữ ngân hàng câu hỏi.

Giáo viên có kiêấn thức câồn thiêất để xây dựng câu hỏi.

Question 4: writing 2 non-functional requirements.

First Non-Functional Requirement: Performance

1. The website must load within 3 seconds after clicking any link or button.

Downloaded by Nguyen Hung (K17 HCM)


● This can be tested using a performance testing tool to measure the page load time after
clicking any link or button.
2. The website must support at least 500 concurrent users without any significant degradation in
response time.
● This can be tested by simulating 500 concurrent users and measuring the response time.
If the response time remains within an acceptable range, the test can be considered
passed.

Second Non-Functional Requirement: Security

1. The website must use HTTPS protocol for all data transmission to ensure secure communication
between users and the server.
● This can be tested by verifying the URL starts with "[Link] and checking if the website
has a valid SSL certificate.
2. The website must prevent unauthorized access by implementing user authentication and access
control mechanisms, such as password protection and role-based access control.
● This can be tested by attempting to access restricted pages or features without proper
authentication or authorization. If access is denied, the test can be considered passed.

Third Non-Functional Requirement: Reliability

1. The website must be available and accessible to users 24/7 with minimal downtime for
maintenance or upgrades.
● This can be tested by monitoring the website's availability and response time over a
period of time. If the website is consistently available and responsive, the test can be
considered passed.
2. The website must have a backup and recovery system in place to prevent data loss in case of a
system failure or disaster.
● This can be tested by intentionally causing a system failure and verifying that the backup
and recovery system successfully restores data and functionality. If the backup and
recovery system works as expected, the test can be considered passed.

Fourth Non-Functional Requirement: Maintainability

1. The website's code and database structure must be well-organized and modular to facilitate
future maintenance and updates.
● This can be tested by evaluating the website's code and database structure and
verifying that it is well-organized and modular. If the code and database structure are
well- organized and modular, the test can be considered passed.
2. The website must have documentation, such as user manuals and technical specifications, to
assist with maintenance and troubleshooting.

Downloaded by Nguyen Hung (K17 HCM)


● This can be tested by reviewing the website's documentation and verifying that it is
comprehensive and easy to understand. If the documentation is comprehensive and
easy to understand, the test can be considered passed.

Downloaded by Nguyen Hung (K17 HCM)

Common questions

Powered by AI

Including both primary and secondary actors in a use case diagram for the EduNext website helps clarify the roles and responsibilities of different users and systems interacting with the software. Primary actors, such as a teacher initiating a use case to add a question, are essential for defining the core interaction. Secondary actors, which might include administrators managing permissions or students who utilize the questions, provide context for any supportive roles or potential influences. This detailed characterization aids in designing comprehensive interactions and ensuring all stakeholder needs are met by the system .

Assumptions about data handling for the 'Add new question' use case in the EduNext website include ensuring that input data is pre-validated for errors, the existing question bank is structured and accessible, and that system databases are robust for storing new entries. Additionally, it assumes that teachers are skilled enough to create well-formed questions. These assumptions provide a foundation that user inputs meet quality criteria necessary for seamless use case execution, enabling reliable functionality .

In the EduNext system, the extend and include use case relationships serve different purposes. An 'extend' relationship, such as 'Answer question extends Create student group', allows optional behavior to enhance a basic use case under certain conditions. The 'include' relationship mandates that another use case must be executed as part of the original process, ensuring certain actions, like voting on an answer as part of answering a question, are carried out consistently. Understanding these relationships helps streamline processes and manage dependencies effectively within the software .

Security as a non-functional requirement is crucial for the EduNext website to protect student data and maintain confidentiality. It is implemented through HTTPS protocols for secure data transmission and role-based authentication to prevent unauthorized access. These measures are validated by checking HTTPS compliance through SSL certificates and testing access restrictions by attempting to reach secured areas without proper credentials. Meeting these security requirements ensures data integrity and builds user trust in the system's safety .

Business rules in the EduNext system, such as limiting question length to 500 characters and requiring a minimum number of answer options, provide clear constraints and standards that must be adhered to during software development. These rules ensure that the 'Add new question' feature meets educational quality standards and facilitates ease of use. By specifying these constraints, developers can focus on consistency and clarity, leading to a more intuitive design and implementation process that aligns with educational goals .

The key functional requirements of the EduNext website include the ability to import student data from the FAP system, display and update student lists, manage questions, and create student groups, among others. These functions align with constructivist learning principles by facilitating active student engagement through collaborative activities like questioning, voting, and group creation. This approach encourages students to construct knowledge by interacting with peers and utilizing different information sources, which is central to constructivist learning .

Use case diagrams effectively represent interactions in the EduNext website by illustrating the relationships between actors (such as students, teachers, and the FAP system) and the system's functional elements. The diagrams use a rectangle to represent the system, ovals for individual use cases, and lines to show interactions between actors and use cases. Actors are placed outside the rectangle, while use cases are inside, indicating how they are initiated and who performs them. This visual representation simplifies understanding of system requirements and interactions .

A well-defined use case for the 'Add new question' functionality includes components such as UC ID and name, actor definitions, triggers, preconditions, postconditions, normal and alternative flows, exceptions, and business rules. These components ensure clarity in who performs the action, under what circumstances, and how the system should respond. They help guide software implementation by detailing specific scenarios the software must handle, leading to a robust and user-oriented design. For instance, specifying that the question statement must not exceed 500 characters maintains usability standards .

Non-functional performance requirements enhance user satisfaction by ensuring the EduNext website is responsive and reliable. Requirements such as loading the website within 3 seconds or supporting 500 concurrent users without degradation in response time directly influence user experience by minimizing wait times and providing seamless interactions. These constraints can be measured using performance testing tools, which help optimize resource allocation and system architecture to meet these standards, thus significantly enhancing overall user satisfaction .

The reliability of the EduNext website is pivotal for maintaining continuous access to learning resources, facilitating uninterrupted student collaboration, and ensuring data integrity. High reliability means minimal downtime, which supports consistent educational activities and prevents disruptions that could negatively impact student motivation and learning outcomes. Moreover, a strong backup and recovery system ensures that data loss due to failures does not affect learning continuity. Reliable systems enhance user trust, leading to higher engagement and better educational outcomes .

You might also like