You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: DevelopmentDesign/README.md
+81-1Lines changed: 81 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -170,7 +170,87 @@ The focus of the spiral model is to identify risk
170
170
<imagesrc="./img/Spiral_model_(Boehm,_1988).png"><spanstyle="font-size:10px"> Illustration of the spiral model as presented by Boehm 1988 </span>, from `https://commons.wikimedia.org/wiki/File:Spiral_model_(Boehm,_1988).png`
171
171
172
172
## RUP, Rational Unified Process
173
-
Rational Unified Process is a software development method based on iterative object-oriented development. The idea is that you tailor the development method to fit the project, this however is not without cost as adapting and formulating templates take time. It is important to note that development models of this type are not in contrast to Agile development but some concessions to the iterative flow may have to be made as the image depicts RUP follows the phases of design as SDLC (with the addition of a 0th step Business modeling), Each phase in RUP is a complete iteration of the design steps Inception, Elaboration,Construction and Transition
173
+
Rational Unified Process is a software development method based on iterative object-oriented development. The idea is that you tailor the development method to fit the project, this however is not without cost as adapting and formulating templates take time. It is important to note that development models of this type are not in contrast to Agile development but some concessions to the iterative flow may have to be made as the image depicts RUP follows the phases of design as SDLC (with the addition of a 0th step Business modeling), Each phase in RUP is a complete iteration of the design steps Inception, Elaboration,Construction and Transition
174
+
175
+
```plantuml
176
+
@startuml
177
+
!theme blueprint
178
+
179
+
skinparam packageStyle rectangle
180
+
skinparam packageTitleFontColor #ffffff
181
+
skinparam packageTitleBackgroundColor #3288bd
182
+
183
+
actor "Manager" as manager
184
+
actor "Software Architect" as architect
185
+
actor "Devloper" as dev
186
+
actor "Deployment engineer" as depEng
187
+
188
+
rectangle "Inception" as inception {
189
+
usecase "Define Project Vision" as defineVision
190
+
usecase "Create Business Case" as createBusinessCase
191
+
usecase "Perform Risk Assessment" as performRiskAssessment
192
+
}
193
+
194
+
rectangle "Elaboration" as elaboration {
195
+
usecase "Develop Use Case Model" as developUseCaseModel
196
+
usecase "Create Analysis Model" as createAnalysisModel
197
+
usecase "Design System Architecture" as designSystemArchitecture
198
+
usecase "Develop Iteration Plan" as developIterationPlan
199
+
}
200
+
201
+
rectangle "Construction" as construction {
202
+
usecase "Implement System Components" as implementSystemComponents
203
+
usecase "Perform Unit Testing" as performUnitTesting
204
+
usecase "Integrate System Components" as integrateSystemComponents
205
+
usecase "Perform System Testing" as performSystemTesting
206
+
usecase "Deploy System" as deploySystem
207
+
}
208
+
209
+
rectangle "Transition" as transition {
210
+
usecase "Gather User Feedback" as gatherUserFeedback
211
+
usecase "Release Software" as releaseSoftware
212
+
usecase "Perform Lessons Learned" as performLessonsLearned
What follows next is an emphasis diagram which describes where the focus of the work should be put in at which time of the project. It is common to have a signof at the end of each phase before starting the next one.
0 commit comments