cs619 final project viva 2017
Why UML
- Graphical notations make the idea/concept more clear as compared to natural language or coding.
- UML helps us to acquire the overall view of the system.
- The two major advantages of using UML in software development life cycle are:
- Abstract features of design
- Relationship between elements of the design
Class Diagram:
Class are type of Objects of program is going to use class diagram describe those classes and how they related.
- It shows the structure of the system by use of classes, their attributes, methods and relationships among objects of the system.
- The purpose of the class diagram is to design the static view of an application.
- Class diagram shows behavioral and data management responsibilities of each class and thus how this responsibility passes across the model.
- Class diagram can describe responsibilities of a system.
- It is used to describe the association, generalization, composition and aggregation relationship among class.
- It is also used to show the features of the classes, i.e. the attribute and methods/operations of each class.
Components of class diagram:
A class is a description of a set of objects that share the same attributes, operations, relationships, and semantics. The components of a class are name, attribute and methods.
Name: The name of the class is the only required tag in the graphical representation of a class. It always appears in the topmost section.
Attribute: An attribute is a named property of a class that describes the object being modeled. In the class diagram, attributes appear in the second compartment just below the name-compartment. Attributes are usually listed in the form:
attributeName : Type
A derived attribute is one that can be assumed from other attributes, but doesn’t actually exist. For example, a Person’s age can be computed from his birth date. A derived attribute is designated by a preceding ‘/’ as in:
/ age: Date
Attributes can be:
+ public
# protected
– private
/ derived
Methods/operations: Operations describe the class behavior and appear in the third compartment. You can specify an operation by stating its signature: listing the name, type, and default value of all parameters, and, in the case of functions, a return type. Complete representation of class components is as follows:
Sequence Diagram:
Interaction diagram that emphasis objects communicate and the time ordering of message.
Sequence diagram is one the interaction diagram, which describes the interaction among the objects or classes of the system in term of exchanges of messages over time. Sequence diagram is also called event diagram, and it is a good way of visualizing, and validating various runtime scenarios. In other words, sequence diagram is used to model and document how the system will behave in various scenarios and validate the logic of complex operations and functions.
Video Links
https://www.youtube.com/watch?v=OkC7HKtiZC0&list=PLGLfVvz_LVvQ5G-LdJ8RLqe-ndo7QITYc
https://www.youtube.com/watch?v=6cQs1JkUrY0
https://www.youtube.com/watch?v=3cmzqZzwNDM
https://www.youtube.com/watch?v=XIQKt5Bs7II
https://www.youtube.com/watch?v=18_kVlQMavE
https://www.youtube.com/watch?v=St4FQd-itu0