0% found this document useful (0 votes)
309 views1 page

Software Engineering Midterm Case Study 1201718

The document provides instructions for a midterm exam in software engineering with two cases to answer. Case 1 asks students to explain what is wrong with a domain model for calculating student GPA and modify it, using an appropriate responsibility pattern. Case 2 asks students to model an ATM transaction process as a UML activity diagram. Students must submit their answers by October 23, 2017 at 12:00 noon, writing their name on A4 bond paper.

Uploaded by

Kristian Czar
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)
309 views1 page

Software Engineering Midterm Case Study 1201718

The document provides instructions for a midterm exam in software engineering with two cases to answer. Case 1 asks students to explain what is wrong with a domain model for calculating student GPA and modify it, using an appropriate responsibility pattern. Case 2 asks students to model an ATM transaction process as a UML activity diagram. Students must submit their answers by October 23, 2017 at 12:00 noon, writing their name on A4 bond paper.

Uploaded by

Kristian Czar
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/ 1

Software Engineering Midterm Exam, 1st Semester, 2017-2018

Read, analyze, and work on the following cases. Submit answers not later than October 23, 2017, 12:00 noon.
Write your answers in A4 size bond paper, with your name written at the left-top portion of all the pages.

CASE #1 (50 points)

Consider the domain model below. A clerk would enter a student ID to the system to request the calculation of a
students Grade Point Average (GPA). The GPA is calculated as follows:
To find out your grade points for a class you have taken, multiply your grade by the credit hours assigned to the
course. Say you took Software Engineering, which has three units credit, and you earned a 2 in the course. Just
multiply 2 (your mark) x 3 (credit hours) = 6. So, for this class, you have six grade points. Once you have figured out
your grade points you can compute the average. You arrive at an average by first adding a group of numbers and
then dividing one total by another. Since your task is to compute your grade point average, you need to total your
grade points. Next divide the total grade points by the total credits attempted.

a. Explain what is wrong with the domain model, and do any modifications necessary.

b. Which is the appropriate responsibility pattern to deploy in order to calculate a students GPA? Utilize this
pattern in order to answer this question and comment on the notion of partial responsibilities where applicable.

CASE #2 (50 points)

Model the following scenario as a UML activity diagram (or process flowchart):

A customer arrives at an ATM. He inserts his card and then he enters his password. If the password is not accepted
he has to re-enter it. If the password is accepted, he selects the type of transaction he wishes to conduct and then he
performs the transaction. Once the transaction is complete, he has the option to select and perform more
transactions, otherwise he gets back his card and his interaction with the ATM terminates.

You might also like