Chapter 1

Systems Analysis and Design Instructors Manual

1-1

Chapter 1 Systems, Roles, and Development Methodologies

1

Key Points and Objectives

1. 2. Information is an organizational resource that must be managed as carefully as other resources. Information systems fall into one of the following eight categories: A. $. &. *. ,. .. 0. 1. I. 2. 5. Transaction processing systems (TP ! process large "olumes of data# routine business transactions. %ffice automation systems (%A ! manipulate information and share it throughout the organization. oftware# such as spreadsheets# word processing# email# teleconferencing and so on are routinely used in %A . 'nowledge wor( systems (') ! help professionals to de"elop new (nowledge# often in teams. +anagement information systems (+I ! are computerized information systems that support a broader range of business functions than do data processing systems. *ecision support systems (* ! are information systems that help support decision ma(ers in ma(ing semi-structured decisions. ,/pert systems capture the e/pertise of a human e/pert or e/perts for sol"ing particular organizational problems. Artificial intelligence research is part of e/pert systems and has two a"enues: understanding natural language and analyzing the ability to reason through a problem to its logical conclusion 0roup decision support systems (0* ! and computer supported collaborati"e wor( systems (& &) ! allow group members to interact and help facilitate group problem sol"ing. ,/ecuti"e support systems (,, ! help senior management to ma(e strategic decisions.

3ew technologies# such as ecommerce# ,nterprise or ,nterprise 4esource Planning# wireless and mobile de"ices# and open source software are being integrated into traditional systems. ,commerce uses the )eb to perform business acti"ities. The benefits of using the )eb are: A. $. &. *. Increasing awareness of the a"ailability of the ser"ice# product# industry# person# or group 25-hour access for users Impro"ing the usefulness and usability of interface design &reating a global system

6. 7.

,nterprise 4esource Planning (,4P! has the goal of integrating many different information systems within the corporation# using proprietary software. ystems must be designed for wireless and mobile de"ices# including mobile commerce (mcommerce!.

Copyright 2011 Pearson ducation! Inc" Pu#lishing as Prentice $all

Chapter 1

Systems Analysis and Design Instructors Manual

1-2

8.

%pen source software (% ! pro"ides both software and the program source code used to create the software. +any users and programmers may pro"ide modifications to the programs. %pen source software may be categorized into four types of communities: A. $. &. *. Ad hoc tandardized %rganized &ommercial

9.

%pen source communities differ from each other on si/ (ey dimensions: A. $. &. *. ,. .. 0eneral structure ,n"ironment 0oals +ethods :ser community ;icensing

<.

ystems analysis and design is a systematic approach to identifying problems# opportunities# and ob=ecti"es> analyzing the information flows in organizations> and designing computerized information systems to sol"e a problem. :ser in"ol"ement throughout the systems pro=ect is a critical success factor. ystems analysts act as outside consultants to businesses# as supporting e/perts within a business and as change agents. Analysts are problem sol"ers and re@uire communication s(ills. It is important for analysts to be aware of their ethical framewor( as they wor( to build relationships with users and customers. The systems de"elopment life cycle is a systematic approach to sol"ing business problems. The human-computer interaction (1&I! is a human-centered approach that places an emphasis on human needs before the needs of an organization or a system. The human-computer interaction should be included into e"ery phase of the systems de"elopment life cycle. The systems de"elopment life cycle is di"ided into se"en phases: A. $. &. *. ,. .. Identifying problems# opportunities# and ob=ecti"es *etermining human information re@uirements Analyzing system needs *esigning the recommended system *e"eloping and documenting software Testing and maintaining the system

1?. 11. 12. 12. 15. 16. 17. 18.

0.
19.

Implementing and e"aluating the system

ystem maintenance is remo"ing undetected errors and enhancing e/isting software.

Copyright 2011 Pearson ducation! Inc" Pu#lishing as Prentice $all

Chapter 1

Systems Analysis and Design Instructors Manual

1-%

1<.

ystems are enhanced for the following reasons: A. $. &. Adding additional features to the system. $usiness and go"ernmental re@uirements change o"er time. Technology# hardware# and software are rapidly changing.

2?. 21.

&A , tools are software pac(ages for systems analysis and design. 4easons for using &A , tools are: A. $. &. To increase analyst producti"ity. .acilitate communication among analysts and users. Pro"iding continuity between life cycle phases.

22.

&A , tools may be di"ided into se"eral categories# namely: A. $. :pper &A , tools are used to perform analysis and design. ;ower &A , tools are used to generate computer language source code from &A , design. The ad"antage in generating source code are: a. b. c. d. e. The time to de"elop new systems decreases. The time to maintain generated code is less than to maintain traditional systems. &omputer programs may be generated in more than one language. &A , design may be purchased from third-party "endors and tailored to organizational needs. 0enerated code is free from program coding errors.

22.

The agile approach is based on: A. $. &. Aalues Principles &ore practices

25.

The four "alues of the agile approach are: A. $. &. *. &ommunication implicity .eedbac( &ourage

26.

.our resources may be ad=usted for successful completion of an agile pro=ect:

A. $.
&. *. 27. 28.

Time &ost
Buality cope

An agile pro=ect is interacti"e and incremental The agile de"elopment process has fi"e distinct stages:

Copyright 2011 Pearson ducation! Inc" Pu#lishing as Prentice $all

Chapter 1

Systems Analysis and Design Instructors Manual

1-&

A. $. &. *. ,. 29. 2<. 2?. 21.

22.

,/ploration Planning Iterations to the first release Productionizing +aintenance

The planning game spells out rules that help formulate the agile de"elopment team from their business customers. %b=ect-oriented (%-%! analysis and design is used to build ob=ect-oriented programs. This includes not only data# but the instructions about operations that manipulate the data. The :nified +odeling ;anguage (:+;! is a standardized ob=ect-oriented modeling language. %b=ect-oriented methodologies focus on small# @uic( iterations of de"elopment.
%b=ect-oriented phases include:

A. $. &. *. ,. ..

*efine the use case model. $egin drawing :+; diagrams. *e"elop class diagrams. *raw statechart diagrams. +odify the :+; diagrams. *e"elop and document the system.

Consulting Opportunity 1 1 !p "#

Healthy Hiring: Ecommerce Help Wanted The @ualifications that the systems analysis team should be loo(ing for when hiring their new ecommerce de"elopment team member should focus on interpersonal s(ills as well as technical s(ills. The system de"elopment pro=ect is not analyzing an e/isting business area and does not ha"e to focus on how the current system wor(s or the problems present in the current system. This implies that the analysis team will ha"e to do e/tensi"e wor( with the users to define the new system before writing any program code. %ne of the primary @ualities of the new analyst is to get along well with the other team members as well as users. A second @uality is the ability to learn new languages rather than (now specific languages. $ecause this is a new pro=ect and the software used to de"elop ecommerce )eb sites as well as the other systems needed to support ecommerce is rapidly changing. In this situation# it is important that the team members ha"e some basic business understanding# because ecommerce is much more than =ust building a )eb site. 1owe"er# it is probably ad"antageous if the team members do not possess identical s(ills and competencies. Team member s(ills that complement one another will help the team as it encounters pro=ect comple/ities and has to draw on a broad base of e/perience and (nowledge. The personality traits that are desirable in a systems analyst who will be wor(ing in ecommerce de"elopment are good interpersonal and team player s(ills# good communication s(ills# curiosity#

Copyright 2011 Pearson ducation! Inc" Pu#lishing as Prentice $all

Chapter 1

Systems Analysis and Design Instructors Manual

1-'

creati"ity# ability to deal with stress and pressure# an understanding of how systems are put together# diagramming and design s(ills# and s(ills related to coding# testing# and debugging software.

$yperCase %&perience 1
As stated in the general introduction# it is strongly suggested that students re"iew the instructions. &lic( on the lin( on the home page. This will enable them to understand the principles of how to use the 1yper&ase en"ironment and assist them in ha"ing a "aluable learning e/perience with it. Cou may wish to ma(e assignments starting with the e/ercises# and ha"e the students download the Aisible Analyst files and restore them into their copy of Aisible Analyst. The Aisible Analyst pro=ect name is +4,. A re"iew session or class discussion of what they learned would be a useful learning e/perience. tudents may also download the Aisio files and the repository )eb page. The students should also go to the reception area and ta(e a stroll around the building# clic(ing on lin(s and e/amining the office en"ironment. 1a"e the students print out the telephone directory.

Copyright 2011 Pearson ducation! Inc" Pu#lishing as Prentice $all

Chapter 1

Systems Analysis and Design Instructors Manual

1-(

'ns(ers to Revie( )uestions

1. Compare treating in)ormation as a resource to treating humans as a resource" Information fuels business and can be the critical factor in determining the success or failure of the business. Treating information as a resource includes physical or ergonomic factors# usability factors# aesthetic and en=oyable aspects# and beha"ioral aspects relating to the usefulness of the system. Treating humans as a resource means learning frustrations and feelings that humans ha"e when wor(ing with a system. 2. *ist the di))erences #et+een ,AS and -.S" An office automation system (%A ! is a set of familiar commercial software tools that allow data wor(ers to manipulate data# rather than create it. 0eneral tools# such as word processing and spreadsheets# are used to manipulate the data. A (nowledge wor( system (') ! is used by professionals to create new (nowledge. 2. De)ine +hat is meant #y MIS" +anagement information systems (+I ! includes transaction processing# decision analysis# and produce output that is used in decision ma(ing. 5. $o+ does MIS di))er )rom DSS/ $oth depend on a database as a source of data> howe"er# * emphasizes the support of decision ma(ing in all phases and is more closely tailored to the person or group using them. 6. De)ine the term e0pert systems" $o+ do e0pert systems di))er )rom decision support systems/ An e/pert system captures and uses the (nowledge of an e/pert for sol"ing organizational problems. ,/pert systems select the best solutions to problems# whereas * s lea"e the ultimate =udgment to the decision ma(er. 7. *ist the pro#lems o) group interaction that group decision support systems 12DSS3 and computer-supported colla#orati4e +or5 systems 1CSC.S3 +ere designed to address" The problems of group interaction that group decision support systems address are: A. $. &. 8. ;ac( of participation *omination by group members 0roup thin( decision ma(ing.

.hich is the more general term! CSC.S or 2DSS/ 0plain" & &) is a more general term# and may include software support called groupware for team collaboration.

9.

De)ine the term mcommerce" +commerce is mobile commerce# performing ecommerce using handheld wireless de"ices.

Copyright 2011 Pearson ducation! Inc" Pu#lishing as Prentice $all

Chapter 1

Systems Analysis and Design Instructors Manual

1-6

<.

*ist the ad4antages o) mounting applications on the .e#" The ad"antages of mounting applications on the )orld )ide )eb are: A. $. &. *. Increasing awareness of the a"ailability of the ser"ice# product# industry# person# or group The possibility of 25-hour access for users tandardizing the design of the interface &reating a global system without worry about time zones

1?.

.hat is the o4erarching reason )or designing 7P systems/ The o"erarching reason for designing ,4P systems is the integration of many information systems e/isting on different managerial le"els and within different functions.

11.

Pro4ide an e0ample o) an open source so)t+are pro8ect" There are many open source software pro=ects that are a"ailable. tudents may be familiar with ones that are not mentioned. +ozilla .irefo/# Apache# and ;inu/ are mentioned in this chapter.

12.

*ist the ad4antages o) using systems analysis and design techni9ues in approaching computeri:ed in)ormation systems )or #usiness" ystem analysis and design techni@ues pro"ide the analyst with a systematic procedure for analyzing data input# :+; diagrams or data flow# and information output> furthermore# the techni@ues can impro"e the functioning of business.

12.

*ist three roles that the systems analyst is called upon to play" Pro4ide a de)inition )or each one" The three roles of a system analyst are: A. $. &. &onsultantDhired from outside an organization to address information systems issues within that organization. upporting ,/pertDser"es as a resource for those who are managing a systems pro=ect. &hange AgentDan analyst who ser"es as a catalyst for change# de"elops a plan for change# and wor(s with others in facilitating that change.

15.

.hat personal 9ualities are help)ul to the systems analyst/ *ist them" Personal @ualities helpful to systems analysts include: A. $. &. *. ,. Problem-sol"ing abilities &ommunication s(ills &omputer e/perience elf-discipline and self-moti"ation Pro=ect management capabilities

16.

*ist and #rie)ly de)ine the se4en phases o) the systems de4elopment li)e cycle 1SD*C3" The se"en phases of the *;& are: A. Identifying problems# opportunities# and ob=ecti"esDrecognizing problems and

Copyright 2011 Pearson ducation! Inc" Pu#lishing as Prentice $all

Chapter 1

Systems Analysis and Design Instructors Manual

1-;

$. &. *. ,. ..

opportunities confronting the business and determining business ob=ecti"es. *etermining information re@uirementsDunderstanding what information users need to perform their =obs. Analyzing system needsDstructured analysis of information needs and decision ma(ing. *esigning the recommended systemDlogical design of the information system. *e"eloping and documenting softwareDstructured de"elopment of software and documentation. Testing and maintaining the systemDtesting and re"ising the system.

0.
17.

Implementing and e"aluating the systemDtraining users and re"iewing system.

.hat are CAS tool used )or/ The reasons for using &A , tools are: A. $. &. Increasing analyst producti"ity Impro"ing analyst-user communication Integrating life cycle acti"ities

18.

.hat is the di))erence #et+een upper and lo+er CAS tools/ :pper &A , tools are used for creating and modifying the system design. ;ower &A , tools are used to generate computer source code# eliminating the need for programming the system.

1;"

De)ine +hat is meant #y the agile approach/ The agile approach is based on "alues# principles# and core practices. It "alues communication# simplicity# feedbac(# and courage.

1<.

.hat is the meaning o) the phrase <the planning game=/ The planning game spells out rules that can help formulate the agile de"elopment teamEs relationship with their business customers. The rules are a basis for building and maintaining a relationship.

2?.

.hat are the stages in agile de4elopment/ The fi"e stages in agile de"elopment are e/ploration# planning# iterations to the first release# productionizing# and maintenance.

21.

De)ine the terms o#8ect-oriented analysis and o#8ect-oriented design" %b=ect-oriented analysis and ob=ect-oriented design are techni@ues intended to facilitate the de"elopment of systems that must change rapidly in response to dynamic business en"ironments.

22.

.hat is >M*/ :+; is the :nified +odeling ;anguage# a standardized ob=ect-oriented language used to brea( down a system into a use case model.

Copyright 2011 Pearson ducation! Inc" Pu#lishing as Prentice $all

Chapter 1

Systems Analysis and Design Instructors Manual

1-?

Central Paci*ic +niversity,Problems

1" @rom the introductory con4ersation Chip and Anna shared! +hich elements mentioned might suggest the use o) CAS tools/ &A , tools would be used to help &hip and Anna communicate with each other and share portions of the design that they ha"e completed. $ecause there are many users for the &omputer ystem# &A , tools will help to facilitate communication among the users and analyst and document the information that they ha"e recei"ed as a result of inter"iews# document analysis# and @uestionnaires.

Copyright 2011 Pearson ducation! Inc" Pu#lishing as Prentice $all