Difference between revisions of "Information System Architecture For AccountIT"
From AccountIT
m (Pierre moved page AccountIT Information System Architecture to Information System Architecture For AccountIT without leaving a redirect) |
|||
(4 intermediate revisions by one user not shown) | |||
Line 1: | Line 1: | ||
+ | =Introduction= | ||
+ | From the [[Use Case Diagram For AccountIT|Use Case Diagram]] it is seen that the AccountIT system has two primary functions, which requires the following data stores: | ||
+ | * Users - records the users who are to access AccountIT. | ||
+ | * Books - records the accounts, which are the core of the AccountIT system | ||
+ | * Roles and Permissions - records what roles a user has and the associated AccountIT functionality the user has permissions to. | ||
+ | * Audit Trail - records what activity a user has performed at a given point in time. | ||
− | + | =Data models= | |
− | + | *[[Conceptual Data Model For AccountIT|Conceptual Data Model]] | |
− | * | + | *[[Physical Data Model For AccountIT|Physical Data Model]] |
− | + | ||
− | * Physical | + | |
− | + | ||
− | + | ||
[[Category:AccountIT]] | [[Category:AccountIT]] |
Latest revision as of 18:39, 27 September 2014
Introduction
From the Use Case Diagram it is seen that the AccountIT system has two primary functions, which requires the following data stores:
- Users - records the users who are to access AccountIT.
- Books - records the accounts, which are the core of the AccountIT system
- Roles and Permissions - records what roles a user has and the associated AccountIT functionality the user has permissions to.
- Audit Trail - records what activity a user has performed at a given point in time.