Case Tools 1

CASE Tools Concepts and Its
Applications
CASE Tools Concepts and Its Applications
• Data Modeling
• Business Growth
• Case study: Student M.I.S
• What is the purpose of such models?
• Types of Models
• Advantages of using a CASE TOOL
• Data Modeling: Business Growth-Organizational 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.
 Data modeling is the process of documenting a complex
software system design as an easily understood diagram,
using text and symbols to represent the way data needs to
flow.
 The diagram can be used to ensure efficient use of data, as
a blueprint for the construction of new software or for re-
engineering.
 Authority is handed to people, areas of responsibility and
accountability are marked out and business transactions
are processed to bring in profits.
 When a new business comes into existence, the top
management will take over the responsibility of designing
the detailed daily, hourly schedule.
 These will be implemented and checked for bugs.
• CASE stands for Computer Aided Software Engineering. It
means, development and maintenance of software projects
with help of various automated software tools.
• CASE Tools
• CASE tools are set of software application programs, which
are used to automate SDLC activities. CASE tools are used by
software project managers, analysts and engineers to
develop software system.
• CASE tools are there to simplify various stages of Software
Development Life Cycle such as Analysis tools, Design tools,
Project management tools, Database Management tools,
Documentation tools are to name a few.
• Use of CASE tools accelerates the development of project to
produce desired result and helps to uncover flaws before
• Diagram tools
• Used to represent system components, data and control flow among
various software components and system structure in a graphical form.
• Flow Chart Maker tool for creating state-of-the-art flowcharts.
• Process Modeling Tools
• Process modeling is a method to create software process model, which is
used to develop the software.
• Process modeling tools help the managers to choose a process model or
modify it as per the requirement of software product.
• For example, EPF Composer
• Project Management Tools
• Used for project planning, cost and effort estimation, project scheduling
and resource planning.
• Managers have to strictly comply project execution with every mentioned
step in software project management.
• Project management tools help in storing and sharing project information
in real-time throughout the organization.
• Documentation Tools
• Documentation in a software project starts prior to the software process,
goes throughout all phases of SDLC and after the completion of the project.
• Documentation tools generate documents for technical users and end users.
Technical users are mostly in-house professionals of the development team
who refer to system manual, reference manual, training manual, installation
manuals etc. The end user documents describe the functioning and how-to
of the system such as user manual. For example, Doxygen, DrExplain, Adobe
RoboHelp for documentation.
• Analysis Tools
• These tools help to gather requirements, automatically check for any
inconsistency, inaccuracy in the diagrams, data redundancies or erroneous
omissions. For example, Accept 360, Accompa, Case Complete for
requirement analysis, Visible Analyst for total analysis.
• Design Tools
• These tools help software designers to design the block structure of the
software, which may further be broken down in smaller modules using
refinement techniques. These tools provides detailing of each module and
• Configuration Management Tools
• An instance of software is released under one version. Configuration
Management tools deal with
• Version and revision management
• Baseline configuration management
• Change control management
• CASE tools help in this by automatic tracking, version management and release
management. For example, Fossil, Git.
• Change Control Tools
• These tools are considered as a part of configuration management tools. They
deal with changes made to the software after its baseline is fixed or when the
software is first released. CASE tools automate change tracking, file
management, code management and more. It also helps in enforcing change
policy of the organization.
• Programming Tools
• These tools consist of programming environments like IDE (Integrated
Development Environment), in-built modules library and simulation tools. These
tools provide comprehensive aid in building software product and include
• Prototyping Tools
• Software prototype is simulated version of the intended software product.
Prototype provides initial look and feel of the product and simulates few aspect
of actual product.
• Prototyping CASE tools essentially come with graphical libraries. They can
create hardware independent user interfaces and design. These tools help us to
build rapid prototypes based on existing information. In addition, they provide
simulation of software prototype. For example, Serena prototype composer,
Mockup Builder.
• Web Development Tools
• These tools assist in designing web pages with all allied elements like forms,
text, script, graphic and so on. Web tools also provide live preview of what is
being developed and how will it look after completion. For example, Fontello,
Adobe Edge Inspect, Foundation 3, Brackets.
• Quality Assurance Tools
• Quality assurance in a software organization is monitoring the engineering
process and methods adopted to develop the software product in order to
ensure conformance of quality as per organization standards. QA tools consist
The two main factors that result in the growth of a
business are:
• Man power
• Fund flow
Man power:
• The person who delegates the line of authority will
have to impose various checks and controls on the
method used for information gathering.
Fund flow:
• Fund flow in an organization will increases with the
growth of business.
• This could mean that the suppliers, who are
supplying raw material to the company, increase in
number.
• The purchasers for the finished product also
increase.
• Greater finance control has to be implemented in
the organization
Student MIS :: Cost of Conversion
• Advertisement
---Follow up cost
---Telephone cost
---Telegram cost
---Letters
---Hand delivered
---Posted
---Courier
• Seminars conducted
• Travel + Miscellaneous Expenses incurred during letter
delivered by hand
• Purpose of models
• Once a model of a business is designed, senior personnel of
the business can apply their knowledge and experience to the
model to improve the manner in which the business flows.
• This will help senior personnel to recommend ways to
improve the processes in the business.
• So from these models one could figure out the:
 Bottleneck or the loop holes in the system.
 Manpower requirements of the system.
 Financial requirement of the system.
Business models
• It represent the business itself, the information it
tracks and the way in which it will be used. These
models may include both manual and automatic
functions.
The information system models:
• It document the automation of business functions,
the actual storage of business data and the
automated ways in which the information is
accessed.
ADVANTAGES
– Improved productivity (through automation of tasks and
rapid application development.
– Document / diagram preparation and amendment is quicker
and more efficient.
– Accuracy of diagrams is improved. Diagram drawers can
ensure consistency of terminology and maintain certain
standards of documentation.
– Improved quality because CASE tools check for
completeness, consistency and contradictions.
– Prototyping is made easier, as re-design can be effected very
quickly.
– Blocks of code can be re-used. Many applications
incorporate similar functions and processes: blocks of
software can be retained in a library and used (or modified)
• Structured System Analysis and Design
– Planning
• Information gathering about use requirements and setting goals.
– Analysis
• Determining use needs and system constraints
• Testing alternative solutions
• Developing a functional specification and logical model
– Design
• Detailed solution
– Diagrams for programs, modules / sub routines and data flow
– Implementation
• Building, testing, deploying and tuning
– Maintenance
• Corrections
• Enhancements
• Structured System Analysis and Design Deliverables
– Planning : Customer Profile / Project Profile
• Information gathering about user requirements and setting goals.
– Analysis : SRS : System Requirement Specification
• Determining use needs and system constraints
• Testing alternative solutions
• Developing a functional specification and logical model
– Design: SDS : Software Design Specification
• Detailed solution
– Diagrams for programs, modules / sub routines and data flow
– Implementation: Source Code, Test Cases, etc
• Building, testing, deploying and tuning
– Maintenance : Contract, maintenance schedule, new req
• Corrections
• Enhancements
• Representation Methods
– Textual
– Diagrammatic
• Flow chart
• Data Flow Diagram
Civil Engineering :
Blue Print
Elevation diagram
Wiring
Plumbing diagram
RCC
Representation Methods : Data Flow Diagram
• A data flow diagram (DFD) is a graphical
representation of the "flow" of data through a
computer system.
OR
• A data flow diagram looks at how data flows
through a system.
• It concerns things like where the data will
come from and go to as well as where it will
be stored.
• Flow chart shows “ flow of Control “ .
• DFD shows “ flow of Data
• The flowchart describes boxes that describe
computations, decisions, interactions & loops.
• It is important to keep in mind that data flow
diagrams are not flowcharts and should not
include control elements.
• DFD Types
LOGICAL DFD
• It focuses on business and how it operates.
• It describes business events that take place and
the data required and produced by each event.
PHYSICAL DFD
• It shows how the system will be implemented.
• DFD Components
• 4 Basic Symbols
– Entities
• People, Things, Organizations
– Process
• Activity that transforms data
– Data Source
• Open Sided Rectangle
• Data can be read from a data store.
This is depicted by an outgoing
arrow.
• External entity cannot read or write to
the data store.
– Data Flow
• Represents movement of data
Data Flow Rules
Data can flow from Data cannot flow from

• External entity to • External entity to
process External entity
• Process to External • External entity to Store
entity • Store to External entity
• Process to store and • Store to Store
back.
• Process to Process
• Data Flow Diagram
General Rules for Drawing the Data Flow Diagram.
I. Any data flow leaving a process must be based on
the data that are input to the process.
II. All data flows are named; the name reflects the data
flowing between the processes, data stores, sources
or sinks.
III. Only data needed to perform the process should be
an input to the process.
IV. A process should know nothing about any other
processes in the system. It should depend on its own
input and output. (Independent)
General Rules for Drawing the Data Flow Diagram Contd
V. Processes are always running, they do not start or
stop. Analyst should assume that a process is always
ready to function or perform necessary work.
VI. Output of the process can take any of the following
forms.
a. An input data flow with information added by the process.
b. A response or change of data from dollars to profit.
c. Change of status.
d. Change of content.
e. Change of organization.
Logical DFD Physical DFD
• Drawn by keeping in mind • Drawn with reference to
how the work is going to be who is going to do the work.
done. • It is arrived by replacing the
• Focus on the process that processes in the Logical DFD
will do the work. by people who are expected
to do the process.
• The Human component has
to interact with the system.
UI design is given
impotance.
Software Versus Information Engineering
• General view of a system.
• Decomposing each functionality into micro-level, so that
they can be implemented as a code.
• Logical program design and physical design are different.
• Software Engineering uses lot of diagrammatic
representations.
Information Engineering
How CASE Tools store Information
• Multiple projects will be handled by companies.
• SAD is mandatory for any project.
• CASE tools must be able to store information in a style
such that there must be no cross-linking.
• CASE Tool repository
– Software Configuration Management
– Software Configuration Items
• Each project / application will have a separate folder.
• This folder will contain complete information about the
project.
• This folder will be accessed regularly by the designated
Data Dictionaries
• The folders are like dictionaries.
• Users can update this dictionary leading to a global
change.
• Involves, copying, renaming, deletion, etc.
• Stores the components of the model.
• Tracks the various component parts of the model such as
graphic files and textual files.
The ten objects of the model
1. Screens
2. Fields
3. Records
4. Diagrams
5. Processes
6. Repositories
7. Connectors
8. Symbols
9. Plain Objects
10. Reserved Object
Data Flow Diagrams (Additional input from
https://www.javatpoint.com/software-engineering-data-flow-diagrams)
– Visual representation of information flow within a system.
– The right amount of the system requirement can be graphically
depicted using a neat and clear DFD.
– Represents data flow covering its entry, exit, factors that change
the information and it’s storage location.
– Describes the scope and boundaries of the entire system.
– Other name is Bubble Graph / Data Flow Graph
– Levels of DFD
• Level 0
• Level 1
• Level 2
Data Flow Diagrams – Level 0 DFD
• Also known as fundamental system model, or context
diagram.
• Represents the entire software requirement as a single
bubble with input and output data denoted by incoming
and outgoing arrows.
• Subsequently the system is decomposed and described
as a DFD with multiple bubbles.
Data Flow Diagrams: Level 0 DFD - Sample
Data Flow Diagrams – Level 1
• Level 0 DFD is decomposed into multiple
bubbles/processes.
• Here the main objectives of the system is highlighted
and the high-level process of 0-level DFD are broken-
down into sub-processes.
• Used to project or record the specific/necessary detail
about the system's functioning.
• System functionality is decomposed into smaller units
for representation

Case Tools 1

Uploaded by

Copyright:

Available Formats

Case Tools 1

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Case Tools 1

Uploaded by

Copyright:

Available Formats

CASE Tools Concepts and Its

• Data Modeling: Business Growth-Organizational Model-

Data can flow from Data cannot flow from

You might also like