Systems Analysis Project Deliverable 1 Project Scoping Document Outline

1
Systems Analysis ProjectDeliverable 1Project
Scoping DocumentOutline
2
Term Project Deliverable Overview

• This presentation outlines
• Term project deliverable 1, due on Friday October
  22 by 5 PM.
• Process for getting started and for gathering
  input for the deliverable

3
Overview

• Deliverable 1 will be a Scoping Document
• Organizational Background
• Business Problem
• System Capabilities
• Feasibility assessment
• Your activities / high level schedule

4
Deliverable

• Scoping Document
• A Word document
• 11 point Arial font
• Double spaced 1.25 inch margin top and bottom.
  1 inch left and right.
• Appendix
• Meeting Agenda(s)
• Meeting Notes

5
Good Document Layout

• Cover page
• TOC page
• Introduction to document
• Section headings/subheadings
• Introduction should start on page 1!

6
Grading

• Document structure and grammar (20)
• Cover page
• Section headings
• Is there an introduction to the document
• Is there active tense, good sentence structure,
  grammar and punctuation, clarity and lack of
  repetition?
• Content (80)
• Organizational Background 10
• Problem statement 25
• Project Scope System Context and Capabilities
  20
• Feasibility 10
• Activities / Schedule 5
• Agendas and notes 10

7
Background Organization

• Provide
• Brief history
• Business they are in what do they do
• Revenue, number of employees, any other measure
  of size

8
Background Sponsor

• Provide an overview of the responsibilities of
  your sponsor
• Who does he/she work for
• What area of the organization does he/she manage
• Who works with/for the sponsor
• Provide an organization chart, if available
  (optional, but useful)
• Clearly identify what part(s) of the organization
  are related to the project you will carry out

9
Background Current Information Systems

• Provide a summary of information systems that are
  related to the project you are looking at
• Remember that Information Systems do not need to
  be automated
• For any automated systems, list the software
  (packages, custom developed programs) and
  hardware that is in place.

10
Problem/Opportunity Area

• Two parts
• Project description Overview of
  problems/opportunities your sponsor would like
  you to look at (business not technical). This
  section should clearly identify WHY we are doing
  this project and the business benefits from the
  project.
• See page 88 in your text for an example
• Detailed analysis of problems to be addressed by
  your project.

11
Problem/Opportunity Drill Down

• Based on the high-level problem opportunity area,
  drill down to identify specific problems and
  opportunities
• Use the following matrix to do drill down
• List a minimum of 6 - 8 problems/opportunities
  (more would be good)

Brief Statement of Problem or Opportunity Brief statement of impact Priority (H M L or out of scope) Benefits in the problem were solved (costs avoided, revenues enhanced, customer satisfaction increased)


12
Problem/Opportunity Drill Down Example
13
Problem/Opportunity Drill Down Example
14
Project Scope System Capabilities

• This section puts the boundaries around your
  project. Provide
• Specify, at a high level, what the system will
  need to do to address the problem area.the
  CAPABILITIES the system must possess
• See page 88 in your text although I am looking
  for a bit more detail
• Specify what the system WILL NOT DO, if
  appropriate (in order to ensure that the
  boundaries of the proposed system are clear.
• Draw a context diagram (see page 89 in your text)
  for your proposed system
• Inputs and outputs

15
Feasibility Assessment

• Cultural, Resource, Schedule and Technical
• NOT economic
• In your own words, describe what each area is
  (see your text or other sources)
• Attempt to assess the feasibility of your project
  for each category

16
Project Plan

• List of key tasks
• Look at tasks associated with Systems Analysis
  Phase in your text.
• Look at the deliverables on 415 web page.
• Probably the last thing you want to work on.
• Who will work on each task (divide and conquer)
• Dependencies which tasks are dependent on the
  completion of one or more previous tasks
• In a table is fine
• Gantt chart is optional (MS Project)

17
Recommended Process

• Set up a face to face meeting with the sponsor
  suggest 1 hour to start.
• Prepare an agenda and a set of questions (this
  presentation should help you)
• Bring questions to class (if you want to review)
• Send the questions to the sponsor well in advance
  of the meeting
• Use the agenda and questions to guide the meeting
• One team member should run the meeting, the
  others should document (scribe).
• Once first meeting is completed and you have
  analyzed the results, determine if you need
  another meeting to gather required information
• If so, follow the meeting process steps outlined
  above