Graphical modelssystem models that use pictures and other graphical elementsImplementation requirementsconstraints such as required programming languages and tools, documentation method and level of detail, and a specific communication protocol for distributed componentsInterface requirementsrequired interactions among systemsInternal stakeholderspersons within the organization who interact with the system or have a significant interest in its operation or successMathematical modelssystem models that describes requirements numerically or as mathematical expressionsModelrepresentation of some aspect of a systemNonfunctional requirementssystem characteristics other than the activities it must perform or supportOpen-ended questionsquestions that encourage discussion or explanationOperational stakeholderspersons who regularly interact with a system in the course of their jobs or livesPerformance requirementsoperational characteristics related to measures of workload, such as throughput and response timePhysical requirementscharacteristics of hardware such as size, weight, power consumption, and operating conditionsReliability requirementsrequirements that describe system dependabilitySecurity requirementsrequirements that describe how access to the application will be controlled and how data will be protected during storage and transmissionStakeholderspersons who have an interest in the successful implementation of the systemSupportability requirementshow a system is installed, configured, monitored, and updatedSwimlane headingactivity diagram column containing all activities for a single agent or organizational unitSynchronization baractivity diagram component that either splits a control path into multiple concurrent paths or recombines concurrent pathsSystem requirementsthe activities a system must perform or support and the constraints that the system must meetTechnology architecturea set of computing hardware, network hardware and topology, and system software employed by an organizationTextual modelstext-based system models such as memos, reports, narratives, and listsUnified modeling language (UML)standard set of model constructs and notations defined by the Object Management GroupUsability requirementsoperational characteristics related to users, such as the user interface, realted work procedures, online help, and documentationWorkflowsequence of processing steps that completely handles one business transaction or customer requestActoran external agent; a person or group that interacts with the system by supplying or receiving dataAutomation boundarythe boundary between the computerized portion of the application and the users who operate the application but are part of the total systemBrief use case descriptionsan often one-sentence description that provides a quick overview of a use caseCRUD techniquean acronym for Create, Read/Report, Update, and Delete; a technique to validate or refine use casesElementary business processes (EBPs)the most fundamental tasks in a business process, which leaves the system and data in a quiescent state; usually performed by one person in response to a business eventEventsomeething that occurs at a specific time and place, can be precisely, identified, and must be remembered by the systemEvent decomposition techniquea technique to identify use cases by determining the external business events to which the system must respondExternal eventan event that occurs outside the system, usually initiated by an external agent<<includes>> relationshipa relationship between use cases in which one use case is stereotypically included within the other use casePerfect technology assumptionthe assumption that a system runs under perfect operating and technolohical conditionsState eventan event that occurs when something happens inside the system that triggers some processSystem controlschecks or safety procedures to protect the integrity of the system and the dataTemporal eventan event that occurs as a result of reaching a point in timeUse casean activity that the system performs, usually in response to a request by a userUse case diagramthe UML model used to graphically show use cases and their relationships to actorsUser goal techniquea technique to identify use cases by determining what specific goals or objectives must be completed by a userAbstract classa class that describes a category or set of objects but that never includes individual objects or instancesAggregationa type of whole-part relationship in which the component parts also exist as individual objects apart from the aggregateAssociationa term, in UML, that describes a naturally occurring relationship between specific things, sometimes called a relationshipAssociation classan association that is also treated as a class; often required in order to capture attributes for the associationAttributesdescriptive places of information about things or objectsBinary associationsassociations between exactly two distinct types of thingsBrainstorming techniquesa techinque to identify problem domain objects in which developers work with users in an open group settingCamelback notionCamelcase notation; when words are concatenated to form a single work and the first letter of each embedded word is capitalizedCardinalitya measure of the number of links between one object and another object in a relationshipClassa category or classification of a set of objects or thingsClass diagrama diagram consisting of classes (i.e., sets of objects) and associations among the classesCompositiona type of whole-part relationship in which the component parts cannot exist as individual objects apart from the total compositionCompound attributean attribute that consists of multiple pieces of information but is best treated in the aggregateConcrete classa class that allows individual objects or instances to existData entitiesthe term used in an ER diagram to describe sets of things or individual thingsDomain classesclasses that describe objects from the problem domainDomain model class diagrama class diagram that only includes classes from the problem domainEntity-relationship diagram (ERD)a diagram consisting of data entities (i.e., sets of things) and their relationshipsGeneralization/Specialization Relationshipsa type of hierarchial relationship in which subordinate classes are subsets of objects of the superior classes; an inheritance hierarchyIdentifieran attribute the value of which uniquely identifies an individual thing or objectInheritancethe concept that specialization classes inherit the attributes of the generalization classKeyan attribute the value of which uniquely identifies an individual thing or objectMultiplicitya measure, in UML, of the number of links between one object and another object in an associationMultiplicity constraintsthe actual numeric count of the constraints on objects allowed in an associationN-ary associationan association between n distinct types of thingsNoun techniquea technique to identify problem domain objects by finding and classifying the nouns in a dialog or descriptionProblem domainthe specific area (or domain) of the user's business need (or problem) that is within the scope of the new systemRelationshipa term that describes a naturally occured association between specific things, sometimes called an associationSemantic neta graphical representation of an individual data entity and its relationship with other individual data entitiesSubclassthe subordinate or more specialized class in a generalization/specification relationshipSuperclassthe superior or more general class in a generalization/specialization relationshipTernary associationan association between exactly three distinct type of thingsUnary associationan association between two instance of the same type of thingWhole-part relationshipsa relationship between classes in which one class is a part or a component portion of another class
