Systems Analysis and Design

Slides:



Advertisements
Similar presentations
Auditing Concepts.
Advertisements

Discussion on SA-500 – AUDIT EVIDENCE
Stepan Potiyenko ISS Sr.SW Developer.
Documentation Testing
Unit 231 Software Engineering Introduction to SWE What is SDLC Phases of SDLC.
Unit 251 Implementation and Integration Implementation Unit Testing Integration Integration Approaches.
© Prentice Hall CHAPTER 9 Application Development by Information Systems Professionals.
Analysis Stage (Phase I) The goal: understanding the customer's requirements for a software system. n involves technical staff working with customers n.
Quality Assurance Through Software Engineering
SE 555 Software Requirements & Specification Requirements Validation.
Notion of a Project Notes from OOSE Slides - modified.
Software Engineering For Beginners. General Information Lecturer, Patricia O’Byrne. – Times: –See noticeboard outside.
Overview of the Multos construction process Chad R. Meiners.
9 1 Chapter 9 Database Design Database Systems: Design, Implementation, and Management, Seventh Edition, Rob and Coronel.
1 Software Testing and Quality Assurance Lecture 1 Software Verification & Validation.
Capability Maturity Model
Chapter 17 Acquiring and Implementing Accounting Information Systems
Introduction to Computer Technology
The Software Development Life Cycle: An Overview
Commercial Database Applications Testing. Test Plan Testing Strategy Testing Planning Testing Design (covered in other modules) Unit Testing (covered.
Managing Software Quality
CSI315 Web Applications and Technology Overview of Systems Development (342)
Chapter 2 The process Process, Methods, and Tools
Maintaining Information Systems Modern Systems Analysis and Design.
N By: Md Rezaul Huda Reza n
Managing the development and purchase of information systems (Part 1)
Topics Covered: Software requirement specification(SRS) Software requirement specification(SRS) Authors of SRS Authors of SRS Need of SRS Need of SRS.
المحاضرة الثالثة. Software Requirements Topics covered Functional and non-functional requirements User requirements System requirements Interface specification.
Software Inspection A basic tool for defect removal A basic tool for defect removal Urgent need for QA and removal can be supported by inspection Urgent.
Based on D. Galin, and R. Patton.  According to D. Galin  Software quality assurance is:  A systematic, planned set of actions necessary to provide.
Chapter 16 Quality Assurance Through Software Engineering Systems Analysis and Design Kendall & Kendall Sixth Edition.
ITEC 3220M Using and Designing Database Systems
Topic (1)Software Engineering (601321)1 Introduction Complex and large SW. SW crises Expensive HW. Custom SW. Batch execution.
Leaders in Asset Management Big Plans for your Property System? How to plan for a Property System Project Prepared by: Yudiann Carlo, CPPS
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
Understanding the IT environment of the entity. Session objectives Defining contours of financial accounting in an IT environment and its characteristics.
S4: Understanding the IT environment of the entity.
Software Project Management Lecture # 11. Outline Quality Management (chapter 26 - Pressman)  What is quality?  Meaning of Quality in Various Context.
 System Development Life Cycle System Development Life Cycle  SDLC Phases SDLC Phases Phase 1: Preliminary Investigation Phase 2: Feasibility Study.
System Implementation System Implementation - Mr. Ahmad Al-Ghoul System Analysis and Design.
Sylnovie Merchant, Ph.D. MIS 161 Spring 2005 MIS 161 Systems Development Life Cycle II Lecture 5: Testing User Documentation.
Software quality factors
The Software Development Process
Software Engineering Lecture # 1.
Assoc. Prof. Dr. Ahmet Turan ÖZCERİT.  System and Software  System Engineering  Software Engineering  Software Engineering Standards  Software Development.
Chapter 16 Quality Assurance Through Software Engineering Systems Analysis and Design Kendall & Kendall Sixth Edition.
第 11 組 MIS 報告. Phases of any information system ~ recognition of a business problem or opportunity ~ recognition of a business problem or opportunity.
1 Software Testing Strategies: Approaches, Issues, Testing Tools.
TESTING THE NEW SYSTEM Various Approaches to Testing.
Software Requirements Specification Document (SRS)
1 The Software Development Process ► Systems analysis ► Systems design ► Implementation ► Testing ► Documentation ► Evaluation ► Maintenance.
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
Pertemuan 14 Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
V-Shaped Software Development Life Cycle Model. Introduction: Variation of water fall model. Same sequence structure as water fall model. Strong emphasis.
Submitted By: Tanveer Khan M.Tech(CSE) IVth sem.  The ISO 9000 standards are a collection of formal International Standards, Technical Specifications,
 System Requirement Specification and System Planning.
Auditing Concepts.
SOFTWARE TESTING Date: 29-Dec-2016 By: Ram Karthick.
Topic for Presentaion-2
SYSTEM ANALYSIS AND DESIGN
McCall’s Quality Factors
Software Quality Assurance
FORMAL SYSTEM DEVELOPMENT METHODOLOGIES
Software engineering.
مقدمه اي بر مهندسي نيازمنديها
Thursday’s Lecture Chemistry Building Musspratt Lecture Theatre,
Capability Maturity Model
Capability Maturity Model
Software Reviews.
Presentation transcript:

Systems Analysis and Design Quality Assurance Systems Analysis and Design

Topics to be discussed Quality Assurance Guidelines for Quality Software Total Quality Management Levels or Activities of Quality Assurance Quality Assurance Goals in Systems Life Cycle Auditing

Quality Assurance The main Objective of a software development project is to ensure that the software should be of high quality.In order to maintain the quality of software ,the Project leader must plan for quality activities that are needed to be performed during different phases of SDLC. BACK

Guidelines for Quality Software Quality assurance approaches are Securing total quality assurance through designing systems and software with a top-down and modular approach Documenting software with appropriate tools Testing, maintaining, and auditing software The user of the information system is the single most important factor in establishing and evaluating its quality. It is far less costly to correct problems in their early stages than it is wait until a problem is expressed through user complains or crises. BACK

Total Quality Management Total quality management (TQM) is a conception of quality as an evolutionary process toward perfection instead of conceiving quality as controlling the number of defective products produced The full organizational support of management and early commitment to quality from the analyst and from the business are necessary BACK

Levels or Activities of Quality Assurance VERIFICATION VALIDATION TESTING CERTIFICATION

Verification: Verification is concerned with matching of quality of software at given phase with the specifications.The Developing Software is inspected and reviewed by a agroup of people during different phases of SDLC. Validation: Validation refers to the process of using the system in the actual live environment in order to find errors.If the results obtained from the system are proper,the System is valid else it is not.

System Testing: In system testing ,the common view is to eliminate program errors.System Testing represents the ultimate review of Specification,Design and Coding.This reviwe may be based on the feedbacks obtained from the users. Validation: Certification is the Confirmation of the Correctness of the Program.Hence Certification is for providing the authenticity of the system design that is Whether the System is According to what was aimed. BACK

Quality Assurance Goals in Systems Life Cycle The Software Life Cycle includes various phases of development and each phase has the goal of Quality Assurance. a) Quality Factor Specifications b)Software Requirement Specifications c) Software Design Specifications d) Software Testing and Implementation e) Maintenance and support

Quality Factor Specifications The goal of this phase is to define the quality factors.Software Quality Factors are: Correctness: Correctness is the extent to which a software satisfies its Specifications. Reliability: It is the extent to which a software can be expected to perform its intended function with required precision. Usability:It is the effort required to learn and operate the software properly.

Integrity: It is the extent to which access of software or data by unauthorized persons can be controlled. Efficiency:It means lass response time and memory requirement. Maintainability:It is the effort required to locate and fix an error in a program. Flexibility:It is the effort required to modify an operational program. Testability:It is the effort required to test to ensure that the system or a program performs its intended function. Portability: It is the effort required to transfer the software from one hardware /software system environment to another. Reusability: It is the extent to which part of software can be reused in other Software. Interoperability:It is the effort required to couple the system with other system Robustness:A Program is robust if it behaves reasonably even in circumstances that were not anticipated in the requirement specification. Data Abstraction:It is a process where we identify the important aspects of a phenomenon and ignore its details.

Software Requirement Specifications The Quality Assurance goal of this phase is to generate the requirements document that provides the technical specifications for the design and development of the software The SRS document should have the following main characteristics Complete Consistent Understandable by the user Modifiable as per the needs of the user Unambiguous This document enhances the system’s quality by formalizing communication between the system developer and the user and provides the proper information for accurate documentation.

Software Design Specifications In this Phase,Software design document defines the overall architecture of the software that provides the functions and features described in the software requirements document.This Document describes the logical subsystems and their respective physical modules.

Software Testing and Implementation The Quality assurance goal of the testing phase is to make the System Reliable and error free. The Quality assurance goal of the Implementation phase is to provide a logical order for the creation of the modules as well as for the creation of the System.

Maintenance and Suppot Maintenance is due to Errors or flaws in the system Enhancing the system Feedback procedures must be in place to communicate suggestions The Quality Assurance goal is to develop a procedure for correcting errors and enhancing Software. BACK

Auditing There are internal and external auditors Internal auditors study the controls used in the system to make sure that they are adequate Internal auditors check security controls External auditors are used when the system influences a company’s financial statements BACK

THANKS