slide1
Download
Skip this Video
Download Presentation
c h a p t e r

Loading in 2 Seconds...

play fullscreen
1 / 10

c h a p t e r - PowerPoint PPT Presentation


  • 93 Views
  • Uploaded on

c h a p t e r. 2. The Analyst as a Project Manager. SYSTEM DEVELOPMENT LIFE CYCLE. PROJECT PLANNING SYSTEMS ANALYSIS SYSTEM DESIGN IMPLEMENTATION SUPPORT / PRODUCTION & MAINTENANCE *. Planning Phase. Define the problem Sketch out a schedule Determine feasibility

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about ' c h a p t e r' - bruno-stokes


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
slide1

c h a p t e r

2

The Analyst as a Project Manager

system development life cycle
SYSTEM DEVELOPMENT LIFE CYCLE
  • PROJECT PLANNING
  • SYSTEMS ANALYSIS
  • SYSTEM DESIGN
  • IMPLEMENTATION
  • SUPPORT / PRODUCTION & MAINTENANCE

*

planning phase
Planning Phase
  • Define the problem
  • Sketch out a schedule
  • Determine feasibility
  • Confirm other resources: staff, $$, management support etc.
feasibility
FEASIBILITY
  • TECHNICAL:
    • Assess Hardware, Software, Technical, $$$ Resources
  • UNDERSTANDING BUSINESS VALUE OF INFORMATION SYSTEMS:
    • Financial Considerations:
      • Tangible Benefits: Cost reduction, increased operational efficiency, cost/benifit
      • NPV, Beak even, payback method, ROI, NPV, cash flow etc.,
    • Non-Financial / Strategic Considerations
      • Better service, speed, quality, implementation time etc.
      • Score carding, Portfolio Analysis
  • Can we and do we want to Implement Change?
analysis phase
Analysis Phase
  • What problem is the organization trying to solve with IS?
    • What are the symptoms / causes?
  • Gather INFO & determine CFS/KSF for IS:
    • Small #, easily identifiable goals
    • Shaped by manager, customers, competitors, users etc.
  • What / who / why requires information?
  • Define system requirements
    • e.g. processing requirements
  • Prototype to help define requirements
  • Generate alternatives: buy, build outsource etc.
  • Compare alternatives and feasibility
  • Make recommendations with management
design phase
Design Phase
  • Design network of Hardware O/S, etc.
  • Design application architecture
    • Large portion of the project
  • Design user interface (prototype?)
  • Design system interfaces/middleware
  • Design and integrate DBMS
  • Prototype if further details needed
  • Design and integrate system controls / security
  • As the project is planned it may cause you to loop back and go to the analysis mode to gather more information
  • Ripple effect
implementation phase
Implementation Phase
  • The phase where the new system is programmed
  • Construct software components
  • Verify and test
  • Convert existing data
  • Train users
  • Convert to the new system
testing
TESTING
  • UNIT TESTING: Tests Each Unit Separately
  • SYSTEM TESTING: Do Modules Function Together as planned?
  • Acceptance Testing
    • Alpha Testing: limited rollout.
    • Beta Testing: more widespread rollout.
      • E.g., Windows 2000

*

support maintain upgrade phase
Support/maintain/upgrade Phase
  • Maintain (bug fix)
  • Enhancements/features/upgrades
  • Support for the users
a few more terms
A few more terms
  • Proof of concept prototype
    • A document containing business benefits and system capabilities of the projects
    • Helps to define the scope of a new project
  • Context diagram:
    • a graphical diagram showing the scope of a system. Who / what / why / what for uses of info
  • MS project
    • Work breakdown structure
    • Gantt Chart
    • Pert/CPM (Project evaluation and review technique / critical path method)
ad