BSc-SysAnal-1- Introduction.pptx

Dr. K. Salimifard (Assoc. Prof.)
ciiorg.pgu.ac.ir
Persian Gulf University
salimifard
k_salimifard ksalimifard@gmail.com

BSc –System Analysis & Design - Intro
Dr. K. Salimifard (C) ..: ciiorg.pgu.ac.ir 2

• An open system of rules, roles, procedures, equipment,
technology and people to produce products and provide
services to satisfy customers.
• Processes are done using procedures, resources, and take
time and use money.
• The better the processes, the better the organization.

• Definition of business analysis & business analyst
profession
• Exploring the knowledge areas of business analysis
• Definition of requirements & its types
• Project Manager vs Business Analyst
• SDLC

Plan Build Test Implement

• Only 16.2% of projects will be completed on time & on budget
• About 40-56% of project conflicts can be traced to requirement
errors
• Finding and fixing requirement errors consumes 70-85% of
project rework costs
• The average project exceeds its planned time schedule by 120%
• About 52.7% of projects will cost 189% of their original estimate
• About 30% of projects are cancelled before completion.

Describe Define Plan Build Test Implement
Business Analysis Project Management

• “A business analyst works as a liaison among
stakeholders in order to analyze, communicate, and
validate requirements for changes to business processes,
policies, and information systems.”

• Project managers are responsible for delivering the
solution to a problem.
• Main concern: project process
• Focus on: big picture
• Defines: schedule, tasks, risks

• Business analysts are responsible for discovering the
problem and determining the solution.
• Main concern: project requirements
• Focus on: minor details
• Defines: requirements

Solution
who
what
Where Why
When
how

• Gathering & prepare business requirements
• Plan & document requirements
• Analyze & model requirements
• Take up change requests
• Perform acceptance testing

Business Requirements
• higher-level statements of the goals, objectives, or needs of
the enterprise.
User Requirements
• statements of the needs of a particular stakeholder or class of
stakeholders.
System Requirements
• describe the behavior and information that the solution will
manage

• A functional requirement describes what a system should do
• Example - A system must send an email whenever a certain condition is
met (e.g. an order is placed, a customer signs up, etc.)
• The non-functional requirement is describing the behavior
of the system as it relates to the system's functionality.
• The non-functional requirement elaborates a performance
characteristic of the system.
• Example - Emails should be sent with a latency of no greater than 12
hours from such an activity.

• Requirements Should be
• Complete
• Correct
• Confirmable
• Concise

• Requirements Elicitation
• finding out what customers (and potential customers) say they
think they want.
• It produces a wish list.
• Requirements Analysis
• distilling the wish list to produce a list of actual requirements
together with dependencies between them.
• It also involves saying that some things on the wish list are out of
scope for one reason or another.

• Requirements specification
• the process of recording the requirements in one or more
forms, including natural language and formal, symbolic, or
graphical representations.
• Requirements validation
• the process of confirming with the customer or user of the
system that the specified requirements are valid, correct, and
complete.

• The SDLC is a process for planning, creating, testing,
and deploying an information system.
• There are usually six stages in this cycle: requirement
analysis, design, development and testing,
implementation, documentation, and evaluation.
• It consists of a detailed plan describing how to develop,
maintain, replace and alter or enhance specific
system.

planning
defining
designing
building
Testing
deployment

• Waterfall Model
• Iterative Model
• Spiral Model
• Agile Model

• Waterfall is best used for simple, unchanging projects.
Its linear, rigid nature makes it easy to use and allows for
in-depth documentation.
• Changes can’t be easily accommodated
• The system isn’t delivered until late
• Gathering accurate requirements can be
challenging

• Initially, a partial implementation of a total system is
constructed so that it will be in a deliverable state.
Increased functionality is added.
• Defects, if any, from the prior delivery are fixed and the
working product is delivered.
• The process is repeated until the entire product
development is completed.

cost
review
1 2
3
4
• The spiral model adds Risk Analysis and RAD
prototyping to the Waterfall model. Each cycle involves
the same sequence of steps as the Waterfall model.

• Spiral model has four quadrants.
• Quadrant 1 - Determine objectives, alternatives and
constraints
• Quadrant 2 - Evaluate alternatives, identify and resolve
risks
• Quadrant 3 - Develop next-level product
• Quadrant 4 - Plan next phase
cost
review
1 2
3
4

• Agile software development is based on an incremental,
iterative approach.
• Change is embraced
• Faster, high-quality delivery
• Strong team interaction
• Continuous improvement
• Customers are heard

• Agile software development is popular among
developers. There are different methodologies that can
be categorized as Agile Models. Have an online search,
and write a report to briefly introduce them and their
steps.
• Save your report as yourFullName-HW1.docx
• Submit by 1401/11/30 on the LMS.

Next Lec

BSc-SysAnal-1- Introduction.pptx

Recommended

Recommended

More Related Content

Similar to BSc-SysAnal-1- Introduction.pptx

Similar to BSc-SysAnal-1- Introduction.pptx (20)

Recently uploaded

Recently uploaded (20)

BSc-SysAnal-1- Introduction.pptx