1 / 4

Conceptual Design versus Logical Design

Conceptual Design versus Logical Design . Conceptual Data Design . Prepared at beginning of project High level view of how the client sees the data Top down process Not concerned with details Normally prepared using brainstorming approach

orsin
Télécharger la présentation

Conceptual Design versus Logical Design

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Conceptual Design versus Logical Design

  2. Conceptual Data Design • Prepared at beginning of project • High level view of how the client sees the data • Top down process • Not concerned with details • Normally prepared using brainstorming approach • Identification of Entities, Attributes and Relationships represented using Entity Relationship Diagram • ERD is constantly modified as project progresses and more is learnt about application’s data

  3. Logical Data Design • Detailed representation of application’s data • Bottom-up process • Purpose of logical data design is to represent application data in the form of related 2-dimensional relations which will correspond to the tables created in a relational database • Details obtained by analysing representative samples of application’s user views or prototyping user views

  4. User View • A user view is a view of the data presented by the application to the user, i.e. a set of requirements that are necessary to support the operations of a particular user • User views may include: input screen, output screen, input form, detailed report, summary report • User view should present sample data • User view may be either a prototype or an actual sample • Should collect a representative sample of user views from different areas in the application • Technique of normalization is applied to each user view to identify relations (i.e. tables)

More Related