Title: Class Outline 4
Course: KVCC_BUS205 > Section: Class Outlines

1.      Opening Case as an illustration

2.      RMO Returns

a.      Consolidated Sales and Marketing System Project

i.           Existing Structure

1.      5 year planning

2.      Technology adoption

3.      Major Systems

a.      Supply Chain Management (SCM)

b.      Phone/Mail order systems

c.      Retail Store System (RSS)

d.      Customer Support System (CSS)

4.      Shortcomings

ii.           New System

1.      Four Subsystems

a.      Sales

b.      Order Fulfillment

c.      Customer Account

d.      Marketing

3.      Systems Analysis

a.      SDLC Activities

i.           Discover and Understand details

1.      Gather detailed information

a.      Interview

b.      Watch

c.      Read

d.      Examine current systems

e.      In short become an expert

2.      Define requirements

a.      What functions must the system perform

3.      Prioritize requirements

a.      What is essential

b.      Scope creep

4.      Develop user-interface dialogs

a.      Provide users with an example or prototype

5.      Evaluate requirements with users

a.      Check back to verify

b.      System Requirements and FURPS

i.           Functional Requirements

1.      Activities that the system must perform

ii.           Non Functional Requirements

1.      Any characteristics besides those it must perform or support

2.      FURPS

a.      F = Functional

b.      U = Usability, related to users such as interface

c.      R = Reliability, dependability of the system

d.      P = Performance, measures of workload

e.      S = Security, access control

3.      +

a.      Design constraints

b.      Implementation

c.      Interface

d.      Physical

e.      Supportability

c.      Stake Holders

i.           What is a stakeholder

ii.           Types

1.      Internal Stakeholders - within the organization

2.      External Stakeholders - outside the organization

3.      Operational Stakeholders - those that use the systems

4.      Executive Stakeholders - not directly using but need information from system

5.      Clients

6.      Technical and Support Staff

iii.           Stakeholders at RMO

4.      Information Gather Techniques

a.      Interviewing users and other stakeholders

b.      Distributing and collecting questionnaires

c.      Reviewing inputs, outputs, and documentation

d.      Researching Vendor solutions

e.      Collecting active user comments and suggestions

5.      Interviewing

a.      Prepare detailed questions

i.           Question Themes

1.      What are the business operations and processes?

2.      How should those operations be performed?

3.      What information is needed to perform those operations?

ii.           Question Types

1.      Open-ended questions

2.      Closed-ended questions

b.      Meet with individuals or groups of users

i.           Preparing for the interview

ii.           Conduction the Interview

c.      Obtain and discuss answers to the questions

d.      Document the answers

e.      Follow up as needed in future meetings or interview

Attached Files:
- KVCC BUS205_BusSysAnalysis_Outline 5.pdf
- KVCC BUS205_BusSysAnalysis_Outline 4.pdf