Simple Design Versus Detailed Design

System function Design effective input

System processing ways Design effective output

Size and scope Design files, tables and databases

System structure Design user interface

Hardware and software Design procedure

General processing flow Design KB and inference engine

Things to be considered when attempting to model a problem

¨ Capable of solving real world application problems

¨ Meeting the requirement of real applications

¨ Easy to get information from the world

¨ Easy to exchange information between the system and the user

¨ Easy to acquire knowledge and data

The empahasis in rad is accurate and detailed planning so that the implementaiton can on smoothly unhindered by unforseen problems. The newer approaches seem to prove themselves to work so even if you are hesitant these radical new methods bring order to almost total choas.

A conceptual data model is a representation of organizational data. The purpose of a conceptual data model is to show as many rules about the meaning and inter- reladonships among data as are possible. You typically do conceptual data modeling in parallel with other requirements analysis and structuring steps during systems analysis. You collect the explanations of the business necessary for conceptual data modeling from like interviewing, questionnaires, and JAD sessions. Information-gathering methods.

Some topics in this essay:
DISADVANTAGES RAD, Developinent RAD, DATA MODELING, DFDs LDS, DETERMINING REQUIREMENTS, Typical Traditional, Study Module, Security DB/KB, Flow Diagrams, Easy Transferability, systems development, conceptual data, data model, current system, dfds lds, data flow, data flows, analysis design, ¨ easy, information systems, conceptual data model, identifying modelling documenting, consists single stage, process identifying modelling, modelling process identifying,