metolologia- requerimientos

8/12/2019 Metolologia- Requerimientos

1/53

Modeling

Business Modeling: Overview


2/53

Introduction to Business Modeling Purpose

Relation to Other Disciplines

Concepts

Scope of Business Modeling

Activity-Based Costing

Business Architecture

Business Patterns

e-Business Development

Modeling Large Organiations

Purpose

!he purposes of "usiness modeling are#

!o understand the structure and the dynamics of the organiation in $hich a systemis to "e deployed %the target organiation&'

!o understand current pro"lems in the target organiation and identify improvementpotentials'

!o ensure that customers( end users( and developers have a common understandingof the target organiation'

!o derive the system re)uirements needed to support the target organiation'!o achieve these goals( the "usiness modeling discipline descri"es ho$ to develop a visionof the ne$ target organiation( and "ased on this vision de*ne the processes( roles( andresponsi"ilities of that organiation in a "usiness use-case model and a "usiness o"+ectmodel'Complementary to these models( the follo$ing artifacts are developed#

Supplementary Business Speci*cation

,lossary

Relation to Other Disciplines!he "usiness modeling discipline is related to other disciplines( as follo$s# !he Requirementsdiscipline uses "usiness models as an important input to

understanding re)uirements on the system'

!he Analysis & Designdiscipline uses "usiness entities as an input to identifyingentity classes in the design model'

!he Environmentdiscipline develops and maintains supporting artifacts(such as the Business-Modeling ,uidelines'
http://var/www/apps/conversion/tmp/scratch_5/co_scobm.htmhttp://var/www/apps/conversion/tmp/scratch_5/co_abc.htmhttp://var/www/apps/conversion/tmp/scratch_5/co_barch.htmhttp://var/www/apps/conversion/tmp/scratch_5/co_bpatt.htmhttp://var/www/apps/conversion/tmp/scratch_5/co_ebiz.htmhttp://var/www/apps/conversion/tmp/scratch_5/co_large.htmhttp://var/www/apps/conversion/tmp/scratch_5/co_scobm.htmhttp://var/www/apps/conversion/tmp/scratch_5/co_abc.htmhttp://var/www/apps/conversion/tmp/scratch_5/co_barch.htmhttp://var/www/apps/conversion/tmp/scratch_5/co_bpatt.htmhttp://var/www/apps/conversion/tmp/scratch_5/co_ebiz.htmhttp://var/www/apps/conversion/tmp/scratch_5/co_large.htm


3/53

Business Modeling : Concepts Scope of Business Modeling

Activity-Based Costing

Business Architecture

Business Patterns e-Business Development

Modeling Large Organiations
http://var/www/apps/conversion/tmp/scratch_5/co_scobm.htmhttp://var/www/apps/conversion/tmp/scratch_5/co_abc.htmhttp://var/www/apps/conversion/tmp/scratch_5/co_barch.htmhttp://var/www/apps/conversion/tmp/scratch_5/co_bpatt.htmhttp://var/www/apps/conversion/tmp/scratch_5/co_ebiz.htmhttp://var/www/apps/conversion/tmp/scratch_5/co_large.htmhttp://var/www/apps/conversion/tmp/scratch_5/co_scobm.htmhttp://var/www/apps/conversion/tmp/scratch_5/co_abc.htmhttp://var/www/apps/conversion/tmp/scratch_5/co_barch.htmhttp://var/www/apps/conversion/tmp/scratch_5/co_bpatt.htmhttp://var/www/apps/conversion/tmp/scratch_5/co_ebiz.htmhttp://var/www/apps/conversion/tmp/scratch_5/co_large.htm


4/53

Costing


5/53

Concepts: Activity-Based Costing

Topics

ntroduction

Calculating the performance of a "usiness process

dentifying areas of improvement.ote# Portions of this content are dra$n from the user/s guide for the Rational Rose Activity-Based Costing Lin0( a product developed and sold "y 1nsem"le Systems%http#22$$$'ensem"le-systems'com2 &'

Introduction Top Top

Activity-based costing (ABC)is a methodology that measures the cost and performanceof activities( resources( and cost o"+ects' Resources are assigned to activities( then activitiesare assigned to cost o"+ects "ased on their use' Activity-"ased costing recognies the causalrelationships of cost drivers to activities 3PLR445'Activity-"ased costing is a"out#

Measuring "usiness process performance( activity "y activity'

1stimating the cost of "usiness process outputs "ased on the cost of the resourcesused in producing the product'

dentifying opportunities to improve process e6ciency and e7ectiveness' Activitycosts are used as the )uantitative measurement' f activities have unusually highcosts or it they don/t add value( they "ecome targets for re-engineering'

Activity-based management (ABM)is a "road discipline that focuses on achievingcustomer value and company pro*t "y managing activities' ABM dra$s on activity-"asedcosting as a ma+or source of information'

Calculating the Peror!ance o a Business Process Top Top

!o calculate the performance of a "usiness process( you need to 0no$ $hat the $or08o$ is

and $hat type of resources are involved in performing the $or08o$' 9ou need to have thefollo$ing elements descri"ing the $or08o$ in place "efore you can start measuring#

A description of the "usiness use case representing the "usiness process:see,uidelines# Business ;se Case( and the sections on $or08o$'

One or more activity diagrams descri"ing the $or08o$:see ,uidelines# ActivityDiagram in the Business ;se-Case Model'

!he realiation of that "usiness use case:see ,uidelines# Business ;se-CaseRealiation'

Basic Cost Drivers


6/53

threads such as outgoing transitions from a decision( and for conditional threads such as aconditional transition outgoing from a synchroniation "ar'

Calculating the Cost o Peror!ing a "or#low

A $or08o$ is descri"ed $ith a collection of activity states' >' ? E'

!he total cost of performing the $or08o$ is the sum of the cost for each activity( althoughthere is often an overhead associated $ith initiating the $or08o$'


7/53

!he total duration for these t$o concurrent threads is F minutes( $hich is the duration of thelongest thread in this case'

Alternative Threads

f alternative threads e=ist in an activity diagram( the cost for the alternative threads arecalculated as the sum of the cost for each alternative( $eighted $ith the occurrencepro"a"ility for each alternative' Alternative threads are sho$n using decision icons'1=ample#


8/53

!he total calculated cost for a thread $ith alternatives is the $eighted cost of the alternativethreads'

Conditional Threads

f a conditional thread e=ists( the cost for that thread is added to the cost for its parallelthreads( $eighted $ith the pro"a"ility of it occurring' A conditional thread is indicated $ith aguard condition on a transition'1=ample#

f there is a conditional thread( its cost is *rst $eighted $ith the pro"a"ility of it occurring(and then added to the cost of its parallel threads'

$ested Activity %raphs

f an activity has a su"-graph( the cost of that activity is the cost of the activities in the su"-


9/53

graph'

Identiying Areas o I!prove!ent TopTop

Activity-"ased costing is often used to compare alternatives( such as proposed changeversus current practice( or to compare di7erent proposed changes' !here are three 0inds of

parameters to $or0 $ith to e=plore di7erences "et$een alternative 8o$s# Changing values of cost attri"utes $ithout changing the structure or realiation of the

$or08o$G for e=ample( assuming shorter time durations'

Changing structure of the $or08o$G for e=ample( changing from se)uential toconcurrent e=ecution of activities'

Changing $hat resources are used in the realiation of the $or08o$G for e=ample(merging resources to eliminate hand-o7s'

!o compare these alternatives( you may create Hsi"lingH activity diagrams to sho$ thevariations of the "usiness use case' Ihen changing $hat resources are used in therealiation of the $or08o$( you must also esta"lish Hsi"lingH realiations of the $or08o$s tocorrectly e=plore resource costs'

Concepts: Business ArchitectureIe de*ne "usiness architecture as an organied set of elements $ith clear relationships toone another( $hich together form a $hole de*ned "y its functionality' !he elementsrepresent the organiational and "ehavioral structure of a "usiness 3system5( and sho$a"stractions of the 0ey processes and structures of the "usiness' 3.DL4J5( 31R5

!he intent of de*ning architecture is not to "e complete( "ut to cover the "readth of theorganiation' Similarly to ho$ $e de*ne soft$are architecture( see Concepts# Soft$areArchitecture($e can tal0 a"out architectural vie$s of the "usiness' 1ach of these vie$scontains an architecturally signi*cant su"set of $hat $ould "e a complete de*nition' A set ofvie$s could "e#

Business process vie$:includes and outlines the 0ey "usiness processes of the"usiness( those that are the reason the "usiness e=ist'

Organiation structure vie$:outlines the 0ey roles and responsi"ilities in the"usiness( as $ell as their grouping'

Culture vie$:e=presses a vision of the organiationKs culture( and de*nes themechanisms put in place to encourage that culture'

uman resource aspects vie$:discusses the mechanisms put in place to maintainand develop the s0ill set of your sta7'

Domain vie$ %optional&:for organiations that handle a comple= set of information( itis often useful to de*ne 0ey mechanisms and patterns to "e applied to thoseinformation structures' n simple cases( this may already "e clear from theorganiation structure vie$'
http://var/www/apps/conversion/referenc.htm#NDL97http://var/www/apps/conversion/referenc.htm#ERI00http://var/www/apps/conversion/tmp/ana_desi/co_swarch.htmhttp://var/www/apps/conversion/tmp/ana_desi/co_swarch.htmhttp://var/www/apps/conversion/tmp/ana_desi/co_swarch.htmhttp://var/www/apps/conversion/referenc.htm#NDL97http://var/www/apps/conversion/referenc.htm#ERI00http://var/www/apps/conversion/tmp/ana_desi/co_swarch.htmhttp://var/www/apps/conversion/tmp/ana_desi/co_swarch.htm


10/53

Patterns


11/53

Concepts: Business PatternsIe de*ne a "usiness pattern as generalied solutions that can "e implemented and appliedin a pro"lem situation %a conte=t&( and there"y eliminate one or more of the inherentpro"lems' Patterns can "e considered prototypes for production' 31R5Patterns are part of ho$ you de*ne your "usiness architecture#

!hey re8ect common solutions to common pro"lems' Patterns help maintain an architectural style throughout the organiation'

!hey are a simple $ay of capturing e=periences'Ie present a fe$ patterns that can "e useful as a "aseline#

Process evaluation pattern

Process feed"ac0 pattern

Activity interaction pattern

Business event-result history patternAll of these patterns are "ased on the e=tensive pattern collection in 31R5'

Process &valuation Pattern Top Top

Conte$t# !his pattern is a si"ling to the process feed"ac0 pattern' t re8ects a need to planfor more strategic and long-term investments $hen improving a process'#roblem# !he process evaluation pattern can "e applied to all situations $here the "usinessprocess results must "e evaluated to provide a competitive edge' Manufacturing( mar0eting(and sales processes are e=amples of the di7erent "usiness processes that must "eevaluated each time they are e=ecuted'%olution# A solution to this pro"lem is to have an evaluation process in place thatcontinuously monitors and suggests improvements( "oth long-term and short term( to a"usiness process'

Participants of the process evaluation patternist o' articiants:aBusiness Actor:A consumer of the "usiness'Core Process:A "usiness process $hich has the primary purpose to ful*ll a need of theconsumer'1valuate Core Process%es&:A "usiness process $hit the primary purpose of monitoring one
http://var/www/apps/conversion/referenc.htm#ERI00http://var/www/apps/conversion/referenc.htm#ERI00http://var/www/apps/conversion/referenc.htm#ERI00http://var/www/apps/conversion/referenc.htm#ERI00


12/53

or more core processes to propose improvements to ma0e them more e6cient'

Dynamic vie$ of the process evaluation pattern'


13/53

Participants of the process feed"ac0 patternist o' articiants:aBusiness Ior0er:A role including the set of responsi"ilities needed to re*ne the processdelivera"le'aDelivera"le:!his is the delivera"le of the process( $hich changes state as the "usiness$or0er manipulates it'Metrics of aDelivera"le:!his is the metrics collected to sho$ the state changes of theprocess delivera"le( and also ho$ the "usiness $or0er performs'

Static vie$ of the process feed"ac0 pattern


14/53

Dynamic vie$ of the process feed"ac0 pattern

Activity Interaction Pattern Top Top

Conte$t# !he activity interaction pattern can "e used $herever comple= interactions"et$een activities $ithin a "usiness process are modeled'#roblem# Activities may share resources $ith one another( typically "y $ay of datatransmission'%olution# !he activity interaction pattern can "e used to model and organie comple=interactions "et$een "usiness resources'

Participants of the activity interaction pattern


15/53

ist o' articiants:aBusinessIor0er:One of the "usiness $or0ers participating in the realiation of theprocess'anotherBusinessIor0er:Another of the "usiness $or0ers participating in the realiation ofthe process'do!hing:Activity performed "y an instance of aBusinessIor0er'

doOther!hing:Activity performed "y an instance of anotherBusinessIor0er'aDelivera"le:Ihat is produced or maintained "y the process'

Dynamic vie$ of the activity interaction pattern:Resource A and resource B use the sameshared o"+ect'

!his pattern has no static vie$'

Business &vent-Result )istory Pattern Top Top

Conte$t# !he "usiness event-result history pattern is suita"le for pro"lem domains $hereyou need to maintain a history of "usiness events and their results' t is most often used tomodel *nancial systems and enterprise resource planning %1RP& systems'#roblem# !he "usiness event-result history pattern is use to trac0 signi*cant "usiness

events and then to connect these events to their results' Capturing the di7erent "usinessevents( along $ith their results:such as decisions( contracts( statements( or products:helps you ma0e "etter "usiness decisions' !he goal of this pattern is to ena"le you to 0eep arecord of all important "usiness events( $hich are typically descri"ed $ith attri"utes such asdescription( purpose( and result'%olution# ;sing the "usiness event-results history pattern ensures that models produced totrac0 important "usiness events and their causes are e=tensi"le' 1=tensi"le means that ne$0inds of events and causes can "e added at a later date to the same overall structure' ;singthis pattern ma0es it possi"le to record "usiness events and( at a later point in time( to


16/53

analye these events and dra$ conclusions' !hese conclusions typically lead to activities ordecisions in the "usiness( such as to discontinue a relationship $ith a customer or vendor"ecause of poor payment history' f no record of "usiness events is maintained( no history isavaila"le to learn from and the same mista0es may "e repeated over and over again' Onepotential pro"lem $ith this pattern is $hen too many lo$-level "usiness events arerecorded( the amount of detail ma0es the record hard to analye and evaluate' 1vents

should "e de*ned so theyKre easy to understand in a "usiness conte=tG for e=ample( orderplaced( product delivered( invoice paid( and so on'

Participants of the "usiness event-result history pattern

ist o' articiants:Business 1vent:!his "usiness entity descri"es signi*cant occurrences to the "usiness'1=amples of attri"utes to a Business 1vent could "e date( priority( description( and type'Common types are delivery( contract signing( and purchase'Product:!his "usiness entity represents the delivera"les' Products can "e a"stract o"+ects(such as a service( "usiness e7ort or mar0et share or physical o"+ects such as soft$are andhard$are' Common attri"utes are identi*er and name' Common types of products arecomputer program( support( consultation( and installation'Party:!his "usiness entity may represent either individuals or companies' !he parties playa role in the conte=t of a Contract' !ypical roles are seller and "uyer' Party typically has theattri"utes name and address'


17/53

Contract:!his "usiness entity represents a deal or a decision' !he Contract de*nes thecircumstances of a delivery( $here the delivery is a Product' !he Contract is usually "et$eena seller and a "uyer( "ut it can also "e "et$een other parties' Common attri"utes aredescription( date and until-date' Contracts can "e associated $ith each otherG for e=ample(one contract can "e complimentary to another contract' !his is also sho$n $ith therecursive association' 1=amples of types of contracts are s0eleton contract or lease contract'

Statement:A Statement e=presses a Contract' A Statement can e=press many contractsand a contract can "e stated many times' !ypical attri"utes are description and date'Statements can also "e associated $ith each other' !his is sho$n $ith the recursiveassociation' 1=amples of types of statements are $ritten statements and ver"al statements'

!he static vie$ of the "usiness event-result history pattern!his pattern has no dynamic vie$'


18/53


19/53

Re*uire!ents: Contenido

re)uirem2inre)'htmre)uirem2inre)'htmre)uirem2$fdre)'htmre)uirem2$fdre)'htmre)uirem2$fovre)'htmre)uirem2$fovre)'htmre)uirem2r)resov'htmre)uirem2r)resov'htmre)uire

m2mdovre)'htmre)uirem2mdovre)'htmre)uirem2cosre)'htmre)uirem2cosre)'htm
http://var/www/apps/conversion/tmp/scratch_5/requirem/in_req.htmhttp://var/www/apps/conversion/tmp/scratch_5/requirem/wfd_req.htmhttp://var/www/apps/conversion/tmp/scratch_5/requirem/wfov_req.htmhttp://var/www/apps/conversion/tmp/scratch_5/requirem/wfov_req.htmhttp://var/www/apps/conversion/tmp/scratch_5/requirem/rq_resov.htmhttp://var/www/apps/conversion/tmp/scratch_5/requirem/mdov_req.htmhttp://var/www/apps/conversion/tmp/scratch_5/requirem/mdov_req.htmhttp://var/www/apps/conversion/tmp/scratch_5/requirem/cos_req.htmhttp://var/www/apps/conversion/tmp/scratch_5/requirem/in_req.htmhttp://var/www/apps/conversion/tmp/scratch_5/requirem/in_req.htmhttp://var/www/apps/conversion/tmp/scratch_5/requirem/wfd_req.htmhttp://var/www/apps/conversion/tmp/scratch_5/requirem/wfd_req.htmhttp://var/www/apps/conversion/tmp/scratch_5/requirem/wfov_req.htmhttp://var/www/apps/conversion/tmp/scratch_5/requirem/wfov_req.htmhttp://var/www/apps/conversion/tmp/scratch_5/requirem/wfov_req.htmhttp://var/www/apps/conversion/tmp/scratch_5/requirem/rq_resov.htmhttp://var/www/apps/conversion/tmp/scratch_5/requirem/rq_resov.htmhttp://var/www/apps/conversion/tmp/scratch_5/requirem/mdov_req.htmhttp://var/www/apps/conversion/tmp/scratch_5/requirem/mdov_req.htmhttp://var/www/apps/conversion/tmp/scratch_5/requirem/mdov_req.htmhttp://var/www/apps/conversion/tmp/scratch_5/requirem/cos_req.htmhttp://var/www/apps/conversion/tmp/scratch_5/requirem/cos_req.htm


20/53

Disciplines>Requirements> Introduction
http://var/www/apps/conversion/tmp/ovu_core.htmhttp://var/www/apps/conversion/tmp/ovu_req.htmhttp://var/www/apps/conversion/tmp/ovu_req.htmhttp://var/www/apps/conversion/tmp/ovu_req.htmhttp://var/www/apps/conversion/tmp/ovu_core.htmhttp://var/www/apps/conversion/tmp/ovu_req.htm


21/53

Introduction to Re*uire!ents Purpose

Relation to Other Disciplines

Concepts

Re)uirements

Re)uirements Management

!ypes of Re)uirements

!racea"ility

;ser-Centered Design

;se-Case Nie$

Purpose TopTop

!he purpose of the Re)uirements discipline is#

!o esta"lish and maintain agreement $ith the customers and other sta0eholderson $hat the system should do'

!o provide system developers $ith a "etter understanding of the systemre)uirements'

!o de*ne the "oundaries of %delimit& the system'

!o provide a "asis for planning the technical contents of iterations'

!o provide a "asis for estimating cost and time to develop the system'

!o de*ne a user-interface for the system( focusing on the needs and goals of theusers'

!o achieve these goals( it is important( *rst of all( to understand the de*nition and scopeof the pro"lem $hich $e are trying to solve $ith this system' !he Business Rules(Business ;se-Case Modeland Business O"+ect Modeldeveloped duringBusinessModeling$ill serve as valua"le input to this e7ort' Sta0eholdersare identi*ed andSta0eholder Re)uestsare elicited( gathered and analyed'

A Nisiondocument( a use-case model( use casesand Supplementary Speci*cationaredeveloped to fully descri"e the system - !atthe system $ill do - in an e7ort thatvie$s all sta0eholders(including customers and potential users( as important sources ofinformation %in addition to system re)uirements&'Sta0eholder Re)uestsare "oth actively elicited and gathered from e=isting sources toget a H$ish listH of $hat di7erent sta0eholders of the pro+ect %customers( users( productchampions& e=pect or desire the system to include( together $ith information on ho$each re)uest has "een considered "y the pro+ect'

!he Nisiondocument provides a complete vision for the soft$are system underdevelopment and supports the contract "et$een the funding authority and thedevelopment organiation' 1very pro+ect needs a source for capturing the e=pectationsamong sta0eholders' !he vision document is $ritten from the customers/ perspective(focusing on the essential features of the system and accepta"le levels of )uality' !he

Nision should include a description of $hat features$ill "e included as $ell as thoseconsidered "ut not included' t should also specify operational capacities %volumes(response times( accuracies&( user pro*les %$ho $ill "e using the system&( and inter-operational interfaces $ith entities outside the system "oundary( $here applica"le' !heNision document provides the contractual "asis for the re)uirements visi"le to thesta0eholders'

!he use-case modelshould serve as a communication medium and can serve as acontract "et$een the customer( the users( and the system developers on thefunctionality of the system( $hich allo$s#

''''

''inde='htm

+avascri

pt#load

!op%&G

+avascrip
http://var/www/apps/conversion/tmp/scratch_5/co_req.htmhttp://var/www/apps/conversion/tmp/scratch_5/co_rm.htmhttp://var/www/apps/conversion/tmp/scratch_5/co_reqty.htmhttp://var/www/apps/conversion/tmp/scratch_5/co_trace.htmhttp://var/www/apps/conversion/tmp/scratch_5/co_ucd.htmhttp://var/www/apps/conversion/tmp/scratch_5/co_ucv.htmhttp://var/www/apps/conversion/artifact/ar_brules.htmhttp://var/www/apps/conversion/artifact/ar_bucm.htmhttp://var/www/apps/conversion/artifact/ar_bucm.htmhttp://var/www/apps/conversion/artifact/ar_bom.htmhttp://var/www/apps/conversion/tmp/ovu_busm.htmhttp://var/www/apps/conversion/tmp/ovu_busm.htmhttp://var/www/apps/conversion/tmp/ovu_busm.htmhttp://var/www/apps/conversion/workers/wk_sthld.htmhttp://var/www/apps/conversion/artifact/ar_stnds.htmhttp://var/www/apps/conversion/artifact/ar_vsion.htmhttp://var/www/apps/conversion/artifact/ar_ucmod.htmhttp://var/www/apps/conversion/artifact/ar_uc.htmhttp://var/www/apps/conversion/artifact/ar_sspec.htmhttp://var/www/apps/conversion/artifact/ar_sspec.htmhttp://var/www/apps/conversion/workers/wk_sthld.htmhttp://var/www/apps/conversion/workers/wk_sthld.htmhttp://var/www/apps/conversion/artifact/ar_stnds.htmhttp://var/www/apps/conversion/artifact/ar_vsion.htmhttp://var/www/apps/conversion/glossary.htm#featurehttp://var/www/apps/conversion/artifact/ar_ucmod.htmhttp://var/www/apps/index.htmhttp://var/www/apps/index.htmhttp://var/www/apps/index.htmhttp://var/www/apps/index.htmhttp://var/www/apps/index.htmhttp://var/www/apps/index.htmhttp://var/www/apps/index.htmhttp://var/www/apps/index.htmhttp://var/www/apps/index.htmhttp://var/www/apps/index.htmhttp://var/www/apps/index.htmhttp://var/www/apps/index.htmhttp://var/www/apps/index.htmhttp://var/www/apps/index.htmhttp://var/www/apps/index.htmhttp://var/www/apps/index.htmhttp://var/www/apps/index.htmhttp://var/www/apps/index.htmhttp://var/www/apps/conversion/tmp/scratch_5/co_req.htmhttp://var/www/apps/conversion/tmp/scratch_5/co_rm.htmhttp://var/www/apps/conversion/tmp/scratch_5/co_reqty.htmhttp://var/www/apps/conversion/tmp/scratch_5/co_trace.htmhttp://var/www/apps/conversion/tmp/scratch_5/co_ucd.htmhttp://var/www/apps/conversion/tmp/scratch_5/co_ucv.htmhttp://var/www/apps/conversion/artifact/ar_brules.htmhttp://var/www/apps/conversion/artifact/ar_bucm.htmhttp://var/www/apps/conversion/artifact/ar_bom.htmhttp://var/www/apps/conversion/tmp/ovu_busm.htmhttp://var/www/apps/conversion/tmp/ovu_busm.htmhttp://var/www/apps/conversion/workers/wk_sthld.htmhttp://var/www/apps/conversion/artifact/ar_stnds.htmhttp://var/www/apps/conversion/artifact/ar_vsion.htmhttp://var/www/apps/conversion/artifact/ar_ucmod.htmhttp://var/www/apps/conversion/artifact/ar_uc.htmhttp://var/www/apps/conversion/artifact/ar_sspec.htmhttp://var/www/apps/conversion/workers/wk_sthld.htmhttp://var/www/apps/conversion/artifact/ar_stnds.htmhttp://var/www/apps/conversion/artifact/ar_vsion.htmhttp://var/www/apps/conversion/glossary.htm#featurehttp://var/www/apps/conversion/artifact/ar_ucmod.htmhttp://var/www/apps/index.htmhttp://var/www/apps/index.htmhttp://var/www/apps/index.htm


22/53

Customers and users to validate that the system $ill "ecome $hat theye=pected'

System developers to "uild $hat is e=pected'!he use-case model consists of use casesand actors' 1ach use case in the model isdescri"ed in detail( sho$ing step-"y-step ho$ the system interacts $ith the actors( and$hat the system does in the use case' ;se cases function as a unifying thread

throughout the soft$are lifecycleG the same use-case model is used in system analysis(design(implementation( and testing'

!he Supplementary Speci*cationsare an important complement to the use-case model("ecause together they capture all soft$are re)uirements %functional and nonfunctional&that need to "e descri"ed to serve as a complete soft$are re)uirements speci*cation'A complete de*nition of the soft$are re)uirementsdescri"ed in the use casesandSupplementary Speci*cationsmay "e pac0aged together to de*ne a Soft$areRe)uirements Speci*cation %SRS&for a particular HfeatureH or other su"system grouping'A Re)uirements Management Planspeci*es the information and control mechanisms$hich $ill "e collected and used for measuring( reporting( and controlling changes tothe product re)uirements'Complementary to the a"ove mentioned artifacts( the follo$ing artifacts are alsodeveloped#

,lossary ;se-Case Story"oard

;ser-nterface Prototype!he ,lossaryis important "ecause it de*nes a common terminology $hich is usedconsistently across the pro+ect or organiation'

!he ;se-Case Story"oardand ;ser-nterface Prototypeare all results of user-interfacemodeling and prototyping( $hich are done in parallel $ith other re)uirements activities'

!hese artifacts provide important feed"ac0 mechanisms in later iterations fordiscovering un0no$n or unclear re)uirements'

Relation to Other Disciplines TopTop

!he Re)uirements discipline is related to other process disciplines'

!he Business Modelingdiscipline provides Business Rules( a Business ;se-Case Modeland a Business O"+ect Model( including a Domain Model and anorganiational conte=t for the system'

!he Analysis & Designdiscipline gets its primary input %the use-case modeland the,lossary& from Re)uirements'


23/53

Rational Unified Process

Re*uire!ents: Concepts

Re)uirements Re)uirements Management

!ypes of Re)uirements

!racea"ility

;ser-Centered Design

;se-Case Nie$

Concepts: Re*uire!entsMore information on this topic can "e found at#

Concepts# Re)uirements Management

Concepts# !ypes of Re)uirements Concepts# !racea"ility

Concepts# ;ser-Centered Design

Ihite Paper# Applying Re)uirements Management $ith ;se CasesA requirementis de*ned as Ha condition or capa"ility to $hich a system must conformH'

!here are many di7erent 0inds of re)uirements' One $ay of categoriing them is descri"edas the .R#%/ model 3,RA45( using the acronym


24/53

'unctionality TopTop


25/53

compati"ility

con*gura"ility

servicea"ility

installa"ility

localia"ility %internationaliation&

Design Re*uire!ent TopTop

A design re)uirement( often called a design constraint( speci*es or constrains the designof a system'

I!ple!entation Re*uire!ent TopTop

An implementation re)uirement speci*es or constrains the coding or construction of asystem' 1=amples are#

re)uired standards

implementation languages

policies for data"ase integrity

resource limitsoperation environments

Interace Re*uire!ent TopTop

An interface re)uirement speci*es#

an e=ternal item $ith $hich a system must interact

constraints on formats( timings( or other factors used "y such an interaction

Physical Re*uire!ent TopTop

A physical re)uirement speci*es a physical characteristic that a system must possessG fore=ample(

material shape

sie

$eight!his type of re)uirement can "e used to represent hard$are re)uirements( such as thephysical net$or0 con*gurations re)uired'


26/53

Concepts: Re*uire!ents Manage!ent Ihat is Re)uirements Management

Pro"lem analysis

;nderstanding sta0eholder needs

De*ning the system Managing the scope of the pro+ect

Re*ning the system de*nition

Managing changing re)uirementsMore nformation# Concepts# Re)uirementsConcepts# !ypes of Re)uirementsConcepts# !racea"ilityIhite Paper# Applying Re)uirements Management $ith ;se Cases

"hat is Re*uire!ents Manage!ent TopTop

Re)uirements management is a systematic approach to *nding( documenting( organiingand trac0ing the changing re)uirements of a system'

Ie de*ne a re)uirementas#

A condition or capability to which the system must conform.

Our formal de*nition of re)uirements management is that it is a systematic approach to

eliciting( organiing( and documenting the re)uirements of the system( and

esta"lishing and maintaining agreement "et$een the customer and the pro+ect teamon the changing re)uirements of the system'

@eys to e7ective re)uirements management include maintaining a clear statement of there)uirements( along $ith applica"le attri"utesfor each re)uirement typeandtracea"ilitytoother re)uirements and other pro+ect artifacts'Collecting re)uirements may sound li0e a rather straightfor$ard tas0' n real pro+ects(ho$ever( you $ill run into di6culties "ecause#

Re)uirements are not al$ays o"vious( and can come from many sources'

Re)uirements are not al$ays easy to e=press clearly in $ords'

!here are many di7erent types of re)uirements at di7erent levels of detail'

!he num"er of re)uirements can "ecome unmanagea"le if not controlled'

Re)uirements are related to one another and also to other delivera"les of thesoft$are engineering process'

Re)uirements have uni)ue properties or property values'


27/53

Pro(le! Analysis TopTop

Pro"lem analysis is done to understand pro"lems( initial sta0eholder needs( and proposehigh-level solutions' t is an act of reasoning and analysis to *nd Hthe pro"lem "ehind thepro"lemH' During pro"lem analysis( agreement is gained on the real pro"lem%s&( and $ho the

sta0eholders are' Also( you de*ne $hat from a "usiness perspective are the "oundaries ofthe solution( as $ell as "usiness constraints on the solution' 9ou should also have analyedthe "usiness case for the pro+ect so that there is a good understanding of $hat return ise=pected on the investment made in the system "eing "uilt'See also Ior08o$ Detail# Analye the Pro"lem'

+nderstanding ,ta#eholder $eeds TopTop

Re)uirements come from many sources( e=amples $ould "e customers( partners( end users(and domain e=perts' 9ou need to 0no$ ho$ to "est determine $hat the sources should "e(get access to those sources( and also ho$ to "est elicit information from them' !heindividuals $ho provide the primary sources for this information are referred to assta0eholders in the pro+ect' f youKre developing an information system to "e used internally

$ithin your company( you may include people $ith end user e=perience and "usinessdomain e=pertise in your development team' Nery often you $ill start the discussions at a"usiness model level rather than a system level' f youKre developing a product to "e sold toa mar0et place( you may ma0e e=tensive use of your mar0eting people to "etter understandthe needs of customers in that mar0et'1licitation activities may occur using techni)ues such as intervie$s( "rainstorming(conceptual prototyping( )uestionnaires( and competitive analysis' !he result of theelicitation $ould "e a list of re)uests or needs that are descri"ed te=tually and graphically(and that have "een given priority relative one another'See also Ior08o$ Detail# ;nderstand Sta0eholder .eeds'

Deining the ,yste! TopTop

!o de*ne the system means to translate and organie the understanding of sta0eholderneeds into a meaningful description of the system to "e "uilt' 1arly in system de*nition(decisions are made on $hat constitutes a re)uirement( documentation format( languageformality( degree of re)uirements speci*city %ho$ many and in $hat detail&( re)uest priorityand estimated e7ort %t$o very di7erent valuations usually assigned "y di7erent people inseparate e=ercises&( technical and management ris0s( and initial scope' Part of this activitymay include early prototypes and design models directly related to the most importantsta0eholder re)uests' !he outcome of system de*nition is a description of the system that is"oth natural language and graphical'See also Ior08o$ Detail# De*ne the System'

Managing the ,cope o the Pro.ect TopTop

!o e6ciently run a pro+ect( you need to carefully prioritie the re)uirements( "ased on inputfrom all sta0eholders( and manage its scope' !oo many pro+ects su7er from developers$or0ing on so called H1aster eggsH %features the developer *nds interesting andchallenging&( rather than early focusing on tas0s that mitigate a ris0 in the pro+ect orsta"ilie the architecture of the application' !o ma0e sure that you resolve or mitigate ris0sin a pro+ect as early as possi"le( you should develop your system incrementally( carefullychoosing re)uirements to for each increment that mitigates 0no$n ris0s in the pro+ect' !o doso( you need to negotiate the scope %of each iteration& $ith the sta0eholders of the pro+ect'

!his typically re)uires good s0ills in managing e=pectations of the output from the pro+ect in
http://var/www/apps/conversion/tmp/scratch_5/wfs_anpr.htmhttp://var/www/apps/conversion/tmp/scratch_5/wfs_unsh.htmhttp://var/www/apps/conversion/tmp/scratch_5/wfs_defs.htmhttp://var/www/apps/conversion/tmp/scratch_5/wfs_anpr.htmhttp://var/www/apps/conversion/tmp/scratch_5/wfs_unsh.htmhttp://var/www/apps/conversion/tmp/scratch_5/wfs_defs.htm


28/53

its di7erent phases' 9ou also need to have control of the sources of re)uirements( of ho$ thedelivera"les of the pro+ect loo0( as $ell as the development process itself'See also Ior08o$ Detail# Manage the Scope of the System'

Reining the ,yste! Deinition TopTop

!he detailed de*nition of the system needs to "e presented in such a $ay that yoursta0eholders can understand( agree to( and sign o7 on them' t needs to cover not onlyfunctionality( "ut also compliance $ith any legal or regulatory re)uirements( usa"ility(relia"ility( performance( supporta"ility( and maintaina"ility' An error often committed is to"elieve that $hat you feel is comple= to "uild needs to have a comple= de*nition' !his leadsto di6culties in e=plaining the purpose of the pro+ect and the system' People may "eimpressed( "ut they $ill not give good input since they donKt understand' 9ou should put lotse7ort in understanding the audience for the documents you are producing to descri"e thesystem' 9ou may often see a need to produce di7erent 0inds of description for di7erentaudiences'Ie have seen that the use-case methodology( often in com"ination $ith simple visualprototypes( is a very e6cient $ay of communicating the purpose of the system and de*ningthe details of the system' ;se cases help put re)uirements into a conte=t( they tell a story ofho$ the system $ill "e used'Another component of the detailed de*nition of the system is to state ho$ the systemshould "e tested' !est plans and de*nitions of $hat tests to perform tells us $hat systemcapa"ilities $ill "e veri*ed'See also Ior08o$ Detail# Re*ne the System De*nition'

Managing Changing Re*uire!ents TopTop

.o matter ho$ careful you are a"out de*ning your re)uirements( there $ill al$ays "e thingsthat change' Ihat ma0es changing re)uirements comple= to manage is not only that achanged re)uirement means that more or less time has to "e spent on implementing aparticular ne$ feature( "ut also that a change to one re)uirement may have an impact onother re)uirements' 9ou need to ma0e sure that you give your re)uirements a structure thatis resilient to changes( and that you use tracea"ility lin0s to represent dependencies"et$een re)uirements and other artifacts of the development lifecycle' Managing changeinclude activities li0e esta"lishing a "aseline( determining $hich dependencies are importantto trace( esta"lishing tracea"ility "et$een related items( and change control'See also Ior08o$ Detail# Manage Changing Re)uirements'
http://var/www/apps/conversion/tmp/scratch_5/wfs_sco.htmhttp://var/www/apps/conversion/tmp/scratch_5/wfs_sco.htmhttp://var/www/apps/conversion/tmp/scratch_5/wfs_refs.htmhttp://var/www/apps/conversion/tmp/scratch_5/wfs_mnch.htmhttp://var/www/apps/conversion/tmp/scratch_5/wfs_sco.htmhttp://var/www/apps/conversion/tmp/scratch_5/wfs_refs.htmhttp://var/www/apps/conversion/tmp/scratch_5/wfs_mnch.htm


29/53

Concepts: Traceability

Introduction*raceability is t!e ability to trace a ro,ect element to ot!er related ro,ect

elements0 esecially t!ose related to requirements1 #ro,ect elements involved intraceability are called traceability items1 *yical traceability items include

di2erent tyes o' requirements0 analysis and design model elements0 testingarti'acts(test cases0 test rocedures0 etc1)0 and end-user suort documentation

and training material0 as s!on in t!e +gure belo1

*!e traceability !ierarc!y1Eac! traceability item !as its on unique set o' associated attributes0 !ic! isuse'ul 'or trac3ing t!e status0 bene+t0 ris30 etc1 associated it! eac! item1

Purpose of Traceability*!e urose o' establis!ing traceability is to !el:

.nderstand t!e source o' requirements Manage t!e scoe o' t!e ro,ect

Manage c!anges to requirements

Assess t!e ro,ect imact o' a c!ange in a requirement

Assess t!e imact o' a 'ailure o' a test on requirements (i1e1 i' test 'ails t!e

requirement may not be satis+ed)

4eri'y t!at all requirements o' t!e system are 'ul+lled by t!e

imlementation1

4eri'y t!at t!e alication does only !at it as intended to do1
http://var/www/apps/conversion/glossary.htm#requirementhttp://var/www/apps/conversion/glossary.htm#traceability_itemhttp://var/www/apps/conversion/tmp/scratch_5/co_reqty.htmhttp://var/www/apps/conversion/tmp/test/ovu_art.htmhttp://var/www/apps/conversion/tmp/test/ovu_art.htmhttp://var/www/apps/conversion/artifact/ar_tstcs.htmhttp://var/www/apps/conversion/artifact/ar_tstpr.htmhttp://var/www/apps/conversion/artifact/ar_eusm.htmhttp://var/www/apps/conversion/artifact/ar_eusm.htmhttp://var/www/apps/conversion/artifact/ar_rattr.htmhttp://var/www/apps/conversion/glossary.htm#requirementhttp://var/www/apps/conversion/glossary.htm#traceability_itemhttp://var/www/apps/conversion/tmp/scratch_5/co_reqty.htmhttp://var/www/apps/conversion/tmp/test/ovu_art.htmhttp://var/www/apps/conversion/tmp/test/ovu_art.htmhttp://var/www/apps/conversion/artifact/ar_tstcs.htmhttp://var/www/apps/conversion/artifact/ar_tstpr.htmhttp://var/www/apps/conversion/artifact/ar_eusm.htmhttp://var/www/apps/conversion/artifact/ar_eusm.htmhttp://var/www/apps/conversion/artifact/ar_rattr.htm


30/53

*raceability !els you understand and manage !o inut to t!e requirements0suc! as business rulesand sta3e!older requests0 are translated into a set o' 3eysta3e!older5user needs and system 'eatures0 as seci+ed in t!e 4isiondocument1*!e use-case model0 in turn0 outlines t!e !o t!ese 'eatures are translated to t!e'unctionality o' t!e system1 *!e details o' !o t!e system interacts it! t!eoutside orld are catured in use cases0 it! ot!er imortant requirements (suc!

as non-'unctional requirements0 design constraints0 etc1) in t!e %ulementary%eci+cations1 *raceability allos you to also 'ollo !o t!ese detailedseci+cations are translated into a design0 !o it is tested0 and !o it isdocumented 'or t!e user1 or a large system0 use casesand %ulementary%eci+cationsmay be ac3aged toget!er to de+ne a %o'tare Requirements%eci+cation (%R%)'or a articular 6'eature6 or ot!er subsystem grouing1A 3ey concet in !eling to manage c!anges in requirements is t!at o' a6susect6 traceability lin31 7!en a requirement (or ot!er traceability item)c!anges at eit!er end o' a traceability lin30 all lin3s associated it! t!atrequirement are mar3ed as 6susect61 *!is 8ags t!e resonsible role to reviet!e c!ange and determine i' t!e associated items ill need to c!ange also1 *!isconcet also !els in analy9ing t!e imact o' otential c!anges1*raceabilities may be set u to !el anser t!e 'olloing samle set o' queries:

%!o me user needs t!at are not lin3ed to roduct 'eatures1

%!o me t!e status o' tests on all use cases in iteration n1

%!o me all sulementary requirements lin3ed to tests !ose status is

untested1

%!o me t!e results o' all tests t!at 'ailed0 in order o' criticality1

%!o me t!e 'eatures sc!eduled 'or t!is release0 !ic! user needs t!ey

satis'y0 and t!eir status1E$amle:or a Recycling Mac!ine system0 t!e 4ision document seci+es t!e 'olloing'eature:

EA*;


31/53

A tyical traceability is s!on in t!e 'olloing diagram:

*!is diagram only s!os traceability to requirements1 t!er traceability may e$ist

as ell0 but is not s!on on t!is diagram: design elements trace don toimlementation comonents0 t!ere are test cases 'or design and imlementation0etc


32/53

Concepts: Types o Re*uire!entsMore nformation# Concepts# Re)uirementsConcepts# Re)uirements ManagementConcepts# !racea"ilityIhite Paper# Applying Re)uirements Management $ith ;se Cases

!raditionally( re)uirements are loo0ed upon as statements of te=t *tting into one of thecategories mentioned in Concepts# Re)uirements' 1ach re)uirement states Ha condition orcapa"ility to $hich the system must conformH'

!o perform e7ective re)uirements management( $e have learned that it helps to e=tend$hat $e maintain as re)uirements "eyond only the detailed Hsoft$are re)uirementsH' Ieintroduce the notion of requirements tyesto help separate the di7erent levels ofa"straction and purposes of our re)uirements'

Ie may $ant to 0eep trac0 of am"iguous H$ishesH( as $ell as formal re)uests( from oursta0eholdersto ma0e sure $e 0no$ ho$ they are ta0en care of' !he Nisiondocument helpsus 0eep trac0 of 0ey Huser needsH and HfeaturesH of the system' !he use-case modelis ane7ective $ay of e=pressing detailed functional Hsoft$are re)uirementsH( therefore use casesmay need to "e trac0ed and maintained as re)uirements( as $ell as perhaps individualstatements $ithin the use case properties $hich state Hconditions or capa"ilities to $hichthe system must conformH'Supplementary Speci*cationsmay contain other Hsoft$arere)uirementsH( such as design constraints or legal or regulatory re)uirements on our system'


33/53

Concepts: +se-Case /iew!o provide a "asis for planning the technical contents of iterations( an architectural vie$called the use-case vieis used in the Re)uirementsdiscipline' !here is only one use-casevie$ of the system( $hich illustrates the use cases and scenarios that encompass

architecturally signi*cant "ehavior( classes( or technical ris0s' !he use-case vie$ is re*nedand considered initially in each iteration'

!he use-case vie$ sho$s an architecturally signi*cant su"set of the use-case model( asu"set of the use cases and actors'

!he analysis( design( and implementation activities su"se)uent to re)uirements arecentered on the notion of an arc!itecture' !he production and validation of thatarchitecture is the main focus of the early iterations( especially during the 1la"orationphase' Architecture is represented "y a num"er of di7erent architectural vie$s( $hich intheir essence are e=tracts illustrating the Harchitecturally signi*cantH elements of themodels'

!here are four additional vie$s# the ogical 4ie( #rocess 4ie( Deloyment 4ie( and>mlementation 4ie' !hese vie$s are handled in the Analysis Designandmplementationdisciplines'

!he architectural vie$s are documented in a %o'tare Arc!itecture Document' 9ou mayadd di7erent vie$s( such as a security vie$( to convey other speci*c aspects of the soft$arearchitecture'So( in essence( architectural vie$s can "e seen as a"stractions or simpli*cations of themodels "uilt( in $hich you ma0e important characteristics more visi"le "y leaving the detailsaside' !he architecture is an important means for increasing the )uality of any model "uiltduring system development'
http://var/www/apps/conversion/tmp/ana_desi/co_swarch.htmhttp://var/www/apps/conversion/tmp/ovu_req.htmhttp://var/www/apps/conversion/tmp/ovu_req.htmhttp://var/www/apps/conversion/tmp/ana_desi/co_swarch.htmhttp://var/www/apps/conversion/itrwkfls/iwf_iie.htmhttp://var/www/apps/conversion/tmp/ana_desi/co_swarch.htmhttp://var/www/apps/conversion/tmp/ana_desi/co_lview.htmhttp://var/www/apps/conversion/tmp/ana_desi/co_pview.htmhttp://var/www/apps/conversion/tmp/ana_desi/co_dview.htmhttp://var/www/apps/conversion/tmp/implemen/co_impvw.htmhttp://var/www/apps/conversion/tmp/ovu_and.htmhttp://var/www/apps/conversion/tmp/ovu_impl.htmhttp://var/www/apps/conversion/artifact/ar_sadoc.htmhttp://var/www/apps/conversion/tmp/ana_desi/co_swarch.htmhttp://var/www/apps/conversion/tmp/ovu_req.htmhttp://var/www/apps/conversion/tmp/ana_desi/co_swarch.htmhttp://var/www/apps/conversion/itrwkfls/iwf_iie.htmhttp://var/www/apps/conversion/tmp/ana_desi/co_swarch.htmhttp://var/www/apps/conversion/tmp/ana_desi/co_lview.htmhttp://var/www/apps/conversion/tmp/ana_desi/co_pview.htmhttp://var/www/apps/conversion/tmp/ana_desi/co_dview.htmhttp://var/www/apps/conversion/tmp/implemen/co_impvw.htmhttp://var/www/apps/conversion/tmp/ovu_and.htmhttp://var/www/apps/conversion/tmp/ovu_impl.htmhttp://var/www/apps/conversion/artifact/ar_sadoc.htm


34/53

Concepts: +ser-Centered Design

Topics

Ihat is user-centered design


35/53

ensures that incremental design carried out in later phases *ts seamlessly into theframe$or0 and that the user interface is consistent in appearance( terminology and concept'Iithin the R;PX( this frame$or0 can "e esta"lished "y using a domain model to ensure thatall terminology and concepts that $ill appear in the user interface are 0no$n andunderstood $ithin the "usiness in general and $ith users in particular' %!here $ill also "esu"sets of the domain model that $ill "e relevant only to speci*c groups of users' Care

should "e ta0en to ensure that the domain model is organied so that these su"sets can "eeasily identi*ed'& As user-interface design progresses in the re)uirements discipline( many ofthe domain classes $ill "e represented as "oundary classes in the interface' !he "oundaryclasses( and the relationships "et$een them( should "e consistent $ith the domain modeland should "e represented consistently through all parts of the system under design' %!hisnot only assists users( "ut also improves reuse of user-interface components'&

&arly user testing

1arly user testing means early prototyping( typically dra$ings and moc0ups descri"ed aslo$-*delity prototypes' i-*delity prototypes $ill follo$ later in the process'Moc0ups can "e used in con+unction $ith use cases to $rite concrete scenarios of use for thesystem under design' !hese can ta0e the form narrative( illustrated narrative %using themoc0ups for illustration&( story"oards( $al0-throughs %$ith users& and the "asis of user focus

groups' Ihile these approaches are unfamiliar to many soft$are developers( they are clearlymore cost e7ective than the discovery of inappropriate design or misunderstoodre)uirements once implementation is under $ay'

Iterative design

O"+ect-oriented development has "ecome synonymous $ith an iterative process' terativedesign is $ell-suited to pro"lems that need a re*nement of understanding and havechanging re)uirements' .ot surprisingly( iterative design is a 0ey component of user-centered design' !his is partly due to the changing needs of users over time( "ut also theinherent comple=ity of producing design solutions that can deal $ith diverse needs'.ote that in user-centered methods( iterative design ta0es place $ithin an integratedframe$or0' Ie deli"erately avoid incremental development( outside of an agreedframe$or0( that might lead to a Ypatch$or0Z solution'

"hy user-centered design

Meeting user needs

nteractive systems rely on their a"ility to accommodate the needs of users for theirsuccess' !his means not only identifying diverse user communities "ut also recogniing therange of s0ills( e=perience and preferences of individual users'Ihile it is tempting for developers and managers to feel that they understand user needs(this is seldom the case in practice' Attention is fre)uently focused on ho$ users ought toperform tas0s rather than ho$ theypreferto perform them' n many cases the issue ofpreference is much more than simply feeling in control( although that is an important issuein itself' Preference $ill also "e determined "y e=perience( a"ility and the conte=t of use'

!hese issues are considered su6ciently important to the design process to $arrant aninternational standard( 3SO [TJ5( entitled human-centred design processes for interactivesystems' !he standard and related issues are discussed in general terms in the remainder ofthis paper'

+ser-interace design

;sers understand and interact $ith a system through its user interface' !he concepts(images and terminology presented in the interface must "e appropriate to usersK needs'


36/53

re)uirements or even the detailed use cases( "ut the characteristics of the users and theenvironments in $hich the systems might operate'

!he user interface must also cater for a potentially $ide range of e=perience along at leastt$o dimensions( computer and domain e=perience( as sho$n in


37/53

instance( training can "e used to reduce the re)uirement for ease of learning in a comple=system' Alternatively a system might "e reduced in its scope in order that it "etter meetsthe core re)uirements of its users %a suggestion made "y Alan Cooper in his "oo0 TheInmates Are Running the Asylum 3COO445&'

0egislation and standards

As part of user-centered design( $e need to consider the s0ills and physical attri"utes ofusers' !hese issues are no$ "eing increasingly em"odied in legislation' !his is mostlydirected at accommodating users $ith disa"ilities' o$ever( ma0ing systems accessi"le to a$ider range of users is generally seen as "ene*ting the user community as a $hole'

!he ta"le "elo$ sho$s the relevant legislation and resources for many parts of the $orld#

Descrition 7eb %ite

A;S!RALA

Disa"ility Discrimination Act http#22$$$'dea0in'edu'au2e=tern2rdlu2ddainde='html

Disa"ility Rights http#22$$$'hreoc'gov'au2disa"ilityrights2inde='html

1;ROP1

!reaty of Amsterdam http#22$$$'edf'unicall'"e2teu2en2inde='asp

1uropean Disa"ility


38/53

and prevention of cumulative stress disorders %also0no$n as repetitive strain in+ury or RS&'A.S is drafting standards concerning humancomputer interaction as part of the nformationnfrastructure Standards Panel %SP& athttp#22$e"'ansi'org2pu"lic2iisp2stdneed2needcat'html

'SO $$$'iso'ch

SO 4T A large series of standards mainly concerned $ithergonomics of $or0stations( "ut also includesguidance on usa"ility %part &' Also the "asis forA.S-


39/53

or features provided "y a product orsystem'

;sers %for each di7erent type orrole&

@no$ledge( s0ill( e=perience( education(training( physical attri"utes( ha"its(preferences( capa"ilities'

1nvironments ard$are( soft$are( materialsG physical and

social environments( relevant standards(technical environment( am"ientenvironment( legislative environment( socialand cultural environment

*able : Conte$t o' use 'rom >% standard 'or user-centered designt is useful to split the user conte=t into its t$o constituent parts %user type and role& and

then to consider the relationships "et$een all four conte=ts#

igure @: Relations!is beteen conte$ts

% ;


40/53

3CO.445' t involves providing a separate Huser roleH for each signi*cant permutation of role(user and environment( then naming the resulting user role $ith a descriptive phrase( ratherthat a simple noun' Compare( for e=ample( the role YCustomerZ $ith the user roles YCasualCustomerZ( YIe" CustomerZ( YRegular CustomerZ and YAdvanced CustomerZ'1ach user role description includes details of the role itself plus its users %referred to as roleincum"ents& and environment' !his approach can "e adopted $ith the R;P "y choosing

actors that correspond to user roles',cenarios2 use cases2 and essential use cases

!he terms scenarios( use cases and essential use cases have a confusing degree of overlapand are used in di7erent design approaches to mean slightly di7erent things'


41/53

press 0eyreturn card

ta0e carddispense cash

ta0e cash

*able : "eneric use case 'or getting cas! 'rom an A*M

!his e=ample details the se)uence of events "et$een the actor and the system( $ith thevertical line "et$een the t$o columns representing the user interface' .otice that $hileConstantine and Loc0$ood recommend this style for essential use cases( this particular usecase is notan essential one' !he reason is that it "ased on the syntactic detail of theinteraction' !hat is( ho#the interaction ta0es place' An essential use case focuses on #hatthe interaction is a"out %called the semantics&' !a"le Q is the essential version of theinteraction'

.ser >ntention %ystem Resonsibility

identify self verify identityo7er choices

choose dispense cash

ta0e cash

*able : Essential use case 'or getting cas! 'rom an A*M!his use case captures the essenceof the getting cash interaction' !he ;ser Action andSystem Response headings have "een replaced "y ;ser ntention and System Responsi"ilityto re8ect the change in emphasis' ,ood interface design centers on user goals andintentionsG these are often hidden in conventional use cases' 1ssential use cases areparticularly useful if#

there are fe$ design constraints %e'g' the implied design constraint of using "an0cards is false&

the system might "e enhanced to use other means of identi*cation %such as some0ind of secure internet access&

there is a desire to create ;se Cases $ithout design constraints( for potential reuse inpro+ects that lac0 these constraints'

o$ever( essential use cases do have their dra$"ac0s' Perfectly straightfor$ard use cases

such as that in !a"le can "e su"+ect to considera"le de"ate $hen it comes to distilling theiressence'


42/53

$ith usa"ility re)uirements to create use-case story"oards( as e=plained in ,uidelines# ;se-Case Story"oard'

%tart by clari'ying t!e use case itsel' - not its user inter'ace1Start "y 0eepingthe description independent of the user interface( especially if the use case isune=plored' !hen( later on( as the use case is understood( the 8o$ of events -story"oard can "e augmented $ith user interface and usa"ility aspects'$from

%uidelines& Use-Case 'toryboard(!his means removing all design or current implementation detail so that only the semantics -the meaning of the interaction - remain' !hen( as various design alternatives are e=plored(syntactic detail - ho$ the interaction ta0es place - is added to the essential use case as atype of realiation' %1ach alternative design is( in e7ect( a realiation of the same essentialuse case'&

!hese use-case story"oards are used as input to the Activity# Prototype the ;ser nterfacetodevelop theuser-interface prototypes'
http://var/www/apps/conversion/artifact/ar_ucstb.htmhttp://var/www/apps/conversion/modguide/md_ucstb.htmhttp://var/www/apps/conversion/modguide/md_ucstb.htmhttp://var/www/apps/conversion/modguide/md_ucstb.htmhttp://var/www/apps/conversion/activity/ac_uip.htmhttp://var/www/apps/conversion/artifact/ar_uiprt.htmhttp://var/www/apps/conversion/artifact/ar_uiprt.htmhttp://var/www/apps/conversion/artifact/ar_ucstb.htmhttp://var/www/apps/conversion/modguide/md_ucstb.htmhttp://var/www/apps/conversion/modguide/md_ucstb.htmhttp://var/www/apps/conversion/modguide/md_ucstb.htmhttp://var/www/apps/conversion/activity/ac_uip.htmhttp://var/www/apps/conversion/artifact/ar_uiprt.htm


43/53

Re*uire!ents: "or#low

Problem

Topics

Purposeo$ to Sta7Ior0,uidelines


44/53

Purpose Top Top

!he purpose of this $or08o$ detail is to#

,ain agreement on the pro"lem "eing solved(

dentify sta0eholders(

De*ne the system "oundaries( and

dentify constraints imposed on the system!he *rst step in any pro"lem analysis is to ma0e sure that all parties involved agree on $hatis the pro"lem that $e are trying to solve $ith our system' n order to avoidmisunderstandings( it is important to agree on common terminology $hich $ill "e used

throughout the pro+ect' 1arly on( $e should "egin de*ning our pro+ect terms in a glossary$hich $ill "e maintained throughout the pro+ect lifecycle'n order to fully understand the pro"lem%s& $e should "e addressing( it is very important to0no$ $ho are our sta0eholders' .ote that some of these sta0eholders -- the users of thesystem -- $ill "e represented "y actorsin our use-case model'

!he Re)uirements Management Plan$ill provide guidance on the re)uirements artifactsthatshould "e developed( the types of re)uirementsthat should "e managed for the pro+ect( there)uirements attri"utesthat should "e collected and the re)uirements tracea"ilitythat $ill"e used in managing the product re)uirements'

!he primary artifact in $hich $e document the pro"lem analysis information is the Nisiondocument( $hich identi*es the high-level user or customer vie$ of the system to "e "uilt' nthe Nision( initial high-level re)uirementsidentify the 0ey featuresit is desired theappropriate solution $ill provide' !hese are typically e=pressed as a set of high-level

featuresthe system might possess in order to solve the most critical pro"lems'@ey sta0eholders should "e involved in gathering the set of features to "e considered( $hichmight "e gathered in a Re)uirements Ior0shop' !he features should "e assigned attri"utessuch as rationale( relative value or priority( source of re)uest and so on( so thatdependencies can "egin to "e managed'

!o determine the initial scope for our pro+ect( the "oundaries of the system must "e agreedupon' !he system analystidenti*es users and systems - represented "y actors- $hich $illinteract $ith the system'
http://var/www/apps/conversion/artifact/ar_gloss.htmhttp://var/www/apps/conversion/workers/wk_sthld.htmhttp://var/www/apps/conversion/artifact/ar_actor.htmhttp://var/www/apps/conversion/artifact/ar_actor.htmhttp://var/www/apps/conversion/artifact/ar_ucmod.htmhttp://var/www/apps/conversion/artifact/ar_ratgl.htmhttp://var/www/apps/conversion/artifact/ars_req.htmhttp://var/www/apps/conversion/tmp/scratch_5/co_reqty.htmhttp://var/www/apps/conversion/artifact/ar_rattr.htmhttp://var/www/apps/conversion/tmp/scratch_5/co_trace.htmhttp://var/www/apps/conversion/artifact/ar_vsion.htmhttp://var/www/apps/conversion/artifact/ar_vsion.htmhttp://var/www/apps/conversion/tmp/scratch_5/co_req.htmhttp://var/www/apps/conversion/glossary.htm#featurehttp://var/www/apps/conversion/glossary.htm#featurehttp://var/www/apps/conversion/tmp/scratch_5/co_reqty.htmhttp://var/www/apps/conversion/tmp/scratch_5/co_reqty.htmhttp://var/www/apps/conversion/workguid/wg_rqwsh.htmhttp://var/www/apps/conversion/artifact/ar_rattr.htmhttp://var/www/apps/conversion/artifact/ar_rattr.htmhttp://var/www/apps/conversion/workers/wk_sysan.htmhttp://var/www/apps/conversion/artifact/ar_actor.htmhttp://var/www/apps/conversion/artifact/ar_gloss.htmhttp://var/www/apps/conversion/workers/wk_sthld.htmhttp://var/www/apps/conversion/artifact/ar_actor.htmhttp://var/www/apps/conversion/artifact/ar_ucmod.htmhttp://var/www/apps/conversion/artifact/ar_ratgl.htmhttp://var/www/apps/conversion/artifact/ars_req.htmhttp://var/www/apps/conversion/tmp/scratch_5/co_reqty.htmhttp://var/www/apps/conversion/artifact/ar_rattr.htmhttp://var/www/apps/conversion/tmp/scratch_5/co_trace.htmhttp://var/www/apps/conversion/artifact/ar_vsion.htmhttp://var/www/apps/conversion/tmp/scratch_5/co_req.htmhttp://var/www/apps/conversion/glossary.htm#featurehttp://var/www/apps/conversion/tmp/scratch_5/co_reqty.htmhttp://var/www/apps/conversion/workguid/wg_rqwsh.htmhttp://var/www/apps/conversion/artifact/ar_rattr.htmhttp://var/www/apps/conversion/workers/wk_sysan.htmhttp://var/www/apps/conversion/artifact/ar_actor.htm


45/53

f you have developed a domain model( a "usiness use-case modelor a "usiness o"+ectmodel( these $ill "e 0ey input( along $ith the "usiness rules( to helping to perform thisanalysis' See also ,uidelines# ,oing from Business Models to Systemsfor more guidance'

!his $or08o$ detail should "e revisited several times during inceptionandearly ela"oration'!hen( throughout the lifecycle of the pro+ect( it should "e revisited as necessary $hilemanaging the inevita"le changesthat $ill occur in our pro+ect( in order to ensure that $e

continue to address the correct pro"lem%s&'

)ow to ,ta Top Top

!he pro+ect mem"ers involved in analying the pro"lem should "e e6cient facilitators andhave e=perience in techni)ues for *nding the pro"lem "ehind the pro"lem' Of course(familiarity $ith the targeted technology is desira"le( "ut it is not essential' Activeinvolvement form various sta0eholdersto the pro+ect is re)uired'

"or# %uidelines Top Top

!he follo$ing are sample techni)ues that can "e applied to *nd the pro"lem "ehind thepro"lem#

Brainstorming


46/53

"or#low Detail: +nderstand ,ta#eholder $eeds

Topics

Purposeo$ to Sta7

Ior0,uidelines

Purpose

!he purpose of this $or08o$ detail is to collect and elicit information from the sta0eholdersof the pro+ect in order to understand $hat their needs really are' !he collected sta0eholderre)uestscan "e regarded as a H$ish listH that $ill "e used as primary input to de*ning thehigh-level featuresof our system( as descri"ed in the Nision($hich drive the speci*cation ofthe soft$are re)uirements( as descri"ed in the use-case model( use casesandsupplementary speci*cations'

!ypically( this activity is mainly performed during iterations in the inceptionandela"oration

phases( ho$ever sta0eholder re)uests should "e gathered throughout the pro+ect "y usingChange Re)uestsfollo$ing the Change Re)uest Management Process'

!he 0ey activity is to elicit sta0eholder re)uestsusing such input as "usiness rules(enhancement re)uests( intervie$sandre)uirements $or0shops' !he primary outputs arecollection%s& of prioritied features and their critical attri"utes( $hich $ill "e used in de*ningthe systemand managing the scopeof the system'

!his information results in a re*nement of the Nisiondocument( as $ell as a "etterunderstanding of the re)uirements attri"utes'Also( during this $or08o$ detail you may startdiscussing the functional re)uirements of the system in terms of its use casesand actors'
http://var/www/apps/conversion/workers/wk_sthld.htmhttp://var/www/apps/conversion/workers/wk_sthld.htmhttp://var/www/apps/conversion/artifact/ar_stnds.htmhttp://var/www/apps/conversion/artifact/ar_stnds.htmhttp://var/www/apps/conversion/artifact/ar_stnds.htmhttp://var/www/apps/conversion/tmp/scratch_5/co_reqty.htmhttp://var/www/apps/conversion/artifact/ar_vsion.htmhttp://var/www/apps/conversion/artifact/ar_vsion.htmhttp://var/www/apps/conversion/artifact/ar_ucmod.htmhttp://var/www/apps/conversion/artifact/ar_uc.htmhttp://var/www/apps/conversion/artifact/ar_sspec.htmhttp://var/www/apps/conversion/itrwkfls/iwf_iii.htmhttp://var/www/apps/conversion/itrwkfls/iwf_iie.htmhttp://var/www/apps/conversion/itrwkfls/iwf_iie.htmhttp://var/www/apps/conversion/artifact/ar_crqst.htmhttp://var/www/apps/conversion/artifact/ar_crqst.htmhttp://var/www/apps/conversion/tmp/conf_mgt/co_revno.htmhttp://var/www/apps/conversion/activity/ac_elstk.htmhttp://var/www/apps/conversion/artifact/ar_brules.htmhttp://var/www/apps/conversion/artifact/ar_crqst.htmhttp://var/www/apps/conversion/workguid/wg_intrv.htmhttp://var/www/apps/conversion/workguid/wg_rqwsh.htmhttp://var/www/apps/conversion/workguid/wg_rqwsh.htmhttp://var/www/apps/conversion/tmp/scratch_5/wfs_defs.htmhttp://var/www/apps/conversion/tmp/scratch_5/wfs_defs.htmhttp://var/www/apps/conversion/tmp/scratch_5/wfs_sco.htmhttp://var/www/apps/conversion/artifact/ar_vsion.htmhttp://var/www/apps/conversion/artifact/ar_rattr.htmhttp://var/www/apps/conversion/artifact/ar_rattr.htmhttp://var/www/apps/conversion/artifact/ar_uc.htmhttp://var/www/apps/conversion/artifact/ar_actor.htmhttp://var/www/apps/conversion/workers/wk_sthld.htmhttp://var/www/apps/conversion/artifact/ar_stnds.htmhttp://var/www/apps/conversion/artifact/ar_stnds.htmhttp://var/www/apps/conversion/tmp/scratch_5/co_reqty.htmhttp://var/www/apps/conversion/artifact/ar_vsion.htmhttp://var/www/apps/conversion/artifact/ar_ucmod.htmhttp://var/www/apps/conversion/artifact/ar_uc.htmhttp://var/www/apps/conversion/artifact/ar_sspec.htmhttp://var/www/apps/conversion/itrwkfls/iwf_iii.htmhttp://var/www/apps/conversion/itrwkfls/iwf_iie.htmhttp://var/www/apps/conversion/artifact/ar_crqst.htmhttp://var/www/apps/conversion/tmp/conf_mgt/co_revno.htmhttp://var/www/apps/conversion/activity/ac_elstk.htmhttp://var/www/apps/conversion/artifact/ar_brules.htmhttp://var/www/apps/conversion/artifact/ar_crqst.htmhttp://var/www/apps/conversion/workguid/wg_intrv.htmhttp://var/www/apps/conversion/workguid/wg_rqwsh.htmhttp://var/www/apps/conversion/tmp/scratch_5/wfs_defs.htmhttp://var/www/apps/conversion/tmp/scratch_5/wfs_defs.htmhttp://var/www/apps/conversion/tmp/scratch_5/wfs_sco.htmhttp://var/www/apps/conversion/artifact/ar_vsion.htmhttp://var/www/apps/conversion/artifact/ar_rattr.htmhttp://var/www/apps/conversion/artifact/ar_uc.htmhttp://var/www/apps/conversion/artifact/ar_actor.htm


47/53

!hose non-functional re)uirements( $hich do not *t easily into the use-case model(should"e documented in the Supplementary Speci*cations'Another important output is an updated ,lossaryof terms to facilitate common voca"ularyamong team mem"ers'

)ow to ,ta Top Top

!he pro+ect mem"ers involved in understanding sta0eholder needs should "e e6cientfacilitators and have e=perience in eliciting information' Of course( familiarity $ith thetargeted technology is desira"le( "ut it is not essential'


!he follo$ing are sample techni)ues that can "e applied to ma0e sure you collect thecorrect and relevant information from the sta0eholders#

ntervie$s

Re)uirements Ior0shop

Brain-storming and idea reduction

;se-Case Ior0shop

Story"oarding Role playing

Revie$ of e=isting re)uirementsSee also#

Re)uirements# Overvie$

Ihite Paper# Applying Re)uirements Management $ith ;se Cases

Concepts# ;ser-Centered Design
http://var/www/apps/conversion/tmp/scratch_5/co_req.htmhttp://var/www/apps/conversion/artifact/ar_ucmod.htmhttp://var/www/apps/conversion/artifact/ar_ucmod.htmhttp://var/www/apps/conversion/artifact/ar_sspec.htmhttp://var/www/apps/conversion/artifact/ar_gloss.htmhttp://var/www/apps/conversion/workguid/wg_intrv.htmhttp://var/www/apps/conversion/workguid/wg_rqwsh.htmhttp://var/www/apps/conversion/workguid/wg_brnst.htmhttp://var/www/apps/conversion/workguid/wg_ucwsh.htmhttp://var/www/apps/conversion/workguid/wg_stbd.htmhttp://var/www/apps/conversion/workguid/wg_rlpl.htmhttp://var/www/apps/conversion/workguid/wg_revxr.htmhttp://var/www/apps/conversion/tmp/ovu_req.htmhttp://var/www/apps/papers/apprmuc.htmhttp://var/www/apps/conversion/tmp/scratch_5/co_ucd.htmhttp://var/www/apps/conversion/tmp/scratch_5/co_req.htmhttp://var/www/apps/conversion/artifact/ar_ucmod.htmhttp://var/www/apps/conversion/artifact/ar_sspec.htmhttp://var/www/apps/conversion/artifact/ar_gloss.htmhttp://var/www/apps/conversion/workguid/wg_intrv.htmhttp://var/www/apps/conversion/workguid/wg_rqwsh.htmhttp://var/www/apps/conversion/workguid/wg_brnst.htmhttp://var/www/apps/conversion/workguid/wg_ucwsh.htmhttp://var/www/apps/conversion/workguid/wg_stbd.htmhttp://var/www/apps/conversion/workguid/wg_rlpl.htmhttp://var/www/apps/conversion/workguid/wg_revxr.htmhttp://var/www/apps/conversion/tmp/ovu_req.htmhttp://var/www/apps/papers/apprmuc.htmhttp://var/www/apps/conversion/tmp/scratch_5/co_ucd.htm


48/53

"or#low Detail: Deine the ,yste!

Topics

Purposeo$ to Sta7

Ior0,uidelines

Purpose


Align the pro+ect team in their understanding of the system'

Perform a high-level analysis on the results of collecting sta0eholder re)uests'

Re*ne theNisionto include the features to include in the system( along $ithappropriate attri"utes'

Re*ne theuse-case model(to include outlined use cases'

More formally document the results in models and documents'Pro"lem Analysisand activities for;nderstanding Sta0eholder .eedscreate early iterationsof 0ey system de*nitions( including the features de*ned in the Nisiondocument( a *rstoutline to the use-case modeland the Re)uirements Attri"utes' n De*ning the System you$ill focus on identifying actorsanduse casesmore completely( and e=pand the glo"al non-functional re)uirements as de*ned in the Supplementary Speci*cations'f you have developed a "usiness use-case modeland "usiness o"+ect model( see also,uidelines# ,oing from Business Models to Systemsfor more guidance'

!ypically( this is primarily performed in iterations during the inceptionand ela"orationphases( ho$ever it may "e revisited as needed $hen managing scopeand responding tochanging re)uirements(as $ell as other changing conditions'
http://var/www/apps/conversion/artifact/ar_stnds.htmhttp://var/www/apps/conversion/artifact/ar_stnds.htmhttp://var/www/apps/conversion/artifact/ar_vsion.htmhttp://var/www/apps/conversion/artifact/ar_vsion.htmhttp://var/www/apps/conversion/artifact/ar_rattr.htmhttp://var/www/apps/conversion/artifact/ar_rattr.htmhttp://var/www/apps/conversion/artifact/ar_ucmod.htmhttp://var/www/apps/conversion/artifact/ar_ucmod.htmhttp://var/www/apps/conversion/artifact/ar_ucmod.htmhttp://var/www/apps/conversion/artifact/ar_uc.htmhttp://var/www/apps/conversion/artifact/ar_uc.htmhttp://var/www/apps/conversion/tmp/scratch_5/wfs_anpr.htmhttp://var/www/apps/conversion/tmp/scratch_5/wfs_anpr.htmhttp://var/www/apps/conversion/tmp/scratch_5/wfs_unsh.htmhttp://var/www/apps/conversion/tmp/scratch_5/wfs_unsh.htmhttp://var/www/apps/conversion/artifact/ar_vsion.htmhttp://var/www/apps/conversion/artifact/ar_ucmod.htmhttp://var/www/apps/conversion/artifact/ar_rattr.htmhttp://var/www/apps/conversion/artifact/ar_actor.htmhttp://var/www/apps/conversion/artifact/ar_uc.htmhttp://var/www/apps/conversion/artifact/ar_uc.htmhttp://var/www/apps/conversion/artifact/ar_sspec.htmhttp://var/www/apps/conversion/artifact/ar_bucm.htmhttp://var/www/apps/conversion/artifact/ar_bom.htmhttp://var/www/apps/conversion/modguide/md_bmtse.htmhttp://var/www/apps/conversion/itrwkfls/iwf_iii.htmhttp://var/www/apps/conversion/itrwkfls/iwf_iii.htmhttp://var/www/apps/conversion/itrwkfls/iwf_iie.htmhttp://var/www/apps/conversion/tmp/scratch_5/wfs_sco.htmhttp://var/www/apps/conversion/tmp/scratch_5/wfs_mnch.htmhttp://var/www/apps/conversion/tmp/scratch_5/wfs_mnch.htmhttp://var/www/apps/conversion/artifact/ar_stnds.htmhttp://var/www/apps/conversion/artifact/ar_vsion.htmhttp://var/www/apps/conversion/artifact/ar_rattr.htmhttp://var/www/apps/conversion/artifact/ar_ucmod.htmhttp://var/www/apps/conversion/artifact/ar_uc.htmhttp://var/www/apps/conversion/tmp/scratch_5/wfs_anpr.htmhttp://var/www/apps/conversion/tmp/scratch_5/wfs_unsh.htmhttp://var/www/apps/conversion/artifact/ar_vsion.htmhttp://var/www/apps/conversion/artifact/ar_ucmod.htmhttp://var/www/apps/conversion/artifact/ar_rattr.htmhttp://var/www/apps/conversion/artifact/ar_actor.htmhttp://var/www/apps/conversion/artifact/ar_uc.htmhttp://var/www/apps/conversion/artifact/ar_sspec.htmhttp://var/www/apps/conversion/artifact/ar_bucm.htmhttp://var/www/apps/conversion/artifact/ar_bom.htmhttp://var/www/apps/conversion/modguide/md_bmtse.htmhttp://var/www/apps/conversion/itrwkfls/iwf_iii.htmhttp://var/www/apps/conversion/itrwkfls/iwf_iie.htmhttp://var/www/apps/conversion/tmp/scratch_5/wfs_sco.htmhttp://var/www/apps/conversion/tmp/scratch_5/wfs_mnch.htm


49/53

)ow to ,ta Top Top

All mem"ers of the pro+ect team should participate'


!he follo$ing are sample techni)ues that can "e applied# Re)uirements Ior0shop

;se-Case Ior0shop

Story"oarding
http://var/www/apps/conversion/workguid/wg_rqwsh.htmhttp://var/www/apps/conversion/workguid/wg_ucwsh.htmhttp://var/www/apps/conversion/workguid/wg_stbd.htmhttp://var/www/apps/conversion/workguid/wg_rqwsh.htmhttp://var/www/apps/conversion/workguid/wg_ucwsh.htmhttp://var/www/apps/conversion/workguid/wg_stbd.htm


50/53

"or#low Detail: Manage the ,cope o the ,yste!

Topics

Purposeo$ to Sta7

Ior0,uidelines

Purpose


Prioritie and re*ne input to the selection of featuresandre)uirementsthat are to "eincluded in the current iteration'

De*ne the set of use cases%or scenarios& that represent some signi*cant( centralfunctionality'

De*ne $hichre)uirement attri"utesand tracea"ilitiesto maintain'!he scope of a pro+ect is de*ned "y the set of re)uirements allocated to it' Managing pro+ectscope to *t the availa"le resources %time( people( and money& is 0ey to managing successful

pro+ects' Managing scope is a continuous activity that re)uires iterative or incrementaldevelopment( $hich "rea0s pro+ect scope into smaller more managea"le pieces';sing re)uirement attri"utes( such as priority( e7ort( and ris0( as the "asis for negotiatingthe inclusion of a re)uirement is a particularly useful techni)ue for managing scope'


51/53

Pro+ect scope should "e managed continuously throughout the pro+ect' A "etterunderstanding of system functionality is o"tained from identifying most actorsand usecases'.on-functional re)uirements( $hich do not *t in the use-case model( should "edocumented in the Supplementary Speci*cations'!he system analystshould determinevalues of priority( e7ort( cost( ris0 values etc'( from the appropriate sta0eholders( to collectin the repository of re)uirements attri"utes'!hese $ill "e used "y the Pro+ect Managerin

planning the iterationsand ena"les the soft$are architectto identify thearchitecturallysigni*cant use cases( de*ning the use-case vie$of the architecturein the Soft$areArchitecture Document'

)ow to ,ta Top Top

!he people involved in this $or08o$ detail should all "e mem"ers of the architecture team'


!he architecture team $ill lead a session to discuss ho$ to "est prioritie the re)uirements'

Topics

Purpose

o$ to Sta7Ior0,uidelines

Re*uire!ents: Activity Overview
http://var/www/apps/conversion/artifact/ar_actor.htmhttp://var/www/apps/conversion/artifact/ar_uc.htmhttp://var/www/apps/conversion/artifact/ar_uc.htmhttp://var/www/apps/conversion/artifact/ar_uc.htmhttp://var/www/apps/conversion/artifact/ar_sspec.htmhttp://var/www/apps/conversion/artifact/ar_sspec.htmhttp://var/www/apps/conversion/workers/wk_sysan.htmhttp://var/www/apps/conversion/workers/wk_sthld.htmhttp://var/www/apps/conversion/artifact/ar_rattr.htmhttp://var/www/apps/conversion/artifact/ar_rattr.htmhttp://var/www/apps/conversion/workers/wk_projm.htmhttp://var/www/apps/conversion/tmp/manageme/wfs_plan.htmhttp://var/www/apps/conversion/workers/wk_archt.htmhttp://var/www/apps/conversion/activity/ac_priuc.htmhttp://var/www/apps/conversion/activity/ac_priuc.htmhttp://var/www/apps/conversion/activity/ac_priuc.htmhttp://var/www/apps/conversion/tmp/scratch_5/co_ucv.htmhttp://var/www/apps/conversion/tmp/scratch_5/co_ucv.htmhttp://var/www/apps/conversion/tmp/ana_desi/co_swarch.htmhttp://var/www/apps/conversion/tmp/ana_desi/co_swarch.htmhttp://var/www/apps/conversion/artifact/ar_sadoc.htmhttp://var/www/apps/conversion/artifact/ar_sadoc.htmhttp://var/www/apps/conversion/artifact/ar_sadoc.htmhttp://var/www/apps/conversion/artifact/ar_actor.htmhttp://var/www/apps/conversion/artifact/ar_uc.htmhttp://var/www/apps/conversion/artifact/ar_uc.htmhttp://var/www/apps/conversion/artifact/ar_sspec.htmhttp://var/www/apps/conversion/workers/wk_sysan.htmhttp://var/www/apps/conversion/workers/wk_sthld.htmhttp://var/www/apps/conversion/artifact/ar_rattr.htmhttp://var/www/apps/conversion/workers/wk_projm.htmhttp://var/www/apps/conversion/tmp/manageme/wfs_plan.htmhttp://var/www/apps/conversion/workers/wk_archt.htmhttp://var/www/apps/conversion/activity/ac_priuc.htmhttp://var/www/apps/conversion/activity/ac_priuc.htmhttp://var/www/apps/conversion/tmp/scratch_5/co_ucv.htmhttp://var/www/apps/conversion/tmp/ana_desi/co_swarch.htmhttp://var/www/apps/conversion/artifact/ar_sadoc.htmhttp://var/www/apps/conversion/artifact/ar_sadoc.htm


52/53

Re*uire!ents: Artiact Overview

!he roles and the artifacts developed in the Re)uirements discipline'

Re*uire!ents: %uidelines Overview ;se Case

Activity Diagram in the ;se-Case Model

Actor

;se-Case Model

Actor-,eneraliation

Communicate-Association

1=tend-Relationship

nclude-Relationship

;se-Case-,eneraliation

;se-Case Diagram

Re)uirements Management Plan

;se-Case Pac0age

Soft$are Architecture Document

Soft$are Re)uirements Speci*cation

Boundary Class
http://var/www/apps/conversion/modguide/md_uc.htmhttp://var/www/apps/conversion/modguide/md_actd.htmhttp://var/www/apps/conversion/modguide/md_actor.htmhttp://var/www/apps/conversion/modguide/md_ucmod.htmhttp://var/www/apps/conversion/modguide/md_actgn.htmhttp://var/www/apps/conversion/modguide/md_comas.htmhttp://var/www/apps/conversion/modguide/md_exrel.htmhttp://var/www/apps/conversion/modguide/md_incl.htmhttp://var/www/apps/conversion/modguide/md_ucgen.htmhttp://var/www/apps/conversion/modguide/md_ucdgr.htmhttp://var/www/apps/conversion/modguide/md_ucdgr.htmhttp://var/www/apps/conversion/modguide/md_rmp.htmhttp://var/www/apps/conversion/modguide/md_ucpkg.htmhttp://var/www/apps/conversion/modguide/md_sad.htmhttp://var/www/apps/conversion/modguide/md_srs.htmhttp://var/www/apps/conversion/modguide/md_bcls.htmhttp://var/www/apps/conversion/modguide/md_uc.htmhttp://var/www/apps/conversion/modguide/md_actd.htmhttp://var/www/apps/conversion/modguide/md_actor.htmhttp://var/www/apps/conversion/modguide/md_ucmod.htmhttp://var/www/apps/conversion/modguide/md_actgn.htmhttp://var/www/apps/conversion/modguide/md_comas.htmhttp://var/www/apps/conversion/modguide/md_exrel.htmhttp://var/www/apps/conversion/modguide/md_incl.htmhttp://var/www/apps/conversion/modguide/md_ucgen.htmhttp://var/www/apps/conversion/modguide/md_ucdgr.htmhttp://var/www/apps/conversion/modguide/md_rmp.htmhttp://var/www/apps/conversion/modguide/md_ucpkg.htmhttp://var/www/apps/conversion/modguide/md_sad.htmhttp://var/www/apps/conversion/modguide/md_srs.htmhttp://var/www/apps/conversion/modguide/md_bcls.htm


53/53

;se-Case Story"oard

;ser nterface %,eneral&
http://var/www/apps/conversion/modguide/md_ucstb.htmhttp://var/www/apps/conversion/modguide/md_uig.htmhttp://var/www/apps/conversion/modguide/md_ucstb.htmhttp://var/www/apps/conversion/modguide/md_uig.htm

metolologia- requerimientos

Documents