COMM 205 Unit 7 Flashcards

(22 cards)

1
Q

Definition: System Development Life Cycle (SDLC)

A

The overall PROCESS for developing information systems from PLANNING and analysis through implementation and maintenance.

  1. Planning
  2. Analysis
  3. Design
  4. Development
  5. Testing
  6. Implementation
  7. Maintenance
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

SDLC 1) Planning and feasibility study

A

1) Planning and feasibility study
Establish a high-level plan of the intended project and determine project GOALS
1. DEFINE the system to be developed.
2. Set the project SCOPE.
3. Develop the project PLAN including tasks,
resources, and timeframe.
Conduct feasibility study / develop business case
1. Determine if a project is technically, economically,
operationally and legally feasible.
Ask: What will the system accomplish?

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Aspects of feasibility study

A
  1. Technical feasibility
  2. Operational feasibility
  3. Legal feasibility
  4. Economical feasibility
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

SDLC 2.

A

2) System Analysis
The end users and IT specialists WORK TOGETHER to UNDERSTAND and DOCUMENT the business requirements for the system.
 DEFINE the system to be developed in more detail.
 How does the EXISTING SYSTEM work?
 WHAT FEATURES should the new system include?
 The major deliverable of this phase is the SYSTEM REQUIREMENT DOCUMENT
Ask: What Functions will the System Perform?

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

SDLC 3.

A

3) System Design
Translate the business requirements into detailed functions of the system -> SYSTEM SPECIFICATION
Determine hardware, software and telecommunications equipment required to run the system -> TECHNICAL ARCHITECTURE
Decide to use off-the-shelf software or develop a new system -> MAKE OR BUY DECISION
Ask: How will the decision work?

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

SDLC 4.

A

4) Development
DEVELOP the system in-house
 Translate the design specifications into computer code.
ACQUIRE the system (not just the software)
 Prepare the RFP (REQUEST FOR PROPOSAL)
 Evaluate vendors and proposals
 Customize the system to satisfy the user requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

SDLC 5.

A

5) Testing

Verify that the system works and meets all of the business requirements defined in the analysis and design phases.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

SDLC 6.

A
6) Implementation
Convert from the old system to the new system.
    1. Direct cutover
    2. Pilot conversion
    3. Phased conversion
    4. Parallel conversion
End-User Training
Data Conversion 
User Documentation 
Change Management
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Definition: Direct cutover

A

The old system is cut off and the new system is turned on.

Least expensive, most risky

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Definition: Pilot conversion

A

Introduce the system in one functional area or location before introducing it to other parts of an organization.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Definition: Phased conversion

A

Introduce components of the new system, e.g. functional modules, in stages.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Definition: Parallel conversion

A

The old and new systems operate simultaneously for a period of time

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

SDLC 7.

A

7) Maintenance
Fix system errors
Update the system to accommodate changes in business requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Definition: Waterfall methodology

A

A sequential, activity- based process in which each phase in the SDLC is performed SEQUENTIALLY from planning through implementation and maintenance.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

What is a Successful Project?

A

On time
Within budget
Meets the business’s requirements
Fulfills the customer’s needs

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Why do Projects Fail?

A
  1. Incomplete Requirements - 13.1%
  2. Lack of User Involvement - 12.4%
  3. Lack of Resources - 10.6%
  4. Unrealistic Expectations - 9.9%
  5. Lack of Executive Support - 9.3%
  6. Changing Requirements & Specifications
  7. Lack of Planning
  8. Didn’t Need It Any Longer
  9. Lack of IT Management 10. Technology Illiteracy
17
Q

Definition: Scope creep

A

Scope creep – UNCONTROLLED CHANGES or continuous growth in a project’s scope.
 Scope creep can be a result of poor change control, unclear project objectives, weak project manager or executive sponsor, and poor communication between parties.
 Scope creep is a risk in most projects. It often results in COST OVERRUN.

18
Q

Definition: Project management

A

Project management is used to ensure that projects fulfill their requirements.
It is the application of KNOWLEDGE, SKILLS, TOOLS, AND TECHNIQUES to project activities to meet project requirements.
It involves identifying and creating project DELIVERABLES as well as setting project MILESTONES to verify the progress of the project.

19
Q

Project management terms

A

 Project deliverables - Any measurable, tangible, verifiable outcome, result, or item that is produced to complete a project or part of a project.
 Project milestones - Represents key dates when a certain group of activities must be performed.
 Gantt chart - A graph showing the tasks on the work breakdown structure along with each task’s projected start and finish dates.

20
Q

Initiating projects

A

Lay the groundwork for the project by:
 clarifying the VALUE it will bring to the organization;
 setting its OBJECTIVES;
 ESTIMATING the project’s LENGTH, SCOPE, AND COST
 identifying major players (incl. the sponsor, the project manager, the team members, and other stakeholders)
 obtaining APPROVAL

21
Q

Definition: Project plan

A

A formal, approved document (or roadmap) that will be used to manage and control project execution.
A well-defined project plan should have:
 Description of Project Scope  A list of Activities
 A Schedule
 Time and Cost estimates
 Risk factors
 Assignments & Responsibilities  Kill Switch

22
Q

Conclusion

A

The traditional systems development approach is the waterfall methodology. Due to its inflexibility and time intensiveness, other methodologies have been developed that are more agile (i.e. MORE FLEXIBLE, LESS TIME INTENSIVE)
Project management is the application of KNOWLEDGE, SKILLS, TOOLS, AND TECHNIQUES to manage project activities to meet project requirements.