We think you have liked this presentation. If you wish to download it, please recommend it to your friends in any social system. Share buttons are a little bit lower. Thank you!
Presentation is loading. Please wait.
Published byEmilia Sturgess
Modified over 4 years ago
14-1 © Prentice Hall, 2004 Chapter 14: OOSAD Implementation and Operation (Adapted) Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich, Jeffrey A. Hoffer
Chapter 14 14-2 © Prentice Hall, 2004 Outline System Implementation Concept Coding, Testing, Converting, Training Steps Installation strategies
Chapter 14 14-3 © Prentice Hall, 2004 System Implementation Concept Activities that transform design into a working system and set the system into the production stage. In OO methodology, these activities fall mostly into the construction and transition stages. Note: As opposed to common sense, coding is part of implementation - not design.
Chapter 14 14-4 © Prentice Hall, 2004
Chapter 14 14-5 © Prentice Hall, 2004 Coding Translation of physical design specifications into working computer code Coding involves use of programming languages such as Java or Visual Basic eXtreme programming – an intensive coding and testing approach involving two-person teams and customer involvement
Chapter 14 14-6 © Prentice Hall, 2004 Reuse The use of previously written software resources, especially objects and components, in new applications Results in great savings of system development time Object-oriented systems are very conducive to reuse.
Chapter 14 14-7 © Prentice Hall, 2004 Approaches to Reuse Ad hoc – individual, unplanned use Facilitated – use informally managed and disseminated by expert guru evangelists Managed – organizationally enforced reuse policies and practices Designed – reusable components developed and maintained in-house Cost and commitment low high
Chapter 14 14-8 © Prentice Hall, 2004 Software Testing Manual and automated procedures for validating correctness of program code, including syntactical and execution issues Testing Syntax – grammatical rules applied to programming languages Testing Execution – logic and performance of the software during operation Note: Bug-free software remains a dream!
Chapter 14 14-9 © Prentice Hall, 2004 Tests can be manual or automated, and may or may not involve code execution.
Chapter 14 14-10 © Prentice Hall, 2004 Tests Without Program Execution Inspections (manual) – Participants examine program code for predictable, language-specific errors Syntax checking (automated) – Compiler or interpreter tests source code for grammatical errors while translating to executable format
Chapter 14 14-11 © Prentice Hall, 2004 Manual Tests With Program Execution Desk checking – trace through the logic of the code, identifying possible logical errors Walkthroughs – Like desk-checking, but in a group-oriented, more structured process
Chapter 14 14-12 © Prentice Hall, 2004 Automated Tests With Program Execution Unit tests – a module tested in isolation for internal consistency Integration tests – testing all modules and components of the application together for interaction compatibilities System tests – testing all programs and applications together to ensure performance and reliability Acceptance tests – user-satisfaction tests
Chapter 14 14-13 © Prentice Hall, 2004 A test case is a specific scenario of transactions, queries, or navigation paths that represent a typical, abnormal, or critical use of the system. Allows repeated testing with each application change
Chapter 14 14-14 © Prentice Hall, 2004 Installation The process of turning over from the old information system to the new one. Types: – Direct – Parallel – Single location – Phased
Chapter 14 14-15 © Prentice Hall, 2004 Direct – Cold turkey, low cost, greater impact of errors.
Chapter 14 14-16 © Prentice Hall, 2004 Parallel – old and new coexist, minimize error impact, high cost in system resources.
Chapter 14 14-17 © Prentice Hall, 2004 Single Location – Pilot approach, allows learning and minimizes error impact, lower resource demand than parallel, difficult to coordinate and maintain.
Chapter 14 14-18 © Prentice Hall, 2004 Phased – Staged and incremental, supports phased system development, minimize error impact, difficult to coordinate old components and new components.
Chapter 14 14-19 © Prentice Hall, 2004 Types of Documentation System – detailed information about a system’s design specifications, its inner workings, and its functionality. User – written or other visual information about an application system, how it works, and how to use it. Internal – comments in source code, generated during the coding process or automatically. External – outcomes of all structured diagrams, including use cases, design classes, activity and sequence diagrams, etc.
Chapter 14 14-20 © Prentice Hall, 2004 User Training Providing on-going educational and problem- solving assistance to information systems users. Training and support material and jobs must be designed along with the associated information systems. User documentation is often in the form of online help, sometimes with Web connections for further information.
Chapter 14 14-21 © Prentice Hall, 2004 Training methods can be interpersonal, manual, or automated.
Chapter 14 14-22 © Prentice Hall, 2004 Help Desks and Information Centers Help desk – a single point of contact for all user inquiries and problems about a particular information system or for all users in a particular department Information center – an organizational unit whose mission is to support users in exploiting information technology
Chapter 14 14-23 © Prentice Hall, 2004
Requirements Engineering Processes – 2
© 2005 by Prentice Hall Appendix 3 Object-Oriented Analysis and Design Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George.
© 2005 by Prentice Hall Chapter 13 Finalizing Design Specifications Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George.
1 Copyright © 2010, Elsevier Inc. All rights Reserved Fig 2.1 Chapter 2.
By D. Fisher Geometric Transformations. Reflection, Rotation, or Translation 1.
ASYCUDA Overview … a summary of the objectives of ASYCUDA implementation projects and features of the software for the Customs computer system.
Business Transaction Management Software for Application Coordination 1 Business Processes and Coordination.
Jeopardy Q 1 Q 6 Q 11 Q 16 Q 21 Q 2 Q 7 Q 12 Q 17 Q 22 Q 3 Q 8 Q 13
DIVIDING INTEGERS 1. IF THE SIGNS ARE THE SAME THE ANSWER IS POSITIVE 2. IF THE SIGNS ARE DIFFERENT THE ANSWER IS NEGATIVE.
Making the System Operational
Week 2 The Object-Oriented Approach to Requirements
Software change management
Testing Workflow Purpose
Chapter 9 Structuring System Requirements: Logic Modeling
Chapter 8 Logic Requirements
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software processes 2.
© 2019 SlidePlayer.com Inc. All rights reserved.