Software Development Coursework Example | Topics and Well Written Essays - 1000 words

Software Development - Coursework ExampleThe use case diagram shall indicate the activities and duties carried out by different individuals involved in the operations of the company. All the actors presented within the use case diagram shall have functions associated with them, and linking them to the rest of the actors within the use case diagram. The build diagram on the other happen shows the different take aims of all the actors involved within the framework of the use case diagram. The use case diagram presents a list of all actors involved in the operations of the company, while the split diagram frameifies the different users involved. The use case diagram presents the various functions per motleyed by different actors within the diagram. Following the identification of these functions, the class diagram shall present a detailed explanation of the categories present within the class diagram. The members present within the class diagram shall have class level attached to t heir identity to classify the categories dividing the members. The use case diagram presents the recipients of the donations as the last actors within the context of the use case. The interaction of these actors shall only occur in the midst of the members presenting them with the donation. Within the class diagram, however, the individuals presenting the donations and the activity coordinators shall form part of the donor-recipient association. ... Since majority of the functions seek to focus on the donors, the central actors in the use case diagram form the association of the donor and the recipient. The associations of the donor and recipient shall be presented as binary association, facilitated through other people not benefiting from the association. Donors shall form part of the public class with the name of donors forming the next class of private level. Classified information contained in the class diagram shall include but not limited to the donations offered by the donor s onto the organisations. This class would be classified as the protected class by the system enabling the storage of information contained in this class for future reference. Retrieving of particulars regarding the donations offered by to each one donor remains the function of few individuals, with the necessary authority to perform these functions. The donors should be able to check the information regarding their previous donations to the organisation. This information remains of the essence(p) for the donors who need to trace their donations before offering others. Following the donations, the donor could be able to retrieve information regarding the loyalty point earned from the donations made. Accessing this information could overly present the opportunity for donor to present their pledges. The use case diagram should present description of the actors who should be making follow-ups on the experimental condition of pledges. This would ensure that the status of the pledges made by donors remains updated, as the information could assist the coordinators in allocating donations to needy recipients. Such information would also play a significant subroutine in ensuring the donations arrive at the required destinations on timely basis. A major disadvantage of the