itft-Detail design
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

itft-Detail design

on

  • 68 views

 

Statistics

Views

Total Views
68
Views on SlideShare
68
Embed Views
0

Actions

Likes
0
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

itft-Detail design Presentation Transcript

  • 1. Detailed Design
  • 2. Introduction • The design translates the system requirements into ways of operate them. • The design is a solution, a “ how to “ approach, compared to analysis, a “what is” orientation. • The design phase focuses on the detailed implementation of the system recommended in the feasibility study.
  • 3. Modularization • One way to plan a new system is to focus on each functional subsystem as a separate entity or application area. • Using such an approach, each application area is treated as if it were totally independent. • The modular systems approach divides each application area into a number of smaller units called modules.
  • 4. Advantages Of Modularization • speed up the systems process. • eliminates unnecessary duplication. • result in higher quality. • provides better control over the total system project. • allows flexibility as additional features may be added later. • parts of the system can be tested separately.
  • 5. limitations Of Modularization • Modular systems design is best viewed as one aspect of a broader planning issue, but it is not a required step in the design process. • changes and errors affect common modules, the negative consequences can be widespread
  • 6. Input Design • Inaccurate input data are the most common cause of error in data processing. • Errors entered by operator can be controlled by input design. • Input design is the process of converting user- originated inputs to a computer based format.
  • 7. Goal of input design • The goal of designing input data is to make data entry:- • Easy • Logical • Error free.
  • 8. Input media and devices • Keyboard • Mouse • Touch Screen • Sound and speech • Automatic data capture • Optical mark recognition (OMR) • Bar codes • Optical character recognition (OCR) • Magnetic Ink
  • 9. Data input methods • ON-LINE - User directly Enters data using screen prompts. • OFF-LINE -Forms filled by users- for example- candidates for admission to a college fill forms
  • 10. DATA OUTPUT DESIGN • Outputs present information to system users. • Outputs, the most visible component of a working information system, are the justification for the system. • During systems analysis, you defined output needs and requirements, but you didn't design those outputs.
  • 11. Output-design Objectives • Serve the intended purpose • Deliver the right quantity of output • Deliver it to the right place • Provide output on time
  • 12. Outputs Reports • Detailed Reports: • Present information with little or no filtering or restrictions. • Some detailed reports are historical in nature. • Exception Reports: • Filter data before it is presented to the manager as information. • Exception reports only report exceptions to some condition or standard.
  • 13. Types of Outputs • Internal outputs It stay inside the system to support the system's users and managers • External outputs It leave the system to trigger actions on the part of their recipients or confirm actions to their recipients
  • 14. Output Media • Paper • Screen • Microfilm • Video/Audio • CDROM, DVD • Other electronic media
  • 15. Output Formats • Tabular output • Zoned output • Graphic output • Narrative output