Brainscape's Knowledge GenomeTM

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


See full index

INFS 347 > Exam 1 > Flashcards

Exam 1 Flashcards

1
Q

Phases of System Development

A

1) planning
2) analysis
3) design
4) implementation

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

Project initiation

A

Creating and assessing goals

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

Feasibility study

A

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

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

System request

A

1) project sponsor
2) business need
3) business requirement
4) business value
5) special issues or constraints

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

Technical feasibility

A

The extent to which the system can be successful design, developed, and installed by IT group

  • risk with familiarity application & tech
  • project size
  • compatibility
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Economic feasibility

A

1) identifying costs & benefits
2) assigning values to costs & benefits
3) determine cash flow
4) assess projects economic value (ROI, BEven, NPV)

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

Costs & benefits can be broken down into 4 categories

A

1) development costs
2) operational costs
3) tangible benefits
4) intangible benefits

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

Organizational feasibility

A

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

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

Project selection

A

Systems projects are evaluated in the context of an entire portfolio of projects (size, cost, purpose, length, risk, scope, and economic value)

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

Approval committee

A

Must be selective about where to allocate resources due to limited funds

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

Creating the project plan

A
  • select the best project methodology
  • develop a project work plan
  • establish a staffing plan
  • create ways to coordinate and control the project
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Project Methodologies (6)

A

1) waterfall development
2) parallel development
3) v-model
4) rad (rapid application development)
5) iterative development
6) agile development

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

Waterfall Development

A

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
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Parallel Development

A

-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

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

V-Model

A

-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

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

Iterative development

A

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)

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

Agile development

A

A group of programming-centric method of IES that focus on streak lining in SDLC
-extreme programming: emphasizes customer satisfaction and teamwork

18
Q

Project estimation

A

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

19
Q

Top-down Methodology in Identifying Tasks

A

Identify highest level tasks, break down them into increasingly smaller units

20
Q

Project work plan

A
  • duration of task
  • current task status
  • task dependencies
  • Kay milestone dates
21
Q

Gantt chart

A

Useful for monitoring products status during project

22
Q

Staffing the project

A

Staffing levels will change

Additional staff may add overhead costs

23
Q

Standards

A

Documentation, coding, specification, interface deign

24
Q

Time boxing

A

To resolve in congruency

  • set deliverables date
  • prioritize my volunteers
  • Build system core
  • postpone unfinished shit
  • Deliver core functionalities
25
Q

Classic mistakes

A

1) over optimism time schedule
2) failing your monitor time schedule
3) famailing to update
4) adding more staff to the project

26
Q

Analysis

A

Breaking a whole into its parts with the intent of understanding the parts nature, functions, and interrelationships
-deliverables

27
Q

Basic process of analysis

A

1) understand the existing situation
2) identify improvements
3) define requirements for the system

28
Q

Requirement

A 
A statement of what the system must do or what characteristics it needs to have
Describe:
-what the business needs
-what the users need to do
-what the software should do
-characteristics the system should have 
-how the system should be built
29
Q

Functional requirement

A
  • process oriented: process system must perform or do

- information oriented: information system must contain

30
Q

No functional requirement

A

Behavioral properties must have

  • operational: the physical and technical environments in which they system will operate
  • performance: the speed, capacity, and reliability of the system
  • security: who has authorized access to the system under what circumstances
  • cultural & political: factors & legal requirement that affect the system
31
Q

Process of determining requirements

A

1) both business and IT perspectives are needed
2) the most effective approach is to have both business people and analysts working together to determine requirements
3) the analyst must also consider how best to pull/gather the requirements from the stakeholders
4) continuous as if evolves over time

32
Q

Interviews

A

Most common technique for gathering info

Inefficiencies lie within Variability and time

33
Q

Joint application development (JAD)

A

Group interview, a structured group process focused on determining requirements
-involves everyone working together
-May reduce scope creep by 50%
Huge time commitment, and taking important people away from their jobs
-must have a formal agenda and ground rules

34
Q

Questionnaire

A

A set of written questions for obtaining informations from individuals

  • must follow up to explain to the participates what you got out of it
  • designing good questions is imperative
  • quick and simple to give out
35
Q

Document analysis

A

Study of existing material describing the current system

  • formal: describes in forms, policy manuals, and organizational charts
  • informal: user additions, unused elements in form and reports
36
Q

Observation

A

The act of watching processes being performed

  • power tool to gain insight into the AS-IS system
  • checks the validity of information gathered elsewhere
  • must be aware how people act when being watched
37
Q

Requirements analysis strategies

A

Problem analysis: asking users to ID problems (small incremental changes, improves efficiency or ease of use)

Root cause: focus on problems first rather than solutions (challenge assumptions, discover real issue)

Duration: detailed examination, compare to basic steps

Outcome: focuses on the understanding of fundamental outcomes that provide value to customer

Technology: many major changes in business is recent times have been enabled by new tech

38
Q

Activity based costing

A

Examine the cost of each major process or step

39
Q

Informal benchmarking

A

Common for customer facing processes as the analyst visits other orgs as a customer

40
Q

Activity elimination

A

The analyst and managers work together to ID how the org could eliminate activities

41
Q

Use cases

A

A text based method of describing and documenting complex processes

  • provides tools for capturing functional requirements
  • helps to manage complexity
  • provides means of communications with users

INFS 347 (2 decks)

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