Goal : A high-level overview of the project or landscape at level 1. This shows in 1 diagram what the project or concern is about. The details come in the underlying views. Not required : Depending on the complexity and size, this view is necessary in a complex architecture.
Naming Conventions Usage: Singular noun. For example: Search query, Search result Logical name. Avoid technical names such as file, database.
Naming Conventions Usage: Noun (name of the package). For example: MsWord, Autonomy Federator
Naming Conventions Usage: Singular noun. For example: Invoice, policy, Fault report Logical name. Avoid technical names.
Naming Conventions Usage: Noun. For example: Application Server, machine name.
Naming Conventions Usage: Noun. For example: Sybase Open Client, CPS, GFX, MQ, EWMS, XML.
Naming Conventions Usage: Noun. Example: Search Gui, VM—search service Web service.
Naming Conventions Usage: Noun. For example: Counter, telephone, e-mail, form and internet.
Naming conventions Usage: Verb in the imperative mood followed by a noun (singular), for example: Check order, make quotation, Report malfunction. Avoid Manage, process, register ……
Naming Conventions Usage: verb. Example: Billing, Search, Indexing.
Naming Conventions Usage: Noun. For example: Collaboration, Message Exchange Extra: Name from the PDC (ing form).
Naming Conventions Usage: noun. For example, Backup and Restore, Printing, Scanning, Searching (ing form).
Naming Conventions Usage: Noun in the ing form. For example: Transaction processing, Indexing.
Naming Conventions Usage: verb. Example: Support, Manage Service.
Naming Conventions Usage: Noun in the ing form. For example: Messaging, Broadcasting.
Naming conventions: Usage Noun e.g. Government employee, Company, Citizen. Avoid User, system.
Usage: noun based on the organization naming the organization of tables in databases, XML files, etc.