Term
| what is IT's role in a business? |
|
Definition
| IT's role is to support all organizations in a business |
|
|
Term
| why did gap in a box fail? |
|
Definition
| gap in a box was a project designed to implement oracle software without any customization. gap suffered from organizational inertia, and the project failed because they wanted the system to cater to them, but only unique process should get custom systems. gap doesnt have a unique system |
|
|
Term
|
Definition
| when a company is very set in their ways and is unwilling to change it's processes or do things in a new way |
|
|
Term
| what is systems development? |
|
Definition
systems development involves
1. analyzing
2. designing
3. building
4. testing
5. deploying
6. supporting
a new system |
|
|
Term
| what does systems development encompass? |
|
Definition
systems development encompasses
1. hardware
2. software
3. data
4. processes
5. people |
|
|
Term
| what areas are programmers concerned with? |
|
Definition
| programmers are concerned with software and a little bit of data |
|
|
Term
| software requires more than ________ expertise, it requires______ knowledge and ________ skill. |
|
Definition
| software development requires more than technical expertise, it requires business knowledge and managment skill |
|
|
Term
| why is IS development difficult? |
|
Definition
IS development is difficult because
1. it's hard to determine what they want/requirements of the project
2. requirements change as project develops
3. schedule and budget difficult to estimate, and the change as the scope changes
4. communication with large teams isn't easy
5. technology changes, how do you adapt? start over all the time?
6. diseconomies of scale- as development teams grow, average contribution per worker decreases and the project becomes more difficult to managemnt
7. unexpected events- i.e. hurricanes |
|
|
Term
|
Definition
| as development teams grow, the average contribution per worker decreases making the project harder to manage |
|
|
Term
|
Definition
| adding more people to the project marks the project latter, aka too many cooks in the kitchen |
|
|
Term
| project triple constraint |
|
Definition
every project can be broken into three aspects:
1. scope
2. resources
3. schedule
increasing or decreasing one will affect the other two as well |
|
|
Term
|
Definition
| the perameters of your project, what are you trying to accomplish? your goals |
|
|
Term
|
Definition
| people, equipment, money you need to complete your project |
|
|
Term
|
Definition
| your timeline for completion of your project. how much time you have to complete your goals |
|
|
Term
| what is the standard way to run a project? |
|
Definition
| yes, it's called framework or methodology |
|
|
Term
| where do you start in project planning? where do you go from there? |
|
Definition
ask the broad questions:
what is the goal
by when
with what
then break it out into stages and detail each stage into managable pieces |
|
|
Term
| what's the first phase of project planning? |
|
Definition
1. inception:
define system goals
determine scope
asses the feasibilty of project |
|
|
Term
| what is a vital part of the inception/analysis step in terms of legalities? |
|
Definition
| it's important that once you agree to a scope you document it to that you can avoid scope creep unless formally approved |
|
|
Term
| whats involved in the proof of concept/feasibility assesment of a project? |
|
Definition
| the cost, schedule, technology, orginizational feasibility |
|
|
Term
| whats the second phase in planning? |
|
Definition
analysis phase:
determine and document features and functions |
|
|
Term
| what is the importance of the analysis phase? |
|
Definition
| it is cheapest to make the decision to modify rather than replace your current system in this phase |
|
|
Term
| what's the third phase of planning? |
|
Definition
design phase:
develop and evaluate alternatives
hardware design determined by project team
software design dependent on source
database is designed
procedures designed for buisness intelligence system
job descriptions are created for users and operations personnel |
|
|
Term
|
Definition
construction phase
system must be built
system must be tested
users and data must be converted from old to new system |
|
|
Term
|
Definition
| you run test processes to fix problems |
|
|
Term
|
Definition
| test the system to confirm it all works and catch bugs before they get to users |
|
|
Term
| what are some methods of testing systems? |
|
Definition
1. test scripts with positive or negative testing
2. beta testing |
|
|
Term
|
Definition
| beta testing involves future system users trying out the system on their own, virtualization allows this to happen now. i.e testing windows 7 |
|
|
Term
|
Definition
|
|
Term
|
Definition
| covert business activity from old to new system |
|
|
Term
| what are some methods to implement? |
|
Definition
pilot (dad moves in alone)
phased (whole family moves in, but only to the living room and kitchen)
in-parallel (live in both houses at once- secure but expensive)
big bang (move into new, demo old) |
|
|
Term
|
Definition
| organization implements intire system on limited users, that way if it doesn't affect everyone so exposure risk is reduced |
|
|
Term
|
Definition
| new system is installed in phases and tested after each phase. this continues until installed at entire organization |
|
|
Term
| in-parallel implementation |
|
Definition
| test new system while running in parallel with the old system on. this is expensive and time consuming because you have to support both systems and enter data twice for each one, but it does provide security if one fails |
|
|
Term
|
Definition
| direct installation of new system and discontinue old, but there is no back up if it fails |
|
|
Term
|
Definition
fixing or adapting system requires
a method to track system failures and enhancements
work on corrections based on priorities
enhancements are prioritized on buisness decisions |
|
|
Term
| when are you implementing project management? |
|
Definition
| you are implementing project managment from start to close of the project. |
|
|
Term
| how do you manage the project? |
|
Definition
you manage the project by managing:
resources, schedule and progresss, risk and issues, handling communication, planning hand-offs between phases, AND MORE |
|
|
Term
|
Definition
a structured approach that is familiar to most developers world wide. works well when you're building something like a house:
requirements-->design-->development-->testing-->deployment
but some of these steps will overlap |
|
|
Term
| Iterative (aka Agile) progression |
|
Definition
inception-->analysis-->design-->preliminary construction-->user review
cycle repeats until the you get good reviews. then you go to
final construction-->production-->maintenance |
|
|
Term
| what progression type is easier |
|
Definition
| iterative progress is easier to achieve than waterfall process |
|
|
Term
| _____ is key risk to all projects |
|
Definition
| communication is key risk to all projects |
|
|
Term
| what is scope creep and how can it affect a projcet? |
|
Definition
| scope creep is the slow accumulation of changes, often costly, to a project such as extension of the deadline without an increase in reousrces. this can kill a project |
|
|
