Phase 5 of the SDLC focuses on systems operation and support after a new system is implemented. This involves providing user training and support through an information center, as well as performing three types of maintenance: corrective maintenance to fix errors, adaptive maintenance to enhance the system, and perfective maintenance to improve efficiency. The overall costs include both fixed operational costs and varying maintenance costs over the system's lifetime.
The document outlines NetSol's experience with implementing the Capability Maturity Model (CMM). It discusses the road map to CMM implementation, including understanding the need and value, initiating software process improvement, planning activities, building infrastructure, building process assets, and preparing for appraisals. It also covers common mistakes, critical success factors, and NetSol's progress achieving CMM levels 2 and 3 and plans for achieving level 4.
This document discusses system development processes and techniques. Chapter 4 explains system development processes including requirements definition, system design, development, testing, acceptance, and operation/maintenance. It also discusses software development management techniques. The key steps in system development are:
1. Requirements definition to determine system functions and requirements
2. System design to design the system based on requirements
3. Development to build the system based on the design
4. Testing to check that the system operates as designed
5. Acceptance to verify the system meets requirements
Defining and Evaluating the Usability of CMS - Saurabh Kudesia STC India UX SIG
The document discusses defining and evaluating usability criteria for content management systems (CMS). It proposes that usability is a multidimensional concept that should be measured using multiple sub-constructs and factors. It presents different measurement models and evaluates the fit of these models based on covariance matrices and fit indices. The document concludes that usability scales are multidimensional and context dependent, and both content and architectural design must be considered when benchmarking CMS usability.
Quantify the Functional Requirements in Software System EngineeringKarthika Parthasarathy
This document discusses an approach to analyzing and quantifying functional requirements in software system engineering. It begins by introducing system engineering as a process that transforms operational needs into system configurations. Software system engineering applies these principles to the development of large, complex software systems. The paper focuses on categorizing and prioritizing functional requirements during the requirements analysis phase of software development. Analyzing, designing, and organizing system elements according to engineering principles helps produce documentation to guide software development and manage technical functions. This process aims to reduce complexity and improve customer satisfaction.
FlexNet Manager Suite Leverages Microsoft System Center to Deliver Next Gener...Flexera
FlexNet Manager Suite leverages Microsoft System Center to deliver next-generation software asset management. It provides SAM and license optimization capabilities that complement Microsoft solutions. It uses SCCM for discovery and inventory then reconciles data from multiple sources to provide an optimized license position according to applicable product use rights. It enables application lifecycles in the organization and manages both the operational and contractual lifecycles of software.
The document discusses the key activities in system implementation which include coding, testing, installation, documentation, training, and support. It provides details on each of these implementation steps such as coding the physical design specifications into working software code, performing various types of testing, replacing the current system with the new system during installation, and documenting the system and training users on how to use it for support after installation. The goal of implementation is to convert specifications into working, reliable software and prepare documentation and training to support user adoption of the new system.
The document discusses an IT management solution called "Manage IT" that helps businesses select and implement effective IT solutions. It includes 11 process modules that cover key IT processes to standardize operations. It also provides compliance services that assess IT systems, create test scripts, and develop remediation plans. A compliance portal gives leadership visibility into compliance activities and security issues. The solution aims to reduce costs, improve controls, ensure regulatory compliance, and drive IT maturity through standardized and repeatable processes.
The document outlines NetSol's experience with implementing the Capability Maturity Model (CMM). It discusses the road map to CMM implementation, including understanding the need and value, initiating software process improvement, planning activities, building infrastructure, building process assets, and preparing for appraisals. It also covers common mistakes, critical success factors, and NetSol's progress achieving CMM levels 2 and 3 and plans for achieving level 4.
This document discusses system development processes and techniques. Chapter 4 explains system development processes including requirements definition, system design, development, testing, acceptance, and operation/maintenance. It also discusses software development management techniques. The key steps in system development are:
1. Requirements definition to determine system functions and requirements
2. System design to design the system based on requirements
3. Development to build the system based on the design
4. Testing to check that the system operates as designed
5. Acceptance to verify the system meets requirements
Defining and Evaluating the Usability of CMS - Saurabh Kudesia STC India UX SIG
The document discusses defining and evaluating usability criteria for content management systems (CMS). It proposes that usability is a multidimensional concept that should be measured using multiple sub-constructs and factors. It presents different measurement models and evaluates the fit of these models based on covariance matrices and fit indices. The document concludes that usability scales are multidimensional and context dependent, and both content and architectural design must be considered when benchmarking CMS usability.
Quantify the Functional Requirements in Software System EngineeringKarthika Parthasarathy
This document discusses an approach to analyzing and quantifying functional requirements in software system engineering. It begins by introducing system engineering as a process that transforms operational needs into system configurations. Software system engineering applies these principles to the development of large, complex software systems. The paper focuses on categorizing and prioritizing functional requirements during the requirements analysis phase of software development. Analyzing, designing, and organizing system elements according to engineering principles helps produce documentation to guide software development and manage technical functions. This process aims to reduce complexity and improve customer satisfaction.
FlexNet Manager Suite Leverages Microsoft System Center to Deliver Next Gener...Flexera
FlexNet Manager Suite leverages Microsoft System Center to deliver next-generation software asset management. It provides SAM and license optimization capabilities that complement Microsoft solutions. It uses SCCM for discovery and inventory then reconciles data from multiple sources to provide an optimized license position according to applicable product use rights. It enables application lifecycles in the organization and manages both the operational and contractual lifecycles of software.
The document discusses the key activities in system implementation which include coding, testing, installation, documentation, training, and support. It provides details on each of these implementation steps such as coding the physical design specifications into working software code, performing various types of testing, replacing the current system with the new system during installation, and documenting the system and training users on how to use it for support after installation. The goal of implementation is to convert specifications into working, reliable software and prepare documentation and training to support user adoption of the new system.
The document discusses an IT management solution called "Manage IT" that helps businesses select and implement effective IT solutions. It includes 11 process modules that cover key IT processes to standardize operations. It also provides compliance services that assess IT systems, create test scripts, and develop remediation plans. A compliance portal gives leadership visibility into compliance activities and security issues. The solution aims to reduce costs, improve controls, ensure regulatory compliance, and drive IT maturity through standardized and repeatable processes.
This document discusses software configuration management and describes its key activities and importance. It covers configuration management planning, change management, version management, and the use of tools to support the configuration management process. Effective configuration management is important for managing evolving software systems and controlling the costs of system changes. It aims to manage all products of the software development process, including specifications, designs, code, and documentation.
The document discusses reliability engineering and fault tolerance. It covers topics like availability, reliability requirements, fault-tolerant architectures, and reliability measurement. It defines key terms like faults, errors, and failures. It also describes techniques for achieving reliability like fault avoidance, fault detection, and fault tolerance. Specific architectures discussed include redundant systems and protection systems that can take emergency action if failures occur.
The document contains slides from supplementary materials for a software engineering textbook. The slides cover topics like system engineering, business process engineering, information strategy planning, business area analysis, requirements engineering, and the relationships between different levels of analysis and design in engineering systems and software. The materials are copyrighted and intended solely for use alongside the textbook in an educational setting.
The documents discuss various topics related to system design and documentation. Three of the documents discuss processes for documentation including that documentation must be done in parallel with development, guide the reader to relevant sections, help locate modules for modification, and remain up to date. Another document discusses the importance of system documentation for project management, development, and operation. A final document discusses the terminology of flexible system design, which aims to maintain performance through changes in configuration.
Enhancing the flexibility to the design of selangkah systemizzatuitm
The document discusses enhancing the flexibility of the Selangkah System used by UiTM to assist students in identifying suitable study programs. It aims to allow easier changes to the system to accommodate annual updates to admission rules and regulations. The current system's hardcoded rules make changes difficult. The research will review the system, verify requirements, and design a more flexible system through documentation and a design that allows dynamic rule changes. This will benefit both students and administrators.
The document discusses the system development life cycle (SDLC), which includes various phases for developing and maintaining systems. The key phases are: system investigation, feasibility study, system analysis, system design, coding, testing, implementation, and maintenance. The feasibility study phase evaluates the technical, operational, economic, motivational, and schedule feasibility of a proposed system. The system analysis phase involves studying user requirements and the current system. System design then specifies how the new system will meet requirements through elements like data design, user interface design, and process design. This produces specifications for the system.
Product lifecycle management (PLM) is a systematic approach to managing the series of changes a product goes through, from its design and development to its ultimate retirement or disposal. PLM software can be used to automate the management of product-related data and integrate the data with other business processes.
This document discusses software reuse and application frameworks. It covers the benefits of software reuse like accelerated development and increased dependability. Application frameworks provide a reusable architecture for related applications and are implemented by adding components and instantiating abstract classes. Web application frameworks in particular use the model-view-controller pattern to support dynamic websites as a front-end for web applications.
This document discusses Lean Six Sigma and how it can be used for business process improvement. It notes that while Lean Six Sigma has been successfully used in manufacturing and other industries, many companies struggle to achieve expected benefits from their Lean Six Sigma programs. This is often due to poor implementation planning and project selection. The document introduces the SystemCPi roadmap as a proven approach to overcome these implementation issues. SystemCPi provides an integrated toolbox to plan, implement, and sustain process improvement initiatives. It helps organizations choose the right projects and tools to achieve operational excellence and competitive advantage through Lean Six Sigma.
The BMC BladeLogic Operations Manager Suite is a platform that automates management, control, and enforcement of configuration changes in the data center. It allows customers to reduce costs by automating manual tasks and improves security through policy-based configuration management. The suite provides configuration management, compliance measurement, and server provisioning across various operating systems and platforms.
The document discusses various topics related to systems development including:
1) The traditional systems development life cycle (SDLC) which includes 7 phases from planning to maintenance.
2) Component-based development methodologies like rapid application development and extreme programming which focus on reusable components.
3) Selfsourcing where end users develop systems with little IT help using prototyping.
4) Prototyping which involves building models to demonstrate system features to users.
5) Outsourcing systems development work to third parties.
Design Issue(Reuse) in Software Engineering SE14koolkampus
The document discusses various techniques for software reuse, including component-based development, application families, and design patterns. It describes the benefits of reuse such as increased reliability and reduced costs. Different types of reusable components are explained, from whole application systems to individual functions. Requirements for effective reuse include components being reliable, documented, and easily found and adapted.
The document discusses software processes and activities. It describes common process models like waterfall, incremental development, and configuration management. The key activities involved in most processes are specification, development, validation, and evolution. Specification defines system requirements while development includes design, implementation, and debugging. Validation ensures the system meets requirements through testing. Processes also evolve to adapt to changing needs.
The document discusses architecture refactoring and defines it as changing a software system or process in a way that does not alter external behavior but improves internal structure. It notes that design erosion over time negatively impacts systems and refactoring can help address this. The document outlines some motivations for refactoring like improving structural and non-functional qualities to achieve a more economical, visible, and symmetric design. It also distinguishes refactoring from reengineering and rewriting.
The document provides information on PureShare SingleView IT, an operational metrics solution that consolidates and monitors IT service management metrics. It allows users to automate data collection, visualize current performance status, and monitor key metrics with an early warning system. The solution presents operational metrics in one centralized view, enables proactive management through trend analysis, and automates reports and key performance indicators.
Ian Sommerville, Software Engineering, 9th Edition Ch1Mohammed Romi
The document provides an introduction to software engineering concepts. It discusses what software engineering is, the importance of ethics in software development, and introduces three case studies that will be used as examples throughout the book. Specifically:
[1] It defines software engineering as an engineering discipline concerned with all aspects of software production. Professional and ethical practices are important.
[2] It discusses software engineering ethics and introduces the ACM/IEEE code of ethics for software engineers.
[3] It provides an overview of three case studies that will be referenced in later chapters: an insulin pump system, a patient management system, and a weather station system.
The chapter discusses software evolution, including that software change is inevitable due to new requirements, business changes, and errors. It describes how organizations must manage change to existing software systems, which represent huge investments. The majority of large software budgets are spent evolving, rather than developing new, systems. The chapter outlines the software evolution process and different approaches to evolving systems, including addressing urgent changes. It also discusses challenges with legacy systems and their management.
Cis 2303 lo1 part 1_weeks_1_2 - student verAhmad Ammari
This document outlines the learning objectives and content for a course on systems analysis and design. The course will describe the evolution of software development processes and methodologies, with a focus on structured analysis. It will cover the components of information systems, systems development life cycle models, and the roles and tasks of systems analysts in gathering requirements and designing specifications. The structured analysis approach and systems development life cycle model involve planning, analysis, design, implementation, and support phases to develop high-quality information systems.
Chapter 1- INTRODUCTION TO SYSTEM ANALYSIS AND DESIGN by DEEPA (1).pptxanumayived
This document provides an introduction to system analysis and design. It discusses key concepts like information, information systems, and information system components. It also describes different system development methods including structured analysis, object-oriented analysis, and agile/adaptive methods. Additionally, it explains the system development life cycle and provides examples of each phase for a clinic management system project.
Ais Romney 2006 Slides 18 Introduction To Systems Developmentsharing notes123
The document summarizes the key phases and activities involved in the systems development life cycle. It discusses:
1) The five main phases: systems analysis, conceptual design, physical design, implementation and conversion, and operation and maintenance.
2) The various individuals and groups involved in systems development, including top management, accountants, an information systems steering committee, systems analysts, and computer programmers.
3) How planning, managing change, and ongoing feasibility assessment occur throughout the life cycle.
The document discusses systems development and analysis. It covers the following key points in 3 sentences:
The systems development life cycle involves 5 phases: analysis, conceptual design, physical design, implementation, and operations/maintenance. Planning is important to coordinate projects and ensure consistency, efficiency, and lower costs. A feasibility study analyzes technical, operational, economic, legal, and scheduling feasibility to determine if a project should proceed.
This document discusses software configuration management and describes its key activities and importance. It covers configuration management planning, change management, version management, and the use of tools to support the configuration management process. Effective configuration management is important for managing evolving software systems and controlling the costs of system changes. It aims to manage all products of the software development process, including specifications, designs, code, and documentation.
The document discusses reliability engineering and fault tolerance. It covers topics like availability, reliability requirements, fault-tolerant architectures, and reliability measurement. It defines key terms like faults, errors, and failures. It also describes techniques for achieving reliability like fault avoidance, fault detection, and fault tolerance. Specific architectures discussed include redundant systems and protection systems that can take emergency action if failures occur.
The document contains slides from supplementary materials for a software engineering textbook. The slides cover topics like system engineering, business process engineering, information strategy planning, business area analysis, requirements engineering, and the relationships between different levels of analysis and design in engineering systems and software. The materials are copyrighted and intended solely for use alongside the textbook in an educational setting.
The documents discuss various topics related to system design and documentation. Three of the documents discuss processes for documentation including that documentation must be done in parallel with development, guide the reader to relevant sections, help locate modules for modification, and remain up to date. Another document discusses the importance of system documentation for project management, development, and operation. A final document discusses the terminology of flexible system design, which aims to maintain performance through changes in configuration.
Enhancing the flexibility to the design of selangkah systemizzatuitm
The document discusses enhancing the flexibility of the Selangkah System used by UiTM to assist students in identifying suitable study programs. It aims to allow easier changes to the system to accommodate annual updates to admission rules and regulations. The current system's hardcoded rules make changes difficult. The research will review the system, verify requirements, and design a more flexible system through documentation and a design that allows dynamic rule changes. This will benefit both students and administrators.
The document discusses the system development life cycle (SDLC), which includes various phases for developing and maintaining systems. The key phases are: system investigation, feasibility study, system analysis, system design, coding, testing, implementation, and maintenance. The feasibility study phase evaluates the technical, operational, economic, motivational, and schedule feasibility of a proposed system. The system analysis phase involves studying user requirements and the current system. System design then specifies how the new system will meet requirements through elements like data design, user interface design, and process design. This produces specifications for the system.
Product lifecycle management (PLM) is a systematic approach to managing the series of changes a product goes through, from its design and development to its ultimate retirement or disposal. PLM software can be used to automate the management of product-related data and integrate the data with other business processes.
This document discusses software reuse and application frameworks. It covers the benefits of software reuse like accelerated development and increased dependability. Application frameworks provide a reusable architecture for related applications and are implemented by adding components and instantiating abstract classes. Web application frameworks in particular use the model-view-controller pattern to support dynamic websites as a front-end for web applications.
This document discusses Lean Six Sigma and how it can be used for business process improvement. It notes that while Lean Six Sigma has been successfully used in manufacturing and other industries, many companies struggle to achieve expected benefits from their Lean Six Sigma programs. This is often due to poor implementation planning and project selection. The document introduces the SystemCPi roadmap as a proven approach to overcome these implementation issues. SystemCPi provides an integrated toolbox to plan, implement, and sustain process improvement initiatives. It helps organizations choose the right projects and tools to achieve operational excellence and competitive advantage through Lean Six Sigma.
The BMC BladeLogic Operations Manager Suite is a platform that automates management, control, and enforcement of configuration changes in the data center. It allows customers to reduce costs by automating manual tasks and improves security through policy-based configuration management. The suite provides configuration management, compliance measurement, and server provisioning across various operating systems and platforms.
The document discusses various topics related to systems development including:
1) The traditional systems development life cycle (SDLC) which includes 7 phases from planning to maintenance.
2) Component-based development methodologies like rapid application development and extreme programming which focus on reusable components.
3) Selfsourcing where end users develop systems with little IT help using prototyping.
4) Prototyping which involves building models to demonstrate system features to users.
5) Outsourcing systems development work to third parties.
Design Issue(Reuse) in Software Engineering SE14koolkampus
The document discusses various techniques for software reuse, including component-based development, application families, and design patterns. It describes the benefits of reuse such as increased reliability and reduced costs. Different types of reusable components are explained, from whole application systems to individual functions. Requirements for effective reuse include components being reliable, documented, and easily found and adapted.
The document discusses software processes and activities. It describes common process models like waterfall, incremental development, and configuration management. The key activities involved in most processes are specification, development, validation, and evolution. Specification defines system requirements while development includes design, implementation, and debugging. Validation ensures the system meets requirements through testing. Processes also evolve to adapt to changing needs.
The document discusses architecture refactoring and defines it as changing a software system or process in a way that does not alter external behavior but improves internal structure. It notes that design erosion over time negatively impacts systems and refactoring can help address this. The document outlines some motivations for refactoring like improving structural and non-functional qualities to achieve a more economical, visible, and symmetric design. It also distinguishes refactoring from reengineering and rewriting.
The document provides information on PureShare SingleView IT, an operational metrics solution that consolidates and monitors IT service management metrics. It allows users to automate data collection, visualize current performance status, and monitor key metrics with an early warning system. The solution presents operational metrics in one centralized view, enables proactive management through trend analysis, and automates reports and key performance indicators.
Ian Sommerville, Software Engineering, 9th Edition Ch1Mohammed Romi
The document provides an introduction to software engineering concepts. It discusses what software engineering is, the importance of ethics in software development, and introduces three case studies that will be used as examples throughout the book. Specifically:
[1] It defines software engineering as an engineering discipline concerned with all aspects of software production. Professional and ethical practices are important.
[2] It discusses software engineering ethics and introduces the ACM/IEEE code of ethics for software engineers.
[3] It provides an overview of three case studies that will be referenced in later chapters: an insulin pump system, a patient management system, and a weather station system.
The chapter discusses software evolution, including that software change is inevitable due to new requirements, business changes, and errors. It describes how organizations must manage change to existing software systems, which represent huge investments. The majority of large software budgets are spent evolving, rather than developing new, systems. The chapter outlines the software evolution process and different approaches to evolving systems, including addressing urgent changes. It also discusses challenges with legacy systems and their management.
Cis 2303 lo1 part 1_weeks_1_2 - student verAhmad Ammari
This document outlines the learning objectives and content for a course on systems analysis and design. The course will describe the evolution of software development processes and methodologies, with a focus on structured analysis. It will cover the components of information systems, systems development life cycle models, and the roles and tasks of systems analysts in gathering requirements and designing specifications. The structured analysis approach and systems development life cycle model involve planning, analysis, design, implementation, and support phases to develop high-quality information systems.
Chapter 1- INTRODUCTION TO SYSTEM ANALYSIS AND DESIGN by DEEPA (1).pptxanumayived
This document provides an introduction to system analysis and design. It discusses key concepts like information, information systems, and information system components. It also describes different system development methods including structured analysis, object-oriented analysis, and agile/adaptive methods. Additionally, it explains the system development life cycle and provides examples of each phase for a clinic management system project.
Ais Romney 2006 Slides 18 Introduction To Systems Developmentsharing notes123
The document summarizes the key phases and activities involved in the systems development life cycle. It discusses:
1) The five main phases: systems analysis, conceptual design, physical design, implementation and conversion, and operation and maintenance.
2) The various individuals and groups involved in systems development, including top management, accountants, an information systems steering committee, systems analysts, and computer programmers.
3) How planning, managing change, and ongoing feasibility assessment occur throughout the life cycle.
The document discusses systems development and analysis. It covers the following key points in 3 sentences:
The systems development life cycle involves 5 phases: analysis, conceptual design, physical design, implementation, and operations/maintenance. Planning is important to coordinate projects and ensure consistency, efficiency, and lower costs. A feasibility study analyzes technical, operational, economic, legal, and scheduling feasibility to determine if a project should proceed.
The document describes the six phases of the System Development Life Cycle (SDLC): 1) Preliminary Investigation assesses feasibility and requirements, 2) System Analysis studies the existing system and defines new requirements, 3) System Design develops alternative system designs, 4) System Development builds the new system, 5) System Implementation installs and trains users on the new system, and 6) System Operation and Maintenance involves ongoing evaluation and updates after implementation. Each phase involves specific tasks, tools, and documentation to progress the system through its entire life cycle.
1. What is the purpose of the system development life cycle (SDL.docxcroysierkathey
1. What is the purpose of the system development life cycle (SDLC)? What is meant by Agile Development and iterative development?
2. List and briefly describe the five activities of systems analysis.
3. What are system controls, and why are they not considered part of the users’ functional requirements?
4. Compare/contrast aggregation with composition for a whole part relationship.
5. List the parts or compartments of a fully developed use case description.
6. Explain four types of integrity controls for input forms. Which have you seen most frequently? Why are they important?
7. Describe the key questions that should be asked and answered when a system designer is describing the environment of a system.
8. Describe each of the four metaphors for user interface design.
9. List the components of a DBMS and describe the function of each.
10. Which would be easier to configure and maintain? A vertically partitioned database or a horizontally partitioned database? Explain why.
Grading Rubric for the Assignment #1:
Delivery: Delivered the assignments on time, and in correct format: 25 percent
Completion: Providing a thoroughly develop the document including descriptions of all questions: 25 percent
Understanding: Demonstrating a clear understanding of purpose and writing a central idea with mostly relevant facts, details, and/or explanation: 25 percent
Organization: Paper is well organized based on the APA format, makes good use of transition statements, and in most instances follows a logical progression including good use of symbols, spacing in output: 25 percent
.
This document introduces systems analysis and design. It defines a system as a collection of components that work together to achieve objectives. It describes the main phases of the system development life cycle as preliminary study, feasibility study, detailed study, analysis, design, coding, testing, implementation, and maintenance. Each phase is described in 1-2 sentences. The purpose is to explain the process of developing and maintaining systems through an organized approach.
ERP SYSTEM POST IMPLEMENTATION AUDIT_TRNG_May,2023 - Part-3.pptxRamanaBulusu1
ERP System Post Implementation Audit - This is useful for auditing an ERP system after the implementation. Refer part-1 and part-2 before coming to this part.
The document summarizes the key phases and activities of the system development life cycle, including planning, analysis, design, implementation, and operation/support phases. It describes the objectives of each phase such as determining requirements during analysis or developing detailed designs during design. Project management, documentation, and techniques like prototyping and testing are discussed as important elements that occur throughout the entire development cycle.
Document defect tracking for improving product quality and productivitych_tabitha7
Here are some key HTML tags and attributes:
<p> - Defines a paragraph
<h1>-<h6> - Headings from level 1-6
<strong> - Bold text
<em> - Italicized text
<a href="url"> - Anchor tag for hyperlinks
<img src="image.jpg"> - Image tag
<div> - Defines a division or section
<span> - Inline container for text
<table> - Defines a table
<tr> - Table row
<td> - Table data/cell
<ul> - Unordered list
<ol> - Ordered list
<li> - List item
<form> - Form
The document discusses the system development life cycle (SDLC) in detail. It describes the 8 main steps of SDLC as systems investigation, systems analysis, systems design, programming, testing, implementation, operation, and maintenance. For each step, it provides explanations of the key activities and objectives. The document also covers alternative development methods like prototyping, joint application design, rapid application development, and object-oriented development. Finally, it discusses database management approaches and the advantages of using a database over traditional file-oriented data storage.
The document discusses the system development life cycle (SDLC) which includes 8 stages: systems investigation, systems analysis, systems design, programming, testing, implementation, operation, and maintenance. It provides details on each stage, including the objectives and key activities. Additionally, it discusses alternative methods for systems development like prototyping, joint application design, rapid application development, integrated computer-aided software engineering tools, and object-oriented development.
The document discusses the system development life cycle (SDLC) in detail. It describes the 8 main steps of SDLC as systems investigation, systems analysis, systems design, programming, testing, implementation, operation, and maintenance. For each step, it provides explanations of the key activities and objectives. The document also covers alternative development methods like prototyping, joint application design, rapid application development, and object-oriented development. Finally, it discusses database management approaches and the advantages of using a database over traditional file-oriented data storage.
Software Architecture Standard IEEE 1471vconovalov
This presentation covers the IEEE 1471/4210 Architecture Standard for the Software Intensive System. Following areas such as Stakeholders and their concerns, Architecture Description and System Qualities Attributes were mainly addressed. The audience consisted of Development leads, developers & testers. Hope other disciplines such as Architects and Business Analysts will find it useful as well.
The document provides an overview of IT project management. It discusses systems development, understanding business needs through business process modeling, the roles of various participants in system development including users and specialists. It also covers the systems analysis and design process, guidelines for systems development including developing accurate cost and benefit information, and maintaining flexibility. Project management tasks like defining, planning, scheduling, monitoring and controlling, and reporting are also summarized.
The document discusses the system development life cycle (SDLC), which is a framework that defines tasks performed at each step of the software development process. It consists of 7 phases: planning, system analysis, system design, system development, system testing, system implementation, and system maintenance. The SDLC aims to ensure delivery of high-quality systems, provide strong management control, and maximize productivity.
System analysis and design involves analyzing existing systems or developing new systems. It includes activities like requirements gathering, specification development, design, coding, testing and implementation. The system development life cycle (SDLC) models like waterfall, spiral and incremental-iterative are approaches used for developing systems. Key stages in SDLC include feasibility study, analysis, design, coding, testing and implementation.
The document discusses the key activities and objectives of the systems analysis phase. It describes requirements modeling, data and process modeling, and considering development strategies as the three main activities. The overall objective is to understand the proposed system and build a solid foundation for further development. The analysis identifies business requirements, considers scalability and total cost of ownership. It also discusses modeling tools like UML and FDD that help represent the system, as well as CASE tools used by analysts.
The System Development Life Cycle (SDLC) is a conceptual model used in project management that describes stages in developing an information system project. It includes planning, analysis, design, implementation, and maintenance phases. During planning and analysis, requirements are defined and the system is evaluated. In design, options are considered and blueprints are developed. Implementation involves completing tasks such as testing. Maintenance provides ongoing support and improvements. The SDLC provides an organized process to develop systems efficiently and meet user needs.
CHAPTER 12 Managing Systems
Support and
Security
Chapter 12 describes systems support and security tasks that continue throughout the useful life of the system. In addition to user support, this chapter discusses maintenance, security, backup and disaster recovery, performance measurement, and system obsolescence.
· Explain the systems support and security phase
· Describe user support activities, including user training and service desks
· Define the four types of maintenance
· Explain various techniques for managing systems maintenance and support
· Describe techniques for measuring, managing, and planning system performance
· Explain risk management concepts
· Assess system security at six levels: physical security, network security, application security, file security, user security, and procedural security
· Describe backup and disaster recovery
· List factors indicating that a system has reached the end of its useful life
· Assess future challenges and opportunities for IT professionals
· Develop a strategic plan for career advancement and strong IT credentials
INTRODUCTION
OBJECTIVES
When you finish this chapter, you will be able to:
Managing systems support and security involves three main concerns: user expectations, system performance, and security requirements.
A systems analyst is like an internal consultant who provides guidance, support, and training. Successful systems often need the most support because users want to learn the features, try all the capabilities, and discover how the system can help them perform their tasks. In most organizations, more than half of all IT department effort goes into supporting existing systems.
This chapter begins with a discussion of systems support, including user training and service desks. You will study the four main types of maintenance: corrective, adaptive, perfective, and preventive. You also will learn how the IT group uses maintenance teams, configuration management, and maintenance releases, and you will examine system performance issues and maintenance tools. You will analyze the security system at each of the six security levels: physical security, network security, application security, file security, user security, and procedural security. You will also learn about data backup and recovery issues. Finally, you will learn how to recognize system obsolescence, and about some of the challenges and opportunities you are likely to face as an IT professional.
PREVIEW CASE: Mountain View College Bookstore
Background: Wendy Lee, manager of college services at Mountain View College, wants a new information system that will improve efficiency and customer service at the three college bookstores.
In this part of the case, Tina Allen (systems analyst) and David Conroe (student intern) are talking about operation, support, and security issues for the new system.
Participants:
Tina and David
Location:
Tina’s office, Friday afternoon, March 28, 2014
Project status:
Tina and David successfull ...
HCL Notes and Domino License Cost Reduction in the World of DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
Your One-Stop Shop for Python Success: Top 10 US Python Development Providersakankshawande
Simplify your search for a reliable Python development partner! This list presents the top 10 trusted US providers offering comprehensive Python development services, ensuring your project's success from conception to completion.
In his public lecture, Christian Timmerer provides insights into the fascinating history of video streaming, starting from its humble beginnings before YouTube to the groundbreaking technologies that now dominate platforms like Netflix and ORF ON. Timmerer also presents provocative contributions of his own that have significantly influenced the industry. He concludes by looking at future challenges and invites the audience to join in a discussion.
OpenID AuthZEN Interop Read Out - AuthorizationDavid Brossard
During Identiverse 2024 and EIC 2024, members of the OpenID AuthZEN WG got together and demoed their authorization endpoints conforming to the AuthZEN API
How to Get CNIC Information System with Paksim Ga.pptxdanishmna97
Pakdata Cf is a groundbreaking system designed to streamline and facilitate access to CNIC information. This innovative platform leverages advanced technology to provide users with efficient and secure access to their CNIC details.
TrustArc Webinar - 2024 Global Privacy SurveyTrustArc
How does your privacy program stack up against your peers? What challenges are privacy teams tackling and prioritizing in 2024?
In the fifth annual Global Privacy Benchmarks Survey, we asked over 1,800 global privacy professionals and business executives to share their perspectives on the current state of privacy inside and outside of their organizations. This year’s report focused on emerging areas of importance for privacy and compliance professionals, including considerations and implications of Artificial Intelligence (AI) technologies, building brand trust, and different approaches for achieving higher privacy competence scores.
See how organizational priorities and strategic approaches to data security and privacy are evolving around the globe.
This webinar will review:
- The top 10 privacy insights from the fifth annual Global Privacy Benchmarks Survey
- The top challenges for privacy leaders, practitioners, and organizations in 2024
- Key themes to consider in developing and maintaining your privacy program
CAKE: Sharing Slices of Confidential Data on BlockchainClaudio Di Ciccio
Presented at the CAiSE 2024 Forum, Intelligent Information Systems, June 6th, Limassol, Cyprus.
Synopsis: Cooperative information systems typically involve various entities in a collaborative process within a distributed environment. Blockchain technology offers a mechanism for automating such processes, even when only partial trust exists among participants. The data stored on the blockchain is replicated across all nodes in the network, ensuring accessibility to all participants. While this aspect facilitates traceability, integrity, and persistence, it poses challenges for adopting public blockchains in enterprise settings due to confidentiality issues. In this paper, we present a software tool named Control Access via Key Encryption (CAKE), designed to ensure data confidentiality in scenarios involving public blockchains. After outlining its core components and functionalities, we showcase the application of CAKE in the context of a real-world cyber-security project within the logistics domain.
Paper: https://doi.org/10.1007/978-3-031-61000-4_16
Threats to mobile devices are more prevalent and increasing in scope and complexity. Users of mobile devices desire to take full advantage of the features
available on those devices, but many of the features provide convenience and capability but sacrifice security. This best practices guide outlines steps the users can take to better protect personal devices and information.
Best 20 SEO Techniques To Improve Website Visibility In SERPPixlogix Infotech
Boost your website's visibility with proven SEO techniques! Our latest blog dives into essential strategies to enhance your online presence, increase traffic, and rank higher on search engines. From keyword optimization to quality content creation, learn how to make your site stand out in the crowded digital landscape. Discover actionable tips and expert insights to elevate your SEO game.
Ocean lotus Threat actors project by John Sitima 2024 (1).pptxSitimaJohn
Ocean Lotus cyber threat actors represent a sophisticated, persistent, and politically motivated group that poses a significant risk to organizations and individuals in the Southeast Asian region. Their continuous evolution and adaptability underscore the need for robust cybersecurity measures and international cooperation to identify and mitigate the threats posed by such advanced persistent threat groups.
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
“An Outlook of the Ongoing and Future Relationship between Blockchain Technologies and Process-aware Information Systems.” Invited talk at the joint workshop on Blockchain for Information Systems (BC4IS) and Blockchain for Trusted Data Sharing (B4TDS), co-located with with the 36th International Conference on Advanced Information Systems Engineering (CAiSE), 3 June 2024, Limassol, Cyprus.
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdfMalak Abu Hammad
Discover how MongoDB Atlas and vector search technology can revolutionize your application's search capabilities. This comprehensive presentation covers:
* What is Vector Search?
* Importance and benefits of vector search
* Practical use cases across various industries
* Step-by-step implementation guide
* Live demos with code snippets
* Enhancing LLM capabilities with vector search
* Best practices and optimization strategies
Perfect for developers, AI enthusiasts, and tech leaders. Learn how to leverage MongoDB Atlas to deliver highly relevant, context-aware search results, transforming your data retrieval process. Stay ahead in tech innovation and maximize the potential of your applications.
#MongoDB #VectorSearch #AI #SemanticSearch #TechInnovation #DataScience #LLM #MachineLearning #SearchTechnology
Cosa hanno in comune un mattoncino Lego e la backdoor XZ?Speck&Tech
ABSTRACT: A prima vista, un mattoncino Lego e la backdoor XZ potrebbero avere in comune il fatto di essere entrambi blocchi di costruzione, o dipendenze di progetti creativi e software. La realtà è che un mattoncino Lego e il caso della backdoor XZ hanno molto di più di tutto ciò in comune.
Partecipate alla presentazione per immergervi in una storia di interoperabilità, standard e formati aperti, per poi discutere del ruolo importante che i contributori hanno in una comunità open source sostenibile.
BIO: Sostenitrice del software libero e dei formati standard e aperti. È stata un membro attivo dei progetti Fedora e openSUSE e ha co-fondato l'Associazione LibreItalia dove è stata coinvolta in diversi eventi, migrazioni e formazione relativi a LibreOffice. In precedenza ha lavorato a migrazioni e corsi di formazione su LibreOffice per diverse amministrazioni pubbliche e privati. Da gennaio 2020 lavora in SUSE come Software Release Engineer per Uyuni e SUSE Manager e quando non segue la sua passione per i computer e per Geeko coltiva la sua curiosità per l'astronomia (da cui deriva il suo nickname deneb_alpha).
Full-RAG: A modern architecture for hyper-personalizationZilliz
Mike Del Balso, CEO & Co-Founder at Tecton, presents "Full RAG," a novel approach to AI recommendation systems, aiming to push beyond the limitations of traditional models through a deep integration of contextual insights and real-time data, leveraging the Retrieval-Augmented Generation architecture. This talk will outline Full RAG's potential to significantly enhance personalization, address engineering challenges such as data management and model training, and introduce data enrichment with reranking as a key solution. Attendees will gain crucial insights into the importance of hyperpersonalization in AI, the capabilities of Full RAG for advanced personalization, and strategies for managing complex data integrations for deploying cutting-edge AI solutions.
In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject.
We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup.
Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved.
The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring.
The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise.
By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.
1. SYSTEMS ANALYSIS & DESIGN
PHASE 5
SYSTEMS OPERATION & SUPPORT
Systems Operation and Support
2. PHASE 5
2
SDLC Phases
Phase 5: Systems Operation and Support
Objectives
Provide maintenance and improvements for the
new information system
Support users and help them obtain the most
value from the new system
SYSTEMS ANALYSIS & DESIGN 3E
3. PHASE 5
3
Chapter 12
Systems Operation and Support
SYSTEMS ANALYSIS & DESIGN 3E
4. PHASE 5
4
Objectives
Explain how the systems operation and
support phase relates to the rest of the SDLC
Describe the information center concept and
how it supports user needs
Discuss the three main categories of systems
maintenance
Describe standard maintenance procedures
SYSTEMS ANALYSIS & DESIGN 3E
5. PHASE 5
5
Objectives
Discuss the role of configuration management
in systems operation
Describe the process of capacity planning,
including workload and performance
measurements
Recognize the signs of system obsolescence
SYSTEMS ANALYSIS & DESIGN 3E
6. PHASE 5
6
Introduction
The new system must meet user expectations
and provide support for business objectives
Systems analysts perform maintenance, and
also act as internal consultants to help users
obtain the greatest value from the system
The more a system is used, the more features
and enhancements are requested, and the
more maintenance is required
SYSTEMS ANALYSIS & DESIGN 3E
7. PHASE 5
7
Introduction
Chapter topics
Three types of maintenance: corrective,
adaptive, and perfective
Support techniques include maintenance teams,
configuration management, and maintenance
releases
System performance issues
CASE maintenance tools
Recognizing system obsolescence
SYSTEMS ANALYSIS & DESIGN 3E
8. PHASE 5
Overview of Systems Support and 8
Maintenance Activities
The systems operation and support phase
begins when the system becomes operational
and ends when the system is replaced
SYSTEMS ANALYSIS & DESIGN 3E
9. PHASE 5
Overview of Systems Support and 9
Maintenance Activities
After delivering the system, the analyst must
perform two tasks
Provide guidance and user training
Formal training sessions
Technical support
Creation of a centralized information center
Perform necessary maintenance
Keep the system operating properly
Increase its value to users
SYSTEMS ANALYSIS & DESIGN 3E
10. PHASE 5
10
Support Activities
User training and assistance
Current employees are trained when the new
system is introduced
New employees typically are trained by user
departments, rather than IS staff
If significant changes take place, the IS group
might develop a user training package
Special Help via e-mail or company intranet
Revisions to the user guide
Training manual supplements
Formal training sessions
Click to see Figure 12-1
SYSTEMS ANALYSIS & DESIGN 3E Package
11. PHASE 5
11
Support Activities
Information centers
An information center has three main objectives
To help people use system resources more
effectively
To provide answers to technical or
operational questions
To make users more productive by teaching
them how to meet their own information
needs
An information center also is called a help desk
Click to see Figure 12-2
SYSTEMS ANALYSIS & DESIGN 3E Package
12. PHASE 5
12
Support Activities
Information centers
Typical information center tasks
Show a user how to create a data query or
report
Demonstrate an advanced system feature
Help a user recover damaged data
Offer tips for better operation
Explain an undocumented software feature
Show a user how to write a macro
Explain how to access the company’s
intranet or the Internet
SYSTEMS ANALYSIS & DESIGN 3E
13. PHASE 5
13
Support Activities
Typical information centers tasks
Assist a user in developing a simple database
Answer questions about software licensing
and upgrades
Provide information about system
specifications
Recommend a system solution that integrates
data from different locations
An information center also monitors
performance and provides support
Click to see Figure 12-3
SYSTEMS ANALYSIS & DESIGN 3E Package
14. PHASE 5
14
Maintenance Activities
The overall cost of a system includes the
systems operation and support phase
Costs include fixed operational costs and
maintenance activities
Operational costs are relatively constant,
while maintenance costs vary over time
High costs when system is implemented
Relatively low costs during system’s useful life
High costs near end of system’s useful life
Click to see Figure 12-4
Package
Click to see Figure 12-5
SYSTEMS ANALYSIS & DESIGN 3E Package
15. PHASE 5
15
Maintenance Activities
Operational costs
Supplies
Equipment rentals
Software leases
Maintenance activities
Changing programs, procedures, or
documentation to ensure correct performance
Adapting the system to changing requirements
Making the system operate more efficiently
SYSTEMS ANALYSIS & DESIGN 3E
16. PHASE 5
16
Maintenance Activities
Three types of maintenance
Corrective maintenance
To fix errors
Adaptive maintenance
To add new capability and enhancements
Perfective maintenance
To improve efficiency
SYSTEMS ANALYSIS & DESIGN 3E
17. PHASE 5
17
Maintenance Activities
Corrective maintenance
Diagnoses and corrects errors in the system
Investigation, analysis, design, and testing are
necessary before a solution is implemented
Typically, a user submits a systems request form
with supporting evidence, if necessary
Response depends on the priority of the
request
All maintenance is logged
Click to see Figure 12-6
SYSTEMS ANALYSIS & DESIGN 3E Package
18. PHASE 5
18
Maintenance Activities
Adaptive maintenance
Adds enhancements to the system
An enhancement is a new feature or capability
Adaptive maintenance often is required in a
dynamic business environment
An adaptive maintenance project is like a mini-
SDLC, with similar phases and tasks
Can be more difficult than new systems
development, because of the constraints of an
existing system
SYSTEMS ANALYSIS & DESIGN 3E
19. PHASE 5
19
Maintenance Activities
Perfective maintenance
Involves changing an operational system to
make it more efficient, reliable, or maintainable
Requests for corrective and adaptive
maintenance typically come from users, while
requests for perfective maintenance typically
come from the IS department
Techniques
Reverse engineering tools aid design
analysis
Reengineering tools can be used
interactively to correct errors
Click to see Figure 12-7
SYSTEMS ANALYSIS & DESIGN 3E Package
20. PHASE 5
Managing Systems Operation and 20
Support
Systems operation requires effective
management techniques
Maintenance team
Configuration management
Maintenance releases
SYSTEMS ANALYSIS & DESIGN 3E
21. PHASE 5
Managing Systems Operation and 21
Support
Maintenance team
Consists of systems analysts and programmers
Systems analysts on maintenance work need
Solid background in information technology
Strong analytical abilities
Solid understanding of business operations
Effective interpersonal and communication
skills
Analysis: studying the whole to understand the
individual elements
Synthesis: studying the individual elements to
understand the overall system
SYSTEMS ANALYSIS & DESIGN 3E
22. PHASE 5
Managing Systems Operation and 22
Support
Configuration management
Process for controlling changes in system
requirements
Usually involves three steps
1. The maintenance request
2. Initial action on the request
3. Final disposition of the request
Objectives of configuration management
Manage different versions of the system
Organize and handle documentation
SYSTEMS ANALYSIS & DESIGN 3E
23. PHASE 5
23
TRADEOFF
Should a systems review committee evaluate
maintenance and new systems requests
separately, or together?
Some say “let the dollars go where they will do
the most good, regardless of project type”
Others feel that separate allocations are needed
to protect maintenance projects
All projects draw from the same resource pool,
but IS groups often are organized into separate
teams, and can handle separate projects better
SYSTEMS ANALYSIS & DESIGN 3E
24. PHASE 5
24
A KEY QUESTION
At Brightside Insurance Company, you
organized the IS group into two units — one
for new systems, one for maintenance
Now one of your best people might quit if he
is assigned to the maintenance team
Should you adopt a different policy and allow
voluntary assignments?
If you must make the assignments, what
criteria should you use?
SYSTEMS ANALYSIS & DESIGN 3E
25. PHASE 5
Managing Systems Operation and 25
Support
Maintenance releases
With a maintenance release methodology, all
noncritical changes are held until they can be
implemented at one time
Each new system version is called a release
Numbering systems
Whole number = significant change
After decimal = relatively minor changes or
fixes
There are pros and cons to this approach
SYSTEMS ANALYSIS & DESIGN 3E
26. PHASE 5
26
Managing System Performance
System performance directly affects users
Centralized operations are easier to measure
than complex networks and client/server
systems
Various statistics can be used to assess
system performance
Capacity planning uses operational data to
forecast system capability and future needs
SYSTEMS ANALYSIS & DESIGN 3E
27. PHASE 5
27
Managing System Performance
Performance and workload measurement
Response time
Turnaround time
Throughput
SYSTEMS ANALYSIS & DESIGN 3E
28. PHASE 5
28
Managing System Performance
Response time
Response time is the overall time between a
request for system activity and the delivery of
the response
Response time includes three elements
The time necessary to transmit or deliver the
request to the system
The time the system needs to process the
results
The time it takes to transmit or deliver the
results back to the user
Response time is critical for user satisfaction
SYSTEMS ANALYSIS & DESIGN 3E
29. PHASE 5
29
Managing System Performance
Turnaround time
Turnaround time measures the efficiency of
centralized computer operations, which still are
used for certain tasks, such as credit card
processing
Turnaround time is the amount of time between
the arrival of a request at a computer center and
the availability of the output for delivery or
transmission
SYSTEMS ANALYSIS & DESIGN 3E
30. PHASE 5
30
Managing System Performance
Throughput
Throughput measures the efficiency of the
computer itself
Throughput is the time from the input of a
request to the central processor until the output
is delivered to the system
SYSTEMS ANALYSIS & DESIGN 3E
31. PHASE 5
31
Managing System Performance
Capacity planning
Monitors current activity and performance levels
Anticipates future activity
Forecasts the resources needed to provide
desired levels of service
In capacity planning you can use a technique
called what-if analysis, where you vary one or
more elements in a model to see the effect on
other elements
Click to see Figure 12-8a Package
Click to see Figure 12-8b
SYSTEMS ANALYSIS & DESIGN 3E Package
32. PHASE 5
32
CASE Tools for System Maintenance
A CASE toolkit provides valuable tools for
system evaluation and maintenance, such as
A performance monitor
A program analyzer
An interactive debugging analyzer
A restructuring or reengineering tool
Automated documentation tools
Network activity monitors
Workload forecasting software
SYSTEMS ANALYSIS & DESIGN 3E
33. PHASE 5
33
System Obsolescence
A system becomes obsolete when its
functions are no longer required by users or
when the platform becomes outmoded
Typical signs of obsolescence
Adaptive and corrective maintenance is
increasing steadily
Operational costs or execution times are
increasing rapidly, and routine perfective
maintenance does not reverse the trend
SYSTEMS ANALYSIS & DESIGN 3E
34. PHASE 5
34
System Obsolescence
Typical signs of obsolescence
A software package is available that provides
the same or additional services faster, better, and
less expensively
New technology offers a way to perform the
same or additional functions more efficiently
Maintenance changes or additions are difficult
and expensive to perform
Users request significant new features to support
business requirements
Click to see Figure 12-9 Package
Click to see Figure 12-10
SYSTEMS ANALYSIS & DESIGN 3E Package
35. PHASE 5
35
SOFTWEAR, LIMITED
Status report: in mid-December 1999, the
payroll package and the ESIP system both are
operating successfully and SWL users are
satisfied
Corrective maintenance has been performed
Printing and alignment problems were resolved
Adaptive maintenance has been requested
Human resources department wants to develop
an annual employee benefits statement, and add
additional ESIP deduction choices
SYSTEMS ANALYSIS & DESIGN 3E
36. PHASE 5
36
SOFTWEAR, LIMITED
New developments
Pacific Software announced the latest version of
its payroll package, which supports integration
of payroll and human resources functions
SWL decides to investigate the possibility of a
human resources information system (HRIS)
After a preliminary investigation, IS staff
recommends that SWL upgrade to the new
payroll package and study the development of a
company-wide human resources system
SYSTEMS ANALYSIS & DESIGN 3E
37. PHASE 5
37
SOFTWEAR, LIMITED
The future
The business environment is changing rapidly
SWL must investigate new information
management technology constantly
At this point, the systems development life cycle
for SWL begins again
SYSTEMS ANALYSIS & DESIGN 3E