Use case prioritization

De productpatterns_wiki
Saltar a: navegación, buscar

Spanish.jpg Español

Box-In.png
Entries

  • Use Case Diagram
    • Can it be used configuration management ?: Yes
  • Requirements specification document
    • Can it be used configuration management ?: Yes

Box-Out.png
Exit

  • Use Case Diagram
    • Can it be used configuration management ?: Yes

Star.png
Solution

process-descending-24px.png
Process

Use case prioritization.png

time-24px.png
Development time

    • To acquire the necessary knowledge to develop the software product: 2 hours.
    • To create the Product Pattern: 2 hours.
    • To apply the Product Pattern: 1 day.

video-24px.png
Explanatory Video

Search-32px.png
Quality Controllers

  • None

start-flag.png
Initial Context

It is developing a software system using the Craig Larman Method, it already has the use case diagram and wants to plan the development of the application.

end-flag.png
Result Context

Planning development cycles (iterations) of the software system to be created is obtained.

cloud.png
Problem

It is desired to organize the development of a software system from which it has been created a use case diagram reflecting the functionality of system. Since you are using the Craig Larman Method, It is desired to divide the development of the software system in several cycles (or iterations) of development, prioritizing the use cases according to the impact that has the development of the functionality of one over another according to a set of predefined design feature.

forces.png
Restrictions (Forces)

  • Type of Organization: SMEs, Large Companies.
  • System Type: It applies to all types of systems.
  • Programming Paradigm: OO (Object Oriented).

roles.png
Roles

  • Analyst
  • Customer
  • Project Manager
  • System Users

lightbulb.png
Lessons Learned

  • Settings in prioritizing use cases [María Isabel Sánchez Segura, 2010]
    • By prioritization I've noticed that sometimes a case of high priority application has an inclusion with other use cases that has remained in cataloged with less priority in later cycles. In these cases we should group all the use cases, both the priority cases, as those associated by inclusion in the same development cycle. Regardless of the priority they have reached the other use cases.
    • Once the priority of each use case is established, it is convenient to group use cases of the same size so that development cycles are balanced.

award.png
Capability Level

  • Capability Level 2 CMMI.

Options.png
Basic Knowledge and Skills

board-24px.png
Knowledge

  • Definition of software requirements (functional and non-functional).
  • Craig Larman Method
  • UML notiones, especially the technique of modeling use cases and sequence diagrams.

help-24px.png
Abilities

  • Capacity of abstraction.
  • Capacity of Analysis.

Information-Sources.png
Information Resources

  • Ferré Grau, X & Sanchez-Segura, M. (2004). Desarrollo Orientado a Objetos con UML. Recuperado el 2009-11-26 de http://www.clikear.com/manuales/uml/index.aspx.
  • Fowler, M. (2004). UML distilled: a brief guide to the standard object modelling language. Addison-Wesley.
  • Larman, C. (2001). Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and the Unified Process (2da. ed.). Prentice Hall.
  • Jacobson, I. & Booch, G.(1999). The unified software development process. Addison-Wesley.
  • Rumbaugh, J. & Jacobson, I. (2005). The unified modeling language reference manual. Addison-Wesley.
  • Rumbaugh, J. (2005). Object-Oriented Modelling and Design. Prentice Hall.