Systems Analysis and Design, Ninth Edition
Page 1 of 48
Systems Analysis Analysis and Design Ninth Edition
End of Chapter Solutions CHAPTE !"#E
DATA AND P$CESS %$DE&"N' ANSWERS TO CASE-SIM: SCR ASSOCIATES ASSOCIATES
1( )esse )esse *ants to see a +ontet +ontet diagram diagram and a diagram diagram - D!D D!D for T"%S( Sample context diagram:
TRAINING
CORPORATE
INSTRUCTOR
A D M I NI S T RA T OR
CLIENT
TRAINING S C H E DU DU L E
REPORTS
DECISIONS
T RAINING SUM M ARY COURSE
C OM OM P L E T I ON ON D A T A
REQUEST
0
C ON ON F I R M A T I O N
ROSTER
STUDENT INVOICE
COURSE ASSIGNM ENT TIM S SYSTEM
PAYM ENT
C OU OU R S E D A T A
A CC OU N T I NG DA T A A C C OU N T I NG
COURSES
SYSTEM
Systems Analysis and Design, Ninth Edition
Page . of 48
Sample diagram 0 DFD: TRAINING TRAI NING REPORTS
TRAININ TRAINI NG ADMINIST MINISTR RATO ATOR
COURSES
STUDENT
SCHEDULE
PAYMENT
DECISIO DECISI ONS
INVOI CE
1
COURSE REQUEST
COURSE M ANAGE
DATA
2
COURSE SCHEDULING EDULI NG
ACCOUNTING REGISTER
COURSE ASSIGNMENT
DATA
STUDENTS CURRENT
AC ACCOUNTING
CONFIRMATI NFIRM ATIO ON
SYSTEM
SCHEDULE
D2
SCHEDULE DATA DATA SCHEDULE DATA
REGISTRATIO STRATI ON DATA
ROSTER STER
3
INSTRUCTOR
D1
STUDENT DATA MAINTAIN TRAINING TRAINI NG RECORDS COM PLETI PL ETIO ON
STUDENT
4
DATA
PRODUCE
TRAINING TRAI NING DATA
DATA
REPORTS TRAINING TRAINI NG DATA
CORPORATE D3
TRAINING TRAI NING DATA
CLIENT
TRAINING TRAINI NG SUM M ARY
TRAINING TRAI NING DATA
2. Need to re/ie* the )AD session summary again0 Try Try to identify four main T"%S T"%S fun+tions and dra* a lo*erle/el D!D for ea+h pro+ess( The four main functions are shown as subprocesses in diagram 0 DFD. They are: M!"# $%&'S# S$(#D&)*!" +,rocess -/ '#"*ST#' ST&D#!TS +,rocess 2/ 2/ M*!T*! M*!T*! T'*!*!" '#$%'DS +,rocess +,rocess / and ,'%D&$# '#,%'TS +,rocess 1. #xamples of the four lowerle3el DFDs follow: follow:
Systems Analysis and Design, Ninth Edition
Page . of 48
Sample diagram 0 DFD: TRAINING TRAI NING REPORTS
TRAININ TRAINI NG ADMINIST MINISTR RATO ATOR
COURSES
STUDENT
SCHEDULE
PAYMENT
DECISIO DECISI ONS
INVOI CE
1
COURSE REQUEST
COURSE M ANAGE
DATA
2
COURSE SCHEDULING EDULI NG
ACCOUNTING REGISTER
COURSE ASSIGNMENT
DATA
STUDENTS CURRENT
AC ACCOUNTING
CONFIRMATI NFIRM ATIO ON
SYSTEM
SCHEDULE
D2
SCHEDULE DATA DATA SCHEDULE DATA
REGISTRATIO STRATI ON DATA
ROSTER STER
3
INSTRUCTOR
D1
STUDENT DATA MAINTAIN TRAINING TRAINI NG RECORDS COM PLETI PL ETIO ON
STUDENT
4
DATA
PRODUCE
TRAINING TRAI NING DATA
DATA
REPORTS TRAINING TRAINI NG DATA
CORPORATE D3
TRAINING TRAI NING DATA
CLIENT
TRAINING TRAINI NG SUM M ARY
TRAINING TRAI NING DATA
2. Need to re/ie* the )AD session summary again0 Try Try to identify four main T"%S T"%S fun+tions and dra* a lo*erle/el D!D for ea+h pro+ess( The four main functions are shown as subprocesses in diagram 0 DFD. They are: M!"# $%&'S# S$(#D&)*!" +,rocess -/ '#"*ST#' ST&D#!TS +,rocess 2/ 2/ M*!T*! M*!T*! T'*!*!" '#$%'DS +,rocess +,rocess / and ,'%D&$# '#,%'TS +,rocess 1. #xamples of the four lowerle3el DFDs follow: follow:
Systems Analysis and Design, Ninth Edition
Page 2 of 48
Diagram - DFD: +#xternal symbols omitted for clarity D5
D4
INSTRU CTOR D ATA ATA
CO UR SE HISTORY HISTORY
SCHEDULE
COURSE
INSTRUCTOR
HISTOR HISTOR Y
DATA
D ECISI ECISION S CO UR SE DATA
1.2
1.1
INSTRU CTOR N EE EEDS DS ANAL YZE
SCHEDULE
SCHEDULE
DATA
ANAL YZE INSTRUCTOR AVAILABI AVAILABIL L ITY
D EMAN MAN D CO UR SE DATA TRAINING TRAINING D ATA
COURSE ASSIGN ASSIGN MENT
1.3
CURRENT C REATE SCHEDULE
SCHEDULE
Systems Analysis and Design, Ninth Edition
Page 4 of 48
Diagram 2 DFD: +#xternal symbols omitted for clarity COU RSE REQUEST REQUEST
CONFIRMATION
SCHEDULE DATA
2.2
2.1
PROCESS
INVOICES
COURSE
AND
REQUESTS
PAYMEN PAYMENTS TS
R EGISTRATION EGISTRATION DATA
IN VOIC VOIC E
HANDLE
PAYMENT PAYMENT
INVOICE R EGISTRATION EGISTRATION
AND
DATA
PAYME PAYMEN N T D ATA
2.5
D6
ACC OU N TIN TIN G DATA STUDENT
R EGISTRATION EGISTRATION UPDATE R EGISTRATION EGISTRATION DATA
INVOICE
STATUS
AND
DATA
PAYME PAYMEN N T D ATA 2.3
COURSE
ACC OU N TING
ROSTER PREPAR PREPAR E
DATA
DATA
ACC OU N TING DATA
2.4
CREATE
COURSE
COURSE
RO STER STER DATA D7
ROSTERS
CO UR SE ROSTE ROSTERS
ROSTER
Systems Analysis and Design, Ninth Edition
Page 3 of 48
Diagram 3 DFD: (External symbols omitted for clarity) C OMPLETION
3.1
DATA UPDATE TRAIN IN G D ATA
TRAIN IN G D ATA
TRAINING DATA
TRAINING DATA
D3
TRAIN IN G D ATA
TRAINING DATA
3.2
STUDENT STUD ENT DATA
UPDATE STUDENT DATA
DATA
Systems Analysis and Design, Ninth Edition
Page of 48
Diagram 4 DFD: (External symbols omitted for clarity) 4.1
TRAINING
TRAINING SUMMARY DATA
PRODUCE
SUMMARY
TRAINING SUMMARY
REPORT DATA
D8
REPORT DATA FILE
REPORT DATA
4.2
TRAINING
TRAINING REPORT DATA
PRODUCE
REPORTS
TRAINING REPORTS
3. Prepare a reply to Jesse’s message about CASE tools. Search the Internet to find two more alternatives. Answers will vary. The memo asks for two additional CASE tool choices. A sear ch for CASE tools will point to many potential vendors and products. Encourage students to come up with as much information as possible.
Systems Analysis and Design, Ninth Edition
Page 5 of 48
4. Prepare a decision table and a decision tree that show the logical rules described in Jesse’s message about fees and discounts. sample decision table and a second 3ersion with simplified rules follow:
'&)#S Multiple courses8 #mployed by S$' client8 $lient ser3ice rep wai3er8 #ligible for discount #ligible for discount ; !ot eligible for discounts
9
2 9
9
1 9
4 !
5 !
6 !
7 !
9
9
!
!
9
9
!
!
9
!
9
!
9
!
9
!
Simplified rules: '&)#S Multiple courses8 #mployed by S$' client8 $lient ser3ice rep wai3er8 #ligible for discount #ligible for discount ; !ot eligible for discounts
9
2 9
9
1 !
4 !
5 !
9
!
!
9
!
!
9
!
9
!
Systems Analysis and Design, Ninth Edition
Page 8 of 48
sample decision tree follows:
Employed 6y SC +lient
Eligi6le for dis+ount A and 9
:es Client ser/i+e rep :es o/erride
No
:es
Eligi6le for dis+ount A and 9
No
%ultiple +ourses
Eligi6le for dis+ount A
No
Employed 6y SC +lient Eligi6le for dis+ount 9
:es
No
Client ser/i+e rep o/erride
:es
Eligi6le for dis+ount 9
No Not eligi6le for dis+ounts
ANSWERS TO CHAPTER EXERCISES Review Questions 1( Des+ri6e data and pro+ess modeling and name the main data and pro+ess modeling te+hni7ues( Data and process modeling is a processcentered approach because it focuses on the flow of data and the processes that affect that data. Data an d process modeling produces a logical model of a business information system by examining the system
ues are DFDs/ the data dictionary/ and process description tools. Data flow diagrams +DFDs show the flow of data through an information system in a graphical/ topdown fashion. The data dictionary documents the contents of data flows/ data stores/ external entities/ and processes. ,rocess description tools include structured #nglish/ decision tables/ and decision trees. Structured #nglish is a subset of standard #nglish used to describe logical processes clearly and accurately. decision table is a tabular description of a logical structure. decision tree is a hori?ontal graphic representation of a logical structure. (Pages 198, 200, 217, 224-230)
Systems Analysis and Design, Ninth Edition
Page ; of 48
.( Des+ri6e the 'ane and Sarson sym6ols used for pro+esses, data flo*s, data stores, and entities( 'i/e four eamples of typi+al names for pro+esses, data flo*s, data stores, and entities( process recei3es input data and changes its content/ form/ or both. The "ane and Sarson symbol for a process is a rectangle with rounded corners/ while the 9ourdon symbol is a circle. The name of the process is placed inside the symbol. #xamples of good process names are ,,)9 '#!T ,9M#!T/ $)$&)T# $%MM*SS*%!/ SS*"! F*!) "'D#/ @#'*F9 %'D#'/ and F*)) %'D#'. data flow is a path by which data mo3es from one part of an information system to another. data flow can represent one or more data elements. The symbol for a data flow is a line with an arrowhead/ and the name of the data flow is placed abo3e/ below/ or alongside the line. The lineuare. The "ane and Sarson symbol usually is shaded/ and the name of the external entity is placed inside the symbol. Some examples of entity names might be $&ST%M#'/ ;!A/ @#!D%'/ or $$%&!T*!" S9ST#M. (Pages 200 205) 2(
Systems Analysis and Design, Ninth Edition
Page 1- of 48
including the contents of data flows/ data stores/ entities/ and processes. The data dictionary also defines and describes all data elements and meaningful combinations of data elements. During enterprise modeling/ the data dictionary d ocuments the contents of data flows/ data stores/ external entities/ and processes that appear in the information systemCs data flow diagrams. (Page 217) ( Eplain the D!D le/eling te+hni7ue( )e3eling also is called exploding/ partitioning/ or decomposing. )e3eling describes the techni>ue of representing the graphical model of an information system first as a single process/ and then in greater and greater detail/ until all processes are functional primiti3es. (Pages 212-213) 5(
Systems Analysis and Design, Ninth Edition
Page 11 of 48
Discussion o!ics 1( Suppose you *ere assigned to de/elop a logi+al model of the registration system at a s+hool or +ollege( uestion. 'egardless of which strategy used/ apply the suggestions and guidelines discussed in this chapter. The main obBecti3e is to ensure that your model is accurate and easy to understand.
.( Some systems analysts find it 6etter to start *ith a de+ision ta6le, then +onstru+t a de+ision tree( $thers 6elie/e it is easier to do it in the re/erse order( o6, she told her 6oss that stru+tured analysis *as not *orth the time to learn and use on the >o6( Her /ie* *as that it *as too a+ademi+ and had too mu+h ne* terminology to 6e useful in a pra+ti+al setting( Do you agree or disagree Defend your position( Students typically support both positions. There are some arguments for agreeing with the systems analystCs 3iewpoint. First/ if the organi?ation already has a systems analysis methodology that wor=s effecti3ely/ there is no reason to introduce a n ew approach. Second/ Bust because some people find structured analysis to be useful does not mean that the organi?ation will find it to be useful. Third/ learning and adopting any new method in3ol3es time and cost/ which need to be identified and allocated. Fourth/ before the introduction of structured analysis/ other systems analysis methodologies were used/ so there probably will be other new approaches in the future to replace structured analysis. Some arguments for disagreeing with the systems analystCs 3iewpoint fo llow. First/ many companies use structured analysis and many experts endorse this approach/ so structured analysis must be an effecti3e approach. Second/ if the company currently does not ha3e a standard systems analysis methodology/ structured analysis is as good as any methodology/ and a standard approach would be beneficial to the company. Third/ learning something new is good/ e3en if the company only ends up >uestioning what they currently do and how they do it.
Systems Analysis and Design, Ninth Edition
Page 1. of 48
Fourth/ the company must =eep uptodate in order to handle Eebbased research/ understand technology de3elopments/ and communicate effecti3ely with other *T professionals. 4( This +hapter des+ri6es a 6la+= 6o +on+ept that allo*s more detail to 6e sho*n as a pro+ess is eploded( Can the +on+ept 6e applied in 6usiness management generally, or is it limited to information systems design Pro/ide reasons and eamples *ith your ans*er( Modular design concepts can be applied in any situation. Students should understand that a modular approach simply brea=s tas=s or processes down into smaller units that easily can be rearranged/ reassigned/ and managed. *n $hapter / students learned about proBect management/ and they can see how tas=s are bro=en down into basic units that can be measured and trac=ed. familiar example of modular design might be prefabricated roof trusses that can be lifted into place and tied into a home construction system. Similarly/ an auto manufacturer might use the same ignition module for se3eral models. child playing with a )egos™ set is an excellent example of flexible modular design at wor=. P"o#ects 1( Dra* a +ontet diagram and a diagram - D!D that represents the registration system at your s+hool or an imaginary s+hool( The DFDs were created with @isible nalyst $S# tool. The context diagram is 3ery basic and does not include other entities that might be added/ including *nstructor/ 'egistrar/ and $lassroom. The context diagram follows:
Systems Analysis and Design, Ninth Edition
Page 12 of 48
The diagram 0 DFD follows:
.( $n the "nternet, lo+ate at least three firms that offer CASE tools( uests for product information. 2( Suppose that you *ant to demonstrate a de+ision ta6le to someone *ho has ne/er seen one( Thin= of an eample, *ith t*o or three +onditions, from e/eryday life( Dra* a d e+ision ta6le that +aptures all possi6le out+omes( Students should be able to suggest many situations where se3eral conditions control the outcome. Some suggestions might be course prere>uisites +and possible wai3ers that determine whether a student can ta=e a particular course 3arious discounts that can +or cannot be combined to change the price at a retail store or a company policy that allows an employee to ta=e sic= lea3e if he or she has enough seniority and accumulated sic= lea3e time.
Systems Analysis and Design, Ninth Edition
Page 14 of 48
4( The data flo* sym6ols sho*n on page .-1 *ere designed 6y Ed :ourdon, a *ell=no*n "T author, le+turer, and +onsultant( %any "T professionals +onsider him to 6e among the most influential men and *omen in the soft*are field( &earn more a6out %r( :ourdon 6y /isiting his
Digita$ %onsu$ting Situation? :ou are a senior systems analyst at Digital Consulting, a gro*ing "T +onsulting firm( :ou are leading the de/elopment team for a ma>or +lient( :ou need to eplain stru+tured analysis to your t*o ne*ly hired >unior analysts @Sara and %i=e 6efore meeting *ith the +lient tomorro* afternoon(
1(Des+ri6e the rules for +reating a +ontet diagram( a. Start by placing a single process symbol in the center of the page. The symbol represents the entire information system/ and you identify it as process 0. b. !ext/ place the external entities around the perimeter of the page/ and use data flows to connect the entities to the central process. c. Do not show any data stores in a context diagram because data stores are internal to the system. d. ,lace the external entities around the central process and label them. e. $reate labeled input and output data flows between the external entities and the central system. .(%a=e a 6asi+ list of dos and donBts *hen de/eloping D!Ds( The basic rules/ or con3entions that apply to DFD de3elopment are: a. #ach context diagram must fit on one page. b. The process name in the context diagram should be the name of the information system. c. &se uni>ue names within each set of symbols. d. Do not cross lines. e. &se a uni>ue reference number for each process symbol. *n addition to these rules/ the systems analyst must use the proper DFD shapes/ connect them correctly/ and produce a le3eled/ balanced set of DFDs. 2(Eplain the importan+e of le/eling and 6alan+ing( Ehen lowerle3el diagrams/ also called child diagrams/ are needed to show detail/ it is essential that they be le3eled and balanced. )e3eling is the process of drawing a series of increasingly detailed diagrams/ until the desired degree of detail is reached. ;alancing maintains consistency among the entire series of diagrams/ including input and output data flows/ data definition/ and process descriptions. )e3eling displays the information system as a single process and then shows more detail until all processes are functional primiti3es. t that point/ an alysts describe the set
Systems Analysis and Design, Ninth Edition
Page 13 of 48
of DFDs as le3eled. )e3eling also is called exploding/ partitioning/ or decomposing. ;ecause analysts create DFDs as a series of topdown pictures of an information system/ each lower le3el pro3ides additional details. DFDs must be balanced properly. balanced set of DFDs preser3es the input and output data flows of the parent on the child DFD. Figure 4-G on page 2-4 shows a balanced DFD it has the same input and output flows as its parent/ which is process -/ F*)) %'D#'. 4(As= Sara and %i=e to re/ie* the order system +ontet diagram on page .-8, and +ompare it to the order system diagram - D!D on page .1.( Then as= them to ans*er the follo*ing 7uestions? @a Ho* many eternal entities are sho*n in e a+h diagram @6 "n ea+h diagram, ho* many data flo*s +onne+t to the eternal entities @+ Ho* many su6 pro+esses are identified in the diagram - D!D @d Could the data store ha/e 6een sho*n in the +ontet diagram
Systems Analysis and Design, Ninth Edition 2
Page 1 of 48
P"ecision oo$s Situation? Pre+ision Tools sells a line of high7uality *ood*or=ing tools(
1(Dra* a +ontet diagram for the order system( sample context diagram might loo= li=e this?
IN-STOCK ORDER
REQUEST
CUSTOMER
WAREHOUSE
PAYMEN T
0
SHIPPIN G OR D ER
STATUS MESSAGE
ORDER SYSTEM
SHIPPIN G C ON FIRMATION
IN VOIC E
INVENTORY REPORTS
A C C O U N T IN G DEPARTMENT
Systems Analysis and Design, Ninth Edition
Page 15 of 48
.(Dra* a diagram - D!D for the order system( sample diagram 0 might loo= li=e this: SHIPPIN G C ON FIR MATION
1
IN -STOCK R EQUEST
ORDER CHECK
WAREHOUSE
O R D ER D A TA
STATU S
STATU S
STATUS
DATA
MESSAGE
CUSTOMER
D1
PENDING ORDERS
2
ORDER IN VOIC E
DATA
PAYMENT ISSU E MESSAGES 5
3
SH IPPIN G MANAGE
GENERATE
AC C OU N TS
SHIPPIN G
R ECEIVABLE
ORDER
ORDER
AC C OU N TIN G DATA D3
ACCOUNTS R ECEIVABLE D ATA AC C O U N TS R ECEIVABLE D ATA 4
O R D ER D A TA
PRODUCE REPORTS
AC C OU N TIN G INVENTORY
DEPARTMENT
REPORTS
2(Name four attri6utes that you +an use to define a pro+ess in the order system( Typical attributes used to define processes are: ,rocess name or label: The process name as it appears on the DFDs. ,urpose or description: brief statement of the process
Systems Analysis and Design, Ninth Edition
Page 18 of 48
,rocess description: This section is filled in only if the process is a functional primiti3e. For functional primiti3es the process description documents the processing steps and business logic.
4(Name four attri6utes that you +an use to define an entity in the order system( Typical attributes used to define entities are: #xternal entity name: The external en tity name as it appears on the DFDs. lternate name+s: ny aliases for the external entity name. Description: Describe the external entity and its purpose. *nput da ta flow: The standard DFD names for the inpu t data flows to the external entity. %utput data flows: The standard DFD names for the data flows lea3ing the external entity.
3
%$a"e&ont 'coo$ Situation? The Claremont S+hool +ourse +atalog reads as follo*s? To enroll in C"S .88, *hi+h is an ad/an+ed +ourse, a student must +omplete t*o prere7uisites C"S 11- and C"S .8( A student *ho +ompletes either one of these prere7uisites and o6tains the instru+torBs permission, ho*e/er, *ill 6e allo*ed to ta=e C"S .88(
1(Create a de+ision ta6le that des+ri6es the Claremont S+hool +ourse +atalog regarding eligi6ility for C"S .88( Sho* all possi6le rules( 'emind students to follow the four steps outlined next to Figure 44 on page 225. The initial 3ersion of the decision table/ which contains all possible rules/ should loo= something li=e the following: '&)#S $*S --0 $*S 275 E*@#' #)*"*;)# *!#)*"*;)#
9 9 9
2 9 9 !
9 ! 9
1 9 ! !
4 ! 9 9
5 ! 9 !
6 ! ! 9
7 ! ! !
.(Simplify the ta6le you >ust +reated( Des+ri6e the results( *n this example/ 'ules - and 2 can be combined/ because if both conditions are met/ a wai3er is not needed and is irrele3ant. lso/ 'ules 6 and 7 can be combined/ because if neither condition is met/ a wai3er cannot be used. Therefore/ after simplification/ six rules remain/ as shown: '&)#S $*S --0 $*S 275 E*@#' #)*"*;)#
9 9
2 ! 9 9
! 9 !
1 9 ! 9
4 9 ! !
5 ! !
Systems Analysis and Design, Ninth Edition *!#)*"*;)#
Page 1; of 48
2(Dra* a simplified de+ision tree to represent the Claremont S+hool +atalog( Des+ri6e the results( The decision tree uses the same logic as the table a bo3e. Ehere the wai3er is not rele3ant/ it is not shown. Therefore/ the eight rules can be simplified to six rules/ and the tree should loo= li=e this: Eligi6le C"S .8 Eligi6le No C"S .8 C"S 11-
No
Not Eligi6le Eligi6le
No C"S 11C"S .8
No
Not Eligi6le
No C"S .8 Not Eligi6le
4(ui3alent/ but in different forms H a graphic 3ersus a table. Ehether to use a decision table or a decision tree often is a matter of personal preference. decision table might be a better way to handle complex combinations of conditions. %n the other hand/ a decision tree is an effecti3e way to describe a relati3ely simple process.
Systems Analysis and Design, Ninth Edition
Page .- of 48
4 %it *us +ines Situation? City 9us &ines is de/eloping an information system that *ill monitor passenger traffi+, pea= tra/el hours, and e7uipment re7uirements( The "T manager *ants you to do+ument a pro+ess +alled 9A&ANCE that determines *hether etra 6uses +urrently are needed on a parti+ular route( The 9A&ANCE pro+ess automati+ally assigns additional 6uses to that route, 6ut only if all other routes are operating on s+hedule( "n any +ase, a super/isor +an o/erride the automati+ 9A&ANCE pro+ess if he or she so desires(
1(Create a de+ision ta6le that des+ri6es the 6us transfer pro+ess( sample decision table follows: '&)#S #xtra buses needed8 ll other routes on schedule8 Super3isor o3erride8 ssign extra buses Do not assign extra buses
9
2 9
9
1 9
4 !
5 !
6 !
7 !
9
9
!
!
9
9
!
!
9
!
9
!
9
!
9
!
fter simplification the table might loo= li=e this: '&)#S #xtra buses needed8 ll other routes on schedule8 Super3isor o3erride8 ssign extra buses Do not assign extra buses
9
2 9
9
1 !
9
!
!
9
!
Systems Analysis and Design, Ninth Edition
Page .1 of 48
.(Dra* a de+ision tree that des+ri6es the 6us transfer pro+ess( The decision tree should loo= something li=e the following: Assign etra 6uses :es $ther routes on time
:es
No
:es Dispat+her o/erride
No
9uses needed
Assign etra 6uses
No etra 6uses
No No etra 6uses
2(Name four attri6utes that you +an use to define a data flo* in the 6us information system( Typical attributes used to define data flows are: Data flow name or label: The data flow name as it appears on the DFDs. lternate name+s: liases for the DFD data flow name+s. Description: Describes the data flow and its purpose. %rigin: The DFD beginning/ or source/ for the data flow the origin can be a process/ a data store/ or an external entity. Destination: The DFD ending point+s for the data flow the destination can be a process/ a data store/ or an external entity. 'eco rd: #ach data flow represents a group of related data elements called a record or data structure. *n most data dictionaries/ records are defined separately from the data flows and data stores. Ehen records are defined/ more than one data flow or data store can use the same record/ if necessary. @olume and fre>uency: Describes the expected number of occurrences for the data flow per unit of time.
4(Name four attri6utes that you +an use to define a data store in the 6us information system( Typical attributes used to define data stores are: Data store name or la bel: The data store name as it appears on the DFDs. lternate name+s: liases for the DFD data store name. Description: Describes the data store and its p urpose. *nput da ta flows: The standard DFD names for the data flows entering the data store. %utput data flows: The standard DFD names for the data flows lea3ing the data store. 'eco rd: The record name in the data dictionary for the data store.
Systems Analysis and Design, Ninth Edition
Page .. of 48
@olume and fre>uency: Describes the estimated number of records stored in the data store specifies any growth and change statistics for the data store
ANSWERS TO CASE STUDIES New Century Heat! C"n"# 1( Prepare a +ontet diagram for Ne* CenturyBs information system( sample diagram might loo= li=e this:
AMERICAN INSURANCE
PATIENT
MEDICAL
COMPANY
CLAIM
PATIENT
ASSOCIATION
INSURANCE PAYMENT
REPORTS AND
PATIENT PAYMENT
OUTPUTS
CPT CODES 0
PATIENT INPUTS
NEW CENTURY OFFICE
PROVIDER REPORTS AND OUTPUTS
SYSTEM
OFFICE STAFF REPORTS AND OUTPUTS
PROVIDER INPUTS
OFFICE STAFF
PROVIDER
$ontext diagram for !ew $entury (ealth $linic %ffice System
Systems Analysis and Design, Ninth Edition
Page .2 of 48
.( Prepare a diagram - D!D for Ne* Century( 9e sure to sho* num6ered pro+esses for handling appointment pro+essing, payment and insuran+e pro+essing, report pro+essing, and re+ords maintenan+e( Also, prepare lo*erle/el D!Ds for ea+h num6ered pro+ess( DFDs follow:
MTD PAYMENTS MTD
PATIENT PAYMENT
PAYMENTS 2
INSURANCE PAYMENT
D4
STATEMENT PROCESS PAYMENT
INSURANCE
PATIENT
COMPANY
APPOINTMENT REQUEST
YTD PAYMENTS
PAYMENT DATA
PAYMENT UPDATE CLAIM
PENDING INSURANCE CLAIMS
D22
INSURANCE CLAIM DATA
AMERICAN MEDICAL ASSOCIATION
CPT
HOUSEHOLD DATA
CODES
1 CHARGES
APPOINTMENT DATA
PROCESS
D
PROVIDER DATA
APPOINTMENT D"
UPDATE PROVIDER CHARGES
SERVICE CHARGE
DATA
D3
APPOINTMENT
PROVIDERS
FEE
DATA
PROVIDER UPDATE
AND SERVICE D1
HOUSEHOLDS
HOUSEHOLD
APPOINTMENT SERVICE DATA
MTD PAYMENTS
SERVICE DATA
DATA
D21
SERVICE DATA
D!
INSURANCE CARRIERS
INSURANCE CARRIER DATA INSURANCE UPDATE
MTD CHARGES PATIENT DATA
SERVICE CHARGE 3
INSURANCE COMPANY REPORT
D2
PATIENTS
CLAIM STATUS SUMMARY PRODUCE REPORTS
APPOINTMENT LIST PATIENT UPDATE
PROVIDER MAILING LABELS
CALL
PROVIDER CHANGE
REPORT
LIST INSURANCE CHANGE
4
HOUSEHOLD OFFICE STAFF
PROVIDER
PATIENT
CHANGE MAINTAIN PATIENT CHANGE
REMINDER POSTCARD
Diagram 0 DFD
RECORDS
Systems Analysis and Design, Ninth Edition
Page .4 of 48
The four main processes shown on diagram 0 DFD are ,'%$#SS ,,%*!TM#!T +,rocess -/ ,'%$#SS ,9M#!T +,rocess 2/ ,'%D&$# '#,%'TS +,rocess / and M*!T*! '#$%'DS +,rocess 1. Samples of lowerle3el diagrams for these four processes follow:
1#3 AMERICAN PATIENT
MODIFY
MEDICAL
CPT
CPT COD E
CODES
ASSOCIATION
APPOINTMEN T REQU EST
CPT CODES CPT FEE SCHEDU LE 1#1
CPT FEE SCHEDU LE
D2 3
PATIENT D ATA
MAKE
FEE
APPOINT MENT
DATA MTD CHARGES
D!
1#4
APPT DATA
SERVIC E
MODIFY
DATA
CPT FEE
PRO VID ER
DATA
SERVICE SCHEDULED D2 " SERVIC E DATA
FEE
DATA SERVIC E CHARGE
APPT DATA
D2
PATIEN TS
D3
PROVIDERS
SCHEDULED D2 APPOINT MENT DATA PRO VID ER APPT DATA
DATA
1#2
CO MPLETED D2 !
COMPLETE
APPT DATA
APPOIN TMENT
PROVID ER CHARGES
SERVIC E DATA
INSUR ANCE C LAIM SERVIC E DATA
DATA
CLAIM
COMPLETED D2 $
PENDING D2 2 INSUR ANCE CLAIMS
SER VIC E DATA INSURANCE CARRIER DATA INSURANCE D2 1
CHARGES
CARRIERS
HOUSEHOLD DATA INSURANCE
D
HOUSEHOLDS
. Diagram - DFD
COMPANY
Systems Analysis and Design, Ninth Edition
Page .3 of 48
PATIEN T PAYMENT
2#1
MTD PAYMEN TS
YTD PAYMEN TS
PROCESS PATIEN T PAYMENT
MTD PAYMEN TS
D4
D
HOUSEHOLDS
2#2 MTD PAYMENTS
PROCESS
YTD PAYMEN TS
INSURANCE PAYMENT D ATA
PAYMENT
PAYMENT UPDATE PENDING D 22
INSURANCE PAYMENT
INSUR ANCE C LAIMS
Diagram 2 DFD
INSURANCE CO MPANY
Systems Analysis and Design, Ninth Edition
Page . of 48
OFFICE STAFF MAILING LABELS
SERVICE
SERVICE
DATA CALL
DATA D1
LIST
SERVICE DATA
APPOINTMENT DATA
D"
MTD
APPOINTMENT DATA
PAYMENTS
APPOINTMENT DATA 3#2
3#1
REMINDER POSTCARD
PRODUCE
PRODUCE DAILY REPORTS
OTHER SERVICE
REPORTS
CHARGE
APPOINTMENT LIST
PROVIDER REPORT
PROVIDER
INSURANC E COMPANY REPORT CLAIM STATUS SUMMARY
Diagram DFD
STATEMENT
PATIENT
Systems Analysis and Design, Ninth Edition
D"
Page .5 of 48
APPOINT MENT D ATA
D1
SERVICE DATA
CALL LIST DATA
3#1#1
PROVIDER APPOINT MENT DATA
CREATE CALL L IST CALL LIST
3#1#2 SERVICE DATA
OFFICE STAFF
CREATE
APPOIN TMEN T LIST
APPOINT MENT LIST
Diagram .- DFD
PROVIDER
Systems Analysis and Design, Ninth Edition
APPOINTMENT DATA
SERVICE DATA
PROVIDER REPORT
3#2#1
CREATE PROVIDER REPORTS
PROVIDER CLAIM STATUS SUMMARY
3#2#3
CREATE MAILING LABELS
STATEMENT DATA
INSURANCE COMPANY REPORT
SERVICE CHARGE
MTD PAYMENTS
PATIENT DATA
Page .8 of 48
MAILING LABELS OFFICE STAFF
3#2#4 STATEMENT CREATE STATEMENTS
APPOINTMENT DATA
PATIENT
3#2#2 REMINDER POSTCARD CREATE REMINDER POSTCARDS
Diagram .2 DFD
Systems Analysis and Design, Ninth Edition
Page .; of 48
INSURANC E CH ANGE
PATIENT CHANGE
PATIENT
HOUSEHOLD CHANGE
4#1
4#2
MODIFY
MOD IFY
MOD IFY
HOUSEHOLD
INSURANCE
PATIENT
4#3
CARRIERS
D2
PATIENT
HOUSEHOLD
UPDATE
UPDATE
PATIEN TS
HOUSEHOLDS
D
PROVIDER
4#4
CHANGE PRO VID ER
INSUR ANCE U PDATE
INSURANCE D 21
CARRIERS
PROVIDER UPDATE
MODIFY
D3
PROVIDER S
PROVIDER
Diagram 1 DFD 2( Prepare a list of data stores and data flo*s needed for the system( Fnder ea+h data store, list the data elements re7uired( The data flows are as follows: APP$"NT%ENT DATA APP$"NT%ENT &"ST APP$"NT%ENT EGFEST APPT DATA CA&& &"ST CA&& &"ST DATA CHA'ES C&A"% C&A"% STATFS SF%%A: CPT C$DES
Systems Analysis and Design, Ninth Edition CPT !EE SCHEDF&E !EE AND SE#"CE DATA !EE DATA H$FSEH$&D CHAN'E H$FSEH$&D DATA H$FSEH$&D FPDATE "NSFANCE CA"E DATA "NSFANCE CHAN'E "NSFANCE C&A"% DATA "NSFANCE C$%PAN: EP$T "NSFANCE PA:%ENT "NSFANCE FPDATE %A"&"N' &A9E& DATA %A"&"N' &A9E&S %TD PA:%ENTS $!!"CE STA!! EP$TS AND $FTPFTS PAT"ENT CHAN'E PAT"ENT DATA PAT"ENT "NPFTS PAT"ENT PA:%ENT PAT"ENT EP$TS AND $FTPFTS PAT"ENT FPDATE P$#"DE APP$"NT%ENT DATA P$#"DE CHAN'E P$#"DE CHA'ES P$#"DE DATA P$#"DE "NPFTS P$#"DE EP$T P$#"DE EP$T DATA P$#"DE EP$TS AND $FTPFTS P$#"DE FPDATE E%"NDE P$STCAD E%"NDE P$STCAD DATA SCHEDF&ED APPT DATA SCHEDF&ED SE#"CE DATA SE#"CE CHA'E SE#"CE DATA STATE%ENT STATE%ENT DATA :TD PA:%ENTS The data stores are as follows: C$%P&ETED APPT DATA C$%P&ETED SE#"CE DATA CPT !EE SCHEDF&E H$FSEH$&DS
Page 2- of 48
Systems Analysis and Design, Ninth Edition "NSFANCE CA"ES %TD CHA'ES %TD PA:%ENTS PAT"ENTS PEND"N' "NSFANCE C&A"%S P$#"DES SCHEDF&ED APP$"NT%ENT DATA SCHEDF&ED SE#"CE DATA The data elements for each data store are as follows: C$%P&ETED APPT DATA @D.5 Data elements? APP$"NT%ENT NF%9E APP$"NT%ENT DATE STAT T"%E END T"%E PAT"ENT NF%9E P$#"DE NF%9E C$%P&ETED SE#"CE DATA @D.8 Data elements? APP$"NT%ENT NF%9E CPT C$DE !EE CPT !EE SCHEDF&E @D18 Data elements? CPT C$DE CPT !EE P$CEDFE NA%E H$FSEH$&DS @D3 Data elements? H$FSEH$&D NF%9E H$FSEH$&D !"ST NA%E H$FSEH$&D &AST NA%E H$FSEH$&D ADDESS H$FSEH$&D C"T: H$FSEH$&D STATE H$FSEH$&D H$%E PH$NE H$FSEH$&D <$ PH$NE "NSFANCE C$( NF%9E E%P&$:E '$FP NF%9E :TD H$FSEH$&D CHA'ES :TD H$FSEH$&D PA:%ENTS :TD "NSFANCE PA:%ENTS
Page 21 of 48
Systems Analysis and Design, Ninth Edition P"$ 9A&ANCE "NSFANCE CA"ES @D8 Data elements? "NSFANCE C$( NF%9E "NSFANCE C$( NA%E "NSFANCE ADDESS 1 "NSFANCE ADDESS . "NSFANCE C"T: "NSFANCE STATE "NSFANCE I"P "NSFANCE PH$NE %TD CHA'ES @D5 Data elements? H$FSEH$&D NF%9E APP$"NT%ENT NF%9E CPT C$DE P$#"DE NF%9E !EE %TD PA:%ENTS @D4 Data elements? H$FSEH$&D NF%9E PA:%ENT DATE PA:%ENT A%$FNT PA:%ENT S$FCE "NSFANCE C$( NF%9E PAT"ENTS @D. Data elements? PAT"ENT NF%9E PAT"ENT &AST NA%E PAT"ENT !"ST NA%E 9"THDATE H$FSEH$&D NF%9E E&AT"$NSH"P C$DE &AST EJA% PEND"N' "NSFANCE C&A"%S @D.. Data elements? "NSFANCE C$( NF%9E E%P&$:E '$FP NF%9E APP$"NT%ENT NF%9E C&A"% A%$FNT PA:%ENT A%$FNT
Page 2. of 48
Systems Analysis and Design, Ninth Edition
Page 22 of 48
PA:%ENT DATE "NSFANCE CHA'ES %TD "NSFANCE CHA'ES :TD "NSFANCE PA:%ENTS %TD "NSFANCE PA:%ENTS :TD "NSFANCE 9A&ANCE $FTSTAND"N' P$#"DES @D2 Data elements? P$#"DE NF%9E P$#"DE NA%E CHA'ES %TD CHA'ES :TD SCHEDF&ED APPT DATA @D.3 Data elements? APP$"NT%ENT NF%9E APP$"NT%ENT DATE STAT T"%E END T"%E PAT"ENT NF%9E P$#"DE NF%9E SCHEDF&ED SE#"CE DATA @D. Data elements? APP$"NT%ENT NF%9E CPT C$DE !EE 4( Prepare a data di+tionary entry and pro+ess des+ription for one of the systemBs fun+tional primiti/es( Answers will vary, because students will be using the data flow diagrams they cr eated in responding to previous questions. This assignment can be approached in several ways. Have students use structured English, decision tables, or another documentation technique. Although the New Century processes do not require a complex logical solution, create an additional New Century guideline, or policy, that would require the use of a decision table or decision tree. For example, New Century might decide to send out special reminders for patients in certain age groups or for those who have had certain procedures performed during the past year. The main objective is to provide an opportunity to practice and apply the skills learned in this chapter. Many sample documents have been prepared for several of the functional primitives shown in the DFDs on our data flow diagrams. Use these as examples, and encourage students to develop their own solutions. In addition, a full list of the functional primitives, including input and output data flows, have been provided. 'P+. D/%./ /R PR/%.''.' 11, 12, 13, D 14
Systems Analysis and Design, Ninth Edition
,'%$#SS -.-: ,&',%S#:
Page 24 of 48
MA# ,,%*!TM#!T Schedules a patientCs appointment and ser3ices.
*!,&T DT F)%ES:
,,%*!TM#!T '#I&#ST ,T*#!T DT $,T F## S$(#D&)#
%&T,&T DT F)%ES:
S#'@*$# DT ,,T DT
,'%$#SS D#S$'*,T*%!: For each ,,%*!TM#!T '#I&#ST from ,T*#!T 'etrie3e ,T*#!T !&M;#' from ,T*#!TS @erify ,T*#!T !&M;#' For each $,T $%D# in ,,%*!TM#!T '#I&#ST 'etrie3e $,T $%D# from $,T F## S$(#D&)# dd$hangeDelete $,T $%D# in S$(#D&)#D S#'@*$# DT dd$hangeDelete ,'%@*D#' !&M;#' in S$(#D&)#D S#'@*$# DT dd$hangeDelete ,,%*!TM#!T !&M;#'/ ,,%*!TM#!T DT#/ ST'T T*M#/ ,T*#!T !&M;#' in S$(#D&)#D ,,%*!TM#!T DT ,'%$#SS -.2: ,&',%S#:
$%M,)#T# ,,%*!TM#!T ,rocesses an appointment that has been completed
*!,&T DT F)%ES:
#M,)%9#' DT ,'%@*D#' DT (%&S#(%)D DT S#'@*$# DT ,,T DT
%&T,&T DT F)%ES:
$)*M $('"#S ,'%@*D#' $('"#S S#'@*$# $('"# S#'@*$# DT ,,T DT
,'%$#SS D#S$'*,T*%!: For each ,,%*!TM#!T !&M;#' 'etrie3e (%&S#(%)D !&M;#' from ,T*#!TS 'etrie3e #M,)%9#' "'%&, !&M;#' from (%&S#(%)DS 'etrie3e *!S. $%. !&M;#' from (%&S#(%)DS For each ,,%*!TM#!T !&M;#' in $%M,)#T#D ,,%*!TM#!T DT 'etrie3e F## from S#'@*$# DT
Systems Analysis and Design, Ninth Edition
Page 23 of 48
pply $('"# to (%&S#(%)DS pply ,'%@*D#' $('"#S to ,'%@*D#'S pply )ST #M to ,T*#!TS pply F## to MTD $('"#S dd ,,%*!TM#!T !&M;#'/ ,,%*!TM#!T DT#/ ST'T T*M#/ #!D T*M#/ ,T*#!T !&M;#' in $%M,)#T#D ,,%*!TM#!T DT dd $,T $%D#/ ,'%@*D#' !&M;#'/ F## in $%M,)#T#D S#'@*$# DT Delete ,,%*!TM#!T !&M;#'/ ,,%*!TM#!T DT#/ ST'T T*M#/ #!D T*M#/ ,T*#!T !&M;#' in $%M,)#T#D ,,%*!TM#!T DT Delete $,T $%D#/ ,'%@*D#' !&M;#' in S$(#D&)#D S#'@*$# DT Send $)*M to *!S&'!$# $%M,!9 ,'%$#SS -.: ,&',%S#:
*!,&T DT F)%ES: %&T,&T DT F)%ES:
M%D*F9 $,T $%D# dd$hangeDelete an merican Medical ssociation $,T code $,T $%D#S $,T $%D#S
,'%$#SS D#S$'*,T*%!: For each $,T $%D# $(!"# from M#'*$! M#D*$) SS%$*T*%! pply $,T $%D# to $,T F## S$(#D&)# ,'%$#SS -.1: ,&',%S#: *!,&T DT F)%ES: %&T,&T DT F)%ES:
M%D*F9 $,T F## dd$hangeDelete a $,T fee F## DT F## DT
,'%$#SS D#S$'*,T*%!: For each F## $(!"# from ,'%@*D#' pply F## to $,T F## S$(#D&)# /.R %/+ PR. PR/%.''.'
,'%$#SS 2.-: ,&',%S#: *!,&T DT F)%ES: %&T,&T DT F)%ES:
,'%$#SS 2.2:
,'%$#SS ,T*#!T ,9M#!T ,rocess a payment recei3ed from a patient ,T*#!T ,9M#!T MTD ,9M#!TS 9TD ,9M#!TS ,'%$#SS *!S&'!$# ,9M#!T
Systems Analysis and Design, Ninth Edition
Page 2 of 48
,&',%S#:
,rocess a payment recei3ed from an insurance company
*!,&T DT F)%ES: %&T,&T DT F)%ES:
*!S&'!$# ,9M#!T MTD ,9M#!TS 9TD ,9M#!TS
,'%$#SS .-.-: ,&',%S#:
*!,&T DT F)%ES: %&T,&T DT F)%ES: ,'%$#SS .-.2: ,&',%S#:
*!,&T DT F)%ES: %&T,&T DT F)%ES:
,'%$#SS .2.-: ,&',%S#:
*!,&T DT F)%ES:
%&T,&T DT F)%ES:
,'%$#SS .2.2: ,&',%S#:
*!,&T DT F)%ES: %&T,&T DT F)%ES: ,'%$#SS .2.: ,&',%S#:
$'#T# $)) )*ST ,repare and print the daily call list that shows all patients who are to be called to be reminded of their appointment $)) )*ST DT $)) )*ST $'#T# ,,%*!TM#!T )*ST ,repare and print the daily appointment list that shows all patients and their scheduled ser3ices for each pro3ider S#'@*$# DT ,'%@*D#' ,,%*!TM#!T DT ,,%*!TM#!T )*ST
$'#T# ,'%@*D#' '#,%'T ,repare and print the wee=ly pro3ider report that summari?es each pro3iderCs charges for the wee= MTD ,9M#!TS ,'%@*D#' '#,%'T DT S#'@*$# $('"# $)*M STT&S S&MM'9 *!S&'!$# $%M,!9 '#,%'T ,'%@*D#' '#,%'T $'#T# '#M*!D#' ,%ST$'DS ,repare and print reminder postcards for each appointment '#M*!D#' ,%ST$'D DT '#M*!D#' ,%ST$'D $'#T# M*)*!" );#)S ,repare and print patient mailing labels
*!,&T DT F)%ES:
M*)*!" );#) DT
%&T,&T DT F)%ES:
M*)*!" );#)S
Systems Analysis and Design, Ninth Edition
,'%$#SS .2.1: ,&',%S#: *!,&T DT F)%ES: %&T,&T DT F)%ES: ,'%$#SS 1.-: ,&',%S#:
*!,&T DT F)%ES: %&T,&T DT F)%ES: ,'%$#SS 1.2: ,&',%S#:
*!,&T DT F)%ES: %&T,&T DT F)%ES: ,'%$#SS 1.: ,&',%S#:
*!,&T DT F)%ES: %&T,&T DT F)%ES: ,'%$#SS 1.1: ,&',%S#: *!,&T DT F)%ES: %&T,&T DT F)%ES:
Page 25 of 48
$'#T# STT#M#!T ,repare and print monthly statements to patients STT#M#!T DT STT#M#!T M%D*F9 ,T*#!T dd/ change/ and delete patient and household data recei3ed from patients ,T*#!T $(!"# ,T*#!T &,DT# M%D*F9 (%&S#(%)D dd/ change/ and delete household data changes recei3ed from patients (%&S#(%)D $(!"# (%&S#(%)D &,DT# M%D*F9 *!S&'!$# $''*#'S dd/ change/ and delete insurance carrier data recei3ed from patients #M,)%9#' $(!"# #M,)%9#' &,DT# M%D*F9 ,'%@*D#' dd/ change/ and delete pro3ider data ,'%@*D#' $(!"# ,'%@*D#' &,DT#
Systems Analysis and Design, Ninth Edition
Page 28 of 48
Pe"sona$ "aine", nc 1( Prepare a +ontet diagram for the ne* system( Sample context diagram: ACTIVITY
REQUEST ACTIVITY
DATA INVOICE MEMBER
ACTIVITY PAYMENT
CONFIRM ACTIVITY REQUEST
ACCOUNTING 0
ASSIGNED
PERSONAL
ACTIVITY
TRAINER
REPORTS
TREND
INFORMATION INSTRUCTOR
REPORTS
MANAGER
MANAGEMENT CONFIRM
SYSTEM
SCHEDULE
AVAILABILITY
DECISIONS
CHARGE ACCOUNTING RESULTS
TREND DATA
AND PAYMENT DATA
PERSONAL TRAINER ACCOUNTING SYSTEM
.( Prepare a diagram - D!D for the ne* system( nswers will 3ary. *n $hapter 1/ students were as=ed to draw an FDD showing the main operations described in the fact statement. nswers will 3ary/ but the obBecti3e is to ha3e students identify three to fi3e functions that will represent maBor business processes. The sample FDD in $hapter 1 identified four primary functions: M!"# M#M;#'S(*, !D $('"#S *!T#'F$# E*T( $$%&!T*!" S9ST#M S$(#D&)# $%&'S#S !D $T*@*T*#S !)9J# S)#S !D M'A#T*!" T'#!DS These four functions can be represented as processes when the context diagram is exploded to diagram 0 DFD.
Systems Analysis and Design, Ninth Edition
Page 2; of 48
Sample diagram 0 DFD: 1
2
ACCOUNTING
M ANAGE PAYMENT
ACCOUNTING
INTERFACE
DATA
M EMBERSHIP
RESULTS
WITH
AND
ACCOUNTING
CHARGES
SYSTEM
TRAINER CHARGE AND PAYM ENT DATA
MEMBER INVOICE
MEMBER
PERSONAL ACCOUNTING SYSTEM TREND
DATA
4
REQUEST ACTIVITY
DATA
ANALYZE D2
MEMBER
SALES AND
DATA
M ARKETING
CONFIRM
TRENDS
ACTIVITY REQUEST
TREND REPORTS
3
ACCOUNTING CURRENT D1
SCHEDULE
COURSES
SCHEDULE
SCHEDULE DECISIONS
AND ACTIVITIES
DATA
MANAGER
REPORTS
SCHEDULE
ACTIVITY DATA
ACTIVITY D3
ACTIVITY
DATA
DATA CONFIRM AVAILABILITY
INSTRUCTOR
ASSIGNED ACTIVITY
ACTIVITY
2( ue that maintains consistency among a set of DFDs by ensuring that input and output data flows align properly.
Systems Analysis and Design, Ninth Edition
Page 4- of 48
ANSWERS TO CHAPTER CAPSTONE CASE: S O$TWEAR % LIMITED &SWL' Suppose that you are working with Rick and Carla when a new systems request comes in. SWL’s vice president of marketing, Amy Neal, wants to change the catalog mailing program and provide a reward for customers who use the Internet. Amy’s plan specifies that customers will remain on SWL’s mailing list if they either requested a catalog, ordered from SWL in the last two years, or signed the guest register on SWL’s new Web site. To encourage Internet visitors, customers who register on the Web site also will receive a special discount certificate. To document the requirements, Rick wants you to design a decision table. Initially, it appears to have eight rules, but you notice that some of those rules are duplicates, or might not be realistic combinations.
1( Design the de+ision ta6le *ith all possi6ilities( The three separate conditions should produce a total of eight possible rules/ and the table should loo= something li=e the following example: F&ES
1
.
2
4
3
5
8
e7uested a +atalog
:
:
:
:
N
N
N
N
$rdered in past t*o years
:
:
N
N
:
:
N
N
Signed
:
N
:
N
:
N
:
N
emain on mailing list
J
J
J
J
J
J
J
e+ei/e +ertifi+ate
J
J
J
J
.( Simplify the ta6le 6y +om6ining rules *here appropriate( !ow the rules can be simplified by considering the following: a. *f a customer registers on the Eeb site/ as in 'ules -/ / 4/ and 6/ he or she stays on the mailing list and gets the discount certificate. *n this situation/ the other two con ditions do not really matter. b. *f a customer did not register on the Eeb/ then it does matter whether they fulfilled the other conditions. *n 'ules 2 and 1/ the catalog re>uest was present and the 2year rule does not matter. *n 'ule 5/ the 2year rule was fulfilled and the catalog re>uest does not matter. c. *f none of the conditions is fulfilled/ as in 'ule 7/ the customer is remo3ed from the mailing list and does not recei3e the discount certificate. The following table shows the simplification Bust described:
Systems Analysis and Design, Ninth Edition
Page 41 of 48
F&ES
1
.
2
4
3
5
8
e7uested a +atalog
:
:
N
$rdered in past t*o years
:
N
Signed
:
N
:
N
:
N
:
N
emain on mailing list
J
J
J
J
J
J
e+ei/e +ertifi+ate
J
J
J
J
Finally/ based on the analysis described in Step 2/ the original eight rules can be combined into Bust four rules/ as follows: F&ES
1
.
2
4
e7uested a +atalog
:
N
$rdered in past t*o years
:
N
Signed
:
N
N
N
emain on mailing list
J
J
J
e+ei/e +ertifi+ate
J
2( Dra* a de+ision tree that refle+ts Amy NealBs poli+y( &sing the same logic/ the decision tree will produce the four rules shown in the final 3ersion of the decision table. The layout of the tree will 3ary depending on which co ndition is depicted first. The simplest solution is to start with the Eeb site condition/ as follows:
Systems Analysis and Design, Ninth Edition
Page 4. of 48 Re(a"n )n (a""n* "+t an, re#e"e #ert"."#ate
S"*ne, We/ +"te re*"+ter
D", n)t +"*n re*"+ter
Re0ue+te, a #ata)*
Or,ere, "n 1a+t tw) year+ D", n)t re0ue+t a #ata)*
D", n)t )r,er "n 1a+t tw) year+
Re(a"n )n (a""n* "+t
Re(a"n )n (a""n* "+t
Re()e .r)( (a""n* "+t
4( Create a set of stru+tured English statements that a++urately des+ri6es the poli+y( Students should re3iew the example in Figure 4 on page 224 and use their imagination for this assignment. #xplain that the obBecti3e is to come up with a reasonable example of structured #nglish H not a detailed process description. sample solution might loo= li=e the following:
For each CUSTOMER If REGISTERED ON WEB SITE Else If CATALOG REQUESTED or ORDERED IN 2 YEARS Else Remoe from ma!l!"# l!s$ Rema!" o" ma!l!"# l!s$ Rema!" o" ma!l!"# l!s$ a"% rece!e cer$!&ca$e
Systems Analysis and Design, Ninth Edition
Page 42 of 48
Mana*e t!e SWL Pr)2e#t :ou ha/e 6een as=ed to manage S<&Bs ne* information system pro>e+t( $ne of your most important a+ti/ities *ill 6e to identify pro>e+t tas=s and determine *hen the y *ill 6e performed( 9efore you 6egin, you should re/ie* the S<& +ase in this +hapter( Then list and analyKe the tas=s, as follo*s? LIST THE TASKS Start 6y listing and num6ering at least ten tas=s that the S<& team needs to perform to fulfill the o6>e+ti/es of this +hapter( :our list +an in+lude S<& Team Tas=s and any other tas=s that are des+ri6ed in this +hapter( !or eample, Tas= 2 might 6e to "dentify the system entities, and Tas= might 6e to Dra* a +ontet diagram( n answer might include tas=s listed in the $hapter *ntroduction $ase/ and other examples of tas=s found in the SE) case or elsewhere in the chapter. sample answer follows: as +ist • )earn how to use data flow diagrams/ data dictionaries/ and process description tools • )earn how to use the four main DFD symbols • &nderstand le3eling and balancing concepts • $reate a data dictionary that will document the DFDs • $reate a context diagram • $reate a diagram 0 DFD • $reate lowerle3el diagrams • $hec= to assure that all DFDs are le3eled and balanced • Describe all processes using structured #nglish/ decision tables and decision trees • $omplete a logical data and process model of the system ANALY3E THE TASKS No* study the tas=s to determine the order in *hi+h they should 6e performed( !irst identify all +on+urrent tas=s, *hi+h are not dependent on other tas=s( "n the eample sho*n in !igure 345, Tas=s 1, ., 2, 4, and 3 are +on+urrent tas=s, and +ould 6egin at the same time if resour+es *ere a/aila6le( $ther tas=s are +alled dependent tas=s, 6e+ause they +annot 6e performed until one or more earlier tas=s ha/e 6een +ompleted( !or ea+h dependent tas=, you must identify spe+ifi+ tas=s that need to 6e +ompleted 6efore this tas= +an 6egin( !or eample, you *ould *ant to identify the system entities 6efore you +ould dra* a +ontet diagram, so Tas= +annot 6egin until Tas= 2 is +ompleted, as !igure 345 sho*s(
nswers will 3ary. sample answer follows: %oncu""ent ass -. )earn how to use data flow diagrams/ data dictionaries/ and process description tools 2. )earn how to use the four main DFD symbols . &nderstand le3eling and balancing concepts
De!enent ass 1. $reate a data dictionary that will document the DFDs
4. $reate a context diagram 5. $reate a diagram 0 DFD
Systems Analysis and Design, Ninth Edition
Page 44 of 48 6. $reate lowerle3el diagrams 7. $hec= to assure that all DFDs are le3eled and balanced G. Describe all processes using structured #nglish/ decision tables/ and decision trees -0. $omplete a logical data and process model of the system
For each dependent tas=/ a sample list of predecessor tas=s follows: De!enent ass 1. $reate a data dictionary that will document the DFDs 4. $reate a context diagram 5. $reate a diagram 0 DFD 6. $reate lowerle3el diagrams 7. $hec= to assure that all DFDs are le3eled and balanced G. Describe all processes using structured #nglish/ decision tables/ and decision trees -0. $omplete a logical data and process model of the system
P"eecesso" ass 1,.,2
4 3 5 8 ;
Chapter 2 des+ri6es pro>e+t management tools, te+hni7ues, and soft*are( To learn more, you +an /isit the !eatures se+tion on your Student Study Tool CD$%, or /isit the %anagement "nformation Systems Course%ate e+t management resour+es li6rary for this 6oo=( $n the e+t .-1-( :ou also +an /isit the $pen
Systems Analysis and Design, Ninth Edition
Page 43 of 48
ANSWERS TO READY $OR A CHALLENGE In+tru#t)r N)te: 'emind students that to 3iew sample answers to ,ractice Tas=s/ they can 3isit the Management *nformation Systems $ourseMate Eeb site at www.cengagebrain.com / na3igate to the resources for this chapter/ and locate 'eady for a $hallenge.
Systems Analysis and Design, Ninth Edition
Page 4 of 48
Systems Analysis and Design, Ninth Edition
A( Dra* a +ontet diagram for the ne* C5 system that sho*s the re/ised design(
Page 45 of 48
