Se ha denunciado esta presentación.
Utilizamos tu perfil de LinkedIn y tus datos de actividad para personalizar los anuncios y mostrarte publicidad más relevante. Puedes cambiar tus preferencias de publicidad en cualquier momento.
Investigate Options (iteration 0)
Rich pictures, Mind maps,
PROMPT, PESTLE, Initial
scope, Glossary
Inception (iteration 1...
Próxima SlideShare
Cargando en…5
×

Mapping of the Business Analysis Process Model to the Open UP iterative software development process

470 visualizaciones

Publicado el

We produced this mapping of the Business Analysis Process Model to the Open UP iterative software development process for a client that had adopted Open UP. It proved to be more cost effective than customising the training material for the client.

Publicado en: Empresariales
  • Sé el primero en comentar

Mapping of the Business Analysis Process Model to the Open UP iterative software development process

  1. 1. Investigate Options (iteration 0) Rich pictures, Mind maps, PROMPT, PESTLE, Initial scope, Glossary Inception (iteration 1) Initiate project Develop technical vision Identify stakeholders Stakeholder analysis Gain agreement on the problem to be solved Modelling business scope (activity breakdown) Activity diagrams (as-is workflow) Modelling the current business system, Strategic needs, Information requirements, Business rules, Gap analysis Gather stakeholder requests Define the scope of the solution Modelling application scope (context diagram) Activity diagrams (to-be workflow) Components Modelling the current business system (recovered information requirements, business rules) Modelling the proposed business system, Investigating feasibility Define features of the system Use cases, User stories Modelling the proposed business system Achieve concurrence Capture a common vocabulary Glossary, Business rules Inception (iteration 2..n), Elaboration, Construction Identify and refine requirements Identity and outline requirements Gather information Identify and capture domain terms Glossary, Business rules Identify the types of requirements relevant to your system Components Formal requirements Identify and capture use cases and actors in a use case model Stakeholder analysis Use cases Identify and capture use cases and scenarios Use cases Scenarios Identify and capture system wide requirements Formal requirements Achieve concurrence Details use case scenarios Detail use cases and scenarios Use cases Scenarios Detail glossary terms Glossary, Business rules Data dictionary Achieve concurrence Update use case model Use cases Scenarios Detail system wide requirements Detail system wide requirements Formal requirements, Data dictionary Detail glossary terms Glossary, Business rules Data dictionary Achieve concurrence Mapping of Essentials of Business Analysis to Open UP http://epf.eclipse.org/wikis/openup/ Consider perspectives Modelling business processes Modelling software applications Analyse Needs Evaluate options Define software requirements © Copyright Lonsdale Systems

×