Exam 1 Flashcards
(41 cards)
Phases of System Development
1) planning
2) analysis
3) design
4) implementation
Project initiation
Creating and assessing goals
Feasibility study
Guides the org in determining whether to proceed
1) technical feasibility: can we build it
2) economic feasibility: should we build it
3) organization feasibility: if we build it, will they come
System request
1) project sponsor
2) business need
3) business requirement
4) business value
5) special issues or constraints
Technical feasibility
The extent to which the system can be successful design, developed, and installed by IT group
- risk with familiarity application & tech
- project size
- compatibility
Economic feasibility
1) identifying costs & benefits
2) assigning values to costs & benefits
3) determine cash flow
4) assess projects economic value (ROI, BEven, NPV)
Costs & benefits can be broken down into 4 categories
1) development costs
2) operational costs
3) tangible benefits
4) intangible benefits
Organizational feasibility
How well the system will be ultimately accepted by its users and incorporated into the ongoing operations of the organization
Stakeholders: project champion, org management, system users
Project selection
Systems projects are evaluated in the context of an entire portfolio of projects (size, cost, purpose, length, risk, scope, and economic value)
Approval committee
Must be selective about where to allocate resources due to limited funds
Creating the project plan
- select the best project methodology
- develop a project work plan
- establish a staffing plan
- create ways to coordinate and control the project
Project Methodologies (6)
1) waterfall development
2) parallel development
3) v-model
4) rad (rapid application development)
5) iterative development
6) agile development
Waterfall Development
Project team proceeds sequentially from one phase to another
- adv: requirements are identified long before programming begins
- disadv: design must be completely specified before beginning
Parallel Development
-adv:Reduces the time required to deliver system
Less likely to produce a need for rework
Disadv: voluminous deliverables
Subprojects must be completed independently to not affect one another
V-Model
-adv: pays more attentions to testing
Simple/straight forward
Improves the overall quality w/ emphasis on early development of test plans
-disadv: rigidity of the waterfall process &is not always appropriate for dynamic nature of business
Iterative development
Breaks the overall project into a series of versions that are developed sequentially
- most important & fundamental requirements in first version
- but also gives ability for users to provide valuable feedback for future versions
Can either use system prototyping (continuity’s improvement) or throw away prototyping (different designs, not all created to be chosen)
Agile development
A group of programming-centric method of IES that focus on streak lining in SDLC
-extreme programming: emphasizes customer satisfaction and teamwork
Project estimation
Process of assigning projected values for time & effort
1) methodology time
2) actual previous projects experience
3) experienced developers
Begins as a range, and becomes for specific as project progresses
Top-down Methodology in Identifying Tasks
Identify highest level tasks, break down them into increasingly smaller units
Project work plan
- duration of task
- current task status
- task dependencies
- Kay milestone dates
Gantt chart
Useful for monitoring products status during project
Staffing the project
Staffing levels will change
Additional staff may add overhead costs
Standards
Documentation, coding, specification, interface deign
Time boxing
To resolve in congruency
- set deliverables date
- prioritize my volunteers
- Build system core
- postpone unfinished shit
- Deliver core functionalities
