• Model the process choreography using BPMN

You are a student and part of a proposal review committee assigned to solicit and review proposals for a new, technology project from several of your school's partners. A request for proposal (RFP) has already been developed and you were not involved in the planning phase or development.

RFP responses (proposals) must be submitted to the school faculty 30 days from the beginning of Week 5 in your class. However, the project team must start planning on the first weekday of Week 5 of the same class. The committee sends a request for proposal (RFP) to several your school's partners and waits, up to one week, for their proposals. The proposal review committee short lists the RFP responses and selects the two most interesting functional designs (proposals) and starts planning the details for these two proposals.

Negotiations with the selected partners requires several iterations in order to clarify the functional design. These iterations include: The review committee documents RFP compliance or non-compliance with clarifying questions in each proposal and, then, requests updated proposals from each partner. Each partner addresses the areas of non-compliance, updates their proposal response, and returns it to the proposal review committee. After three clarification rounds, each proposal is in its final form and given to the school faculty. The faculty reviews each proposal and selects one of the proposals. The selection decision or outcome results in one of two messages: Either the project proposal was rejected or it was accepted. In the latter case, the review committee announces the project award result to the appropriate partner.