0% found this document useful (0 votes)
19 views1 page

CSE215L Project Requirements

Uploaded by

hossain.walid018
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
19 views1 page

CSE215L Project Requirements

Uploaded by

hossain.walid018
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 1

CSE215 Lab: Project Specification

You need to design your own classes with following requirements.

• Implement a system that will allow the user to add data in the system, display the data already
stored, delete data from the system given a certain info or other criteria, search for data given a
certain info or other criteria, edit data given an info or other criteria. After the changes, the files
in which you will store the information need to be updated so that the display function always
shows the updated version of the system.

• At least three classes are required (at least 1 super class and 2 sub classes) - 15 points
• Create two different packages and use those - 5 points
• In your class design you must have to have the reflection of the concept of Encapsulation,
Method overloading, Method overriding, and Abstraction. - 20 points
• Exception must be handled for any abnormal/exceptional cases. At least 1 custom exception
must be there. - 10 points
• You have to use text/binary file in terms of storing the data. - 10 points
• Make user interface using either java FX or Swing - 10 points

• Project report with UML diagram of your classes — 20 points

• Viva -------------------------------------------------- 10 points

General Guideline:

• Divide the work among the team members so that no single member gets overburdened. All
members must be involved in the implementation. Cooperate with each other so that you learn
from the implementation process. You may study online material for your better understanding
but the work you submit must be yours. Plagiarism of any form is highly discouraged. Although
a single member will not develop the entire project and you must have a clear understanding of
how code in each section of the project contribute and coordinate in the overall development of
the project.

• During viva you will be asked questions on the sections you have implemented (inside your
code) as well as on the entire project in general. So, it is recommended that you have a clear
understanding of the entire project and the concept behind it.

• At the day of project submission, you need to submit your project softcopy/source code (in
canvas) also a project report hardcopy (printed) written in MS word with details about your
project and hand over it to me during the project demonstration. In project report don’t print the
code; only the details about your project likely - introduction, methodology, class UML
diagram, uses, conclusion etc.

• In each team maximum 2 people is allowed. Make sure no group will have the same topic for
the project. In that case, project will be rejected and no marks will be given to any of the group.

N:B: You can’t make project on the following topic: library management system, pharmacy
management system, bank management system, Bus, Air, Rail etc. management system, calculator,
and any type of game.

You might also like