Object and Data Modelling

Running head: OBJECT AND DATA MODELLING
Object and Data Modelling
Name of Student
Name of the University
Author Note

OBJECT AND DATA MODELLING
Table of Contents
1. Identify and briefly describe the main functional and non-functional requirements...................3
Functional Requirement:.............................................................................................................3
Non-functional requirements:......................................................................................................4
2. Draw a use case model for the information system.....................................................................5
Use Case Model Diagram............................................................................................................5
Use case Description....................................................................................................................6
Fully developed use case:............................................................................................................7
3. Draw a UML domain model class diagram for all systems.........................................................8
Class Diagram..............................................................................................................................8
Assumptions................................................................................................................................8
4. Specific Tasks Required for Each Design Activities...................................................................9
Describing the environment.........................................................................................................9
Designing application components............................................................................................10
User interfaces...........................................................................................................................10
The database..............................................................................................................................10
Bibliography..................................................................................................................................11

OBJECT AND DATA MODELLING
1. Identify and briefly describe the main functional and non-functional requirements
Functional Requirement:
The main functional requirements of the ATM are described below:
System requirement: One of the major requirement will be establishing of parameters within the
system for data storage and setting that can be used in the execution process.
No activity condition: In case, there is no valid cash card; the display will flash the in initial
display.
Cashless ATM: In the deemed scenario, the acceptance of the card should be denied while the
screen flashes an error message.
Authorization: Another notable requirement suggests that after the cash card mode is entered, a
pin acceptance should be done so that the ATM can process the validity of the cash card.
Card acceptance: Readability of the bank code and serial number to ensure the validity of the
card after which the card can be accepted by the ATM. In case, the card is not read within a
timeframe of 5 seconds, the screen will flash a timeout error notification.
Serial Number reading: The code along with the recorded serial number should be registered
with the system. The serial number on the card should be read efficiently by the machine.
Pin Request: On successful recognition of the cash card. A screen will be flashed asking for the
card’s pin and only after validation of the pin, the system can be accessed.
Processing of Pin: Post processing of the entered pin, the screen will display a dialogue box
citing whether the input response is positive or negative. If the response is identified negative,
the user will be offered three chances to re-enter their pin after which the system will block the
user by capturing the card.
Transaction Type: On validation of the pin the screen will display message after which the user
can proceed with the transaction that will include options such as withdraw, deposit, transactions
and others.

OBJECT AND DATA MODELLING
Post transaction: Post-transaction, the system will enquiry about the further step that will
include continuation of the process or not. Additionally, printing of the receipt will also be
enquired after which the process will be complete.
Non-functional requirements:
The non-functional requirements of the ATM system are described below:
 Scalability: The ATM should offer scalability that is it should be capable of withstanding harsh
situations such as excessive load that can be resulted from increased number of users and
provide cash to the users as long as it has ample cash.
 Flexibility: Another notable requirement of the ATM should be flexibility. The system should not
be limited to withdrawal of the cash only; it should also offer options like, checking of last
transactions, cash deposit, change of pin, applying for the bank account and similar others.
 UI ease: User Interface (UI) is one of the most desirable requirement for the ATM because it
decides what comfort will the user enjoy while using the ATM. Hence, it is mandatory that the
input and dialogue box displayed on the ATM’s screen is understandable and offers ease of use.
The options should also be understandable and visible to the users.
 Usability ease: The ATM should also offer ease of usability to the users that is the actions should
be responded effectively and efficiently. A tutorial for the first time users can be added to
enhance understanding.
 Adaptability: The discussed system should also offer adaptability that is it should follow open
system that can be volatile as per the circumstances. However, the adaptability should not
compromise on the security of the system.
 Efficiency: Efficiency is one of the most required feature of the system and hence should be
cited special attention. The users should receive adequate response to the input they have given
to the system that and no option should be included in the system that is not capable of
providing appropriate response.
 Compatibility: Another notable non-functional requirement of the system is compatibility. The
discussed system should offer compatibility with the systems in existence to ensure that the
users are comfortable with the system and can easily understand the purpose of the system.
The data collected during account opening process at the banks should be applied to the
deemed system while ensuring the compatibility.
 Security: Security is the most crucial requirement of the deemed system and should be strong
enough to withstand undesired circumstances. The password protection does ensure the safety
of the system to a limit, however, to enhance it to next level the connection between the ATM
and bank (by electronics means) should be secured. Additional, appropriate care should be
given to avoid stalkers when, user is entering the pin.