Business Process Analysis
Business Process Analysis begins (also starts the The
Campus Technology Exchange Process, ) as a partnership with the process owner (functional)
and the programmer/analyst (technical). A needs-statement (wish! or idea!) is written by the process owner and a requirement is established.
Additional detail, i.e., Scope, targeted Data System, Business Case, funding, etc., is added to the requirement statement, permitting both owner
and technical to get an accurate size of the level of work. The iterative building of the requirement, formulating costs and estimates, results
in a specification that is the formal basis of what the process owner wants; and what the technical needs to design and develop an application as
a customization or new service on the web or in the portal. Once the requirement and spec that have been costed, the process owner becomes the
project manager (or appoints one) of his/her requirement, creates a timeline, and follows the attached workflow diagram.
| Project Workflow Lifecycle |
| Project Workflow Specifications |






