important points to note -...
TRANSCRIPT
1
Important Points to Note
• All Participating colleges are requested to mute your audio lines during the webinar session.
• Participants are requested to make note of questions / responses to questions, if any, and pass them onto the Class Representative who can sit closer to the system to send out the messages on behalf of theclass.
• Question & Answer(Q&A) is scheduled at the end of the session and each college is given a chance toask 2-3 questions. Answers to the questions posted by colleges through chat option will also beanswered during the Q&A.
• Instructor may initiate relevant Polls at regular intervals during the session. Institutes are requested togain inputs from all the participants and provide your responses to these polls initiated by instructor.
• Session Feedback will be initiated at the end of the webinar. Institutes are requested to get thecollective opinion from the participants and provide your responses for the feedback questionnaire.
Requirement Elicitation and Analysis
Session Plan• Recap
• Requirement Elicitation and Analysis
• Use case diagram
• Activity diagram
• Papyrus UML tool
• Modelio UML tool
4
Recap: Introduction to InceptionIncepting an enterprise application is the first life cycle phase of raising enterprise applications that primarily consists of the following activities:
• Enterprise analysis
• Business modeling
• Requirements elicitation & analysis
• Requirements validation
• Planning and estimation
5
Requirement Elicitation and Analysis• Requirements elicitation and analysis is a systematic approach
of capturing client requirements, analyzing them and documenting the problem domain.
• There are various kinds of requirements which need to be elicited and are broadly divided into two categories:– Functional Requirements– Non Functional Requirements(NFR)
• Functional requirement elicitation and analysis starts with – enlisting the entities that use the system => Actors– the functional reasons why they will use the system => Use Cases
6
2. Customer initiates loan process
4. Pre approved loan amount generated by accounting system based on credit rating offered by external agency1. Prospect registers with bank
via internet / bank representative to be considered as customer
9. Approved loan amount is disbursed to customer
7. Verifier verify the documents and send for approval
Bank - Loan Management System
3. Customer provides information via internet or bank representative
5. Customer submit loan application for pre-approved loan amount (or less) or opt for higher amount6. Customer uploads necessary
documents or hands it over to bank representative for verification
8. Approver approves the loan
7
Actors
Human User / Role External System / device
Who is going to use the system?
8
2. Customer initiates loan process
4. Pre approved loan amount generated by accounting system based on credit rating offered by external agency1. Prospect registers with bank
via internet / bank representative to be considered as customer
9. Approved loan amount is disbursed to customer
7. Verifier verify the documents and send for approval
Bank - Loan Management System
3. Customer provides information via internet or bank representative
5. Customer submit loan application for pre-approved loan amount (or less) or opt for higher amount6. Customer uploads necessary
documents or hands it over to bank representative for verification
8. Approver approves the loan
9
Poll - Please provide your response
Identify the actors for the Loan Management system.i. Customer ii. Apartment Builder iii. Credit Rating system iv. Approver(a) i, ii and iv (b) i and ii (c) i and iii (d) i, iii and iv (e) i and iv
Loan Management System Actors• Prospect
• Customer
• Bank Representative
• Credit rating system
• Accounting system
• Document verifier
• Approver11
Use cases
• Prospect• Bank Representative• Customer• Credit rating system• Accounting system• Document verifier• Approver
Why does an actor need to interact with the system?
Initiates loan
Generate Preapproved loan amount based on customer’s credit rating
Upload documents
Verifies uploaded documents
Approves the loan
Loan disbursed
Register with the bank
12
Unified Modelling Language• Visual language of modelling business processes and software systems• Behavior diagram – what must happen in system being modelled
– Use case diagram – to represent functional requirements view– Activity diagram – describes business and operational step by step workflows of
components in a system
• Interaction diagram – flow of control and data in the system– Sequence diagram – depicts how objects communicate with each other in a
sequence of messages and indicates lifespan of objects
• Structure diagram – highlight what must be present in modelled system– Class diagram – describes structure of system– Deployment diagram - describes the hardware used in system implementations and
the execution environments and artifacts deployed on the hardware.
13
Use Case Diagram
• Identify actors
• Identify use cases
• Identify relationship between actor and use case
– Association
• Simplest relationship
• Represented by straight line
14
Loan Management System Use Case Diagram
Upload Document
Approve Loan
Review Document
Document Verifier
Approver
Prospect
Register Prospect
Customer
Credit Rating
System
Initiate Loan
Accounting
System
Bank
Representative
Disburse Loan
15
Relationships in use case diagram
• Relationship between actors
– Generalization
• Relationship between use cases
– Generalization
– Uses / Includes
– Extends<<include>>
<<extend>>
16
Generalization
• Actor • Use case
Bank Executive
Bank representative
Approver Document verifier
Initiate loan
Initiate loan by bank representativeInitiate loan by customer
17
Uses / Includes Relationship
• If use case always includes another use case
<<include>>
Initiate loan Provide customer information
18
Extends Relationship
• If use case optionally extends to another use case under some condition(s)
Initiate loan Provide credit rating
<<extend>>
If pre-approved loan is not updated in last six months
19
Poll - Please provide your response
Identify the relationship for the followingi. The passenger checks in at the airport. If he has baggage, the baggage also needs to be
checked in.ii. Group check in can be done at the airport. All members in the group has to check in
individually.(a) Both i and ii are include relationship (b) Both i and ii are extends relationship(c) i is extends and ii is includes relationship (d) i is includes and ii is extends relationship
Activity Diagram
• Represent workflow
• Similar to flow chart
• Used when scenarios are complex
21
LoMS Activity Diagram
Provide pre approved loanInitiate loan
Preapproved loan not update in last 6 months Provide credit
rating
Confirm loan amount
Upload docs Verify docs
Provide pre app loan amount
Approve loanIncorrect docs Docs verified
Disburse loan Loan approved
ApproverDocument verifierCredit rating systemAccounting systemCustomer
22
Introduction to Papyrus Tool• An open source, integrated modeling environment (IME)
• Built on Eclipse platform
• Provides diagram editors for Eclipse Modelling Framework-based modeling languages such as UML 2 and SysML
• Supports 5 UML Structural and 5 Behavioural diagrams
• Supports extending UML vocabulary through custom profiles and stereotypes
23
Installation of Papyrus• Standalone installation
– Install the Papyrus UML Eclipse Rich Client Platform from http://www.papyrusuml.org/scripts/home/publigen/content/templates/show.asp?P=114&L=EN&ITEMID=7
• Update site installation– Add the papyrus plugin to an existing installation of eclipse– In the menu bar, select Help-> Install New Software -> Add– Provide the update site corresponding to the version of Eclipse used.
(Ex:http://download.eclipse.org/modeling/mdt/papyrus/updates/releases/juno)– Select the papyrus packages and click on Finish to complete installation– Restart the Eclipse IDE
24
Papyrus Tool Demo
25
Introduction to Modelio• An open source rich client platform
• Supports 4 UML Structural and 4 Behavioural diagrams
• Supports extending UML vocabulary through custom profiles and stereotypes
• Installation of Modelio– Download the appropriate zip file from
http://www.modelio.org/downloads/download-modelio.html
– Unzip the file
– Use Modelio
26
Modelio Tool Demo
27
Summary
• Requirement elicitation and analysis
– Use case diagram
– Activity diagram
• Papyrus Tool
• Modelio Tool
28
References
• http://www.tutorialspoint.com/uml/uml_activity_diagram.htm
• http://www.uml-diagrams.org/use-case-diagrams.html
• www.eclipse.org/papyrus
• http://wiki.eclipse.org/Papyrus_User_Guide
• http://www.modelio.org
29
Thank You
30