DOMAIN CLASSES AND USE CASES
Start Part A, B, and C after you have completed Unit 3.
Start Part D after you have completed Part A, B, and C of this assignment.
Start Part E after you have completed Part D of this assignment.
REFERENCES
DELIVERABLES
This assignment requires that you develop and submit the following items for the proposed Car Sharing IS:
1. Use case diagrams
2. Problem domain classes
3. Use case descriptions
- Text should be submitted in MS-Word (or Word-compatible) or PDF (or PDF compatible) format.
- Diagrams must be prepared using one of the software tools suggested in Unit 0.
- If you would like to use another tool, you have to ask your tutor before you start with this assignment!
- If the diagrams are small (smaller than one page) you may paste them into a Word or PDF file instead of submitting a .gif or .jpg file. Make sure the diagrams are readable!
DETAILED DESCRIPTION AND REQUIREMENTS
PART A: USE CASE DIAGRAM
In the object-oriented approach, analysts use a collection of models based on use cases to capture system requirements-an approach referred to as use case driven.
This approach takes each use case and extends its requirements in more detail.
A use case is a convenient way to document a system's events. It serves as a kind of table of contents for the business events and activities that must be supported by the system. It will be used to identify how the system will be used and which actors will be involved in which use cases.
For the Car Sharing system, the use cases in which we are interested relate to the
following activities:
- membership - from recruitment to termination.
- accounts and billing.
- reservations.
- inventory - vehicles and locations.
- vehicle usage (completed trips).
For this part of the assignment, you will need to develop an overall use case diagram for the Car Sharing IS. This may be formatted as in Figures 3-13 to 3-16 on pages 82-84 of the textbook, or you may develop the use case diagram as outlined in the tutorial of your software tool.
Part A is worth 30 marks. Marking criteria are
- completeness and correctness (27 marks)
- organization and presentation (3 marks)
The organization and presentation of information are part of the interpersonal and
communication skills required of systems analysts.
PART B: PROBLEM DOMAIN CLASSES
You will develop a domain class model diagram for the proposed Car Sharing IS.
See the RMO example on p. 111 of the textbook.
First identify potential classes by thinking about each "thing" relevant to the Car Sharing IS. Next identify the relationships among things and define their attributes (see "'Things' in the Problem Domain" on pages 92-98 of the textbook for both tasks).
You now have the information required to define and draw the UML classes representing the "things" in the users' work environment. Carefully review pp. 101 111 of the textbook before working through the RMO domain class diagram in Figure 4-21 to 4-23 on pp. 109-111 of the textbook.
Now apply your skills and produce a domain class diagram for the proposed Car
Sharing IS for all data relating to
- membership - from recruitment to termination.
- accounts and billing.
- reservations.
- inventory - vehicles and locations.
- vehicle usage (completed trips).
Part B is worth 30 marks. Marking criteria are
- completeness and correctness (27 marks)
- organization and presentation (3 marks)
The organization and presentation of information are part of the interpersonal and
communication skills required of systems analysts.
PART C: USE CASE DESCRIPTIONS
In this part of the assignment, you will develop use case descriptions to refine the processing details for the use cases identified in the use case diagram developed in Part A.
Please carefully read the section "Use Case Descriptions" on pp. 121-124 before starting to develop the following use case descriptions:
- Fully developed use case descriptions: for the use case for making a reservation over the Web.
- (Figure 5-2 and 5-3 on pp. 123 and 124 of the textbook are good examples.)
- Page 3 of 5
- Brief use case description: for all other uses cases in the Car Sharing IS.
(Figure 5-1 on page 122 of the textbook is a good example.)
Part C is worth 20 marks. Marking criteria are
- completeness and correctness (18 marks)
- presentation - readability, use of references, etc. (2 marks)
PART D: ESSAY QUESTION
Please discuss why models and diagrams are created, and what benefits they bring to system analysis. Furthermore, discuss the three types of models in system development by explaining their purposes and in which situations to use and not to use each of these types.
In contrast to the question of the discussion forum in Unit 3, you are here expected to focus on models and diagrams in general, while the question in the discussion forum aims at the particular models/diagrams.
Please answer the questions above, using overall 200-300 words. Being able to answer questions precisely is part of the interpersonal and communication skills required of systems analysts; therefore, meeting the word limit is important.
Answers consisting of more than 300 words will be marked with 0 points, and answers of less than 200 words will receive reduced marks proportionate to the length of the answer.
Make sure that your answer is written in your own words rather than being copied either from the textbook or from another source! Cite the sources you use in your answer, and provide references. There should be at least two references in your answer, and at least one of them should not be the textbook. If you are not sure how to list and cite sources, please read "How to Cite Correctly" in the Important
Resources block on the right side of the course home page.
Part D is worth 10 marks. Marking criteria are
? completeness and correctness (9 marks)
? presentation - readability, use of references, etc. (1 mark)
PART E: REFLECTION ON THE ACTIVITIES OF THE ASSIGNMENT
In this part of the assignment, you are asked to reflect on the activities that you have completed for Assignment 2. Use your blog to reflect on your problems, insights, and contributions during and after your task-related activities. For example, you could ask yourself the following questions: What was easy and what was difficult in this assignment? What causes/caused me problems (and why)?
Which solutions or approaches have I found/tried that could also be useful for my colleagues? Where was I unable to find a solution (and why)? How do/did I approach the current problem? etc.
Do not include any concrete, specific solutions from your assignment in your reflection message! The goal of this activity is to write and reflect from a generic point of view rather than discussing concrete solutions!
The minimum requirement for this assignment is one blog posting of at least of 300 words. You are, of course, encouraged to post longer messages as well as more often!
Post your message to your blog on and also upload a copy of your posting for Assignment 2.
Part E is worth 10 marks. Marking criteria are
- level of reflection (9 marks)
- presentation - readability, etc.
The organization and presentation of information are part of the interpersonal and communication skills required of systems analysts.
SEQUENCE DI AGRAMS AND DESI GN CLASS DI AGRAMS REFERENCES
DELIVERABLES
This assignment requires that you develop and submit the following items for selected aspects of the proposed Car Sharing IS:
1. Design class diagram
2. First-cut sequence diagram
3. Multilayer design for sequence diagram
- Text should be submitted in MS-Word (or Word-compatible) or PDF (or PDF compatible) format.
- Diagrams must be prepared using one of the software tools suggested in Unit 0.
If you would like to use another tool, you have to ask your tutor before you start with this assignment!
- If the diagrams are small (smaller than one page) you may paste them into a Word or PDF file instead of submitting a .gif or .jpg file. Make sure the diagrams are readable!
DETAILED DESCRIPTION AND REQUIREMENTS
PART A: DESIGN CLASS DIAGRAM AND SEQUENCE DIAGRAMS
1. Create a preliminary version of the design class diagram (first-cut design class diagram) for the Car Sharing IS. This requires that you (a) elaborate class attributes, and (b) add navigation visibility arrows (see pp. 308-314 in the textbook). See Figure 10-16 on p. 314 of the textbook for an example of the output of this step. Do not submit the first-cut design class diagram from
the textbook!
2. Develop first-cut sequence diagrams to explain object interactions for the "Make Reservation through Web Interface" use case (see pp. 332-344) of the textbook, and follow the "Guidelines and Assumptions for First-Cut Sequence Diagram Development" on p. 344.
3. Develop a multilayer design for the "Make Reservation through Web Interface" use case. Follow the process in "Developing a Multilayer Design" on pp. 345-349 of the textbook.
4. Update the design class diagram by adding method signatures. Don't forget to include all methods (see discussion on pp. 351-353 of the textbook) and any controller classes required. See Figure 11-18 on p. 352 for an example of what is required.
Part A is worth 80 marks. Marking criteria are completeness and correctness of
o controller, boundary/view, data access classes
o methods - signatures, data passed/returned
o interactions - describe scenario completely and correctly
o attributes
Page 2 of 4
o visibility - navigation
o methods
o controller classes
The organization and presentation of information are part of the interpersonal and
communication skills required of systems analysts.
PART B: ESSAY QUESTION
The design phase includes the development of several diagrams. Explain why that many diagrams are needed and what the purpose/value of each of them is. Make sure that your description clearly states the need for each diagram and that it is therefore clear how this diagram is different from others.
Answer the questions above, using overall 300-400 words. Being able to answer questions precisely is part of the interpersonal and communication skills required of systems analysts; therefore, meeting the word limit is important.
Answers consisting of more than 400 words will be marked with 0 points, and answers of less than 300 words will receive reduced marks proportionate to the length of the answer.
Make sure that your answer is written in your own words rather than being copied either from the textbook or from another source! Cite the sources you use in your answer, and provide references. There should be at least two references in your answer, and at least one of them should not be the textbook. If you are not sure how to list and cite sources, please read "How to Cite Correctly" in the Important Resources block on the right side of the course home page.
Part B is worth 10 marks. Marking criteria are completeness and correctness (9 marks)
presentation - readability, use of references, etc. (1 mark)
The organization and presentation of information are part of the interpersonal and
communication skills required of systems analysts.
PART C: REFLECTION ON THE ACTIVITIES OF THE ASSIGNMENT
- In this part of the assignment, you are asked to reflect on the activities that you have completed for Assignment 4. Use your blog to reflect on your problems, insights, and contributions during and after your task-related activities. For example, you could ask yourself the following questions: What was easy and what was difficult in this assignment? What causes/caused me problems (and why)?
- Which solutions or approaches have I found/tried that could also be useful for my
- colleagues? Where was I unable to find a solution (and why)? How do/did I approach the current problem? etc.
- Do not include any concrete, specific solutions from your assignment in your reflection message! The goal of this activity is to write and reflect from a generic point of view rather than discussing concrete solutions!
- The minimum requirement for this assignment is one blog posting of at least of 300 words. You are, of course, encouraged to post longer messages as well as more often!
- Post your message to your blog on and also upload a copy of your posting for Assignment 4.