Personal tools
You are here: Home Project Info LANDIS-II Project Risks

Project Risks

  • Goal: Identify the primary risks for this project. Some of these risks apply across multiple iterations and are therefore included as a separate Unified Process document. Risks can also be thought of as project uncertainties.
  • Risk 1: Component Variables:
    • Will each component be able to add its own unique list of variables to the landscape?
    • Successfully resolved in Iteration 1.
  • Risk 2: Plug&Play:
    • Can dynamic libraries (aka Plug&Play) be implemented in C++? If so, how difficult?
    • If C# is required, will the new C# generics (eg templates) interact well with the existing C++ generics?
    • Will be addressed in Iteration 2.
  • Risk 3: User Interface and Model Interaction:
    • Need to clarify the interactions between the core model and the user interface (both graphical and command-line). This will impact the model architecture.
    • Need to complete Use Cases to resolve.
    • Use Cases will be at least 50% complete for Iteration 2.
  • Risk 4: Learning Unified Process:
    • We are still learning the Unified Process and adapting it to our needs. There may be some unnecssary efforts and some valuable pieces of the Unified Process may be missed.
    • Will require us to continue up the learning curve.
Document Actions