Chapter 1 Flashcards

1
Q

Roles of the Systems Analyst

- name 3 primary roles

A
The analyst must be able to work with people of all descriptions and be experienced in working with computers
Three primary roles:
1) consultant
2) supporting expert
3) agent of change
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Qualities of the Systems Analyst

A
  • Problem solver
  • Communicator
  • Strong personal and professional ethics
  • Self-disciplined and self-motivated
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What is the Systems Development Life Cycle (SDLC)?

A

The systems development life cycle is a phased approach to solving business problems
Developed through the use of a specific cycle of analyst and user activities
Each phase has unique user activities

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

Name the 7 phases of SDLC

A
  1. Identifying problems, opportunities, and objectives
  2. Determining human information requirements
  3. Analysing system needs
  4. Designing the recommended system
  5. Developing and documenting software
  6. Testing and maintaining the system
  7. Implementing and evaluating the system
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Information

A
  • fuels business
  • key resources that determines success or failure of business
  • must be managed correctly
  • must be obtained, entered, stored, secured, processed, retrieved, and made available
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Need for systems analysis and design

A
  • Installing a system without proper planning can result in user dissatisfaction and disuse
  • Lends structure to the analysis and design of information systems
  • User involvement is a critical part of successful development of computer
    systems
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Roles of systems analyst

A
  1. be able to work with people of all descriptions

2. be experienced with computers

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

Three primary roles of systems analyst

A
  1. consultant
  2. supporting expert
  3. agent of change
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Consultant

A

ability and knowledge to guide management and other stakeholders to the correct solution

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

Qualities of systems analyst

A
  • problem solver
  • communicator
  • strong personal and professional ethics
  • self disciplined and self motivated
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Systems development life cycle

A

Phased approach to solving business problems

Developed through cycle of analyst and user activities

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

7 phases of Systems Development Life Cycle

A
  1. Identifying problems, opportunities and objectives
  2. Determining human information requirements
  3. Analysing system needs
  4. Designing recommended system
  5. Developing and documenting software
  6. Testing and maintaining system
  7. Implementing and evaluating system
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Reasons maintenance is performed

A
  • remove software errors

- enhance existing software

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

why is software enhanced?

A
  • includes additional features
  • address business changes over time
  • address hardware and software changes
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

What are CASE tools?

A

Computer aided software engineering
Productivity tools for systems analysts that have been created explicitly to
improve their routine work through the use of automated support

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

Why use CASE tools?

A
  • improve analyst-user communication
  • help support modelling functional requirements
  • assist in drawing project boundaries
17
Q

what is the agile approach?

A

a software development approach based on

  • values
  • principles
  • core principles
18
Q

4 agile values

A
  1. communication
  2. simplicity
  3. feedback
  4. courage
19
Q

5 states of the agile modelling development process?

A
  1. exploration
  2. planning
  3. iterations to first release
  4. productionising
  5. maintenance
20
Q

agile modelling development process: exploration

A
  • assemble team
  • assess skills
  • examine potential technology
  • experiment with writing user stories
  • playful and curious attitude
21
Q

agile modelling development process: planning

A
  • Rules that formulate teams relationship with customer

- Maximize value of the system

22
Q

agile modelling development process: iteration to first release

A
  • testing
  • feedback
  • change
23
Q

agile modelling development process: productionizing

A
  • product released

- may be improved by adding features

24
Q

agile modelling development process: maintenance

A
  • new features may be added
  • Riskier customer suggestions may be considered
  • Team members can be rotated
25
Q

What is object oriented systems analysis and design?

A
  • Alternate approach to SDLC
  • Used for systems that must change rapidly due to a dynamic business
    environment
  • Use Unified Modeling Language (UML)
26
Q

steps in UML development process

A
  1. draw use case diagrams
  2. write use case scenarios
  3. derive activity diagrams from use cases
  4. develop sequence diagrams
  5. create class diagrams
  6. draw state chart diagrams
  7. modify diagrams and complete specifications
  8. develop and document system
27
Q

what is the use case model?

A
  • Identify the actors and the major events carried out by the actors
  • Diagram with stick figures showing the actors and arrows showing how the actors relate
28
Q

when to use Systems Development Life Cycle?

A
  • Important to document each step of the way
  • Management feels comfortable using this method
  • Adequate resources and time to complete full SDLC
  • Communiation of how new systems work is important
29
Q

when to use Agile Modelling Development?

A
  • Applications need to be developed quickly
  • Rescue takes place
  • Customer is satisfied with incremental improvement
30
Q

When to use Object-oriented Systems Analysis and Design?

A
  • Problems modeled lend themselves to classes
  • Organization supports UML learning
  • Systems can be added gradually
  • Possible to reuse old software
  • Acceptable to tackle difficult problems first