LOVELY PROFESSIONAL

UNVERSITY

CAP302

Analysis and design of Information

System

Homework#3

Submitted to: Submitted by:

Amandeep Mam Rahul Pandey
RD-3901-A-15
Reg no.-10903849
Q-1 Data dictionary is interrelated with steps of SDLC in project
development. Justify giving examples?

Ans :
Data dictionary is interrelated with steps of SDLC in project
development because:--

a) Data dictionary are integral components of structured analysis; since

data flow diagrams by themselves do not fully describe a subject of the
investigation.

b) A data dictionary is a catalog-a repository of the element in the

system.

c) In data dictionary one will find a list of all the elements composing the
data flowing through a system. The major elements are –
• Data flows
• Data stores
• Processes
•
d) The dictionary is developed during data flows analysis and assist the
analysis Involved in determining system requirements and its content are
used during System design as well.

e) The data dictionary contains the following description about the data:-
• The name of the data element.
• The physical source/ Destination name.
• The type of the data element.
• The size of data element.
• Usage such as input or output or update etc
• Reference(/s) of DFD process nos, where used.
• Any special information useful for system specification such as
validation rules etc.
f) this is appropriately called as system development data dictionary, Since
it is created during the system development, facilitating the
development functions, used by the developers and is designed for the
developers information needs in mind.

g) for every single data element mentioned in the DFD there should be at
least one and only one unique data element in the data dictionary.

h) the type of data elements is considered as numeric, textual or image,

audio etc

i) usage should specify whether the referenced DFD process uses it as

input data(only read) or creates data output (e.g Insert) or update.

j) a data element can be mentioned with reference to multiple DFD

processes but in that case if the usages are different , then there
should be one entry for each usage.

k) the data dictionary is used as an important basic information during the

development stages.

l) Importance of data dictionary:

• To manage the details in large system.
• To communicate a common meaning for all system elements.
• To document the features of the system.
• To facilitate analysis of the details in order to evaluate
characteristics and determine where system changes should be
made.
• To locate errors and omissions in the system.

m) Points to be considered while constructing a data dictionary

• Each unique data flow in the DFD must have one data dictionary
entry. There is also a data dictionary entry for each data store
and process.
• Definition must be readily accessible by name.
• There should be no redundancy or unnecessary definition in the
data definitions. It must also be simple to make updates.
 • The procedures for writing definitions should be straightforward
but specific there should be only one way of defining words.

Q-2 Draw a Data Flow diagram for University management system (UMS).

Ans :
Q-3 CASE tools improve effectiveness and productivity of the analyst. How?
What can be impact of using CASE tools on quality of a software product?

Ans :
Benefits of using Case Tools :--
CaseTools extend the capability of the systems analyst. They provide
the potential to improve the productivity of the analyst, facilitate more
effective procedures, and improve system quality. In other words, both
the process of systems development and the product that results can
be improved through the use of proper tools.

Improve Productivity: -
With the right tools, the analyst has the potential to be more
productive; the same development activities can be completed in less
time than when tools are not used. Tools increase the analyst’s
productivity by reducing the amount of time needed to document,
analyze, and construct information systems. When used properly, they
increase the analyst’s efficiency.
Provoke
Improve Effectiveness: -
Tools suggest procedures, leading to the use of more effective
processes. If productivity means doing the task right i.e. improved
productivity, effectiveness means doing the right task i.e.deciding the
best task to perform to achieve a result. Tools can suggest the right
way to approach a task.

Improve System Quality: -

Users of information systems want the same thing : a quality system
delivered in a reasonable length of time. At one time, there were very
few tools. Thus, application prototyping was not possible, and neither
was structured analysis. The invention of fourth-generation languages
and dataflow diagrams- two essential tools for these respective
activities, changed systems analysis procedures in organizations.
OBJECTIVES OF USING CASE Tools :

1. Improve Productivity:
Most organizations use CASE to increase the speedswith which systems
are designed and developed. Imagine the difficultiescarpenters would face
without hammers and saws. Tools increase the analysts’productivity by reducing
the time needed to document, analyze, and constructan information
system.

2. Improve Information System Quality: When tools improve processes,

they usually improve the results as well as they:

(i). Ease and improve the testing process through the use of
automatedchecking.
(ii). Improve the integration of development activities via common method-
ologies.
(iii). Improve the quality and completeness of documentation.
(iv). Help standardize the development process.
(v). Improve the management of the project.
(vi). Simplify program maintenance.
(vii). Promote reversibility of modules and documentation.
(viii). Shorten the overall construction process.
(ix). Improve software portability across environments.
(x). Through reverse engineering and re-engineering, CASE products
extend the files of existing systems.Despite the various driving forces (objectives)
for the adoption of CASE,there are many resisting forces that also preclude many
organizations from investing in CASE.

3. Improve Effectiveness:
Effectiveness means doing the right task (i.e.,deciding the best task to
perform to achieve the desired result). Tools can suggest procedures (the
right way) to approach a task. Identifying userrequirements, stating them
 in an understandable form, and communicatingthem to all interested
parties can be an effective development process.

4. Organizations Reject CASE Because:

• The start-up cost of purchasing and using CASE.

• The high cost of training personnel.
• The big benefits of using CASE come in the late stages of the SDLC.
• CASE often lengthens the duration of the early stage of the project.
• CASE tools cannot easily share information between tools.
• Lack of methodology standards within organizations. CASE products force
analysts to follow a specific methodology for system development.
• Lack of confidence in CASE products.
• IS personnel view CASE as a threat to their job security.

Despite these issues, in the long-term, CASE is very good. The functionality
ofCASE tools is increasing and the costs are coming down. During the next
severalyears, CASE technologies and the market for CASE will begin to mature
 PART-B

Q-4 A woolen manufacturer, without compromising in quality and by keeping

the sales same, can increase his profit. How a software could help him to do
so and at what places?

Ans :

Software and ICT play a significant part in enabling an effective CRM capability,
especially in large organizations.

There are many and various systems available, and it is important to have a clear
idea of your requirements during the software solution selection process, which for
most organizations will also involve the selection of ICT service provider too, since
any software solution, for all but very small companies, generally requires support
for specifying, implementation, training and maintenance.

Siebel, Sage (who now provide the well-known Accpac and ACT! CRM solutions), and
Front Range (whose product is Goldmine) are all significant and proven CRM
software products companies. There are many others, and very many more ICT
service providers through whom distribution and support is normally arranged.

As with any ICT project, ensure you work with reliable and knowledgeable advisors,
with access to cost-effective proven solutions, who can help you to build and
implement an effective CRM software and ICT capability.
Q-5 Take a real life system and apply prototype approach and describe the
steps that would be followed in the approach.
Ans :

• The system prototype method involves the user more directly in the analysis
& design experience than does the SDLC or structured analysis method.

• A prototype is working sys – not just an idea on paper – that is developed to

test ideas and assumption about the new system. Like any computer based
sys it consists of working software that accepts input, performs calculations,
produces printed or displayed information or performs other meaningful
activities.it is the first version or iteration of an information system an
original model.

• The design and the information produced by the system are evaluated by
users. This can be effectively done only if the data are real & the situations
live. Changes are expected as the system is used

Reasons for system prototyping:

• Information requirements are not always well defined. Users may know only
that certain biz areas need improvement or that existing procedures must be
changed. Or they may know that they need better information for managing
certain activities but are not sure what that info is.
• The user’s requirements might be too vague to even begin formulating a
design. In other cases, a well managed systems investigations may produce a
comprehensive set of sys requirements, but building a sys that will meet
those requirements may require development of new technology.

• Unique situations, about which developers have neither info nor experience,
and high cost or high risk situations in the proposed design is new and
untested, are often evaluated through prototypes.
 • The prototype is actually a pilot or test model; the design evolves through
use.

• Although the prototype is working system, it is designed to be easily

changed. Information gained through its use is applied to a modified design
that may again be used as a prototype to reveal still more valuable design
information.

• The process is repeated as many times as necessary to reveal essential

design requirement.

• System prototyping is an interactive process. It begins with only few

functions and be expanded to include others that are identified later.

Steps in the prototyping process:

1. Identify the user’ known information requirements and features needed in

the system.
2. Develop a working prototype
3. Use the prototype, noting needed enhancements and changes. These expand
the list of known sys requirements
4. Revise the prototype based on info gained through user experience
5. Repeat these steps as needed to achieve a satisfactory system.
Q-6 Why various development activities are important to be carried out
during structured analysis?

Ans :

Various development activities are important to be carried out

during structured analysis to:--

• Ensure that projects can successfully continue should a loss of staff occur
without a damaging effect on the project.
• Develop overall better quality systems
• Improve the way in which projects are controlled and managed
• Allow more effective use of experienced and inexperienced staff and their
Development.
• Make it possible for projects to be supported by computer based tools e.g.
computer-aided software engineering systems.
• Improve communication between participants in a project so an effective
framework is in place.

Benefits :

 Timelines: Theoretically, SSADM allows one to plan, manage and control a

project well. These points are essential to deliver the product on time.

 Usability: Within SSADM special emphasis is put on the analysis of user

needs. Simultaneously, the systems model is developed and a comprehensive
demand analysis is carried out. Both are tried to see if they are well suited
 to each other. Respond to changes in the business environment. As in SSADM
documentation of the project’s progress is taken very seriously, issues like
business objectives and business needs are considered while the project is
being developed. This offers the possibility to tailor the planning of the
project to the actual requirements of the business.

 Effective use of skills: SSADM does not require very special skills and can
easily be taught to the staff. Normally, common modelling and diagramming
tools are used. Commercial CASE tools are also offered in order to be able to
set up SSADM easily. Better quality: SSADM reduces the error rate of IS
by defining a certain quality level in the beginning and constantly checking
the system.

 Improvement of productivity: By encouraging on-time delivery, meeting

business requirements, ensuring better quality, using human resources
effectively as well as trying to avoid bureaucracy, SSADM improves the
overall productivity of the specific project and the company.

 Cuts costs: SSADM separates the logical and the physical systems design.
So the system does not have to be implemented again with new hard -or
software.