Discussion: Object-Oriented Systems

NOW F OR AN ORIGINAL PAPER ASSIGNMENT:Discussion: Object-Oriented Systems

Object-Oriented Systems Development

The object-oriented systems development model blends SDLC logic with object-oriented modeling and programming power (Stair & Reynolds, 2016 ). Object-oriented modeling makes an effort to represent real-world objects by modeling the real-world entities or things (e.g., clinic, patient, account, nursing or healthcare professional) into abstract computer software objects. Once the system is object oriented, all of the interactions or exchanges take place between or among the objects. The objects are derived from classes, and each object is comprised of data and the actions that can be enacted on that data. Class hierarchy allows objects to inherit characteristics or attributes from parent classes, which fosters object reuse, resulting in less coding. The object-oriented programming languages, such as C++ and Java, promote software repurposing and reuse. Therefore, the class hierarchy must be clearly and appropriately designed to reap the benefits of this SDLC approach, which uses object-oriented programming to support the interactions of objects.

For example, in the case scenario, a system could be developed for the Wellness Alliance to manage the community health programming for the clinic system being set up for outreach. There could be a class of programs, and well-baby care could be an object in the class of programs; programs is a relationship between Wellness Alliance and well-baby care. The program class has attributes, such as clinic site, location address, or attendees or patients. The relationship itself may be considered an object having attributes, such as pediatric programs. The class hierarchy from which all of the system objects are created with resultant object interactions must be clearly defined.

The OOSD model is a highly iterative approach. The process begins by investigating where object-oriented solutions can address business problems or needs, determining user requirements, designing the system, programming or modifying object modeling (class hierarchy and objects), implementing, user testing, modifying, and reimplementing the system, and ends with the new system being reviewed regularly at established intervals and modifications being made as needed throughout its life.