With changing environment, the role of different professions is also changing. The software engineers of tomorrow will be facilitators, their role will be to embed the centuries old research available into software tools and packages, and enable the users of respective domain, mostly public, to benefit from this resource by using these tools. Responding to the need of time, University of Arid Agriculture expects UIIT to develop a comprehensive Agriculture Information System (AIS), which will be based on the research carried out at the university or available elsewhere. UAAR faculty members will act as clients as well as resource persons for the development of various components of AIS. AIS will be operating on stand-alone machines initially, later it will be placed on the UIIT servers and made available to the university students through local/wide area networks for testing and their feed-back. After acceptance test, it will be made available to the end-users for remote access through Internet. AIS will serve the needs of a farmer. It will provide Information about crops, soil, climate, seeds, pesticides and have in-built models for different crops to predict their growth and yields. Another important component of AIS is the subsystem called 'Land Calculator' to measure the area of the plot provided its sides are given. Land Calculator (LC) will be a very useful tool to resolve the land disputes, and will hopefully be one of the favorites of the farmers. It will have graphical multi-lingual user interface, like AIS. It'll ask the user for number of sides and will enable the user to draw the sketch of the plot and allow him/her to label the sides (by the labels of 8 characters long strings). After that it would ask for the length of each side. Then on click of 'execute' button it would shade the plot and calculate the area of the plot. User would have the provision to choose any set of units, the classical system of karam, marla, kanal, beegha and acres; metric system of meters and hectares; or the British system have foot and yard for length, and square yards for area. In the first version LC would handle on simple geometry plots, i. e. those having three or four sides only. After entry if required it will adjust/scale the drawn figure according to the dimensions of the sides and this adjusted figure will have different colors. If desired user can simple click on the 'change units' button and can choose the other system of units, and LC will reproduce the figure with changed units and in different color. Similarly, change of language can facilitate the user further, and enhance the versatility and audience of the AIS. Note: All individual Students are advice to prepared the Activity table including values of Activity Duration, Earliest Start date, Latest Start date, Earliest Finish date, Latest Finish date based on Assumptions, keeping in view the above mentioned system description. You need to answer following questions. Produce the following for above mention System Description, 1. Construct Critical Path Method (CPM) Network 2. Arrow Diagramming Method (ADM) 3. Precedence Diagramming Method (PDM)

What computer network component allows data transfers from one computer to another through a telephone line?

What result from the passage of this amendment

Calculating the "total price" of an item is tedious, so implement a get_item_cost method that just returns the quantity times the price for an item. by the way, the technical term for this kind of instance method is an accessor method, but you'll hear developers calling them getters because they always start with "get" and they get some value from instance attributes. in order to make the items sortable by their total total price, we need to customize our class. search the lectures slides for "magic" to see how to do this. see section 9.8 for an additional reference. the receipt class: this will be the class that defines our receipt type. obviously, a receipt will consist of the items on the receipt. this is called the composition design pattern. and it is very powerful. instance attributes: customer_name : it is very important to always know everything you can about your customers for "analytics", so you will keep track of a string customer name in objects of type receipt. date : the legal team has required that you keep track of the dates that purchases happen for "legal reasons", so you will also keep track of the string date in objects of type receipt. cart_items : this will be a list of the items in the cart and hence end up on the receipt. methods: 1. create a default constructor that can take a customer name as an argument, but if it gets no customer name, it will just put "real human" for the customer_name attribute. it should also accept a date argument, but will just use the value "today" for the date instance attribute if no date is given. the parameters should be named the same as the instance attributes to keep things simple. 2. add_item : self-descriptive. takes a parameter which we hope beyond hope is of type itemtopurchase and adds it to the cart_items. returns none. 3. print_receipt : takes a single parameter isevil, with default value true. returns a total cost of all the items on the receipt (remember to factor in the quantity). prints the receipt based on the following specification: for example, if isevil is true, and customer_name and date are the default values: welcome to evilmart, real human today have an evil day! otherwise, it should print: welcome to goodgo, real human today have an good day! then the receipt should be printed in sorted order like we discussed earlier, but whether or not it starts with the highest cost (think reverse), depends on the value of isevil. if it is evil, then the lowest cost items should print first, but if it is good, then it will print the highest cost items first. (cost meaning price*quantity). remember to return the total cost regardless! your main() function: the main flow of control of your program should go in a main() function or the program will fail all the unit tests. get the name of the customer with the prompt: enter customer name: get the date with the prompt: enter today's date then, ask the question: are you evil? your program should consider the following as true: yeah yup let's face it: yes hint: what do these strings all have in common? your program should consider all the following as false: no nah perhaps but i'm leaning no (just be glad you don't have to handle "yeah no.") okay enough horsing around. (get it? aggies? ! horsing! ) next, in the main() function, you will have to create a receipt object and start adding things into it using an input-while loop. the loop will prompt the user for the item name exactly as in the previous zylab (9.11). but unlike the previous zylab, the loop will terminate only if an empty string is entered for the item name. then, the price and the quantity will be prompted for exactly as in the previous zylab. create the itemtopurchase objects in the same manner as the previous zylab, but don't forget to add them to the receipt using your add_item instance method. then, the items on the receipt should be printed with the same formatting as in the previous zylab, of course with either "good" or "evil" ordering. however, on the last line, the total should be printed as follows: where 10 is replaced by the actual total. sample run here is what a sample run of the final program should look like: enter customer name: nate enter today's date: 12/20/2019 are you evil? bwahahahaha yes enter the item name: bottled student tears enter the item price: 2 enter the item quantity: 299 enter the item name: salt enter the item price: 2 enter the item quantity: 1 enter the item name: welcome to evilmart, nate 12/20/2019 have an evil day! salt 1 @ $2 = $2 bottled student tears 299 @ $2 = $598 total: $600