• Shuffle
    Toggle On
    Toggle Off
  • Alphabetize
    Toggle On
    Toggle Off
  • Front First
    Toggle On
    Toggle Off
  • Both Sides
    Toggle On
    Toggle Off
  • Read
    Toggle On
    Toggle Off
Reading...
Front

Card Range To Study

through

image

Play button

image

Play button

image

Progress

1/39

Click to flip

Use LEFT and RIGHT arrow keys to navigate between flashcards;

Use UP and DOWN arrow keys to flip the card;

H to show hint;

A reads text to speech;

39 Cards in this Set

  • Front
  • Back
SoA Service Oriented Architecture
treats every component of an IT system a database file a server a CRM software solution.
Insourcing
IT specialist inside your organization
Self sourcing
do it yourself approach many end users take with little or no help from IT specialists.
Outsourcing
A third party organization
Systems development life cycle SDLC
A structured step by step approach for developing information systems.
Waterfall methodology
Each phase of the SDLC is followed by another from planning, through implementation
PHASE 1 Planning
Create a solid plan for developing your information system

Critical success Factor (CSF)

A factor simply critical to your organizations success

Project scope

Clearly defines the high level system requirements

Scope creep

Occurs when the scope of the project increases

Feature creep

Occurs when developers add extra features that were not part of the original/initial requirements.

Project scope document

A written definition of the project scope and is usually no longer than a paragraph

Project Plan

defines the what when and who questions of system development

Project manager

An individual who is an expert in project planning and management defines and develops the project plan and tracks the plan to ensure all key project milestones and completed on time.

Project milestones

Represents key dates for which you need a certain group of activities performed.
PHASE 2 Analysis
Involves end users and IT specialists working together to gather understand and document the business requirements for the proposed system

Business requirements

the detailed set of knowledge worker requests that the system must meet in order to be successful. Address the why and what of your development activities.

Joint application development (JAD)

Knowledge workers and IT specialists meet, sometimes for several days to define or review the business requirements for the system.

Requirements definition document

prioritizes the business requirements and places them in a formal comprehensive document.
PHASE 3 DESIGN
Build a technical blue print of how the proposed system will work
Technical architecture
defines the hardware software and telecommunications equipment required to run the system
Design system Models
Includes GUI screens that users will interface with database designs, report formats software steps etcetera
PHASE 4 Development
take all of your detailed design documents from the design phase and transform them into an actual system.
Build the technical architecture

Build the database and programs

Mostly performed by IT specialists
PHASE 2 Testing
verifies that the system works and meets all of the business requirements defined in the analysis phase.
Write the test conditions
the detailed steps the system must perform along with the expected results of each step.

Unit testing

tests individual units of code.

System testing

verifies that the units of code function correctly when integrated

Integration testing

verifies that separate systems work together

User acceptance testing (UAT)

determines if the system satisfies the business requirements.
PHASE 6 Implementation
distribute the system to all of the knowledge workers and they begin using the system to perform their everyday jobs
Write detailed User documentation
highlights how to use the system.
Provide online training for the system users
Online training runs over the internet or off a CD ROM
Workshop training
Is held in a classroom environment and lead by an instructor
Parallel implementation method
Use both the old and new system simultaneously
Plunge implementation method
discard the old system completely and use the new
Pilot implementation method
Start with small groups of people on the new system and gradually add more users.
PHASE 7 Maintenance
Monitor and support the new system to ensure it continues to meet the business goals
Help desk to support the system users
A group of people who responds to knowledge workers questions.