Solution file Final SE exam
Question 01
Solution 1(a)
Non-documented requirements are difficult to negotiate between the stakeholders.
The coverage of the requirements by means of test cases cannot be checked.
Question 01
a.
Incremental development is supported through small, frequent system releases.
Customer involvement means full-time customer engagement with the team.
People not process through pair programming, collective ownership and a process that
avoids long working hours.
Change supported through regular system releases.
Maintaining simplicity through constant refactoring of code.
b. Students must translate the below diagram in words and can draw a diagram of scrum cycle
just to give further clarity.
c. 72
d. Write a test
Make sure the test fails
Write enough code so the test passes
Refactor as necessary
e. because of software invisibility
Question 03
1. Define interaction modes in a way that does not force a user into unnecessary or undesired
actions
Yes- provided dropdown so user can select role
2. Allow user interaction to be interruptible and undoable
No- No clear button. Only ok button.
3. Design for direct interaction with objects that appear on the screen.
Yes. GUI offers direct interaction with buttons and control items
4. Anticipation.
No. It is not known whether already added stories can be edited or deleted. Moreover, the link is
blue but not underlined so hard to guess it is a link. OK does not clearly describe what would
happen after clicking it.
5. Metaphors
No metaphors used
Question 04
a) Definitions
b)
-Novice users: Users will not have used a computer system and will be unaware of what user stories are.
-Knowledgeable Intermittent: Will know what user stories are, but will not have used such a system. May
require time to add user stories as unfamiliar with interface
-Knowledgeable Frequent: Will have knowledge about user stories as well as be comfortable with
computers. Use the interface frequently so may know how to work around bugs present in the system
-User's mental model: User will know that each user story has three parts and an computer system to
create user stories will give user the option to add a subject, some description and add detailed user stories
as well as provide functionality to add/ edit and delete user stories
-Syntactic knowledge: User will know how to operate a GUI and understand what dropdown, textboxes,
cross buttons etc are usually used for
Question 06
a.
V= E-n+2
v= 23-20+2 = 5
Question -05
1. Two external Input (Dictionary name, and document name)
2. Three external out puts—word processed message, error message, report
3. Two external inquiries—word process inquiry and error found inquiry.
4. One ILF- (Dictionary)
5. Two, EIFs (personal dictionary, Document file)
2 5 10
3 4 12
2 6 12
1 8 8
2 7 14
count 56
Question 07
Solution Question 08
a. The sequence diagram helps in finding the test cases. You are required to draw a
sequence diagram for the following use cases and design test cases with the help of the
sequence diagrams.
b. For each test case, please mention the category (e.g. unit/performance/black box/)
it belongs to.
Test Cases for Quick & Routine Checkup
We will perform Scenario Testing for these problems. Since, both checkup require
user authentication and payment methods, their test cases are added first.
Test Cases for User Authentication (Unit Testing & White Box):
Login user with valid username and password.
Login user with valid username and without a password.
Login user with wrong username but correct password.
Login user with valid username but incorrect password.
Login user with incorrect username and incorrect password.
Login user with empty username and password fields.
Test Case for Symptoms Selection (Unit Testing & White Box):
Proceed without selecting any symptoms from the provided list.
Select symptoms of non-critical sickness.
Select symptoms of critical sickness.
Select symptoms of both critical and non-critical sickness.
Select all the symptoms on the list.
Select only one symptom from the list.
Test Case for Payment Method (Component Testing & Black Box)
Select Debit Card/Jazz Cash/Easy Paisa and provide correct account and
pin, then proceed with the payment.
Select Debit Card/Jazz Cash/Easy Paisa and provide correct account and
wrong pin, then proceed with the payment.
Select Debit Card/Jazz Cash/Easy Paisa and provide invalid account but
correct pin, then proceed with the payment.
Cancel the transaction before completion to see if it still navigates to the
physician selection page or not.
Test Case for Physician Selection (Componenet Testing & Black Box)
Proceed with selecting physician from the available list. (Notice if system
assign the selected physician or not).
Select more than one physician from the list.
Proceed without selecting any physician (Notice if a physician is assigned
by the system or not).
Logout System (Navigate back to check if system allows the last page to
reload or not).
Test Cases for System Validation (System Testing & Black box)
Login the system with valid credentials, select non-critical sickness
symptoms, pay the fee via payment method, select a physician, verify the
appointment, log out the system.
Login the system with valid credentials, select critical sickness symptoms,
pay the fee via payment method, select a physician, verify the appointment,
log out the system.
c. How can you validate the safety and efficiency of the system, what kind of test
cases will be required?
a. To validate the efficiency of the system, we would have to perform the
Performance Testing. Following Tests can be used to evaluate the performance of the
system.
i. Log in Users and Navigate the website, look for any delay in response of the
webpages. Note the page loading time for 500, 1000, and 1500 users.
ii. Request appointments for patients with different symptoms and select phsyicians
for 500, 1000, and 1500 users. Note system response time for all 3 batches.
iii. Similarly, request for routine check up requests with all 3 batches to see if system
lags for any functionality.
If the website functions smoothly on 1000 and more users, then browsing
efficiency is sufficient.
b. Safety Validation: Medical records are extremely private and very difficult
to acquire if lost.
i. We will need to keep multiple data backups for patients with long term sickness.
ii. Perform soft crash to see if crash corrupts the incomplete data.
iii. Disconnecting a user after the payment to see if the system will allow the user to
continue from where s/he left.
d. Can we utilize the Test Driven Development approach for the above mentioned
system, support your answer with 2-3 logical arguments?
The Test Driven Development (TDD) in this regard will be most helpful for
following reasons.
Since, the system will be used by the Hospital it is highly critical and each
functionality of the sytem should be tested rigorously. This will be
achievable with regression testing; which is core feature of TDD.
With TDD each line of code will be executed and tested (full code
coverage) hence; ensuring nothing unexpected happens with the user;
saving the reputation of the hospital.
Test will be written for each functionality, providing a good documentation
for the system. This will help the hospital management in system
configuration & increasing the usability of the system.
