Project gives up to 60 points from the overall 100 points.

1-2 students per project
Each student carries responsibility for 1 business process, so 1 process per student - ie. 2 processes are needed with a 2-student project. Usually one larger process can be logically divided into two subprocesses, so in that case each student is responsible for one subprocess.

The chosen business processes have to deal with e-government issues.

Two variants of each business process should be analysed: either AS IS and TO BE process variants, or TO BE1 and TO BE2 process variants, or AS IS1 and AS IS2 process variants.

For example, a college admissions market can have 4 variants:
1) decentralised market, each college has a separate market and their own information system, no preferences are gathered, each applicant has to find a study place on their own
2) partially centralised separate submarkets, each college has a separate market and their own IS
3) centralised separate submarkets, a common information system (SAIS in Estonia) but each college has a separate submarket, applicant submits separate preferences for each submarket.
4) a unified admissions market, a common information system, preferences are gathered together into a clearinghouse, clearinghouse matches applicants into study places

The goal of the project of this course is to model at least two variants of a process and then assess in which environmental conditions it is appropriate to use one process variant and in which case another variant.

Possible reasons for different process variants:
a) different customer loads require different process variants taylored to those customer loads
b) different business models require different process variants
c) differing resource availability, need to optimise some measure or some resource use
d) unexpected rise in frequency of exceptional cases, need to be managed in a more orderly manner

The process should include at least 2 roles that are performed by humans (for example, a client and a customer service representative; two parties making a deal; two parties brokered by a third party, etc.). A process can also include the so-called system roles or software (-agent, -component) roles, but those do not count as human roles.

Process examples: 
processing visa requests,
a visa auction?,
processing citizenship requests,
processing driving license requests,
negotiating a new insurance contract (of a specific type),
processing an insurance case (of a specific type),
state or municipal office processing a request for information,
tax declaration process for a physical person,
tax declaration process for a judicial person,
etc.

The process should have at least one positive ending and at least one negative ending.
Any process simplification has to be negotiated with the teacher.

Appropriate element subtypes have to be used (in Bizagi extended mode) when modeling the process. Element subtypes gan be neglected in a simulation model.

Each process model has to be accompanied with a textual description of the process steps, so as to minimise possible misunderstandings.

Simulation of the process model can be done in the case software (Bizagi), or manually. In either case, resource use has to be specified at appropriate process elements and probabilities have to be speficied at gateway threads. The results of the simulation have to support the comparative analysis of AS IS and TO BE processes.

A short project vision of up to 1 page in length has to be submitted by Friday 16:00, October 16th (by end of week 7). The project vision should include the following: organization under analysis, chosen business processes, the start and end events of chosen business processes. 1-2 sentences describing what happens between the start and end events.

The draft of the full project has to be submitted by email (tarmo.veskioja@ttu.ee) by Friday 16:00, December 4th. The final full project has to be submitted by Friday 16:00, December 18th OR at least 2 days before defending your project, whichever of the two deadlines arrives first.

Submitted project has to be defended (no presentations, student has to answer to the questions of the teacher related to the project). Undefended project does not get points. Project has to be defended together by all project members. As a rule, project defendings are in a verbal form, but as an exception it might be possible to defend the submitted project via Skype as well.