*지* 스토어

*지*

개인

팔로워0 팔로우

소개

등록된 소개글이 없습니다.

전문분야 등록된 전문분야가 없습니다.

판매자 정보

학교정보

입력된 정보가 없습니다.

직장정보

입력된 정보가 없습니다.

자격증

입력된 정보가 없습니다.

판매지수

판매중 자료수

1개
전체 판매량

1개
최근 3개월 판매량

0개
자료후기 점수

-
자료문의 응답률

-

전체자료 1개

[시스템 분석 및 설계] Downtown Video Rental System

DOWNTOWN VIDEO RENTAL SYSTEMI N D E XDEFINITION OF PROJECT ANALYSIS PROJECT DESIGN PROJECT1.DEFINITION OF PROJECTDowntown Videos is a chain of 11 video stores scattered throughout a major metropolitan area in the Midwest. 2. Each store rents the videos and games. 3. Each store has the parameter of rating, category. 4. Each store provides mailing services and promotions about customer's household.. 5. Downtown video system updates the rental information and reports it to master. 6. Master can check the expiry date of the rented item by the system.2.ANALYSIS PROJECT2-1. EVENT TABLE 2-2. USE CASE DIAGRAM 2-3. USE CASE SCENARIO 2-4. CLASS DIAGRAM 2-5. SEQUENCE DIAGRAM2-1. EVENT TABLEEventTriggerSourceActivity/ Use CaseResponseDestinationCheck category of video and gameAsk availability of itemCustomerSelect itemAvailable item to rentCustomerRent itemChoose item ask for rentCustomerAsk for rentRent with approval require to be memberCustomerCheck out itemEnter rented itemCustomerGive paymentRt itemMasterProduce tracking reportsTracking reportsMasterIn the analyzing of the project, It was difficult for us to get through the barriers of constructing the event table. It took most of time that define events and those activities because these present the aim of the whole project. It couldn't be too cautious of us to add or delete the event and activity because of its effecting on subsystem. Right after constructing the Event table, we have just began to understand the phase of analysis.2-1. EVENT TABLE2-2. Use Case DiagramWe first designed the Event table and then, we designed the Use Case Diagram. It was not quite difficult to design the Use Case Diagram from Event table, after knowing that the each activity in Event table was same to each of Use Case. If the activity in event table is clearly defined, we think that it is not hard to design the Use Case Diagram.2-2. Use Case Diagram1. Select item ● Main Customer selects the category of video and game that he wants and asks it ks whether the customer is qualified or not and if so, the clerk gives item with approval. ● Exception Conditions If customer is the new, let him know the necessity of membership and become a member2-3. Use Case Scenario3. Give payment ● Main Downtown takes what the customer rented. after checking it out, clerk receives the payments. 4. Return item ● Main On falling the time of due, customer returns and the clerk records item when it is returned. ● Exception Conditions When the due date is expired, the clerk sends notice to customer and gives the fee of penalty.2-3. Use Case Scenario[con't]5. Create new member ● Main In case of new customer, clerk suggest becoming a member, then takes customer's basic qualifications and information of his household additionally. ● Exception Conditions If customer doesn't want, clerk denies renting. 6. Provide special mail and promotion ● Main To extend customer, master provides special mailing and service of promotion to the family of customer. ● Excep Use Case Scenario [con't]2-4.Class DiagramWhat we focused on constructing the Class diagram is setting up the definition of object and the function of association, so, that gave us a difficulty on this part After defining of the class, we needed to distinguish what the parameter is. As the project is usually found in our circumstances, parameter could be found easily. After that, the cardinality has been left. Cardinality shows the association between classes. We defined the cardinality from the association among the classes. Finally, we created the Class diagram through these path.2-4. Class Diagram2-5. Sequence Diagram ( for Member management )2-5. Sequence Diagram (for Rent)As we know, the Class diagram gives the way of constructing the sequence diagram. The first thing we need to do was finding enter the customer and the flow of information in system sequentially. We add actors and object, and then we put the sequence and association of those things. Lifeline was left. Each meanin of constructing the State chart. But the concept of state chart was still away from us though we started to construct. We had caught it from referring the other books. From the base that each class generates each State diagram, all states that come from the rental object and customer object were defined and arranged the changes of those,besides factors that let the state changed. The different ideas among us made it modified over and over. It gave us meaning of what the State chart is.2-6. State Chart3. DESIGN PROJECT Design class diagram(short-form]Design class diagram is the highest level of this project and the most difficult part of this project. At first, we didn't understand what the method is and how to use it. Additionally, design phase is strange for us whom had just studied about analysis part. From checking the Class diagram again, we created the method that had been modified several times. It was also hard to allot the input values and find the best. After we designed the how}

공학/기술| 2004.03.12| 21페이지| 1,000원| 조회(674)

시스템분석, uml, 비디오 렌탈 시스템

미리보기

닫기