Object-Oriented Software Development with UML - UNU-IIST ...

Conceptual Model – Concepts and Classes 51Concept Categoryphysical or tangible objects (or things)placesdocuments, specifications, designs, or descriptionsof thingstransactionsroles of peoplecontainers of other thingsthings in a containerExamplesPOST, House, Car, Sheep, People, AirplaneStore, Office, Airport, PoliceSationProductSpecification, ModuleDescription,FlightDescriptionSale, Payment, ReservationCashier, Student, Doctor, PilotStore, Bin, Library, AirplaneItem, Book, Passengerother computers or electro-mechanicalsystems external to our systemabstract noun conceptsCreditCardAuthorizationSystem,TrafficControlHunger, AcrophobiaAir-organisationshistoric events, incidentsprocesses(often not represented as a concept, butmay be)rules and policiescatalogsSalesDepartment, Club, ObjectAirlineSale, Robbery, Meeting, Flight, Crash,LandingSellingAProduct, BookingASeatRefundPolicy, CancellationPolicyProductCatalog, PartsCatalogrecords of finance, work, contracts, legalmattersReceipt, Ledger,MaintenanceLogEmploymentContract,financial instruments and servicesmanuals, booksLineOfCredit, StockEmployeeManual, RepairManualThis strategy is to create a list of candidate concepts from the client’s requirements description, initialinvestigation reports, system functions definitions, and use cases.Notice that the categories are not mutually exclusive and one concept may belong to more than category.Another useful and simple technique for identification of concepts is to identify the noun and noun phrasesin the textual descriptions of a problem domain, and consider them as candidate concepts or attributes.Report No. 259, July 2002UNU/IIST, P.O. Box 3058, Macau