Implementing the Rational Unified Process with S-Miner Vision Definition Baseline Plan

Transcription

1 Implementing the Ratinal Unified Prcess with S-Miner Visin Definitin Baseline Plan Cpyright PROFECI 1/10 This dcument is the prperty f PROFECI limited( ). The infrmatin cntained reflects the knw-hw and the

2 INTRODUCTION 3 REQUIREMENTS MANAGEMENT DISCIPLINE 3 S-MINER 3 RUP CONTEXT 3 REQUIREMENTS MANAGEMENT OVERVIEW 4 DEVELOPING THE VISION 6 INTRODUCTION PROCESS 6 6 ERS ELICITATION 6 VISION DEFINITION 7 S-MINER SUPPORT FOR VISION DEFINITION 8 DERIVING S-MINER VISION DEFINITION META-MODEL FOR YOUR OWN QUALITY PROGRAM 9 CONTINUING TO NEXT PHASES 10 Cpyright PROFECI 2/10 This dcument is the prperty f PROFECI limited( ). The infrmatin cntained reflects the knw-hw and the

3 Intrductin This dcument fcuses n requirements engineering in the early phase f a prject which is cmmnly referred as Definitin f the visin in the RUP (Ratinal Unified Prcess) methdlgy. It dcuments a generic fundatin t visin definitin implemented as a S-Miner s meta-mdel which can be used as it is t quickly initiate a RUP r which can serve as a custmizable basis fr specific instantiatins in any cmpany cntext. It is part f a mre glbal generic fundatin t requirements management which is als implemented as a S-Miner s meta-mdel. The verall generic fundatin t requirements management is dedicated t prduct s engineering teams r IT systems architects wh have t identify, clarify, review, finalize and cntinually mnitr the functins and features that make up prduct/applicatin requirements baselines that they are maintaining. Requirements Management Discipline Requirements management is a systematic apprach t dcumenting, rganizing and tracking changes t the requirements f a system. A requirement is defined as a cnditin r capability t which the system must cnfrm. Requirements management is a systematic apprach t: Elicit, rganize, and dcument the requirements f the system, and Establish and maintaining agreement between the custmer and the prject team n the changing requirements f the system. Prduct engineering teams / IT systems architects must use a frmal, standard apprach fr managing all requirements. This apprach must be part f an verall quality assurance prgram which purpse is t prmte, develp and deply best practices ver design phases f cmputer systems. S-Miner S-Miner has been develped frm ur wide experience as cnsultant in research & develpment and specificatin phases f varius kind f systems in varius dmains with varius custmers methds, practices, dcuments layuts, and quality assurance prgrams. Since its develpment started in 1999, S-Miner has gained a capacity t virtually integrate any kind f engineering methds in any kind f dmain. This utstanding custmizatin capacity is brught by a meta-mdel mechanism which allws t teach the tl with yur wn quality assurance prgram (methd, vcabulary, frmalism, ) s that it strictly implements yur quality assurance prgram and ptimizes its deplyment and disseminatin amng yur teams. RUP Cntext The fllwing has been defined t specifically supprt the applicatin f the RUP methdlgy which is based n the fllwing key best practices: Creating and maintaining a clear statement f the requirements thrugh a frmal, welldefined prcess. Requirements are identified frm several different surces, bth external and internal. Stakehlders requests are initially captured as enhancement requests (ERs). This dcument details the prcess by which ERs are cllected, rganized and reviewed befre being further analyzed and refined int features and ther requirement types that serve as the cntract with stakehlders as t the cntents f the release f a prduct/applicatin. Cpyright PROFECI 3/10 This dcument is the prperty f PROFECI limited( ). The infrmatin cntained reflects the knw-hw and the

4 Defining and managing by requirement types Traditinally, requirements are lked upn as statements f text that describe a cnditin r capability t which the system must cnfrm. In rder t perfrm effective requirements management, it is imprtant t extend what is maintained as requirements beynd nly the detailed sftware requirements. Therefre, the cncept f requirements types allws t separate the different levels f abstractin and purpses f the requirements. Creating and maintaining applicable attributes fr each requirement type. In rder t manage requirements mre effectively, specific attributes are defined fr each requirement type. Attributes are data elements that prvide additinal infrmatin abut an item. Attributes are used t relate the feature r requirements data t ther types f prject infrmatin. The attributes are used t track, priritize, and manage the requirements. Fr example, the attribute, unique identifier will help track the requirement, the pririty r risk level may help t identify key requirements that may need t be addressed in an early iteratin r a requirement that may require mre intensive testing. Maintaining and updating a requirements repsitry. Requirements are maintained in a centralized requirements repsitry and kept current during the prject. Creating and maintaining traceability t ther requirements and ther prject artifacts. Traceability is a mechanism fr ensuring requirements cverage frm prject start-up t prject cmpletin. Tracking key artifacts t the requirements that they realize r verify ensures that agreed-upn bjectives and functinality are met and integrated int the slutin as the prject prgresses. Furthermre, traceability prvides with the ability t assess mre accurately the impact f a change r enhancement request since the change can be traced t all impacted prject artifacts. Cnducting cverage reviews during the prject t verify that all requirements are being addressed in the slutin. These reviews identify and analyze requirements that are missing supprting artifact references in the requirements cverage reprts. Cntrlling changes t the system requirements. Requirements Management Overview The requirements discipline revlves arund understanding the needs f prduct stakehlders, analyzing thse requirements, and rganizing them in such a manner that they may be best understd and used by fllw-n activities. A clear understanding and agreement n requirements is essential fr the develpment f any prduct/applicatin. Thrughut the lifecycle f a prduct/applicatin, enhancement requests (ERs) are submitted by stakehlders. At pre-defined intervals, ERs are apprved, rejected r delayed. During the inceptin phase f a prject, apprved ERs are distilled int new prduct features r enhancements t existing features. The selected features must be precisely identified / described and then serve as a basis fr an impact analysis in rder t understand the affect f the features n the existing prduct. A cllectin f features that are realizable within a given time frame is accumulated, reviewed, and apprved as part f a Visin dcument fr the prject. Cpyright PROFECI 4/10 This dcument is the prperty f PROFECI limited( ). The infrmatin cntained reflects the knw-hw and the

5 There are several different types f requirements. Features may be functinal r nn-functinal in nature. Functinal features will always be traced frm ne r mre use cases. A use case represents the interactin between the system and any number f actrs. Nn-functinal features will always be traced frm ne r mre supplementary specificatins. A use case is always cmpsed f a series f flws, including a basic flw plus any number f alternate flws. The cmbinatin f a series f flws that results in a cmplete path thrugh a use case is a use case scenari. Finer-grained requirements that specify the behavir f the system may be captured as business rules that trace t specific use case flws. Als any requirements pertaining t state f the system may be captured as infrmatin needs. All f the abve types f requirements must be managed in a requirements repsitry, and changes t them must be strictly cntrlled. All requirements types have an assciated state and fllw the same state transitins that ccur at pre-defined pints in the requirements management prcess. Once a requirement has been apprved, it can nly be changed as a result f an apprved and scheduled ER. The prject team uses requirements traceability t ensure that all assciated prject artifacts are mdified t include the apprved change t the requirement. Peridically audits f the requirements data are cnducted. Audits include such things as traceability and cverage reviews and reviews f the revisin histry f apprved requirements t ensure that n changes have been made withut apprval. Cpyright PROFECI 5/10 This dcument is the prperty f PROFECI limited( ). The infrmatin cntained reflects the knw-hw and the

6 Develping the visin Intrductin In the inceptin phase fr a prject, a cllectin f stakehlders requests in the frm f Enhancement Requests (ERs) and their riginating needs is cnsidered fr a prduct release. ERs t be cnsidered tgether with the assciated new r impacted features will then serve t feed the Visin dcument fr the release. This dcument will have t be agreed upn by all the stakehlders. The Visin defines the stakehlders view f the prduct t be develped, specified in terms f the stakehlders key needs and features. Cntaining the prpsed features fr a prduct release, it serves as a cntract between the prject team and the stakehlders. It will be the basis fr all subsequent wrk fr the release. The Visin sets the scpe fr a release. A cmpleted Visin is a pre-requisite fr exiting the inceptin phase and entering the elabratin phase fr a prject. A prject withut a visin is a prject with n directin, and as such is an unacceptable prpsitin. ERs elicitatin This first part f the prcess invlves Business Analyst teams and Stakehlders. Prcess On the basis f an identificatin f each stakehlder (S-Miner ) and f the prduct(s) (S-Miner ) r applicatin(s) (S-Miner ) Stakehlders Needs (new & evlutin) are identified and their descriptin is captured in a centralized repsitry (S-Miner ) On the basis f a stakehlders needs selectin, analysis and cnslidatin Enhancement Request are then defined and their descriptin is captured in a centralized repsitry (S-Miner ). Cpyright PROFECI 6/10 This dcument is the prperty f PROFECI limited( ). The infrmatin cntained reflects the knw-hw and the

7 Prviding this first set f visin elements, a first dcumentatin set is autmatically prduced (S- Miner ). It cntains : the pre-visin dcument describing stakehlders needs and the prpsed enhancement requests several matrixes t supprt cverage & impact analysis Stakehlder / ER f interest ER / Originating Needs This first dcumentatin set must then be validated by the stakehlders grup befre ging n t next step. Visin definitin Given a set f ERs fr a release, System Analyst teams distill a set f features that need t be included/mdified in the prduct(s) / applicatin(s) t satisfy the ERs. This prcess requires cllabratin with the stakehlders t agree n the features t be implemented. As features are identified and described, the System Analysts capture them in a centralized repsitry (S-Miner ). Each feature (new & evlutin f existing nes) traces back t the ER frm which it is derived. In additin t capturing the features, the System Analysts builds the visin dcument by extracting relevant infrmatin (S-Miner ) frm the centralized repsitry (S-Miner ) and by adding additinal prse t cnfrm t a visin dcument template (S-Miner ) issued frm the glbal quality assurance prgram. Prviding this secnd set f visin elements, the Visin Dcumentatin set is autmatically prduced (S-Miner ). It cntains : the Visin dcument describing the features t be develped fr each prduct / applicatin impacted by the release. It als prvides the full set f riginating stakehlders needs and enhancement requests in rder t prvide detailed descriptin f the cntract between the teams invlved in next phases with stakehlders. Cpyright PROFECI 7/10 This dcument is the prperty f PROFECI limited( ). The infrmatin cntained reflects the knw-hw and the

8 several matrixes t supprt cverage & impact analysis Stakehlder / ER f interest ER / Originating Needs Stakehlder / Features f interest Stakehlder / Prducts f interest Features / riginating ERs Features / riginating Needs Prducts / riginating ERs Prducts / riginating Needs This dcumentatin set must then be validated by the stakehlders grup befre ging n t next phase. S-Miner supprt fr Visin Definitin S-Miner meta-mdel fr Visin Definitin prvides the necessary cncepts fr managing a single centralized repsitry fr : Stakehlders identificatin & descriptin Stakehlders needs identificatin & descriptin Enhancement requests identificatin & descriptin Prducts / Applicatins identificatin & descriptin Prduct s features identificatin & descriptin Prduct s release identificatin & descriptin It als prvides all the necessary features t capture traceability and infrmatin s relatinships : ERs / Stakehlders Needs Features / ERs Release / ERs Fr each kind f infrmatin managed, S-Miner autmatically prvides : lifecycle supprt (draft, submitted, validated, ), versin management, changes mnitring, repsitry cmparisn and synchrnizatin, S-Miner als prvides advanced publishing and dcument mdeling features. It allws t build any kind f dcuments by aggregating infrmatin extracted frm the repsitry and external surces within yur custm templates t fit yur cmpany s lk n feel. Cpyright PROFECI 8/10 This dcument is the prperty f PROFECI limited( ). The infrmatin cntained reflects the knw-hw and the

9 Deriving S-Miner Visin Definitin meta-mdel fr yur wn quality prgram S-Miner Visin Definitin meta-mdel can easily be custmized t add / change cncepts, attributes, It can bth prvide a ready t use slutin fr implementing RUP prcess, r, a basis t be imprved in rder t take yur wn quality assurance prgram specificities. Cpyright PROFECI 9/10 This dcument is the prperty f PROFECI limited( ). The infrmatin cntained reflects the knw-hw and the

10 Cntinuing t next phases S-Miner Visin Definitin meta-mdel integrates int a mre glbal RUP meta-mdel which supprts the whle RUP prcess. When used with the full RUP meta-mdel it is extended with: Actrs identificatin & descriptin Use Cases identificatin & descriptin Detailed Use cases definitin Business Rules identificatin, descriptin & allcatin Cpyright PROFECI 10/10 This dcument is the prperty f PROFECI limited( ). The infrmatin cntained reflects the knw-hw and the