16.08.2013 Views

system design - DSpace at CUSAT - Cochin University of Science ...

system design - DSpace at CUSAT - Cochin University of Science ...

system design - DSpace at CUSAT - Cochin University of Science ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

PROJECT REPORT Callipers – The Training Manager<br />

to assess his/her trainer. All these details can be viewed and edited by the<br />

administr<strong>at</strong>or.<br />

5.5 Logical Level System Design<br />

Logical <strong>design</strong> covers the following:<br />

Reviews the current physical <strong>system</strong>-its d<strong>at</strong>aflow, file content etc.<br />

Prepares input specific<strong>at</strong>ions-form<strong>at</strong>, content and most <strong>of</strong> the input<br />

functions. This includes determining the flow <strong>of</strong> the document form input<br />

d<strong>at</strong>a source to the actual input loc<strong>at</strong>ions.<br />

Prepares edit, security and control specific<strong>at</strong>ions. This includes<br />

specifying the rules for edit correction, back up procedures and the controls<br />

th<strong>at</strong> ensure processing and file integrity.<br />

Specifies the implement<strong>at</strong>ion plan.<br />

Prepares a logical <strong>design</strong> walkthrough to the inform<strong>at</strong>ion flow, output,<br />

Input controls and implement<strong>at</strong>ion plan.<br />

Reviews benefits, cost, target d<strong>at</strong>es and <strong>system</strong> constraints.<br />

5.6 Physical Level System Design<br />

An applic<strong>at</strong>ion <strong>system</strong> physical <strong>design</strong> approach can be easily<br />

understood by users and easily used by programmer analysts during<br />

implement<strong>at</strong>ion. Both overall <strong>system</strong>s level and program level physical <strong>design</strong>s<br />

are normally cre<strong>at</strong>ed from D<strong>at</strong>a Flow Diagram (DFD) and Entity Rel<strong>at</strong>ionship<br />

Diagram (ERD) based logical <strong>design</strong>s, by separ<strong>at</strong>ing processes and d<strong>at</strong>a stores by<br />

time (such as daily vs. monthly, day vs. night), place (client or server, centralized<br />

vs. distributed), online vs. b<strong>at</strong>ch, and manual vs. autom<strong>at</strong>ed. Using a physical<br />

<strong>design</strong> we are able to easily cre<strong>at</strong>e detailed program level <strong>design</strong>s needed to<br />

implement the <strong>system</strong>. The key point in the methodology is th<strong>at</strong> users can<br />

- 34 -

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!