Unlock document.
This document is partially blurred.
Unlock all pages and 1 million more documents.
Get Access
Abstract
This paper documents the analysis, design and implementation of the System Development
Project for Bead Bar. The project will look into the reconstruction and augmentation of the
network structure, application, database file system and mobile options. The systems
development life cycle in this project because of its complexity, will be divided into
smaller, more easily managed segments or phases. Segmenting the project allows
managers to verify the successful completion of project phases before allocating resources
to subsequent phases.
Introduction
The hardware and software development of this project will typically include planning,
design, development, testing, implementation, and maintenance phases. However, the
phases may be divided differently depending on the organization input. For example,
initial project activities might be designated as request, requirements-definition, and
planning phases, or initiation, concept-development, and planning phases. For this project
we will be using a typical structured outline. The end users of the system under
development will be involved in reviewing the output of each phase to ensure the system is
being built to deliver the needed functionality.
The subcomponents that play a role in the project need to fulfill some certain requirements.
These requirements come out from the end user recommendations, and the features that
will be available in the new version.
The initial Planning Phase will produce an outline of the project. Serving as the basis for
acquiring the resources needed to achieve our definitive goal. Outline inserted for review:
Business Considerations:
Strategic business and technology goals and objectives;
Expected benefits measured against the value of current technology;
Potential organizational changes regarding facilities or the addition/reduction of end users,
technicians, or managers;
Budget, scheduling, or personnel constraints; and
Potential business, regulatory, or legal issues that could impact the feasibility of the
project.
Functional Requirements:
End-user functional requirements;
Internal control and information security requirements;
Operating, database, and backup system requirements (type, capacity, performance);
Connectivity requirements (stand-alone, Local Area Network, Wide Area Network,
external);
Network support requirements (number of potential users; type, volume, and frequency of
data transfers); and
Interface requirements (internal or external applications).
Project Factors:
Project management methodology;
Risk management methodology;
Estimated completion dates of projects and major project phases; and
Estimated costs of projects and major project phases.
Cost/Benefit Analysis:
Expected useful life of the proposed product;
Alternative solutions (buy vs. build);
Nonrecurring project costs (personnel, hardware, software, and overhead);
Recurring operational costs (personnel, maintenance, telecommunications, and overhead);
Tangible benefits (increased revenues, decreased costs, returntion-investments); and
Intangible benefits (improved public opinions or more useful information).
Once theprovisional approval to initiate this project is obtained, the requested
documentation will serves as a starting point to conduct a more thorough feasibility study.
