Scribd
Upload
20 views

T-2002-03 - Tutorial 3 SDLC and UML Use Case (Part 1)

The document provides an overview of the software development life cycle (SDLC) and introduces use case diagrams in Unified Modeling Language (UML). It discusses the four phases of the SDLC - planning, analysis, design, and implementation. It also defines software development methodology and lists some common methodologies. For different systems described in the document, it suggests the most appropriate generic software process model to use based on factors like requirements changes and upfront explanation needed. Finally, it introduces use case diagrams and provides examples to model user requirements and interactions with different actors in a university accommodation system and textbook donation management app.

Uploaded by

Jack TK
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
20 views

T-2002-03 - Tutorial 3 SDLC and UML Use Case (Part 1)

The document provides an overview of the software development life cycle (SDLC) and introduces use case diagrams in Unified Modeling Language (UML). It discusses the four phases of the SDLC - planning, analysis, design, and implementation. It also defines software development methodology and lists some common methodologies. For different systems described in the document, it suggests the most appropriate generic software process model to use based on factors like requirements changes and upfront explanation needed. Finally, it introduces use case diagrams and provides examples to model user requirements and interactions with different actors in a university accommodation system and textbook donation management app.

Uploaded by

Jack TK
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 7

WIA2002 Software Modelling

Tutorial 3

Part 1: Overview of Software Development Life Cycle

1. What are the four phases of SDLC?


Planning, Analysis, Design, Implementing

[HS] Okay

2. What is software development methodology?


It is a formalized approach to implementing the Software Development Life
Cycle.
Software development methodology refers to structured processes involved
when working on a project. It is a blend of design philosophies and pragmatic
realism that stretches back to the early days of computing.

It can be divided into four categories: structured design, rapid application


development, object-oriented system analysis and design, and agile
development. All of these are different in the ordering of processes. Different
methodologies may have their own advantages and disadvantages. Therefore,
there is no best method, only the most appropriate one, depending on the
budget, =tools, time and any other factors.

[HS] Very good.

3. Giving reasons for your answer based on the type of system being developed,
suggest the most appropriate generic software process model that might be
used as a basis for managing the development of the following systems:

● An app to give an alert notification on haze condition based on the user


current location
● An app to purchase used textbooks

● A mobile story books for children

● A system to control anti-lock braking in a car

● A virtual reality system to support software maintenance

● A university accounting system that replaces an existing system

● An interactive travel planning system that helps users plan journeys with
the lowest environmental impact

software being developed generic software process

An app to give an alert notification Waterfall model. The cost can be


on haze condition based on the minimise.
user current location

An app to purchase used textbooks Reuse-oriented software


engineering. The purchase and
viewing component is an existing
component because it is quite
general.

A mobile story books for children Reuse-oriented software


engineering. The existing reading
book component can be re-used
and hence reducing cost.

A system to control anti-lock Incremental development. It is


braking in a car because the requirements mostly
will change as real user experience
with the software.

A virtual reality system to support Waterfall development. It required


software maintenance up-front explanation from the user
about the entire system.

An interactive travel planning Incremental development. The


system that helps users plan actual function will keep changing
journeys with the lowest in order to maximise the user
environmental impact experience.

[HS] Okay. Good. The following is the summary I made. I am trying to create
a game for you during tutorial session at https://www.socrative.com/ >
Student Login. I will give a code during our tutorial session ya. :) Meanwhile,
please idigest the table below.
4. Consider the reuse-based process model shown below.

Explain why it is essential to have two separate requirements engineering


activities in the process.
a) Requirements specification is for component analysis of the legacy system
in order to get an initial idea of the components that may be used.
[HS] Okay.

b) After this, a second requirements engineering activity, known as


requirements modification, will allow customers to provide further more
detailed information about the components, allowing the reused component
that will be identified.

[HS] Requirements modification is a process to make the customer to modify


their requirements based on (a). What happens if the customer does not
agree to modify their requirements?

Part 2: Introduction of UML Use Case Diagram

5. Determine the actor and use case involved for each requirement:
a) Students can enroll many classes
Actor: student
Use case: UC-1 enroll class
b) Students should login before entering to the system
Actor: student
Use case: UC-1 login
c) Customers enable to purchase many products through the system
Actor: customer
Use case: UC-1 purchase product
d) Customers must logout the system
Actor: customer
Use case: UC-1 logout

[HS] Good, good. Very good.

6. There are two types of students that can apply for accommodation through
the University Accommodation System. There are Undergraduate and
Postgraduate students. Only undergraduate students are required to make
payment. Draw an UML use case diagram to model this scenario.
(Note: You are not required to model other scenarios such as login use case or
register use case).

[HS] Good. Just improvise the naming convention of use cases as they are not
accurate.

[HS] Wow, we have not learnt generalizing actors, but you are able to do this.
Bravo. Did you read lecture notes week 3? hehe.
[HS] Good. Exactly like my answer scheme with exception of one thing. Clue:
naming convention of the use cases. can someone guess? :)

7. To donate textbooks using Textbook Management App, a donor is required to


register account by providing name, matriculation number, and address.
Once the donor has registered, the donor must log in to use the app. The
donor can donate his old book by giving the name of the books, and the
quantity of the book.
a) Draw an UML use case diagram to model this scenario.
[HS] good. Just like my answer scheme with exception of 1 thing at register
use case. can someone guess? :)

[HS] Good too. See, there are multiple correct answers. please revise the
naming convention for use cases.

b) Think of a way on how this software can enable receiver to: -


- view available book
- request book to be delivered to his/her house.
(Note: You are not required to model other scenarios)
[HS] Good. Be better if you combine answers from (a).

[HS] We have not learnt extend yet. Next week ya. This is not accuracy. The
way to read this diagram is: “Sometimes, in order to view available book, the
receiver must request deliver book”.

Does this tally with the question?

You might also like