ISQS 4348 Deliverables

Feasibility Study

Outline:

Cover page (Cover page includes Name of deliverable, name of project, team # and team members listed in alphabetic order)

System Summary (Brief one paragraph description of the system)

Project Summary

Project Name: (This is the name of your project)

Responsible User (The responsible user is the person paying the bill)

Responsible Analyst(s) (This is the system analysis team)

Scope (This is where you carefully define what is in and what is not in your project)

Start Date (This is the beginning of semester)

Project Completion Date (This is the end of next semester when you implement your system)

Completion Date for Structured Specification (This is the end of the analysis phase)

Project Budget Amount (This is the total from your cost benefit analysis)

Background for Problem being solved (This is a comprehensive description of the problem and why it is a problem)

Data Collecting Sheets (This is the documentation from your data collection. It may include interview notes, memos to and from users, surveys and survey results, any other documentation that you were given or developed to help you with the analysis)

System Description (includes context) (This includes a description of the system you think you will be designing with a context diagram. Include tangible and intangible costs and benefit descriptions)

New system constraints and assumptions (List constraints on the new system such as time limits, money limits, equipment constraints, software constraints, etc. Also list any assumptions you are making in the analysis. The assumptions are caveats to the CBA as well as assumptions concerning the system environment, etc.)

Specific Performance Requirements (Just as it says, this is where you list specific requirements concerning the performance of a new system)

Interfaces to Other Systems (This is where you would describe any interfaces to other systems, either manual or electronic)

Cost/Benefits Analysis:

Technical Feasibility (This is a description of the technology that may be used and why it is or is not feasible. May include information on alternative solutions)

Economic Feasibility (This is a spreadsheet)

One time cost

Ongoing cost (Look at the example)

Benefits

Net present value analysis and Break-even point (re: example)

Baseline Project Plan (This is the time frame, or time line when work will occur and when it is due to be complete.)

ISQS 4348

Systems Analysis

Requirements Specification

The Requirements Specification Report should have the following format:

Cover page

Table of contents (if appropriate, meaning if it is very long)

Introduction

Requirements

· Strategic requirement # 1 with explanation, in terms that are measurable and in business vernacular

· Tactical requirement #1 with explanation in terms that are measurable but may be more technical.

· Tactical requirement # 2, ….

· Tactical requirement # 3, ….

· Tactical requirement #N, ….

· Strategic requirement # 2, …….

· Tactical requirement #1 with explanation in terms that are measurable but may be more technical.

· Tactical requirement # 2, ….

· Tactical requirement # 3, ….

· Tactical requirement #N, ….

· Strategic requirement # 3,…….

· Tactical requirement #1 with explanation in terms that are measurable but may be more technical.

· Tactical requirement # 2, ….

· Tactical requirement # 3, ….

· Tactical requirement #N, ….

· Strategic requirement # N, …..

· Tactical requirement #1 with explanation in terms that are measurable but may be more technical.

· Tactical requirement # 2, ….

· Tactical requirement # 3, ….

· Tactical requirement #N, ….

Summary