COMPUTER APPLICATION IN CASE TOOLS, Cheat Sheet of Computer Applications

FORM PURCHASE ONLY IM THE COLLEGE STUDENT

Typology: Cheat Sheet

2025/2026

Uploaded on 12/07/2025

pandi-raja
pandi-raja 🇮🇳

1 document

1 / 102

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
1
Unit – I
Data Modeling: Business Growth-Organisational Model-Case Study of student MIS-What
is the purpose of such Models-Understanding the business-Types of models-model
development approach-the case for structural development-advantages of using a case tool.
System analysis and design-what is DFD-General Rules for Drawing DFD-Difference
Between Logical data flow diagram and Physical data flow diagram- Software verses
Information Engineering-How case tools store information.
1. Datamodeling:
How we are modling the business
When a new bussiness comes into gain a profit
Management will take over the responsbility of desingning the detailes daily
These will be implemented qnd checked for bugs for bussiness growth
2. Bussiness growth:
2 main factors
i) manpower ii) Fund flow
There will be responsible heads in the organization
There will pass accurate information to senior
The various plans of the company can be projectd
So the fundflow will increase, the decisions are made by the organization based on the
information based by various lvels of heads
Fund flow increase the organization growth of business
The raw material suppliers will increase
Finished product also increase
Fund flow increase
Financial control increase Supplier rawmetrial Mrketting increse
Finished products increase
pf3
pf4
pf5
pf8
pf9
pfa
pfd
pfe
pff
pf12
pf13
pf14
pf15
pf16
pf17
pf18
pf19
pf1a
pf1b
pf1c
pf1d
pf1e
pf1f
pf20
pf21
pf22
pf23
pf24
pf25
pf26
pf27
pf28
pf29
pf2a
pf2b
pf2c
pf2d
pf2e
pf2f
pf30
pf31
pf32
pf33
pf34
pf35
pf36
pf37
pf38
pf39
pf3a
pf3b
pf3c
pf3d
pf3e
pf3f
pf40
pf41
pf42
pf43
pf44
pf45
pf46
pf47
pf48
pf49
pf4a
pf4b
pf4c
pf4d
pf4e
pf4f
pf50
pf51
pf52
pf53
pf54
pf55
pf56
pf57
pf58
pf59
pf5a
pf5b
pf5c
pf5d
pf5e
pf5f
pf60
pf61
pf62
pf63
pf64

Partial preview of the text

Download COMPUTER APPLICATION IN CASE TOOLS and more Cheat Sheet Computer Applications in PDF only on Docsity!

Unit – I

Data Modeling: Business Growth-Organisational Model-Case Study of student MIS-What

is the purpose of such Models-Understanding the business-Types of models-model

development approach-the case for structural development-advantages of using a case tool.

System analysis and design-what is DFD-General Rules for Drawing DFD-Difference

Between Logical data flow diagram and Physical data flow diagram- Software verses

Information Engineering-How case tools store information.

1. Datamodeling:

 How we are modling the business

 When a new bussiness comes into gain a profit

 Management will take over the responsbility of desingning the detailes daily

 These will be implemented qnd checked for bugs for bussiness growth

2. Bussiness growth:

2 main factors

i) manpower ii) Fund flow

 There will be responsible heads in the organization

 There will pass accurate information to senior

 The various plans of the company can be projectd

 So the fundflow will increase, the decisions are made by the organization based on the

information based by various lvels of heads

 Fund flow increase the organization growth of business

 The raw material suppliers will increase

 Finished product also increase

Fund flow increase

Financial control increase Supplier rawmetrial Mrketting increse

Finished products increase

3. Oraganization model

Oranization model indicates how its business runs

Model Management

Develop model strategy Maintain project model Maintain corarate model

 Model can be used to improve the way of business

 Its indicate the strength and weakness

 The weakness can be evaluated and changed to strengths

 Rules: i) shape of the object ii)Relationship between objects

4. Case study: A student MIS system

o There are a lot of computer traning instutes who take in a students. and train

them in the use of computer

o Computer training institutes will have to adverttise , when a students reads the

advertisementand join the organization students is conversion

Eg: let’s considr the cost of letter

1. Type of envelope 2. Quality of paper + weight of paper 3. Weight of the

envelope 4. Printing cost for each letter 5. Coast of postage

Disadvantage of hard coding atomic values into program

 Hardcode it become impossible to implement changes when it takes place

 A small changes is made at the atomic level it can’t be implemented in the

computer system without making changes in the source file

 IT professionals we have to try and make the applications as flexible as possible

What is CASE tool

Development of special S/W that works on micros, minis and mainframes called

Computer Aided Software Engineering

The case for structures development

 S/W development is an art and a science

 CASE technology is the automation of step-by-step methodologies

 Development from step-one planning to ongoing maintenance

Planning: Gathering information about user problems and requirements

Analysis: Determine user needs and system constraints testing, gathering functional

specification

Design: Diagrams and data flow

Implementation: Building, testing, installing and tuning S/W

Maintenance : Implementing plans, tuning, correcting and enhancing system.

Advantages of using CASE tools

 This maybe a simple diagram showing the flow of data between business

functions.

 These models help the system developer in the analysis and design activities by

displaying system components graphically at various levels.

The methodology link

1. Before 1970’s applications grew more complex and more people got involved

int the development and maintenance

2. CASE tools are used to support modeling activities

3. CASE tools can automate the generation of the physical database

4. CASE tool can also produce program code

5. This reduce time and optimized code

6. CASE tools provide additional information about the objects

7. CASE tools includes diagramming logic

8. CASE tool have the capability to track additional information about the objects.

9. Logical errors in system design are trapped and corrected immediately

10. CASE tools embedded with rules.

Casing the market:

 CASE tools has one of the highest growth rate many companies buying multiple

copies of tools

 CASE will most likely occur when developers and managers

 CASE tools are micro computer based powerful graphics to enhance the user

interface

System analysis and design:

Introduction:

 A computer can work on a task at very high speed and with great accuracy when

compared to a human being

 Analysis system required we can understand how the system function and what

are its inputs what kind of processing takes place and what kind of output is

produced.

 Analysis of the manual system helps him design a set of instructions that will

tell the computer what to do

 It is essentially systems analysis prior design, most computer system will not

produce to kind of output that we require

 System analysis and design in the early days was done based on the

programmers personal skills this varied person to person

 This method was very personalized this method had several clearly

understandable rules

 Its creates the structured diagrams and charts

Structured system analysis and design

1. Structured methodologies help to standardize and systematize s/w development

and maintenance

2. Strutting produces clear fast- to-write and easy- to- maintain programs

3. At that time data flow diagrams were drawn using plastic templates as a

diagramming assistance

4. Biggest drawback of structured methodologies their diagramming techniques

are manual, slow and tedious

5. CASE tool new structured methodologies by providing automated graphics

facilities for producing charts and diagram screen and report painters, data dictionaries

extensive reporting facilities analysis and checking tools documentation generators

and code generators.

6. Diagrams checks the logical error and point these out to the user of the tool

7. Rules were embedded into the tools this needed the DFD drawn to become very

accurate and to be used guiding to actual code writing

8. Diagramming tool and the hole S/W package behaved as a tool box

9. A toolbox with a set of sophisticated tools which had a good deal of intelligence

build

10. The entire toolbox to be called Computer Aided Systems Engineering

The people who pioneered SSAD

 Perter Yourdon, Gane sarson, Jackson martinDemarco,Mellor,Hately,Ward

2 methods used SSAD very popular

i) Peter yourdon’s methods,Chris Gane and Trish Sarson’s methods

Planning: Gathering information about user problems and requirements setting

goals

Analysis: Determining the design for a selected solution,including diagrams and

dataflow

Design: Detailing the design for a selected colution, including diagrams and data

flow

1. Any DFD leaving a process must be based on data that are input to the process

2. All DFD are named their name reflects the data flowing between to perform the

process should be an input to the process

3. Only data needed to perform the process should be an input to the process

4. Be independent of any other process in the system it should depend upon it

own input and output

5. Process are always running they do not start or stop process is always ready to

perform work

6. Output of the process can take any of the following forms

a) An input DFD with information added by the process

b) A response or change of data from dollarsto profit

c) Change of status

d) Change of content

e) Change of organization

Difference between logical DFD and Physical DFD

Logical Physical

Logical DFD are drawn keeping Physical DFD drawn with

in mind how the work is going to be done reference to who is goging to

do the work

Mainly focus on the process which will

Do the work Physical DFD has to replac the

process in the logical DFD by

the logical DFD

by the people who are doing

the process

The Physical DFD bring the human being in picture

designer is completely satisfied that the DFD

is correct and that code written based not the DFD wil work without logival

errors Intraction between the

human being of thes/w, data

entry screens are necessary

Software versus information engineering:

 Logical program design is separate from physical design

 s/w engineering supports data flow , tree structured and procedural logic

diagrams and screen report

 diagram include those showing entity relationship data structures,

hierarchical tree-structured decomposition, data flow dependency,

screen and report layouts and detailed program logic

How case store information

Any application will undergo an initial stage of system analysis

and design

Application stored in case

App1 App2 APP n

For any new application that is created in a case tool a sub-directory has to be

created for it this subdirectory will contain all the information that is related to

that application directory will act like a dictionary for application designer.

With in the CASE tool there is a centralized storage location this is termed as a

data dictionary

Data dictionary also track the various components of the model

It capable of displaying the graphic files as well as the textual files

Data object of the model can be classified in ten categories

1. Screens 2. Fields 3. Records 4.Diagram 5. Processes 6. Repositories’ 7.

Connectors 8.Symbols 9.Plain objects 10. Reserved object

The data dictionary also stores information of the data objects related to

their attributes data structures data elements

Data dictionary split into two parts

Definition Diagrams

Data dictionary

Case study of payroll system

3. Presentation diagram for payroll system Dealing with all types of engineering material the organization, the payroll system is computerized successfully the strength gained from this convince you are supposed to learn the current manual system and change it to new computerized system

  1. learn how the current manual system works
  2. Meet the key personnel of the organization
  3. conceptualize in diagrams
  4. go back and talk
  5. Draw your data flow diagrams
  6. Construct the table structure
  7. Getting programming done
  8. Implement the new system
  9. Check that it functions properly
  10. If any flaws found then go back to step 1
  11. Makes a smooth transfer from the manual to the computer system This presentation will not include the following
  1. Hardware and software environment
  2. Details and bottleneck of the current manual system The environmental model This is an over view of the proposed system it concentration what has to be done rather than how is to done. The various heads are
  3. an event list
  4. functional decomposition diagram
  5. context diagram
  6. presentation diagram
  7. a statement of purpose **The event list This is required so that you can assure your client that you have understand his current manual system fully.
  1. Schematics of the model: Main menu** Master menu Pls Loan Govt Exit me no ____ main menu transaction No days

Exit menu_______ main menu Report menu Payslip Exit Utilities mnu Backup Passwd Exit Exit menu FORMS: 1.data type 2. Data length To enable the programmer to do this the user data is stored in a temporary pool this temporary pool is called FORM This FORM or screen helps an analyst in 2 ways

  1. A human being is a person who is always reluctant to change to increase the accepatability of te new system the analyst can design forms that looks exactly
  2. The problem of firing complex validationsion the user data can be solved by using fors as the temporary pool to store data the valid data then can be picked up form the form and can be transferred to the table Displaying of the forms menus 1.creating fields on the form2. Positioning fields on the forms 3. Choosing the acceptable default values for the field. 4. Chaining of screen by using fields on the form 5. Defining field macro for the field 6. Providing help on field. 7. Providing help on the form SCREENS: 1.main menu screen 2. Master menu screen 3.pls screen 4.loan screen 5. Govt screen 6.Transaction menu screen. 7.do days screens 8. Exit menu screen 9. Report menu screen 10. Pay slip screen. 11. Utilities menu screen 12. Backup screen. 13. Passwd screen. CASE tools also provide an option to design all these data entry screens The total no. of screens that are to be designed can be determined from the diagrams This will also make the documentation for the system Thus documentation of the system cionsist of the dat aflow diagram the hierarchy of th e dat a diagrams the system Thus documentation of the system consist of the function of the current manual system the data flow diagram the hierarchy of the system the presentation diagrams the screen current functioning of the system **MENU SCREEN1.
  3. Main menu screen
  4. Master menu screen
  5. Pls screen
  6. Loan screen
  7. Govt screen
  8. Transaction menu screen
  9. No_days screen**

Date of joining: The organization: Married: No.of dependents: Employeea are graded at different levels in an organization because of this you always have a hierarchy in an organizations Repots: There are document like the salary register report and the salary summary report that has to be generated every 3 month once every quarter the salary register report is forwarded to the human resource department while the salary summary report goes to the financial accounting department which use it for reporting the profit and loss statement Utilitilities Field Value clear to clear library B bachup y payroll ubl p passwd y payroll ubl E main menuy y payroll ubl Please enter the following Backup Passwd Exit Installation OF uBridge & Synthesis How to use the tools in uBridge Synthesis for case An individual case tool automates one small focused step in the life cycle process. Individual tools fall into these general catogiries Diagramming tools to pictorially reprecent system specification Screen and report painters fort creating system specifications and for simple prototyping Dictionaries information management systems and fecilities to store report and query technical and project management system information. Specification checking tools to ditect incomplete , syntactically incorrect ,and inconsistent system specification Code generators to be able to generate executable code from pictorial system specifications Documentation generators to produce technical and user documentation required by structured Methodologies.Prototyping tools help determine system requirements and predict perrformence beforehand Screen dialog and navigation with entry and edits can be simulated with or without compilers .Sorce code for record file screen and report discrptions can be generated automatically .Also essential are executable specification languages. These are the most sophisticated prototypin Master transaction utilities reports exit Backup PASSWORD EXIT CHOICE

tools which involved specifying system requirements and executing specifications interactively to refibnd correct and ensure completeness of the system to meet user requirements.CASE tools essentially consist ofDiagramming section Prototyping section Code generation sectionInstallisation of ubridge synthesisHardware requirements To instale CASE toolIBM PC/XT or true compatible under ms-DOS ver 3.0 One floppy drive (5 ¼”,3 ½”)640 KB of RAMHard disk with at least 3 MB of free spaceInstallation Create a dictionary,say synth C:>md synth Change ypour directory to yhis directory C:>cd synth Insert the first floppy in the drive and copy it in the synth directory in this way copy all the ten floppys in the synth directory C:>copy a:. c:\synth C:\synth>INSTSYN The installation program instsyn will operate for a while and give the message “synthesis installation complete” Computerized software is generally divided into two classes Systems software Commertial application software Each class of software is developed in computer programming languages having its own vocabulary,syntax and symantics A great deal of preplanig has to go into the creation of such software questions arise Did we clearly specify all our requirements? Did the system specialist really understand what is required? How reliable will the software developed be? Will it be developed ontime? Will the software be easy to maintain? Will the software be clearly documented? Will we require special staff to run and maintain the software? Software is an abstract rather than a physical entity .this distinguishes it from most other engineering product. software once designed has no continuous manufacturing phase. It needs to be maintained. Software engineering is intended to assist the development of good quality software with in the buget and time scale constrains today with the use of case tools all areas have been largely automated. Computer aided software engeeniering(CASE) Computer aided software engeeniering(CASE) is the latest technology which is healpin to produce very relaiyable software case tools automate activities in all stages of the software devolepment life cycle. They are Requirement definition Design Codeing Development Testing Implementation Documentation The case tools themselves are pices of software either devolpoed in house or produced by third party software houses and sold as property products once such product that helps automate most stages of the software development life cycle is uBridge Synthesis.

DEF FONT

Seveseveral type of fonts are used in ubridge while diagramming ,we have to sset up a DEFAULT font to load when ubridge loads up,this default is defined in this window MAX FONT We can define the memory size used by ubridge to load fonts. large the memory size greater will be the speed with whichubridge switches between fonts. LABEL IMMEDIATE While creating an OBJECT in window ubridge will ask you to name & lable then as soon as they are created if the immediate switch is on this is a default seting thic can be changed for each window SYSTEM LABLE When you create a lable on a screen ubridge will always mark the label area carefully,making it smaller then the “hot area” if this parameter is given as no then ubridge ask you to explicitly mark the area of the lable CONNECTOR COLOUR We can select one of the sixteen colors for the connection between the objects on screen The object/text set-up window: THE OBJECT SCALE FACTOR Object sizes in a window can can be scaled from 1to 7 with 4 being default size TEXT SIZE: Similerr to object text can also be scaled 1 to 5 with default being 3 OBJECT COLOUR Object colour can be chosen from a palette of 16 colors TEXT COLOUR Text colour can be chosen from a palette of 16 colors After having setup ubridge the next step is to tell the SYSMAN who will be the user of ubridge This is done by entering the ASSIGN sub-menu system This sub menu is brifureated in two part : A) Where you can identify a user to the system When you enter the user assignment screen you can add ,modify ,delete a user on the system save and obtain help for the screen you are currently on B) Where you identify a project and assign a user to a project When you enter the project assignment screen you can add ,modify ,delete on your project RELEASE: Prevent any changes to the project data dictionary REACTIVATE : Aloes further changes to a project after it has been RELEASED HOUSE KEEPING

On entering to a house keeping menu choice allows a user to backup and restore file from the current sub directory concerned This means we are now ready to begin to use ubridge capabilities for prototyping and testig to our advantage The ubridge page There is a visible area on the screenon the screen on on which you work which is much less then the actual page length The maximum number of rows are 72 The maximum number of columns are 256 These have default setting that load up when ubridge loads up but via SYSTEM MNGEMENT INTERFACE CHANGE SCREEN SIZE Unit – III Introduction to Ubridge: Introduction - Main flow of the system prototyping your Report- Introducing the Novice Model of the Operation.Introducing Synthesis - Synthesis basic – Synthesis

- Menu Drawingthe screen-Requirement Definition-Diagram-Data Dictionary-Document-Synthesis MainAdministration - Synthesis reference - importing and exporting screen. INTRODUCING TO UBRIDGE INTRODUCTION CASE TOOLS must have an option so that the designing of the screen can be achived to do this ubridge synthesis uses its first menu screenNow using this menu we must be able to draw our screens.it must let us manipulate the assenthetics of the form.The form that are designed for the payroll project suggest that we must be able to

  1. draw boxes or lines
  2. define simple field and table field
  3. attach text to the form
  4. attach default value for a field
  5. stich filed validation to a field
  6. chain different screen together
  7. do cursor controlling
  8. define the screen logic To get started with ubridge synthesis we need to first get into the tools by keying in
  1. data manager PROTOTYPING YOUR REPORTS: We can plan a report as much as 256 columns wide wee can paint a report using the screen paint option and acctualy define its contents. A complete report model can be created and chained to the model system accessible via the report option of the main menu to provide realityof the model flow INTRODUCING THE NOVICE MODE OF OPERATION: The novice mode makes the various activities such as painting of screens defining of data chaining of screens etc.. of ubridge. This mode thus makes a model of your system with out you having to paint screens define data chain screens together or any othere activity that is normally required to make such a model.

Introducing SYNTHESIS

After knowing what is uBridge, and how we can configure the system using SYMAN let's get to known SYNTHESIS, the systems analyis and design work bench SYNTHESIS Basics Starting SYNTHESIS You can run SYNTHESIS from any directory or sub-directory with the command: SYNTH (ENTER) Adjusting to different Monitor types : SYNTHESIS assumes a color monitor when you run it using the command SYNTH(Enter) Thus if you have a monochrome monitor the resultant shades may not have adequate contrast you can override the color usage by keying in '/B' after SYNTH: SYNTH/B(Enter) The SYNTHESIS Main Menu Once you logged in through the login window of SYNTHESIS the main menu of SYNTHESIS will be displayed The SYNTHESIS Main Menu has the following options: Requirement : Paint your screen and report layouts the way you see them. Describe data that you want your system to handle.Build your vie of system. Diagram : Gives you choice of nine standard Diagramming techniques.

Data Dictionary: Provides a direct data dictionary interface. Document : Build a document based on the data dictionary.this document could be a system document, a user manual or a plain proposal Administrator : Use the administrator to set up colors, select a printer and access DOS. Quit :At theend of a session, this option will take you back to the DOS prompt. Drawing the screens REQUIREMENTS DEFINTION This option allows yor to make a requirement definition of the system analysis abs design When You choose this option,SYNTHESIS actually calls UBridge 2.0+(which is the precursor to SYNTHESIS) This is a requirement definition toll ehich assists you in defining your system requirements. At the end of the requiremment definition, ou have a modle of your system which shows you exactly what you new system is going to do. (B) Diagram: The diagramming menu has the options as below: Draw : To actually position and draw an object and to connect the objects. Label :To place a short textual description on an object or connector. Describe :To give more details about the object Tolls : To make changes in your diagram like moving ,cut & Paste zooming in and out, exploding and imploding process. Control :Display a control panel to change the font,size &color setting. Window :Activates the window manager.its allow you to create .move remove & resize the window. Administrator : Lets you get ,save load and print Diagrams Quit: : used to exit from the diagramming menu. (C) DATA-DICTONARY: