Friday, June 21, 2019

Framework Essay Example | Topics and Well Written Essays - 1000 words

Framework - Essay ExampleThis paper reviews and compares the methodologies, recommending the best outline to develop the system. Analysis Fixits Nature of business Fixit TV repairs and video repairs deals with the repair of various electrical and electronic equipment while also selling area of the equipment. The employee base of the enterprise is made up of proprietor, who deals with customers and does most of the repair work, a part-time administrator who deals with the book-keeping and bill payments, and a team of sub-contractors who are brought in as necessary. At present the day-to-day running relies heavily on the proprietors memory or is written on a scrap of paper. As indicated, at the moment all procedures are manual, repairs are logged as they arrive, and the equipment and the customer details together the descriptions of the fault are always noned, giving each play a unique job ticket. The ticket has a unique number and contains the customer demographic details, the equ ipments details and the faults description. As a result of the complexities associated with the current procedure, the business through its proprietor seeks to implement a new system to run the business operations. However many question attire in how to develop the system. Questions How can the requirement be captured How can these requirements be conceptualized How can the system design be implemented, tested and debugged How will it be enter? How can the system be integrated, evolved, maintained and finally decommissioned? Comparison Agile development approach and object oriented design have various features which act upon them significant though distinctively separate. The main distinction is the approach in which the developer employs to realize an end product. The agile development approach involves a set of software product development approaches which are founded on incremental and iterative development (Satzinger, Jackson& Burd 2012). On the other(a) hand, object based d esign is a procedure of preparedness a scheme of relating objects for the reason of resolving a software issue. The primary thing to consider in the assertions is the reality that one encompasses envisionning while the other employs emergent and incremental development approaches. To begin with agile development approaches, it utilizes some principles and practices which can be glowered upon by various developer who favor planning and implementation of plan as opposed to bind coding. The major setback with this approach is that the design models do not need to model each single detail. The models do not require to be complete and perfect. This implies that an iterative methodology is utilized whereby no specifics are being operated with, instead they are operated on in tandem with the deliverable system. The other challenge relates to the documentation of the end system. With the case of agile development approach, the documentation of the system though essential is not accorded t he much desired dialect as it is the case with object oriented design(Yourdon 1994). Instead, the agile approach focuses on unit tests to form a greater part of the documentation of the design. Now as we develop the system using the agile approaches and procedures guided by spiral or waterfall model, without the presence of

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.