1

SYSTEM & ANALYSIS DESIGN (SAD)

Pertemuan 9

Project Report : Specify

Problem and IS Solution

Candiwan

Prodi MBTI – Fakultas Ekonomi & Bisnis

 2

OUTLINE

2
 3

1 Specify Problem on Project

3
 4

Ishikawa Diagram
Graphical tool used to identify, explore, and depict problems and the causes and
effects of those problems. It is often referred to as a cause-and-effect diagram or
a fishbone diagram.
Problem at right (fish head)
Possible causes drawn as "bones" off main backbone
Brainstorm for 3-6 main categories of possible causes

6-4
 5

Identifying Problems,
Opportunities, And Objectives
Activity:
 Interviewing user management
 Summarizing the knowledge obtained
 Estimating the scope of the project
 Documenting the results
Output:
 Feasibility report containing problem definition and objective
summaries from which management can make a decision on
whether to proceed with the proposed project

5
 6

Sample Interview Guide

6-6 (continued)
 7

Sample Interview Guide (concluded)

6-7
 8

2 Identify User Requirement

8
 9

Requirements Discovery

Given an understand of problems, the systems analyst can start to

define requirements.

Fact-finding – the formal process of using research, meetings,

interviews, questionnaires, sampling, and other techniques to collect
information about system problems, requirements, and preferences. It
is also called information gathering or data collection.

6-9
 10

Seven Fact-Finding Methods

Sampling of existing documentation, forms, and databases.

Research and site visits.
Observation of the work environment.
Questionnaires.
Interviews.
Prototyping.
Joint requirements planning (JRP).

6-10
 11

Functional VS Nonfunctional Requirements

Functional requirement
something the information system must do

Nonfunctional requirement
a property or quality the system must have
Performance
Security
Costs

6-11
 12

Documenting and
Analyzing Requirements

Documenting the draft requirements

Use cases
Decision tables
Requirements tables
Analyzing requirements to resolve problems
Missing requirements
Conflicting requirements
Infeasible requirements
Overlapping requirements
Ambiguous requirements
Formalizing requirements
Requirements definition document
Communicated to stakeholders or steering body
6-12
 13

Requirements Definition Document

Requirements Definition Document – A formal document that

communicates the requirements of a proposed system to key
stakeholders and serves as a contract for the systems project.

Synonyms
Requirements definition report
Requirements statement
Requirements specification
Functional specifications

6-13
 14

Sample Requirements Definition Report Outline

6-14
 15

3 Identify Stakeholder

15
 16

Stakeholder

People who have an interest in information systems that already exist or

are offered. Stakeholders can include technical and non-technical
worker, can also include inside and outside worker.

16
 17
Stakeholder System

SYSTEM
OWNER

SYSTEM
USER
SYSTEM
DESIGN
SYSTEM
BUILDER
ANALYST
Inayatullah
SYSTEM
 18

System User

Information worker at any information system. Unlike system owner,

system user tend to ignore system cost and benefit, but pay more attention
to the system functionality provided for their work and ease of learning
and use of the system.

18
 19

Internal System User

 Administrative and service worker

 Technical and professional staff (knowledge worker)
 Supervisor, middle manager, and executive manager.

19
 20

External System User

 Customer
 Supplier
 Coworker or partner
 Employees working at
 Home (telecommute)
 Mobile (mobile), for example sales.

20
 21

System Designer

Technical specialists who translate the business requirements of system

users and limiting technical solutions. He designed databases, inputs,
outputs, screens (screens / displays), networks, and computer software that
would meet the requirements of system users.

21
 22

Example

 Administrator database
Network architect
Web architect
Artist chart for the interface
Security expert
Technology specialists, such as barcodes

22
 23

System Builder

Technical specialist who build information system and component based

on design specifications produced by designers.

23
 24

Example

 Application programmer
 Programmer system
 Database programmer
 Network administrator
 Security administrator
 Webmaster
 Software integrator, which integrates software with hardware, networks and
other software.
 25

System Analyst

Specialist who study the problem and need of an organization, to determine

how people, data, processes and information technology can achieve the best
progress for business.

25
 Where does System Analyst Work? 26

1. Owner
system
2. Designer and
Builder
System
3.4 system analysis and
designer and system builder
5. Analysis of systems for
smaller computer departments

26
 27

Link and Match Application

4 Usability with Company Goals

27
 28

What Is Usability?

“The extent to which a product can be used by specified users to

achieve specified goals with effectiveness, efficiency, and satisfaction in
a specified context of use”

Effectiveness + Efficiency + Satisfaction = Usability

28
 29

Human Computer Interaction

HCI is a “very important concept in the system development process as it is about
understanding and creating software and other technology that people will want to use,
will be able to use, and will find effective when used. And the usability concept and the
methods and tools to encourage it, achieve it, and measure it are now touchstones in
the culture of computing”

(Carroll 2002 , p. xxvii)

HCI research similarly emphasises techniques for developing a large number of prototypes,
exploring different possible solutions, and evaluating the usability of alternatives.

29
 30

Goals of HCI

To establish a simple system with good usability, the HCI specialists need to be
aware of the following issues (Preece et al. 1994 , p. 15):
•Understand the factors such as organizational, social, and psychological factors
that determine how people operate and make use of computer technology
effectively.
•Develop tools and techniques to help designers ensure that computer systems
are suitable for the activities f or which people will use them.
•Achieve efficient, effective, and safe interaction in terms of both individual
Human Computer Interaction and group interaction.

30
 31

Purpose of HCI

The purpose of HCI is to design a computer system to match the needs and
requirements of the users. To achieve the goals of HCI, a number of approaches
can be utilized. These approaches are: (Preece et al. 1994 , p. 46–47)
•Involving the user: (involve the user as much as possible so that s/he can
influence the system design).
•Integrating different kinds of knowledge and expertise: (integrate knowledge
and expertise from the different disciplines that contribute to HCI design).
•Making the design process iterative: (testing can be done to check that the
design does indeed meet users’ requirements).

31
 32

Identify Existing Application

5 Related to Similar Solution

32
 33

Five Steps You Can Use To Determine

If An Existing App Can Be Containerized

• 1. Is the app pre-packaged as a single binary or JAR file?

• 2. Is the platform on which your app is built available in a containerized version or
package yet?
• 3. Are any of your 3rd party apps available in a container version yet?
• 4. Is the app stateless?
• 5. Is your application already part of continuous integration/continuous deployment
pipeline?

Source : https://d2iq.com/blog/five-steps-you-can-use-to-determine-if-an-existing-app-can-be-containerized

33
 34

Identify The Advantage of

6 Application to be Developed

34
 35
Advantages Can Be Measured
Various Ways

1. Increasing company profits

2. Reducing business costs
3. System costs and benefits
4. Increasing market share
5. Increasing efficiency
6. Improving decision making
7. Less errors
8. Security improvements
9. Greater capacity
 36

7 IS Solution on Project

36
 37

IS Solution on Project

• ISS provides IT (computer, networking, wireless technology, applications, software, cabling,

etc.) solutions for businesses that complement the goals and industry so that the business
can succeed and continue to grow in value. ISS takes pride in understanding our customers
needs, goals, and direction. Armed with that information helps ISS to develop solutions that
will help our customer to focus on the delivery of their goods and services. Allowing the
customer to focus on their strengths ultimately contributes to their success.
(Source : Van Horm, 2005)

37
 38

IS Solution on Project

• The development, implementation and maintenance of computer-based information system

solutions require innovative thinking, research and communication skills, extensive documentation,
and the ability to effectively apply proposed solutions.
• Information System Solutions: A Project Approach integrates basic information systems knowledge
with these requirements, culminating in their combined application in a project-based real-world
scenario.
• Three different project models, an SDLC-based chapter organization and an emphasis on teamwork
make this text easily adaptable to your teaching needs. Successfully tested in the classroom and
approved by thousands of students, Information System Solutions: A Project Approach prepares your
students to be active, effective contributors to the professional field of information systems.
(Source : Van Horm, 2005)

38
 References
39
Schwarzkopf

• Jeffrey L. Whitten, Lonnie D. Bentley, 2007,” Systems Analysis and Design Method 7th Edition”, McGrawHill
• Whitten, Jeffery L.; Lonnie D. Bentley; Kevin C. Dittman. 2004. Systems Analysis andDesign Methods. 6 edition. McGraw-Hill
• ISO 9241-11, Ergonomic Requirements for Office Work with Visual Display Terminals (VDTs) - Part 11: Guidance on usability
(1998)
• Carroll JM (2002) Human-computer interaction in the new millennium. Addison-Wesley, New York
• Alan Blackwell. 2010. Human Computer Interaction. https://www.cl.cam.ac.uk/teaching/1011/HCI/HCI2010.pdf retrivied on
7 March 2019.
• Issa, T. and Isaias, P. 2015. Sustainable design: HCI, usability and environmental concerns. London: Springer-Verlag.
• Van Horm, Richard; Schwarzkopf, Albert B.; Price, Leon R, 2005, Information Systems Solutions: A Project Approach,
Bliobiometric, New York.
• https://d2iq.com/blog/five-steps-you-can-use-to-determine-if-an-existing-app-can-be-containerized
•

39