requirements lifecycle management is basically just the upkeep of all of the information and
the requirements related to a specific project or initiative that we are currently undertaking
so this particular knowledge area describes the tasks that B is perform in order to manage and
maintain requirements and design information from inception to retirement so we'll talk a
little bit more about what that means later but those are two important terms that you're going
to want to understand is that as soon as a need is identified that is the inception and in retirement
is basically can sometimes be further passed the project being closed but we'll talk about
that and so the purpose of this knowledge area is to ensure that business that the business
stakeholder and solution requirements and designs so these are the various levels of requirements
so business requirements take auto promise and solution requirements and designs are aligned
to one another and that the solution implements them so we're basically hoping to ensure that
the information is available for future use and so Babic basically describes you know the
requirements lifecycle as something that begins with representation of a need or representation
of a business need right we all know that requirements are a representation of a need and
it continues through the development of a solution right and our designs are our solutions and then
it ends when a solution and the requirements that represented are retired so this goes back to when
we talked about retirement up here retirement is not necessarily when the project closes it
is when a solution that uses those requirement is actually retired alright and another thing to note
is that the concept of a requirements life cycle is different from a methodology so when about you
know a traditional waterfall methodology in the in the phases you know you've got your initiation
and analysis of a criminalist that's the sdlc right so that's a little bit different from the
requirements lifecycle and this is just a quick image of a potential requirements lifecycle not
every requirement goes through the same lifecycle so you you start with you know maybe a requirement
and this is one that's a little mature so this one is actually being assessed so we're determining
whether or not we're bringing it forward if we do yes then you're gonna get your approval or send
it off for approval once you get the approval if it's approved again you're either going to
maintain it or trace over or prioritize it so if it doesn't if it doesn't make the assessment right
you're just gonna continue that cycle again so if it's no here you're just gonna keep on assessing
it until you're able to move it forward and then if it's not approved then you need to go back to
the drawing board and start all over so this is a you know a typical requirements lifecycle but this
doesn't this is kind of like once it reaches assessment there's several other states that
it would probably be entered before it goes into that into assessment so the requirements lifecycle
management knowledge area typically includes well according to Babic it occludes traced
requirements maintained requirements prioritized requirements assessed requirements changes and
approve requirements so tracing is basically where we analyze and maintain the relationships between
requirements design in the solution components maintaining the requirements is where we're
making sure that the requirements and designs are accurate and current right so as information
changes or information updates we need to make sure that we are updating our documentation and
any information that is being used for work down the line so we're maintaining those requirements
prioritize requirements is where we're actually assessing the value urgency and risk associated
with particular requirements and designs so most of us associate this with you know prioritizing a
backlog or you know having certain dates that represents the urgency for a particular piece
of work that's being done or the work that you know we want to make sure that the work that's
most important gets done first and then assess requirements changes is where we evaluate new
and changing sticker requirements to determine if they actually need to be acted upon and then
approve requirements is where we assess and work with the stakeholders involved in the governance
process in order to reach an approval and a gray net so here's our business analysis core
concept model it basically describes how the core concept model is used within the context
of the requirements lifecycle management each week I outside of the first week I've skip past
this it's good for you to know as a supplement information but we talked about it during week
one and then once you get more familiar with the various tasks within the requirements lifecycle
management I recommend going back and just going over those core concepts to see how you can apply
them to this particular knowledge area and so our inputs for the requirements lifecycle
management knowledge area include requirements designs proposed change and requirements that
are actually verified and then again here are five tasks that we're going to be performing
in this knowledge area and so our outputs are all all of our outputs are simply going to be
requirements and designs but they'll be in various states so the various states would
include Tres requirements and designs maintain requirements and designs prioritize requirements
and designs and then we're also going to have some requirements change assessments
requirements and design change assessments and then approve requirements and designs