ABSTRACT
Functional requirements describe the desired system behavior, while nonfunctional requirements can be imagined as the additional attributes to the behavior related to time restrictions, performance, and so on. This chapter presents use case and collaboration diagrams. Use cases have another role in the analysis phase. The job of the analyst is to realize the use cases by the corresponding collaborations between objects. The means of modeling both static and dynamic structures of the society of objects in UML are the collaboration diagrams. Three categories of object properties exist: general properties, table of constraints, and tagged values. The general properties include the object name, full path, classifier name, and multiplicity. The chapter illustrates the requirements and analysis phases of communication protocol engineering by presenting the case of the session initiation protocol (SIP), RFC 3261. The chapter provides a discussion on SIP domain specifics, the SIP requirements model, and the SIP analysis model.
