Case Tool Alignment

PIONEER COLLEGE OF ARTS AND SCIENCE CASE TOOLS
CASE TOOLS CONCEPTS AND APPLICATIONS
UNIT I:
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.
UNIT II:
Approach used to solve the problem statement: How to deal with a problem
statement-Data flow diagram for Payroll System-Presentation Diagram for Payroll System-
sehematics of the model-Forms-Screens-Menu Screens-Data entry Screens-Report Output
Format-Utilities. Installation of Ubridge and Synthesis: How to use the tools in Ubridge
Synthesis for case-Installation of Ubridge Synthesis-Computer Aided Software Engineering-
Getting Ubridge to work-Setup-Assign-Housekeep-The Ubridge page.
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 Drawing the screen-Requirement Definition-Diagram-Data
Dictionary-Document-Synthesis Main Administration - Synthesis reference - importing and
exporting screen.
UNIT IV:
Diagram definition tool: Introduction-Starting DDT-Drawing your own Icon -
Defining the connection rules-Rebuilding your icon. Object oriented methodologies:
Rambaugh et.al. s̳ object modeling techniques-The Booch methodology –The Jacobson et.al.
Methodologies-Pattern-Frame works-The Unified Approach.
UNIT V:
Introduction to UML-UML Diagram-Class Diagram-Use Case Diagram-Interaction
-Sequence Diagram-Collaboration Diagram-State Chart Diagram-Activity Diagram-
Component Diagram-Deployment Diagram.
1
UNIT - I
INTRODUCTION :
CASE stands for Computer Aided Software Engineering. It means, development and
maintenance of software projects with help of various automated software 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.
There are number of CASE tools available 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 moving ahead with next stage in software development.
Components of CASE Tools
CASE tools can be broadly divided into the following parts based on their use at a particular
SDLC stage:
 Central Repository - CASE tools require a central repository, which can serve as a
source of common, integrated and consistent information. Central repository is a central
place of storage where product specifications, requirement documents, related reports
and diagrams, other useful information regarding management is stored. Central
repository also serves as data dictionary.
 Upper Case Tools - Upper CASE tools are used in planning, analysis and design stages
of SDLC.
 Lower Case Tools - Lower CASE tools are used in implementation, testing and
maintenance.
 Integrated Case Tools - Integrated CASE tools are helpful in all the stages of SDLC,
from Requirement gathering to Testing and documentation.
CASE tools can be grouped together if they have similar functionality, process activities and
capability of getting integrated with other tools.
2
Scope of Case Tools
The scope of CASE tools goes throughout the SDLC.
Case Tools Types
Now we briefly go through various CASE tools
Diagram tools
These tools are used to represent system components, data and control flow among various
software components and system structure in a graphical form. For example, Flow Chart Maker
tool for creating state-of-the-art flowcharts.
Process Modeling Tools
Process modeling is 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
These tools are 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. For example, Creative Pro Office,
Trac Project, Basecamp.
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,
CaseComplete 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 interconnections among modules. For example, Animated
Software Design
3
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, Accu REV.
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 features for simulation and testing. For example,
Cscope to search code in C, Eclipse.
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 of configuration and change control tools and software
testing tools. For example, SoapTest, AppsWatch, JMeter.
4
Maintenance Tools
Software maintenance includes modifications in the software product after it is delivered.

Automatic logging and error reporting techniques, automatic error ticket generation and root
cause Analysis are few CASE tools, which help software organization in maintenance phase of
SDLC. For example, Bugzilla for defect tracking, HP Quality Center.
CASE Tools and its scope
CASE technology is the automation of step by step methodologies for software and system
development. CASE tools are characterized by the stage or stages of software development life
cycle on which they focus.
Since different tools covering different stages share common information, it is required that
they integrate through some central repository system (data dictionary) to have a consistent view
of such information. In phases of software development life cycle integrated through a central
data dictionary. Case Tools are used in many ways in our organizations. Case tools can be
broadly classed into these broader areas:
 Requirement Analysis Tool

 Structure Analysis Tool
 Software Design Tool
 Code Generation Tool
 Test Case Generation Tool
 Document Production Tool
 Reverse Engineering Tool
While many organizations still use the SDLC methodology, it is often supplemented with other
methods.
Many systems developers use the CASE tools in various stages of the Software
Development Life Cycle. They mainly use it while developing the following methodologies:
 Life Cycle
 Object-oriented Approach
 Rapid Applications Development (RAD)
 Prototyping
 Joint Applications Development (JAD)
CASE Tools in future…
Horizontal and Vertical Division of AO-groups
The whole system is composed of many active objects. Active objects (AO) are
categorized into several groups. Active objects in the same group are responsible for the same
5
type of tasks. For example, active objects to support SA/SD methodology and object-oriented
methodology.
This is what we call horizontal division. All AO-groups are organized hierarchically. For
example, the group on top level is for users; the group on second level is for domains; the group
on third level is for development knowledge; the group on fourth level is for tools; the group on
fifth level is for technique support. This is what we call the vertical division. For each group,
there is a delegate which is a local server of that group. The communication among different
groups is through delegates at the corresponding levels.
Knowledge Representation and Processing
The system maintains multiple layers of knowledge and has the ability of self-learning and self-
improvement. Especially, the system can do reasoning on incomplete information. Otherwise,
the system cannot 'figure out' users' intentions and the interaction between a user and a tool will
not be able to continue in some cases. Each node can be bound to a set of rules. Mixed
knowledge representation is good for reducing the size of the network, and thus speeding up the
learning process. In neural network, an output can always be derived from any input, even if the
input is incomplete. Self learning is a natural and standard process in a neural network.
Visual Integration of CASE Tools
Although a CASE shell is very useful for the creation and integration of CASE tools, we believe
it still is not simple and intuitive enough for CASE users. We suggest to provide CASE users
with more intuitive means to describe the integration of CASE tools. A diagramming tool,
similar to DFD diagramming tool, might be useful for this purpose. Pipe-filter, event-trigger and
message passing models are all useful means to realize the integration of CASE tools.
Work Flow Model
Basically, software project development is a team based activity. A CASE tool should be able to
support this feature. For this purpose, it is necessary to model the work process, and the
collaboration and coordination among team members. We hope to represent all these
information through a work flow model. Currently, there are many ways to model a work flow
for team based collaborative software development. However, most of them are too strict to
change dynamically (on the fly). We suggest using decentralized process models, such as
'ViewPoint' (E), which can be described visually and is also possible to cope with deviations
during process enactment.
Java Technologies
We are sure that the next generation CASE tools will be able to operate in heterogeneous and
distributed environments. JAVA is such a specification which allows for transparent access to
applications operating on multiple computing platforms. JAVA is endorsed by the OMG, an
organization that includes major computer manufacturers such as Digital, Sun, HP, IBM as well
as software providers such as Microsoft, Sunsoft, and Object Design among its members. JAVA
is possibly to become a de facto standard in the future. Based on this observation, we suggest
that the next generation CASE tools are established on CORBA standard. To develop platform
independent CASE tools, some platform independent programming languages, such as Java
programming language will be used.
A STUDENT MIS SYSTEM

6
COST OF CONVERSION
 Advertisement
 Seminars conducted
 Travel + miscellaneous expenses
SUB HEADS
FINANCIAL REQUIREMENT
WHAT IS THE PURPOSE OF SUCH MODELS
DOCUMENTATION
UNDERSTANDING THE BUSINESS
 Structured analysis
 Improving system quality
 Project team co-ordination
The case for structures development
 Planning
 Analysis
 Design
 Implementation
 Maintenance
SYSTEMS ANALYSIS AND DESIGN
Systems development is systematic process which includes phases such as planning, analysis,
design, deployment, and maintenance. Here, in this tutorial, we will primarily focus on −
 Systems analysis
 Systems design
Systems Analysis
It is a process of collecting and interpreting facts, identifying the problems, and decomposition
of a system into its components.
System analysis is conducted for the purpose of studying a system or its parts in order to
identify its objectives. It is a problem solving technique that improves the system and ensures
that all the components of the system work efficiently to accomplish their purpose.
Systems Design
It is a process of planning a new business system or replacing an existing system by defining its
components or modules to satisfy the specific requirements. Before planning, you need to
7
understand the old system thoroughly and determine how computers can best be used in order to
operate efficiently.
System Design focuses on how to accomplish the objective of the system.
System Analysis and Design (SAD) mainly focuses on −
 Systems
 Processes
 Technology
What is a System?
 The word System is derived from Greek word Systema, which means an organized
relationship between any set of components to achieve some common cause or objective.
 A system is “an orderly grouping of interdependent components linked together
according to a plan to achieve a specific goal.”
 Elements of a System
 The following diagram shows the elements of a system −
What is a data flow diagram (DFD)?
 A picture is worth a thousand words. A Data Flow Diagram (DFD) is traditional visual
representation of the information flows within a system. A neat and clear DFD can
depict a good amount of the system requirements graphically. It can be manual,
automated, or combination of both.
 It shows how information enters and leaves the system, what changes the information
and where information is stored. The purpose of a DFD is to show the scope and
boundaries of a system as a whole. It may be used as a communications tool between a
systems analyst and any person who plays a part in the system that acts as the starting
point for redesigning a system.
 It is usually beginning with a context diagram as the level 0 of DFD diagram, a simple
representation of the whole system. To elaborate further from that, we drill down to a
level 1 diagram with lower level functions decomposed from the major functions of the
system. This could continue to evolve to become a level 2 diagram when further analysis
is required. Progression to level 3, 4 and so on is possible but anything beyond level 3 is
8
not very common. Please bear in mind that the level of details for decomposing
particular function really depending on the complexity that function.
DATA FLOW DIAGRAM

It's easy to understand the flow of data through systems with the right data flow diagram
software. This guide provides everything you need to know about data flow diagrams, including
definitions, history, and symbols and notations. You'll learn the different levels of a DFD, the
difference between a logical and a physical DFD and tips for making a DFD.
What is a data flow diagram?
A data flow diagram (DFD) maps out the flow of information for any process or system.
It uses defined symbols like rectangles, circles and arrows, plus short text labels, to show data
inputs, outputs, storage points and the routes between each destination.
Data flowcharts can range from simple, even hand-drawn process overviews, to in-depth,
multi-level DFDs that dig progressively deeper into how the data is handled.
They can be used to analyze an existing system or model a new one. Like all the best
diagrams and charts, a DFD can often visually “say” things that would be hard to explain in
words, and they work for both technical and nontechnical audiences, from developer to CEO.
That’s why DFDs remain so popular after all these years. While they work well for data flow
software and systems, they are less applicable nowadays to visualizing interactive, real-time or
database-oriented software or systems.
History of the DFD
Data flow diagrams were popularized in the late 1970s, arising from the book Structured
Design, by computing pioneers Ed Yourdon and Larry Constantine. They based it on the “data
flow graph” computation models by David Martin and Gerald Estrin. The structured design
concept took off in the software engineering field, and the DFD method took off with it. It
became more popular in business circles, as it was applied to business analysis, than in
academic circles.
Also contributing were two related concepts:
Object Oriented Analysis and Design (OOAD), put forth by Yourdon and Peter Coad to
analyze and design an application or system.
Structured Systems Analysis and Design Method (SSADM), a waterfall method to
analyze and design information systems. This rigorous documentation approach contrasts with
modern agile approaches such as Scrum and Dynamic Systems Development Method (DSDM.)
Three other experts contributing to this rise in DFD methodology were Tom DeMarco,
Chris Gane and Trish Sarson. They teamed up in different combinations to be the main definers
of the symbols and notations used for a data flow diagram.
Symbols and Notations Used in DFDs
Two common systems of symbols are named after their creators:
Yourdon and Coad
Yourdon and DeMarco
9
Gane and Sarson
One main difference in their symbols is that Yourdon-Coad and Yourdon-DeMarco use circles
for processes, while Gane and Sarson use rectangles with rounded corners, sometimes called
lozenges. There are other symbol variations in use as well, so the important thing to keep in
mind is to be clear and consistent in the shapes and notations you use to communicate and
collaborate with others.
External entity:
An outside system that sends or receives data, communicating with the system being
diagrammed. They are the sources and destinations of information entering or leaving the
system. They might be an outside organization or person, a computer system or a business
system. They are also known as terminators, sources and sinks or actors. They are typically
drawn on the edges of the diagram.
Process:
any process that changes the data, producing an output. It might perform computations,
or sort data based on logic, or direct the data flow based on business rules. A short label is used
to describe the process, such as “Submit payment.”
Data store:
files or repositories that hold information for later use, such as a database table or a
membership form. Each data store receives a simple label, such as “Orders.”
Data flow:
The Route that data takes between the external entities, processes and data stores. It
portrays the interface between the other components and is shown with arrows, typically labeled
with a short data name, like “Billing details.”
DFD rules and tips
Each process should have at least one input and an output.
Each data store should have at least one data flow in and one data flow out.
10
Data stored in a system must go through a process.
All processes in a DFD go to another process or a data store.
What’s the difference between a logical DFD and a physical DFD?

A logical DFD focuses on the business and business activities, while a physical DFD
looks at how a system is implemented. So while any data flow diagram maps out the flow of
information for a process or system, the logical diagram provides the “what” and the physical
provides the “how.” They are two different perspectives on the same data flow, each designed to
visualize and improve the system. The logical DFD describes the business events that take place
and the data required for each event. It provides a solid basis for the physical DFD, which
depicts how the data system will work, such as the hardware, software, paper files and people
involved. In tandem, the logical and physical can fully visualize the current state and model the
new state to be considered and then implemented.
11
CASE REPOSITORY
• A repository is a centralised database containing all models (diagrams), data dictionary entries,
form & report definitions and system & organisational information
• Holds complete information to develop a system from initiation to maintenance
• Supports team is development
12
CASE ANALYSIS TOOLS

• Help handle the complexities of building large complex systems
• Analyse items stored in the repository for consistency & completeness
• includes diagrams, data, process flows and reports
• e.g. all classes in a sequence diagram are present in the class diagram and
messages are consistent
• Analysis tools often may be customised
CASE DOCUMENTATION GENERATORS

• Create reports based on the Repository’s contents
• technical & user documents in standard formats
• Benefits:
• helps manage large amounts of documentation generated during Systems

Development Lifecycle
• reduces “retrospective” documenting of system
• high quality documentation reduces maintenance costs/effort
• Automatic generation of program and database definition code from information stored in the
Repository
• Produce source code (not compiled) allows generation for several environments
• standard programming language conventions
• compiled on different platforms with different operating systems
• e.g. the IBM Rational Rose suite includes tools which:

13
• generate class definitions,
• in C++, Visual Basic, Java etc.;
• generate ER model, SQL schema (e.g. Oracle8), CORBA IDL and Web Publisher;
• reverse engineer from many of these;
• trace requirements from model to code;
• model integrator / check model
• guide the development process.
• e.g. the ASCENT suite developed at UoT
BENEFITS OF USING CASE TOOLS

• Automation of tedious tasks
• Syntax/completeness checks ensure consistency
• Amending/updating achieved far more easily
• documentation can be kept up-to-date
• beneficial effect on maintenance
• More rapid development
• more feasible to develop & evaluate alternative designs
• an aid to prototyping
• Capture of system data for reuse
• particularly important for OO development
• May guide the use of a methodology
• Clearer communication with users
• Continuity of development with changing staff
• Standardised quality assurance/test procedures
• Improvements in system quality
Reduction in defects increases morale

ROLE OF CASE IN SOFTWARE QUALITY ASSURANCE
• CASE can help with:
– adherence to standards,
– integrity of documentation,
– centrally held data dictionary,
– fast capture of requirements,
– quick modification to designs,
14
– trace requirements from model to code,
– guide the development process,
– easy, consistent code-generation.
• All important in maintaining quality
Limitations of CASE
• Limited flexibility in documentation
– standards may not suit organisation or project needs
• Development approach limited to fit capabilities of the CASE tool
– may not adhere to industry or organisational standards
Training and experience required

• Front loaded cost of installation of CASE tool & training
– benefits may outweigh initial costs
• Incomplete coverage of syntax/ consistency checks
• Limited intelligence - no checks on overall quality or correctness
UNIT - II
INSTALLATION OF UBRIDGE AND 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.
1. Diagramming tools to pictorially represent system specifications.
2. Screen and report painters for creating system specifications and for simple prototyping.
3. Dictionaries, information management system and facilities to store, report and query
technical and project management system information.
4. Specification – checking tools to detect incomplete, syntactically incorrect, and inconsistent
system specifications.
5. Code generations to be able to generate executable code from pictorial system specifications.
6. Documentation generators to produce technical and user documentation required by
structured methodologies.
* Prototyping tools help determine system requirement and predict performance beforehand.
* Prototyping are user interface painters (screen painters, report painters and menu-builders)
that prototype the user interface to give users an advance view of how the system will look&
to identify&correct problem areas.
* Screen dialogue & navigation with entry & edits can be simulated with or without
compilers.
*Source code for record, file, and Screen& report descriptions can be generated automatically.
15
*Sophisticated prototyping tools, which involve specifying system requirements and executing
specified to refine, correct & ensure completeness of the system to meet user requirements.
Tools are,
* Diagramming section
*Prototyping section
*Code generation section
INSTALLATION OF UBRIDGE SYNTHESIS:
*Hardware requirements
* Installation
Hardware requirements:
* To install case tools (Ubridge synthesis) on your machine the following hardware
requirement must be satisfied.
*1BM pc /xT or true compatible under MS_DOS version 3.0 or later.
*One floppy drive (5 ¼” or 3 ½”).
*640 kb of RAM.
*Hard disk with at least 3MB of free space.
*Other than mouse drives it’s advisable not to have any program resident in memory.
Example: when synthesis is running.
*Synthesis needs 520 KB of memory free for its use.
Installation:
(i) Create a directory, say synthesis
C :\> md synth
Change your directory to this directory.
C :\> cd synth
Insert the 1st floppy in the drive and copy it in synthesis directory.
In this way copy all the ten floppies in the synthesis directory.
C :\> copy a: *.*c:\ synth
Note: after all the ten floppies are copied, please find out the type of monitor you are using.
*if it’s a monitor then there is nothing to worry about it for MGA or HGA monitor please run
this command.
C:\>synhga
C:\ synth\ INSTSYN
*The installation program instsyn will operate for a while & then give the message.
16
“Synthesis installation complete”.
Notes: synthesis cannot run without installation.
*computerized software is generally divided into 2 broad classes.
1. System software
2. Commercial application software
*each class of software is developed in computer programming languages own vocabulary,
syntax & semantics.
*software can be a few lines of code or a single computer program & it can be a very large
block of code doing complex things which constitutes a package.
COMPUTER AIDED SOFTWARE ENGINEERING:
* Creative process, we can enhance productivity.
* CASE very reliable software.
* CASE tools automate activities in all stages of the software development lifecycle
* requirement definition
* design
* development
*testing
*implementation
*documentation
*One such product that helps automate most stages of the software development lifecycle is
Ubridge synthesis.
*CASE tools is the concept of a central repository called a data dictionary.
Data dictionary: * This is a central store which holds all the software synthesis design data, its
diagrams & documentation all related to the software under development.
*Using CASE tools can develop reusable modules which can reduce the amount of
repetitive work the developer needs to do form application to application.
GETTING UBRIDGE TO WORK
* The user interface that allows access to the system. Configuration & security facilities is
called the SYSTEM MANAGER.
* ’SYSMAN’ we are this executable we can access various options that Ubridge provides.
C:\ SYNTH>sysman
SYSTEM MANAGER
Password:
17
 When the system is coded for the first time the password supplied is INDUS then the user
interface loads & we have access to various options of “SYSMAN” including the option of
changing the password.
SYNTHESIS SYSMAN
Assign House Keep
Setup Views
Ok Cancel Help
SETUP Ubridge to work in the manner that you want
Synthesis setup
Video mode : Auto Printer port : Lpt 1
Input / Output : unbuffered Dir Blocks: 3
Printer: Epson24
Change password
Word processor :
Graphics setup ok cancel help
1) The video mode in which Ubridge needs to run.

CGA, EGA &VGA
Note: A. com file needs to be run before invoking Ubridge on a MGA/ HGA system else the
system hangs (Example check installation Ubridge).
2) Declare the printer port LPT1, LPT(local printer terminal)2.
Parallel or serial & which port is declared.
18
3) The type of input and output for files.
4) The type of printer driver required to work your printer.
5) CHANGE THE PASSWORD to sysman to one of your choice.
6) Identify the sub- directory where your favorite word processor sills.
The GRAPHICS SETUP:
SYNTHESIS GRAPHICS SETUP
Default Font: Standard Max Font: 3
Labelimm : No System Label: Yes
Connector color : White
Object / Text Ok Cancel Help
DEF FONT:
 Several types of fonts are used in Ubridge while diagramming. We have to setup a
DEFAULT font to load when Ubridge loads up, this default is defined in this window.
MAXFONT:
 Memory sized used by load fonts. Define the memory size used by Ubridge to load fonts.
LABEL IMMEDIATE:
 While creating an OBJECT in a window. Ubridge will ask you to name & label them.
SYSTEM LABEL:
 When you create a LABEL on screen. Ubridge will always mark the label area carefully.
CONNECTOR LABEL:
*You can select one of 16 class for the connectors between objects on screen. This is a default
setting but a connector color can also be set in a window session.
The object / text set up window:
Synthesis graphics setup (object/text)
Object scale factor: 3 text size: 3
Object color: white
Text color: red

19
ok cancel help
The object scale factor:

*objects sizes in a window can be scaled from 1 to 7 with 4 being the default size.
*This scaling allows the user to see more or less of the obj draw in a window.
Text size:
*Similar to objects, text can also be scaled from 1 to 5 with the default bring 3.
*1 to 5 corresponds to tiny, small, medium, large & very large.
Object color:
*object colors can be chosen from a palette of 16 colors.
Text color:
*Text color can be chosen from a palette of 16 colors.
*The ok, cancel and help buttons can be clicked on by the mouse to save your changes, exit
without saving your changes.
*Help for the screen you are currently working on.
*This is done by entering the ASSIGN sub-menu system.
Synthesis assignment
user project
ok cancel help
This sub-menu is bifurcated in 2 pass:

A) Where can identify a user to the system.
B) Where you identify a project and assign a user to a project.
a) When you enter the user assignment screen you can ADD, MODIFY, DECETE a user on the
system SAVE these changes or ABORT.
&obtain HELP for the screen you are currently on.
b) When you enter the project assignment window you can ADD, MODIFY, DELETE pro to
the system.
RELEASE => present any changes to the project data dictionary.
20
REACTIVATE => allow further changes to a project after it has been RELEASED.
c) When you have setup a project you can assign user to a project, Ubridge allows you to.
*ADD, MODIFY, DELETE users assigned to a project the user access to a project can also be
controlled to be either READ ONLY or READ WRITE for a user.
ON ENTERING THE HOUSEKEEPING MENU LOOK

*This allows a user to Backup and Restore file from the current sub directory.
Synthesis housekeep
List project name:
backup restore
ok cancel help
*We have defined users of the system as well as projects to Ubridge and assigned these users to
project with each user’s access rights.
THE UBRIDGE PAGE
*The visible area on the screen on which you work, which is much less than the actual page
length.
*The MAXIMUM no. of rows are 72
*The MAXIMUM no. of columns are 256
*Default settings that load up when Ubridge loads up but via the system management software
CHANGE SCREEN SIZE.
*TOP LEFT hand side of the page & you will be able to see only a part of the actual page.
*TOP right only a part the no’s -> status line indicates where in the cursor is on the page.
UNIT - III
INTRODUCTION TO UBRIDGE
Introduction:
*we have seen the different screen that have to be designed for the payroll project.
*CASE tool must have an option so that the designing of the screens can be achieved.
*Ubridge synthesis uses its first menu screen.
Example:Ubridge menu screen.
*using this menu, we must be able to draw our screens so that it satisfies the client as well as the
user using it.
21
*The forms that are designed for the payroll project suggest.
1. Draw boxes/ lines.
2. Define simple fields and table fields.
3. Attach text to the screen.
4. Attach default value for a field.
5. Stich field validation to a field.
6. Chain different screens together so that we can develop the pull down menu system.
7. Do cursor controlling.
8. Define the screen logic.
*To get started with Ubridge synthesis we used to first get into the tool by keying in
C:\ synth>synth
After entering the username &password and the project. Name you will be put on the 1st screen
of Ubridge.
Ubridge synthesis version 1.1

Req diagram data.dictionary document admin quit help
*To get inside painting your screens you must choose the requirement option.
How Ubridge is used is essentially as following
MAIN FLOW OF THE SYSTEM
*use Ubridge to create a screen. All the necessary video attributes such as bright, flash, reverse
of the screen can be defined.
*including several graphic blocks can be used to enhance the screen aesthetic presentation.
Paint ubridge ver 2.01 row 001 col 001

Paint data built execute interface administrator F1 help
Menu screens:
*We can use the paint tool to design menu screens.
*One menu screen can call as another menu or data entry type of screen. This is done by a
process called chaining.
Data as Ubridge see it:
*In Ubridge, DATA is defined as those areas of the screen representing variable information.
*Once the field to from has been identified Ubridge will display the set of values or ranges that
are currently defined for the field.
22
*When entering the screen name to link to, if you do not remember the names of the screens
press * Enter and a list of screens from your active library will be displayed.
*Position the highlight on the screen name you wish to select and press enter.
Now select the EXECUTE option:
Several options will be available,
1. Current screen
2. AIL from current
3. Specific screen
4. Data manager
Ubridge ver 2.0 row 001 col 001

Paint data built execute interface administrator F1 help
Current screen
All from current
Specific screen
Data manager
*Press S and select the 1st screen of the working model we have created and Enter.
Display ->for executing the model of the Ubridge screen.
PROTOTYPING YOUR REPORTS
*Reports will be a major portion of your model.
*You can plan a report as much as 256 columns.

*you can PAINT a report using the screen paint option and actually define its contents.
*Even here fields can be defined with the addition of a proper report header a complete report
model can be created.
*And chained to the model system accessible via the REPORTS option of the main MENU to
provide reality of the models flow.
INTRODUCING THE NOVICE MODEL OF OPERATION
*The novice model makes the various activities such as painting of screens, defining of data,
chaining of screens.
*Ubridge transparent to the user.
*This mode thus makes a model of your sys without having to paint screens, define data, chain
screens together or any other activity that is normally required to make such a model.
*The novice user interacts with the various activities of Ubridge through question answer
dialogue boxes.
23
*Ubridge automatically makes a BARE BOX model of your requirements, no attempt is made
to add any sophistication to the generated model.
INTRODUCING synthesis:
*synthesis concept of building physical and logical models of an application. System using
graphical techniques.
*Enabling end user’s, analyst and designers to get a clear picture of the system and how its parts
fit together to meet the user’s need.
SYNTHESIS Basics:
Starting SYNTHESIS:
You can run synthesis from any directory or sub directory with the command.
<Path name> SYNTH {Enter}
Adjusting to Different Monitor types:
Synthesis assumes a color monitors when you run it using the command SYNTH {enter}.
If you have a monochrome monitor the resultant shades may not have adequate contrast. You
can override the clear usage by keying in ‘/b’ after SYNTH.
<PATHNAME> SYNTH /B {Enter].
The synthesis Main Menu:
One you have logged in through the login window of SYNTHESIS the main menu of
synthesis will be displayed.
*Requirement
* Diagram
*Data Dictionary
*Document
*Administrator
*Quit
Requirement:
*Paint your screen and report layouts the way you see them
*Data that you want your system to handle.
*Built your view of the synthesis & actually make a prototype of the system you want.
*Finally give your programmer the facility to exit act screen and report formats into different
mainframe / pc compatible forms.
Diagram:
*Build your own objects and techniques.
Data Dictionary:
24
*Provides a direct data dictionary interface. Allows you to make reports and queries & analysis
diagrams.
Document:
*Build a document based on the data dictionary. This document could be a synthesis document.
A user manual or a plain synthesis proposed.
Administrator:
*use the administrator to setup colors, select a printer & to access DOS.
Quit:
At the end of a session, this option will take you back to the DOS prompt.
DRAWING THE SCREENS:
[A] REQUIREMENT DEFINITION:
*This option allows you to make a requirement definition of the system under Analysis
& designs.
*At the end of the requirement definition, you have a model of your system.
*Which shows you exactly what your new system is going to do.
*You can actually execute or run this model by entering data through your screens and getting
reports in print with live data entered.
[B] DIAGRAM:
The diagramming menu has the options.
1. Draw -> to actually position and draw an object and connect the objects.
2. Label -> to place a short textual description on an object or connector.
3. Describe -> to give more details about the object.
4. Tools -> to mark changes in your diagram like moving an object, deleting an object, cut and
paste, zooming in and out, exploding& imploding a process.
5. Control -> display a control panel to change the font, size and color settings.
6. Window -> Activate the window managers. It allow you to create, move, remove & resize a
window, maximize & minimize a window, activate a window & undo all these ,,,,,
7. Administrator-> Lets you get, save, load and print diagrams.
8. Quit-> Used to exit from the diagramming menu.
[c] DATA DICTIONARY:
*An entity is something about which information is stored in a sys.
* DATA DICTIONARY is a repository of details of all entities handled within SYNTHESIS.
The data dictionary is in 2 phases:
1) Part I of the data dictionary:
*1st part of the data dictionary contains data that’s stored for use by SYNTHESIS only.
Example: Diagram definition and object definitions.
25
*This part of the data dictionary comes populated with data with the initial SYNTHESIS
distribution disks.
2. Part II of the data dictionary:
*The 2nd part contains data that is stored for a project.
Example: all the entities that describe the “sales” project of your organization will be stored in
this part of the data dictionary.
*During Analysis and design of a system, you create screens and models of a requirement and
represent your logical and physical designs using diagrams.
*In the process of describing screens and diagrams SYNTHESIS automatically stores all data in
part II of the data dictionary.
Ubridge synthesis ver 1.1

Requirement diagram data.dictionary document admin help
Direct interface
Diagram analysis
Reports
Query
Extract
Options are:
1). Direct Interface-> A means by which you can view, add, modify or delete courtiers of data
dictionary.
2). Diagram Analysis-> A facility to help you check completeness of your diagrams.
3). Reports-> you can extract selective lists of specific entities in a project.
4). Query-> you can find out “Where all” a field of data is used and “What if” a repository is
modified.
5). Extract-> using the extract facility, you can generate C and COBOL code of data structures
in your project data dictionary.
THE DIRECT INTERFACE:
*Entities in the data dictionary are handled by the direct interface in 3 ways.
1).General interface is entered through the “entity window” this applies to all entities.
2).The “field” entity requires additional interface that’s entered through the “field window”
3).”Record” entity add interface entered through the “record window”
DIAGRAM ANALYSIS:
Three types of diagram analysis can be performed,
26
1).DFD Analysis, for ensuring completeness of a diagram.
*When you invoke this option, a list of all data flow diagrams stored in the dictionary will be
displayed.
*select one for analysis.
*It used for check the diagram is correct or if it’s not.
*List out of missing interface.
2).Level balancing for ensuring across DFD:
*In a DFD you can have a “process” that exp codes to another DFD.
*The data flows that are connected to this “process” should be accounted for in the DFD
represents the process.
Leveled Data flow diagrams:
*At the top most in the hierarchy of a leveled DFD is the context Analysis diagram.
* This is the parent of the 1st level breakdown diagram.
*The next level of DFD (e.g. child)
Balancing of a data flow diagram:
Balancing -> Data flows into and out of a process in a parent diagram.
*This is the equivalent of input and output to and from a child diagram.
Advantage: Levelled DFD ‘S allow a top-down approach read from top-down.
Normalization:
Normalization is a technique that has been developed to ensure that the data structure is
efficient.
 1NF (first normal form)
 2NF (second normal form)
 3NF (third normal form)
Un-normalized form (UNF) relation:
*1st we have to prepare a list of data items that are present in this form.
*we have to choose a key for the UNF.
Guidelines for choosing a key:
1. The key must have a unique values for each occurrence of the group of data connected.
2. The key must not repeat within a group of data.
3. Where the data can only be identified uniquely by a key made up of more than one d.item a
compound or composite key. ->choose the least no. of data items.
UNF Relations:
Data
Grn number
27
Supplier name
Supplier Address
Order reference
*Item code *Total
*Description *Discount
*Rate *Grand total
*Quantity
*Indicates data element it’s repeating in this format.
1NF:
*Does not include any repeating groups.
*Any single data item or group of items within the UNF relation occur more than once for a
single value of the key should be removed.
2NF:
*2NF each field (or attribute or data item) depends on the whole key & not on part of the key.
Relation 1 R2 R3
Date GNR number item code
GNR number item code description
Supplier name Rate
Supplier address
Order ref quantity
Discount Total
Chancel total
*In the FNF relation2, Description & rate depend on item code and not on Grn no.
*Thus we remove this and form author relation.
3NF:
*Each field depends only on the key and doesn’t depend on other fields within that record.
Example: Supplier address in relation 1 is dependent on supplier name and Grand total is
dependent on discount.
*In relation 2 total is dependent on quantity.
Relation 1 Relation 2 R3 R4
Date GNR number item code supplier name
GNR number item code description supplier address
Supplier name Rate
Order ref Quantity
Discount
*Report
*Query
*Extract
28
Reports:
*You can extract reports on any of the entities in the data dictionary.
*Reports are in the form of lists of data dictionary contents.
*after you select this option, you want reported.
Query:
*gives the information of fields & division for making a query.
2 divisions:
1. Field or records
2. Repositories.
 ” Field “option of query a list of a fields and records will be displayed.

 Select the field that you want to query on.
 Repository in diagrams.
Extract:
*Records described in the project data dictionary can be extracted in C or COBOL code formats.
*The “Extract “utility can be invoked through the “Data Dictionary “menu.
*Select the record to extract next give the name of the TEXT file that will be used as the output.
DOCUMENT:
*Document module you can build a complete document.
*Based on the contents of the data dictionary & extraneous data.
*The documents that you can build are system proposals, system specification, system manuals
& user manuals.
*Once you choose this option.
*Create a document
*modify a document
*Generate a document
*Word processor.
1 ST option -> enter a document.name
*A section can either be an Ubridge screen, a diagram or a text file.
Text files should be in ASCII format,
*Word processor output.
* Reports generated using the “Diagram analysis” “Query “or “Report” facilities.
* Reports generated using the Ubridge “print document” facility.
*All text files designed as section must be present in the uses directory.
Extensions “.txt”
*The “Introduction” chapter would contain the following sections:
29
1. INTR01 .TXT ->exp the object of system.
2. Stores interaction -> presentation diagram shows the human interaction.
3. INTR02.TXT -> overview of the system
4. Stores system -> DFD describes the data flows in the system.
INTR01.TXT:
*you are asked to select either t for text, s-> screen d-> diagram.
Generating a document:
*Generate an existing document.
*Get a selection list, select the document you just created.
* . Doc extension.
Printing a document:
PRDOC -> execute the program
Key in: PRDOC {project name} {user name}
SYNTHESIS ADMINISTRATOR:
*The synthesis administrator essentially gives you facilities to reconfigure synthesis colors,
select a different printer and change the function key short cut assignments.
*If also gives you a means to access DOS directly without exiting from SYNTHESIS.
THE SYNTHESIS REFERENCE
1. EXPLODE -> Describe a process, dataflow, connector or repository in detail as another
diagram, record or screen.
 Diagramming tools icon selection list.
UNIT - IV
DIAGRAM DEFINITION TOOL
*In previous study about the DFD diagrams.
*Ubridge synthesis will create new icons or diagrams.
*If you take a listing of Ubridge synthesis home directory it will show you an executable
add.exe.
*When Ubridge is installed there is a file called DDT.EXE -> draw your own diagrams & icons.
*DDT works on CGA, EGA, VGA & her rules graphics monitors.
*Following files are present in the systems directory.
1. DDT.EXE
2. UBCOLOR.UBE
3. UBHELP.UBE
30
4. UBINDX.UBE
5. UCDATA.UBE
*The file UCDATA.UBE will be modified during DDT interaction. It’s suggested that you
make a backup copy of this file before using DDT.
*So that an accidental corruption of the file due to incorrect interaction can be avoided.
STARTING DDT
At the dos prompt key-in as follows
C:\synth >ddt
This will call the executable from the synthesis home directory.
Ubridge synthesis DDT ver 1.0
Object diagram administrator
Object : Diagram:
Diagram: DDT opening screen

Administrator -> Select the administrator option let you create new diagrams, modify existing
diagram.

New object/diagram
Get object
Save object
Get diagram
Save
Quit
Status:
*Since we want to create a new diagram select the option new object/diagram.
*you will have to specify the diagram name, diagram description, manual connection
&overlap connection.

Diagram name: aaa
Diagram description:Rukminis gane&sarson
Manual connection: No overlap connection: No
31
Icon object list connector list symbol list
Ok cancel help
DRAWING YOUR OWN ICON

*To draw your own DFD you will 1 st have to create your own icon is compulsory.
*To draw your own icon, choose the icon option.
Diagram name: aaa

Icon window
D Icon label:Rukus hotkey:u

M icon draw
I ok cancel help
*You will have to specify a label to this icon. This will be automatically attached to the icon that
you will create.
*After specifying the icon label select DCON DRACE option.
Connector Anchor Hotarea Grid setcolor Quit

Line
Circle
Area
Previous
Next
Last
First
32
Delete
Redraw
Zap Do you wish to save changer? (Y/N)
*Use any or all the options that are available to you and draw an icon the way you like.
*Save your diagram by selecting the quit option that is given above you will return back to the
previous screen.
Example: Select the object list & set ok for the command button.
*You would like to have different objects in are DFD select the object list button.
[Diagram]
*The object name list will show you all the objects that are available to you.
*Choose the object that you want & click the Add menu.
DEFINING THE CONNECTION RULE
*For any object that you will select the explosion rule and the connection rule must be specified.
*1st select the explosion rule menu. A pop-up window opens up.

Explosion rule window
Object name: External entity G&S
Object name list Explode name list
Screen add
Record delete
33
DFD gane&sarson
DFD yourdon
Ok cancel help
*Here since the external entity cannot be exploded we are not giving any explosion name list.
*You will have to select the object from the object name list and select the Add menu to add it
to the exploded name list.
*After you have finished select the ok menu to return back to the previous screen.
*Data store can be exploded into a record.
*Similarly for each of the object list it will ask for explosion rule & the connection rule.
*Select the connection list menu to define the type of connection you want.
Diagram connection window

Diagram name: ------
Connector name list diagram connector
Slant arrow add
Slant line straight arrow
Straight linemodify
Straight arrow
Double arrowdelete
Double headed arrow
One to many
Ok cancel help
*Select the connector name from the connector name list and choose the add menu to add that
connector to the diagram connector list.
*When you choose the add menu the following pop-up opens up on the screen.
*This will pick up the connector type from the name that you have selected.
*You will have to specify the c.name & hot key for the connector type that you have selected
34
Add connector window
Connector type: Straight arrow
Connector name: St –arr Hot key: s
Expansion rule
Ok cancel help
*Now you will have to specify the expansion rule menu and the following pop-up window
opens up.
[Diagram]
*Select the name from the object name list and then select the add menu.
*This will add the entry in the connector expand list. After finished this, select the ok menu to
accept your changes and return back to the main screen.
New object/diagram
Get object/diagram
Save object/diagram
Get diagram
Save
Status: Quit
REBUILDING YOUR ICON

*Now, select the save diagram option to save the new diagram. This will display a message to
you on the screen.
*After the new diagram is saved, select the quit option and come to the prompt.
Example: C: \synth>
*The new icon that was drawn right now must be built in the system so that it will be accessible.
*Run the icon make.exe so that whatever icon you have drawn can be actually accessed.
*At the prompt-key.
C: \synth>icon make
*This will re-built.
OBJECT-ORIENTED METHODOLOGIES
35
A. RUMBAUGH ET AL.S OBJECT MODELING TECHNIQUES
*OMT (Object Modeling Technique) Presented By Join Rumbaugh.

*A Method for Analysis, design &important of a System Using Object Oriented Technique.
*OMT is a fast, Interactive Approach for identifying &modeling all the objects making up a
system.
*details such as class, attributes, method inheritance & association is expressed easily.
4 Phases:
1. Analysis -> The Results are Object, Dynamic and Functional Models.
2. System Design-> Structures Of The Basic Architecture Of The System Along With High-
Level
3. Object Design->Design Documents Consist Of Detailed Object Static, Dynamic &
Functional Models.
4. Important-> Reusable, Extendible &robust Code.
1. The Object Model
Structure of Object in a System Identify Relationships To Other Objects, Attitude and
Operations.
*The Object Diagram Contains Classes Interconnected By Association Lines.
*Each Class represents a set of Individual Objects.
*The Association Line Established Relationship among the Classes.
*Association Line Represents a Set of Links from the Objects Of One Class To The
Object.
2) THE OMT DYNAMIC MODEL
* OMT Provide a Detailed and Comprehensive Dynamic Model. Let Depend State,
Transition, events and Action.
* OMT State Transition Diagram A Network So States And Events.
* Each State Resolve One In More Event At Which Time It Makes The Transition To
The Next Stage.
* Next Stage Depends On The Current State As Well As The Event.
3) THE OMT FUNCTIONAL MODEL
The OMT Data Flow Diagram (DFD) shows the flow of data between different Processes
in Business.
Data flow diagram use four primary symbol:
1. Process:
The process is any function being performed.
2. Data flow:
The data flow shows the direction of data element moments.
3. Data store:
The data stores is a location where data are stored.
4. External entity:
36
An external entity is a source or destination of a data element.
THE BOOCH METHODOLOGY

 The booch methodology is a widely used object- oriented method that helps you
design your system using object paradigm.
 It covers analysis and design phase of an object-oriented system.
The booch method consist of the following diagram.
 Class diagram
 Object diagram
 State transition diagram
 Module diagram
 Process diagram
 Interaction diagram
I. The macro development pattern:

 The macro process server as a controlling framework for the macro process and can
take weeks or even months.
 In the macro process, the traditional phases of analysis and design to a large extent are
preserved.
The macro development process consist of following steps:
a) Conceptualization: Establish a set of goals and develop a prototype to prove the

concepts.
b) Analysis and development: Class diagram to describe the roles of responsibility
object are to cagey out in performing the desired behavior of the system.
c) Design: To determine which process is allocate the process and also determine
the schedule for multiple process.
d) Evolution: Produce a stream of software implementations.
e) Maintenance: Make localized changes to the system to add new requirements
and eliminate bugs.
II. The micro development process:

*The micro development process is a description of the day-to-day activities by a single or
small group of software development.
The micro development process consist of following steps:
I. Identify classes of objects.
II. Identify clean and object semantics.
III. Identify clean and object relationship.
IV. Identify clean and object interfaces and implementation.
c). THE JACOBSON ET AL. METHODOLIES
37
*The Jacobson ET AL. Methodologies cover the entire life cycle and struts traceability
between the different phases.
I. Use cases.
II. Object oriented software engineering
III. Object oriented business engineering
I) Use cases:
*A use case is an interaction between users and a system.
*The use-case model captures the goal of user and the responsibilities of the system.
The use case describe one of the followings:
*Non-formal text with no clear flow of events.
*Text easy to read but with a clear flow of event to follow.
*Format style using pseudo code.
The use case description must contain:
*How and when the use case begins & ends.
*The interaction between the use case and its actors.
*need to store the system.
*Exceptions to the flow of events.
*Concept of the problem domain.
-> Every single use case should describe one main flow of events.
-> An exceptional or additional flow of event could be added.
->The extend relationship is used when you have one use case it similar to another use case.
->An abstract use case is not complete and has no actors that intimate it but is used by another
use case.
library
Checking out books
Getting an inter library loan
Doing research
Reading books, newspaper
Purchasing supplier
supsuppliers
Use - case of a library
38
(ii) Object-oriented software engineering: objector
*Object-oriented software engineering (OOSE) also called objector.
*It is a method of object-oriented development with the specify aim to fit the development of
large, real-time system.
*The development process is called use-case driven development.
*The system development method based on OOSE is a disciplined process of the industrialized
of software.
*Jacobson ET.AL Objectorhas been developed and applies to numerous application areas and
embodies in the CASE TOOL systems.
*objector is built around several different models.
i) Use case tool:
The use case model defines the outside and inside of the system.
ii) Domain object model:
The object of the “real” world are mapped into the domain object model.
iii) Analysis object model:
The analysis object model presents how the source code should be carried out.
iv) Implementation model:
It represents the implementation of the system.
v) Test model:
It constitute the test plans, specifications and reports.
[
Use case model
Tested in
Express in
Structured by realized by implemented by
Ok
Not ok
Domain object analysis design implementation test
Model model model model model
(III).Object-oriented business engineering:

Object-oriented business engineering (OOBE) is object modeling at the enterprises level.
i. Analysis phase:
The analysis phase defines the system to be built in terms of the problem-domain
object model.
This reduce complexity and promoter maintainability over the life of the system.
ii. Design and implementation:
The implementation environment must be identified for the design model.
39
The analysis object are translated into design object that fit the current
implementation environment.
iii. Testing phase:
Finally jacobson describes several testing levels and techniques, the level
includes unit, integration, and system testing.
PATTERNS
Introduction:
*A pattern is instructive information that captures the essential structure and insight of a
successful family of proven solutions.
*A pattern involves a general descriptions of a solution to a recurring problem bundle with
various goals and constraints.
*”A pattern in waiting” which it is inappropriate to decisively to know to recur sometimes is
called a proto-pattern.
A Good Pattern will do the following:
I. It solve a problem
II. It is a proven concept.
III. The solution is not obvious.
IV. It describe a relationship.
V. The pattern has a significant human component.
It includes,
A. Generative and Non Generative pattern
B. Pattern templates
C. Ant patterns
D. Capturing patterns
A. generative and non-Generative patterns:

* Generative patterns are patterns that not only describe recurring problem, they can tell us
how to generate something and can be observed in the resulting system.
*Nongenerative patterns are static and passive
They describe recusing phenomena without necessarily saying how to reduce them.
B. Pattern templates:
*Every pattern must be expressed “in the form rule “, which establish a relationship between
a context and a configuration.
The following essential components should be clearly recognized on reading a pattern:
1) Name - a meaningful name
2) Problem - a statement of the problem that describes its intent.
3) Context - the preconditions under which the problem and its solution seems to recur and for
which the solution is desirable.
40
4) Forces - a description of the relevant forces and constraints and how they interact or conflict
with one another.
5) Solution - static relation and dynamic rule describing how to realize the desired outcome.
6) Examples - one or more sample application are illustrated.
7) Resulting context - the static or configuration of the system after the patterns has been
applied, including consequences of applying patterns.
8) Rationale - a justifying explanation of step or rules in the pattern and also of the pattern as a
whole in terms of how and why if resolve.
9) Related patterns - the static and dynamic relationship of a pattern.
10) Known users - the known assurance within existing system.
c) Anti Patterns:
* A pattern represents a “best practice” whereas Anti patterns represents “worst
practices” or “a lesson learned”.
An ant patterns come in two varieties:
i) A bad solution to a problem that resulted in a bad solution

ii) How to get out a bad situation and how to proceed from there to a good solution
d) Capturing patterns:
*writing good patterns is very difficult patterns provide not only fact but also tells a story
that captures the experience that are trying to covey.
*The process of looking for patterns two document is called pattern mining or sometimes
called reverse architecture.
Guidelines,
i) Focus apracticability- patterns should be describe proven solution to recusingproblem.
ii) Aggressive Disregard of originality – pattern writers do not need to be the original inventor
or discoverer of solution.
iii) Non anonymous review- pattern submission are she peered rather than reviewed pattern
classified or improved.
iv)Writer’s workshop instead of presentations – presenting by individual authors.
v) Careful editors - the pattern authors should have opportunity to incorporate all the
comments and insight.
FRAMEWORK
*Framework are a way of delivering application development patterns to supports best

practices sharing during application development.
*A frame work is a way of presenting a generic solution to a problem that can be applied to
all levels in a development.
*A single framework typically encompasses several design patterns a frame work can we
viewed as the implementation of a system design patterns.
*Major different between design pattern and frame work design.
i) Design pattern are more abstract form framework.
Framework can be embodied in code design pattern have to be implemented each time they are
used.
ii) Design pattern are similar architecture element than frameworks.
41
A typical framework contains several design patterns.
iii) Design patterns are a specialized than framework.
Framework always have a particular application domain.
Design pattern can be used in really any kind of application.
UNIT - V
INTRODUCTION TO UML (UNIFIED MODELING LANGUAGE)
UML is a standard language for specifying, visualizing, constructing, and documenting the
artifacts of software systems.
UML was created by the Object Management Group (OMG) and UML 1.0 specification draft
was proposed to the OMG in January 1997.
OMG is continuously making efforts to create a truly industry standard.
 UML stands for Unified Modeling Language.

 UML is different from the other common programming languages such as C++, Java,
COBOL, etc.
 UML is a pictorial language used to make software blueprints.
 UML can be described as a general purpose visual modeling language to visualize,
specify, construct, and document software system.
 Although UML is generally used to model software systems, it is not limited within this
boundary. It is also used to model non-software systems as well. For example, the
process flow in a manufacturing unit, etc.
UML is not a programming language but tools can be used to generate code in various
languages using UML diagrams.
Goals of UML
A picture is worth a thousand words, this idiom absolutely fits describing UML. Object-
oriented concepts were introduced much earlier than UML. At that point of time, there were no
standard methodologies to organize and consolidate the object-oriented development. It was
then that UML came into picture.
There are a number of goals for developing UML but the most important is to define
some general purpose modeling language, which all modelers can use and it also needs to be
made simple to understand and use.
UML diagrams are not only made for developers but also for business users, common
people, and anybody interested to understand the system. The system can be a software or non-
software system. Thus it must be clear that UML is not a development method rather it
accompanies with processes to make it a successful system.
In conclusion, the goal of UML can be defined as a simple modeling mechanism to

model all possible practical systems in today’s complex environment.
A Conceptual Model of UML
42
 A conceptual model can be defined as a model which is made of concepts and their
relationships.
 A conceptual model is the first step before drawing a UML diagram. It helps to
understand the entities in the real world and how they interact with each other.
As UML describes the real-time systems, it is very important to make a conceptual model and
then proceed gradually. The conceptual model of UML can be mastered by learning the
following three major elements −
 UML building blocks

 Rules to connect the building blocks
 Common mechanisms of UML
This chapter describes all the UML building blocks. The building blocks of UML can be defined
as −
 Things
 Relationships
 Diagrams
Things are the most important building blocks of UML. Things can be −
 Structural
 Behavioral
 Grouping
 Annotational
Structural things define the static part of the model. They represent the physical and
conceptual elements. Following are the brief descriptions of the structural things.
Class − Class represents a set of objects having similar responsibilities.
Interface − Interface defines a set of operations, which specify the responsibility of a class.
Collaboration −Collaboration defines an interaction between elements.
Use case −Use case represents a set of actions performed by a system for a specific goal.
43
Component −Component describes the physical part of a system.
Node − A node can be defined as a physical element that exists at run time.
BEHAVIORAL THINGS
A behavioral thing consists of the dynamic parts of UML models. Following are the behavioral
things −
Interaction − Interaction is defined as a behavior that consists of a group of messages

exchanged among elements to accomplish a specific task.
State machine − State machine is useful when the state of an object in its life cycle is
important. It defines the sequence of states an object goes through in response to events. Events
are external factors responsible for state change
GROUPING THINGS
Grouping things can be defined as a mechanism to group elements of a UML model together.
There is only one grouping thing available −
Package − Package is the only one grouping thing available for gathering structural and
behavioral things.
ANNOTATIONAL THINGS
Annotational things can be defined as a mechanism to capture remarks, descriptions, and

comments of UML model elements. Note - It is the only one Annotational thing available. A
note is used to render comments, constraints, etc. of an UML element.
44
RELATIONSHIP
Relationship is another most important building block of UML. It shows how the elements are
associated with each other and this association describes the functionality of an application.
There are four kinds of relationships available.
Dependency
Dependency is a relationship between two things in which change in one element also affects
the other.
Association
Association is basically a set of links that connects the elements of a UML model. It also
describes how many objects are taking part in that relationship.
Generalization
Generalization can be defined as a relationship which connects a specialized element with a

generalized element. It basically describes the inheritance relationship in the world of objects.
Realization
Realization can be defined as a relationship in which two elements are connected. One element
describes some responsibility, which is not implemented and the other one implements them.
This relationship exists in case of interfaces.
UML DIAGRAMS
UML diagrams are the ultimate output of the entire discussion. All the elements, relationships
are used to make a complete UML diagram and the diagram represents a system.
45
The visual effect of the UML diagram is the most important part of the entire process. All the
other elements are used to make it complete.
UML includes the following nine diagrams, the details of which are described in the subsequent
chapters.
 Class diagram
 Object diagram
 Use case diagram
 Sequence diagram
 Collaboration diagram
 Activity diagram
 Statechart diagram
 Deployment diagram
 Component diagram
We prepare UML diagrams to understand the system in a better and simple way. A single
diagram is not enough to cover all the aspects of the system. UML defines various kinds of
diagrams to cover most of the aspects of a system.
You can also create your own set of diagrams to meet your requirements. Diagrams are
generally made in an incremental and iterative way.
There are two broad categories of diagrams and they are again divided into subcategories −
 Structural Diagrams
 Behavioral Diagrams
Structural Diagrams
The structural diagrams represent the static aspect of the system. These static aspects represent
those parts of a diagram, which forms the main structure and are therefore stable.
These static parts are represented by classes, interfaces, objects, components, and nodes. The
four structural diagrams are −
 Class diagram
 Object diagram
 Component diagram
 Deployment diagram
Class Diagram
Class diagrams are the most common diagrams used in UML. Class diagram consists of
classes, interfaces, associations, and collaboration. Class diagrams basically represent the
object-oriented view of a system, which is static in nature.
Class diagram represents the object orientation of a system. Hence, it is generally used
for development purpose. This is the most widely used diagram at the time of system
construction.
46
Object Diagram
Object diagrams can be described as an instance of class diagram. Thus, these diagrams
are more close to real-life scenarios where we implement a system.
Object diagrams are a set of objects and their relationship is just like class diagrams.
They also represent the static view of the system.
The usage of object diagrams is similar to class diagrams but they are used to build
prototype of a system from a practical perspective.
Component Diagram
Component diagrams represent a set of components and their relationships. These

components consist of classes, interfaces, or collaborations. Component diagrams represent the
implementation view of a system.
During the design phase, software artifacts (classes, interfaces, etc.) of a system are
arranged in different groups depending upon their relationship. Now, these groups are known as
components.Finally, it can be said component diagrams are used to visualize the
implementation.
Deployment Diagram
Deployment diagrams are a set of nodes and their relationships. These nodes are physical
entities where the components are deployed.
Deployment diagrams are used for visualizing the deployment view of a system. This is
generally used by the deployment team..
Behavioral Diagrams
Any system can have two aspects, static and dynamic. So, a model is considered as
complete when both the aspects are fully covered.
Behavioral diagrams basically capture the dynamic aspect of a system. Dynamic aspect
can be further described as the changing/moving parts of a system.
UML has the following five types of behavioral diagrams −
 Use case diagram

 Sequence diagram
 Collaboration diagram
 Statechart diagram
 Activity diagram
Use Case Diagram
Use case diagrams are a set of use cases, actors, and their relationships. They represent
the use case view of a system.
47
A use case represents a particular functionality of a system. Hence, use case diagram is
used to describe the relationships among the functionalities and their internal/external
controllers. These controllers are known as actors.
Sequence Diagram
A sequence diagram is an interaction diagram. From the name, it is clear that the
diagram deals with some sequences, which are the sequence of messages flowing from one
object to another.
Interaction among the components of a system is very important from implementation

and execution perspective. Sequence diagram is used to visualize the sequence of calls in a
system to perform a specific functionality.
Collaboration Diagram
Collaboration diagram is another form of interaction diagram. It represents the structural

organization of a system and the messages sent/received. Structural organization consists of
objects and links.
The purpose of collaboration diagram is similar to sequence diagram. However, the

specific purpose of collaboration diagram is to visualize the organization of objects and their
interaction.
Statechart Diagram
Any real-time system is expected to be reacted by some kind of internal/external events.

These events are responsible for state change of the system.
Statechart diagram is used to represent the event driven state change of a system. It basically
describes the state change of a class, interface, etc.State chart diagram is used to visualize the
reaction of a system by internal/external factors.
Activity Diagram
Activity diagram describes the flow of control in a system. It consists of activities and
links. The flow can be sequential, concurrent, or branched.
Activities are nothing but the functions of a system. Numbers of activity diagrams are
prepared to capture the entire flow in a system.
Activity diagrams are used to visualize the flow of controls in a system. This is prepared
to have an idea of how the system will work when executed.
CLASS DIAGRAM
 Class diagram is a static diagram. It represents the static view of an application. Class
diagram is not only used for visualizing, describing, and documenting different aspects
of a system but also for constructing executable code of the software application.
48
Class diagram describes the attributes and operations of a class and also the constraints imposed
on the system. Class diagram shows a collection of classes, interfaces, associations,
collaborations, and constraints. It is also known as a structural diagram.
PURPOSE OF CLASS DIAGRAMS
Class diagrams are the only diagrams which can be directly mapped with object-oriented
languages and thus widely used at the time of construction.
UML diagrams like activity diagram, sequence diagram can only give the sequence flow
of the application, however class diagram is a bit different. It is the most popular UML diagram
in the coder community.
The purpose of the class diagram can be summarized as −
 Analysis and design of the static view of an application.

 Describe responsibilities of a system.
 Base for component and deployment diagrams.
 Forward and reverse engineering.
How to Draw a Class Diagram?
Class diagrams are the most popular UML diagrams used for construction of software
applications. It is very important to learn the drawing procedure of class diagram.
Class diagram is basically a graphical representation of the static view of the system and
represents different aspects of the application. A collection of class diagrams represent the
whole system.
The following points should be remembered while drawing a class diagram −
 The name of the class diagram should be meaningful to describe the aspect of the
system.
 Each element and their relationships should be identified in advance.
 Responsibility (attributes and methods) of each class should be clearly identified
 For each class, minimum number of properties should be specified, as unnecessary
properties will make the diagram complicated.
 Use notes whenever required to describe some aspect of the diagram. At the end of the
drawing it should be understandable to the developer/coder.
 Finally, before making the final version, the diagram should be drawn on plain paper and
reworked as many times as possible to make it correct.
The following diagram is an example of an Order System of an application. It describes a

particular aspect of the entire application.
 First of all, Order and Customer are identified as the two elements of the system. They
have a one-to-many relationship because a customer can have multiple orders.
 Order class is an abstract class and it has two concrete classes (inheritance relationship)
SpecialOrder and NormalOrder.
 The two inherited classes have all the properties as the Order class. In addition, they
have additional functions like dispatch () and receive ().
49
The following class diagram has been drawn considering all the points mentioned above.
Where to Use Class Diagrams?
.Class diagram clearly shows the mapping with object-oriented languages such as Java, C++,
etc. From practical experience, class diagram is generally used for construction purpose.
In a nutshell it can be said, class diagrams are used for −
 Describing the static view of the system.

 Showing the collaboration among the elements of the static view.
 Describing the functionalities performed by the system.
 Construction of software applications using object oriented languages.
USE CASE DIAGRAMS
PURPOSE OF USE CASE DIAGRAMS
The purpose of use case diagram is to capture the dynamic aspect of a system. However,
this definition is too generic to describe the purpose, as other four diagrams (activity, sequence,
collaboration, and Statechart) also have the same purpose. We will look into some specific
purpose, which will distinguish it from other four diagrams.
Use case diagrams are used to gather the requirements of a system including internal and
external influences. These requirements are mostly design requirements. Hence, when a system
is analyzed to gather its functionalities, use cases are prepared and actors are identified.
When the initial task is complete, use case diagrams are modelled to present the outside
view.
50
In brief, the purposes of use case diagrams can be said to be as follows −
 Used to gather the requirements of a system.

 Used to get an outside view of a system.
 Identify the external and internal factors influencing the system.
 Show the interaction among the requirements are actors.
HOW TO DRAW A USE CASE DIAGRAM?
Use case diagrams are considered for high level requirement analysis of a system. When
the requirements of a system are analyzed, the functionalities are captured in use cases.
We can say that use cases are nothing but the system functionalities written in an
organized manner. The second thing which is relevant to use cases are the actors. Actors can be
defined as something that interacts with the system.
Actors can be a human user, some internal applications, or may be some external
applications. When we are planning to draw a use case diagram, we should have the following
items identified.
 Functionalities to be represented as use case

 Actors
 Relationships among the use cases and actors.
Use case diagrams are drawn to capture the functional requirements of a system. After
identifying the above items, we have to use the following guidelines to draw an efficient use
case diagram
 The name of a use case is very important. The name should be chosen in such a way so
that it can identify the functionalities performed.
 Give a suitable name for actors.
 Show relationships and dependencies clearly in the diagram.
 Do not try to include all types of relationships, as the main purpose of the diagram is to
identify the requirements.
 Use notes whenever required to clarify some important points.
Following is a sample use case diagram representing the order management system. Hence, if
we look into the diagram then we will find three use cases (Order, SpecialOrder, and
NormalOrder) and one actor which is the customer.
The SpecialOrder and NormalOrder use cases are extended from Order use case. Hence, they
have extended relationship. Another important point is to identify the system boundary, which is
shown in the picture. The actor Customer lies outside the system as it is an external user of the
system.
51
WHERE TO USE A USE CASE DIAGRAM?
Use case diagrams specify the events of a system and their flows. But use case diagram
never describes how they are implemented. Use case diagram can be imagined as a black box
where only the input, output, and the function of the black box is known.
These diagrams are used at a very high level of design. This high level design is refined
again and again to get a complete and practical picture of the system. A well-structured use case
also describes the pre-condition, post condition, and exceptions. These extra elements are used
to make test cases when performing the testing.
Although use case is not a good candidate for forward and reverse engineering, still they
are used in a slightly different way to make forward and reverse engineering. The same is true
for reverse engineering. Use case diagram is used differently to make it suitable for reverse
engineering.
In forward engineering, use case diagrams are used to make test cases and in reverse
engineering use cases are used to prepare the requirement details from the existing application.
Use case diagrams can be used for −
 Requirement analysis and high level design.

 Model the context of a system.
 Reverse engineering.
 Forward engineering.
INTERACTION DIAGRAM
From the term Interaction, it is clear that the diagram is used to describe some type of
interactions among the different elements in the model. This interaction is a part of dynamic
behavior of the system.
52
This interactive behavior is represented in UML by two diagrams known as Sequence
diagram and Collaboration diagram. The basic purpose of both the diagrams. are similar
Sequence diagram emphasizes on time sequence of messages and collaboration diagram

emphasizes on the structural organization of the objects that send and receive messages.
PURPOSE OF INTERACTION DIAGRAMS
The purpose of interaction diagrams is to visualize the interactive behavior of the

system. Visualizing the interaction is a difficult task. Hence, the solution is to use different types
of models to capture the different aspects of the interaction.
Sequence and collaboration diagrams are used to capture the dynamic nature but from a
different angle.
The purpose of interaction diagram is −
 To capture the dynamic behaviour of a system.

 To describe the message flow in the system.
 To describe the structural organization of the objects.
 To describe the interaction among objects.
HOW TO DRAW AN INTERACTION DIAGRAM?
The purpose of interaction diagrams is to capture the dynamic aspect of a system. So to

capture the dynamic aspect, we need to understand what a dynamic aspect is and how it is
visualized. Dynamic aspect can be defined as the snapshot of the running system at a particular
moment
We have two types of interaction diagrams in UML. One is the sequence diagram and
the other is the collaboration diagram. The sequence diagram captures the time sequence of the
message flow from one object to another and the collaboration diagram describes the
organization of objects in a system taking part in the message flow.
Following things are to be identified clearly before drawing the interaction diagram
Message flows among the objects.

The sequence Objects taking part in the interaction.
in which the messages are flowing.
Object organization.
Following are two interaction diagrams modeling the order management system. The first
diagram is a sequence diagram and the second is a collaboration diagram.
WHERE TO USE INTERACTION DIAGRAMS?
We have already discussed that interaction diagrams are used to describe the dynamic
nature of a system. Now, we will look into the practical scenarios where these diagrams are
used. To understand the practical application, we need to understand the basic nature of
sequence and collaboration diagram.
53
The main purpose of both the diagrams are similar as they are used to capture the dynamic
behavior of a system. However, the specific purpose is more important to clarify and
understand.
Sequence diagrams are used to capture the order of messages flowing from one object to
another. Collaboration diagrams are used to describe the structural organization of the objects
taking part in the interaction. A single diagram is not sufficient to describe the dynamic aspect
of an entire system, so a set of diagrams are used to capture it as a whole.
Interaction diagrams are used when we want to understand the message flow and the structural
organization. Message flow means the sequence of control flow from one object to another.
Structural organization means the visual organization of the elements in a system.
Interaction diagrams can be used −
 To model the flow of control by time sequence.

 To model the flow of control by structural organizations.
 For forward engineering.
 For reverse engineering.
THE SEQUENCE DIAGRAM
The sequence diagram has four objects (Customer, Order, SpecialOrder and
NormalOrder).
The following diagram shows the message sequence for SpecialOrder object and the
same can be used in case of NormalOrder object. It is important to understand the time
sequence of message flows. The message flow is nothing but a method call of an object.
The first call is sendOrder () which is a method of Order object. The next call is confirm
() which is a method of SpecialOrder object and the last call is Dispatch () which is a method of
SpecialOrder object. The following diagram mainly describes the method calls from one object
to another, and this is also the actual scenario when the system is running.
54
The Collaboration Diagram
The second interaction diagram is the collaboration diagram. It shows the object
organization as seen in the following diagram. In the collaboration diagram, the method call
sequence is indicated by some numbering technique. The number indicates how the methods are
called one after another. We have taken the same order management system to describe the
collaboration diagram.
Method calls are similar to that of a sequence diagram. However, difference being the
sequence diagram does not describe the object organization, whereas the collaboration diagram
shows the object organization.
To choose between these two diagrams, emphasis is placed on the type of requirement. If
the time sequence is important, then the sequence diagram is used. If organization is required,
then collaboration diagram is used.
WHERE TO USE INTERACTION DIAGRAMS?
Sequence diagrams are used to capture the order of messages flowing from one object to
another. Collaboration diagrams are used to describe the structural organization of the objects
taking part in the interaction. A single diagram is not sufficient to describe the dynamic aspect
of an entire system, so a set of diagrams are used to capture it as a whole.
55
Interaction diagrams are used when we want to understand the message flow and the
structural organization. Message flow means the sequence of control flow from one object to
another. Structural organization means the visual organization of the elements in a system.
Interaction diagrams can be used −
 To model the flow of control by time sequence.

 To model the flow of control by structural organizations.
 For forward engineering.
 For reverse engineering.
STATECHART DIAGRAM
 A Statechart diagram describes a state machine. State machine can be defined as a

machine which defines different states of an object and these states are controlled by
external or internal events.
 As Statechart diagram defines the states, it is used to model the lifetime of an object.
PURPOSE OF STATECHART DIAGRAMS
Statechart diagram is one of the five UML diagrams used to model the dynamic nature
of a system. They define different states of an object during its lifetime and these states are
changed by events.
Statechart diagrams are useful to model the reactive systems. Reactive systems can be
defined as a system that responds to external or internal events.
Statechart diagram describes the flow of control from one state to another state. States
are defined as a condition in which an object exists and it changes when some event is triggered.
The most important purpose of Statechart diagram is to model lifetime of an object from
creation to termination.
Statechart diagrams are also used for forward and reverse engineering of a system.
However, the main purpose is to model the reactive system.
Following are the main purposes of using Statechart diagrams −
 To model the dynamic aspect of a system.

 To model the life time of a reactive system.
 To describe different states of an object during its life time.
 Define a state machine to model the states of an object.
HOW TO DRAW A STATECHART DIAGRAM
Statechart diagram is used to describe the states of different objects in its life cycle.
Statechart diagrams are very important for describing the states. States can be identified
as the condition of objects when a particular event occurs.
Before drawing a Statechart diagram we should clarify the following points −

56
o Identify the important objects to be analyzed.
o Identify the states.
o Identify the events.
Following is an example of a Statechart diagram where the state of Order object is analyzed
The first state is an idle state from where the process starts. The next states are arrived for events
like send request, confirm request, and dispatch order. These events are responsible for the state
changes of order object.
WHERE TO USE STATECHART DIAGRAMS?
Statechart diagram defines the states of a component and these state changes are
dynamic in nature. Its specific purpose is to define the state changes triggered by events. Events
are internal or external factors influencing the system.
Statechart diagrams are used to model the states and also the events operating on the
system. When implementing a system, it is very important to clarify different states of an object
during its life time and Statechart diagrams are used for this purpose. When these states and
events are identified, they are used to model it and these models are used during the
implementation of the system.
If we look into the practical implementation of Statechart diagram, then it is mainly used
to analyze the object states influenced by events. This analysis is helpful to understand the
system behavior during its execution.
The main usage can be described as −
o To model the object states of a system.

o To model the reactive system. Reactive system consists of reactive objects.
o To identify the events responsible for state changes.
57
o Forward and reverse engineering.
ACTIVITY DIAGRAM
Activity diagram is another important diagram in UML to describe the dynamic aspects
of the system.
Activity diagram is basically a flowchart to represent the flow from one activity to
another activity. The activity can be described as an operation of the system.
The control flow is drawn from one operation to another. This flow can be sequential,
branched, or concurrent. Activity diagrams deal with all type of flow control by using different
elements such as fork, join, etc
Purpose of Activity Diagrams
The basic purposes of activity diagrams is similar to other four diagrams. It captures the
dynamic behavior of the system. Other four diagrams are used to show the message flow from
one object to another but activity diagram is used to show message flow from one activity to
another.
Activity is a particular operation of the system. Activity diagrams are not only used for
visualizing the dynamic nature of a system, but they are also used to construct the executable
system by using forward and reverse engineering techniques. The only missing thing in the
activity diagram is the message part.
It does not show any message flow from one activity to another. Activity diagram is
sometimes considered as the flowchart. Although the diagrams look like a flowchart, they are
not. It shows different flows such as parallel, branched, concurrent, and single.
The purpose of an activity diagram can be described as −
 Draw the activity flow of a system.

 Describe the sequence from one activity to another.
 Describe the parallel, branched and concurrent flow of the system.
How to Draw an Activity Diagram?
Activity diagrams are mainly used as a flowchart that consists of activities performed by
the system. Activity diagrams are not exactly flowcharts as they have some additional
capabilities. These additional capabilities include branching, parallel flow, swimlane, etc.
Before drawing an activity diagram, we must have a clear understanding about the
elements used in activity diagram. The main element of an activity diagram is the activity itself.
An activity is a function performed by the system. After identifying the activities, we need to
understand how they are associated with constraints and conditions.
Before drawing an activity diagram, we should identify the following elements −
Activities
58
Association
Conditions
Constraints
Once the above-mentioned parameters are identified, we need to make a mental layout of the
entire flow. This mental layout is then transformed into an activity diagram.
Following is an example of an activity diagram for order management system. In the diagram,
four activities are identified which are associated with conditions. One important point should
be clearly understood that an activity diagram cannot be exactly matched with the code. The
activity diagram is made to understand the flow of activities and is mainly used by the business
users
Following diagram is drawn with the four main activities −
Send order by the customer

Receipt of the order
Confirm the order
Dispatch the order
After receiving the order request, condition checks are performed to check if it is normal or
special order. After the type of order is identified, dispatch activity is performed and that is
marked as the termination of the process.
Where to Use Activity Diagrams?
The basic usage of activity diagram is similar to other four UML diagrams. The specific
usage is to model the control flow from one activity to another. This control flow does not
include messages.
Activity diagram is suitable for modeling the activity flow of the system. An application can
have multiple systems. Activity diagram also captures these systems and describes the flow
59
from one system to another. This specific usage is not available in other diagrams. These
systems can be database, external queues, or any other system.
This diagram is used to model the activities which are nothing but business requirements. The
diagram has more impact on business understanding rather than on implementation details.
Activity diagram can be used for −
 Modeling work flow by using activities.

 Modeling business requirements.
 High level understanding of the system's functionalities.
 Investigating business requirements at a later stage.
COMPONENT DIAGRAM
Component diagrams are different in terms of nature and behavior. Component diagrams
are used to model the physical aspects of a system. Physical aspects are the elements such as
executables, libraries, files, documents, etc. which reside in a node.
Component diagrams are used to visualize the organization and relationships among
components in a system. These diagrams are also used to make executable systems.
Purpose of Component Diagrams
Component diagram is a special kind of diagram in UML. The purpose is also different
from all other diagrams discussed so far. It does not describe the functionality of the system but
it describes the components used to make those functionalities.
Thus from that point of view, component diagrams are used to visualize the physical
components in a system. These components are libraries, packages, files, etc.
Component diagrams can also be described as a static implementation view of a system.

Static implementation represents the organization of the components at a particular moment.
A single component diagram cannot represent the entire system but a collection of
diagrams is used to represent the whole.
The purpose of the component diagram can be summarized as −
 Visualize the components of a system.

 Construct executables by using forward and reverse engineering.
 Describe the organization and relationships of the components.
How to Draw a Component Diagram?
Component diagrams are used to describe the physical artifacts of a system. This artifact
includes files, executables, libraries, etc
The purpose of this diagram is different. Component diagrams are used during the
implementation phase of an application. However, it is prepared well in advance to visualize the
implementation details.
60
Initially, the system is designed using different UML diagrams and then when the
artifacts are ready, component diagrams are used to get an idea of the implementation.
This diagram is very important as without it the application cannot be implemented

efficiently. A well-prepared component diagram is also important for other aspects such as
application performance, maintenance, etc.
Before drawing a component diagram, the following artifacts are to be identified clearly −
 Files used in the system.

 Libraries and other artifacts relevant to the application.
 Relationships among the artifacts.
After identifying the artifacts, the following points need to be kept in mind.
 Use a meaningful name to identify the component for which the diagram is to be drawn.
 Prepare a mental layout before producing the using tools.
 Use notes for clarifying important points.
Following is a component diagram for order management system. Here, the artifacts are
files. The diagram shows the files in the application and their relationships. In actual, the
component diagram also contains dlls, libraries, folders, etc.
In the following diagram, four files are identified and their relationships are produced.
Component diagram cannot be matched directly with other UML diagrams discussed so far as it
is drawn for completely different purpose.
The following component diagram has been drawn considering all the points mentioned
above.
Where to Use Component Diagrams?

61
We have already described that component diagrams are used to visualize the static
implementation view of a system. Component diagrams are special type of UML diagrams used
for different purposes.
These diagrams show the physical components of a system. To clarify it, we can say that
component diagrams describe the organization of the components in a system.
Organization can be further described as the location of the components in a system.

These components are organized in a special way to meet the system requirements.
As we have already discussed, those components are libraries, files, executables, etc.
Before implementing the application, these components are to be organized. This component
organization is also designed separately as a part of project execution.
Component diagrams are very important from implementation perspective. Thus, the
implementation team of an application should have a proper knowledge of the component
details
Component diagrams can be used to −
 Model the components of a system.

 Model the database schema.
 Model the executables of an application.
 Model the system's source code.
DEPLOYMENT DIAGRAM
Deployment diagrams are used to visualize the topology of the physical components of a
system, where the software components are deployed.
Deployment diagrams are used to describe the static deployment view of a system.
Deployment diagrams consist of nodes and their relationships.
Purpose of Deployment Diagrams
The term Deployment itself describes the purpose of the diagram. Deployment diagrams
are used for describing the hardware components, where software components are deployed.
Component diagrams and deployment diagrams are closely related.
Component diagrams are used to describe the components and deployment diagrams
shows how they are deployed in hardware.
UML is mainly designed to focus on the software artifacts of a system. However, these
two diagrams are special diagrams used to focus on software and hardware components.
Most of the UML diagrams are used to handle logical components but deployment
diagrams are made to focus on the hardware topology of a system. Deployment diagrams are
used by the system engineers.
The purpose of deployment diagrams can be described as −
o Visualize the hardware topology of a system.

62
o Describe the hardware components used to deploy software components.
o Describe the runtime processing nodes.
How to Draw a Deployment Diagram?
Deployment diagram represents the deployment view of a system. It is related to the

component diagram because the components are deployed using the deployment diagrams. A
deployment diagram consists of nodes. Nodes are nothing but physical hardware used to deploy
the application.
Deployment diagrams are useful for system engineers. An efficient deployment diagram is
very important as it controls the following parameters −
 Performance
 Scalability
 Maintainability
 Portability
Before drawing a deployment diagram, the following artifacts should be identified −
Nodes
Relationships among nodes
Following is a sample deployment diagram to provide an idea of the deployment view of order
management system. Here, we have shown nodes as −
 Monitor
 Modem
 Caching server
 Server
The application is assumed to be a web-based application, which is deployed in a clustered

environment using server 1, server 2, and server 3. The user connects to the application using
the Internet. The control flows from the caching server to the clustered environment.
The following deployment diagram has been drawn considering all the points mentioned above.
63
Where to Use Deployment Diagrams?
Deployment diagrams are mainly used by system engineers. These diagrams are used to
describe the physical components (hardware), their distribution, and association.
Deployment diagrams can be visualized as the hardware components/nodes on which the

software components reside.
Software applications are developed to model complex business processes. Efficient

software applications are not sufficient to meet the business requirements. Business
requirements can be described as the need to support the increasing number of users, quick
response time, etc.
To meet these types of requirements, hardware components should be designed

efficiently and in a cost-effective way.
Now-a-days software applications are very complex in nature. Software applications can
be standalone, web-based, distributed, mainframe-based and many more. Hence, it is very
important to design the hardware components efficiently.
Deployment diagrams can be used −
 To model the hardware topology of a system.

 To model the embedded system.
 To model the hardware details for a client/server system.
 To model the hardware details of a distributed application.
64
 For Forward and Reverse engineering.
65
66

Case Tool Alignment

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 Tool Alignment

Uploaded by

Copyright:

Available Formats

PIONEER COLLEGE OF ARTS AND SCIENCE CASE TOOLS

CASE TOOLS CONCEPTS AND APPLICATIONS

Components of CASE Tools

The scope of CASE tools goes throughout the SDLC.

Case Tools Types

Now we briefly go through various CASE tools

Process Modeling Tools

Project Management Tools

 Version and revision management

Change Control Tools

These tools consist of programming environments like IDE (Integrated Development

Web Development Tools

Quality Assurance Tools

Software maintenance includes modifications in the software product after it is delivered.

CASE Tools and its scope

 Requirement Analysis Tool

CASE Tools in future…

Horizontal and Vertical Division of AO-groups

Knowledge Representation and Processing

Visual Integration of CASE Tools

Work Flow Model

A STUDENT MIS SYSTEM

WHAT IS THE PURPOSE OF SUCH MODELS

UNDERSTANDING THE BUSINESS

The case for structures development

SYSTEMS ANALYSIS AND DESIGN

System Design focuses on how to accomplish the objective of the system.

System Analysis and Design (SAD) mainly focuses on −

What is a data flow diagram (DFD)?

DATA FLOW DIAGRAM

What’s the difference between a logical DFD and a physical DFD?

• Holds complete information to develop a system from initiation to maintenance

• Supports team is development

CASE ANALYSIS TOOLS

• Analyse items stored in the repository for consistency & completeness

• includes diagrams, data, process flows and reports

• Analysis tools often may be customised

CASE DOCUMENTATION GENERATORS

• technical & user documents in standard formats

• helps manage large amounts of documentation generated during Systems

• reduces “retrospective” documenting of system

• high quality documentation reduces maintenance costs/effort

• standard programming language conventions

• compiled on different platforms with different operating systems

• e.g. the IBM Rational Rose suite includes tools which:

• in C++, Visual Basic, Java etc.;

• reverse engineer from many of these;

• trace requirements from model to code;

• model integrator / check model

• guide the development process.

• e.g. the ASCENT suite developed at UoT

BENEFITS OF USING CASE TOOLS

• Syntax/completeness checks ensure consistency

• Amending/updating achieved far more easily

• documentation can be kept up-to-date

• beneficial effect on maintenance

• More rapid development

• more feasible to develop & evaluate alternative designs

• Capture of system data for reuse

• particularly important for OO development

• May guide the use of a methodology

• Clearer communication with users

• Continuity of development with changing staff

• Standardised quality assurance/test procedures