Introduction to Conceptual Modeling

Size: px

Start display at page:

Download "Introduction to Conceptual Modeling"

Angelica Wilcox
5 years ago
Views:

Department of Computer Languages and Systems University of Seville October 204

Know the basic concepts of ing. Know the main notations for ing.

1 0/4/204 ing? Introduction to Conceptual Modeling Software Engineering and Databases Group Department of Computer Languages and Systems University of Seville October 204 Learning objectives ing? Understand the need for ing and its place in the process. Know the basic concepts of ing. Know the main notations for ing. Be able to develop a for an information system from information about the problem domain and some requirements. October 204 Introduction to Software Engineering and Information Systems IISSI

2 0/4/204 What is ing? ing? Conceptual ing is a requirements analysis and database design technique. As an analysis requirements technique It helps to identify problems in the requirements before starts, avoiding unnecessary costs. As a database design technique It enables the abstract representation of the relevant concepts and facts from the problem domain and their further transformation into a database scheme. October 204 Introduction to Software Engineering and Information Systems 2 What is the problem domain? ing? Area of expertise or application that needs to be known in order to solve a problem. In the context of information systems, the problem domain is the set of interrelated concepts which are necessary to understand the customer business, and therefore to understand their needs and to propose a suitable solution. Source: Development framework of the Junta de Andalucía (MADEJA), requirement engineering area. October 204 Introduction to Software Engineering and Information Systems 3 IISSI 2

3 0/4/204 When is the used? ing? Regardless of the life cycle, it is used during the analysis. Requirements Analysis Design Implementation Testing Maintenance October 204 Introduction to Software Engineering and Information Systems 4 Requirements traceability ing? All the elements of a must be traced back towards those requirements that justifies them, usually information requirements and business rules. class Ejemplo trazabilidad RI-00 - El sistema deberá almacenar la información correspondiente a los usuarios del sistema. En concreto: RF El sistema deberá enviar automáticamente un a los usuarios cuando «trace» «trace» Usuario apellidos fechanacimiento October 204 Introduction to Software Engineering and Information Systems 5 IISSI 3

0/4/204 Conceptual ing standard UML (Unified Modeling Language). ing? Join result of several previous approaches. Managed by the OMG (Object Management Group). Widely used in the software industry.

4 0/4/204 Conceptual ing standard UML (Unified Modeling Language). ing? Join result of several previous approaches. Managed by the OMG (Object Management Group). Widely used in the software industry. Multiple available tools. It has 4 types of diagrams for software ing (version 2.4., August 20). In ing, the mainly used diagrams are: Class diagrams Object diagrams October 204 Introduction to Software Engineering and Information Systems 6 Basic concepts of ing Entity class ing? Attribute Association Role Multiplicity Object (instance of a class) Link (instance of an association) Generalization/specialization Composition October 204 Introduction to Software Engineering and Information Systems 7 IISSI 4

5 0/4/204 Entity class ing? It represents a concept which is important in the problem domain and for which the system must store information, as specified (or deduced) from some requirements. Classes are named with a noun in singular form. class Ejemplos de clases Alumno fechanacimiento código Asignatura número fecha tienebeca Matrícula October 204 Introduction to Software Engineering and Information Systems 8 Entity class attributes ing? They represent properties of a concept which is important in the problem domain and for which the system must store information, as specified (or deduced) from some requirements. Attributes are named with a noun in singular form. Attributes values must be atomic. class Ejemplos de clases Alumno fechanacimiento código Asignatura número fecha tienebeca Matrícula October 204 Introduction to Software Engineering and Information Systems 9 IISSI 5

6 0/4/204 Association between entity classes ing? Represents some kind of relation between two or more concepts that are relevant in the problem domain and for which the system must store information, as specified (or deduced) from some requirements. class Ejemplos de asociación Asignatura Matrícula código 0.. aparec een 0.. número fecha tienebeca October 204 Introduction to Software Engineering and Information Systems 0 Association between entity classes ing? It is named using a verb in singular third person and prepositions if needed. It must form a comprehensible sentence when reading it together with the roles. class Ejemplos de asociación Asignatura Matrícula código 0.. aparec een 0.. número fecha tienebeca October 204 Introduction to Software Engineering and Information Systems IISSI 6

7 0/4/204 ing? Role of one association end Role played by each one of the classes in the association. By default, it is its own name. They must be specified in associations of a class with itself or when there exist more than one association between the same two classes. class Ejemplos de roles espadred e padre 0..2 Persona Vuelo salida saled e origen Aeropuerto hijo 0.. llegada llegaa destino October 204 Introduction to Software Engineering and Information Systems 2 ing? Multiplicity of one association end Given an object of a class, it indicates the minimum and maximum number of objects of the other class to which it can be associated using association links. class Ejemplos de roles class Ejemplos de asociación código Asignatura 0.. aparec een número 0.. fecha tienebeca Matrícula espadred e padre 0..2 Persona Vuelo salida saled e origen Aeropuerto hijo 0.. llegada llegaa destino October 204 Introduction to Software Engineering and Information Systems 3 IISSI 7

8 0/4/204 ing? Objects Every instance or occurrence of a class. Links Every instance or occurrence of an association. class Equipos de fútbol Jugador juegaen 0.. Equipo October 204 Introduction to Software Engineering and Information Systems 4 ing? Objects Every instance or occurrence of a class. Links Every instance or occurrence of an association. object Equipos de fútbol j : Jugador j :Jugador juegaen = "Antoñito" juegaen j2 : Jugador j2 :Jugador = "Redondo" e2 : Equipo e :Equipo = "Xerez CD" e : Equipo e2 :Equipo = "Sevilla FC" j3 : Jugador j3 :Jugador = "Kanouté" juegaen j4 : Jugador juegaen j4 :Jugador = "Negredo" J6 : Jugador = "Luis Fabiano" juegaen j5 : Jugador j5 :Jugador = "Jesús Navas" October 204 Introduction to Software Engineering and Information Systems 5 IISSI 8

9 0/4/204 ing? Generalization-Specialization Sometimes, several concepts of the problem domain have relations of type is-a, for example: Is-a vehicle Is-a Is-a truck car motorcycle This concepts usually have common properties, that appears as attributes or common associations in the. October 204 Introduction to Software Engineering and Information Systems 6 Generalization/Specialization class Ejemplo de generalización ing? espropietariod e Autom óvil matrícula númerobastidor o plazas 0.. Persona propietario propietario 0.. espropietariod e Cam ión matrícula númerobastidor o tonelaje ejes 0.. propietario espropietariod e M otoc ic leta matrícula númerobastidor o cilindrada asegurado asegurado asegurado tieneseguro tieneseguro tieneseguro 0.. Seguro 0.. compañia númeropóliza tipo precio 0.. October 204 Introduction to Software Engineering and Information Systems 7 IISSI 9

10 0/4/204 Generaization Generalization Specialization Specialization Generalization/Specialization class Ejemplo de generalización ing? Persona Seguro compañia númeropóliza tipo precio 0.. espropietariod e propietario 0.. tieneseguro Autom óvil plazas asegurado Vehíc ulo matrícula númerobastidor o M otoc ic leta cilindrada {completa, disjunta} tonelaje ejes Cam ión The most general class (the superclass), contains all the common properties (attributes and associations), inherited by the specific classes (subclasses). October 204 Introduction to Software Engineering and Information Systems 8 Generalization-Specialization class Ejemplo de generalización ing? Persona Seguro compañia númeropóliza tipo precio 0.. espropietariod e propietario 0.. tieneseguro Autom óvil plazas asegurado Vehíc ulo matrícula númerobastidor o M otoc ic leta cilindrada {completa, disjunta} tonelaje ejes Cam ión All instances of the subclasses are also instances of the superclass. Generalization is a transitive and antisymmetric relation. October 204 Introduction to Software Engineering and Information Systems 9 IISSI 0

11 0/4/204 ing? Composition Special association that represents the concept of being-part-of: A part only belongs to one whole. A part cannot exists without being part of one whole. The whole elimination implies the elimination of all its parts. It is a transitive and antisymmetric relation. It can be recursive. class Ejemplo de composición Fac tura.. {ordered} L íneadefac tura October 204 Introduction to Software Engineering and Information Systems 20 UML notation for entity classes class Notación clase ing? NombreClase atributo: Tipo atributo2: Tipo2 : atributon: TipoN Name area (compulsory) Attributes area (optional, can be hidden if needed) With the «entity» stereotype, we indicate that the class represents and entity and not a class of an object-oriented programming language. In ing, we will assume the «entity» stereotype by default. October 204 Introduction to Software Engineering and Information Systems 2 IISSI

12 0/4/204 UML notation for entity classes class Notación clase ing? NombreClase atributo atributo2 [0..] atributon The value of atributo2 can be null In ing, the types of attributes are not usually specified (except for enumerations). [0..] means that it is an optional attribute, i.e. that there will be moments in which it its value will be unknown and therefore it will be represented by a null value. October 204 Introduction to Software Engineering and Information Systems 22 UML notation for associations ing? Role name Role played by each one of the classes of the association. By default, it is the class name in lowercase. A rol A mult A Association name It is optional and must be a verbal form with sense when reading it with the roles. It is read from left to right and from top to bottom. If it must be read other way, direction must be indicated. rol B mult B B Multiplicity It indicates the minimum and maximum number of class instances that are related to a specific instance of the other class. In multiple multiplicities, order can be indicated using {ordered}. Usual values 0.. : optional.. : compulsory 0.. : multiple optional.. : multiple compulsory : same as 0.. : same as.. October 204 Introduction to Software Engineering and Information Systems 23 IISSI 2

13 0/4/204 UML notation for objects and links ing? Class and name of the object Must be highlighted for not confusing them with a class. obj : Clase atrib = valor atrib2 = valor2 atribn = valorn asociacióna asociacióna asociaciónb Links Identified using the name of the association, highlighted. obj2 : Clase2 obj3 : Clase2 obj4 : Clase3 Names and values of attributes Optional, it shows the values of the attributes of the object. October 204 Introduction to Software Engineering and Information Systems 24 UML notation for objects and links ing? lf : LíneaDeFactura cantidad = 3 precio = 2,50 f : Factura número = 8765 fechaemisión = 0/06/20 emitidaa lf2 : LíneaDeFactura cantidad = precio = 63,05 c : Cliente contienea p2 : Producto contienea lf3 : LíneaDeFactura contienea p3 : Producto p : Producto cantidad = precio = 5,25 c : Cliente emitidaa : Factura Multiobject notation Shows multiple objects without identifying them individually. October 204 Introduction to Software Engineering and Information Systems 25 IISSI 3

14 0/4/204 class UML Notación notation clasificación for classifications ing? Subc lase atribpropio atribpropio2 Superc lase atribcomún atribcomún2 {restricciones} Subc lasen atribpropiox atribpropioy Constraints Shows if the classification is complete/incomplete and disjoint/overlapped. Complete/Incomplete classification {complete}: instances of the superclass must be instances of at least one subclass, superclass is abstract. {incomplete}: there can be instances of the superclass that are not instances of any subclass. October 204 Introduction to Software Engineering and Information Systems 26 class UML Notación notation clasificación for classifications ing? Subc lase atribpropio atribpropio2 Superc lase atribcomún atribcomún2 {restricciones} Subc lasen atribpropiox atribpropioy Constraints Shows if the classification is complete/incomplete and disjoint/overlapped. Disjoint/Overlapped classification {disjoint}: superclass instances can be instances of only one subclass. {overlapped}: superclass instances can be instances of one or more subclasses. October 204 Introduction to Software Engineering and Information Systems 27 IISSI 4

0/4/204 UML notation for classifications class Ejemplo de generalización ing? Persona Seguro compañia númeropóliza tipo precio 0.. espropietariod e propietario 0.

italics. Camión {complete, disjoint} implies a partition of the set of instances of the superclass.

15 0/4/204 UML notation for classifications class Ejemplo de generalización ing? Persona Seguro compañia númeropóliza tipo precio 0.. espropietariod e propietario 0.. tieneseguro Automóvil plazas asegurado Vehíc ulo matrícula númerobastidor o M otoc ic leta cilindrada {completa, disjunta} tonelaje ejes Abstract class The name of abstract classes is written in italics. Camión {complete, disjoint} implies a partition of the set of instances of the superclass. Vehicles Cars Motorcycles Trucks October 204 Introduction to Software Engineering and Information Systems 28 UML notation for classifications class Ejemplo comunidad universitaria ing? M iem brocu {completa, solapada} Alum no Em pleado {completa, disjunta} PAS PD I October 204 Introduction to Software Engineering and Information Systems 29 IISSI 5

emitidaa c ontiene Cliente Produc to October 204 Introduction to Software Engineering and Information Systems 30 UML notation for association classes ing?

16 0/4/204 UML notation for compositions ing? class Notación composición Compuesto class Ejemplo factura Fac tura número fechaemisión mult.. {ordered} Componente L ínead efac tura cantidad precio Composite The black diamond identifies the composite. Its multiplicity is always, so there is no need to indicate it. emitidaa c ontiene Cliente Produc to October 204 Introduction to Software Engineering and Information Systems 30 UML notation for association classes ing? Sometimes it is needed to add information to the associations, turning them into classes. class Ejemplo clase asociación Empleado trabajaen Proyec to presupuesto how many hours does each employee work on each project? class Ejemplo clase asociación Empleado trabajaen Proyec to presupuesto Esf uerzo horas October 204 Introduction to Software Engineering and Information Systems 3 IISSI 6

0/4/204 ing? UML notation for associations classes Example: the hours that an employee works on a project are neither properties of the employee nor the project, but of the association between them.

17 0/4/204 ing? UML notation for associations classes Example: the hours that an employee works on a project are neither properties of the employee nor the project, but of the association between them. f : Esfuerzo horas = 20 e : Empleado trabajaen trabajaen f5 : Esfuerzo horas = 2 f2 : Esfuerzo horas = 5 p2 : Proyecto p : Proyecto trabajaen f3 : Esfuerzo horas = 7,5 trabajaen trabajaen f4 : Esfuerzo horas = 25 e3 : Empleado e2 : Empleado October 204 Introduction to Software Engineering and Information Systems 32 ing? UML notation for associations classes It is also possible to them as a class component of the participating classes. Both s are equivalent. class Ejemplo clase asociación Proyec to Empleado trabajaen presupuesto Esf uerzo horas class Ejemplo clase asociación con composición Empleado Proyec to presupuesto Esf uerzo horas October 204 Introduction to Software Engineering and Information Systems 33 IISSI 7

18 0/4/204 Notation for constraints ing? They allow additional information in the which cannot be expressed in any other way. class Ejemplo de restricción Fac tura número fechaemisión emitidaa Cliente {f ac turas sin duplic ados: un mismo producto no debe aparecer dos veces en la misma factura.}.. {ordered} L ínead efac tura cantidad precio c ontiene Produc to Notation Constraints are represented by notes. The text must be between curly braces, indicating the name of the constraint and its description. Optionally, it can be linked to the affected entities. October 204 Introduction to Software Engineering and Information Systems 34 Notation for enumerations ing? Define a type that can be used in the class attributes. The attributes are the possible values. class Notación enumerados «enumerado» Sexo hombre mujer «enumerado» VíaPúblic a calle plaza avenida carretera «enumerado» Categoría infantil aventuras cienciaficción drama October 204 Introduction to Software Engineering and Information Systems 35 IISSI 8

19 0/4/204 Entity-relationship diagrams Published by Peter Chen en 976. ing? Previous alternative to UML for ing. identificador atributo Entidad atributo mín:máx identificador interrelación mín:máx Entidad atributo atributo P. Chen, The Entity- Model - Toward a Unified View of Data. ACM Transactions on Database Systems (): 9 36, 976. October 204 Introduction to Software Engineering and Information Systems 36 Entities idjugador Regular Jugador Equipo ing? posición país Weak s Partido fecha idjugador Jugador 0:N 0: juegaen Equipo posición país idpersona 0:2 Padre Persona espadrede 0:N Hijo October 204 Introduction to Software Engineering and Information Systems 37 IISSI 9

20 0/4/204 Equivalence of notations ing? código 0:N Asignatura número fecha Asignatura apareceen 0:N Matricula Matrícula 0:N realizadapor Alumno idalumno class Ejemplo matrícula Asignatura código aparec een M atríc ula número fecha realizadapor Alumno idalumno October 204 Introduction to Software Engineering and Information Systems 38 ing? Conceptual Recommended steps:. Analyze the information about the problem domain (glossary) and requirements. 2. Identify possible entities and attributes. 3. Identify possible associations. 4. Incrementally build the identifying the multiplicity of the associations. 5. Identify classifications between entities with common properties (attributes and/or associations). 6. Identify composition between entities. 7. Add the constraints that cannot be graphically expressed. 8. Validate with possible scenarios using object diagrams. 9. Register all semantic problems that must be discussed with customers and users. October 204 Introduction to Software Engineering and Information Systems 39 IISSI 20

21 0/4/204 Bibliography ing? C. Larman, UML y Patrones. Ed. Prentice-Hall, 999. Chapters 9 to 2 C. Larman, UML y Patrones (2ª edición). Ed. Prentice-Hall, Chapters 0 to 2 M. Fowler, UML Distilled (3 rd edition). Ed. Addison-Wesley, Chapter 3 October 204 Introduction to Software Engineering and Information Systems 40 IISSI 2

Requirements Analysis and Negotiation

Requirements Analysis and Negotiation Analysis and Negotiation Software Engineering and Databases Group Department of Computer s and Systems University of Seville Analysis and Negotiation Learning objectives Know the objectives, products and