Enviar pesquisa
Carregar
Mod9
•
0 gostou
•
393 visualizações
P
pravin kumbhar
Seguir
Educação
Tecnologia
Denunciar
Compartilhar
Denunciar
Compartilhar
1 de 42
Baixar agora
Baixar para ler offline
Recomendados
Unit 4 designing classes
Unit 4 designing classes
gopal10scs185
Unit 2
Unit 2
ChhayaShelake
4.class diagramsusinguml
4.class diagramsusinguml
APU
Claas diagram
Claas diagram
baabtra.com - No. 1 supplier of quality freshers
Software Requirement Specification
Software Requirement Specification
Vishal Singh
Structured Vs, Object Oriented Analysis and Design
Structured Vs, Object Oriented Analysis and Design
Motaz Saad
Class diagram java
Class diagram java
ravinlaheri2
UML Modeling in Java
UML Modeling in Java
Daffodil International University
Recomendados
Unit 4 designing classes
Unit 4 designing classes
gopal10scs185
Unit 2
Unit 2
ChhayaShelake
4.class diagramsusinguml
4.class diagramsusinguml
APU
Claas diagram
Claas diagram
baabtra.com - No. 1 supplier of quality freshers
Software Requirement Specification
Software Requirement Specification
Vishal Singh
Structured Vs, Object Oriented Analysis and Design
Structured Vs, Object Oriented Analysis and Design
Motaz Saad
Class diagram java
Class diagram java
ravinlaheri2
UML Modeling in Java
UML Modeling in Java
Daffodil International University
Object Oriented Design
Object Oriented Design
Aravinth NSP
Object Oriented Design
Object Oriented Design
Sudarsun Santhiappan
Lect1
Lect1
sujitkumar Sujit.Karande
Object Oriented Analysis
Object Oriented Analysis
Pramod Parajuli
UNIT II STATIC UML DIAGRAMS.pptx
UNIT II STATIC UML DIAGRAMS.pptx
anguraju1
B vb script11
B vb script11
oakhrd
Behavioral pattern By:-Priyanka Pradhan
Behavioral pattern By:-Priyanka Pradhan
Priyanka Pradhan
Introduction to UML
Introduction to UML
yndaravind
Basics of Java
Basics of Java
Prarabdh Garg
Object Oriented Programming In .Net
Object Oriented Programming In .Net
Greg Sohl
Abap Inicio
Abap Inicio
unifor
Oo abap-sap-1206973306636228-5
Oo abap-sap-1206973306636228-5
prakash185645
From use case to software architecture
From use case to software architecture
Ahmad karawash
Lab manual
Lab manual
karthi s
Software engineering: design for reuse
Software engineering: design for reuse
Marco Brambilla
Object oriented basics
Object oriented basics
vamshimahi
Lab 4 (1).pdf
Lab 4 (1).pdf
MohammedAlobaidy16
Unified Modeling Language
Unified Modeling Language
GiO Friginal
Object oriented analysis
Object oriented analysis
Mahesh Bhalerao
CS8592-OOAD Lecture Notes Unit-2
CS8592-OOAD Lecture Notes Unit-2
Gobinath Subramaniam
Introduction to Nonprofit Accounting: The Basics
Introduction to Nonprofit Accounting: The Basics
TechSoup
How to Create and Manage Wizard in Odoo 17
How to Create and Manage Wizard in Odoo 17
Celine George
Mais conteúdo relacionado
Semelhante a Mod9
Object Oriented Design
Object Oriented Design
Aravinth NSP
Object Oriented Design
Object Oriented Design
Sudarsun Santhiappan
Lect1
Lect1
sujitkumar Sujit.Karande
Object Oriented Analysis
Object Oriented Analysis
Pramod Parajuli
UNIT II STATIC UML DIAGRAMS.pptx
UNIT II STATIC UML DIAGRAMS.pptx
anguraju1
B vb script11
B vb script11
oakhrd
Behavioral pattern By:-Priyanka Pradhan
Behavioral pattern By:-Priyanka Pradhan
Priyanka Pradhan
Introduction to UML
Introduction to UML
yndaravind
Basics of Java
Basics of Java
Prarabdh Garg
Object Oriented Programming In .Net
Object Oriented Programming In .Net
Greg Sohl
Abap Inicio
Abap Inicio
unifor
Oo abap-sap-1206973306636228-5
Oo abap-sap-1206973306636228-5
prakash185645
From use case to software architecture
From use case to software architecture
Ahmad karawash
Lab manual
Lab manual
karthi s
Software engineering: design for reuse
Software engineering: design for reuse
Marco Brambilla
Object oriented basics
Object oriented basics
vamshimahi
Lab 4 (1).pdf
Lab 4 (1).pdf
MohammedAlobaidy16
Unified Modeling Language
Unified Modeling Language
GiO Friginal
Object oriented analysis
Object oriented analysis
Mahesh Bhalerao
CS8592-OOAD Lecture Notes Unit-2
CS8592-OOAD Lecture Notes Unit-2
Gobinath Subramaniam
Semelhante a Mod9
(20)
Object Oriented Design
Object Oriented Design
Object Oriented Design
Object Oriented Design
Lect1
Lect1
Object Oriented Analysis
Object Oriented Analysis
UNIT II STATIC UML DIAGRAMS.pptx
UNIT II STATIC UML DIAGRAMS.pptx
B vb script11
B vb script11
Behavioral pattern By:-Priyanka Pradhan
Behavioral pattern By:-Priyanka Pradhan
Introduction to UML
Introduction to UML
Basics of Java
Basics of Java
Object Oriented Programming In .Net
Object Oriented Programming In .Net
Abap Inicio
Abap Inicio
Oo abap-sap-1206973306636228-5
Oo abap-sap-1206973306636228-5
From use case to software architecture
From use case to software architecture
Lab manual
Lab manual
Software engineering: design for reuse
Software engineering: design for reuse
Object oriented basics
Object oriented basics
Lab 4 (1).pdf
Lab 4 (1).pdf
Unified Modeling Language
Unified Modeling Language
Object oriented analysis
Object oriented analysis
CS8592-OOAD Lecture Notes Unit-2
CS8592-OOAD Lecture Notes Unit-2
Último
Introduction to Nonprofit Accounting: The Basics
Introduction to Nonprofit Accounting: The Basics
TechSoup
How to Create and Manage Wizard in Odoo 17
How to Create and Manage Wizard in Odoo 17
Celine George
Unit-V; Pricing (Pharma Marketing Management).pptx
Unit-V; Pricing (Pharma Marketing Management).pptx
VishalSingh1417
UGC NET Paper 1 Mathematical Reasoning & Aptitude.pdf
UGC NET Paper 1 Mathematical Reasoning & Aptitude.pdf
Nirmal Dwivedi
HMCS Vancouver Pre-Deployment Brief - May 2024 (Web Version).pptx
HMCS Vancouver Pre-Deployment Brief - May 2024 (Web Version).pptx
marlenawright1
Application orientated numerical on hev.ppt
Application orientated numerical on hev.ppt
RamjanShidvankar
Micro-Scholarship, What it is, How can it help me.pdf
Micro-Scholarship, What it is, How can it help me.pdf
Poh-Sun Goh
SOC 101 Demonstration of Learning Presentation
SOC 101 Demonstration of Learning Presentation
camerronhm
Food safety_Challenges food safety laboratories_.pdf
Food safety_Challenges food safety laboratories_.pdf
Sherif Taha
Kodo Millet PPT made by Ghanshyam bairwa college of Agriculture kumher bhara...
Kodo Millet PPT made by Ghanshyam bairwa college of Agriculture kumher bhara...
pradhanghanshyam7136
On National Teacher Day, meet the 2024-25 Kenan Fellows
On National Teacher Day, meet the 2024-25 Kenan Fellows
Mebane Rash
How to Manage Global Discount in Odoo 17 POS
How to Manage Global Discount in Odoo 17 POS
Celine George
SKILL OF INTRODUCING THE LESSON MICRO SKILLS.pptx
SKILL OF INTRODUCING THE LESSON MICRO SKILLS.pptx
Amanpreet Kaur
Unit 3 Emotional Intelligence and Spiritual Intelligence.pdf
Unit 3 Emotional Intelligence and Spiritual Intelligence.pdf
Dr Vijay Vishwakarma
Jual Obat Aborsi Hongkong ( Asli No.1 ) 085657271886 Obat Penggugur Kandungan...
Jual Obat Aborsi Hongkong ( Asli No.1 ) 085657271886 Obat Penggugur Kandungan...
ZurliaSoop
General Principles of Intellectual Property: Concepts of Intellectual Proper...
General Principles of Intellectual Property: Concepts of Intellectual Proper...
Poonam Aher Patil
Basic Civil Engineering first year Notes- Chapter 4 Building.pptx
Basic Civil Engineering first year Notes- Chapter 4 Building.pptx
Denish Jangid
How to Give a Domain for a Field in Odoo 17
How to Give a Domain for a Field in Odoo 17
Celine George
Understanding Accommodations and Modifications
Understanding Accommodations and Modifications
MJDuyan
Spatium Project Simulation student brief
Spatium Project Simulation student brief
Association for Project Management
Último
(20)
Introduction to Nonprofit Accounting: The Basics
Introduction to Nonprofit Accounting: The Basics
How to Create and Manage Wizard in Odoo 17
How to Create and Manage Wizard in Odoo 17
Unit-V; Pricing (Pharma Marketing Management).pptx
Unit-V; Pricing (Pharma Marketing Management).pptx
UGC NET Paper 1 Mathematical Reasoning & Aptitude.pdf
UGC NET Paper 1 Mathematical Reasoning & Aptitude.pdf
HMCS Vancouver Pre-Deployment Brief - May 2024 (Web Version).pptx
HMCS Vancouver Pre-Deployment Brief - May 2024 (Web Version).pptx
Application orientated numerical on hev.ppt
Application orientated numerical on hev.ppt
Micro-Scholarship, What it is, How can it help me.pdf
Micro-Scholarship, What it is, How can it help me.pdf
SOC 101 Demonstration of Learning Presentation
SOC 101 Demonstration of Learning Presentation
Food safety_Challenges food safety laboratories_.pdf
Food safety_Challenges food safety laboratories_.pdf
Kodo Millet PPT made by Ghanshyam bairwa college of Agriculture kumher bhara...
Kodo Millet PPT made by Ghanshyam bairwa college of Agriculture kumher bhara...
On National Teacher Day, meet the 2024-25 Kenan Fellows
On National Teacher Day, meet the 2024-25 Kenan Fellows
How to Manage Global Discount in Odoo 17 POS
How to Manage Global Discount in Odoo 17 POS
SKILL OF INTRODUCING THE LESSON MICRO SKILLS.pptx
SKILL OF INTRODUCING THE LESSON MICRO SKILLS.pptx
Unit 3 Emotional Intelligence and Spiritual Intelligence.pdf
Unit 3 Emotional Intelligence and Spiritual Intelligence.pdf
Jual Obat Aborsi Hongkong ( Asli No.1 ) 085657271886 Obat Penggugur Kandungan...
Jual Obat Aborsi Hongkong ( Asli No.1 ) 085657271886 Obat Penggugur Kandungan...
General Principles of Intellectual Property: Concepts of Intellectual Proper...
General Principles of Intellectual Property: Concepts of Intellectual Proper...
Basic Civil Engineering first year Notes- Chapter 4 Building.pptx
Basic Civil Engineering first year Notes- Chapter 4 Building.pptx
How to Give a Domain for a Field in Odoo 17
How to Give a Domain for a Field in Odoo 17
Understanding Accommodations and Modifications
Understanding Accommodations and Modifications
Spatium Project Simulation student brief
Spatium Project Simulation student brief
Mod9
1.
MODULE 9
OBJECT ORIENTED SYSTEM MODELLING Learning Units 9.1 Objects and their properties 9.2 Identifying objects in an application 9.3 Modelling systems with object Systems Analysis And Design © V. Rajaraman
2.
MOTIVATION
Information Systems are becoming very complex We thus need methods to design complex systems Main method is to break up a large system into a number of cooperation components and designing each component or subsystem separately Question: How do we do this? The main purpose of this module is to answer this question Systems Analysis And Design © V. Rajaraman 1 of 41
3.
DESIRABLE PROPERTIES OF
COMPONENTS Each subsystem or component must • Have clearly defined responsibility • Acts when requested by an "order" • How the component does its task need not be known to other components • What the component does should be known 9.1.1 System Analysis And Design © V. Rajaraman 2 of 41
4.
DESIRABLE PROPERTIES OF
COMPONENTS (CONTD) • Components must be general enough to be reusable • Variety of components should be reduced-this is facilitated by allowing components to inherit properties of other components • Another aid to genaralize the function of a component is to allow generic commands which make components do their task • This is called POLYMORPHISM 9.1.2 System Analysis And Design © V. Rajaraman 3 of 41
5.
OBJECT ORIENTED MODELLING
Use of component oriented design • Facilitates changes in the system at low cost • Promotes reuse of components • Problem of integrating components to configure large system simplified •Simplifies design of distributed systems 9.1.3 System Analysis And Design © V. Rajaraman 4 of 41
6.
OBJECT AND THEIR
PROPERTIES All tangible entities in an application can normally be modelled as objects For example: A student,a cycle,a train ticket Some intangible entities may also be modelled as objects For example: a bank account, stack data structure Objects with similar meaning and purpose grouped together as CLASS A member of a class is an object instance 9.1.4 System Analysis And Design © V. Rajaraman 5 of 41
7.
CHARACTERSTICS OF OBJECTS
All objects have attributes Example : student : Name Roll no Address Year Department All objects have a state Example Ticket : reserved, waiting list Student : present, absent 9.1.5 System Analysis And Design © V. Rajaraman 6 of 41
8.
CHARACTERSTICS OF OBJECTS
All objects have set of OPERATIONS which can be performed on them Operations determine object behavior Example : Admit student Cancel ticket 9.1.6 System Analysis And Design © V. Rajaraman 7 of 41
9.
CLASS DIAGRAM –
UML NOTATION Universal Modelling Language (UML) is an industry standard notation to represent a class Example of UML notation for a Class Vendor CLASS NAME Vendor id Name LIST OF ATTRIBUTES Address Vendor type Add vendor Delete vendor OPERATIONS OR (METHODS) Find address Change address Find vendor type 9.1.7 System Analysis And Design © V. Rajaraman 8 of 41
10.
INSTANCE DIAGRAM –
UML NOTATION Shows an object instance's attributes and values EXAMPLE Class name Object name and its A 2546 : VENDOR Class name VENDORNAME = AD SINGH & CO Vendor id VENDOR TYPE = DISTRIBUTOR Attributes and their VENDOR ADDRESS = 5, MALL values ROAD,KANPUR 208001 9.1.8 System Analysis And Design © V. Rajaraman 9 of 41
11.
OPERATION TYPES ON
OBJECTS Constructor-creating new instances of a class Deleting existing instance of class Example : add new vendor Query - accessing state without changing value - has no side effects Example : find vendor address 9.1.9 System Analysis And Design © V. Rajaraman 10 of 41
12.
OPERATION TYPES ON
OBJECTS Update - changes value of one or more attributes - affect state of object - has side effects example : change address of vendor Implementation of operations on objects called methods 9.1.10 System Analysis And Design © V. Rajaraman 11 of 41
13.
IMPLEMENTATION OF CLASSES TERMINOLOGY
USED IN OBJECT ORIENTED MODELLING ABSTRACTION Picking necessary operation and attributes to specify objects ENCAPSULATION Hiding implementation details of methods from outside world ENCAPSULATION AlSO KNOWN AS INFORMATION HIDING INFORMATION HIDING ALLOWS IMPROVEMENT OR MODIFICATION OF METHODS USED BY OBJECTS WITHOUT AFFECTING OTHER PARTS OF A SYSTEM 9.1.11 System Analysis And Design © V. Rajaraman 12 of 41
14.
VIEW OF OBJECTS
AS CONTRACTORS 1) Objects can be thought of contractors who carry out assigned contracts for clients 2) Clients need not know how the contractor carries out its contracts 3) Contractors can modify/improve methods they use to carry out contracts without “informing” clients 4) External interface presented to clients remain same 9.1.12 System Analysis And Design © V. Rajaraman 13 of 41
15.
INHERITANCE
New classes are created from current classes by using the idea of inheritance New classes inherit attributes and/or operations of existing classes Inheritance allows both generalisation and specialisation in modelling Specialisation - given student class, arts students and science student are two subclasses -Subclasses inherit properties of parents and in addition may have their own special attributes and operations 9.1.13 System Analysis And Design © V. Rajaraman 14 of 41
16.
EXAMPLE OF INHERITANCE
Class name College student Roll no Attributes Name Address Year of study Operations Admit Promote Science student Class Name Arts student Roll no Name Roll no Address Name Year of study Attributes Address Department Year of study Laboratory name Department Admit Admit Promote Operations Promote Calculate laboratory fee Calculate field trip fee 9.1.14 System Analysis And Design © V. Rajaraman 15 of 41
17.
GENERALISATION/SPECIALISATION Given a
class Eye surgeon we can generalize it to surgeons which will inherit most of the attributes and operations of the eye surgeon A general class School, will inherit many properties of middle school, primary school Given a class Doctor we can obtain subclasses : Surgeon, Physician, General Practitioner, Consulting Doctor.All these will inherit many properties of doctor and will have their own new attributes and operations 9.1.15 System Analysis And Design © V. Rajaraman 16 of 41
18.
POLYMORPHISM
By polymorphism we mean ability to manipulate objects of different distinct classes knowing only their common properties Consider classes hospital & school For both the operation admit will be meaningful - they will be interpreted differently by each class Advantage of polymorphism is ease of understanding by a client A client gives a generic request - each contractor interprets and executes request as appropriate to the circumstances 9.1.16 System Analysis And Design © V. Rajaraman 17 of 41
19.
IDENTIFYING OBJECTS
Simple method - identify nouns in Requirements specification. These are potential objects - Identify verbs in requirements specification. These are potential operations 9.2.1 System Analysis And Design © V. Rajaraman 18 of 41
20.
CRITERIA FOR PICKING
OBJECTS 1) We remind that an object class has many objects as members 2) Wherever there is no possibility of confusion we use them synonymously 3) Objects should perform assigned services.In other words they must have responsibilities specified by us. 4) Objects must have relevant attributes which are necessary to perform service. Attributes must have Non-Null values. 9.2.2 System Analysis And Design © V. Rajaraman 19 of 41
21.
CRITERIA FOR PICKING
OBJECTS 5) A class must be essential for functioning of the system 6) Must have common set of attributes and operations which are necessary for all occurrences of the objects in the class 7) Objects should be independent of implementation of the system. 9.2.3 System Analysis And Design © V. Rajaraman 20 of 41
22.
HOW TO SELECT
OBJECTS 1) Potential objects selected from word statement primarily by examining noun phrases 2) All Noun phrases need not be objects 3) If there are some objects whose attributes do not change during the functioning of a system we reject them -They are probably external entities 4) We will illustrate selecting objects using examples 9.2.4 System Analysis And Design © V. Rajaraman 21 of 41
23.
EXAMPLE 1 –WORD
STATEMENT ESSENTIALS OF AN ADMISSION PROCESS TO A UNIVERSITY ARE Applicants send applications to a university registrar’s office A clerk in the registrar's office scrutinizes applications to see if mark list is enclosed and fee paid If scrutiny successful applications passed on to the relevant department 9.2.4 System Analysis And Design © V. Rajaraman 22 of 41
24.
EXAMPLE 1 –WORD
STATEMENT Departmental committee scrutinizes applications sent to it.Applications are ranked. Depending on the seats available decides to admit, wait list or reject.The application is returned with the message to the registrar’s office clerk. Registrar's office clerk informs the applicant the result of his applications 9.2.5 System Analysis And Design © V. Rajaraman 23 of 41
25.
EXAMPLE 1 –IDENTIFICATION
OF OBJECTS POTENTIAL OBJECTS 1. APPLICANT 2. APPLICATION 3. REGISTRAR’S OFFICE CLERK 4. DEPARTEMENTAL (COMMITTEE) How to select relevant objects? Decision based on answers to following questions Does it have attributes? Are operations performed on the attributes? 9.2.6 System Analysis And Design © V. Rajaraman 24 of 41
26.
EXAMPLE 1 –IDENTIFICATION
OF OBJECTS ANSWERS FOR EXAMPLE 1 1. Applicant has attributes. However no operations performed on it.It is not an object in this problem. 2. Application has attributes operations are performed using attributes of application.Result conveyed to applicant.Admit it as an object 3. Registrar’s office clerk has attributes,performs operations on application, attributes and not on clerk’s attributes.Thus reject. 4. Department taken as potential object.It has attributes.Operations are performed using attributes. Operations are performed using attributes of application object and also using attributes of department.Thus admit department as an object 9.2.7 System Analysis And Design © V. Rajaraman 25 of 41
27.
ATTRIBUTES AND OPERATIONS
PERFORMED BY IDENTIFIED OBJECTS CLASS NAME CLASS NAME APPLICATION DEPARTEMENT ATTRIBUTES ATTRIBUTES APPLICATION NUMBER DEPARTMENT CODE APPLICANT NAME DEPARTMENT NAME APPLICANT ADDRESS COURSE MARKS SHEET NO OF STUDENTS TO BE FEE PAID RECEIPT ADMITTED DEPT. APPLIED CODE NO ON WAIT LIST APPLN STATUS MIN. ENTRY QUALIFICATION CLERK CODE STATUS OF APPLICATION OPERATIONS OPERATIONS SCRUTINIZE SEND APPLICATION TO DEPT SEND RESPONSE SCRUTINIZE APPLICATION ADMIT/W.L/REJECT TO SEND APPLICATION STATUS APPLICANT 9.2.8 System Analysis And Design © V. Rajaraman 26 of 41
28.
EXAMPLE 2 :
RECEIVING ITEMS ORDERED ABSTRACT OF WORD STATEMENTS Receiving office receives several items from vendors Receiving office checks delivery note against orders and detects excess/deficient deliveries if any Discrepancy note (if any) sent to purchase office Receiving office sends items received note to inspection office Inspection office physically inspects items received and accepts good items.Bad items returned to vendor Items accepted note sent to stores office Discrepancy note sent to purchase office Stores office updates inventory based on items accepted note Stores office sends taken into stock report to the accounts office for payment to vendor Accounts office sends payments to vendors Candidate objects underlined 9.2.9 System Analysis And Design © V. Rajaraman 27 of 41
29.
PICKING RELEVANT OBJECTS
POTENTIAL OBJECTS (UNDERLINED IN LAST PPT) ARE: 1. RECEIVING OFFICE 2. ITEMS 3. VENDORS 4. DELIVERY NOTE 5. ORDERS 6. DISCREPANCY NOTE 7. PURCHASE OFFICE 8. ITEMS RECEIVED NOTE 9.INSPECTION OFFICE 10. ACCEPTED ITEMS NOTE 11. STORES OFFICE 12. INVENTORY 13. GOODS TAKEN IN STOCK REPORT 14. ACCOUNTS OFFICE 15. PAYMENT VOUCHER OBJECTS NOT RELEVANT TO THIS APPLICATION Items Orders Inventory As no operations on these Goods taken in stock Payment voucher RELEVANT OBJECTS Receiving office – Even though its own attributes are not relevant,its functional attributes are important.These are: -Delivery note and order to vendor It thus derives its attributes from these 9.2.10 System Analysis And Design © V. Rajaraman 28 of 41
30.
RELEVANT OBJECTS
VENDORS No operations on this object are needed in this application.However its attributes are necessary as the Accounts office makes payment to vendors CLASS : VENDORS ATTRIBUTES : Vendor code Vendor name Vendor address VENDOR is actually an external object.We have thus given only attributes relevant to this application.In general design one would usually define this object more comprehensively 9.2.11 System Analysis And Design © V. Rajaraman 29 of 41
31.
ATTRIBUTES OF DELIVERY
NOTE AND ORDER TO VENDOR CLASS : ORDER TO VENDOR CLASS : DELIVERY NOTE Attributes : Attributes : Receiving clerk id Order no Order no Vendor code Vendor code Item code Delivery date Item name Item code Qty ordered Qty supplied Units Units Price/Unit Order date Delivery period 9.2.12 System Analysis And Design © V. Rajaraman 30 of 41
32.
RECEIVING OFFICE OBJECT
Receiving office is selected as an object.Its attributes are attributes derived from delivery note and order to vendor The class diagram is give below CLASS RECEIVING OFFICE Is Part of Is Part of DELIVERY ORDER TO NOTE VENDOR 9.2.13 System Analysis And Design © V. Rajaraman 31 of 41
33.
RECEIVING OFFICE OBJECT
CLASS : RECEIVING OFFICE Attributes : Derived as shown in the previous slide Operations : Compare order no,item code, qty,etc in delivery note with that in order to vendor Send discrepancy note (if any) to purchase office and vendor.If no discrepancy send delivery note to purchase Send delivery note to inspection office(object) 9.2.14 System Analysis And Design © V. Rajaraman 32 of 41
34.
OTHER RELEVANT OBJECTS
CLASS : STORES OFFICE Attributes : Attributes of inspection office + qty in stock Operations : Update inventory by adding no of items accepted to qty in stock Send advice to accounts object to make payment for qty accepted 9.2.15 System Analysis And Design © V. Rajaraman 33 of 41
35.
NEXT OBJECT IS
INSPECTION OFFICE CLASS : INSPECTION OFFICE Attributes : Derived attributes from delivery note + no of items accepted Operations : Send information an accepted items to store and accounts Send discrepancy note( if any) to purchase office and vendor 9.2.16 System Analysis And Design © V. Rajaraman 34 of 41
36.
OTHER OBJECTS ARE
CLASS : ACCOUNTS OFFICE Attributes : Derived from inspection office attributes + price/unit of item Operations : Calculate amount to be paid Print cheque Request vendor object for vendor address Print vendor address label Dispatch payment to vendor Intimate Purchase office of payment 9.2.17 System Analysis And Design © V. Rajaraman 35 of 41
37.
OBJECT ORIENTED MODELLING-CRC
METHOD Steps in object oriented modelling 1) Find objects and their classes 2) Determine responsibilities of each object 3) State responsibilities, that is, actions. It can can carry out on its own using its knowledge 4) Determine objects with whom they collaborate. 5) State contracts each object assigns to its collaborations 6) A collaborator either performs a requested action or gives information 7) Document each class – its responsibilities,its collaborators and their responsibilities 8) Develop an object interaction/collaboration graph 9.3.1 System Analysis And Design © V. Rajaraman 36 of 41
38.
CRC TEAM IDEA
CRC TEAM : user's representative System analyst(s) project coordinator RESPONSIBILITY : Identify objects Specify responsibility Specify collaborators and their responsibilities Prepare a card for each class called class index cards 9.3.2 System Analysis And Design © V. Rajaraman 37 of 41
39.
CRC METHODOLOGY
1. Make CRC Card for each class CRC CARD CLASS NAME : SUPER CLASSES AND SUBCLASSES : SHORT DESCRIPTION OF CLASS : COLLABORATORS : PRIVATE RESPONSIBILITIES OF CLASS : CONTARCTS WITH COLLABORATORS : Develop a graph to show interaction between classes 9.3.3 System Analysis And Design © V. Rajaraman 38 of 41
40.
CRC MODEL -
EXAMPLE For Example1 of last learning unit the CRC model is given below Class : APPLICATION Super class : None Sub class : None Collaborators : DEPARTEMENT Description : This class represents applications received for admission to a university Private Responsibilities : Scrutinize : Applications are scrutinized to see if fee is paid and marks sheet is enclosed. If yes, applications is sent to department class.Else a rejected letter is sent to the applicant Contract(s) and Collaborator(s): Forward application to department : When it passes scrutiny else send reject to applicant Send letter to applicant : When Department notifies decision (Admit,Reject,Waitlist) send appropriate letter to the applicant 9.3.4 System Analysis And Design © V. Rajaraman 39 of 41
41.
CRC MODEL –
EXAMPLE (CONTD) Class : DEPARTMENT Super class : None Sub class : None Collaborators : APPLICATION Description : This class represents departments whose responsibility is to admit, reject or place an waiting list on application Private Responsibilities : Rank order applications based on selection criteria.Mark in application:admitted,rejected or in waiting list depending o available seats Contract(s) and Collaborator(s): Send reply to applicationclass on admitted, rejected or wait list 9.3.5 System Analysis And Design © V. Rajaraman 40 of 41
42.
COLLABORATION GRAPH
Examine application CLASS CLASS Admit/reject/wait list APPLICATION DEPARTMENT Application status Applicant COLLABORATION GRAPH FOR EXAMPLE2 Delivery CLASS CLASS Inspect RECEIVING OFFICE INSPECTION OFFICE Vendor Payment Update Delivery copy Inventory Discrepancy note CLASS CLASS CLASS PURCHASE OFFICE Payment ACCOUNTS OFFICE Make STORES OFFICE copy payment 9.3.6 System Analysis And Design © V. Rajaraman 41 of 41
Baixar agora