Scribd
Upload
172 views5 pages

Final Examination: SUBJECT: Software Engineering (ID: IT076IU)

This document outlines the instructions for a final exam in Software Engineering. Students will work in groups of 5-7 members to complete several tasks related to a topic of their choice, including: 1. Listing functional and non-functional requirements. 2. Drawing an analysis class diagram and explaining the analysis process. 3. Deriving a design class diagram and describing the differences from an analysis diagram. 4. Creating a sequence diagram and explaining the process. 5. Providing test cases matching the number of group members. The exam aims to test students' software engineering knowledge and ability to plan the development process. Guidelines specify including member names and contributions in

Uploaded by

Hồng Đức
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
172 views5 pages

Final Examination: SUBJECT: Software Engineering (ID: IT076IU)

This document outlines the instructions for a final exam in Software Engineering. Students will work in groups of 5-7 members to complete several tasks related to a topic of their choice, including: 1. Listing functional and non-functional requirements. 2. Drawing an analysis class diagram and explaining the analysis process. 3. Deriving a design class diagram and describing the differences from an analysis diagram. 4. Creating a sequence diagram and explaining the process. 5. Providing test cases matching the number of group members. The exam aims to test students' software engineering knowledge and ability to plan the development process. Guidelines specify including member names and contributions in

Uploaded by

Hồng Đức
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

International University - VNUHCM

School of Computer Science and Engineering


-----------------

Final Examination
Date: 12/01/202; Duration: 08h00 (12/01/2022) – 22h00 (15/01/2022)
Online Electric devices are allowed.

SUBJECT: Software Engineering (ID: IT076IU)


Approval by the School of Computer Science Lecturer:
and
Engineering
Signature

Full name:
Proctor 1 Proctor 2
Signature Signature

Full name: Full name:

STUDENT INFO
Student name:

Student ID:
INSTRUCTIONS: the total of point is 100 (equivalent to 40% of the course)
1. Purpose:
• Test your knowledge of the principles and methods of software engineering (CLO1) •
Examine your plan of the software development process (CLO2)
2. Requirements:
• Carefully read each question and answer it following the requirements.
• Write the answers and draw models CLEAN and TIDY directly in the exam paper.

[The questions from here]

International University – VNUHCM Student Name:………...………………………………… School of


Computer Science and Engineering Student ID:………………………………………………. -----------------
QUESTIONS
For this exam, students are teamed up to form groups of 5 to 7 members with a topic of your
own choice (in the attachment). Each group must work together to perform the following tasks
on the given topic:
1. (20 marks) List all functional and non-functional requirements, at least four requirements
of each type.
Req.ID Requirement Name Details Description Type
1 Authentication The customer, buyer or admin can Functional
create and use by their own
account
2 Authorization Author login, buying process…. Functional

3 Data history User can use history of their Functional


data( probably admin)
4 Stock transaction Correction, adjustments, and cancel Functional
stock
5 Adminstrative Admin permission Functional
6 Maintainability Maintain system/details Functional/Non-
functional
7 Security Keep stock transaction, data Non-functional
information in security
8 Performance Time, date… Non-functional
9 Capacity Number of data(available stock, Non-functional
private info)
10 Manageability Profit canculator, stock delivery, Non-functional
buying data)
11 Service Paid/Pending stock Non-functional

2. (20 marks) Draw an analysis class diagram. Present necessary steps of the analysis
process for drawing this class diagram.
Present necessary steps of the analysis process for drawing this class diagram:
● Analyze the situation and create a Use Case diagram.
● Give each class an appropriate name so that the elements may be easily identified.
● Fill in the required attributes and functions for each class
● Identify elements and each relationship between classes

3. (20 marks) From the results of question 2, derive a design class diagram. Describe the
differences between an analysis class diagram and a design class diagram.
Difference
+ Analysis Class Diagram show the requirement and all functions of the total
project, while Design Class Diagram show more detail and deeper about the ability
of the project
+ Some information in Analysis Class Diagram may appear in Design Class
Diagram
+ The main point of the Analysis is to figure out what the problem is and sketch the
manuscript of the requirement. It means the Analysis Diagram focus on solving the
issues.
+ The goal of the design is to deal with the problem and gives some solutions
against it
+ To sum up, Analysis Class Diagram is often showed to the clients, customers or
some third-party that want to have a full view of the project. And Design Class
Diagram often used by Developer that they can solve the problem clearly

4. (20 marks) Draw a sequence diagram. Describe the step-by-step process to create a
sequence diagram.

− Identify a set of objects that will participate in the general collaboration (or use case
scenario)

− Consider the first point of the scenario (or if you get it from the first point of the flow of
event of a use case)

− Consider what the system needs to be done to respond to an actor when the actor
sends the message to the system

− Repeat each of the points of the scenario (or flow of event) and until you complete all
the points in the scenario
5. (20 marks) List test cases based on the requirements. The number of test cases is at
least equal to the number of group members. The test cases must include the following
information: step, action, expected system response, pass/fail, comments.

GUIDELINES
1. Clearly state your reasonable assumptions and explain your decisions (if any)

2. Your report must mention the members’ names and their contribution percentages.
3. Your report must be uploaded into the BlackBoard system and MS. Teams.

– END –
2 /2

You might also like