COMPUTER AND ITS

APPLICATION IN PHARMACY
Module: System Analysis and
Design
(Development of Information Systems)

Rana M. Ajmal
[email protected]

1
Objectives Overview
Activities that occur
System development Guidelines for system
during system
phases development
development

Steps in the program

Activities performed Differentiate between
development life cycle
during each system structured design and
and tools used to make
development phase object-oriented design
this process efficient

Explain the basic control

structures and design
tools used in designing
solutions to
programming problems

2
 System Development

System development is a set of activities

used to build an information system
An information
A system is a set of system (IS) is a System development
components that collection of activities are grouped
interact to achieve a hardware, software, into phases, and is
common goal. data, people, and called the system
Businesses uses many procedures that work development life
types of systems together to produce cycle (SDLC)
quality information

3
System Development Life Cycle
SDLC

4
 System Development
 System development should follow three
general guidelines:

Group activities or tasks into phases

Involve users (anyone for whom system is

built)

Develop clearly define standards

(procedures company employees to follow)
5
 System Development
 System development should involve representatives from
each department in which the proposed system will be used

 System analyst
is responsible for
designing and
developing
information
system
 Liaison between
user and IT
professionals
6
 On Going Activities
 Project management is the process of planning,
scheduling, and then controlling the activities during
system development
 To plan and schedule a project efficiently, the project
leader identifies:
Required Time estimates
Project scope
activities for each activity

Activities that
Cost estimates Order of
can take place at
for each activity activities
the same time
7
 Gantt Chart
 A popular tool used to plan and schedule the
time relationships among project activities

8
 PERT Chart
 A Program Evaluation and Review Technique
(PERT) chart also can be used for planning
and scheduling time

9
 On Going Activities
 Feasibility is a measure of how suitable the
development of a system will be to the organization
 A project that is feasible at one point during system
development might become infeasible at a later point
 Thus, systems analysts frequently reevaluate
feasibility during the system development project.

Operational Schedule Technical Economic

feasibility feasibility feasibility feasibility

10
 On Going Activities
 Documentation is the collection and summarization
of data and information
 Includes reports, diagrams, programs, and other
deliverables
 A project notebook contains all documentation for a
single project
 Users and IT professionals refer to existing
documentation when working with and modifying
current systems
 All documentation be well written, thorough,
consistent, and understandable
 Maintaining up-to-date documentation should be an
ongoing part of system development 11
 On Going Activities
 Project team need accurate and timely data and
information for many reasons
 They must keep a project on schedule, evaluate
feasibility, and be sure the system meets requirements
 During system development, members of the project
team gather data and information using several
Review
techniques
documentation Observe

Survey
(Questionnaire) Interview
12
 Who Initiates System Development
Project
A user may request a new or modified system

Organizations may want to improve hardware, software, or other

technology

Situations beyond an organization’s control might require a change

Management might mandate a change

A user may request a new or modified information system using a request

for system services or a project request

13
 Project Request
 Project Request is a formal request for new or
modified information system

14
 1. Planning Phase
 The planning phase for a project begins when
the steering committee receives a project
request
 Four major activities are performed:

Review and
Prioritize Form a project
approve Allocate
the project development
the project resources
requests team
requests

15
 2. Analysis Phase
 The analysis phase consists of two major
activities:
Conduct a preliminary Perform detailed
investigation analysis
• Determines and • Study how the current
defines the exact system works
nature of the problem • Determine the users’
or improvement wants, needs, and
• Interview the user requirements
who submitted the • Recommend a
request solution

16
 2. Analysis Phase
 Preliminary
Investigation
 Determine exact
nature of problem or
improvement and
whether it is worth
pursuing
 Findings are
presented in feasibility
report, also known as
a feasibility study

17
 2. Analysis Phase
 Detailed Analysis – sometimes called logical
design
 Study how current system works
 Determine user’s wants, needs, and requirements
 Recommend solution
 Analysts develop the proposed solution without
regard to any specific hardware or software
 Analysts make no attempt to identify the
procedures that should be automated and those
that should be manual
 analysts use all of the data and information
gathering techniques 18
 2. Analysis Phase
 Process modeling (structured analysis and
design) is an analysis and design technique
that describes processes that transform inputs
into outputs

Entity-
Data flow Project
relationship
diagrams diagrams dictionary

19
 2. Analysis Phase
 An entity-relationship diagram (ERD) is a tool
that graphically shows the connections among
entities in a system
 Entities are objects in the system that have
data
 Entity names
usually are nouns
written in all capital
letters.
 Each relationship
describes a
connection between
two entities 20
 2. Analysis Phase
 A data flow diagram (DFD) is a tool that
graphically shows the flow of data in a system
 Data flows
 Processes
 Data stores
 Sources

 Top level context diagram, identifies only the major

process
 lower-level DFDs contain sub processes
21
 2. Analysis Phase
 The project dictionary contains all the
documentation and deliverables of a project
 Helps keep track of huge amount of details in
system. Various techniques to enter items in it.
 Explains every item
found on DFDs
and ERDs.
 Structured English is a
style of writing that
describes the steps in
a process
22
2. Analysis Phase
A decision table is a table
that lists a variety of
conditions and the actions
that correspond to each
condition

A decision tree also shows

conditions and actions,
but it shows them
graphically
23
2. Analysis Phase
 Decision table

24
2. Analysis Phase
 Decision tree

25
 2. Analysis Phase
 The data dictionary stores the data item’s name, description,
and other details about each data item
 Some DBMSs automatically generate the data dictionary. For
others, the systems analyst creates the data dictionary

26
 2. Analysis Phase
 Object modeling combines the data with the
processes that act on that data into a single unit,
called an object
 UML (Unified Modeling Language) has been
adopted as a standard notation for object modeling
and development
 UML includes 13 different diagrams
 Each diagram conveys a view of the system
 Two diagrams include:

Use case
Class diagram
diagram
27
 2. Analysis Phase
 A use case diagram
graphically shows how
actors (users) interact
with the information
system
 Diagrams are
considered easy to
understand
 an ideal tool for
communicating systemAn actor is a user or other entity such
as a program.
requirements with The function that the actor can perform
users is called the use case
28
 2. Analysis Phase
 A class diagram
graphically shows
classes and subclasses
in a system
 Each class can have
one or more subclasses
 Subclasses use
inheritance to inherit
methods and attributes
of higher levels

29
 2. Analysis Phase
 The system proposal assesses the feasibility of
each alternative solution
 Recommends the most feasible solution for the
project, which often involves modifying or
building on the current system.
 The steering committee discusses the system
proposal and decides which alternative to pursue

Packaged Custom
Outsourcing
software software
30
 Possible Solutions
 Modify the existing system
 Buy Packaged software – prewritten software
available for purchase
 Horizontal market software – meets needs of many
companies
 Vertical market software – designed for a particular
industry
 Develop own custom software – software
developed at user’s request
 Outsource – have outside source develop
software
31
 3. Design Phase
 The design phase consists of two major
activities

Develop all of the

Acquire hardware details of the new
and software or modified
information system

32
 3. Design Phase
 To acquire the necessary hardware and
software:

Solicit vendor
Make a decision
• Use research proposals • Various techniques
techniques such as are used to
• RFQ, RFP, or RFI is • Systems analyst
e-zines determine the best
sent to potential proposal makes
vendors or VARs recommendation to
steering committee
Identify technical Test and evaluate
specifications vendor proposals

33
 3. Design Phase
 The next step is to develop detailed design specifications
 Sometimes called a physical design because it specifies hardware
and software components for automated procedures

Architectural Database
design design

Input and
Program
output
design
design

34
 3. Design Phase
 Systems analysts typically develop two types of
designs for each input and output

Mockup
Layout chart

35
 3. Design Phase
 A prototype (proof of concept) is a working
model of the proposed system
 Prototypes have inadequate or missing
documentation
 Users tend to embrace the prototype as a final
system
 can be an effective tool if the development team and
the users discipline themselves to follow all system
development activities
 Should not eliminate or replace activities rather, it
should improve the quality of these activities
 Beginning a prototype too early may lead to
problems 36
 Computer-Aided Software
 Engineering
CASE tools are designed to support one or
more activities of system development
 CASE tools sometimes contain the following
tools:

Project
Graphics Prototyping
repository

Quality Code
Housekeeping
assurance generator
37
Case Tools

38
 3. Design Phase
 Many people should review the detailed design
specifications
 An inspection is a formal review of any system
development deliverable
 A team examines the deliverables to identify errors
 Step-by-step review by project team and users of any
system development cycle deliverable
 Used to review detailed design specifications before
they are given to programming team
 Identifies any errors and allows IT personnel to correct
them
 Used throughout entire system development cycle to
review a variety of deliverables 39
 4. Implementation Phase
 The purpose of the implementation phase is to
construct the new or modified system and then
deliver it to users

Install and Convert to

Develop
test the new Train users the new
programs
system system

40
 4. Implementation Phase
 The program development life cycle follows
these steps:
1
• Analyze the requirements

2
• Design the solution

3
• Validate the design

4
• Implement the design

5
• Test the solution

6
• Document the solution
41
 4. Implementation Phase
 Various tests should be performed on the new system
 Systems analysts and users develop test data so that they can perform
various tests.
 The test data should include both valid (correct) and invalid (incorrect)
data.
 When valid test data is entered, the program should produce the correct
results. Invalid test data should generate an error.
Integration Acceptance
Unit test Systems test
test test
• Verifies that • Verifies that • Verifies that • Checks the
each all programs an new system
individual in an application to ensure
program or application works with that it works
object works work other with actual
by itself together applications data
properly
42
 4. Implementation Phase
 Training involves showing users exactly how
they will use the new hardware and software in
the system
 One-on-one sessions
 Classroom-style lectures
 Web-based training

43
 4. Implementation Phase
 One or more of four conversion strategies can
be used to change from the old system to the
new system

44
 5.Operation, Support, and Security
 Phase
The purpose of the operation, support, and
security phase is to provide ongoing assistance
for an information system and its users after
the system is implemented

Perform Monitor
Assess system
maintenance system
security
activities performance

45
 5.Operation, Support, and Security
 Phase
A computer security plan should do the following:
 Summarizes in writing all of the safeguards that are in
place to protect a company’s information assets

For each risk,

Identify all identify the
Identify all
security risks that safeguards that
information
may cause an exist to detect,
assets of an
information asset prevent, and
organization
loss recover from a
loss

46
 Summary
 System Development Life Cycle Phases
 Ongoing Activities
 Project Management, Feasibility, Documentation
 Planning
 Review, approve and prioritize project requests
 Analysis
 Preliminary Investigation, Detailed analysis
 Design
 Acquire Hardware and software, Develop details
 Implementation
 Develop programs, install and test new system
 Operation, Support and Security
 Maintenance Activities, System performance and security
47