Object-Oriented Modeling of Lilydale Movies System Project

Verified

Added on  2020/05/04

|10
|1028
|322
Project
AI Summary
This project focuses on the object-oriented (OO) modeling of the Lilydale Movies system. The assignment includes a use case diagram illustrating various functionalities such as customer registration, movie loaning, and sales reporting. Detailed use case descriptions are provided, outlining the triggers, pre-conditions, post-conditions, activities, and exceptions for each use case. Activity and sequence diagrams are also presented to visualize the system's processes and interactions. The project covers essential aspects of software design, including registration, movie management, and reporting features. The diagrams and descriptions collectively provide a comprehensive model of the system's behavior and structure. The assignment concludes with a bibliography of relevant academic sources.
Document Page
Running head: OO MODELLING OF LILYDALE MOVIES SYSTEM
OO Modelling of Lilydale Movies System
Name of the Student
Name of the University
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
1OO MODELLING OF LILYDALE MOVIES SYSTEM
Table of Contents
1. Use Case Diagram:......................................................................................................................2
2. Use Case Description:..................................................................................................................3
3. Activity and Sequence Diagram:.................................................................................................7
Bibliography:...................................................................................................................................9
Document Page
2OO MODELLING OF LILYDALE MOVIES SYSTEM
1. Use Case Diagram:
Figure 1: Use Case Diagram of Lilydale Movies
(Source: Created by Author)
Document Page
3OO MODELLING OF LILYDALE MOVIES SYSTEM
2. Use Case Description:
Register: The customer and staff will register themselves into the system through
providing information.
Login: The customer and staff will login to the system through user id and password.
Loan: The customer can loan movies from organization.
Return Loan: he customers will be returning movies that has been loaned.
Buy: The customers will be buying movies from Lilydale Movies.
Reserve: The customers will be reserving non available movies so that they get
notification as soon as it appears and loan or buy those.
Renewal: The system will renew the loan period of a movie.
Comment: The customers will be providing feedback of a movie through comment.
Record Movie: A new movie will be registered within the system.
Transaction history: The customer will be able to see the transaction history of a
customer.
Movie Catalogue: The movies that has been recorded within the system will be shown to
the staff as a list along with status of availability.
Rent Analysis: A report regarding the rent of movies either against a customer or a movie
will be presented.
Overdue list: The list of the customers those have not returned the movie within time will
be presented as a list along with additional related information.
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
4OO MODELLING OF LILYDALE MOVIES SYSTEM
Sales Report: The management will be able to see the sales amount and all the other sales
related information within this report.
Out of Stock Report: The management will be able to see which movie is out of stock
and for how long.
Movie Rental Report: A report against all the customers who have rented movies from
Lilydale Movies.
Intermediate Use Case Description:
Name Registration
ID UC-1
Brief
Description
Registration of customers into the system
Trigger Increase customer amount
Pre-
Condition
The customer must not be registered before
Post
Condition
The customer data must be valid
Activity Customer System
Fill the digital form Collect data from form
Analyze data
Send additional details if required Analyze the information
Check if customer is pre-registered
Registers customer
Document Page
5OO MODELLING OF LILYDALE MOVIES SYSTEM
Exception The customer data are true but not passed the system evaluation
Name Sales Report
ID UC-1
Brief
Description
A movie sales related data will be provided to the management
Trigger A new report is being generated
Pre-
Condition
Any sales has been occurred within the month
Post
Condition
The report is generated
Exception The stores are not within geographical boundary
Name Record Movie
ID UC-1
Brief
Description
The staff register a movie within system
Trigger The movie list is increased by one
Pre-
Condition
The movie is new to the system
Post
Condition
The movie details support organization allowed genre
Exception The movie details are not provided with it
Document Page
6OO MODELLING OF LILYDALE MOVIES SYSTEM
Fully Developed Use Case Description:
Name Registration
ID UC-1
Brief
Description
Registration of customers into the system
Trigger Increase customer amount
Pre-
Condition
The customer must not be registered before
Post
Condition
The customer data must be valid
Activity Customer System
Fill the digital form Collect data from form
Analyze data
Send additional details if required Analyze the information
Check if customer is pre-registered
Registers customer
Exception The customer data are true but not passed the system evaluation
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
7OO MODELLING OF LILYDALE MOVIES SYSTEM
3. Activity and Sequence Diagram:
Figure 2: Activity Diagram of Lilydale Movies
(Source: Created by Author)
Document Page
8OO MODELLING OF LILYDALE MOVIES SYSTEM
Figure 3: Sequence Diagram of Lilyd ale Movies
(Source: Created by Author)
Document Page
9OO MODELLING OF LILYDALE MOVIES SYSTEM
Bibliography:
Abrahamsson, P., Salo, O., Ronkainen, J. and Warsta, J., 2017. Agile software development
methods: Review and analysis. arXiv preprint arXiv:1709.08439.
Estler, H.C., Nordio, M., Furia, C.A., Meyer, B. and Schneider, J., 2014. Agile vs. structured
distributed software development: A case study. Empirical Software Engineering, 19(5),
pp.1197-1224.
Fuggetta, A. and Di Nitto, E., 2014. Software process. In Proceedings of the on Future of
Software Engineering (pp. 1-12). ACM.
Kaur, R. and Sengupta, J., 2013. Software process models and analysis on failure of software
development projects. arXiv preprint arXiv:1306.1068.
Krahn, H., Rumpe, B. and Volkel, S., 2014. Roles in software development using domain
specific modeling languages. arXiv preprint arXiv:1409.6618.
Perkusich, M., Soares, G., Almeida, H. and Perkusich, A., 2015. A procedure to detect problems
of processes in software development projects using Bayesian networks. Expert Systems with
Applications, 42(1), pp.437-450.
Sharma, C., Sabharwal, S. and Sibal, R., 2014. Applying genetic algorithm for prioritization of
test case scenarios derived from UML diagrams. arXiv preprint arXiv:1410.4838.
Störrle, H., 2014. On the impact of layout quality to understanding UML diagrams: size matters.
In International Conference on Model Driven Engineering Languages and Systems (pp. 518-
534). Springer, Cham.
chevron_up_icon
1 out of 10
circle_padding
hide_on_mobile
zoom_out_icon
[object Object]