Problem Analysis will focus the team on developing an understanding of the problem to solved. Analysis activities should take place using only the constructs and terminology of the problem domain: no solution domain concepts should be considered. Since computers merely automate an existing manual process, the analysis model should reflect a completely manual interpretation of the problem’s workflow. Think of lots of people performing the activities with pencil and paper, folders and filing cabinets, and you'll be on the right track. The analysis model captures the business rules and data for the domain and problem you're trying to automate. Consequently, this activity need only be performed once for a particular business problem. 

   Not only is the analysis reusable for many different implementations, but the analysis model also forms the basis for the implementation architecture! By identifying all the participants, and assigning them roles and responsibilities, the initial architecture for the solution. This activity is crucial for determining the correct architecture for your system!

(select any activity or artifact for more information)