Upgrade to remove ads
Only $35.99/year

MIS Exam #2 Chapter 6

Terms in this set (51)

systems development life cycle (SDLC)
a structured step-by-step approach for developing information systems; a.k.a waterfall methodology
waterfall methodology
an approach in which each phase of SDLC is followed by another, from planning through implementation
SDLC phases
planning, analysis, design, development, testing, implementation, maintenance
planning
create a solid plan for developing your information system
planning activities
define the system to be developed; set the project scope; develop the project plan including tasks, resources, and timeframes
defining the system to be developed
make choices based on your organization's priorities, which may be expressed as critical success factors
critical success factor (CSF)
a factor simply critical to your organization's 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 initial requirements
project scope document
a written definition of the project scope; usually no longer than a paragraph
project plan
defines the what, when, and who questions or 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 are completed on time
project milestones
represent key dates for which you need a certain group of activities performed
analysis
involves end users and IT specialists working together to gather, understand, and document the business requirements for the proposed system
two primary analysis activities
gather the business requirements; prioritize the requirements
business requirements
the detailed set of knowledge worker requests that the system must meet in order to be successful
joint application development (JAD)
knowledge workers and IT specialists meet 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
cost to fix errors
higher in later stages; cheaper in earlier stages of SDLC
design
build a technical blueprint of how the proposed system will work
primary design activities
design the technical architecture; design system models
technical architecture
defines the hardware, software, and telecommunications equipment required to run the system
system models
includes GUI screens that users will interface with, database designs, report formats, software steps, etc.
development phase
take all of your detailed design documents from the design phase and transform them into an actual system
two primary development activities
build the technical architecture; build the database and programs
testing phase
verifies that the system works and meets all of the business requirements defined in the analysis phase
two primary testing activities
write the test conditions; perform the testing of the system
test conditions
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
implementation phase
distribute the system to all of the knowledge workers and they begin using the system to perform their everyday jobs
two primary implementation activities
write the detailed user documentation; provide training for the system users
user documentation
highlights how to use the system
online training
runs over the Internet or off a CD-ROM
workshop training
held in a classroom environment and lead by an instructor
parallel implementation
use both the old and new system simultaneously
plunge implementation
discard the old system completely and use the new
pilot implementation
start with small groups of people on the new system and gradually add more users
phased implementation
implement the new system in phases
maintenance
monitor and support the new system to ensure it continues to meet the business goals
two primary maintenance activities
build a help desk to support the system users; provide an environment to support system changes
help desk
a group of people who responds to knowledge workers' questions
component-based development
focuses on building small self-contained blocks of code that can be reused across a variety of applications
component-based methodologies
rapid application development (RAD); extreme programming (XP); agile methodology
rapid application development (RAD)
emphasizes extensive user involvement in the rapid and evolutionary construction of working prototypes of a system to accelerate systems development
extreme programming (XP)
breaks a project into tiny phases and developers cannot continue on to the next phase until the first phase is complete
agile methodology
a form of XP, aims for customer satisfaction through early and continuous delivery of useful software components
service-oriented architecture (SoA)
perspective that focuses on the development, use, and reuse of self-contained blocks of code (called services) to meet all application software needs
Recommended textbook explanations

Complex Analysis: A First Course with Applications

3rd EditionDennis G. Zill, Patrick D. Shanahan
1,433 explanations

Elementary Number Theory

7th EditionDavid Burton
776 explanations

A Transition to Advanced Mathematics

7th EditionDouglas Smith, Maurice Eggen, Richard St. Andre
620 explanations

Introductory Combinatorics (Classic Version)

5th EditionRichard A. Brualdi
685 explanations