SHARE MANAGEMENT APPLICATION - Individual Assignment
IS6217
Share Management Application
Building on the work you completed in Semester 1 you are going to create an object-
oriented, database-driven, Python GUI share management application for the MIMAS
Investment Ltd. The application must interact with a Database (e.g. MIMAS_Investment.sqlite)
that contains information about customer and account details. Sample Data is presented below.
You are not obliged to use this data structure, but the database should support the functionality of your
application.
Field Data Type Sample Data
Customer_ID Autonumber 1
Cust_Name Text Joe Bloggs
Cust_Address Text Text
Cust_Telephone Text (021)12345678
Field Data Type Sample Data
Account_Number Autonumber 000000001
Cash_Balance Numeric 1000€
Account_Type Text Savings
PIN Numeric 1234
Share_Balance Numeric 100
You are required to create a share management application that will allow the customer to interact
with the share management application and update the database accordingly. For the purposes
of meeting the Minimum Requirements noted below you will need to populate
the database with relevant customer and account records. Advanced requirements for this
application require you to create administration functionality within your application. For this
exercise, you may use a share value of 1 euro per share, or any other value you see fit.
Minimum Requirements (75%):
• Pin Access.
• A customer should be able to withdraw money if sufficient funds available (updating balance
in database as appropriate).
• A customer can deposit funds (updating balance in database).
• A customer can check their balance, both share and cash (retrieve balance from database).
• A customer can purchase shares if they have sufficient cash balance.
• A customer can sell shares and have proceeds sent to their Cash Balance.
• Code should be commented as required.
Submission
• You will be required to archive (zip) your software solution and submit it via Canvas.
o Where work is submitted up to and including 7 days late, 10% of the total
marks available shall be deducted from the mark achieved.
o Where work is submitted up to and including 14 days late, 20% of the total
marks available shall be deducted from the mark achieved.
o Work submitted 15 days late or more shall be assigned a mark of zero.
• Ensure you include a text file which includes any usernames/passwords/PINS/SQL
queries that are required to test the application.
• Provide a copy of the database and ensure all database connections are appropriate.
Submission Details
• Project to be submitted via Canvas.
• Provide a "Readme" word document highlighting Username/Passwords and PIN numbers, all
SQL queries relating to the creation and population of the SQLite database, and any code
"commented out" for review with a brief explanation of the intended functionality attempted.
• Submission should include a relevant CSV file for testing your application.
• Project to be submitted electronically.
• All code will be analysed for plagiarism.
• Due date for this submission to be found on Canvas.
Advanced Requirements (25%):
• Integrated administration functionality allowing for CRUD operations on all customer records.
• Ability to read customer data from a CSV file and upload data from said file into the relevant
database for use within the application.
• Note: Students are expected to use their own judgment and creativity when implementing
advanced requirements. Special attention should be paid to data governance, user access roles and
database structure. Students are encouraged to attempt all requirements. Use comments to
highlight any work that, while not functional, shows an attempt made to implement a specific
requirement, highlight any commented functionality in accompanying documentation. It is
expected that your program will execute and run with no syntax errors. Any code causing errors
should be commented out and noted in documentation.
Marking
• Coding Standard and Logic (60%)
• Sophistication, Integration and Completeness (20%)
• Graphical User Interface and Usability (20%)
Criteria 1H 2H1 2H2 Pass Fail
Coding
Standard and
Logic
Code is object
oriented,
commented.
Appropriate
data types are
used. Logic is
appropriate.
Structured
exception
handling and
validation
used where
appropriate.
Efforts at object
orientation with
some minor
implementation
errors. Code
commented
infrequently.
Repetition of
code. Some
gaps in
validation and
exception
handling.
Inefficient
coding
standard and
logic. Limited
validation.
Data input
and
calculations
are hard
coded in
places. No
commenting.
Coding
standard and
logic
inadequate.
Some basic
logic errors. No
validation.
Sophistication
and
Completeness
Requirements
are met and
exceeded
with
additional
novel
functionality.
Requirements
are met. Some
additional
functionality or
utility.
Requirements
are met but
no additional
functionality .
Some gaps in
requirements
/
functionality.
Large gaps in
requirements.
Limited
functionality.
User Interface
and Usability
Appropriate
navigation
and data
display
controls. Role
based
navigation.
Application
facilitates core
functionality in
an efficient
manner.
Some
difficulties
navigating
between
screens.
Inefficient
navigation in
places.
Single view
of data.
Inefficient
use of
controls.
Poor usability
and
navigation.