ITEC 1010 Chapter 8 part: 1

0.0(0)
Studied by 3 people
call kaiCall Kai
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/29

30 Terms

1
New cards
Buy Versus Build
Buying off-the-shelf software is less risky and leads to quicker deployment

\n - Maintenance and support costs may become expensive
2
New cards
Pros of Buy
A software solution can be acquired and deployed relatively quickly. An organization can "test drive" software before acquiring it.
3
New cards
Cons of Buy
Unmodified, the software may not be a good match to an organization's needs. Maintenance and support costs can become excessive.
4
New cards
Pros of Build
Customized software is more likely to be a good match to an organization's needs. A custom application provides the potential to achieve competitive advantage.
5
New cards
Cons of Build
The cost to build a system can be quite high compared to the cost of purchasing off-the-shelf software. Customized software can take months or even years to deploy.
6
New cards
Waterfall system development process
A sequential, multistage system development process in which work on the next stage cannot begin until the results of the current stage are reviewed and approved or modified as necessary
7
New cards
6 phases of waterfall system development process

1. Investigation
2. Analysis
3. Design
4. Construction
5. Integration
6. Testing and implementation
8
New cards
Advantages of Waterfall System Development Process
* Formal review at the end of each phase allows maximum management control.
* This approach requires creation of considerable system documentation so that system requirements can be traced back to stated business needs.
* Approach produces many intermediate products that can be reviewed to measure progress toward developing the system
9
New cards
Disadvantages of Waterfall System Development Process
→ Users get a system that meets the needs as understood by the developers; however, this might not be what the users really needed.

→Often, user needs go unstated or are miscommunicated or misunderstood.

→ Users can't easily review intermediate products and evaluate whether a particular product (e.g., a data-flow diagram) will lead to a system that meets their business requirements
10
New cards
System Investigation
The initial phase in the development of a new or modified business information system whose purpose is to gain a clear understanding of the specifics of the problem to solve or the opportunity to address.
11
New cards
Steps of the investigation phase

1. Review systems investigation request
2. Identify and recruit team leader and team members
3. Develop budget and schedule for investigation
4. Perform investigation
5. Perform preliminary feasibility analysis
6. Prepare draft of investigation report
7. Review results of investigation with steering team
12
New cards
1\. Review systems investigation request
* A preliminary statement of the problem or opportunity to be addressed
* A brief discussion of how this effort aligns with previously defined company and organization objectives, goals, and strategies
* Identification of the general areas of the business and business processes to be included in the scope of the study
13
New cards
2\. Identify and recruit team leader and team members
* A leader is identified and recruited after managers grant approval to initiate systems investigation
* Investigation team members chosen next
14
New cards
Investigation team's responsibilities
* Gather and analyze data
* Prepare an investigation phase report
* Present results to the project steering team
15
New cards
3\. Develop budget and schedule for investigation
* The team develops a list of specific objectives and activities to accomplish along with a schedule for completing the work
* The team establishes major milestones to help monitor progress
* A budget is prepared including travel expenses and funds for consultants
16
New cards
4\. Perform investigation
* Refine the initial problem definition and scope described in the systems investigation request
* Identify the high-level business requirements the system must meet
* Identify any issues or risks associated with the project
17
New cards
Joint Application Development (JAD)
A structured meeting process that can accelerate and improve the efficiency and effectiveness of the investigation, analysis, and design phases of a systems development project.
18
New cards
Functional Decomposition
A technique used during the investigation, analysis, and design phases to define the business processes included within the scope of the system.
19
New cards
JAD participants
* Facilitator
* Decision Makers
* Users
* System developers
* Scribe
20
New cards
Facilitator
* Determines JAD session objectives
* Encourages everyone to participate
21
New cards
Decision Makers
* Resolve conflict
* Avoid gridlock
22
New cards
Users
* Describe business as it is and as it should be
* Define problems
* Identify potential benefits, analyze existing system
* Define requirements of new systems
23
New cards
System developers
* Observe
* Offer technical opinion on cost
* Gain deep understanding of customers' needs and desires
24
New cards
Scribe
* Participate in discussion to clarify points
* Publish results of JAD session and solicit feedback
25
New cards
5\. Perform preliminary feasibility analysis
* Technical feasibility
* Economic feasibility
* Legal feasibility
* Operational feasibility
* Schedule feasibility
26
New cards
Technical feasibility
Examines whether a project is feasible within the current limits of available technology
27
New cards
Economic feasibility
Determines whether the expected benefits associated with the project outweigh the expected cost sufficiently to make the project financially attractive
28
New cards
Legal feasibility
The process of determining whether laws or regulations may prevent or limit a system development project
29
New cards
Operational feasibility
The process of determining how a system will be accepted by people and how well it will meet various system performance expectations
30
New cards
Schedule feasibility
The process of determining whether a project can be completed within a desired time frame