Hướng dẫn Input_Trường hợp nghiên cứu 1: TraveLine Transit pdf

Tell the students that to create the UML diagrams, they first need to read the case study thoroughly and identify the key elements that would appear in the diagrams, such as actors, use

Instructor Inputs Pr

Tell the students that to create the UML diagrams, they first need to read the case study thoroughly and identify the key elements that would appear in the diagrams, such as actors, use cases, classes, and components

For the TraveLine Transit Services case study, some of the actors that can be identified are:

„ Employee

„ Operational department employee

„ CR department employee

„ Administrator

„ Customer

Some of the use cases that can be identified for the system are:

„ Log on

„ Log feedback

„ Display pending complaints

„ Accept investigation details

„ Accept corrective action details

„ Update status of feedback

„ Generate pending complaints report

„ Generate investigation report

„ Display feedback status

Some of the classes that can be identified for the system are:

„ Employee

„ OperationalDepartmentEmployee

„ CRDepartmentEmployee

„ Administrator

„ Customer

„ Feedback

„ Complaint

„ Suggestion

„ Commendation

Case Study 1: TraveLine Transit Services

1.4 Project ¤NIIT

The state diagram can be drawn for the Complaint class, where the various states for a Complaint object are:

„ New

„ Under Investigation

„ Investigation Complete

„ Closed

The sequence, communication, and activity diagrams can be drawn for any one of the identified use cases

Some of the components that can be depicted in the component diagram are:

„ Feedback entry

„ Complaint updation

„ EmployeeDatabaseMaintenance

Tell the students that to create the UML diagrams, they first need to read the case study thoroughly and identify the key elements that would appear in the diagrams, such as actors, use cases, classes, and components

For the MerryMeeting Event Organizers case study, some of the actors that can be

identified are:

„ Client

„ Employee

„ CustomerCareRepresentative

„ Administrator

„ Attendee

„ Venue owner

Some of the use cases that can be identified for the system are:

„ Log on

„ Accept venue details

„ Display venue details

„ Register an event

„ Accept event details

„ Display event details

„ Accept payment

„ Accept fee (Charged from attendee for attending an event)

„ Accept customer details

„ Register for attending an event

„ Generate daily registration report

„ Generate daily events report

„ Display a list of upcoming events

Some of the classes that can be identified for the system are:

„ Client

„ Employee

„ CustomerCareRepresentative

„ Administrator

„ Attendee

„ Venue owner

„ Venue

Case Study 2: MerryMeeting Event Organizers

1.6 Project ¤NIIT

„ Event

The state diagram can be drawn for the Event class, where the various states for an Event object are:

„ Booked

„ Cancelled

„ Completed

The sequence, communication, and activity diagrams can be drawn for any one of the identified use cases

Some of the components that can be depicted in the component diagram are:

„ EventBooking

„ EventCancellation

„ ReportGeneration

Tell the students that to create the UML diagrams, they first need to read the case study thoroughly and identify the key elements that would appear in the diagrams, such as actors, use cases, classes, and components

For the Jessup’s case study, some of the actors that can be identified are:

„ Employee

„ Administrator

„ SeniorManagement

„ Sales&MarketingExecutive

„ SalesRepresentative

Some of the use cases that can be identified for the system are:

„ Log on

„ Accept product details

„ Display product details

„ Accept promotional scheme details

„ Display promotional scheme details

„ Accept wholesale dealer details

„ Display wholesale dealer details

„ Accept sales data

„ Accept sales data for products under promotional scheme

„ Track performance

„ Generate reports

Some of the classes that can be identified for the system are:

„ Employee

„ Administrator

„ SeniorManagement

„ Sales&MarketingExecutive

„ SalesRepresentative

„ Product

„ PromotionalScheme

„ Sales

„ WholesaleDealer

Case Study 3: Jessup’s – Manufacturer of Electronic

Consumer Goods

1.8 Project ¤NIIT

The state diagram can be drawn for the Product class, where the various states for a Product object are:

„ Normal

„ Discounted

„ With complimentary product

The sequence, communication, and activity diagrams can be drawn for any one of the identified use cases

Some of the components that can be depicted in the component diagram are:

„ AdminTasks

„ Sales

„ ReportGeneration

Tell the students that to create the UML diagrams, they first need to read the case study thoroughly and identify the key elements that would appear in the diagrams, such as actors, use cases, classes, and components

For the Heartland Home Finance case study, some of the actors that can be identified are:

„ Administrator

„ Manager

„ Accounts Department Employee

„ Sales Representative

Some of the use cases that can be identified for the system are:

„ Log on

„ Accept loan program details

„ Display loan program details

„ Accept branch office details

„ Display branch office details

„ View un-assigned loan application forms

„ Assign loan applications

„ Accept employee details

„ View performance of sales representatives

„ Update loan application form

„ Accept EMI payment details

„ Generate Payment Status report

„ Accept loan application form

„ Display application status

„ Display balance payments

„ Generate reports

Some of the classes that can be identified for the system are:

„ Administrator

„ Manager

„ AccountsDepartmentEmployee

„ SalesRepresentative

Case Study 4: Heartland Home Finance

1.10 Project ¤NIIT

„ LoanApplication

The state diagram can be drawn for the LoanApplication class, where the various states for a LoanApplication object are:

„ Processing

„ Approved

„ Rejected

The sequence, communication, and activity diagrams can be drawn for any one of the identified use cases

Some of the components that can be depicted in the component diagram are:

„ AdminTasks

„ SalesRepTasks

„ AccountsDepTasks

„ ReportGeneration

Tell the students that to create the UML diagrams, they first need to read the case study thoroughly and identify the key elements that would appear in the diagrams, such as actors, use cases, classes, and components

For the Cray Systems case study, some of the actors that can be identified are:

„ Administrator

„ Manager

„ HQ Employee

„ Branch Office Employee

„ Customer

Some of the use cases that can be identified for the system are:

„ Log on

„ Accept product and peripheral details

„ Accept/Modify branch office details

„ Display branch office details

„ Accept/Modify employee details

„ Display employee details

„ Accept customer details

„ Accept customer queries

„ Display query details

„ Assign queries to executives

„ Generate alerts related to query resolution status

„ Generate employee reports

„ Grade employees

„ Store query details

„ Provide solutions to queries

„ Generate reports on individual performance

„ Lodge query

„ Accept feedback

„ Display status of queries to customers

„ Generate reports

Case Study 5: Cray Systems

1.12 Project ¤NIIT

Some of the classes that can be identified for the system are:

„ Administrator

„ Manager

„ HQEmployee

„ BranchOfficeEmployee

„ Customer

„ QueryDetails

„ ProductDetails

The state diagram can be drawn for the QueryDetails class, where the various states for a QueryDetails object are:

„ Forwarded to Headquarters

„ Unassigned

„ Closed

„ Closed Unsuccessfully

„ Pending

The sequence, communication, and activity diagrams can be drawn for any one of the identified use cases

Some of the components that can be depicted in the component diagram are:

„ AdminTasks

„ ManagerialTasks

„ CustCareExecTasks

„ CustomerTasks

„ ReportGeneration

The guidelines for project allocation and evaluation are:

„ The project must be allocated to the students by the end of the second cycle

„ Each student must work on the project individually

„ During allocation, explain the scope of the project to the students by referring to the topics Project Activities and Project Timelines

„ Ask the students to refer to the sample case study and its solution provided in the Sample Project documentation

„ Ask the students to fill the appropriate documentation formats at each stage of project development

„ Demonstrate the sample solution by using the vsd file provided in the Project_Solution folder of the TIRM CD

„ Evaluate the students according to the guidelines provided in the topic Project Evaluation Guidelines

Project Execution

1.14 Project ¤NIIT