" The Systems Analyst isthe key person inthe development of information systems. Selecting the Appropriate "= The ystems Development ifeycle consists of four Development Methodology stages: Planning Analysis, Design, and Implementation. ™ Project Identification and Initiation recognize a business need that canbe satisfied through the use of information ‘technology. * System Request describes the business value for an information stem * AFeasiblity Analysis suse to provide more detall about ‘the risks associated with the proposed system. * Arequirement isa statement of what the system must do or what characteristics it needs tohave. " Requirements describe =" what the business needs (business requirements) thatthe sas nes ose requrements) ‘what the software should do (unctionat requirements) ~ characteristics the system should have (non-functional requirements), and ~ how the system should be built toate sa chien Comparison of Requirements Elicitation Techniques Inte Stepney laf | | iM Fennec teil De ee lil citi | Atoeeoaeeecentes indir ||| Sienerecabelclealan elem ina Hi i] 1 i f iDEVELOPING AN ALTERNATIVE MATI ternative matrix combines several feasibility analyses inte one matrix, for each system = the + Itcontains technical, economical and organizational feasibillt cendidate, pros and cons, and other information. slong the aid + Sometimes, weights and scores are added to create a weighted = The score assigned ia a subjective assignment. Iternative matrix. ch clesign(acenario) ‘ches vicar ‘Special hare, sowere, ofl nate The syn vel sk ot the Wes ‘Requrement Tecpremets imposed y busines raquierert: eriecper sh Pere Explore + Al cfc Ketone wil bas an ainayson at ‘wotkcomecion to anche ncn actos ote Kaa be en lb rnd rr pee seer el aioe metres Jom eng i ri i eee Sagat Sfunse sah arg Eeaipaadlees Te ped end we te nan Decrease onlin tore Permit Regions The om och tego wl med =e The mammes to sewer ane eens Rare ert aoe Teper ay nds wi tld pacers ett eced bangiscorge owiehe Me sami abe gee moe fn ey es ct Se eames sare a Soce Sie enn barbed Som FIGURE 8-6 osetinl Reens Peformance RequirementsClient-Server Architectures * cient server architectures balance the Security Requirements processing between cient devices and one or more server devices * The cients responsible forthe presentation logic whereas te server is responsible forthe data access ogi and data storage * Aihick or fat client contains all or most of pplication logic; whereas 3 thin client contains a small portion ofthe application logic Speed Requirements gee ote Capacity Requirements fequiremons ‘Availabilty and Reliability “wee Recwaretvent The interlace should be @ series of areas on the screen that are used moniter tor differect, purposes for encrnpie, top ones Ror comments Gnd navigation, @ middla Grea for informanén fo be input or Ouiput, and @ Boner area for status information: Content awareness Users should always be aware of where they ate In the system and what information is being displayed. Interfaces should be functional and! inviting to users trough careful use of white space, colrs, Gnd fonts, There ts ohen a Nadel! bowen including Though whe space lo moka the interlace look plsosing ond losing 50. Much space that important information cows nat ian the scresn, User experince __Alnough ease of use ond saws of loaning fen load! simi dasign infroauer’ wears of seftparo wil Tnoler vow Shlouming, whowes hequon” teers wil preter ease of = m” Acuthet Consistency ‘Cinalstency in irterioce design enobias users to predict whot wil happen: Bolore Roy porionn @ xc, We ona the rhest Important elon ects of letuning, wase Of use, end Gosthetien Minieiai:iaetafiont The intectow should be slimes to use, Meal chasis pln eave Tier heey etew eee Neen aetna sone eae + The user interface dasign proce: = Use scenario development, interface structure design, interface standards, design, interface design prototyping, and interface evaluation + Navigation design = The fundamental goal of navigation design is to make the system as simple to use as possible, + Input design ~The goal of input design is to simply and easily capture accurate information for the system. + Output design = The geal of the output design is to present information te users so that they can accurately understand it with the least effort.