1.a) DATA FLOW DIAGRAM
Data flow diagrams illustrate how data is processed by a system in terms of inputs and outputs.Data flow diagram are used widely for modeling the requirements.the DFD is also known as a data flow graph or a bubble chart. Data Flow Diagram Notation
We can use two different types of notations on our data flow diagrams: Yourdon & Coad or Gane & Sarson. Process Notations
A process transforms incoming data flow into outgoing data flow.
Yourdon and Coad Process Notations
Gane and Sarson Process Notation
Datastores are repositories of data in the system. They are sometimes also referred to as files.
Yourdon and Coad Datastore Notations
Gane and Sarson Datastore Notations
Dataflows are pipelines through which packets of information flow. Label the arrows with the name of the data that moves through it.
4)External Entity Notations
External entities are objects outside the system, with which the system communicates. External entities are sources and destinations of the system's inputs and outputs.
1.b) ENTITY RELATIONSHIP DIAGRAM
Entity–relationship model (ER model) in software engineering is an abstract way to describe a database. This article refers to the techniques proposed in Peter Chen's 1976 paper.An ER model is an abstract way to describe a database. There are three basic elements in ER models:
Entities are the "things" about which we seek information. Attributes are the data we collect about the entities.
Relationships provide the structure needed to draw information from multiple entities.
Symbols Used In ERD:
1.c) OBJECT ORIENTED DESIGN
Object-oriented design is the process of planning a system of interacting objects for the purpose of solving a software problem. It is one approach to software design. An object contains encapsulated data and procedures grouped together to represent an entity. The 'object interface', how the object can be interacted with, is also defined. An object-oriented program is described by the interaction of these objects. Object-oriented design is the discipline of defining the objects and their interactions to solve a problem that was identified and documented during object-oriented analysis.
2. Automated Teller Machine (ATM)
A software to be developed for automated transactions. The system should be standalone in nature. It should be designed to provide functionality as explained:
Withdrawl the amount.
Cash take in any formet either 100 or 500.
More security provide.
Slip of transaction.
2.b)Data Flow Diagram:
2.b.i) CONTEXT LEVEL DIAGRAM:
2.b.ii)ONE LEVEL DIAGRAM:
2 c) USE CASE DIAGRAM
A use case diagram at its simplest is a representation of a user's interaction with the system and depicting the specifications of a use case. A use case diagram can portray the different types of users of a system and the various ways that they interact with the system.
Withdrawl use case discription:
1.Display a menu for transactions including withdraw cash with instructions to insert bankcard to begin the process. 2.Customer inserts the bankcard and a system verifies that the card is valid. 3.Systems prompt the customer to choose a language.
4.Customer chooses language.
5.System prompts the customer for pin number.
6.Customer enters pin number and submits data.
7.System verifies pin and displays an option for “Cash Withdrawal.” 8.Customer selects ”Cash Withdrawal.”
9.System prompts customer for “Amount to Withdraw.”
10.Customer enters amount and submits data.