Abstract
A lot of what we have been talking about so far is concerns mapping the information for a web site. We have mapped the navigational structure and we have mapped the content structure. What we have not done at all is map (or ‘model’) any type of flow. Information is not static, it doesn’t just sit there. Information has to be created, it may change over time, it may move (change locations), and it may be archived or deleted at some point. In order to understand everything about our data, not just where the information lives or how it is structured, we need to be able to map the data flow as well. Fortunately, there is a well-established body of knowledge on how to map these flows called business process modeling (BPM).
If you can’t describe what you are doing as a process, you don’t know what you’re doing. —W. Edwards Deming
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
Rights and permissions
Copyright information
© 2012 Ruven Gotz
About this chapter
Cite this chapter
Gotz, R. (2012). Business Process Mapping. In: Practical SharePoint 2010 Information Architecture. Apress. https://doi.org/10.1007/978-1-4302-4177-5_7
Download citation
DOI: https://doi.org/10.1007/978-1-4302-4177-5_7
Publisher Name: Apress
Print ISBN: 978-1-4302-4176-8
Online ISBN: 978-1-4302-4177-5
eBook Packages: Professional and Applied ComputingApress Access BooksProfessional and Applied Computing (R0)