The inception phase of a RUP project is focused on ensuring that all project stakeholders have a clear understanding of the scope of the project. Business and system requirements are of paramount importance in this phase. The primary purpose of inception can be defined as:
·
To formulate the
project scope
·
To establish the
business case for a system
·
To achieve concurrence
among all stakeholders on the objectives
·
To assess risk
·
To synthesize a
candidate architecture
Because the emphasis of the
inception phase is on understanding requirements and determining risk, primary
artifacts include:
·
Vision
·
(Initial) Software
Development Plan
·
Business Case
·
(Initial) Use-Case
Model
·
Tailored Process
Specification
·
Risk list
·
Risk Management Plan
Other optional artifacts may
include:
·
Business Model
·
Domain Model
·
Architectural proof of
concept
1) [DISPLAY2]<FileSystem_File.FullName>[ENDDISP3]
As the project progresses, more
requirements will be defined and at a greater level of detail.
* the number of level 0 and level
1 requirements stabilizing towards the end of inception
Symptom |
Response |
The chart keeps increasing |
The scope hasn’t yet stabilized. This may indicate that inception hasn’t completed. |
The number of level 1 requirements continues to increase as the number of level 0 requirements stabilized. |
This indicates that the project is gaining a better understanding of the defined scope. |
2) [DISPLAY7]<FileSystem_File.FullName>[ENDDISP8]
This chart shows the types of
information recorded in RequisitePro and the growth of each type of
information. Is this the type of
information your company produces?
Are these the growth curves your company expects?
Symptom |
Response |
The number of features stabilizes. |
This indicates we’ve settled on the project scope. |
The number of use case requirement types is increasing. |
This may indicate we’re adding detail. |
3) [DISPLAY12]<FileSystem_File.FullName>[ENDDISP13]
Fewer requirements should have a
status of proposed as inception draws to a close.
Symptom |
Response |
The majority of requirements are being approved. |
We’re gaining consensus on the requirements for this project. |
None are incorporated. |
We haven’t done any prototyping during inception. |
4) [DISPLAY17]<FileSystem_File.FullName>[ENDDISP18]
Towards the end of inception, the
understanding of the requirements should become clearer. Information about ownership and planned
iteration should become more complete.
Symptom |
Response |
The distribution is unbalanced. |
This indicates that nobody has really made tough decisions about the priority of the requirements. |
No requirements have a null priority. |
Some thinking has been done, but not enough. |
5) [DISPLAY22]<FileSystem_File.FullName>[ENDDISP23]
Towards the end of inception, the
understanding of the requirements should become clearer. Information about ownership and planned
iteration should become more complete.
Symptom |
Response |
The planned work isn’t evenly distributed across the iterations. |
The shape of this chart will depend upon the type of information your company tracks and when that information is produced. In this sample project the first construction iteration is #3, which is when most of the work is done |
Roughly 20% of the requirements are being delivered in the Elaboration phase. |
This indicates that the architecture is relatively stable. |
[OPEN1]C:FileSystem_File:FileSys:File:FileName=^S${PJC_WEBPATH}\x5CPublishedViews\x5CPublic\x5CTrend\x20of\x20Level\x200\x20and\x20Level\x201\x20Requirements.PNG
[DISPLAY2]F:FileSystem_File:FileSys:File::FilePath:SAAA5b:
[ENDDISP3]F:FileSystem_File:FileSys:File::FilePath:SAAA5b:
[DISPLAY4]F:FileSystem_File:FileSys:File::Image:GAA:
[ENDDISP5]F:FileSystem_File:FileSys:File::Image:GAA:
[OPEN6]C:FileSystem_File:FileSys:File:FileName=^S${PJC_WEBPATH}\x5CPublishedViews\x5CPublic\x5CTrend\x20of\x20Level\x200\x20and\x20Level\x201\x20Requirements\x20with\x20Type.PNG
[DISPLAY7]F:FileSystem_File:FileSys:File::FilePath:SAAA5b:
[ENDDISP8]F:FileSystem_File:FileSys:File::FilePath:SAAA5b:
[DISPLAY9]F:FileSystem_File:FileSys:File::Image:GAA:
[ENDDISP10]F:FileSystem_File:FileSys:File::Image:GAA:
[OPEN11]C:FileSystem_File:FileSys:File:FileName=^S${PJC_WEBPATH}\x5CPublishedViews\x5CPublic\x5CTrend\x20of\x20Level\x200\x20and\x20Level\x201\x20Requirements\x20with\x20Status.PNG
[DISPLAY12]F:FileSystem_File:FileSys:File::FilePath:SAAA5b:
[ENDDISP13]F:FileSystem_File:FileSys:File::FilePath:SAAA5b:
[DISPLAY14]F:FileSystem_File:FileSys:File::Image:GAA:
[ENDDISP15]F:FileSystem_File:FileSys:File::Image:GAA:
[OPEN16]C:FileSystem_File:FileSys:File:FileName=^S${PJC_WEBPATH}\x5CPublishedViews\x5CPublic\x5CDistribution\x20of\x20Level\x200\x20and\x20Level\x201\x20Requirements\x20by\x20Priority.PNG
[DISPLAY17]F:FileSystem_File:FileSys:File::FilePath:SAAA5b:
[ENDDISP18]F:FileSystem_File:FileSys:File::FilePath:SAAA5b:
[DISPLAY19]F:FileSystem_File:FileSys:File::Image:GAA:
[ENDDISP20]F:FileSystem_File:FileSys:File::Image:GAA:
[OPEN21]C:FileSystem_File:FileSys:File:FileName=^S${PJC_WEBPATH}\x5CPublishedViews\x5CPublic\x5CDistribution\x20of\x20Level\x200\x20and\x20Level\x201\x20Requirements\x20by\x20Iteration.PNG
[DISPLAY22]F:FileSystem_File:FileSys:File::FilePath:SAAA5b:
[ENDDISP23]F:FileSystem_File:FileSys:File::FilePath:SAAA5b:
[DISPLAY24]F:FileSystem_File:FileSys:File::Image:GAA:
[ENDDISP25]F:FileSystem_File:FileSys:File::Image:GAA: