Slide 3

Question 1

Why IS Projects Are Hard

Answer 1

1. High Stakes
    Capital and human resource intensive
    Mission critical & highly visible
2. Complexity
    Cross functional in nature
    Large scale
    Rapidly changing technology and requirements

Question 2

What is systems development cycle (SDLC)

Answer 2

What: The activities that go into developing information system solutions to an organizational problem or opportunity

 Formal process
 Comprehensive (hopefully leaves no stones unturned)
 Repeatable

Question 3

How to create a systems development cycle (SDLC)

Answer 3

 Analyze critical business processes

 Break the opportunity/problem into pieces smaller and more manageable

Question 4

a systems development cycle (SDLC):

Answer 4

the overall process for developing information systems from planning and analysis through implementation and maintenance (7 steps)
planning, analysis, design, development, testing, implementation, maintenance

Question 5

SDLC, Planning phase

Answer 5

Planning phase – involves establishing a high-level plan of the intended project and determining project goals

Question 6

SDLC - Systems Analysis- Planning :

Answer 6

Purpose:
 Define the problem(s)
 Identify the causes of the problem(s)
 Specify potential solutions  Determine if the potential solution(s) are achievable (Feasibility Study)

Question 7

Types of Feasibility (systems analysis - planning)

Answer 7

 Economic: Can we afford to do this, do the benefits outweigh the costs?
 Technical: “Do H/W & S/W exist to do this?”
 Operational: “Will this make us better?”, “Is the solution desirable within existing conditions”
 Organizational: “Does it fit with our organization?”
 Legal/Political: Stakeholder and regulatory analysis

Question 8

Systems Analysis- Requirements Definition

Answer 8

1. Purpose:
    Define the information requirements and functions, resources and interfaces
2. Outputs:
    Feasibility document (Planning document, Project gets a “Go/No Go!”)
    Entity Relationship Diagrams w/o attributes
    Management “signs off” on project

Question 9

Systems Design purpose

Answer 9

Explains how the system will meet the informational requirements determined in the Systems Analysis Phase

Question 10

“Blueprint” of how system is going to be built :

Answer 10

 Conceptual Model:
 Entity Relationship Diagrams w/ detail attributes  describes information structures
 Schematic Diagram (Data Flow Diagrams)
 describes information flows

 Logical Model:
 Hierarchical, Network, Relational, Object-oriented model

 Physical Model:
 Actual hardware, software, telecommunications diagram (diagrams that show layout of how things will connect

Question 11

Procurement of software solutions/ Potential Coding Modifications purpose

Answer 11

1. Evaluation and selection of software
2. System specifications prepared during the design phase are translated into software programming modifications if needed.

Question 12

Testing purpose

Answer 12

To determine whether the system produces the desired results under know conditions

Question 13

Alpha testing

Answer 13

User testing of a information system using simulated data – Normally done by the internal IS group

Question 14

Beta testing

Answer 14

User testing of a completed information system using real data

Question 15

Other different types of testing:

Answer 15

 Unit testing – tests each module of software using true information the organization will use
 Application (or system) testing – verifies that all units of code work together  Integration testing – exposes faults in the integration of software components or units
 Backup and recovery testing – tests the ability of an application to be restarted after failure
 Documentation testing – verifies instruction guides are helpful and accurate
 User acceptance testing (UAT) – tests if a system satisfies its acceptance criteria

Question 16

Conversion/Implementation purpose

Answer 16

Implementation of new system and change over from old to new system

Question 17

Conversion/Implementation approach

Answer 17

 Installation of software/hardware solution
 Make minor adjustments to system
 Documentation
 Train users
 System testing/Beginning to use new system

Question 18

Maintenance is:

Answer 18

Involves performing changes, corrections, additions, and upgrades to ensure the system continues to meet the business goals

Maintenance – fixing or enhancing an information system to meet the needs of organization and it’s customers

Question 19

Maintenance purpose

Answer 19

 System performance
] Respond to change
 Continuous improvement  Adding new modules of Enterprise Resource planning or Software as a Service contract.

Question 20

Maintenance issues

Answer 20

 Evaluation of proposed changes
 Training on upgraded items.
 Cost

Question 21

Different types of maintenance include:

Answer 21

1) Adaptive maintenance : making changes to system to accommodate organization change and/or customer needs
2) Corrective maintenance: Correcting processes/features that don’t work correctly.
3) Perfective maintenance: Simply enhancing the system, not necessary but make system better
4) Preventative maintenance: like a system tune-up – Software upgrades, hardware upgrades, etc.