In Software Engineering I Learned

In Software Engineering I Learned

Rational Unified Process.
In Software Engineering I Learned a lot more about how the process of it works. The type of approach I took in software was the Rational Unified Process approach. I found it to be quiet a tough process at first but then gained a lot of knowledge about it. Rational Unified Process (RUP) is a type of methodology that is based around the development of software. It can be very beneficial throughout the entire process. It involves four main phases which are Inception, Elaboration, Construction and transition. The inception phase is the first phase, talks about the scope, which is the idea the came up they came up with for the project. The second phase is Elaboration. This phase talks about the projects requirements being evaluated. The team talks about certain tools that can be used for the project. These can include expenses and software. The third phase is Construction which is the project itself being developed and being finished off. The fourth phase is Transition is where the project has time to be updated a bit more. Afterwards it is then launched.

Scrum is a type of Agile methodology approach in Software Engineering. It’s a type of framework that groups use to manage and control their work. it’s mostly based around the development of software. the group must then complete their own tasks within a time limit. They use certain tools to assist them throughout the process. The first is a product backlog. This is a list of tasks that need to completed. Another tool used is Sprint backlog. This involves using the items listed in the product backlog. It lists the ones that need to be used apart of the sprint. Then there are the sprint tasks which are the tasks used in the sprint backlog.

We Will Write a Custom Essay Specifically
For You For Only $13.90/page!

order now

Rational unified process (RUP) and Scrum do have some similarities but there are a lot of differences between the two in terms of how the processes both work. When it comes to the type of approach they are both use iterative. The cycle in RUP uses four phases (Inception, Elaboration, Construction and transition) whereas the cycle in Scrum a workload can be done within just one iteration. There is a big difference in size of the projects and the size of teams. RUP was designed for projects that are a quiet large, complex and high in value. Ones that would usually be built for large companies. It’s also used for long term projects (usually a few months). Since the projects are quiet large the team sizes will also be Huge in numbers. It also provides a guide lines for all members that are involved such as users, designers and managers. Scrum is usually used for projects that are quiet small, not worth a lot in value, with smaller groups. With the process of planning things in a project RUP has milestones to meet and they must meet their deadlines, so therefore there is more pressure put on the team. Whereas with scrum Deadlines don’t matter as much as they do in RUP.
The next comparison is based on defining the scope of a project. When we use RUP the scope is always figured out before the project is even started. The scope written down a document and the team can go back and look over the Scope if they want to. When it comes to using SCRUM, Scope isn’t used. We use Backlogs. These are a list of features that should be helpful towards the success of your project. If they are not useful then they should be left out. The members of the team have to keep constantly monitoring them.

The next part in the comparison is the phases and processes of each Method. As mentioned RUP has 4 phases that include Inception, Elaboration, Construction and transition. During the inception phase. During it the team will get together and talk about the project. They will discuss things such as is the project worth the effort to build? What kind of equipment will be needed? How much will our expenses be? This is a very important step to start off with as things can go wrong when not properly planned. The second phase is elaboration which involves analysing the requirements needed. This part is very import as it can have an effect on the fourth phase (transition). It tells us whether the project will either be low in risk or extremely high. The third phase is construction which is where the development of the project begins. All the requirements and software used are put together to complete the project. The fourth and final phase is Transition. This phase is where the project has been completed and it will be launched for the public if it’s being commercialised. Other than the phase being about the completion of the project there are other things to do as well such as bugs needing to be fixed or if anything new needs to be added in to it. The project will still need to monitored If anything goes wrong.

In Scrum there are 5 phases used. They include initiate, plan and estimate, implement, review and retrospect and Release. Initiate phase involves creating a project vision. This is goal or expectation that you would like to see at the end result of a project. You then need to identify the scrum team. We also create a product backlog. This tool which is already mentioned is a list of tasks that the user should be able to do with the product. The second phase is plan and estimate which involves creating user stories. An example of a user story taken from our project in the training simulator would be “the user should be able to select a weapon type”. It should give the user the functionality to select a weapon they wish to fight with. After that the user stories must be approved by the product owner. The team must then make tasks out of them. So for user story such as the selecting a weapon type the game must then have a dropdown menu for the player to select the weapon. So the task would be to then make a dropdown menu with a list of weapons. The team must then create an estimated number of days that each task should take to finish. Finally, they must create a sprint backlog. The group will meet in the scrum meeting and decide on what tasks will be completed in the sprint. (A sprint is the duration of time a task needs to completed in).
The third phase is implement. Here the group will work on the tasks that are in the sprint. They also may update their tasks if necessary. they should organise times where the team can meet for scrum meetings. These meetings usually last up to 15 minutes and the team must discuss the progress that they have made with their tasks and what is next to do. The fourth phase is review and retrospect. Here the team will review what they have done in the project and talk about what they have learned throughout the sprint. What they have learned can used in future project when using scrum. They must also show the sprint task to the product owner. The final phase is release where the product is finished and get launched.

Overall I can say that Rational Unified process was tough to get used to. I found it quite interesting to learn about and would consider using it for future projects. I found using Scrum much easier as we had used some techniques that are used in scrum such as Scrum meetings which were very beneficial. I also found using the product and sprint backlogs very helpful when it comes to planning and keeping track of your tasks. It’s also a great monitor what tasks are currently being use and which ones aren’t.

References (2018). Phases and processes in Scrum project| SCRUMstudy.
online Available at:
Accessed 14 May 2018.

Powell-Morse, A. (2018). Rational Unified Process: What Is It And How Do You Use It?.
online Airbrake Blog. Available at:
Accessed 14 May 2018. (2018). RUP vs Scrum.
online Available at:
Accessed 14 May 2018.

Ali (2018). Difference between rup and scrum methodologies.
online Available at:
Accessed 14 May 2018. (2018). Rational Unified Process vs. Agile |
online Available at:
Accessed 14 May 2018.


I'm Alfred!

We can help in obtaining an essay which suits your individual requirements. What do you think?

Check it out