Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

App Dev > The System Development Cycle > Flashcards

The System Development Cycle Flashcards

1
Q

-hardware, software, data, people, and procedures that work together to produce quality information.

A

Information system (IS)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

set of components that interact to achieve common goal.

A

system

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

(phases of the system development cycle)
-review project requests
-prioritize project requests
-allocate resources
-identify project development team.

A

phase 1: planning

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

(phases of the system development cycle)
-conduct preliminary investigation.
-perform detailed analysis activites:
–study current design
–determine user requirements
–recommend solution

A

phase 2: analysis

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

(phases of the system development cycle)
-acquire hardware and software is necessary.
-develop details of system

A

phase 3: design

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

-develop programs if necessary
-install and test new system
-train users
-convert to new system

A

phase 4: implementation

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

-conduct post-implementation system review.
-identify errors and enhancements
-monitor system performance.

A

phase 5: support

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

-arrange tasks into phases.
-involve users (anyone for whom system is being built)
-develop clearly defined standrds (proedures comapny expects employees to follow)

A

guidelines for system development

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

-responsible for designing and developing information system.
-liaison between users and IT professionals

A

systems analyst

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

-formed to work on project from beginning to end.
-consists of users, systems analyst, and other IT professionals

A

project team

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

-one member of the team who manages and controls project budget and schedule.

A

project leader

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

-measure of how suitable system development will be ot the comapny.

A

feasibility

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

-operational feasibility
-schedule feasibility
-technical feasibility
-economic feasibility (a.k.a cost/benefit feasibility)

A

four feasibility tests

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

-collection and summarization of data and information.
-includes reports, diagrams, programs, and other deliverables

A

documentation

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q
  1. review documentation
  2. observe
  3. questionnaire
  4. interview
  5. joint-application design (JAD) session
  6. research
A

data and information gathering techniques

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

-to correct problem in existing system
-to improve existing system
-competition can lead to change
-outside group may mandate change

A

reasons to create or modify an information system

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

-formal request for new or modified information system.
-also called project request

A

request for system services

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

-begins when steering committee receives project request.

A

planning phase

19
Q

-decision-making body for the company.
-review and approve project requests
-prioritize project requests
-allocate resources
-form project development team for each approved project.

A

steering committee

20
Q

-conduct preliminary investigation, also called feasibility study
-perform detailed analysis

A

analysis phase

21
Q

-determine exact nature of problem or improvement and whether it is worth pursuing.
–findings are presented in feasibility report a.k.a feasibility study

A

preliminary investigation

22
Q
  1. study how current system works
  2. determine user’s wants, needs, and requirements
  3. recommend solution
A

detailed analysis

23
Q

-access feasibility of each alternative solution
- recommends the most feasible solution for the project.
-presented to steering committee, which decides how system will be developed.

A

system proposal

24
Q

(possible solutions)
-prewritten software available for purchase

A

buy packaged software

25
Q

(possible solutions)
-meets needs of many companies

A

horizontal market software

26
Q

(possible solutions)
-designed for particular industry

A

vertical market software

27
Q

(possible solutions)
-software developed at user’s requests

A

write own custom software

28
Q

(possible solutions)
-have outisde source develop software

A

outsource

29
Q

-acquire hardware and software
-develop all details of new or modified information system

A

design phase

30
Q

-talk with other systems analysis
-visit vendor’s stores
-surf web
-read print and online trade journals, newspapers, and magazines

A

identify all hardware and software requirements of new or modified system

31
Q

(Basic documents used to summarize technical specifications)
-identifies product(s) you want.
-vendor quotes price(s) for listed product(s).

A

request for quotation (RFQ)

32
Q

(Basic documents used to summarize technical specifications)
-vendor selects product(s) that meet(s) your requirements and then quotes price(s)

A

request for proposal (RFP)

33
Q

(Basic documents used to summarize technical specifications)
-less formal method that uses standard form to request information about product or service

A

request for information (RFI)

34
Q

-references from vendor
-talk to current users of products
-product demonstrations
-trial version of software
-benchmark test measures performance

A

how systems analysts test software products

35
Q

-specifications for components in proposed solution
-includes several activites
–database design
–input and output design
–program design

A

detailed design

36
Q

-sample of inout or output that contains actual data

A

mockup

37
Q

-working model of proposed system
-beginning a prototype too early may lead to problems

A

prototype

38
Q

-software tools designed to support activities of system development cycle

A

computer-aided software engineering (CASE)

39
Q

-purpose is to construct or build, new or modified system and then deliver it to users.

A

implementation phase

40
Q

(types of tests performed by system developers)
-verifies each individual program works by itself

A

unit test

41
Q

(types of tests performed by system developers)
-verifies all programs in applicatin work together

A

systems test

42
Q

(types of tests performed by system developers)
-verifies application works with other applications

A

integration test

43
Q

-showing user excatly how they will use new hardware and software in system.

A

training

44
Q

-provide on going assistance after system is implemented

A

support phase

App Dev (1 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions