Structured Systems Analysis and Design



IFSM 636

Group Project Requirements

Deliverable 1: Baseline Project Plan

The objective of this deliverable will be to describe the proposed project in detail and to determine whether it is worth pursuing. Each systems analysis group is required to conduct an examination of the organization with which they are working and produce a report that contains the following components:

• Title of the project

• A description of the organizational environment for which this system is being developed, including name, location(s), size (approximate), major areas of business or activity, organizational type (commercial, non-profit, governmental, educational, etc.). You may include other aspects that will enhance your overall understanding of the organization.

• Baseline Project Plan

• Introduction

• A detailed Problem Statement that documents the problem or opportunity that is motivating this project. The problem statement should include what aspect of the current organizational situation will be improved or ameliorated by carrying out the project. If relevant, a brief description of current information systems that provide services to the organization could be included.

• Scope statement - a brief description of the people, business functions or processes, and locations that will be impacted by this undertaking. This should also describe the manner in which each of these entities and functions will be impacted by this system. It should also include, if appropriate, related issues that are not within the scope of the project.

• A brief section on your group's recommendation. This should include the decision to go ahead with this project or not, as well as a summary of the justification for the decision. If your team has changed the definition of the project in any way as a result of your feasibility analysis, please describe these changes here.

• System Description

• A brief description of the “obvious” solution to the problem outlined above, i.e. the system that you believe, at this point, will probably be recommended after the analysis phase. It is this belief, or assumption, that underlies the feasibility analysis that comes later. This description should only be as detailed as your current thinking about it.

• An outline of alternative solutions that will also be investigated.

• Feasibility analysis

• Economic feasibility – identify all relevant costs and benefits, indicating which are tangible and which are intangible, which are one-time and which are recurring, and quantify at least some aspects. This information should be well-organized and presented clearly.

• Technical feasibility – describe the technical issues that will be relevant in this project and discuss whether or not your team has the capabilities required or if others will have to be involved.

• Operational feasibility – address, at least briefly, the relevant issues affecting operational feasibility, including whether or not the problem can be solved, how users are likely to accept a new or modified system, and if there are any compatibility issues with other existing systems.

• Legal and contractual feasibility - address, at least briefly, the relevant issues affecting legal and contractual feasibility.

• Political feasibility - address, at least briefly, the relevant issues affecting political feasibility.

• Schedule feasibility – include a preliminary schedule of the entire project (not just this semester’s work, but all the way to implementation and testing), and your assessment of the probability that the schedule will be met.

• Management issues

• Team members – for each member of the project team, include name, work and educational background (brief), special skills relevant to the project, and major role the member is expected to play on the project team.

• Identify any risks or constraints on the project. These may be schedule, budget, policy, or any other constraints or risks that your group can identify in the preliminary assessment of the organization. These should include anything that you think may become a problem or obstacle to the successful completion of this project.

• A Statement of Work, written for your customer (give them a copy), that states precisely what they should expect from you. This should be written in terms that the customer will understand well. It should include a version of your problem and scope statements, and possibly a simplified description of the “obvious” solution you’ve identified (although you must also say that other alternatives will be investigated and the final solution may be different). Also outline what you expect will be necessary in terms of customer contact (i.e. how many hours of their time will you require).

• A brief description of the manner in which you gathered information for forming this report. Specifically, this should identify the fact-finding approaches you used to support this deliverable, the sources of information you used, and any other techniques you used to identify and clarify problems, opportunities, and goals.

• Finally, you are free to provide any materials that will support your findings and conclusions in this report.

Important Requirements for your Report

Your deliverable must be well organized, with clear headings delineating the sections, and the sections in the order listed above. All deliverables must be submitted in a single file whenever possible, not broken up into separate files. If separate files are necessary, please send me an email explaining why the deliverable is broken up into different files and what each file contains. These requirements apply to all deliverables on this project.

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download