Unit 6- systems development and Decision making Flashcards
reasons to make system changes
- hardware and software upgrade
- job moves/changes (location, skills, etc)
- management changes (new ideas)
- Process flow (make more efficient)
- strategic
SDLC- SYSTEMS DEVELOPMENT LIFE CICLE
- Planning,
- Analyzing
- Designing
- Developing
- Testing
- Implementing
- Maintaining
1.Analysis phase
- identify problems, opportunities, objective.
- Determining information requirements
- analyzing systems needs
2.Design phase
- designing the recommended system
5. Developing and documenting software
3.Implementation phase
- testing and maintaining system
7. implementing and evaluating system
when to use Waterfall methodology (SDLC)
- stages completed in order, cannot go back
- most appropriate systems requirements are clear, well documented, and unlikely to change
- technology is understood and not dynamic
- sufficient resources and expertise are available to support the process
Build and Fix (SDLC)
- modify until successful
- continuous maintenance
- quick changes
Agile Development
- iterative development model
- rapid application adaptive planning
- fast delivery
- continuous improvement
- flexibility in responses to change
- collaborative, cross functional teams
Prototyping model steps
- Experimental system, is quickly inexpensively built.
1. identify users basic requirements
2. developing the initial prototype
3. using prototype
4. revising and enhancing the prototype
End user development
- informal method of solutions development by end users.
- Made possible by 4th generation languages
- Enable the end users to develop systems and solutions with little or no assistance from technical specialists
What is a system analyst?
- specializes in the analysis, design, and implementation of information systems
- serves and interacts with the users to understand their needs and requirements.
- seldom are involved in development of hardware or software
cloud computing
- you have all your data in more then one location
- public
- private
- hybrid
implementation methods
- direct
- parallel-(running 2 systems at the same time)
- prototyping
- phased
Feasibility Analysis
- whether the solution is financially, technologically, or organizationally feasible.
- whether the proposed system is a good investment
- whether organization can adapt to changes
Economic feasibility
total cost of ownership takes into account the total costs over time, including hardware, software, labor, licensing , etc.
Thechnical
to determine the technical feasibility of a system, technology and providers need to be compared and limitations identified.
operational
provides insight into whether or not the proposed system is compatible with the existing operations of the organization
schedule
determines whether the project will be viable once completed.
legal
determines the legal aspects and repercussions of the project
political
considers how potential stakeholders will respond to the changes from the proposed system. some may not support it
