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.