tag:blogger.com,1999:blog-102444522011-04-21T15:04:06.173-07:00This is where I'm going to keep notes on what I am doing in my CIS 327 class. Bethhttp://www.blogger.com/profile/12065469084243475192noreply@blogger.comBlogger11100tag:blogger.com,1999:blog-10244452.post-1106844725836268012005-01-27T07:59:00.000-08:002005-01-27T08:52:05.836-08:00These are all of the definitions and terms. I figured it would be easier on me to make it one post. <br /> <br />1. Abstraction - in object-oriented programming, this means that programmers focus on the commonalities among objects in the system, rather than on the special cases. <br /> <br />2. Inheritance - software reuse in which classes are created by taking an existing class's data and methods and embellishing them with new or modified capabilities. <br /> <br />3. Polymorphism - enables us to write programs that process objects of classes that are part of the same class hierarchy as if they are all objects of their superclasses. <br /> <br />4. Encapsulation - a way to combine different data and methods to create a class of an object. <br /> <br />5. Association - a relationship between classes. <br /> <br />6. Multiplicity - tells how many objects of a class participate in the association. <br /> <br />7. Qualified Association - A qualified association between two classes results in the generation of data members and member functions in one or both classes. <br /> <br />8. Reflexive Association - the relationship between the entity and itself. <br /> <br />9. Inheritance and Generalization - creating classes from existing classes. <br /> <br />10. Aggregations - is the typical whole/part relationship. <br /> <br />11. Composites - the lifetime of the part is controlled by the whole. <br /> <br />12. Contexts - A context model is a composite of a sequence of navigational objects for which an order is provided. <br /> <br />13. Interfaces and Realizations - an interface is a set of operations that specifies some aspect of a class's behavior, and it's a set of operations a class presents to other classes. It can specify a subset of a class's operations and not necessarily all of them. <br /> <br />14. Use Case Diagram - is a description of a system's behavior from a user's standpoint. <br /> <br />15. Class Diagram - a class is a category or group of things that have similar attributes, so a class diagram shows all those things in it. <br /> <br />16. Object Diagram - an object is an instance of a class, a specific thing that has specific values of the attributes and behaviors. The diagram shows all of this. <br /> <br />17. State Diagram - a diagram that shows at any given time, an object is in a particular state. <br /> <br />18. Sequence Diagram - shows the time-based interaction of objects interacting with one another. <br /> <br />19. Activity Diagram - shows the activities that occur within a use case or within an object's behavior typically occuring in a sequence. <br /> <br />20. Collaboration Diagram - elements of a system work together to accomplish the system's objectives and a modeling language must have a way of representing this. <br /> <br />21. Component Diagram - use case is a description of a system's behavior from the use's standpoint. <br /> <br />22. Deployment Diagram - shows the physical architecture of a computer-based system. <br /> <br />I hope my definitions of these terms was at least understandable. I've been sick, so I may not have gotten all of them right. <br />Have a great day!!! :) <br /><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/10244452-110684472583626801?l=cis327bethharris.blogspot.com' alt='' /></div>Bethhttp://www.blogger.com/profile/12065469084243475192noreply@blogger.com3