COMP1712 Software Engineering Principles and Practices

Running head: SOFTWARE ENGINEERING FUNDAMENTALS
Software Engineering Fundamentals
Name of the Student
Name of the University
Authors note

1SOFTWARE ENGINEERING FUNDAMENTALS
Table of Contents
Expanded use cases description.................................................................................................2
Level 2 data flow diagram..........................................................................................................5
Activity diagram.........................................................................................................................6
Appendix B: Analysis Model.....................................................................................................7
Appendix C: Issues List.............................................................................................................7

2SOFTWARE ENGINEERING FUNDAMENTALS
Expanded use cases description
For the proposed online library management system there will be modules for
publishers, subscribers, advertisers and community discussion about the published magazine
on the online magazine platform. Following are the two of the use cases that will be
expanded for better understanding of the process and scenario. The use cases are payment
for advertisement (in subscription management module) and online advertising use case.
For subscription management use case
Figure: Expanded use case for the making payment for Advertisement

3SOFTWARE ENGINEERING FUNDAMENTALS
The above is the use case for the subscription management module for the online
magazine management system. For this use case, the main actors are Guest visitor to the site,
Subscribed Members to the system, Unsubscribed members to the system, system
Administrator, Publisher of the magazines, Advertisers and Forum users for the published
magazines.
The use case includes the different stages that needs to be completed to complete the
process. Following table consist of different details of the expanded use case;
Use case ID UC001
Use case Name Payment for advertisement
Primary
Actor
Subscribed and logged in advertiser of the
system.
Secondary
Actors
The system administrator.
Preconditions The member has an active account on the system.
The advertiser needs to be logged in to the
system.
Advertiser should not have any previous pending
payment for the advertisement.
Assumptions The user/advertiser is registered.

4SOFTWARE ENGINEERING FUNDAMENTALS
Trigger The advertiser has requested to post an
advertisement on the online magazine system.
Success Post
Condition
Confirmation mail and screen is displayed on the
screen.
The user is able to access use the functionalities provided
by the system.
Failed Post
Condition
Failure screen is displayed with the reason of
failure.

5SOFTWARE ENGINEERING FUNDAMENTALS
Use cases for Subscribe for magazines and pay for subscriptions
Figure: Expanded use case for subscription of the users
Use case ID UC002

6SOFTWARE ENGINEERING FUNDAMENTALS
Use case Name Subscribe for magazines and pay subscriptions
Primary Actor Registered and logged in user.
Secondary Actors System Administrator
Preconditions User has an active account in the online magazine management system.
The users search for the specific publications or copies of the content
through the system.
There are no pending subscription payments by the user.
The user has not reached a certain number of subscriptions for the
month.
Assumptions The user is an active user on the system.
Trigger The user has selected a specific version or copy of a content to
subscribe on the online magazine system.
Success Post Condition Confirmation mail for the subscription is sent to the registered
mail address.
The user is able to view the status of the subscription through the
system.
Failed Post Condition Failure screen with proper reason is displayed on the screen.

7SOFTWARE ENGINEERING FUNDAMENTALS
Level 2 data flow diagram
Following is the data flow diagram of the use case of making the payment for the
advertisement on the magazines.

8SOFTWARE ENGINEERING FUNDAMENTALS
After the successful completion of this operation system also provides the advertisers
with the other option for posting the advertisement and publish it on the available magazines
in the system. After the confirmation of the of the upload of the advertisement and payment
the system will redirect to the profile page of the user.
Once the user uploads the advertisement using the system, the advertiser have to
enter the auto generated advertisement ID to publish or edit the advertisement. This stage
will validate the identity of the authorised advertiser to the system and their payment.
Moreover, from their respective user accounts the advertiser will be able to view their past
payments, renewals of their packages and the publication on which their advertisements are
posted as well as making changes to the advertisements to improve their reach.

9SOFTWARE ENGINEERING FUNDAMENTALS
The above one is the data flow diagram for the subscription to the magazines use case
by the subscribers. The use case involves a number of other processes like, the subscriber log
in to the system, accessing the available magazines according to the different authors and
content type.
In this use case the main actor is the potential subscriber to the system in the
scenario. The subscriber would have to log in to the system using the correct credentials.
Through the authentication process the user logs in to the system selects one magazine
either through the search or list process helps in the user to search the required title for the
type of magazine required by him.

10SOFTWARE ENGINEERING FUNDAMENTALS
Activity diagram
Figure: Activity diagram for making payment for advertisement

11SOFTWARE ENGINEERING FUNDAMENTALS
The above diagram is activity diagram for making the payment for posted
advertisements. The diagram depicts the overview of the activities that needs to be completed
for completing the use case. The use case or the process starts as the advertiser registers on
the online magazine management system with the required credentials of the user. In the next
stage the user will check for the duration for which the advertiser wants to publish their
advertisement on the system as well as for the copies or publications on which they want to
publish. After making the payment they are navigated to the system modules where they can
easily upload their content to advertise.

12SOFTWARE ENGINEERING FUNDAMENTALS
Figure: Activity diagram for Subscription use case

13SOFTWARE ENGINEERING FUNDAMENTALS
The above is the activity diagram is provided for the subscription management use
case. This use case starts at the time a registered or unregistered subscriber wants to subscribe
for a magazine or publication. In case the user is not a registered then the system will redirect
to the registration module to complete the process. If the user is registered one, then the will
login using the registered credentials that are previously stored credentials through the
system. After logging in to their account the user can find for the single articles, single issues,
sets and series – either free or fee-based subscription. The users can search for content of
their interest and subscribe for the selected copy. In order to complete the subscription,
process the user will be request to complete the subscription fees after checking the
subscription fee structure. After the users gets the subscription selcted magazine the user will
be able to add those magazines to their favourite magazines.
The administrator can be able to use this specific module in order process the reports
for the subscriptions of the user and along with the revenue from the subscriptions.

14SOFTWARE ENGINEERING FUNDAMENTALS
Appendix B: Analysis Model

15SOFTWARE ENGINEERING FUNDAMENTALS