Information Systems
College of Business Administration
University of Missouri - St. Louis
Final Paper/Presentation

BACKGROUND

      Learn history and issues about client      
Evaluate public sources, such as newspapers, the internet and local and/or

      Identify similar systems

      Identify basic characteristics of that type of system

      Learn jargon

      Evaluate environment      
Competition      
Technology      
Capital      
People      
Raw Materials      
Regulation      
Data      
Opportunities

      Develop questions for client


SYSTEM DESCRIPTION

      Identify stakeholders

      Interview Client and Stakeholders

      Identify client’s perception of the problems

      Identify client’s goals, requirements and expectations

      Review systems, manuals, forms and other written materials

      Identify system characteristics (Inputs, Outputs, Processes, Stakeholders)

      Identify stakeholders’ perspectives

      Determine client’s perception of solutions

      Determine stakeholders’ perceptions of solutions

      Document:      
current system description      
current deficiencies      
opportunities

      Identify problems and opportunities      
from your analysis      
from client’s perception      
from stakeholders’ perceptions

      Create data flow diagram of current system

      Create written description of the situation


COST-BENEFIT STUDY

      Define scope of proposed system in terms of its functions, users, dimensions and constraints

      Define and document possible types of solutions

      Examine the costs of similar systems.

      Produce a rough estimate of the system size, costs, schedules, etc.

      Evaluate gross estimates of costs and benefits for various solutions

      Evaluate business need for various systems

      Compare the business needs and the cost/benefit analyses of systems

      Propose one or more systems – provide brief descriptions of systems, needs and costs/benefits

      Refine environmental influence document

      Refine system description

      Identify deliverables of proposed solutions

      Proposed tentative schedule for the delivery of key stage deliverables

      Define the benefits of the system. Include both quantitative and qualitative measures

      Refine proposed system description

      Present potential systems to client for review

      Present potential systems to stakeholders for review

      Further analyze system

      Refine the scope of the new system


QUESTIONNAIRE/INTERVIEW

      Determine issues for consideration

      Determine      
their uses of the current system      
perceived deficiencies of the current system      
their requirements for the new system.

      Interview (or use questionnaire) with all users and stakeholders


SYSTEM SPECIFICATIONS

      Develop detailed set of user-specified requirements for the new system

      Summarize and critique new system requirements. Include:      
prioritized user requirements      
resolution of current system's deficiencies.

      Develop a list of benefits.      
Include both tangible and intangible benefits and costs      
Include both quantitative and qualitative benefits and costs

      Produce detailed estimate of costs, schedules, resources, and the like, including a schedule for the production of major deliverables.

      Refine System description

      Identify Data requirements

      Identify Network and telecommunications requirements

      Identify System controls (password access, recovery/restart, etc.)

      Identify Revised cost/benefit analysis and payback schedule

      Identify Estimates of the next stage and remainder of project

      Identify potential risks associated with the plan

      Refine the system description

      Consider the physical, environmental, and operational constraints into system constraints.

      Evaluate possibilities such as on-line, transation-based, distributed, centralized, terminals, workstations, etc.

      Draw diagrams of proposed system (including data flow and entity-relationship diagrams)      
Create data flow diagrams of proposed system      
Create use case diagrams of proposed system      
Create entity-relationship of proposed system

      Develop system data dictionary

      Document all interfunction and interdata relationships

      Ensure compatibility with corporate systems

      Review and expand cost-benefit analysis

      Produce system specifications document

      Review system specification document with client and stakeholders


CREATE PROTOTYPE

      Review prototype with client and stakeholders

      Refine alternative system descriptions

      Refine data requirements

      Refine technical specifications

      Refine cost-benefit analysis

      Recommended design alternatives: prototyping techniques, phased development, etc.

      Recommended implementation techniques, self code purchased packages, or external development

      Develop system test plan

      Identify system controls


| UM-St. Louis Home Page | College of Business Page | IS Home Page | Analysis Home Page |



Page Owner: Professor Sauter (Vicki.Sauter@umsl.edu)

© Vicki L. Sauter. All rights Reserved.