Lecture 7 -...

Info iconThis preview shows pages 1–2. Sign up to view the full content.

View Full Document Right Arrow Icon
Help Print This Page The Object-Oriented Modeling Approach Use-Case Modeling | Moving To Design | Agile Methodologies | eXtreme Programming | The Heart of the Systems Development Process This week, we are discussing techniques and graphical diagrams that systems analysts use for object-oriented analysis and design (OOAD) . The deliverables from project activities using object-oriented modeling include - data-flow diagrams entity-relationship diagrams repository descriptions Benefits associated with the object-oriented modeling approach include - Implementation of more advanced technology. 1. Better communication between all stakeholders. 2. The capability to reuse code and analysis and design artifacts. 3. Improvement of consistency throughout your system. 4. The object-oriented development life cycle refines the system through each phase, with the model becoming more detailed as it evolves. Object-oriented analysis and design methodologies have three phases: Analysis - The initial prototype of the operational system is created. 1. Design - During this phase, the prototype is progressively refined to match the production environment. 2. Implementation - During this phase, the design is coded using the selected programming language and/or database management system (DBMS). 3. The Unified Modeling Language is a standard to allow the systems analyst or system architect to visually model the system and to create the objects (artifacts) of the business process and software. The UML includes the following - Business use-cases 1. Sequence diagrams 2. State diagrams 3. Class diagrams 4. An analyst can represent several views of the system using the UML. Use-Case Modeling Systems analysts perform use-case modeling during the initial (analysis) phase to better understand the functional requirements of the proposed system. A use-case model depicts external entities and their interaction with the system (called actors ) and business processes (called use cases ) that make up the system. Figure A–1 depicts a use-case diagram for a school registration system.
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 2
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 6

Lecture 7 -...

This preview shows document pages 1 - 2. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online