ASSIGNMENT

OF

Analysis And Design of

Information System (CSE02)

HOMEWORK: 3

SUBMITTED TO: SUBMITTED BY

Mr. Tara Chand Verma Arun
RE2803A09
10808035
Q2: Define various element of Designing of system application i.e Input, Control,
Procedures,Program Specifications with suitable example.

Manage Customers' Expectations

When developing a prototype, customers are encouraged to participate and offer

constructive comments and suggestions. Upon seeing the completed prototype, however,
customers may expect to see a working system almost immediately. It is important to
manage customers' expectations. For example:
Ensure the customer understands the purpose and scope of the prototype. Clarify the
amount of work involved in full development.

Ensure the customer understands that they should identify potential flaws in the prototype
to ensure accuracy, even though it is not a complete system.

Q5: The use of CASE tools decides by whom? What are the various criteria to choose any
specific CASE tool for the given phase?

Ans:- Ans: The ISDOS project at the University of Michigan initiated a great deal of
interest in the whole concept of using computer systems to help analysts in the very
difficult process of analysing requirements and developing systems. Several papers by
Daniel Teichroew fired a whole generation of enthusiasts with the potential of automated
systems development. His PSL/PSA tool was a CASE tool although it predated the term.
His insights into the power of meta-meta-models was inspiring, particularly to a former
student, Dr. Hasan Sayani, currently Professor, Program Director at University of
Maryland University College. All aspects of the software development life cycle can be
supported by software tools, and so the use of tools from across the spectrum can,
arguably, be described as CASE; from project management software through tools for
business and functional analysis, system design, code storage, compilers, translation
tools, test software, and so on.
However, tools that are concerned with analysis and design, and with using design
information to create parts (or all) of the software product, are most frequently thought of
as CASE tools. CASE applied, for instance, to a database software product, might
normally involve:
• Modeling business / real-world processes and data flow
• Development of data models in the form of entity-relationship diagrams
• Development of process and function descriptions
CASE software supports the software process activities such as requirement engineering,
design, program development and testing. Therefore, CASE tools include design editors,
data dictionaries, compilers, debuggers, system building tools, etc.CASE also refers to
the methods dedicated to an engineering discipline for the development of information
system using automated tools.CASE is mainly used for the development of quality
software which will perform effectively.

Q3: In what kind of situations we use CASE tools. What are the various categories
of CASE tools? Can we use different tools for different levels of application
development?

Components of CASE Tools

CASE Tools are made up of a number of components, depending upon their category and
complexity. The six components are Diagramming Tools, Analysis Tools, Repository,
Code Generators, Form and Report Generators and Documentation Generators

Diagramming Tools
Diagramming Tools are the fundamental and indispensable component of a CASE Tool.
Systems can be modeled in a graphical form using Diagramming Tools. Outputs from
techniques such as data modeling and process modeling can generally be produced more
quickly with a CASE Tool than by hand.

Analysis Tools
Analysis Tools are the component of a CASE Tool that differentiates a CASE Tool from
a graphics package. With Analysis Tools a diagram can be automatically checked for
inconsistencies, incomplete aspects or incorrect specifications using rules applicable to
that diagram. This component is particularly useful when combining the work of several
systems analysts.

Repository
The Repository is the component of a CASE Tool that contains all the information on the
diagrams generated by the CASE Tool. The Repository generally consists of two
segments, the Information Repository and Data Dictionary. The Information Repository
contains details of all the models and parts of the models, whilst the Data Dictionary
contains the details of each data item in each part of each model.

Q1: Why we iterate the system development life cycle process when we build
prototype too? What issues may arise with these iteration processes when we
examine real application rather than prototype?

Prototype is a working system. It is developed to test the ideas and assumptions about the
new system. It consists of working software that accepts input, performs calculations,
procedures printed or displayed information, or performs other meaningful activities. The
prototyping process includes the following steps: gather preliminary requirements,
identify participants, select prototyping tools, complete overhead tasks, build the
prototype, manage expectations. Gather Preliminary Requirements in this the prototype is
initially developed from preliminary requirements gathered from the
customer. Functional requirements usually focus on the key input and output data, as
well as the principal data groups. For example, a prototype inventory system may
include stock issues and receipts, a supplier file, and a file containing rudimentary parts
information.

Identify Participants

Keep the number of people working on a prototype small. As a rule of thumb, identify a
maximum of two people. Involve at least one member from the customer
organization. To accelerate the prototyping effort, the prototype developer(s) should be
skilled in the tool selected and knowledgeable of the application.

Q4: What Objectives should an analyst seek to achieve when formulating the design
of an information system?

The questions that an analyst uses to guide the process are

1. What problem is this system having that you hope to solve by developing this project

2. What is the project doing at present to alleviate or solve the issue? What has been tried
in the past?

3. What inside resources will this project be utilizing?

4. Have you determined a vision for the project?

5. What risks to you foresee and are you willing to take them?

6. Are you under any type of time constraint?

7. What is the projected cost of the program?

8. Who is the end user? What support will they have?

After assessing the quality of the data and of the measurements, one might decide to
impute missing data, or to perform initial transformations of one or more variables,
although this can also be done during the main analysis phase.
Final stage of the initial data analysis
During the final stage, the findings of the initial data analysis are documented, and
necessary, preferable, and possible corrective actions are taken.

Q6: Discuss the manner in which CASE tools integrated. What is the meaning of
integration here?

ANS:- The front end tools are responsible for collecting input in various forms from the
user and processing it to conform to a specification the back end can use. The front end is
an interface between the user and the back end.
• They are responsible for the early acticities in system development process

• They support the development of graphic models.

• DFD are one of the best example o are the best representatives of the front end
tools.

Back end is purely implemtation part. Back-end tools seek front-end

companions; vendors work to make code generators an integrated component in the
tool suite - includes related articles on code generators
• They are aimed at assisting the analyst in the formulation of programe
logic,processing algo and the physical description of data
• Convert software logic designs into the actual programme code.