FYP

A+,A,A-,B+,B,B-

ROAD TRIP
DFC40243
JTMK
March 7, 2022 – June 17, 2022
Sesi II 2021/2022
 a. Theory Test(1) 15%
b. Problem Based Exercise(2) 10%
c. Mini Project(2)25%
d. Mini Project Presentation(2)10%
e. Case Study (1)10%
TOTAL70%

Topic 1 : Intro
to System
Analysis & our JOURNEY Topic 5 : System
Implementation
Design and Support

Topic 2 :
System
Topic 3 : Topic 4 :
Planning
System System
Analysis Design
 Learning Outcome:
i. Student able to apply Information System
ii. Student able to demonstrate system
development approach
iii. Student able to apply Project Management

CLO 1 – Implement the appropriate model,

tools and techniques concept of System
Analysis & Design for developing project.

Topic 1 : Intro to System Analysis & Design

What is System Analysis & Design?

 What is Information?
exam
Information is data that has been transformed into
output that is valuable to users.

What is Information System?

Information system deals with data of the organizations.

The purposes of Information system are to process input,

maintain data, produce reports, handle queries, handle on line
transactions, generate reports, and other output.

What is Information System Components?

An information system has five key components:
hardware
software
data
processes
people
 Hardware consists of everything in the physical layer of the
information system. For example, hardware can include servers,
workstations, networks, telecommunications equipment, fiber-optic
cables, mobile devices, scanners, digital capture devices, and other
technology-based infrastructure.

Software refers to the programs that control the hardware and

produce the desired information or results.
os System software manages the hardware components, which can
include a single workstation or a global network with many thousands
of clients.
Application software consists of programs that support day-to-day
business functions and provide users with the information they
require.

Data is the raw material that an information system transforms into

useful information.

Processes describe the tasks and business functions that users,

managers, and IT staff members perform to achieve specific results.

People who have an interest in an information system are called

stakeholders.
 WHAT IS TYPES OF INFORMATION?
Information systems different in their business needs. It also depending upon different levels in organization
information systems differ.

Three major information systems are: What difference?

Decision support system and
Decision making

Decision
support system

Management
information
system

Transaction
processing
BUSINESS NEED
 IQ TEST
Lorem ipsum dolor sit amet. Et quis nulla vel facere
aliquam aut animi culpa quo quia dolorem.

data
process
software
people
hardware
 IQ TEST
Lorem ipsum dolor sit amet. Et quis nulla vel facere
aliquam aut animi culpa quo quia dolorem.
 System Development Method:

Structured Analysis Object Oriented Analysis Agile / Adaptive Method

1. Structured analysis is a traditional systems
development technique that is time-tested and easy to
understand.
2. Structured analysis uses a series of phases, called the
systems development life cycle (SDLC) to plan, analyze,
design, implement, and support an information system.
1. Object oriented analysis combines data and the processes
that act on the data into things called objects.
2. Use Object Oriented to model real-world business
processes and operations
1. Newest development techniques change over
time.
2. Attempt to develop a system incrementally, by
building a series of prototypes and constantly
adjusting them to user requirements.
3. Agile methods typically use a spiral model, which
represents a series of iterations, or revisions, based
on user feedback.
Structured Analysis

-Represents the system in terms of data and the processes that act upon
that data.

-System development is organized into phases, with deliverables and

milestones to measure progress.

-It is called process centered technique because it focuses on processes

that transform data into useful information

Modelling tool – Data Flow Diagram (DFD). Uses various symbols and
shapes to represent data flow, processing and storage

-Advantages - Traditional method, relies on written documentation,

frequent phase iteration can provide flexibility comparable with other
methods, well-suited to project management tools and techniques.

-Disadvantages - Changes can be costly, requirements are defined early

and can change during development, users might not be able to describe
their needs until they can see examples of features and functions.

-The SDLC waterfall model typically consists of five phases:

a) Planning
b) Analysis
c) Design
d) Implementation
e) Support and Security
➢ Object Oriented Analysis
-Views the system in terms of objects that combine data and
processes.

-The objects represent actual people, things, transactions, and events.

O-O phases tend to be more interactive.

-Modelling tool - Various object-oriented diagrams depict system

actors, methods and messages.

-Advantages - Integrates easily with object-oriented programming

languages, code is modular and reusable, which can reduce cost and
development time, easy to maintain and expand as new objects can
be cloned using inherited properties.

-Disadvantages - Newer method might be less familiar to development

team members, interaction of objects and classes can be complex in
larger systems.
➢ Agile/Adaptive Methods

-Breaks development process down into cycles, or iterations that add

functionality.

-Each iteration is designed, built, and tested in an ongoing process.

-Attempts to reduce major risks by incremental steps in short time

intervals.

-Modelling tool - Tools that enhance communication, such as

collaborative software, brainstorming, and whiteboards, business
process modeling.

-Advantages - Very flexible and efficient in dealing with change,

stresses team interaction and reflects a set of community-based
values, frequent deliverables constantly validate the project and
reduce risk.

-Disadvantages - Team members need a high level of technical and

communications skills, lack of structure and documentation can
introduce risk factors, overall project might be subject to scope
change as user requirements change.
 IQ TEST
Lorem ipsum dolor sit amet. Et quis nulla vel facere
aliquam aut animi culpa quo quia dolorem.
SYSTEM DEVELOPMENT LIFE CYCLE (SDLC)
Planning Analysis Design Development Testing Implementation Maintenanc
e
SYSTEM DEVELOPMENT LIFE CYCLE (SDLC)
SYSTEM DEVELOPMENT LIFE CYCLE (SDLC)
 Life Cycle Models

Waterfall model

Spiral Model

Iterative and incremental development

Agile Model

Prototyping model

Rapid Application Development (RAD)

Joint Application Development (JAD)

WATERFALL MODEL

ADVANTAGES
This model is simple and easy to understand and
use.
It is easy to manage due to the rigidity of the model
– each phase has specific deliverables and a review
process.
In this model phases are processed and completed
one at a time. Phases do not overlap.
Waterfall model works well for smaller projects
where requirements are very well understood.

DISADVANTAGES
It is very difficult to go back and change something
that was not well-thought out in the concept stage.
No working software is produced until late during
the life cycle.
High amounts of risk and uncertainty.
Not a good model for complex and object-oriented
projects.
Poor model for long and ongoing projects.
SPIRAL MODEL

ADVANTAGES
High amount of risk analysis hence, avoidance of
Risk is enhanced.
Good for large and mission-critical projects.
Strong approval and documentation control.
Additional Functionality can be added at a later date

DISADVANTAGES
Can be a costly model to use.
Risk analysis requires highly specific expertise.
Project’s success is highly dependent on the risk
analysis phase.
Doesn’t work well for smaller projects.
ITERATIVE AND INCREMENTAL DEVELOPMENT MODEL

ADVANTAGES
Generates working software quickly and early during the
software life cycle.
This model is more flexible – less costly to change scope
and requirements.
It is easier to test and debug during a smaller iteration.
In this model customer can respond to each built.
Easier to manage risk because risky pieces are identified
and handled during it’d iteration.

DISADVANTAGES
Needs good planning and design.
Needs a clear and complete definition of the whole system
before it can be broken down and built incrementally.
Total cost is higher than waterfall.
AGILE DEVELOPMENT MODEL

ADVANTAGES
People and interactions are emphasized rather than process
and tools.
Customers, developers and testers constantly interact with
each other.
Face-to-face conversation is the best form of communication.
Close, daily cooperation between business people and
developers.
Continuous attention to technical excellence and good design.

DISADVANTAGES
In case of some software deliverables, especially the large
ones, it is difficult to assess the effort required at the
beginning of the software development life cycle.
There is lack of emphasis on necessary designing and
documentation.
The project can easily get taken off track if the customer
representative is not clear what final outcome that they want.
PROTOTYPING MODEL

ADVANTAGES
Users are actively involved in the development
Users get a better understanding of the system being
developed.
Errors can be detected much earlier.
Quicker user feedback is available leading to better solutions.
Missing functionality can be identified easily
Confusing or difficult functions can be identified

DISADVANTAGES
Leads to implementing and then repairing way of building
systems.
Increase the complexity of the system as scope of the system
may expand beyond original plans.
Incomplete or inadequate problem analysis.
RAPID APPLICATION DEVELOPMENT (RAD)

ADVANTAGES
Reduced development time.
Increases reusability of components
Quick initial reviews occur
Encourages customer feedback
Integration from very beginning solves a lot of integration
issues.

DISADVANTAGES
Depends on strong team and individual performances for
identifying business requirements.
Only system that can be modularized can be built using RAD
Requires highly skilled developers/designers.
High dependency on modeling skills
JOINT APPLICATION DEVELOPMENT (JAD)

ADVANTAGES
Allows key users to participate effectively.
The result in a more accurate statement of system
requirements, a better understanding of common goals, and a
stronger commitment to the success of the new system.

DISADVANTAGES
More expensive and can be cumbersome if the group is too
large relative to the size of the project.
IDENTIFY Appropriate life cycle model

You and group members (2-3) discuss:

1. Your group title.
2. What product?
3. Your client?
4. Business needs?
5. Life cycle model? Why?
Project Management Activities
Project Management Step in Project
Planning
Three key steps in project planning:
1. Create a work breakdown structure. The position of the bar shows the planned starting and ending time of each task,
2. Identify task patterns.
3. Calculate the critical path.
STEP 1: CREATE A WORK BREAKDOWN STRUCTURE (A) USING GANTT CHART
Gantt chart is a horizontal bar chart that represents a set of tasks involves
breaking a project down into a series of smaller tasks.
and the length of the bar indicates its duration.
On the horizontal axis, time can be shown as elapsed time from a fixed starting
point, or as actual calendar dates. A Gantt chart also can simplify a complex
project by combining several activities into a task group.
Gantt charts can present an overview of the project’s status, but they do not
provide enough detailed information, which is necessary when managing a
complex project. Most project managers find that PERT/CPM charts, which are
discussed next, are better tools for managing large projects.
GanttProject
STEP 1: CREATE A WORK BREAKDOWN STRUCTURE (B) PERT/CPM
The Program Evaluation Review Technique (PERT) was developed by the U.S.
Navy to manage very complex projects, such as the construction of nuclear
submarines.
the Critical Path Method (CPM) was developed by private
industry to meet similar project management needs. The distinction between
the two methods has disappeared over time, and today the technique is
called either PERT, CPM, or PERT/CPM.

PERT is a bottom-up technique, because it analyzes a large, complex project as a

series of individual tasks.
1. To create a PERT chart, you first identify all the project tasks and estimate how
much time each task will take to perform.
2. You must determine the logical order in which the tasks must be performed.
For example, some tasks cannot start until other tasks have been completed.
In other situations, several tasks can be performed at the same time.
3. Once you know the tasks, their durations, and the order in which they must
be performed, you can calculate the time that it will take to complete the
project.
4. You also can identify the specific tasks that will be critical to the project’s on-
time completion.
EXAMPE PERT/CPM
IDENTIFY TASK IN A WORK BREAKDOWN STRUCTURE
A work breakdown structure must clearly identify each task and
include an estimated duration.
A task, or activity, is any work that has a beginning and an end
and requires the use of company resources such as people,
time, or money.
Examples of tasks include conducting interviews, designing a
report, selecting software, waiting for the delivery of
equipment, or training users.
Tasks are basic units of work that the project manager plans,
schedules, and monitors — so they should be relatively small
and manageable.
1. LISTING THE TASKS
2. PROJECT SIZE
3. HUMAN RESOURCES
4. EXPERIENCE WITH SIMILAR PROJECTS
5. CONSTRAINTS
STEP 2: CREATE TASK PATTERNS
In any project, large or small, tasks depend on each other and must be performed in a sequence, not unlike the
commands in a software program.
Task patterns can involve dependent tasks, multiple successor tasks, and multiple predecessor tasks.
In larger projects, these patterns can be very complex, and an analyst must study the logical flow carefully.

TASK NAME
TASK ID
TASK DURATION
START DAY/DATE
FINISH DAY/DATE

Main Types of Task Patterns:

DEPENDENT TASKS - When tasks must be completed one after another, like the relay race
MULTIPLE SUCCESSOR TASKS - When several tasks can start at the same time, each is called a concurrent task.
MULTIPLE PREDECESSOR TASKS - Suppose that a task requires two or more prior tasks to be completed before it can
start.
STEP 2: CREATE CRITICAL PART ANALYSIS
A critical path is a series of tasks which, if delayed, would affect the completion date of the overall project. If any
task on the critical path falls behind schedule, the entire project will be delayed.
For example, suppose that you invite Joan and Jim to your home for dinner. Joan arrives on time, but Jim arrives 30
minutes late. Jim’s arrival is part of the critical path, because you do not want to start without him, so the meal will
be served 30 minutes later than originally planned.
Project managers always must be aware of the critical path, so they can respond quickly to keep the project on track.
Microsoft Project and other project management software can highlight the series of tasks that form the critical path.
 ACTIVITY CREATE WBS
You and group member create WBS for your project
ESTIMATE TASK COMPLETION TIMES AND COSTS
Task duration can be hours, days, or weeks depending on the project. Because the following example uses days,
the units of measurement are called person-days.

A person-day represents the work that one person can complete in one day. This approach, however, can
present some problems.
For example, if it will take one person 20 days to perform a particular task, it might not be true that
two people could complete the same task in 10 days or that 10 people could perform the task in two days.

Some tasks can be divided evenly so it is possible to use different combinations of time and people, up to a
point. For instance, if it takes two persondays to install the cables for a new local area network, one person
might do the task in two days, two people in one day, or four people in half a day.

In most systems analysis tasks, however, time and people are not interchangeable. If one analyst needs two
hours to interview a user, two analysts also will need two hours to do the same interview.

Project managers often use a weighted formula for estimating the duration of each task.
The project manager first makes three time estimates for each task: an optimistic, or best-case estimate (B), a
probable-case estimate (P), and a pessimistic, or worst-case estimate (W). The manager then assigns a weight,
which is an importance value, to each estimate. The weight can vary, but a common approach is to use
ESTIMATE TASK COMPLETION TIMES AND COSTS

The weight can vary, but a common approach is to use a ratio of B = 1, P = 4,

and W = 1. The expected task duration is calculated as follows:
best-case estimate (B),
a probable-case estimate (P), and a pessimistic,
or worst-case estimate (W).
Leadership and Project Manager
Leadership and Project Manager
 INTRODUCTION TO SYSTEM ANALYSIS & DESIGN
System Development Life Cycle (SDLC) of Clinic Management System

Project Initiation

Head of Outpatient Clinic Head of IT Department

(Client) (Project Manager)
➢ Has a business idea ➢ Arrange a
to enhance the meeting/discussion
current system
➢ Send a formal request
to IT dept which is
called system request

* System request can either be a system change or an improvement to the current

system
 INTRODUCTION TO SYSTEM ANALYSIS & DESIGN
System Development Life Cycle (SDLC) of Clinic Management System

Project Initiation

➢ Both client and project manager discuss about:

- problem in the current system
- what are the solutions
- time factor
- how will it increase the efficiency
➢ Both agrees to the terms and agreement
➢ Client then sign the agreement
➢ Project manager accept the project
 INTRODUCTION TO SYSTEM ANALYSIS & DESIGN
System Development Life Cycle (SDLC) of Clinic Management System

Planning

➢ Understanding why the system should be developed (identify the problem)

and how it is suppose to be developed

➢ Deliverables
- Feasibility Analysis/Study
* technical feasibility (Can the system be developed?)
* economic feasibility (Will it provide business value?)
* organizational feasibility (If system is developed, is it usable?)
- Project plan, Gantt Chart, Cost and Benefit Report

➢ Project manager and client bring the system request and feasibility analysis
to the steering committee for approval
➢ Once approved, the project enters into project management
 INTRODUCTION TO SYSTEM ANALYSIS & DESIGN
System Development Life Cycle (SDLC) of Clinic Management System

Planning

➢ Staff project (Designer, Programmer, DBA, Software tester, Network Manager)

- Create work breakdown structure
➢ Identify scope
➢ Identify and manage risk
➢ Gather requirements (interviews, questionnaire, observation)
- User Registration
- Login
- Homepage
- Logout
➢ Begin documentation
 INTRODUCTION TO SYSTEM ANALYSIS & DESIGN
System Development Life Cycle (SDLC) of Clinic Management System

Analysis

➢ Discuss the requirements gathered in detail (Functional and

non-functional requirement)
➢ Develop Requirements Definition

Project team
 INTRODUCTION TO SYSTEM ANALYSIS & DESIGN
System Development Life Cycle (SDLC) of Clinic Management System

Analysis

1. USER REGISTRATION 2. LOGIN

a) Username input field a) Username input field
b) Full name field b) Password field
c) New IC field c) Submit button
d) Status selection d) Read user from database
e) Module access right selection e) Log user into the system
f) Submit button
g) Save user in database

3. HOMEPAGE 4. LOGOUT
a) New user should redirect here a) Logout button
b) Existing users redirect here after b) Clear session
login
 INTRODUCTION TO SYSTEM ANALYSIS & DESIGN
System Development Life Cycle (SDLC) of Clinic Management System

Analysis

➢ Develop use cases

➢ Develop data flow diagrams
➢ Develop Entity Relationship Model (ER-D)

➢ Deliverable
- Software Requirement Specification (SRS)

Project team
 INTRODUCTION TO SYSTEM ANALYSIS & DESIGN
System Development Life Cycle (SDLC) of Clinic Management System

Design

➢ Architecture design
- describes the hardware/ software/ network/
- Eg. Client side, server side, web-based
➢ User interface design (GUI)
- layout, color scheme (purple, grey)
➢ Program design (programming language)
- ASP
 INTRODUCTION TO SYSTEM ANALYSIS & DESIGN
System Development Life Cycle (SDLC) of Clinic Management System

Design

➢ Framework
- Javascript, MySQL, MariaDB
 INTRODUCTION TO SYSTEM ANALYSIS & DESIGN
System Development Life Cycle (SDLC) of Clinic Management System

Design

➢ System server design

- client-server architecture
- network
- IP address
- server

➢ System database design

- database name
- table names
- fields
 INTRODUCTION TO SYSTEM ANALYSIS & DESIGN
System Development Life Cycle (SDLC) of Clinic Management System

Design

➢ Browser compatibility
- design so that it support various browsers
➢ Mobile support
- design so that it support various mobile framework

➢ Deliverables
- Software Design Definition (SDD)
- Database Definition Documentation (DDD)
 INTRODUCTION TO SYSTEM ANALYSIS & DESIGN
System Development Life Cycle (SDLC) of Clinic Management System

Development

➢ Operation Team will setup physical hardware (server, database)

➢ Programmers will write the code

 INTRODUCTION TO SYSTEM ANALYSIS & DESIGN
System Development Life Cycle (SDLC) of Clinic Management System

Development

➢ Designers continue to plan user interfaces

➢ Testers will start to develop test cases for the test plan
➢ Start to imagine usability of the system and see whether the user
interfaces flow together
➢ Testers might discover flaws in the early stage of the system
 INTRODUCTION TO SYSTEM ANALYSIS & DESIGN
System Development Life Cycle (SDLC) of Clinic Management System

Testing

➢ Example, when testing logout function in the system, tester found out
that the browser did not clear the session.
➢ An authorized user can use the computer to login, get the access to
all data, manipulate the system, release bugs

➢ Testers will test based on the test cases built (Unit testing/System
testing)
➢ Validate all the requirements that has been created so that all
functionality work as expected
➢ Find as many bugs as possible

➢ Deliverable
- Test Cases/Test Plan/Test Result
 INTRODUCTION TO SYSTEM ANALYSIS & DESIGN
System Development Life Cycle (SDLC) of Clinic Management System

Implementation

➢ The project team will get ready with the production server (install new
hardware, server, scalable for production)
➢ Setting up URL links, database
➢ Some organization may start with a pilot project/launch

➢ Once everything is ready, the system will Go-Live to the real users

➢ Deliverable
- Complete Functioning System
 INTRODUCTION TO SYSTEM ANALYSIS & DESIGN
System Development Life Cycle (SDLC) of Clinic Management System

Maintenance

➢ Once the system is successfully running, many users start to use the
system on a daily basis, the server and environment need to be
monitored.
➢ DBA has to monitor on the load, performance, storage so that it does
not bring the system down at any point

➢ Larger servers, databases might be needed

 INTRODUCTION TO SYSTEM ANALYSIS & DESIGN
System Development Life Cycle (SDLC) of Clinic Management System

Maintenance

➢ Bugs/errors might be found by users during production

➢ Users will write an email/call the IT dept to report the issue
➢ Programmers will then fix the bugs and deploy again

➢ Deliverable
- Operational Information System