970 Words4 Pages
1.1 Assumptions: It is assumed that when the data is collected, the free cycle database has no renewal. The data of Edinburgh is gathered during March and April, 2014, There are insiders working as web editors, and they are authorized to block member IDs of who tried to lead improper transactions. Members are willing to provide their detail and reliable information. Members will consciously provide all the information expected of their offers, wants and their transaction behavior. Member ID can be withdrawn by members. 1.2 Limitations and improvement: Because of the spontaneity of the information provided, there might be lack of detail information. Time interval exists between the start and the end of a transaction may induce inaccurate transaction amount analyzed. Top-down approach is used in this new database design. Six entities, including web editor, member, wants, offering, category and items transacted are firstly identified. Category makes the search procedure much easier and helps summarize items that are transacted most frequently. Constraints on these entities, relationships and attributes are also added. Attributes as publish date and transaction date record the duration of transaction more precisely. According to this result, we can get the ratio of successful transaction within a particular period of time, which better estimates the efficiency of the free cycle website. Level of satisfaction is also listed for quality measurement. 2. Entity List: There are 6 entities identified by the organization to classify and store data: Member Want Offering Category Transacted Items Web Editor 3. Business rules The new database designed for more efficient data searching and storing classifies and analyses data based on 6 maj... ... middle of paper ... ... a member ID of member who published it. Also it stores level of satisfactory and how new is the goods evaluated by the member who received the offering. The relational schema is: {OffeID#, OfferName, CategoryRef, MemberID, O_Description, O_PublishDate, TransactionID, TransactStatus, TransactionDate, O_Address, LevelOfSatisfac, NewToOld_Condition,} Category: This table mainly contains the name and total amount of transaction of the category which is identified by categoryID of the transaction. The relational schema is: { CategoryRef#, CategoryName, TransactAmount} Transacted Items: This table is contained by Category Table, describe the name of transacted items under the category, amount of transaction and category reference. The items are identified by Transacted Item ID. The relational schema is: { TransactItemID#, TransactItemName, TransactAmount, CategoryRef}

More about lll

Open Document