Please enable JavaScript.
Coggle requires JavaScript to display documents.
5 .Requirements Analysis and Modeling (UML(Unified Modeling Language) (UML…
5 .Requirements Analysis and Modeling
Requirements analysis allows the software engineer to
elaborate on basic requirements established during earlier requirement engineering tasks
build models that depict user scenarios, functional activities, problem classes and their relationships, system and class behavior, and the flow of data as it is
Requirement analysis model can be
a bridge
between system description and design model
it's a simplification of reality
better understand the system
build models of complex system because we cannot comprehend such a system in its entirely
models can be formal or informal
UML(Unified Modeling Language)
serves as a bridge between the requirements specification and the implement
Provide a means to specify and document the design of a software system
Process and programming language independent
suited to subject-oriented program development
UML hierarchy
Use cases
Scenario that describes a "thread of usage" for a system
actors represent roles people or devices play as the system functions
users can play a number of different roles for a given scenario
UML association
Association and dependencies
two analysis classes are oftern related to one another in some fashion
Association can be refined by indicating multiplicity
In many instances, a client-server relationship exists between two analysis classes
Associations
Inheritance/Generalization
Uni-directional
Bi direction
Aggregation
Composite Aggreation
Reflexive