Site-Wide Activity

  • Jonathan Latko‘s profile was updated 2 hours, 6 minutes ago

  • MAX Lab 1a and 1b assignment is due 5/29 end of the day. 
    Starting Section 3 material for review before class.
    MAX Lab 2a and 2b is due on June 4th end of the day.

  • Here is the exercise.

    Here is the solution.

    Here is the movie rental schema.

  • Leave your response as a comment on this post by the beginning of class on May 30, 2016. Your response only needs to be about three or four sentences. These weekly questions should reinforce class discussions, […]

    • In information systems, we use decision trees when constructing databases. However, there are other uses for decision trees. One situation where a decision tree would be helpful would be to decide between two options. For example, say you want to go on vacation with your family, but you can’t decide between two destinations. You could make a decision tree based on the weather of that location (if it is going to rain at one location, do not go there; if it is not going to rain at the other location, choose that location), flight prices, hotel prices, amount of activities, etc. “Decision” trees can be extremely helpful when trying to “decide” on something.

    • Other than the Business world, they can be used pretty in everyday life situations. If one has a good experience with decision trees in the business world, they can then translate it to the real world, when problems or decisions arise and need to be made. Decision trees are helpful, not only because they are graphics that help you ‘see’ what you are thinking, but also because making a decision tree requires a systematic, documented thought process. Often, the biggest limitation of our decision making is that we can only select from the known alternatives. Decision trees help formalize the brainstorming process so we can identify more potential solutions. Applied in real life, At times decision trees can be very complex and end up including pages of options. But, regardless of the complexity, decision trees are all based on the same principles. And someone we good experience or an extensive background in decision trees from the business world can perfectly translate to the real world.

    • When you get two great job offer and not sure which one to pick. I think, we all would love to have a situation like this and use Decision Tree. It will make our lives much more easier.

    • In my opinion, I think that a decision tree can be helpful not only in business, but also in personal choices as well. Decision tree makes everything easier to be understood. It is also helpful for those people who don’t know how to make decision come to a better decision. Decision tree is also a great tool to plan out a study plan or daily schedule. It laid everything out and it helps you to make the best decision.

    • Decision trees can help people make positive choices regardless of the subject. For example, when choosing which college to attend you could use a decision tree to outline the perks and potential experience of multiple schools. Included in the decision tree could be distance from home and how that effects your life, tuition costs and student loan debt, is it a small school or big school, etc. By using the decision tree to outline the possibilities of multiple options, you can give yourself a view of which path is best for you. Having the ability to see what each path has in store allows us to make the best decisions possible.

    • Decision trees can be helpful in analyzing any situation that has several possible outcomes, and that has yes or no answers to arrive at each outcome. I can see a decision tree being very helpful at work if you have a job that involves a certain process. For example, say you worked as a Credit Analyst. If someone applies for credit, you could follow the branch corresponding to how much money they make, which might take you to what their credit score is, which might tell you whether or not to lend to that person. Or if you work as a customer service representative, you might be able to ask: can you help the customer, can you not help the customer, or can you direct the customer to someone else who can help them. If you can help them, you would follow the branches corresponding to what their problem is. If you can’t help them, the process ends there. I see a decision tree as being helpful in our everyday jobs if we can tailor it specifically to what we do.

    • Other than in information systems, I think decision trees can be used in supply chain management. After taking MSOM 3101 I learned that it is best to visualize a process. For example a decision tree can be used when trying to visualize the process in a distribution center. The decision tree will allow someone to see the different outcomes depending on the business rules of the distribution center. The decision tree will be able to answer questions like, is the item in stock? If so what happens next? and more. Some people can visualize this process in their heads, while others need to visualize it on paper. The decision tree helps with that.

    • A decision trees are useful tool utilized within the information systems field. They allow for individuals to pan out possible outcomes for an event/scenario and also calculate the costs of each possibility. But decision trees can also come to great use in other fields than just the information systems sector. An area that decision trees would be resourceful would be in comparing choosing a college major. Myself, as well as any other college students, struggle with declaring / sticking with a major based off of the difficulty, work load, time management, and overall enjoyment of choosing a major. By laying out the different factors (tuition costs between schools, average salary pay post graduation, amount of time study a week, course load, etc.) it may help for a student better analyze which major will best accommodate their personal and professional wants and need and allow for a major best suited for that individual to be chosen.

    • This may be hard to relate if you are not too technical, but this is what I thought of. I sometimes write programs for fun, and one of the tools that can be very beneficial for creating a good program is a decision tree. Decision trees help you to visualize all the possible different choices, and it helps you to keep track of options that are further down each branch. It may be hard to completely conceptualize all the different choices that can be made later if you have already made a choice. Decision trees keep track of all the information that you need in order to understand what you, or a software program, should do. So, decision trees are very helpful for writing programs, and I can see where this same use could be transferred to other areas of life where decisions nested under other decisions is very common.

    • Decision tress can be useful in many personal and professional situations. One example I could have seen a decision tree be helpful was when I was working at a golf club. There was not a lot of structure for the training of new employees and completing the day end task that needed to be done before closing the shop. Having a plan of tasks for new employees gives employees a sense of structure and knowledge of how to complete a job in a timely fashion. I know I learn faster when I have a physical schedule of what I need to do. A decision tree is a good way to explain the task at hand.

    • Decision trees can be very helpful in corporate life as well, particularly in terms of setting standard procedures for dealing with structured problems. For example, people who work at call centers for after-sales service can benefit a lot if they have been trained to deal with customer issues with a decision tree. They would be able to know where to start to approach customers with appropriate questions and decide on actions needed to be taken based on yes or no answers from customers. Since most low-skill jobs are still concerned with highly structured problems, companies can use decision trees as a useful and effective training tool to help establish standard practices and procedures.
      Furthermore, decision trees are also helpful in everyday life whenever we are faced with decisions to make. For example, a family planning on where to go for vacation can use decision trees to take into account factors such as weather, sufficient financial resources, distances, visa availability etc.

    • I think that decision trees could be a very useful good tool no matter in your career or in your daily life. Sometimes we usually have a fear of choice, for example, there are a lot of possibility or complex factors need to be integrated, if you don’t draw it out, you will not be able to have a clear thinking and making a decision. Decision trees make the things easier, draw it out can help with your logical thinking, organizing your data, it also a very good records for an event to restore in a hardware such as a laptop or smart phone. so I love this fancy tool very much.

  • Here are the assignment instructions. 

    This assignment is due by the start of class on Tuesday, May 30th. 

  • Exam is Thursday at regular class time, we will start on time.
    Bring a number pencil.
    Closed book.
    25 Multiple choice questions.
    Half readings/terms/videos/lectures etc
    Half on diagram […]

  • Leave your response as a comment on this post by May 26, 2017. Remember, it only needs to be three or four sentences. For these weekly questions, I’m mainly interested in your opinions, not so much particular “f […]

    • The hardest part of creating an ERD is focusing on what is part of the database that the problem is asking for. It can be hard because there can be information that is not needed for the database and it can be deceiving. To deal with this, I would say to read the problem multiple times to fully understand what is needed for the ERD

    • I believe the trickiest thing is determining the useful entities in a problem. Closely followed by determining the relationship between each entity. Once you have found both pieces of information, it’s much simper to look out for the descriptive words for each. A good idea to determine the entities is to list each NOUN in the scenario and the cross off the list the ones that don’t have attributes, are duplicates or synonyms, or not applicable in any way. Taking the time to do this makes the ERD model process much easier.

    • One of the trickiest things for me about creating an ERD from a problem description is the entity/attribute identification. Sometimes I have trouble determining if a certain noun is supposed to be its’ own entity or if it just belongs as an attribute of another entity. In the process of determining that, I have to figure out where to place it in the ERD diagram and sometimes finding a relationship for it that makes sense is difficult. I have just been reading the problem multiple times and breaking it down noun by noun and eventually it all finds its’ place.

    • For me, the most difficult part of creating an ERD is identifying the actual question that is being asked and then entities that are necessary to answer this question. Having extra information can muddle the important information and confuse you. I think the best way to deal with this is to underline the actual question or write it down. Then as you work through the problem and begin identifying entities, refer back to the original question you are answering and make sure the entity is necessary to answer the problem.

    • In my view, the trickiest thing is to deal with relationships between different entities. For example, one to many, one to one, many to many are different and need to tell clearly. In addition, sometime one entity can has many matches during a period, but cannot has more than one match at the same time. It is complex and hard to deal with. In the real case, it might be harder. However, in class, there are clear stories. We should read them carefully and just follow the description.

    • Personally, the trickiest part about creating an ERD from a problem description is identifying the cardinality of the relationships and filtering through all the “extra” information to find the correct entities and their attributes. To help with identifying the cardinality, it is important to first analyze the text carefully to see if it explicitly references what the correct cardinality should be. If not clearly stated, then try to think logically about the relationships between the 2 entities and mark the cardinality based on that. To easily filter through all the extra information, I tend to box all of the entities and circle the attributes associated with them.

    • HI Everyone!

      For me, the difficulties in the Entity Relationship Diagram were defining the specifics of the relationship. Setting relationships cardinality and participation is important because it characterizes the relationship. When talking the problem out these details are quite obvious, but when I review the diagram I always question whether I did this portion correctly. I would advise anyone who has this same difficulty to focus on getting everything else set and then read through the scenarios to make sure what is said matches the rules described. Do not worry about the symbols being in the right place as the program will do this automatically. Rereading and verifying scenario to setup was the key to getting over this issue for me.

      Have a great week!

    • I think the thing I found trickiest with thing about creating an ERD from a problem description was piecing together the idea that entities can have multiple relationships to other entities. Like for instance maybe one entity has multiple relationships with multiple other entities, which has multiple relationships with even more entities. In our ER Modeling assignment (especially assignment 2), that took me the longest. Sometimes it felt like I was getting lost in a circle of relationships. I would advise doing a more complex/complicated example in class as a group so that when it comes to the exam or projects it seems simpler doing it by oneself.
      Have a great weekend!

    • I think the trickiest part of making an ERD diagram is figuring out when an attribute actually belongs with a relationship rather than an entity. It’s the type of scenario where if you were to pair said attribute with a certain entity, it would only made a little bit of sense, but you can immediately sense a flaw in the grouping. My advice for getting around this is consider all of your options, read the prompt carefully, and don’t overthink it because that’s likely going to hurt.

  • Velma Martinez‘s profile was updated 3 days, 20 hours ago

  • Please complete 50 quiz for chapter 4 before Saturday 5/27/2017 and post your results in this site.

  • Please complete your 50 quiz for chapter 3 before Mon 5/22/2017 and post your results in this site.

  • Here is the exercise.

    Before you start, save this Tableau file and the studentloans2013 Excel workbook to your computer. Remember, to save the file right-click on the link and choose “Save As…” (don’ […]

  • Here is the exercise.

    And here is the graphic file you’ll need: Philadelphia Area Obesity Rates.png.

    Right-click on the file and save it to your computer.

  • Chiquitta Evans‘s profile was updated 4 days, 17 hours ago

  • Chiquitta Evans changed their profile picture 4 days, 17 hours ago

  • Peipei Yu changed their profile picture 4 days, 18 hours ago

  • Peipei Yu changed their profile picture 4 days, 18 hours ago

  • Peipei Yu changed their profile picture 4 days, 18 hours ago

  • Peipei Yu changed their profile picture 4 days, 18 hours ago

  • Peipei Yu changed their profile picture 4 days, 18 hours ago

  • Load More
Skip to toolbar