HRM 3440 Lecture Notes - Lecture 29: Systems Development Life Cycle, Object Model, Business Process
23 May 2018
School
Department
Course
Professor
HRM 3440 Lecture 29 Notes – Modules
Introduction
• Modules can be developed internally or obtained from an external source.
• After a company has the programming modules, programmers and systems analysts can
modify them and integrate them with other modules to form new programs.
• Object-oriented systems development (OOSD) combines the logic of the systems
development life cycle with the power of object-oriented modeling and programming.
• OOSD follows a defined systems development life cycle, much like the SDLC.
• The life cycle phases are usually completed with much iteration.
• Object-oriented systems development typically involves the following tasks:
• Identifying potential problems and opportunities within the organization that would be
appropriate for the OO approach.
• This process is similar to traditional systems investigation.
• Ideally, these problems or opportunities should lend themselves to the development of
programs that can be built by modifying existing programming modules.
• Defining what kind of system users require.
• This aalysis eas defiig all the ojets that are part of the user’s ork eiroet
(object-oriented analysis).
• The OO team must study the business and build a model of the objects that are part of
the business (such as a customer, an order, or a payment).
• Many of the CASE tools discussed can be used, starting with this step of OOSD.
• Designing the system.
• This process defines all the objects in the system and the ways they interact (object-
oriented design).
• Design involves developing logical and physical models of the new system by adding
details to the object model started in analysis.
• Programming or modifying modules.
find more resources at oneclass.com
find more resources at oneclass.com
