Reading...
Play button
Play button
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;
17 Cards in this Set
- Front
- Back
|
Servicing customers
Collaborating with business partners Conducting electronic transactions within an organization |
e-business
|
|
|
The process of building a model that demonstrates the features of a proposed product, service, or system
|
prototpying
|
|
|
4 steps of prototyping
|
4 steps:
Identify basic requirements Develop initial prototype User review Revise and enhance the prototype |
|
|
advantages of prototyping
|
Encourages active user participation
Helps resolve discrepancies among users Gives users a feel for the final system Helps determine technical feasibility Helps sell the idea of a proposed system |
|
|
disadvantages of prototyping
|
Leads people to believe the final system will follow
Gives no indication of performance under operational conditions Leads the project team to forgo proper testing and documentation |
|
|
focuses on building small self-contained blocks of code (components) that can be reused across a variety of applications
|
component based development
|
|
|
Is a modular approach
Uses (reuses) already built components Builds new components as needed that can also be used in future projects Contrast with SDLC which focuses on an entire project |
component based development
|
|
|
three component based development methodoligies
|
Rapid application development (RAD)
Extreme programming (XP) Agile methodology |
|
|
Accelerated SDLC process that relies on prototypes
Extensively involves users throughout the process Continuous process of design, development, and testing of prototypes |
Rapid application development
|
|
|
Breaks a project down into small phases
Development can not move on to the next phase until the current one is complete |
exptreme programming (XP)
|
|
|
Similar to extreme programming
Goal is customer satisfaction through early and continuous delivery of software components |
agile methodology
|
|
|
The development and support of IT systems by end users with little or no help from IT specialists
Do-it-yourself systems development approach Can relieve IT specialists of the burden of developing many smaller systems |
self sourcing - end user development
|
|
|
Improves requirements determination
Increases end user participation and sense of ownership Increases speed of systems development Reduces invisible backlog of requested but not approved systems |
advantages of self sourcing/end usuer development
|
|
|
Inadequate end user expertise leads to inadequately developed systems
Lack of organizational focus creates “privatized” IT systems Insufficient analysis of design alternatives leads to subpar IT systems Lack of documentation and external support leads to short-lived systems |
disadvantages of self sourcing/end user development
|
|
|
to a third party for a contractually specified:
Length of time Cost Level of service/quality |
delegating systems development
|
|
|
why outsource?
|
Technology
Cost Internet/globalization Others? |
|
|
India, China, Eastern Europe (including Russia), Ireland, Israel, Philippines
|
primary outsourcing countries
|
