Revised Unified Process (Assignment3) - Amel94/ITC303-XCoders GitHub Wiki

Unified in the RESOURCE ALLOCATION SYSTEM PROCESS project has these two primary aspects that are important to the project plan The unified process Resource allocation system project is iterative. Resource Allocation system Project progress is measured against clear milestones. Iterative Development of our project was done, iterative. The Unified Process is an incremental process whereby the overall project is broken down into phases and iterations. The iterations are risk-driven, that is, oriented toward mitigating risks and each one should deliver executable software that’s demonstrable and testable against the project’s requirements and use cases. The project manager uses iteration plans to manage the project in the system of resource Allocation. Generally, work that falls outside of an iteration plan shouldn’t be undertaken. An iteration plan • provides a detailed description of the upcoming phase of work, • defines the worker roles involved, necessary activities, and artifacts to be delivered in that iteration, • outlines a very clear set of measurement criteria by which progress can be assessed during the iteration and success can be measured at the end, • defines specific start/end dates and delivery dates of the tasks which assign for the employees. Clear Milestones The RUP identifies four phases for development in the Resource Allocation system project. Each phase focuses the project team on a aspect of the project and has associated with it a number of milestones. These milestones help the project manager assess project progress and ensure that the project will deliver required features and will have quality built in. The phases and what they focus on are as follows:

1. Inception — The focus of this phase is understanding the scope of the project.

2. Elaboration — The architecture as well as the requirements of the projects being built must be understood by the end of this phase.

3. Construction — The projects must be constructed by employees, the tasks assign by the project manager to the employees.

4. Transition — Each task must be rolled out to the project manager during this phase. The Inception phase is “where you define the project scope and define the business case for the system. The initial use cases for your software are identified. Use cases are the industry standard technique for defining the functional requirements for systems, providing significant productivity improvements over traditional requirement documents because they focus on what adds value to users as opposed to product features. Basic project management documents are started during the Inception phase, including the initial risk assessment, the estimate, and the project schedule. As you would expect, key tasks during this phase include business modeling and requirements engineering, as well as the initial definition of your environment including tool selection and process tailoring”. The Elaboration phase “focuses on a detailed analysis of the problem domain and the definition of an architectural foundation for your project. Because use cases aren’t enough for defining all requirements a deliverable called a Supplementary Specification is defined which describes all non-functional requirements for your system. A detailed project plan for the Construction Phase is also developed during this phase based on the initial management documents started in the Inception phase”. The Construction phase “often the heart of software projects (typically to their detriment) is where the detailed design for your application is developed as well as the corresponding source code. I say that projects focus on this phase to their detriment because organizations often do not invest enough resources in the previous two phases and therefore lack the foundation from which to successfully develop software that meets the needs of their users. The goal of this phase is to produce the software and supporting documentation to be transitioned to your user base”. The Transition phase is to “deliver the system to your user community. There is often a beta release of the software to your users, typically called a pilot release within most businesses, in which a small group of users works with the system before it is released to the general community. Major defects are identified and potentially acted on during this phase”. Finally, an assessment is made regarding the success of your efforts to determine whether another development cycle/increment is needed to further enhance the system. In the context of iterative development, the milestones for a phase provide a focus for the iterations. Each iteration moves the project through certain milestones. For example, an iteration within the inception phase would be structured around the need to understand the scope of the project; the iteration would provide the management framework for the team to explore the system boundary, implications of a possible solution, and the size of that solution. The number of iterations would depend on how difficult it might be to define the scope of the project. If the scope were very hard to understand or could be grouped into easily defined pieces, more than one iteration might be needed. If, as is normally the case, it would take one clear piece of work to understand the scope, one iteration would be appropriate. The milestones defined in the RUP are of necessity quite general the project manager will need to refine the milestones, so they focus the team on the needs of the project in its particular organizational context. In addition, because the aim of an iteration is to mitigate risk, during an iteration the team will be resolving issues that apply not only to the focus of the phase but also to other disciplines, such as architecture, testing, change management, or construction. The manager combines the iterative, risk-oriented approach with the refined milestones to determine the structure of the project plan. This is The plan of our Resource Allocation system According to the unified process.