Systems Design Chapter 03 Flashcards
1
Q
Project management
A
Organizing and Directing other people to achieve a planned result within a determined schedule and budget
2
Q
Reasons for Project Failure
A
- Incomplete or changing sys requirements
- Limited user involvement
- Lack of executive support
- Lack of technical support
- Poor project planning (including inadequate risk assessment)
- Unclear objectives (including unreasonable expectations)
- Lack of required resources
3
Q
Reasons for Project Success
A
- Clear system requirments
- Substantial user involvement
- Support from upper management
- Thorough and detailed project plans
- Realistic work schedules and milestones
4
Q
Project manager
A
Defines and executes project management tasks
5
Q
Project Manager Internal Tasks
A
- Identify project tasks and build a work breakdown structure
- develop the project schedule
- recruit and train team members
- assign team members to tasks
- coordinate activities of team members and subteams
- assess project risks
- monitor and control project deliverables and milestones
- verify the quality of project deliverables
6
Q
Project Manager External Tasks
A
- Report the project’s status and progress
- Establish good working relationshiops with those who identify the needed system requirements (the people who will use system)
- Work directly with the client (the project’s sponsor) and other stakeholders
- Identify resource needs and obtain resources.
7
Q
Oversight Committee
A
Clients and key managers who review and direct the project
8
Q
User
A
The person or gorup of people who will use system
9
Q
Project Mangement Process that overlap the SDLC process
A
executing, controlling, and closing the project out.
10
Q
Project Management Tasks
A
- Begining of Project - Overall planning
- During project:
- Project execution management
- Project Control Management
- Project Closeout
- Project management approach differs for Predictive SDLC & Adaptive SDLC
11
Q
Project Mangement & SDLC Tasks for a predictive project
A
Project Execution mgmt and Project control mgmt over analysis design & implementation. Project closeout over deliverable.
12
Q
Project Management & SDLC Tasks for an Adaptive Project
A
For each cycle:
- Detailed cycle plan
- Together:
- -Cycle execution
- -Cycle control mgmt
- Ending Cycle Close out
All over Analysis/design/implementation to deliverable.
13
Q
PMBOK - Scope Management
A
- Control Functions included in system
- Control scope of work done by team
14
Q
PMBOK - Time Management
A
- Build Detailed Schedule of all project tasks
- Monitor progress of project against milestones
15
Q
PMBOK - Cost Mangement
A
- Calculate initial cost/benefit analysis
- Montior expenses
16
Q
PMBOK - Quality management
A
Establish quality plan and control activities for each project phase
17
Q
PMBOK - Human Resource Mangement
A
- Recruit and hire project team members
- Train, motivate, team build
18
Q
PMBOK - Communications Management
A
- Identify statekholders and their communications
- Establish team communications
19
Q
PMBOK - Risk Management
A
- Identify and review risks for failure
- develop plans to reduce these risks
20
Q
PMBOK - Procurement Management
A
- Develop requests for proposals (RFPs)
- Evaluate bids, write contracts, monitor performance
21
Q
PMBOK - Integration Mangement
A
Integrating all the other knowledge areas into one seamless whole
22
Q
Three driving forces to start IS project
A
- Respond to opportunity - Top-down
- Resolve problem - Bottom up
- Conform to directive - Legislative changes
23
Q
Defining the problem
A
- Review business needs
- use strategic plan documents
- consult key users
- develop list of expected business benefits
- Identify expected System capabilties
- define scope in terms of requirements
24
Q
Business Benefits
A
Influences that can change the financial statements - decreasing costs, increasing revenues
25
Deliverables of problem defining activity
1. System Scope Document - a document that contains problem description, business benefits, and system capabilties.
2. Proof of concept prototype
3. Context diagram
26
Producing the Project Schedule
1. Developing a work breakdown structure WBS
2. building a schedule using a Gantt chart
3. Develop resource requirements and the staffing plan
27
Activities & Tasks
1. Activity is made up of a group of related tasks or other smaller activities
2. A task is the smallest piece of work that is identified and scheduled - can't be broken down further
28
WBS - Work Breakdown Structure
1. WBS is a list of all the required individual activities and tasks for the project.
2. Two approaches for building a WBS - By deliverable or by timeline
29
4 Techniques for identifying tasks
1. Top-Down- identifying the major activities and then listing internal tasks
2. Bottom-up - Listing all the tasks you can think of and organizing them later
3. Template - Using standard template of tasks
4. Analogy - find a similar project that is finished and cophying its tasks
30
Charts used to develop a project schedule
1. Pert Chart - tells us the minimum days reuqired or earliest possible completion date
1. a technique for scheduling a project based on individual tasks or activities
2. MS Project calls it a network diagram
2. Gantt Chart
1. a bar chart that represents the tasks and activities of the project schedule against a calendar
31
Critical Path
The sequence of tasks that determine the length of the project
It indicates the earliest date that the project can be completed
32
Slack Time / Float
Amount of time an task can be delayed wihtout having a negative impact on the project completion date
33
Milestone
A precise point on the project schedule that indicates a specific completion point
34
Confirming Project Feasibility
1. Risk Management
2. Economic feasibility - Cost/benefit analysis & Sources of funds (cash flow, long-term cap)
3. Organizational and cultural feasibility
4. Technological feasibility
5. Schedule Feasibility
6. Resource Feasibility
35
Risk Description
1. Critical team member not available
2. Chaging legal requirements
3. employees not computer savvy
36
Organization and Cultural Feasibility
Each company has own culture - new system must fit into culture
Evaluate related issues for potential risks
37
Organizational & Cultural Issues
1. Low level of computer competency
2. Computer phobia
3. Perceived loss of control
4. Shift in power
5. Fear of job change or employment loss
6. Reversal of established work proceedures
38
Technological Feasibility
1. Does system stretch stateof the art tech
2. does inhouse expertise presently exist for development
3. does an outside vendor need to be involved
4. solutions include
1. training or hiring more experienced employees
2. hiring consultants
3. changing scope and project approach
39
Schedule Feasibility
1. Estimates needed without complete information
2. Mangement deadlines may not be realistic
3. Project Managers
1. drive realistic assumptions and estimates
2. recommend completion date flexibility
3. assign interim milestones to periodically reassess completion dates
4. involve experience personnel
5. manage proper allocation of resources
40
Resource Feasibility
1. Team member availability
2. Team skill levels
3. computers equipment and supplies
4. support staff time and availablility
5. physical facilities
41
Economic Feasibility
Is the aniticipated value of the benfits greater than projected cost of development
does organization have adequate cash flow to fund the project during the delveopment period
42
Cost/Benefits Analysis
3 step process
Estimate the anticipated development costs and operational costs
estimate the anticipated financial benefits
caculated from the dedtailed estimates of costs and benefits
43
Development Costs
1. Salaries and wages
2. Equipment and installation
3. software and licenses
4. consulting fees
5. training
6. facilities
7. utilities and tools
8. support staff
9. travels and miscellaneous
44
Operating Costs
1. Connectivity - pay service provider
2. Euqipment maintenance
3. Upgrade software
4. computer operations
5. program support
6. amortization of equipment
7. training and ongoing assistance
8. supplies
45
NPV - Net Present Value
The net benefits and costs for an investement in today's dollars
46
Payback Period
The time period in which the benefits have offset the costs
47
ROI - Return on Investment
A measure of percentage gain from an investment in the new system
48
Formula for discount factor
1/(1+discount)n
Where N=year
49
Formula for Payback Period
Number of years in red + (last year amount in red/(last year amount in red + first year amount in black))
50
Formula for ROI
(Benefits - Costs)/Costs
51
Source of Benefits
1. Reducing Staff
2. Increasing volume of work
3. Decreasing operating expenses
4. Reducing error rates
5. achieving quicker processing speed
6. bettering money management
7. reducing paperwork costs
52
