Strategy to Develop the System - Essay Example

? FRAMEWORK Insert Introduction Since the early 1980’s, researchers in the field of computer science have went under the impression which the software production process involves a set of systematic and well-defined discrete procedures which brought to mind Management Information Systems (MIS) creation progressions which have evolved over time to discrete forms of advanced computing (International Conference on New Trends in Software Methodologies, Tools and Techniques, Fujita & Pisanelli 2007). Nevertheless, the established methods to software development are often the subject of incessant review. In line of this review, we examine the complexities of agile development and object oriented design in the development of a new system for Fixit TV and Video repairs. This paper reviews and compares the methodologies, recommending the best strategy to develop the system. Analysis Fixit’s Nature of business Fixit TV repairs and video repairs deals with the repair of various electrical and electronic equipment while also selling part 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 proprietor’s 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 noted, giving each job a unique job ticket. The ticket has a unique number and contains the customer demographic details, the equipment’s details and the fault’s 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 arise 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 documented? How can the system be integrated, evolved, maintained and finally decommissioned? Comparison Agile development approach and object oriented design have various features which make 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 development approaches which are founded on incremental and iterative development (Satzinger, Jackson& Burd 2012). On the other hand, object based design is a procedure of planning 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 planning 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 the much desired emphasis 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 a document indicating the roadmap which could be signed off by the proprietor of the business, the feedback has to be a friend. Whether from the proprietor or the other employees, the feedback must be admitted. As a consequence of the iterative nature of agile methodologies; that is, spiral and waterfall models, we have to do a shallow of analysis the requirements, design, implementation, coding, testing and iteration of the development activities as necessitated (Sommerville 2005). In the end, it is easier to fit oneself leaping form task to task, attempting to strike a balance and making sure that every breadth meets the canons of its counterparts. Majority of the things which were mentioned sets forth an imprint of blind coding, a place in which many individuals go wrong in their decisions and the analysis of the design approach. Although planning and design for the development might not be detailed as in the case of Object oriented Design, it plays a colossal part in realizing how to forge ahead and finding a way to integrate the necessary requirements and features into the prevailing edifice(Deacon 2005). It is precarious to ruminate through how the system will be developed, how it will be actually designed, before its development. These design exertions can take the formula of a white board outline; or a meek test which an individual write before writing the business code; or anything fabricated from a modeling contrivance. This is very essential and requires to be done in petite intervals. This implies, that this cannot be done in the premature development stages, however an enlightened facet of the full development procedure. The two major approaches of agile software development; Water Fall model and Spiral model has various faults and is subject to numerous criticisms. One criticism involves its developer-centric nature instead of user centric (Beyer 2010). A single claim with agile development approach emphasizes on the procedure of gathering requirements and implementing it than the design of the product (Dennis, Wixom, & Roth 2009). Similarly agile methodologies may be inefficient in big enterprises and specific projects. Various people argue that agile approaches are suitable for non-sequential and developmental projects, and several enterprises consent to the claim that agile approaches are very extreme and embrace a contextually inapt hybrid approach which blends the features of extreme and systematic driven approaches. On the other hand, OOD which has been touted as the future bid step in system engineering presents a better approach to the implementation of the desired system for Fixit TV repairs and video repairs (Zu?llighoven 2005). The design methods employed seek to decrease development time; diminish the amount of resources needed to retain existing applications; escalate reuse of code, and offer a competitive advantage to businesses which utilize it (Malys?kin 2003). Object-oriented design involves a programming paradigm which uses objects as instances of classes, containing attributes and methods, to design systems. These classes are implemented using data abstraction, messaging, encapsulation, modularity, inheritance and polymorphism. OOD utilizes the classes as the foundation of the system to be developed, with each attribute, method and aspect of the system being represented in some form of object or class (Farrell 2013). The system development is well planned with a conceptual model being advanced as an outcome of the object oriented analysis. This analysis attempts to capture entities in the problem domain, outlining how different object interrelate, or behave upon the introduction of a given impetus. The object oriented approach generally gives a rich analysis, design, implementation, testing, documentation, integration, evolution, maintenance and decommissioning. Recommendation Having used the Object oriented design approach, to develop some system in Java, I find the need to have the preliminary documentation and outlining of the requirements, leading to a clear road map of the requirements and analysis, allowing the developers to conceptualize the actual requirements of the system. It is significant though, the approach might take some reasonable time, the approach present a robust method which allows for a colossal and systematic planning of the system development process. Thus I would recommend Object Oriented Design Approach. References Beyer, H. 2010, User-centered agile methods, Morgan & Claypool, San Rafael: Calif. Deacon, J. 2005, Object-oriented analysis and design: a pragmatic approach, Pearson Addison-Wesley, Harlow, England [u.a.]. Dennis, A., Wixom, B. H., & Roth, R. M. 2009, Systems analysis and design, Wiley, Hoboken, NJ. Farrell, J. 2013, An object-oriented approach to programming logic and design, Course Technology/Cengage Learning, Boston, MA. International Conference on New Trends in Software Methodologies, Tools and Techniques, Fujita, H., & Pisanelli, D. M. 2007, New trends in software methodologies, tools and techniques. IOS Press, Amsterdam, Malys?kin, V. E. 2003, Parallel computing technologies 7th international conference, PaCT 2003, Nizhni Novgorod Russia, September 15-19, 2003 : proceedings. Springer, Berlin [etc.]. Satzinger, J. W., Jackson, R. B., & Burd, S. D. 2012, Systems analysis and design in a changing world, Cengage Learning, Boston, MA, Course Technology. Sommerville, I. 2005, Software engineering, Addison-Wesley, New Delhi,. Yourdon, E. 1994, Object-oriented systems design: an integrated approach, Yourdon Press, Englewood Cliffs, N.J. Zu?llighoven, H. 2005, Object-oriented construction handbook. Morgan Kaufmann, Amsterdam. Read More