Ask a question to Desklib · AI bot


Object-Oriented Approach to System Development: A Case Study of Derby Auctioneers Information System

Added on -2019-09-22

This article discusses the object-oriented approach to system development using Derby Auctioneers Information System as a case study. It covers functional and non-functional requirements, use case model, candidate class list, and class diagram.
| 9 pages
| 1298 words

Trusted by 2+ million users,
1000+ happy students everyday

IntroductionThere are two main approaches to systems development. These are; the structured approach and the object-oriented approach. The structured approach follows the structured analysis, design and programming techniques. The programming language employed here follows a sequence of statements where each statement executes at every decision point. It typically consists of a set of repeated statements. More sophisticated programs are divided into a hierarchy of programs in a top-down approach. Programs at the top module calls the lower one during execution (Valacich, 2015). These modules should be highly cohesive and loosely coupled. The structured analysis part of the approach makes it easier for the system developer toidentify the system process requirements and the data requirements, and the interrelates of the processes in the system towards the realization of a common goal. On the other hand, the object-oriented approach models the information system as a collection of interrelated objects working together to achieve a common goal. An object is an entity that is able to respond to the messages.The object-oriented analysis identifies the objects that carry out certain tasks coupled with the user events that are necessary for their accomplishment (Kendall & Kendall, 2014). The object oriented design shows graphically how these objects interact to achieve their functions. The object-oriented programming finally writes down the actual code that is necessary to accomplish these functions in an information system. This project utilizes object-oriented design, whereby a list of functional and non-functional requirements are produced alongside ause case model of thesystem with separate descriptions of the use cases, a list of candidateclasses and an initial class diagram.
Functional RequirementsFunctional requirements defines a set of inputs and outputs that specifies the overall behaviour of the system. These may include; business rules, legal requirements, external interfaces, certification and reporting requirements, authorization and authentication levels and the business administrative rules (Valacich, 2015). From the Derby Auctioneers', these requirements include; customer log in process, online item bidding, bid withdrawal, determiningwinning bid, payment for item, uploading item photos, updating items and shipping the items to the customer Non-Functional RequirementsThe non-functional requirements define the criterion employed in specifying the system behaviour as opposed to the specification of the these behaviours. These requirements include; system performance, reliability, interoperability, scalability, availability, capacity, recoverability,usability, maintainability, serviceability and manageability. These requirements also focus on the environmental aspects of the system, regulatory, security and data integrity. From the Derby Auctioneers' case study, these requirements include; 'the system should optimally utilize its computing resources', 'the reliability, interoperability, scalability, availability, capacity, recoverability, usability, maintainability, serviceability and manageability of the system must bemet and maintained' and 'the data the integrity of the data contained within the system must be secured from unauthorized access and modification.
Use case modelSystemSystem User Admin (Ken)(John)Derby Auctioneers Information SystemLog into the systemLog into the systemBrowse through Item photosBid on ItemsPay for won itemsPost item photosDetermine winning bidShip item to the customer

Found this document preview useful?

You are reading a preview
Upload your documents to download
Become a Desklib member to get accesss

Students who viewed this