CarRentalAdministration

1、car rental administrationmay 2009 version 1.1byclass 1qper s laursen &susanne rugeroskilde business academytable of contentstable of contents21.inception phase31.1.purpose31.2.overview of activities31.3.elicit stakeholders requests31.4.find actors and use cases31.5.structure the use case diagram

2、51.6.detail a use case52.elaboration phase, iteration e162.1.overview of activities62.2.develop the domain model62.3.architectural analysis82.4.use case analysis92.5.gui design92.6.use case design92.6.1.system sequence diagrams92.6.2.operation contracts102.7.class design102.7.1.sequence diagrams102.

3、7.2.design class diagram112.7.3.start up112.8.coding of classes121. inception phase1.1. purposethe purpose of inception phase is to state the system requirements and the boundary of the system, find the actors and use cases. 1.2. overview of activitieswe will do the following activities:· elici

4、t stakeholders requests· find actors and use cases· structure the use case diagram· detail a use case· (revise project plan & risk list· develop iteration plan for elaboration, e1)1.3. elicit stakeholders requeststhe users at the car rental are customer, sales manager, s

5、alesman, serviceman,. a customer search for cars for rent based upon certain criteria.the sales manager uses the system to register cars, make statistics etc.the bla, bla, bla1.4. find actors and use casesprimary actors:sales managersalesmanserviceman customer.use cases:uc1: register caruc2: registe

6、r customeruc3: check in caruc4: check out caruc5: register contractuc6: 1.5. structure the use case diagramhere we present the use case diagram which shows the interaction between actors and use cases. bla, bla, bla (tell about this use case diagram)use case diagram here1.6. detail a use casehere we

7、 detail the use case which we have chosen to be the first to work on in our project. the use case is described fully dressed (partly).bla, bla, bla (tell about this use case)uc1: register carscope: next generation it application for car rental businesses.level: user goalprimary actor: managerstakeho

8、lders and interests:manager: wants fast, reliable registration of car information. wants to be able to register cars before they arrive at the company.salesman: wants the right information about the cars in the rental system. sales manager: wants to know information about the cars.preconditions: man

9、ager authenticated and identified. success guarantee: car is saved.main success scenario: 1. need for registration of car occurs.2. manager starts new car registration.3. manager enters car information (regno, regdate, model, brand, type, color, price)4. system saves car.5. system presents car infor

10、mation. alternative scenarios:bla, bla, bla2. elaboration phase, iteration e12.1. overview of activitieswe will do the following activities:· .· develop the domain model· architectural analysis· use case analysis· use case design· gui design· plan coding· codi

11、ng of classes· unit testing· (revise project plan & risk list· develop iteration plan for elaboration, e2)2.2. develop the domain modelthe classes in our domain model are based on the use case registercar. (tell about the classes, attributes and structures)domain model here2.3. ar

12、chitectural analysisthe architecture in our system consists of 3 layers. on top we have all the guis, below we have our collections/controllers and at the bottom the model classes. 2.4. use case analysisto help make the domain model, we do use case analysis. by looking at our use cases we are able t

13、o make the classes, associations and finding the attributes. between the class . and the class. we chose the structure composition because an object in class cannot exist without an object in class . bla, bla, bla2.5. gui designthis is how we have decided that our guis should look like:gui-design he

14、rethis design we think is easy to use and therefore very user-friendly. bla, bla, bla. the above gui is a template which we intend to follow when designing the other guis. 2.6. use case designin use case design we do the system sequence diagrams (ssd) and the operation contracts for the use case reg

15、ister car. 2.6.1. system sequence diagramsuc1: register car2.6.2. operation contractshere we show the operation contracts for the use case register car. we show the ones that change the domain model. 2.7. class designthe ssds and operation contracts shows the system from a real-world point of view.

16、in class design we move into the world of software. here we show - by doing sequence diagrams and design class diagram - the design of our software.bla, bla, bla (tell about how you did it using grasp-patterns)2.7.1. sequence diagramssequence diagram here2.7.2. design class diagramby looking at the object design in our sequence diagram we are able to transform this into the design class diagram. the design class diagram shows the classes, their attributes and operations (signatures). also the rela