Summary

In this chapter, we looked at architectural best practices for portal efforts. We started showing how to take customer requirements and map them to storyboards or wireframes. We then looked at how these wireframes or storyboards can assist in the mapping of the portal object model (portlet fields and objects) to an SOA and data model. We proceeded looking at service design conceptual view and some end-to-end traceability possibilities. We then looked at a high-level logical portal architecture view for both core banking and call center portal efforts. We finished with a brief discussion of nonfunctional aspects of portal implementations, which will take us to the next chapter. The next chapter will go over into portal gold architecture and reusable assets.