System Analysis and Design

Presented by:
Munawar, PhD
 Teaching Plan
 Course Title: System Analysis and Design
(Analisis dan Perancangan Sistem)
 Credit 3 (2+1)
System Analysis and Design

 Prerequisite: -
 Instructor: Munawar
 Group: Max 3 students

2
 Course Content Layout
 Week 1
 Intro to System Analysis and Design
 What is Analysis and Design
System Analysis and Design

 What is Object Oriented Analysis and Design

 The Unified Process (UP)
 Development Roles

3
 Course Content Layout (Cont.)
 Week 2
 Development Methodologies Selection
 Managing Project
 Week 3
System Analysis and Design

 Analyisis Phase
 Requirement Determination
 Requirement Analysis Strategy

4
 Course Content Layout (Cont.)
 Week 4
 Information Gathering
 Week 5
System Analysis and Design

 Use Case Analysis

5
 Course Content Layout (Cont.)
 Week 6
 Process Modeling
 Assignment 1
System Analysis and Design

 Week 7
 Data Modeling
 Week 8
 Design

6
 Course Content Layout (Cont.)
 Week 9
 Architecture Design
 Week 10
System Analysis and Design

 User Interface Design

 Week 11
 Program Design

7
 Course Content Layout (Cont.)
 Week 12
 Implementation
 Week 13
System Analysis and Design

 Transition to New System

 Week 14
 Course Project Presentation

8
 Course Evaluation
 Attendance : 0-10%
 Mid Test : 20%
 Final Test : 30%
System Analysis and Design

 Assignment : 40-50%%

9
 Reference Books
 Munawar. (2018). Analisis dan Perancangan Sistem dengan
UML. Informatika. Bandung
 Dennis, A., Wixon,B.H. and Tegarden, D. (2005). Systems
Analysis And Design With UML Version 2.0: An Object-
Oriented Approach, Second Edition. John Wiley & Sons, Inc.
System Analysis and Design

 George, J. F., Batra, D., Valacich, J.S., Hoffer, J.S. (2007)

Object-Oriented Systems Analysis and Design, Second
Edition: Pearson Prentice Hall.
 Bahrami, A. (1999). Object Oriented Systems Development,
Using The Unified Modeling Language. McGraw-Hill, Inc.
 Stumpf, R.V., Teague, L.C. (2005). Object-Oriented Systems
Analysis And Design With UML. New Jersey: Pearson
Prentice Hall.
 Bennet, S., McRobb, S and Farmer, R. (2002). Object
Oriented Systems Analysis and Design using UML, Second
edition. McGraw-Hill, Inc.

10
System Analysis and Design

Book Recommendation

11
System Analysis and Design

Book Recommendation

12
 Lecture 1

What is analysis and design

What is OOAD
Unified process
Development roles
 What Is Systems Analysis and Design?
 The process of implementing and operating
an information system
 Requires knowledge of:
System Analysis and Design

 Organization’s objectives, structure, processes

 Information technology opportunities and
constraints
 Software analyst
 Major goal- improve organizational systems

14
 What Is Systems Analysis and Design?

SYSTEM
SOFTWARE
HARDWARE USERS
System Analysis and Design

C-BIS APPLICATION
DOCUMENTATION
SPECIFIC & MANUALS
JOB ROLES

CONTROLS

15
 Software Development Process

Sequence step-by-step
Approach. May incorporate
Methodologies several development techniques.
System Analysis and Design

Software
Engineering
Process

Techniques Tools

Processes followed by analyst

on their work, wide range of tasks Computer programs
-interviews, planning and manage, - eg: CASE tools
Diagramming system functions, etc

16
 What Is a System?
 A group of interrelated procedures used for a
business function, with an identifiable
boundary, working together for some
System Analysis and Design

purpose.
 Payroll system, inventory system, library
system, etc.

17
System Analysis and Design

18
 Characteristics of Systems
 Boundary – divides system from environment
 Inputs – data from environment to system
 Output – data from system to environment
Components – subparts of systems operating
System Analysis and Design


independently (objects)
 Interrelationships – associations between
components of a system
 Interfaces – mechanism for interacting with a
component

19
 Important System Concepts
 Decomposition – breaking down a system
into smaller constituents
 Modularity – the result of decomposition;
System Analysis and Design

parts of a system, easier to understand

overall system.
 Coupling – dependencies between
subsystems, dependent on each other
 Cohesion – extent to which a subsystem
performs a single function.

20
 Developing Small Scale System
 Say I ask you to develop a system that asks
the user for their birth date, and prints out the
day of week for their next birthday.
System Analysis and Design

 How would you design such a system?

21
 Developing Small-scale Systems
(Cont.)
 How would you design such system?
 The answer is: You probably won’t design

 The problem is simple

System Analysis and Design

 You probably won’t maintain it

 You can probably write the program alone
 It is unlikely to have unsolved bugs in such a program
 If the program fails, it is not particularly inconvenient to
execute it again to achieve the result
 The program is not particularly useful

22
 Medium-scale Systems
 Say I ask you to develop a system that
stores customers and products in a database
and provides a GUI for browsing these
System Analysis and Design

products and customers.

 How would you design such a system?

23
 Medium-scale Systems
 How would you design such a system?
 reduce the effort to design
 Most likely, you have a team of 4-5 developers
System Analysis and Design

 Modularize the program so that developers can work

independently
 You would probably have bugs to fix, as well as some
improvements to make over time
 If the code is hard to follow, the a new developer wants
your code to fix the bugs, it will be very difficult as this
program should be maintained and improved.

24
 Large-scale Systems
 Say I ask you to develop a new operating
system
 How would you design such a system?
System Analysis and Design

25
 Large-scale Systems
 How would you design such a system?
 There are likely hundreds of developers
 People who fix bugs are probably not the
System Analysis and Design

same people who wrote the code

 Bugs in such a system are unavoidable
 Duplicated codes are likely occur
 New versions are a certainty, so
improvements are expected

26
System Analysis and Design

27
 Transaction Processing System (TPS)
 Automate the handling of data for business
activities or transactions.
 Capture transaction data.
System Analysis and Design

 Goal: improve transaction processing by

increasing speed, enhancing productivity,
simplifying processes
 E.g: withdrawal of customer account, deposits
of customer account, point of sales in
supermarket, inventory system.

28
 Management Information System
(MIS)
 Use raw data from TPS systems, and
converts them into meaningful aggregate
form (standard reports).
System Analysis and Design

 Goal: provide the information that helps

managers in their jobs.
 E.g: bank transactions and investments.
 Several TPS – customer order, raw material
purchasing, employee timekeeping.

29
 Decision Support System (DSS)
 Interactively assist with decision making by applying
mathematical or logical models and a dialogue of
interactions to solve unstructured problems.
System Analysis and Design

 Involves data manipulation and models, drill down

into specific areas. From problem finding to choosing
a course of action.
 “what if analysis”
 Goal: provide comparisons of alternatives and
recommendation of preferred option.
 Such as :EIS, data warehouse, KMS (corporate
portal).
30
 Software Development Life Cycle
System Analysis and Design

31
 Systems Planning and Selection
 Analyze and arrange organization’s
information needs, identify and describe
potential project, determine system scope,
and provide a business case for continuing
System Analysis and Design

with the project

 Feasibility analysis: determine economic and

organizational impact of the system

32
 An Introduction to Analysis
 Build the right thing (who, what, where, when)
 Analysis focuses on user requirements
(functional or non-functional)
System Analysis and Design

 In other words, we want to decide exactly

WHAT system the customer wants to have.
 Step 1: determine the requirements
 Step 2: studied the requirements and
structures accordingly with interrelationship,
eliminate redundancies.
 Step 3: generate alternative initial design to
match with the requirements.
33
 Analysis
 Usually Performed by a System Analyst
 This is a person whose job is to find out what
an organization needs in terms of software
System Analysis and Design

system
 Analysis looks at the software as a black box
 An analyst will never care about the internal of
the system, merely how a user would interact
with it from outside.

34
 Systems Analysis
 Thorough study of organization’s current system and
processes, determination of system requirements,
structuring requirements, generate alternative design
strategies.
System Analysis and Design

 Use case- set of sequences of action that a system

performs based on an observable result of value to a
particular actor.
 Use of UML for system modeling
 Goal: describe what needs to be done (an alternative
solution recommended by the analysis team.)

35
 An Introduction to Design
 Build the thing right (How the system will operate)
 Design focuses on how to provide the required
functionality (h/ware, s/ware, n/work infrastructure,
user interface, forms and reports, database and files,
System Analysis and Design

specific programs)
 E.g.: we want to decide HOW to structure the software
that provides the functional and non functional
requirements determined during analysis.
 Four steps: design strategy, architecture design,
database & file specification, program design

36
 Systems Design
 Translating alternative solution generated by analysis
phase into detailed logical and physical system
specifications.
System Analysis and Design

 Logical design: not tied to any hardware or software

platform
 Physical design: specific programming languages,
databases, architectures
 Goal: identify how the task will be accomplished
 Product – physical systems specifications (diagram/
written report)

37
 System Implementation and Operation
 Information system is coded, tested, and
installed, and undergoes periodic corrections
and enhancements
System Analysis and Design

 Goal: provide a fully operational system

38
 Evolution of System Development
Methodologies
 SDLC
 Systems Development Life Cycle
 Structured Analysis and Design
System Analysis and Design

 Use of Data Flow Diagrams

 Data-Oriented Methodology
 Use of Entity Relation Diagrams
 Object-Oriented Methodology
 Use of Unified Modeling Language (UML)
Diagrams
39
System Analysis and Design

The current trend is to use OOSAD, but many organizations

are still using structured analysis and design
40