Lecture1.systems and Its Component Merged
Lecture1.systems and Its Component Merged
a. Resources
b. Procedures/Rules/Policies
c. Data/ Information
d. Processes/Function
Systems
Resources
• By following
. the right standard of procedures the system can
achieved targeted objectives.
• By following
. the right standard of procedures the system can
achieved targeted objectives.
.
LESSON 2. THE ROLES OF SYSTEM ANALYST
System Analyst- Systematically assesses how users interact with technology and how
businesses function by examining the inputting and processing of data and the outputting of
information with the intent of improving organizational processes. Many improvements involve
better support of users’ work tasks and business functions through the use of computerized
information systems.
• Consultant
• Supporting expert
• Agent of change.
The systems analyst frequently acts as a systems consultant to humans and their businesses
and, thus, may be hired specifically to address information systems issues within a business.
Such hiring can be an advantage because outside consultants can bring with them a fresh
perspective that other people in an organization do not possess. It also means that outside
analysts are at a disadvantage because an outsider can never know the true organizational
culture. As an outside consultant, you will rely heavily on the systematic methods discussed
throughout this text to analyze and design appropriate information systems for users working in a
particular business. In addition, you will rely on information systems users to help you understand
the organizational culture from others’ viewpoints.
Another role that you may be required to play is that of supporting expert within a business for
which you are regularly employed in some systems capacity. In this role the analyst draws on
professional expertise concerning computer hardware and software and their uses in the
business. This work is often not a full-blown systems project, but rather it entails a small
modification or decision affecting a single department.
As the supporting expert, you are not managing the project; you are merely serving as a
resource for those who are. If you are a systems analyst employed by a manufacturing or
service organization, many of your daily activities may be encompassed by this role .
Systems Analyst as Agent of Change
The most comprehensive and responsible role that the systems analyst takes on is that of an
agent of change, whether internal or external to the business. As an analyst, you are an agent of
change whenever you perform any of the activities in the systems development life cycle and are
present and interacting with users and the business for an extended period. An agent of change
can be defined as a person who serves as a catalyst for change, develops a plan for change, and
works with others in facilitating that change.
As a systems analyst, you must recognize this fact and use it as a starting point for your analysis.
Hence, you must interact with users and management (if they are not one and the same) from
the very beginning of your project. Without their help you cannot understand what they need to
support their work in the organization, and real change cannot take place.
If change (that is, improvements to the business that can be realized through information systems)
seems warranted after analysis, the next step is to develop a plan for change along with the
people who must enact the change. Once a consensus is reached on the change that is to be
made, you must constantly interact with those who are changing.
As agent of change, the system analyst advocate a particular avenue of change involving the use
of information systems.
Reference
https://www.w3computing.com/systemsanalysis/roles-systems-analyst/
SYSTEMS DEVELOPMENT
LIFE CYCLE
(SDLC)
ter Description
Expected Outcomes
References
• J.A Hoffer, J.F. George, and J.S. Valacich, "Modern Systems Analysis and Design", 7/E,
Addison-Wesley, 2014
• Kenneth E. Kendall, Julie E. Kendall.,“Systems Analysis and Design ”, Pearson, 2014
• D. Jeya Mala and S. Geeta, "Object Oriented Analysis & Design Using UML",
McGrawHill, 2013
• Alan Dennis, Barbara Haley Wixom, David Tegarden, "Systems Analysis and Design With
UML : An Object-Oriented Approach ", John Wiley, 2010
• Klaus Pohl, "Requirement Engineering Fundamentals", Santa Barbara, CA : Rocky Nook,
2011
Introduction
• Software Development Life Cycle (SDLC) Model is a concept on
standard and procedural to be followed when developing a
system.
• Planning Maintenan
Analysis
ce
• Analysis
• Design
• Implementation
• Maintenance
Implementati
Design
on
SDLC Phases
Planning
The proposed system is assess for its feasibility, meaning,
evaluate for its practical and beneficial to build that system.
Feasibility must be assess from developer and customer’s
point of view.
There are six feasibility factors :
Economical
Technical
Operational
Legal
Schedule
Political
Analysis
Testing stages:
Unit testing
Integration testing
System testing
User Acceptance Test
Implementation
Design
Coding/Implementation
Testing
Maintenance
Figure 2.2 Waterfall Lifecycle Model
Waterfall Lifecycle Model
Advantages:
i. Provides structure approach to new
developer
ii. Sets requirements early iii. Easy to
understand iv. Milestones are better
understood
Other SDLC Approaches
There are many other approaches to system
development model such as:
i. Iterative Prototype Model ii.
Spiral Model
iii. Rapid Application Development
iv. V-Shaped SDLC Model v.
OOAD Approach
Systems Development
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.
Analysis specifies what the system should do.
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 understand the old system thoroughly and determine how
computers can best be used in order to operate efficiently.
Types of Systems
The systems can be divided into the following types −
Categories of Information
There are three categories of information related to managerial levels and the decision
managers make.
Strategic Information
• This information is required by topmost management for long range
planning policies for next few years. For example, trends in revenues,
financial investment, and human resources, and population growth.
• This type of information is achieved with the aid of Decision Support
System (DSS).
Managerial Information
• This type of Information is required by middle management for short and
intermediate range planning which is in terms of months. For example,
sales analysis, cash flow projection, and annual financial statements.
• It is achieved with the aid of Management Information Systems (MIS).
Operational information
• This type of information is required by low management for daily and short
term planning to enforce day-to-day operational activities. For example,
keeping employee attendance records, overdue purchase orders, and
current stocks available.
• It is achieved with the aid of Data Processing Systems (DPS).
SYSTEMS ANALYSIS AND DESIGN
❑Closed Questions
❑Open ended Questions
❑Probe Questions