Ch 1: Systems, Roles, & Development Methodologies Flashcards Preview

TAMUCT_CIS5307_SystAnalysis_Fall2018 > Ch 1: Systems, Roles, & Development Methodologies > Flashcards

Flashcards in Ch 1: Systems, Roles, & Development Methodologies Deck (21)
Loading flashcards...
1

List the advantages of using systems analysis and design techniques in approaching computerized information systems for business.

  1. Maximize the usefulness of information
  2. Positions a business to strategically use information as a competitive edge

2

List three roles the systems analyst is called upon to play. Provide a definition for each.

  1. Consultant: an outside expert who brings fresh perspective and relies on systematic approaches and project management fundamentals, versus intimate knowledge of organization's culture, to assess business challenges and recommend appropriate information system solutions.
  2. Supporting Expert: an inside expert who serves as a hardware and software resource with intimate knowledge of an organization's culture to project managers and focuses on modifications that affect smaller groups.
  3. Agent of Change: anytime an anlyst stays in an organizational longer than two weeks and works with others to facilitate change by performing activities within the system development lifecycle.

Ch 1, pp. 2-3, 17

3

What personal qualities are helpful to a systems analyst?

  1. Problem Solver
  2. Communictator
  3. Personal Ethic
  4. Professional Ethic
  5. Self-Discipined
  6. Motivated
  7. Skill sets in programming and managing

Ch 1, pp. 4, 17

4

List and define the seven phases of the systems development life cycle.

  1. Identifying problems, opportunities, and objectives: brainstorming and scoping the project. Critical to this phase it the output of a feasibility report with problem definition and project objectives.
  2. Determining human information requirements: useing an HCI-centric paradigm the analyst employs an array of both interactive and unobtrusive methods to answer the 5W's of the employees' computer information needs. Critical to this phase is understanding the people, goals, data, and procedures invovled.
  3. Analyzing system needs: analyst determines the system's needs. Critical to this phase is the output of diagrams that graphically illustrate systems and a data dictionary that exhaustively lists items within the system along with their specifications.
  4. Desiging the recommended system: creating the front and backend. Critical to this phase are the outputs of procedures, forms, and user interface design that facilitate accurate data input; database creation; controls and backups to protect the system; and program specification packets.
  5. Developing and documenting software: ensuring custom software works and continuity is preserved. Critical to this phase are the outputs of user help in the form of manuals, FAQs, and/or Read Me files.
  6. Testing and maintaining the system: occures before deployment and signifies the majority of the analysts long-term work. Critical to this phase is the output of pinpointing and fixing problems that surface when sample and actual data run through the system.
  7. Implementing and evaluating the system: bringing the system into production. Critical to this phase is smooth conversion, user training, and intended user use (key criterion).

Ch 1, pp.4-9

5

What are computer-aided software engineering (CASE) tools used for?

Analysts rely on CASE tools to increase productivity communicate effectively with users, and integrate the work that they do on the system from the beginning to the end of the life cycle. Capabilties of CASE tools include diagramming, analyzing, and modeling. Examples of CASE tools include MS Visio, Visible Analyst, or OmniGraffle.

Ch 1, pp. 10-11, 502

 

6

Explain what is meant by agile approach.

Also known as agile modeling with its genesis traced to Kent Beck's concepts of exteme programming, the agile approach is a five-stage interactive and incremental systems development approach that has values, principles, and practices useful for analysts who desire a flexible, interactive, and participative approach. This approach values four things: communication, simplicity, feedback, and courage. The five stages of the agile approach are: exploration, planning, iterations to the first release, productionizing, and maintenance.

Ch 1, pp. 11-13, 501

7

What is the meaning of the phrase planning game?

A metaphor for the agile planning process that uses key terms like goals, strategy, pieces, and players in order to describe the development team's relationship with it's business partner. The overarching goal of the game is to maximize the value produced by the system. This is accomplishged by fielding the simplest solution as quickly as possible and immediately implamenting customer feedback to improve fast-turn iterations to the first release.

Ch 1, pp. 12-13, 505 

8

What are the stages in agile development?

9

Define the term object-oriented analysis and design (O-O).

O-O is an system development approach that breaks a system down into use case model by organizing objects into classes with shared attributes and behaviors. O-O and unified modeling language (UML) go hand-in-hand. O-O is the approach, UML is the tool.

Ch 1, pp. 13

10

What is UML?

Industry standard for modeling object-oriented analysis and design of software systems.

Ch. 1, pp.13, 507

11

What is open source software?

A development model and philosophy of liberating software from certain licensing restrictions and publishing its source code, which can then be studied, shared, and modified by users and programmers, sometimes in proprietary ways for profit. The Linux operating system is an example.

Ch. 1, pp. 505

12

What is the role of systems analyst in the development of open source software?

The analysts roll in developing OSS software is to incorporate shared design by weaving open source software designs into their system development. This is accomplished by participating in the OSS community through meaninful contributions that build mutually beneficial relationships, cross-fertilize information, and catalyze creativity.

Ch 1, pp. 16

13

List two reason an organization may want its analysts to participate in an open source community.

  1. Remain abreast of software development
  2. Incorporate emerging best-practices and software into in-house systems
  3. Faster to develop in an OSS community then on a small team
  4. Minimize development costs
  5. Bolster brand by contributing something meaningful to the software community
  6. Altruistic

14

Systems Development Lifecycle Model

15

Define the first phase of the systems development life cycle.

Identifying problems, opportunities, and objectives: brainstorming and scoping the project. Critical to this phase it the output of a feasibility report with problem definition and project objectives.

Ch 1, pp.5-6

16

Define the second phase of the systems development life cycle.

Determining human information requirements: useing an HCI-centric paradigm the analyst employs an array of both interactive and unobtrusive methods to answer the 5W's of the employees' computer information needs. Critical to this phase is understanding the people, goals, data, and procedures invovled.

Ch 1, pp.6

17

Define the third phase of the systems development life cycle.

Analyzing system needs: analyst determines the system's needs. Critical to this phase is the output of diagrams that graphically illustrate systems and a data dictionary that exhaustively lists items within the system along with their specifications.

Ch 1, pp.6-7

18

Define the fourth phase of the systems development life cycle.

Desiging the recommended system: creating the front and backend. Critical to this phase are the outputs of procedures, forms, and user interface design that facilitate accurate data input; database creation; controls and backups to protect the system; and program specification packets.

Ch 1, pp.7-8

19

Define the fifth phase of the systems development life cycle.

Developing and documenting software: ensuring custom software works and continuity is preserved. Critical to this phase are the outputs of user help in the form of manuals, FAQs, and/or Read Me files.

Ch 1, pp.8

20

Define the sixth phase of the systems development life cycle.

Testing and maintaining the system: initially occures before deployment, but continues for the lifespan of the system, and signifies the majority of the analysts long-term work. Critical to this phase is the output of pinpointing and fixing problems that surface when sample and actual data run through the system.

Ch 1, pp.8-10

21

Define the seventh phase of the systems development life cycle.

Implementing and evaluating the system: bringing the system into production. Critical to this phase is smooth conversion, user training, and intended user use (key criterion).

Ch 1, pp.8