UML package diagram for Bank account

This bank account UML package diagram was redesigned from the Wikimedia Commons file: Package diagram1.jpg.
[commons.wikimedia.org/ wiki/ File:Package_ diagram1.jpg]
This file is licensed under the Creative Commons Attribution-Share Alike 3.0 Unported license. [creativecommons.org/ licenses/ by-sa/ 3.0/ deed.en]
"A very important concept in object-oriented design, inheritance, refers to the ability of one class (child class) to inherit the identical functionality of another class (super class), and then add new functionality of its own. (In a very non-technical sense, imagine that I inherited my mother's general musical abilities, but in my family I'm the only one who plays electric guitar.) To model inheritance on a class diagram, a solid line is drawn from the child class (the class inheriting the behavior) with a closed, unfilled arrowhead (or triangle) pointing to the super class. Consider types of bank accounts: Figure 4 shows how both CheckingAccount and SavingsAccount classes inherit from the BankAccount class.
Figure 4: Inheritance is indicated by a solid line with a closed, unfilled arrowhead pointing at the super class." [ibm.com/ developerworks/ rational/ library/ content/ RationalEdge/ sep04/ bell/ index.html]
This bank account UML package diagram example was created using the ConceptDraw PRO diagramming and vector drawing software extended with the ATM UML Diagrams solution from the Software Development area of ConceptDraw Solution Park.

This example of automated payroll management system UML activity diagram was created on the base of figure on the webpage "Automated payroll management system" from ethelmandane.wikispaces.com.
"In the Philippines and in other foreign countries the government has a trend to embrace automation for process efficiency. One of the processes that are being automated is the payroll process. Payroll is the total amount required to pay workers and employees during a week, month or other period.
One of the government offices that desires to automate their payroll system is the NSO Camarines Sur which is located 2nd Floor MMCN Building, Panganiban Avenue, Naga City. The National Statistics Office (NSO) envisions to be recognized as a world-class provider of statistical and civil registration products and services and lives with its mission to produces and provides quality statistical and civil registration products and services. ...
The project seeks to create an Information System Plan for an Automated Payroll Management System. ...
The creation of the Information System Plan will benefit the accounting section of the organization. Specifically it is significant to:
1. Administrative Assistants. It will help to lessen time and effort in preparing and computing the salary of the employee.
2. NSO. It will help the organization to be more productive and efficient."
[ethelmandane.wikispaces.com/ ]
This file is licensed under a Creative Commons Attribution Share-Alike 3.0 License. [creativecommons.org/ licenses/ by-sa/ 3.0/ ]
This UML activity diagram example modeling the automated payroll management system using automated teller machine (ATM) was created using the ConceptDraw PRO diagramming and vector drawing software extended with the ATM UML Diagrams solution from the Software Development area of ConceptDraw Solution Park.

This example was redesigned from the Wikipedia file: LastResortHotel BookRoom Process.png. [en.wikipedia.org/ wiki/ File:LastResortHotel_ BookRoom_ Process.png]
This file is licensed under the Creative Commons Attribution-ShareAlike 3.0 License. [creativecommons.org/ licenses/ by-sa/ 3.0/ ]
"Event partitioning is an easy-to-apply systems analysis technique that helps the analyst organize requirements for large systems into a collection of smaller, simpler, minimally-connected, easier-to-understand ‘mini systems’ / use cases. ...
Defining requirements.
Single process in a fictitious hotel using data flow diagram notation.
Single use case in a fictitious hotel using use case diagram notation.
This approach helps the analyst to decompose the system into ‘mentally bite-sized’ mini-systems using events that require a planned response. The level of detail of each response is at the level of ‘primary use cases’. Each planned response may be modelled using DFD notation or as a single use case using use case diagram notation.
The basic flow within a process or use case can usually be described in a relatively small number of steps, often fewer than twenty or thirty, possibly using something like ‘structured English’. Ideally, all of the steps would be visible all at once (often a page or less). The intention is to reduce one of the risks associated with short-term memory, namely, forgetting what is not immediately visible (‘out of sight, out of mind’). ...
Single process in a fictitious hotel using data flow diagram notation." [Event partitioning. Wikipedia]
The DFD example "Last resort hotel book room process" was created using the ConceptDraw PRO diagramming and vector drawing software extended with the Data Flow Diagrams solution from the Software Development area of ConceptDraw Solution Park.