Task 3 & Task 4
Haq_1
Lect4.pptxProject Management Techniques Online: Chapter C &
Investigating System Requirements: Chapter 2
SBM4201 System Analysis and Design
Bahareh Berenjforoush
Systems Analysis and Design in a Changing World, 7th Edition – Online chapter C & Chapter 2
Objectives: Online Chapter and Chapter 2
Calculating Net Present Value, Payback Period, and Return on Investment
Understanding PERT/CPM Charts
Building the Project Schedule with Microsoft Project
Project Management Body of Knowledge (PMBOK)
The RMO Consolidated Sales and Marketing System Project
Systems Analysis Activities
What Are Requirements?
Stakeholders
Systems Analysis and Design in a Changing World, 7th Edition - Online chapter C & Chapter 2
2
Online Chapter C: PERT/CPM Charts
PERT/CPM chart is a network diagram with boxes that represent the tasks or activities of the project and with connecting arrows that represent the sequence and dependencies between tasks
PERT, which stands for Project Evaluation and Review Technique developed by the U.S. Department of Defense to organize, monitor, and control very large, complex defense projects
CPM, which stands for Critical Path Method, was developed independently
In practice, the two techniques are combined
Systems Analysis and Design in a Changing World, 7th Edition - Online chapter C
PERT/CPM chart Critical Path
Early start time – the earliest time that a task can begin due to predecessor durations
Late start time – the latest time that a task can start to maintain the schedule
Slack time – the amount of time a task or leg of sequential tasks can be delayed without impacting the project schedule
On Critical Path
Not On Critical Path
Systems Analysis and Design in a Changing World, 7th Edition - Online chapter C
Create Work Breakdown Structure (WBS) First Iteration of CSMS Project
Systems Analysis and Design in a Changing World, 7th Edition - Online chapter C
PERT/CPM chart After identifying task dependencies
Systems Analysis and Design in a Changing World, 7th Edition - Online chapter C
Work Breakdown Structure (WBS) With Predecessor Information added
Systems Analysis and Design in a Changing World, 7th Edition - Online chapter C
Project Management Body of Knowledge (PMBOK)
This section is based on the Project Management Body of Knowledge (PMBOK) that has been developed by the Project Management Institute (PMI)
PMI is a nonprofit professional organization with members from every industry and large organization in the United States as well as major international organizations
With 500,000 members, it sponsors various conferences and workshops around the globe on project management
Systems Analysis and Design in a Changing World, 7th Edition - Online chapter C
Project Management Body of Knowledge (PMBOK)
PMBOK Has 10 Major Categories
Project scope management
Project time management
Project cost management
Project quality management
Project human resources management
Project communications management
Project risk management
Project procurement management
Project stakeholder management
Project integration management
Systems Analysis and Design in a Changing World, 7th Edition - Online chapter C
Project Scope Management
Objectives
To precisely define the functions and capabilities to be included in the new system
To verify that the identified capabilities are necessary and are important priorities for the project at hand
To control the set of functions so it doesn’t grow inappropriately
Techniques
Defining the scope
Verifying the scope
Controlling the scope
Systems Analysis and Design in a Changing World, 7th Edition - Online chapter C
Project Time Management
Objectives
To ensure that the project schedule accurately accommodates the work to be done
To effectively use resources and techniques to accelerate the overall time to completion
To accurately measure completed work to correctly assess the percentage completed
Techniques
Building the schedule
Modifying the schedule
Optimizing the schedule
Systems Analysis and Design in a Changing World, 7th Edition - Online chapter C
Project Cost Management
Objectives
To accurately estimate the anticipated project costs
To accurately predict the cash flow and timing of expenditures
To confine actual project expenditures to those that are included within the plan
To capture and record actual project expenditures correctly
Techniques
Estimating costs
Controlling expenditures
Systems Analysis and Design in a Changing World, 7th Edition - Online chapter C
Project Quality Management
Objectives
Easy to use
Fit for its intended purpose
Robust
Reliable
Secure
Maintainable
Techniques
Quality assurance (QA) planning
Quality reviews
Systems Analysis and Design in a Changing World, 7th Edition - Online chapter C
Project Human Resources Management
Objectives
To ensure that the project team is staffed at the right time with people who have adequate skills in the right mix
To provide appropriate training and development opportunities for members of the team
To organize the project team and sub-teams for effective work
To encourage work teams to become effective working units
To provide the leadership and vision necessary to encourage and motivate members of the team
To ensure that the working environment, including facilities, tools, and support, is conducive to accomplishing work
Systems Analysis and Design in a Changing World, 7th Edition - Online chapter C
Project Communications Management
Objectives
To ensure that the necessary information is gathered in a timely manner and is complete and accurate
To ensure that project information is disseminated frequently and is an accurate representation of the project
To ensure that members of the project team have current information
To capture and record important project information in a central information repository
Techniques
Planning for gathering information, internal communications, and dissemination of project information
Systems Analysis and Design in a Changing World, 7th Edition - Online chapter C
Project Risk Management
Objectives
To determine the potential areas of high risk for the project
To develop strategies and plans of actions to reduce the identified risks
To carry out the plans of action to monitor and control the project risks
Techniques
Risk identification
Risk management
Systems Analysis and Design in a Changing World, 7th Edition - Online chapter C
Project Procurement Management
Objectives
To plan the procurement process
To ensure that solicitation documents are complete and accurate
To evaluate and select alternative providers
To ensure that contracts are adequate, with sufficient performance controls and metrics
To monitor and control deliverables
Techniques
Planning procurement requirements, development of solicitation documents, evaluating providers and alternatives, developing contracts, and monitoring and controlling deliveries
Systems Analysis and Design in a Changing World, 7th Edition - Online chapter C
Project Stakeholder Management
Objectives
Identify all the relevant stakeholders and understand their interest or role
Understand and manage the expectations of stakeholders
Manage and control stakeholder communications
Manage and control stakeholder involvement
Techniques
Similar to Communications Management
Systems Analysis and Design in a Changing World, 7th Edition - Online chapter C
Project Integration Management
Objectives
To see that the work of the project is completed successfully
Project integration management focuses on the specific tasks that ensure the project is coordinated, executed, and controlled properly
The skills from all the other knowledge areas are included in the project processes of integration management
Systems Analysis and Design in a Changing World, 7th Edition - Online chapter C
Chapter 2: Ridgeline Mountain Outfitters (RMO)
RMO has an elaborate set of information systems that support operations and management
Customer expectations, modern technological capabilities, and competitive pressures led RMO to believe it is time to upgrade support for sales and marketing
A new Consolidated Sales and Marketing System was proposed
This is a major project that grew out of the RMO strategic planning process
20
Systems Analysis and Design in a Changing World, 7th Edition - Chapter 2
RMO Information Systems Strategic Plan
Technology architecture— the set of computing hardware, network hardware and topology, and system software employed by the organization
Application architecture—the information systems that supports the organization (information systems, subsystems, and supporting technology)
21
Systems Analysis and Design in a Changing World, 7th Edition Chapter 2
RMO Existing Application Architecture
Supply Chain Management (SCM)
5 years old; Java/Oracle
Tradeshow system will interface with SCM
Phone/Mail Order System
12 years old; Visual Studio/MS SQL
Reached capacity; minimal integration
Retail Store System
Older package solution; minimal integration
Customer Support System (CSS)
Web based system; evolved over the years, minimal integration
22
Systems Analysis and Design in a Changing World, 7th Edition - Chapter 2
Proposed Application Architecture: Integrate SCM and New CSMS
23
Systems Analysis and Design in a Changing World, 7th Edition - Chapter 2
New Consolidated Sales and Marketing System (CSMS)
Sales Subsystem
Integrates online, phone, and retail stores
Order Fulfillment Subsystem
Track shipments, rate products and services
Customer Account Subsystem
Shopping history, linkups, “mountain bucks” rewards
Marketing Subsystem
Promotional packages, partner relationships, more complete merchandise information and reporting
24
Systems Analysis and Design in a Changing World, 7th Edition - Chapter 2
Systems Analysis Activities
The New Consolidated Sales and Marketing System (CSMS) will require discovering and understanding extensive and complex business processes and business rules
The SDLC indicates the project starts with identifying the problem, obtaining approval, and planning the project (as seen in Chapter 1)
To get to the heart of systems analysis, this text skips right to analysis activities generally and the specifically for the RMO CSMS project (Core Process #3)
Project planning and project management are covered I detail later in the text
25
Systems Analysis and Design in a Changing World, 7th Edition - Chapter 2
Systems Analysis Activities Involve discovery and understanding
26
Systems Analysis and Design in a Changing World, 7th Edition - Chapter 2
Systems Analysis Activities
Gather Detailed Information
Interviews, questionnaires, documents, observing business processes, researching vendors, comments and suggestions
Define Requirements
Modeling functional requirements and non-functional requirements
Prioritize Requirements
Essential, important, vs. nice to have
Develop User-Interface Dialogs
Flow of interaction between user and system
Evaluate Requirements with Users
User involvement, feedback, adapt to changes
27
Systems Analysis and Design in a Changing World, 7th Edition - Chapter 2
What Are Requirements?
System Requirements =
Functional requirements
Non-functional requirements
Functional Requirements– the activities the system must perform
Business uses, functions the users carry out
Shown as use cases in Chapter 1
Non-Functional Requirements– other system characteristics
Constraints and performance goals
28
Systems Analysis and Design in a Changing World, 7th Edition - Chapter 2
FURPS+ Requirements Acronym
Functional requirements
Usability requirements
Reliability requirements
Performance requirements
Security requirements
+ even more categories…
29
Systems Analysis and Design in a Changing World, 7th Edition - Chapter 2
FURPS+ Requirements Acronym
30
Systems Analysis and Design in a Changing World, 7th Edition - Chapter 2
Additional Requirements Categories
Design constraints –
Specific restrictions for hardware and software
Implementation requirements
Specific languages, tools, protocols, etc.
Interface requirements
Interface links to other systems
Physical requirements
Physical facilities and equipment constraints
Supportability requirements
Automatic updates and enhancement methods
Systems Analysis and Design in a Changing World, 7th Edition - Chapter 2
31
Stakeholders: Who do you involve and talk to?
Stakeholders– persons who have an interest in the successful implementation of the system
Internal Stakeholders– persons within the organization
External stakeholders – persons outside the organization
Operational stakeholders – persons who regularly interact with the system
Executive stakeholders– persons who don’t directly interact, but use the information or have financial interest
32
Systems Analysis and Design in a Changing World, 7th Edition - Chapter 2
Stakeholders of a comprehensive accounting system for public company
33
Systems Analysis and Design in a Changing World, 7th Edition - Chapter 2
Stakeholders For RMO CSMS Project
Phone/mail sales order clerks
Warehouse and shipping personnel
Marketing personnel who maintain online catalog information
Marketing, sales, accounting, and financial managers
Senior executives
Customers
External shippers (e.g., UPS and FedEx)
34
Systems Analysis and Design in a Changing World, 7th Edition - Chapter 2
RMO Internal Stakeholders
35
Systems Analysis and Design in a Changing World, 7th Edition - Chapter 2
Summary (Online Chapter C)
This online chapter supplements and enhances the printed chapters on project management
This chapter explained the foundation concepts of PERT/CPM charts and how they are developed
The Project Management Body of Knowledge (PMBOK) includes ten specific knowledge areas that are important to project management
In this chapter, each knowledge area is discussed, with an explanation given for the primary objectives of each knowledge area
Systems Analysis and Design in a Changing World, 7th Edition - Online chapter C & Chapter 2
Summary (continued, Chapter 2)
System projects originate from the information system strategic plan, which contains an technology architecture plan and an application architecture plan
Systems analysis involves defining system requirements– functional and non-functional
Systems Analysis and Design in a Changing World, 7th Edition - Online chapter C & Chapter 2
Summary (continued, Chapter 2)
Analysis activities include
Gather detailed information
Define requirements
Prioritize requirements
Develop user-interface dialogs
Evaluate requirements with users
FURPS+ is the acronym for functional, usability, reliability, performance, and security requirements
Stakeholders are the people who have an interest in the success of the project
There are internal vs. external stakeholders and operational vs. executive stakeholders
38
Systems Analysis and Design in a Changing World, 7th Edition - Online chapter C & Chapter 2
References
Satzinger .J, Jackson. R & Burd. S, 2016, Systems Analysis and Design in a Changing 7th edn, Cengage, Australia.
