Online Magazine Management System Software Engineering Report

Verified

Added on  2023/06/03

|11
|822
|416
Report
AI Summary
This report presents a Software Engineering analysis of an online magazine management system. It includes a use case diagram depicting the system's functionalities, such as making subscriptions and publishing documents. The report expands on selected use cases, detailing the actors, triggers, purpose, and summary of each process. Activity diagrams illustrate the workflows for publishing documents and managing subscriptions, while Level 2 Data Flow Diagrams (DFDs) map the data flow within these processes, including entities, processes, and data stores. The appendix provides additional diagrams and extended use cases to enhance the understanding of the system's design and functionality. The analysis covers the payment process and document publishing, providing a comprehensive overview of the system's architecture and operation.
Document Page
Running head: SOFTWARE ENGINEERING
Software Engineering
Name of the Student:
Name of the University:
Author Note
tabler-icon-diamond-filled.svg

Secure Best Marks with AI Grader

Need help grading? Try our AI Grader for instant feedback on your assignments.
Document Page
1
SOFTWARE ENGINEERING
Table of Contents
Use Case Diagram...........................................................................................................................2
Expanded use case diagram 1..........................................................................................................3
Selected Use Cases..........................................................................................................................3
Making Subscription....................................................................................................................3
Expanded Use Case Diagram..................................................................................................3
Expanded use case diagram 2..........................................................................................................4
Selected Use Cases..........................................................................................................................4
Publishing document...................................................................................................................4
Expanded Use Case Diagram..................................................................................................4
Activity Diagram 1..........................................................................................................................6
Activity Diagram 2..........................................................................................................................7
Level 2 Data Flow Diagram 1.................................................................................................8
Level 2 Data Flow Diagram 2.................................................................................................8
Appendix........................................................................................................................................10
Extended Use Case....................................................................................................................10
Data Flow Diagram....................................................................................................................10
Activity Diagram.......................................................................................................................10
Document Page
2
SOFTWARE ENGINEERING
Use Case Diagram
Figure 1: Use Case Diagram of the Online Magazine Management system
Source: (Created by Author)
Document Page
3
SOFTWARE ENGINEERING
Expanded use case diagram 1
Figure 2: Use Case Diagram of the payment process
Source: (Created by Author)
Selected Use Cases
Making Subscription
Expanded Use Case Diagram
Use case: Making Subscription
Actors: Subscribers (initiator)
Trigger: The subscribers would want to view the online content.
Purpose: The main purpose of subscribing to the system is that they would be able to
Summary: The subscribers would be subscribing to the system and viewing the online content,
pay for the subscriptions, also subscribe for the contents that are online.
Type:
tabler-icon-diamond-filled.svg

Secure Best Marks with AI Grader

Need help grading? Try our AI Grader for instant feedback on your assignments.
Document Page
4
SOFTWARE ENGINEERING
a. Secondary
b. real
Cross reference: The system provides the subscribers with the ability to view the online content,
charge fees online, help them in paying for the subscriptions. 3.6.1 Functional Requirements
REQ -1, REQ -2, REQ -3, REQ -4.
Pre-conditions (assumptions)and post-conditions: The subscriber has to pay for the
subscriptions in order to become a subscriber and pay for the online content that they view.
Expanded use case diagram 2
Figure 3: Use Case Diagram of the publishing document
Source: (Created by Author)
Selected Use Cases
Publishing document
Expanded Use Case Diagram
Use case: Publishing document
Document Page
5
SOFTWARE ENGINEERING
Actors: Publisher (initiator)
Trigger: A publisher wants to publish the piece of work.
Purpose: The Online magazine management system is to publish the piece of work.
Summary: The publisher would like to publish the magazines on the management system and
hence they would be able to upload their piece of work on the system.
Type:
a. primary
b. essential
Cross reference: The system provides the publisher to prepare online adverts and publish them
online, 3.5.1 REQ -1 and REQ -2
Pre-conditions (assumptions)and post-conditions: The publisher should have the online adverts
already prepared.
Document Page
6
SOFTWARE ENGINEERING
Activity Diagram 1
Figure 4: Activity Diagram of Publishing Documents
Source: (Created by Author)
The activity diagram of the process of publishing the documents for the online magazine
has been used for displaying the processes that would be taking place within the organization.
The publisher uploads the paper that is to be published online and the library staff stores the
details of the document on the system and publishes it online.
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
7
SOFTWARE ENGINEERING
Activity Diagram 2
Figure 5: Activity Diagram of Making Subscriptions
Source: (Created by Author)
The activity diagram of the subscription process has been described here. The process
starts when the subscriber logs in to the system and after the registration process they are able to
subscribe to the system and after the subscriptions lets them view contents online.
Document Page
8
SOFTWARE ENGINEERING
Level 2 Data Flow Diagram 1
Figure 6: Data Flow Diagram of Publishing Documents
Source: (Created by Author)
The data flow diagram for publishing the documents have been discussed in this part of
the report. The main process is Publisher publishing the documents and the two sub processes
that are included in this process are the advertising documents and publishing documents. The
main entities of the system are the publishers and the Library Staffs. The database in which the
details of the operations are stored are in the Advert File.
Level 2 Data Flow Diagram 2
Figure 7: Data Flow Diagram of Making Subscriptions
Source: (Created by Author)
Document Page
9
SOFTWARE ENGINEERING
The data flow diagram of making subscriptions has been described in this part of the
report. The main entity that has been identified here are subscribers. The process of the
subscribers making subscriptions and making payment for viewing the content online has been
described here with the main process being the Subscribers making the subscriptions.
tabler-icon-diamond-filled.svg

Secure Best Marks with AI Grader

Need help grading? Try our AI Grader for instant feedback on your assignments.
Document Page
10
SOFTWARE ENGINEERING
Appendix
Extended Use Case
Data Flow Diagram
Activity Diagram
chevron_up_icon
1 out of 11
circle_padding
hide_on_mobile
zoom_out_icon
[object Object]