1. There is a client requirement document 1.1 Represent the categories of the re
ID: 3873963 • Letter: 1
Question
1. There is a client requirement document
1.1 Represent the categories of the requirements that client-requirement document can be grouped.
1.2 Define every category by analyzing the following client-requirement document to design a software package of Car Gallery:
a). The computer system should track the document flow of the company.
b). The Windows XP operating system should be used
c). The software should provide the automation of the following activity of
the Car Gallery:
1. Renting of car
2. Selling of car
3. Preparing the documents for selling of car
4. Preparing the documents for renting of car
d). Records of the following lists in a computer system are to be orgarnized
sequentially:
1. List of the selling cars.
2. List of the renting cards.
e). The system should permit easy and efficient maintenance
f). Software package must comply with corporate standards.
g). Booking requests for selling and renting of cars should be supplied
weekly to manager.
h). The clerk of the Car Gallery must log in to the system.
i). The design of software package should be accomplished in two years
j). Control information must be supplied regularly for management.
k). The size of the database should be less than 4 gigabytes.
2. Identify use case and related actors by using client requirements docments in question 1. Draw the results in a UML use case diagram. Briefly make a description for every actor and cases.
3. Write a description of one use case in expanded, essential, conversational style. In both a typical course of events, and an alternatives section. In the alternatives section, list two frequent alternatives. Draw a use case diagram according to the description.
4. Give definitions and explain differences between "extend" and "include" relationships in use case diagram
5. What is the cheapest phase in a software development life cycle?
A) Analysis of requirements B) Design C) Implementation D) Maintenance
6. Represent and explain classification of non-functional requirements
7. Represent and explain abstraction levels in software Development Process.
8. Represent collection of UML diagrams and relationships between them.
COM411/SWE322/SWE201 Software Engineering M MIDTERY Time allowed 90 minutes Instructor Dr. Adil Amirjano Student 1D: 2e Student name: p. Questions: aAD P" I. There is a client-requirement document 1.1 (4) Represent the categories of the requirements that client-requirement document can be grouped 1.2 (22) Define every category by analyzing the following client-requirement document to design software package of Car Gallery a) The computer system should track the document flow of the company b) The Windows XP operating system should be used. c) The software should provide the automation of the following activity of the Car Gallery I. Renting of car 2. Selling of car 3. Preparing the documents for selling of car 4. Preparing the documents for renting of car Records of the following lists in a computer system are to be 1. d) List of the selling cars. 2. List of the renting cars. e) The system should permit easy and efficient maintenance D Software package must comply with corporate standards. g) Booking requests for selling and renting of cars should be supplied weekly to manager The clerk of the Car Gallery must log in to the system. h) i) The design of software package should be accomplished in two years. i) Control k) The size of the database should be less than 4 gigabytes. I information must be supplied regularly for management. 2. (20 pts) Identify use cases and related actors by using client requirements document in que Draw the results in a UML use case diagram. Briefly make a description for every actor an pts) Write a description of one use case in expanded, essential, conversational style. In both a typical course of events, and an alternatives section. In the alternatives section, list two frequent alternatives. Draw a use case diagram according to the description. 4. (10 pts) Give definitions and explain differences between "extend" and "include" relation use case diagram. 5. (5 pts) What is the cheapest phase in a software development life cycle? A) Analysis of requirements B) Design C) Implementation D) Maintenance 6. (10 pts) Represent and explain a classification of non-functional requirements. (10 pts) Represent and explain abstract tion levels in Software Development Process diagrams and relationships between them. 7.Explanation / Answer
4)Answer:
Extend:
Extend is a directed relationship that specifies how and when the behavior defined in usually supplementary (optional) extending use case can be inserted into the behavior defined in the extended use case.
Extended use case is meaningful on its own, it is independent of the extending use case. Extending use case typically defines optional behavior that is not necessarily meaningful by itself. The extend relationship is owned by the extending use case. The same extending use case can extend more than one use case, and extending use case may itself be extended.
The extension takes place at one or more extension points defined in the extended use case.
Extend relationship is shown as a dashed line with an open arrowhead directed from the extending use case to the extended (base) use case. The arrow is labeled with the keyword «extend».
Include:
Use case include is a directed relationship between two use cases which is used to show that behavior of the included use case (the addition) is inserted into the behavior of the including (the base) use case.
The include relationship could be used:
A large use case could have some behaviors which might be detached into distinct smaller use cases to be included back into the base use case using the UML include relationship. The purpose of this action is modularization of behaviors, making them more manageable.
differences:
Extend is used when a use case conditionally adds steps to another first class use case.
For example, imagine "Withdraw Cash" is a use case of an ATM machine. "Assess Fee" would extend Withdraw Cash and describe the conditional "extension point" that is instantiated when the ATM user doesn't bank at the ATM's owning institution.
Notice that the basic "Withdraw Cash" use case stands on its own, without the extension.
Include is used to extract use case fragments that are duplicated in multiple use cases.
The included use case cannot stand alone and the original use case is not complete without the included one.
This should be used sparingly an only in cases where the duplication is significant and exists by design (rather than by coincidence). For example, the flow of events that occurs at the beginning of every ATM use case (when the user puts in their ATM card, enters their PIN, and is shown the main menu) would be a good candidate for an include.
Related Questions
Navigate
Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.