Chapter 1
EOC Questions
CHAPTER 1 Introduction to Systems Analysis and Design.
1. Compare Compare and and contrast contrast phases, steps, techniues techniues and and deli!era"l deli!era"les. es.
The Systems Development Life Cycle “SDLC” has a set of four fundamental phases: plannin! analysis! desin! and implementation" Different pro#ects may emphasi$e different parts of the SDLC or approach the SDLC phases in different %ays! &ut all pro#ects have elements of these four phases" Each phase is itself composed of a series of steps! %hich rely upon techni'ues that produce delivera&les (specific documents and files that provide understandin a&out the pro#ect)" Example: Example: *hen you apply for admission to a university! there are several phases that all students o throuh: information atherin! applyin! and acceptin" Each of these phases has steps+information atherin includes steps li,e searchin for schools! re'uestin re'uestin information! information! and readin readin &rochures" &rochures" Students then use techni'ues techni'ues (e""! -nternet searchin) that can &e applied to steps (e""! re'uestin information) to create delivera&les (e""! evaluations of o f different aspects of universities)"
#. Descri"e Descri"e the ma$or ma$or phases phases in the systems systems de!elopmen de!elopmentt li%e cycle cycle &SD'C(. &SD'C(. There are four ma#or phases in SDLC"
a) .lanni .lannin: n: The .lannin .lannin phase is the fundam fundament ental al process process of understa understandi ndin n %hy an information system should &e &uilt and determinin ho% the pro#ect team %ill o a&out &uildin it" &) /nalysis: The /nalysis phase ans%ers the 'uestions of %ho %ill use the system! %hat the system %ill do! and %here and %hen it %ill &e used" Durin this this phase! phase! the pro#ec pro#ectt team team invest investia iates tes any curren currentt system system(s) (s)!! identi identifi fies es improvement opportunities! and develops a concept for the ne% system" c) Desin Desin:: The desi desin n phase phase decides decides ho% ho% the syste system m %ill oper operate ate!! in terms terms of the hard%are! hard%are! soft%are! soft%are! and net%or, net%or, infrastru infrastructure0 cture0 the user interface! interface! forms forms and report reports0 s0 and the specif specific ic prora prorams! ms! data&ases data&ases!! and files files that that %ill %ill &e needed" d) -mplem -mplementa entatio tion: n: The final final phase in the SDLC SDLC is the implemen implementat tation ion phase! phase! durin %hich the system is actually &uilt (or purchased! in the case of a pac,aed soft%are desin)" This is the phase that usually ets the most attention! &ecause for most systems it is lonest and most epensive sinle part of the development process"
.ae 1
Chapter 1
EOC Questions
). Descri"e the principal steps in the planning phase. *hat are the ma$or deli!era"les
The plannin phase is the fundamental process of understandin %hy an information system should &e &uilt and determinin ho% the pro#ect team %ill o a&out &uildin it" -t has t%o steps: 1" .ro#ect -nitiation: This step involves the identification of the system2s &usiness value" / s ystem request presents a &rief summary of a &usiness need! and it eplains ho% a system that supports the need %ill create &usiness value" The -S department %or,s toether %ith the person or department that enerated the re'uest (called the project sponsor ) to conduct a feasi&ility analysis" The feasibility analysis eamines ,ey aspects of the proposed pro#ect li,e the technical feasi&ility! economic feasi&ility and orani$ational feasi&ility 3" .ro#ect 4anaement: Once the pro#ect is approved! it enters+pro#ect manaement" Durin pro#ect manaement! the pro#ect manaer creates a %or, plan! staffs the pro#ect! and puts techni'ues in place to help the pro#ect team control and direct the pro#ect throuh the entire SDLC" The delivera&le for pro#ect manaement is a pro#ect plan that descri&es ho% the pro#ect team %ill o a&out developin the system"
+.
Descri"e the principal steps in the analysis phase. *hat are the ma$or deli!era"les
The analysis phase ans%ers the 'uestions of %ho %ill use the system! %hat the system %ill do! and %here and %hen it %ill &e used" Durin this phase! the pro#ect team investiates any current system(s)! identifies improvement opportunities! and develops a concept for the ne% system" This phase has three steps: 1" /nalysis Stratey: Developed to uide the pro#ect team2s efforts" Such a stratey usually includes an analysis of the current system (as5is system) and its pro&lems! and then %ays to desin a ne% system (to5&e system)" 3" 6e'uirements 7atherin: The analysis of this information+in con#unction %ith input from pro#ect sponsor and many other people+leads to the development of a concept for a ne% system" The system concept is then used as a &asis to develop a set of &usiness analysis models that descri&es ho% the &usiness %ill operate if the ne% system %ere developed" 8" System .roposal: The analyses! system concept! and models are com&ined into a document called the system proposal , %hich is presented to the pro#ect sponsor and other ,ey decision ma,ers"
.ae 3
Chapter 1
EOC Questions
The system proposal is the initial delivera&le that descri&es %hat &usiness re'uirements the ne% system should meet" This is really the first step in the desin of the ne% system"
-. Descri"e the principal steps in the design phase. *hat are the ma$or deli!era"les
The desin phase decides ho% the system %ill operate! in terms of the hard%are! soft%are and net%or, infrastructure0 the user interface! forms and reports0 and the specific prorams! data&ases! and files that %ill &e needed" The desin phase has four steps: 1" Developin desin stratey: This clarifies %hether the system %ill &e developed &y the company2s o%n prorammers! %hether it %ill &e outsourced to another firm (usually a consultin firm)! or %hether the company %ill &uy an eistin soft%are pac,ae" 3" 9asic architecture desin: This descri&es the hard%are! soft%are! and net%or, infrastructure that %ill &e used" -n most cases! the system %ill add or chane the infrastructure that already eists in the orani$ation" 8" Data&ase and file specifications: These define eactly %hat data %ill &e stored and %here they %ill &e stored" " .roram Desin: The analyst team develops the proram desin! %hich defines the prorams that need to &e %ritten and eactly %hat each proram %ill do" This collection of delivera&les (architecture desin! interface desin! data&ase and file specifications! and proram desin) is the system specification that is handed to the prorammin team for implementation" /t the end of the desin phase! the feasi&ility analysis and pro#ect plan are reeamined and revised! and another decision is made &y the pro#ect sponsor and approval committee a&out %hether to terminate the pro#ect or continue"
. Descri"e the principal steps in the implementation phase. *hat are the ma$or deli!era"les
The final phase in the SDLC is the implementation phase! durin %hich the system is actually &uilt (or purchased! in the case of a pac,aed soft%are desin)" This phase has three steps:
.ae 8
Chapter 1
EOC Questions
1" System construction: The system is &uilt and tested to ensure it performs as desined" Since the cost of &us can &e immense! testin is one of the most critical steps in implementation" 3" -nstallation: This is the process &y %hich the old system is turned off and the ne% one is turned on" -t may include a direct cutover approach! a parallel conversion approach! or a phased conversion stratey" 8" Support plan: This plan usually includes a formal or informal post5 implementation revie%! as %ell as a systematic %ay for identifyin ma#or and minor chanes needed for the system"
/. *hat are the roles o% a pro$ect sponsor and the appro!al committee
.ro#ect sponsor: .ro#ect Sponsor could &e represented either &y an individual or a department or a team" The pro#ect sponsor is from %here the re'uest is enerated" They are &asically involved throuh out the various phases of the SDLC" a" The -S department %or,s hand in hand %ith the pro#ect sponsor to conduct a feasi&ility analysis! &e it a technical! orani$ational or an economical feasi&ility" &" Durin the /nalysis phase the pro#ect team investiates any current system! identifies improvement opportunities and develops a concept for the ne% system in con#unction %ith the input from the pro#ect sponsor" c" /t the end of the desin phase the feasi&ility analysis and the pro#ect plan are reeamined and revised and the decision %hether the pro#ect is to continue or terminated is made &y the pro#ect sponsor alon %ith the approval committee" d" The ,ey delivera&les for each phase are typically very lon and are presented to the pro#ect sponsor for approval as the pro#ect moves from phase to phase" e" The pro#ect sponsor approves the ,ey delivera&les for each phase only after %hich the pro#ect moves from phase to phase" f" The pro#ect sponsor alon %ith the users provides valua&le comments %hich are used to re5analy$e! re5desin and re5implement a second prototype %hich provides fe% more features"
.ae
Chapter 1
EOC Questions
/pproval Committee: Sometimes referred to as the steerin committee is the final decision ma,er reardin the fate of the pro#ect after carefully revie%in the system re'uest! feasi&ility analysis! system proposal etc" a) -n plannin phase after feasi&ility analysis the approval committee decides %hether the pro#ect should &e underta,en" &) /fter /nalysis the system proposal is for%arded to the approval committee to decide %hether the pro#ect should continue to move for%ard c) Durin the Desin phase the feasi&ility analysis and pro#ect plan are reeamined and the approval committee %ill decide %hether to terminate or continue %ith the pro#ect
0. *hat does gradual re%inement mean in contet o% SD'C
7enerally! the clarity of understandin and the depth of detail of the ne% system are radually refined durin the phases of the SDLC" -nitially! the re'uirements are only vauely understood" This understandin is improved durin the /nalysis phase" ;urther detail is developed durin Desin! and then is fully epressed durin -mplementation"
2. Compare and contrast process3centered methodologies 4ith data3centered methodologies.
.rocess5centered methodoloies: .rocess5centered methodoloies emphasi$e process models as the core of the system concept" Example: .rocess5centered methodoloies %ould focus first on definin the processes (e""! assem&le sand%ich inredients)" Data5centered methodoloies5 Data5centered methodoloies emphasi$e data models as the core of the system concept" Example: Data centered methodoloies %ould focus first on definin the contents of the storae areas (e""! refrierator) and ho% the contents %ere orani$ed"
16.
Compare and contrast structured3design "ased methodologies in general to RAD3"ased methodologies in general.
Structured desin methodoloies are usually fairly formal! step5&y5step approaches to systems development" The pro#ect moves throuh the phases in a systematic %ay" The emphasis in most of these methodoloies is development of paper5&ased specifications for the ne% system prior to implementation" 6/D methodoloies! on the other hand! tend to emphasi$e 'uic, creation of a limited5capa&ility version of the
.ae <
Chapter 1
EOC Questions
system or a model of the system" These methodoloies focus on refinin this preliminary system or model rather than tryin to fully descri&e it on paper prior to implementation"
11.
Compare and contrast etreme programming and thro4a4ay prototyping.
Etreme prorammin (=.): Etreme .rorammin is founded on four core values %hich provide a foundation on %hich =. developers use to create any system" The four core values are Communication! Simplicity! ;eed&ac, and Courae" Thro%a%ay .rototypin: Thro%a%ay prototypin5&ased methodoloies &alance the &enefits of %ell thouht out analysis and desin phases %ith the advantaes of usin prototypes to refine ,ey issues &efore a system is &uilt" Each of these issues is eamined &y analy$in! desinin! and &uildin a desin prototype"
1#.
Descri"e the ma$or elements and issues 4ith 4ater%all de!elopment.
*aterfall Development follo%s the phases of the life cycle in se'uence (.lannin! /nalysis! Desin! and -mplementation)" Each phase is thorouhly documented and approval is re'uired &efore proceedin to the su&se'uent phase" -t is difficult! thouh not impossi&le! to o &ac,%ards in the SDLC under *aterfall Development" *aterfall Development re'uires that the system re'uirements &e precisely specified prior to implementation and also often >free$es> those re'uirements durin development" The hih deree of effort devoted to specifyin user re'uirements is a strenth of *aterfall Development &ut specifyin those re'uirements on paper is la&orious and may lead to errors and omissions" >;ree$in> the re'uirements durin development helps assure that the system is developed accordin to specifications! &ut in a dynamic &usiness environment! the system that is ultimately developed may &ear little resem&lance to %hat is actually needed at the time the pro#ect is completed" Therefore! etensive maintenance may &e needed after implementation to revise the system to meet current conditions" The t%o ,ey advantaes of the structured desin %aterfall approach are that: • •
-t identifies system re'uirements lon &efore prorammin &eins -t minimi$es chanes to the re'uirements as the p ro#ect proceeds"
The t%o ,ey disadvantaes are that: a" The desin must &e completely specified &efore prorammin &eins" &" / lon time elapses &et%een the completion of the system proposal in the analysis phase and the delivery of the system"
.ae ?
Chapter 1
EOC Questions
1). Descri"e the ma$or elements and issues 4ith parallel de!elopment
The parallel development methodoloy attempts to address the pro&lem of lon delays &et%een the analysis phase and the delivery of the system" -nstead of doin desin and implementation in se'uence! it performs a eneral desin for the %hole system and then divides the pro#ect into a series of distinct su&pro#ects that can &e desined and implemented in parallel" Once all su&pro#ects are complete! there is a final interation of the separate pieces! and the system is delivered The ma#or issues in this approach are that it still suffers from pro&lems caused &y paper documents" -t also adds a ne% pro&lem such as sometimes the su&pro#ects are not completely independent0 desin decisions made in one su&pro#ect may affect another! and the end of the pro#ect may re'uire sinificant interation efforts"
1+. Descri"e the ma$or elements and issues 4ith phased de!elopment.
.hased Development is a 6/D methodoloy that does not attempt to develop the complete system initially" -nstead! the system is enerally specified" @ser re'uirements are orani$ed into a series of versions" The first version includes the essential system components and is delivered to the users 'uic,ly" Su&se'uent versions add features and refinements to the system &ased on the initial specification plus the usersA feed&ac, and reaction to usin the system" The critical issue %ith .hased Development is to accurately specify the initial re'uirements so that the first version provided to the users is useful! althouh incomplete" -f this is done %ell! .hased Development %ill provide value to the orani$ation &y ettin the users a system to use 'uic,ly" Be% re'uirements may &e identified throuh user feed&ac, as %ell! %hich improves the >fit> of the system to the &usiness needs"
1-. Descri"e the ma$or elements and issues 4ith prototyping.
/ prototypin5&ased methodoloy performs the analysis! desin! and implementation phases concurrently! and all three phases are performed repeatedly in a cycle until the system is completed" .rototype is usually the first part of the system that the user %ill use and the ,ey advantae of a prototypin5&ased methodoloy is that it very 'uic,ly provides a system for the users to interact %ith! even if it is not ready for %idespread orani$ational use at first" The ma#or pro&lem %ith prototypin is that its fast5paced system releases challene attempts to conduct careful! methodical analysis" Often the prototype underoes such sinificant chanes that many initial desin decisions &ecome poor ones" This can
.ae
Chapter 1
EOC Questions
cause pro&lems in the development of comple systems &ecause fundamental issues and pro&lems are not reconi$ed until %ell into the development process" Example: -maine &uildin a car and discoverin late in the prototypin process that you have to ta,e the %hole enine out to chane the oil (&ecause no one thouht a&out the need to chane the oil until after it had &een driven 1! miles)" 1. Descri"e the ma$or elements and issues 4ith thro4a4ay3prototyping.
-n thro%5a%ay prototypin! there is a more careful and riorous analysis performed as compared to .rototypin (more similar to the traditional SDLC)" o%ever! in the Desin phase! models of various elements of the system are developed to help eplore desin alternatives and refine system re'uirements" These prototypes help users clarify their needs! options! and priorities" Once user re'uirements are esta&lished throuh reaction to the desin prototype! it is discarded0 ho%ever! the re'uirements it em&odied are incorporated into the ne% system" Thro%5a%ay prototypin is very useful in situations %here users are uncertain a&out ,ey elements of the system" Thro%5a%ay prototypes can help focus users on desin issues and improve understandin of &usiness needs" The approach helps create a system that suits the users needs even thouh those needs may have &een poorly understood initially"
1/. Descri"e the ma$or elements and issues 4ith 7P.
Etreme prorammin (=.) is founded on four core values: communication! simplicity! feed&ac,! and courae" These four values provide a foundation that =. developers use to create any system" ;irst! the developers must provide rapid feed&ac, to the end users on a continuous &asis" Second! =. re'uires developers to follo% the F-SS principle"G Third! developers must ma,e incremental chanes to ro% the system! and they must not only accept chane! they must em&race chane" ;ourth! developers must have a 'uality5first mentality" =. also supports team mem&ers in developin their o%n s,ills" Three of the ,ey principles that =. uses to create successful systems are continuous testin! simple codin performed &y pairs of developers! and close interactions %ith end users to &uild systems very 'uic,ly" ;or small pro#ects %ith hihly motivated! cohesive! sta&le! and eperienced teams! =. should %or, #ust fine" o%ever! if the pro#ect is not small or the teams aren2t #elled! then the success of an =. development effort is dou&tful" This tends to thro% the %hole idea of &rinin outside contractors into an eistin team environment usin =. into dou&t" 10. Descri"e the ma$or elements and issues 4ith SCR89.
.ae G
Chapter 1
EOC Questions
Scrum development focuses on a fe% ,ey practices" ;irst! teams are self5orani$ed and selfdirected" @nli,e other approaches! Scrum teams do not have a desinated team leader" -nstead! teams orani$e themselves in a sym&iotic manner and set their o%n oals for each sprint (iteration)" Second! once a sprint has &eun! Scrum teams do not consider any additional re'uirements" /ny ne% re'uirements that are uncovered are placed on a &ac,lo of re'uirements that still need to &e addressed" Third! at the &einnin of every %or,day! a Scrum meetin ta,es place" ;ourth! at the end of each sprint! the team demonstrates the soft%are to the client" 9ased on the results of the sprint! a ne% plan is &eun for the net sprint" One of the ma#or criticisms of Scrum! li,e all aile methodoloies! is that it is 'uestiona&le %hether Scrum can scale up to develop very lare! mission5critical systems" / typical Scrum team si$e is no more than seven mem&ers" 12. *hat are the :ey %actors in selecting a methodology
There are several factors that influence the choice of a methodoloy: • • • • • •
Clarity of the user re'uirements ;amiliarity %ith the &ase technoloy System compleity Beed for system relia&ility Time pressures H Beed to see proress on the time schedule"
#6. *hat are the ma$or roles played "y a systems analyst on a pro$ect team / System /nalysts role is to: • • • •
-dentifyin ho% technoloy can improve &usiness processes Desinin the ne% &usiness processes Desinin the information system Ensurin that the system conforms to information systems standards
#1. Compare and contrast the role o% a systems analyst, "usiness analyst, and in%rastructure analyst.
These three roles emphasi$e different perspectives on the system" The &usiness analyst represents the sponsorIusers interests! %hile the systems analyst ,no%s ho% to apply -S to support &usiness needs" Toether! the systems analyst and the &usiness analyst can desin a system that conforms to the -S standards %hile addin value to the &usiness" The infrastructure analyst has more technical ,no%lede and provides the team %ith technical constraints! or identifies infrastructure chanes that the ne% system %ill re'uire"
.ae J
Chapter 1
EOC Questions
System /nalyst: / System /nalysts role is to: • • • •
-dentifyin ho% technoloy can improve &usiness processes Desinin the ne% &usiness processes Desinin the information system Ensurin that the system conforms to information systems standards
9usiness /nalyst: / 9usiness /nalyst2s role is to: • • •
/naly$in the ,ey &usiness aspects of the system -dentifyin ho% the system %ill provide &usiness value Desinin the ne% &usiness processes and policies
-nfrastructure /nalyst: The -nfrastructure /nalyst2s role is to: • •
Ensurin the system conforms to infrastructure standards -dentifyin infrastructure chanes needed to support the system
##. *hat is the di%%erence "et4een classes and o"$ects / class is the eneral template %e use to define and create specific instances! or o&#ects" Every o&#ect is associated %ith a class" /n object is an instantiation of a class! %hich means an o&#ect has state! &ut not a class"
#). *hat are methods and messages
4ethods implement an o&#ect2s &ehavior" / method is nothin more than an action that an o&#ect can perform" / messae is essentially a function or procedure call from one o&#ect to another o&#ect" #+. *hy are encapsulation and in%ormation hiding important characteristics o% o"$ect3oriented systems
-n o&#ect5oriented systems! com&inin encapsulation %ith the information5hidin principle suests that the information5hidin principle &e applied to o&#ects instead of merely applyin it to functions or processes" /s such! o&#ects are treated li,e &lac, &oes" The fact that %e can use an o&#ect &y callin methods is the ,ey to reusa&ility &ecause it shields the internal %or,ins of the o&#ect from chanes in the outside system! and it ,eeps the system from &ein affected %hen chanes are made to an o&#ect" #-. *hat is meant "y polymorphism 4hen applied to o"$ect oriented systems
.ae 1
Chapter 1
EOC Questions
.olymorphism means that the same messae can &e interpreted differently &y different classes of o&#ects" ;or eample! insertin a patient means somethin different than insertin an appointment" #. Compare and contrast dynamic and static "inding.
Dynamic! or late! &indin is a techni'ue that delays typin the o&#ect until run5time" /s such! the specific method that is actually called is not chosen &y the o&#ect5 oriented system until the system is runnin" This is in contrast to static &indin" -n a statically &ound system! the type of o&#ect is determined at compile time" Therefore! the developer has to choose %hich method should &e called instead of allo%in the system to do it" #/. *hat is a use case
/ use case is a description of a system2s &ehavior as it responds to stimuli from its environment" These stimuli come from the various users of the system as %ell as from eternal systems" The use cases are used to identify and to communicate the re'uirements for the system to the prorammers %ho must %rite the system" / use case diaram is a type of &ehavioral diaram that is part of the @nified 4odelin Lanuae (@4L) and that raphically depicts a use case or a collection of use cases"
#0. *hat is meant "y use3case dri!en
@se5case driven means that use cases are the primary modelin tools definin the &ehavior of the system"
#2. *hat is the 8ni%ied 9odeling 'anguage
The @nified 4odelin Lanuae (@4L) is a standard set of diarammin techni'ues" The o&#ective of @4L is to provide a common voca&ulary of o&#ect5oriented terms and diarammin techni'ues rich enouh to model any systems development pro#ect from analysis throuh implementation"
)6. *ho is the ;"$ect 9anagement
The O&#ect 4anaement 7roup is a consortium of orani$ations %hose purpose it is to set standards for o&#ect5oriented systems" The O47 is the roup that ratified the @4L as an industry standard"
.ae 11
Chapter 1
EOC Questions
)1. *hat is the primary purpose o% structure diagrams
Structure diarams provide a %ay to represent the data and static relationships in an information system" The structure diarams include class! o&#ect! pac,ae! deployment! component! and composite structure diarams"
)#. =or 4hat are "eha!ior diagrams used
9ehavior diarams provide the analyst %ith a %ay to depict the dynamic relationships amon the instances or o&#ects that represent the &usiness information system" They also allo% the modelin of the dynamic &ehavior of individual o&#ects throuhout their lifetime" The &ehavior diarams support the analyst in modelin the functional re'uirements of an evolvin information system" The &ehavior modelin diarams include activity! se'uence! communication! interaction overvie%! timin! &ehavior state machine! protocol state machine! and use5case diarams"
)). *hy is it important %or an ;;SAD approach to "e architecture centric
/ development methodoloy is said to &e architecture centric if the architecture is the main artifact upon %hich the desin and implementation of the system is &uilt" -n other %ords! first the developers decide upon a frame%or, and then the system is &uilt around and upon it" The architecture &ecomes &oth an ena&ler and a constraint on ho% the system is developed" -t is important of an OOS/D approach to &e architecture centric &ecause this approach allo%s the development team to iterate repeatedly %ithout underminin the sta&ility of the system2s core" -f the architecture %ere to &e revisited and modified over time! then there %ould &e a very ood chance that support to some (or most) system components %ould eventually &e compromised"
)+. *hat does it mean %or an ;;SAD approach to "e incremental and iterati!e
-terative and incremental development means that the system underoes continuous testin and refinement throuhout the life of the pro#ect" /s each increment and iteration is completed! a more complete representation of the user2s real functional re'uirements is uncovered"
)-. *hat are the phases and 4or:%lo4s o% the 8ni%ied Process
The phases of the @nified .rocess are:
.ae 13
Chapter 1
EOC Questions
1" -nception: a &usiness case is made for the proposed system" 3" Ela&oration: re'uirements are determined and the system is desined" 8" Construction: focuses heavily on prorammin the evolvin information system" " Transition: addresses aspects typically associated %ith the implementation phase of a traditional SDLC approach The %or,flo%s of the @nified .rocess are: 1" Enineerin *or,flo%s a" 9usiness 4odelin *or,flo% &" 6e'uirements *or,flo% c" /nalysis *or,flo% d" Desin *or,flo% e" -mplementation *or,flo% f" Testin *or,flo% " Deployment *or,flo% 3" Supportin *or,flo%s a" .ro#ect 4anaement *or,flo% &" Confiuration and Chane 4anaement *or,flo% c" Environment *or,flo%
). Compare the phases o% the 8ni%ied Process 4ith the phases o% the 4ater%all model.
The -nception phase of the @nified .rocess is similar to the .lannin phase of the *aterfall methodoloy" The Ela&oration phase of the @nified .rocess encompasses most of the activities in &oth the /nalysis and Desin phases of the *aterfall methodoloy" The Construction and Transition phases of the @nified .rocess toether comprise the set of activities normally performed durin the -mplementation phase of the *aterfall methodoloy"
)/. *hich phase in the SD'C is most important and 4hy
/ll systems development pro#ects follo% essentially the same fundamental process called the system development life cycle (SDLC)" The plannin phase in SDLC is the most important phase &ecause durin this phase the pro#ect team identifies the &usiness value of the system! conducts a feasi&ility analysis! and plans the pro#ect" This phase is the fundamental process of understandin %hy an information system should &e &uilt and determinin ho% the pro#ect team %ill o a&out &uildin it"
)0. Descri"e the ma$or elements and issues 4ith an o"$ect3oriented approach to de!eloping in%ormation systems.
.ae 18
Chapter 1
EOC Questions
O&#ect5oriented systems analysis and desin (OOS/D) is most associated %ith a phased development 6/D5&ased methodoloy! %here the time spent in each phase is very short" OOS/D uses a use5case5driven! architecture5centric! iterative! and incremental information systems development approach" -t supports three different vie%s of the evolvin system: functional! static! and dynamic" OOS/D allo%s the analyst to decompose comple pro&lems into smaller! more manaea&le components usin a commonly accepted set of notations" /dditionally! o&#ect5oriented systems analysis and desin allo%s the analyst to interact %ith the user %ith o&#ects from the user2s environment instead of a set of separate processes and data"
.ae 1
