MIS 3320 BAYLOR Final review Actual Exam 2024/2025
MIS 3320 BAYLOR Final review Actual Exam 2024/2025 class diagrams used to model classes & their associations with other classes -UML diagram -object oriented (OO) diagram (used for OOAD, OOP/OOPL, OODB) domain model class diagram -in analysis phase -model objects in the problem domain (things that need to be remembered) -PK identified as {key} -similar to ERD -domain models go to DBA and programmer design class diagram -in design phase -model software classes (data types: string, date, int, etc) -top part is domain model plus data types, bottom part listed with + & functions or methods ERD vs Domain Model Class Diagram terminology -entity --> domain class (data) -attribute --> attribute -relationship --> association -cardinality --> multiplicity -instance --> object (or instance) order: domain/data class order form: GUI class (graphical user interface, software) domain classes -contain attributes -used to instantiate objects (create an object as an instance) -cookie cutter analogy OOP/OOPL OOProgramming & OOProgrammingLanguages -primary keys may be modeled but are not required because objects can be associated by reference (unique ID automatically created BUT relational databases need primary keys, so we will add them except for subclasses & association classes) -UML notation: attribute {key} -OODataBases class diagram associations multiplicities: min..max, many is *, specific numbers allowed (ex. 4..7) association class generalization hierarchy (is-a) whole-part association (has-a) association class -same as ERD associative entity -resides only on many to many -UML notation: dashed line extending from the many to many relationship, keep the M:M line, do not add a primary key Generalization Hierarchy aka specialization hierarchy -generalize as move up -specialize as move down -triangle always points to superclass & specific (away from arrow) are subclasses -inheritance is in effect--all attributes are inherited from superclass to subclass -an is-a association (read from bottom up) -only for things of the same type superclass known as: generalization, base, parent class -class being inherited by another (subclass) -top class subclass known as: specialization, derived, child class -class that inherits from another class -extends the superclass abstract class vs concrete class abstract -notation: italicized -designed to not be instantiated (no objects of this type) -only make superclass abstract if all subclasses are represented & no other types concrete -notation: plain text -designed to be instantiated (objects created for this type) when to create a generalization 1-has own unique attributes (some objects do not share the same attributes) 2-has associations not at the top whole-part hierarchy -used to represent has-a association -2 types: aggregation & composition -diamond is attached to the whole -still includes multiplicities aggregation vs composition aggregation -removable parts -has a but parts can exist separately -loosely coupled -empty diamonds composition -has a but parts cannot exist separately -non-removable, stronger -tightly coupled -filled in diamonds UML Unified Modeling Language -OO modeling language consisting of multiple types of diagrams -3 Amigos: James Rumbaugh, Grady Booch, & Ivar Jacobson -Rational Unified Process (RUP): OO systems development methodology -adopted & managed by OMG (Object Management Group) types of UML diagram •Structure diagrams - Class diagram, Component diagram, Deployment diagram, Object diagram, Package diagram, etc. •Behavior diagrams - Activity diagram, Use Case diagram, Sequence diagram, State machine, Communication diagram, etc. use case diagram •a UML diagram depicting the relationship between actors & use cases -shows scope of system -functionality: use cases -reuse of code UML Activity Diagram a graphical representation of procedural flow that includes activities people, systems, and flows which are sequential, conditional, & repetition -used to model business processes & use cases (BPMN: business process modeling notation) **user interface the way in which the user interacts with the system -the set of inputs & outputs that the user interacts with to invoke the functions of an application GOALS -functionality -usability (increase productivity, decrease effort, decrease errors) to the user, the user interface = system user experience (UX) design a broad field that looks at all aspects of a person's interaction with a product -product: functionality, usability -user: who are they, their perceptions & feelings, motivations, & values are considered GOAL: create positive experiences -increased user satisfaction (increased brand loyalty, increased product promotion by user, increased sales) UX Researcher understanding the user - who are they & what motivates them? -gather info: interview, surveys -look for patterns & divide into segments (target specific user group) -identify requirements UX designer focus on how it works -design wireframes & prototypes (strong prototyping skills) UI designers focus on how it looks -make it look great Interaction designers -focus on motion: animations & transitions UI elements any object on a screen that can be manipulated by the user -UI controls, UI elements, design elements, human interface objects (HIO) desktop application UI elements -menustrip (menu bar)--ex. file, edit, view, help -toolstrip (has icons, ie. file & document & save, under menu bar) -statusstrip (bottom, ie. status saved) Containers (all move as one) -GroupBox (has label, selections) -Panel (list of things, highlight what is selected) -TabControl (tab names) Data Entry/Selection Other -Label -Button (clickable & performs an action) -PictureBox Tabular Data -DataGridView (don't put data in full grid, don't let user change the data) -BindingNavigator (record navigation bar, location in records) UI elements data entry -TextBox: WORST control, only one to validate -CheckBox: user can pick more than one choice -RadioButton: mutually exclusive, only pick one choice -ComboBox: drop down, combo of list box and text box, can make read only (grayed out, system creates it) -ListBox: drop down, constantly visible set of choices, single or multi select) -MonthlyCalendar -DateTimePicker: shows full calendar & then drops down -NumericUpDown: click up & down, only accepts numbers
Escuela, estudio y materia
- Institución
- MIS 3320
- Grado
- MIS 3320
Información del documento
- Subido en
- 24 de mayo de 2024
- Número de páginas
- 17
- Escrito en
- 2023/2024
- Tipo
- Examen
- Contiene
- Preguntas y respuestas
Temas
-
mis 3320 baylor final review actual exam 2024202