SlideShare a Scribd company logo
1 of 23
Download to read offline
Unit 3

 Object Oriented analysis process
2. Identifying use cases
3. Classification
4. Identifying object
   relationships,attributes and
   methods
Identifying use cases:
                 Objective
•   Use case modeling and analysis
•   Identifying actors
•   Identifying use cases
•   Developing effective documentation
Identifying use cases
• Introduction
• Objective of analysis
  – To capture complete, unambiguous , consistent
    picture of requirements of system
  – Separating system’s behavior from behavior
    implementation
     • What the system must do to satisfy users requirement and
       needs
     • Won't specify how to do it
     • Requires to view the system from users perspective
Cont.. Of introduction
• Transformation 1
  – users need to problem statement and
    requirement
• Tools to extract information about a
  system
  – examination of existing system documentation
  – Interviews
  – Questionnaire
  – observation
Why analysis is a difficult activity
• Analysis activity involves understanding
  – problem
  – Associated constraints
  – Methods to overcome this constraints
• Iterative process
Cont..
• Sources that makes analysis difficult
  – Fuzzy descriptions
     • Bcs of interpretation problem
  – Incomplete requirements
     • Due to users forgetting to identify them, High cost,
       politics
  – Unnecessary features
Business object analysis:
 understanding the business layer
• Process of
  – understanding sys requirement
     • Developing use case
        – Discussing uses and objectives with users
        – Understanding expected inputs, desired response
     • Prototype
        – Helps to understand how the system ’ll be used
  – Establishing goals
• Outcome of this process
  – Identifying classes
  – Relationship
Use case driven object oriented
    analysis: the unified approach
                                      Identify
          Develop     Develop        classes ,      Refine
actors   usecase &   interaction   relationships,      &
          activity     diagram       attributes,    iterate
          diagram                     methods
           Build
         prototype
Business process modelling
• Not necessary for all project
• When required business process and
  requirements can be modelled to any level
  of detail
• Activity diagram support this modelling
• disadv
  – Time consuming process
• Adv
  – familiarity
yes   yes      Go to
           yes          Go to                                                   counter and
                     counter and                                                 check out
                       return                                                    the books
Return                 books
book?
                                               yes
                                   yes
                                                     Interlibrary
                                                         loan
                  borrow                       no
                   book?
                              no
                                                     Search for
                                                       book



                                         yes         Do
                 Do search
                                                research on
                                                   topics
                             no



                                         yes         Read news
                 Read news                           paper and
                 paper?
                             no                      magazine



         Acivty diagram –library system
Use case model
•   Senarios for understanding the system
•   Interaction bw user and system
•   Captures users goal and systems responsibility
•   Used to discover classes and relationship
•   Developed by talking to users
•   Use case model
    – Provides external view of the system
• Object model (UML class diagram)
    – Provides internal view
Use cases and microscope
• A use case is a sequence of transaction in a
  system whose task is to yield results of
  measurable value to an individual actor of the
  system
• Actor
  –   Role played by the user with respect to the system
  –   Single actor may perform many use cases
  –   Can be external system
  –   Can be one get value from the system, or just
      participate in the use case
Borrow books       uses

                                            Check library card
                        extends
                                      uses
                   Get an
              interlibrary loan
                                     uses

               Return books
member                                                 Circulation clerk

                Do research



         Read books and news paper




              Purchase supplies
                                                        supplier
Uses and extends association
• Uses
  – common sub flows are extracted and
    separate use case is created
  – Relationship bw usecase and extracted one is
    called uses relationships
• Extends
  – Used when use case is similar to other, but do
    bit more or more speciliazed
• Abstract use case
  – No initiating actor
  – Used by concrete use cases
• concrete use cases
  – Interacts with actors
Identifying actors
• Actor
   – Role played by the user
• Actors found thru answers of following question
   – Who is using the system
   – Who is affected by the system
   – Which group needs help from the system
   – Who affects the system, which user groups are needed by the
     system to perform it functions
   – Which external h/w or other systems use the system to perform
     tasks
   – What prob does this application solve and for whom
   – How do users use the system(ie use case), and what they are
     doing with the system
• Accounts need not be human. It is an external system
Identifying actor (cont..)
• Two-three rule
  – Used to identify the actors
  – Start with naming at least 2 or 3 , people who
    could serve as the actor in the system.other
    actor can be identified in the subsequent
    iteration
Guideline for finding use cases
• For each actor, find the tasks and function that
  the actor should be able to perform or that the
  system needs the actor to perform (use case)
• Name the use cases
• Describe the use cases briefly by applying terms
  with which the user is familiar (to make less
  ambiguous)
• Each use case has only one main actor
  – Isolate users from actor
  – Isolate actors from other actors(separate
    responsibilities)
  – Isolate use cases that have different initiating actors
How detailed must a use case be? When to
stop decomposing it and when to continue
• Develop system use case diag
• Draw package
  – to represent business domains of the system . for
    each package create child use case diagram
• Prepare at lest one senario for each use case
  – Each scenario shows different sequence of
    interaction , with all decisions definite
• When the lowest use case level is arrived, which
  can’t be broken further, sequence and
  collaboration diagram is drawn
Dividing use case into package
• Whole system is divided into many
  packages
• Each package encompasses multiple use
  cases
Developing effective documentation
• Effective document provides
  – Reference point
  – Form of communication
  – Reveals issues and gaps in the analysis and
    design
Guidelines for developing effective
            document
• Common cover
  – Identify document
  – Current version
  – Individuals responsible for doc
• 80-20 rule
  – 80% of work can be done with the 20% of doc.
  – 20% -easily accessible, 80%-only who needs can
    access
• Familiar vocabulary
• Make the doc as short as possible
• Organize the document
Unit 3

More Related Content

Similar to Unit 3

UX Workshop at Startit@KBC
UX Workshop at Startit@KBCUX Workshop at Startit@KBC
UX Workshop at Startit@KBCUXprobe
 
Usability Lab within Agile (by Ian Franklin at NUX Leeds January 2018)
Usability Lab within Agile (by Ian Franklin at NUX Leeds January 2018)Usability Lab within Agile (by Ian Franklin at NUX Leeds January 2018)
Usability Lab within Agile (by Ian Franklin at NUX Leeds January 2018)Northern User Experience
 
evaluation technique uni 2
evaluation technique uni 2evaluation technique uni 2
evaluation technique uni 2vrgokila
 
Session1 methods research_question
Session1 methods research_questionSession1 methods research_question
Session1 methods research_questionmilolostinspace
 
Assessing user experience of e-books in academic libraries
Assessing user experience of e-books in academic librariesAssessing user experience of e-books in academic libraries
Assessing user experience of e-books in academic librariesTao Zhang
 
Software Practice 12 breakout - Tracking usage and impact of software
Software Practice 12 breakout - Tracking usage and impact of softwareSoftware Practice 12 breakout - Tracking usage and impact of software
Software Practice 12 breakout - Tracking usage and impact of softwareSoftwarePractice
 
INTELLECTUAL AND PROPERTY RIGHTSunit 1 R23 (1).pptx
INTELLECTUAL AND PROPERTY RIGHTSunit 1 R23 (1).pptxINTELLECTUAL AND PROPERTY RIGHTSunit 1 R23 (1).pptx
INTELLECTUAL AND PROPERTY RIGHTSunit 1 R23 (1).pptxSamuelAbragham
 
Analytic emperical Mehods
Analytic emperical MehodsAnalytic emperical Mehods
Analytic emperical MehodsM Surendar
 
Lecture 6 Interaction Design for VR
Lecture 6 Interaction Design for VRLecture 6 Interaction Design for VR
Lecture 6 Interaction Design for VRMark Billinghurst
 
Validating Ideas Through Prototyping
Validating Ideas Through PrototypingValidating Ideas Through Prototyping
Validating Ideas Through PrototypingChris Risdon
 
Terra incognita with no GPS: A case study approach to mapping assessment
Terra incognita with no GPS: A case study approach to mapping assessmentTerra incognita with no GPS: A case study approach to mapping assessment
Terra incognita with no GPS: A case study approach to mapping assessmentMargot
 
User Experience Design Fundamentals - Part 1: Users & Goals
User Experience Design Fundamentals - Part 1: Users & GoalsUser Experience Design Fundamentals - Part 1: Users & Goals
User Experience Design Fundamentals - Part 1: Users & GoalsLaura B
 
Methods of research
Methods of researchMethods of research
Methods of researchNavneet Nair
 
COMP 4010: Lecture 5 - Interaction Design for Virtual Reality
COMP 4010: Lecture 5 - Interaction Design for Virtual RealityCOMP 4010: Lecture 5 - Interaction Design for Virtual Reality
COMP 4010: Lecture 5 - Interaction Design for Virtual RealityMark Billinghurst
 
Medical Research paper writing
Medical Research paper writingMedical Research paper writing
Medical Research paper writingdrnikhilpanse
 
Introduction to UX Research: Fundamentals of Contextual Inquiry
Introduction to UX Research: Fundamentals of Contextual InquiryIntroduction to UX Research: Fundamentals of Contextual Inquiry
Introduction to UX Research: Fundamentals of Contextual InquiryMarc Niola
 
UX 101: An Overview of User Experience
UX 101: An Overview of User ExperienceUX 101: An Overview of User Experience
UX 101: An Overview of User ExperienceBrad Gerstein
 

Similar to Unit 3 (20)

User Research
User ResearchUser Research
User Research
 
UX Workshop at Startit@KBC
UX Workshop at Startit@KBCUX Workshop at Startit@KBC
UX Workshop at Startit@KBC
 
Usability Lab within Agile (by Ian Franklin at NUX Leeds January 2018)
Usability Lab within Agile (by Ian Franklin at NUX Leeds January 2018)Usability Lab within Agile (by Ian Franklin at NUX Leeds January 2018)
Usability Lab within Agile (by Ian Franklin at NUX Leeds January 2018)
 
R vaughan
R vaughanR vaughan
R vaughan
 
evaluation technique uni 2
evaluation technique uni 2evaluation technique uni 2
evaluation technique uni 2
 
Session1 methods research_question
Session1 methods research_questionSession1 methods research_question
Session1 methods research_question
 
Assessing user experience of e-books in academic libraries
Assessing user experience of e-books in academic librariesAssessing user experience of e-books in academic libraries
Assessing user experience of e-books in academic libraries
 
Software Practice 12 breakout - Tracking usage and impact of software
Software Practice 12 breakout - Tracking usage and impact of softwareSoftware Practice 12 breakout - Tracking usage and impact of software
Software Practice 12 breakout - Tracking usage and impact of software
 
INTELLECTUAL AND PROPERTY RIGHTSunit 1 R23 (1).pptx
INTELLECTUAL AND PROPERTY RIGHTSunit 1 R23 (1).pptxINTELLECTUAL AND PROPERTY RIGHTSunit 1 R23 (1).pptx
INTELLECTUAL AND PROPERTY RIGHTSunit 1 R23 (1).pptx
 
Analytic emperical Mehods
Analytic emperical MehodsAnalytic emperical Mehods
Analytic emperical Mehods
 
Lecture 6 Interaction Design for VR
Lecture 6 Interaction Design for VRLecture 6 Interaction Design for VR
Lecture 6 Interaction Design for VR
 
Validating Ideas Through Prototyping
Validating Ideas Through PrototypingValidating Ideas Through Prototyping
Validating Ideas Through Prototyping
 
Terra incognita with no GPS: A case study approach to mapping assessment
Terra incognita with no GPS: A case study approach to mapping assessmentTerra incognita with no GPS: A case study approach to mapping assessment
Terra incognita with no GPS: A case study approach to mapping assessment
 
User Experience Design Fundamentals - Part 1: Users & Goals
User Experience Design Fundamentals - Part 1: Users & GoalsUser Experience Design Fundamentals - Part 1: Users & Goals
User Experience Design Fundamentals - Part 1: Users & Goals
 
Methods of research
Methods of researchMethods of research
Methods of research
 
COMP 4010: Lecture 5 - Interaction Design for Virtual Reality
COMP 4010: Lecture 5 - Interaction Design for Virtual RealityCOMP 4010: Lecture 5 - Interaction Design for Virtual Reality
COMP 4010: Lecture 5 - Interaction Design for Virtual Reality
 
Medical Research paper writing
Medical Research paper writingMedical Research paper writing
Medical Research paper writing
 
E3 chap-09
E3 chap-09E3 chap-09
E3 chap-09
 
Introduction to UX Research: Fundamentals of Contextual Inquiry
Introduction to UX Research: Fundamentals of Contextual InquiryIntroduction to UX Research: Fundamentals of Contextual Inquiry
Introduction to UX Research: Fundamentals of Contextual Inquiry
 
UX 101: An Overview of User Experience
UX 101: An Overview of User ExperienceUX 101: An Overview of User Experience
UX 101: An Overview of User Experience
 

More from gopal10scs185 (20)

Os4
Os4Os4
Os4
 
Os1
Os1Os1
Os1
 
Os8
Os8Os8
Os8
 
Os8
Os8Os8
Os8
 
Os7
Os7Os7
Os7
 
Os6
Os6Os6
Os6
 
Os4
Os4Os4
Os4
 
Os3
Os3Os3
Os3
 
Os2
Os2Os2
Os2
 
Unit4 desiging classes
Unit4 desiging classesUnit4 desiging classes
Unit4 desiging classes
 
Unit 5 testing
Unit 5 testingUnit 5 testing
Unit 5 testing
 
Unit 5
Unit 5Unit 5
Unit 5
 
Unit 5 usability and satisfaction test
Unit 5 usability and satisfaction testUnit 5 usability and satisfaction test
Unit 5 usability and satisfaction test
 
Unit 4 designing classes
Unit 4  designing classesUnit 4  designing classes
Unit 4 designing classes
 
Unit 3 attributes, methods, relationships
Unit 3 attributes, methods, relationshipsUnit 3 attributes, methods, relationships
Unit 3 attributes, methods, relationships
 
Design rule 31
Design rule 31Design rule 31
Design rule 31
 
Unit4 desiging classes
Unit4 desiging classesUnit4 desiging classes
Unit4 desiging classes
 
Unit three identifying actors
Unit three  identifying actorsUnit three  identifying actors
Unit three identifying actors
 
Unit 5 testing
Unit 5 testingUnit 5 testing
Unit 5 testing
 
Unit 5
Unit 5Unit 5
Unit 5
 

Recently uploaded

THE STATE OF STARTUP ECOSYSTEM - INDIA x JAPAN 2023
THE STATE OF STARTUP ECOSYSTEM - INDIA x JAPAN 2023THE STATE OF STARTUP ECOSYSTEM - INDIA x JAPAN 2023
THE STATE OF STARTUP ECOSYSTEM - INDIA x JAPAN 2023Joshua Flannery
 
Real-time Geospatial Aircraft Monitoring Using Apache Kafka
Real-time Geospatial Aircraft Monitoring Using Apache KafkaReal-time Geospatial Aircraft Monitoring Using Apache Kafka
Real-time Geospatial Aircraft Monitoring Using Apache KafkaHostedbyConfluent
 
Technology Governance & Migration In The AI Era
Technology Governance & Migration In The AI EraTechnology Governance & Migration In The AI Era
Technology Governance & Migration In The AI Era2toLead Limited
 
Bridge to the Future: Migrating to KRaft
Bridge to the Future: Migrating to KRaftBridge to the Future: Migrating to KRaft
Bridge to the Future: Migrating to KRaftHostedbyConfluent
 
Which standard is best for your content?
Which standard is best for your content?Which standard is best for your content?
Which standard is best for your content?Rustici Software
 
Mastering Kafka Consumer Distribution: A Guide to Efficient Scaling and Resou...
Mastering Kafka Consumer Distribution: A Guide to Efficient Scaling and Resou...Mastering Kafka Consumer Distribution: A Guide to Efficient Scaling and Resou...
Mastering Kafka Consumer Distribution: A Guide to Efficient Scaling and Resou...HostedbyConfluent
 
Aggregating Ad Events with Kafka Streams and Interactive Queries at Invidi
Aggregating Ad Events with Kafka Streams and Interactive Queries at InvidiAggregating Ad Events with Kafka Streams and Interactive Queries at Invidi
Aggregating Ad Events with Kafka Streams and Interactive Queries at InvidiHostedbyConfluent
 
Event Modeling Anti-patterns | Kafka Summit London
Event Modeling Anti-patterns | Kafka Summit LondonEvent Modeling Anti-patterns | Kafka Summit London
Event Modeling Anti-patterns | Kafka Summit LondonHostedbyConfluent
 
BODYPACK DIGITAL TECHNOLOGY STACK - 2024
BODYPACK DIGITAL TECHNOLOGY STACK - 2024BODYPACK DIGITAL TECHNOLOGY STACK - 2024
BODYPACK DIGITAL TECHNOLOGY STACK - 2024Andri H.
 
CERN IoT Kafka Pipelines | Kafka Summit London
CERN IoT Kafka Pipelines | Kafka Summit LondonCERN IoT Kafka Pipelines | Kafka Summit London
CERN IoT Kafka Pipelines | Kafka Summit LondonHostedbyConfluent
 
Attacking (and Defending) Apache Kafka | Kafka Summit London
Attacking (and Defending) Apache Kafka | Kafka Summit LondonAttacking (and Defending) Apache Kafka | Kafka Summit London
Attacking (and Defending) Apache Kafka | Kafka Summit LondonHostedbyConfluent
 
Transcript: Book industry state of the nation 2024 - Tech Forum 2024
Transcript: Book industry state of the nation 2024 - Tech Forum 2024Transcript: Book industry state of the nation 2024 - Tech Forum 2024
Transcript: Book industry state of the nation 2024 - Tech Forum 2024BookNet Canada
 
DS Lesson 2 - Subsets, Supersets and Power Set.pdf
DS Lesson 2 - Subsets, Supersets and Power Set.pdfDS Lesson 2 - Subsets, Supersets and Power Set.pdf
DS Lesson 2 - Subsets, Supersets and Power Set.pdfROWELL MARQUINA
 
Bitdefender-CSG-Report-creat7534-interactive
Bitdefender-CSG-Report-creat7534-interactiveBitdefender-CSG-Report-creat7534-interactive
Bitdefender-CSG-Report-creat7534-interactivestartupro
 
Transport in Open Pits______SM_MI10415MI
Transport in Open Pits______SM_MI10415MITransport in Open Pits______SM_MI10415MI
Transport in Open Pits______SM_MI10415MIRomil Mishra
 
Brick-by-Brick: Exploring the Elements of Apache Kafka®
Brick-by-Brick: Exploring the Elements of Apache Kafka®Brick-by-Brick: Exploring the Elements of Apache Kafka®
Brick-by-Brick: Exploring the Elements of Apache Kafka®HostedbyConfluent
 
Case Study: Implementing a Data Mesh at NORD/LB
Case Study: Implementing a Data Mesh at NORD/LBCase Study: Implementing a Data Mesh at NORD/LB
Case Study: Implementing a Data Mesh at NORD/LBHostedbyConfluent
 
Introduction to Cybersecurity | IIT(BHU)CyberSec
Introduction to Cybersecurity | IIT(BHU)CyberSecIntroduction to Cybersecurity | IIT(BHU)CyberSec
Introduction to Cybersecurity | IIT(BHU)CyberSecYashSomalkar
 
Apache Kafka's Common Pitfalls & Intricacies: A Customer Support Perspective
Apache Kafka's Common Pitfalls & Intricacies: A Customer Support PerspectiveApache Kafka's Common Pitfalls & Intricacies: A Customer Support Perspective
Apache Kafka's Common Pitfalls & Intricacies: A Customer Support PerspectiveHostedbyConfluent
 
Book industry state of the nation 2024 - Tech Forum 2024
Book industry state of the nation 2024 - Tech Forum 2024Book industry state of the nation 2024 - Tech Forum 2024
Book industry state of the nation 2024 - Tech Forum 2024BookNet Canada
 

Recently uploaded (20)

THE STATE OF STARTUP ECOSYSTEM - INDIA x JAPAN 2023
THE STATE OF STARTUP ECOSYSTEM - INDIA x JAPAN 2023THE STATE OF STARTUP ECOSYSTEM - INDIA x JAPAN 2023
THE STATE OF STARTUP ECOSYSTEM - INDIA x JAPAN 2023
 
Real-time Geospatial Aircraft Monitoring Using Apache Kafka
Real-time Geospatial Aircraft Monitoring Using Apache KafkaReal-time Geospatial Aircraft Monitoring Using Apache Kafka
Real-time Geospatial Aircraft Monitoring Using Apache Kafka
 
Technology Governance & Migration In The AI Era
Technology Governance & Migration In The AI EraTechnology Governance & Migration In The AI Era
Technology Governance & Migration In The AI Era
 
Bridge to the Future: Migrating to KRaft
Bridge to the Future: Migrating to KRaftBridge to the Future: Migrating to KRaft
Bridge to the Future: Migrating to KRaft
 
Which standard is best for your content?
Which standard is best for your content?Which standard is best for your content?
Which standard is best for your content?
 
Mastering Kafka Consumer Distribution: A Guide to Efficient Scaling and Resou...
Mastering Kafka Consumer Distribution: A Guide to Efficient Scaling and Resou...Mastering Kafka Consumer Distribution: A Guide to Efficient Scaling and Resou...
Mastering Kafka Consumer Distribution: A Guide to Efficient Scaling and Resou...
 
Aggregating Ad Events with Kafka Streams and Interactive Queries at Invidi
Aggregating Ad Events with Kafka Streams and Interactive Queries at InvidiAggregating Ad Events with Kafka Streams and Interactive Queries at Invidi
Aggregating Ad Events with Kafka Streams and Interactive Queries at Invidi
 
Event Modeling Anti-patterns | Kafka Summit London
Event Modeling Anti-patterns | Kafka Summit LondonEvent Modeling Anti-patterns | Kafka Summit London
Event Modeling Anti-patterns | Kafka Summit London
 
BODYPACK DIGITAL TECHNOLOGY STACK - 2024
BODYPACK DIGITAL TECHNOLOGY STACK - 2024BODYPACK DIGITAL TECHNOLOGY STACK - 2024
BODYPACK DIGITAL TECHNOLOGY STACK - 2024
 
CERN IoT Kafka Pipelines | Kafka Summit London
CERN IoT Kafka Pipelines | Kafka Summit LondonCERN IoT Kafka Pipelines | Kafka Summit London
CERN IoT Kafka Pipelines | Kafka Summit London
 
Attacking (and Defending) Apache Kafka | Kafka Summit London
Attacking (and Defending) Apache Kafka | Kafka Summit LondonAttacking (and Defending) Apache Kafka | Kafka Summit London
Attacking (and Defending) Apache Kafka | Kafka Summit London
 
Transcript: Book industry state of the nation 2024 - Tech Forum 2024
Transcript: Book industry state of the nation 2024 - Tech Forum 2024Transcript: Book industry state of the nation 2024 - Tech Forum 2024
Transcript: Book industry state of the nation 2024 - Tech Forum 2024
 
DS Lesson 2 - Subsets, Supersets and Power Set.pdf
DS Lesson 2 - Subsets, Supersets and Power Set.pdfDS Lesson 2 - Subsets, Supersets and Power Set.pdf
DS Lesson 2 - Subsets, Supersets and Power Set.pdf
 
Bitdefender-CSG-Report-creat7534-interactive
Bitdefender-CSG-Report-creat7534-interactiveBitdefender-CSG-Report-creat7534-interactive
Bitdefender-CSG-Report-creat7534-interactive
 
Transport in Open Pits______SM_MI10415MI
Transport in Open Pits______SM_MI10415MITransport in Open Pits______SM_MI10415MI
Transport in Open Pits______SM_MI10415MI
 
Brick-by-Brick: Exploring the Elements of Apache Kafka®
Brick-by-Brick: Exploring the Elements of Apache Kafka®Brick-by-Brick: Exploring the Elements of Apache Kafka®
Brick-by-Brick: Exploring the Elements of Apache Kafka®
 
Case Study: Implementing a Data Mesh at NORD/LB
Case Study: Implementing a Data Mesh at NORD/LBCase Study: Implementing a Data Mesh at NORD/LB
Case Study: Implementing a Data Mesh at NORD/LB
 
Introduction to Cybersecurity | IIT(BHU)CyberSec
Introduction to Cybersecurity | IIT(BHU)CyberSecIntroduction to Cybersecurity | IIT(BHU)CyberSec
Introduction to Cybersecurity | IIT(BHU)CyberSec
 
Apache Kafka's Common Pitfalls & Intricacies: A Customer Support Perspective
Apache Kafka's Common Pitfalls & Intricacies: A Customer Support PerspectiveApache Kafka's Common Pitfalls & Intricacies: A Customer Support Perspective
Apache Kafka's Common Pitfalls & Intricacies: A Customer Support Perspective
 
Book industry state of the nation 2024 - Tech Forum 2024
Book industry state of the nation 2024 - Tech Forum 2024Book industry state of the nation 2024 - Tech Forum 2024
Book industry state of the nation 2024 - Tech Forum 2024
 

Unit 3

  • 1. Unit 3 Object Oriented analysis process 2. Identifying use cases 3. Classification 4. Identifying object relationships,attributes and methods
  • 2. Identifying use cases: Objective • Use case modeling and analysis • Identifying actors • Identifying use cases • Developing effective documentation
  • 3. Identifying use cases • Introduction • Objective of analysis – To capture complete, unambiguous , consistent picture of requirements of system – Separating system’s behavior from behavior implementation • What the system must do to satisfy users requirement and needs • Won't specify how to do it • Requires to view the system from users perspective
  • 4. Cont.. Of introduction • Transformation 1 – users need to problem statement and requirement • Tools to extract information about a system – examination of existing system documentation – Interviews – Questionnaire – observation
  • 5. Why analysis is a difficult activity • Analysis activity involves understanding – problem – Associated constraints – Methods to overcome this constraints • Iterative process
  • 6. Cont.. • Sources that makes analysis difficult – Fuzzy descriptions • Bcs of interpretation problem – Incomplete requirements • Due to users forgetting to identify them, High cost, politics – Unnecessary features
  • 7. Business object analysis: understanding the business layer • Process of – understanding sys requirement • Developing use case – Discussing uses and objectives with users – Understanding expected inputs, desired response • Prototype – Helps to understand how the system ’ll be used – Establishing goals • Outcome of this process – Identifying classes – Relationship
  • 8. Use case driven object oriented analysis: the unified approach Identify Develop Develop classes , Refine actors usecase & interaction relationships, & activity diagram attributes, iterate diagram methods Build prototype
  • 9. Business process modelling • Not necessary for all project • When required business process and requirements can be modelled to any level of detail • Activity diagram support this modelling • disadv – Time consuming process • Adv – familiarity
  • 10. yes yes Go to yes Go to counter and counter and check out return the books Return books book? yes yes Interlibrary loan borrow no book? no Search for book yes Do Do search research on topics no yes Read news Read news paper and paper? no magazine Acivty diagram –library system
  • 11. Use case model • Senarios for understanding the system • Interaction bw user and system • Captures users goal and systems responsibility • Used to discover classes and relationship • Developed by talking to users • Use case model – Provides external view of the system • Object model (UML class diagram) – Provides internal view
  • 12. Use cases and microscope • A use case is a sequence of transaction in a system whose task is to yield results of measurable value to an individual actor of the system • Actor – Role played by the user with respect to the system – Single actor may perform many use cases – Can be external system – Can be one get value from the system, or just participate in the use case
  • 13. Borrow books uses Check library card extends uses Get an interlibrary loan uses Return books member Circulation clerk Do research Read books and news paper Purchase supplies supplier
  • 14. Uses and extends association • Uses – common sub flows are extracted and separate use case is created – Relationship bw usecase and extracted one is called uses relationships • Extends – Used when use case is similar to other, but do bit more or more speciliazed
  • 15. • Abstract use case – No initiating actor – Used by concrete use cases • concrete use cases – Interacts with actors
  • 16. Identifying actors • Actor – Role played by the user • Actors found thru answers of following question – Who is using the system – Who is affected by the system – Which group needs help from the system – Who affects the system, which user groups are needed by the system to perform it functions – Which external h/w or other systems use the system to perform tasks – What prob does this application solve and for whom – How do users use the system(ie use case), and what they are doing with the system • Accounts need not be human. It is an external system
  • 17. Identifying actor (cont..) • Two-three rule – Used to identify the actors – Start with naming at least 2 or 3 , people who could serve as the actor in the system.other actor can be identified in the subsequent iteration
  • 18. Guideline for finding use cases • For each actor, find the tasks and function that the actor should be able to perform or that the system needs the actor to perform (use case) • Name the use cases • Describe the use cases briefly by applying terms with which the user is familiar (to make less ambiguous) • Each use case has only one main actor – Isolate users from actor – Isolate actors from other actors(separate responsibilities) – Isolate use cases that have different initiating actors
  • 19. How detailed must a use case be? When to stop decomposing it and when to continue • Develop system use case diag • Draw package – to represent business domains of the system . for each package create child use case diagram • Prepare at lest one senario for each use case – Each scenario shows different sequence of interaction , with all decisions definite • When the lowest use case level is arrived, which can’t be broken further, sequence and collaboration diagram is drawn
  • 20. Dividing use case into package • Whole system is divided into many packages • Each package encompasses multiple use cases
  • 21. Developing effective documentation • Effective document provides – Reference point – Form of communication – Reveals issues and gaps in the analysis and design
  • 22. Guidelines for developing effective document • Common cover – Identify document – Current version – Individuals responsible for doc • 80-20 rule – 80% of work can be done with the 20% of doc. – 20% -easily accessible, 80%-only who needs can access • Familiar vocabulary • Make the doc as short as possible • Organize the document