Chapter 1 Review Questions
1. The diference between an inormation system and a computer application is that an ino system can include sotware, database, and manual related processes. Whereas, Whereas, a computer application includes only the computer sotware. 2. The purpose o systems analysis is to describe in detail the what! that a system must do to satisy the need or to solve the problem. The systems analysis is important because it provides details on all the unctions o a system. "ssentially, it allows the individual to understand and speciy what a system is doin# or what it should do. $. The diference between systems analysis and systems desi#n is that systems analysis deals with what a sotware system should accomplish and systems desi#n deals with how the system s ystem will accomplish the end result. %aid diferently, the systems desi#n deals with solvin# the systems problem whereas the systems analysis deals with what the end #oal #oa l o the new system should be. &. ' pro(ect is a planned underta)in# that has a be#innin# and an end, and that produces some de*nite result. +. The processes or sotware systems development are /dentiy the problem or need and obtain approval to proceed. 0lan and monitor the pro(ect. What to do, how to do it, and who does it 3iscover and understand the details o the problem or the need. 3esi#n the system components that solve the problem or satisy the need. 4uild, test, and inte#rate the systems components. Complete systems tests and deploy the solution. . '#ile development reers to an inormation systems development process process that emphasi5es 6e7ibility to anticipate new re8uirements durin# development. '#ile development development embraces the act that no one )nows all a ll the problems thereore thereore the way you #o about developin# the product is throu#h a#ile development where chan#es are ta)en into account once they are reali5ed. 9ence the 6e7ibility aspect o a#ile development. :. The purpose o a systems vision document is to identiy the bene*ts and capabilities included with in the systems. The speci*c document contains a product description, a list o the systems capabilities, and a list o the businesses bene*ts #ained by the new system.
Chapter 1 Review Questions
;. 4y de*nition a subsystem is an identi*able and partitioned portion o an overall system. The system is the entire sotware pro#ram i you will. The system is described in detail throu#h the system capabilities in the systems vision document. The subsystems are derived rom the systems capabilities in the systems vision document. What the subsystems do is they cate#ori5e the systems capabilities into chun)s. assi#n the proper people to them. 1?. The components o the wor) brea)down structure W4% are as ollows 3iscover and understand the details o the all aspects o the problem. 3esi#n the components o the solution to the problem. 4uild the components and inte#rate everythin# into the solution. 0erorm all systems level tests and deploy the solution. 11. 4y de*nition a use case is a methodolo#y used in system analysis to identiy, clariy, and or#ani5e system re8uirements. The inormation that a use case dia#ram provides is as ollows The boundary, which de*nes the system o interest in relation to the world around it The employees, usually individuals involved with the system are de*ned accordin# to their roles The use cases, which are the speci*c roles played by the employees within and around the system The relationships between and amon# the employees and the use cases 12. ' class dia#ram provides inormation about classes, their attributes and their relationships. "ssentially, a class dia#ram ta)es the ob(ect class which is the thin#s in the real world that the system needs to )now and @the class dia#ramA e7amines the relationship between each ob(ect class in a visual manner.
Chapter 1 Review Questions
1$. The use case dia#ram involves the business o the pro(ect and shows who will utili5e the system and the use case dia#ram also shows what services the pro#ram provides. Bor e7ample, the use case would in relation to how the user will #o about unctionin# the system.
Chapter 1 Review Questions
Brom here you either *nd more errors and report them or you are done #iven that you *7ed all the errors. 1=. The purpose o user acceptance testin# is to have the user test the system in order to determine the correctness o the system and to test its *tness to accomplish the business re8uirements. 2?. 3ividin# your pro(ect into separate iterations is a #ood idea because it enables you to incrementally deliver capabilities such as an e7ecutable, usable subset o implemented and tested re8uirements that can be assessed by sta)eholders at the end o each iteration. This provides rapid and timely eedbac) loops, so that issues can be addressed and improvements made at a lower cost. 'lso, this is accomplished while you still have suEcient bud#et and time let to do so, and you have not #one so ar ahead that ma(or rewor) is re8uired. 21. The #oal with iteration plannin# is to establish a ew hi#hlevel ob(ectives or what to accomplish durin# the iteration, produce a suEciently detailed plan outlinin# who needs to do what to accomplish those ob(ectives, and de*ne how to assess that you accomplished what you set out to accomplish.
