PROJMANG_MIDTERM

• Systems Analysis and Design (SAD)

  • Defining the purpose and functionalities of a system
  • Detailing the implementation of each component of the system
• System Analyst


  The key person who analyzes business needs based on organizational functions, requirements, identifies opportunities for improvement, solves problems, and designs systems to implement these ideas
• Roles of the System Analyst

  • Consultant
  • Supporting expert
  • Agent of change
• Qualities of the Systems Analyst

  • Problem solver
  • Communicator
  • Strong personal and professional ethics
  • Self-disciplined and motivated
• System boundary


  Delineates the system from its environment, where inputs and outputs occur
• Automation boundary


  Separates the automated and manual parts of the system
• System Components


  • Hardware
  • Software
  • Data
  • Processes
  • People
• Hardware


  Physical layer of the system. Includes workstations, servers, networks, telecommunication equipment, cables, input and output devices, among others
• Software


  • System software
  • Application software
• System software


  Manages hardware components, such as operating systems, security software, utility programs, and network operating systems (NOS)
• Application software


  Supports daily business functions and manages user information needs, including enterprise applications like order processing and payroll systems
• Data


  Raw material transformed into useful information. Stored in tables. Specific information extracted by linking tables
• Processes


  Serve as building blocks of a system. Define the tasks and business functions that users perform to achieve specific results. Represent actual day-to-day business operations
• People


  • Internal users
  • External users
• Internal users


  Administrators, managers, technicians, sales staff, and corporate officers
• External users


  Customers tracking orders on the company's website and suppliers using the customer's system to plan manufacturing schedules
• Systems Development Tools and Techniques

  • Modeling
  • Prototyping
  • Computer-Aided Systems Engineering (CASE) Tools
• Modeling


  • Business or Requirements model
  • Data model
  • Object model
  • Network model
  • Process model
• Prototyping


  Tests system concepts and examines input, output, and user interface before final decisions
• Pros of Prototyping


  • Accelerates development process
  • Allows quick user interaction
  • Identifies needed changes and refines requirements
• Cons of Prototyping


  • May lead to premature decisions before thorough understanding of business issues
  • Initial design decisions may be poor
• Computer-Aided Systems Engineering (CASE) Tools


  Known as computer-aided software engineering, utilizes powerful software (CASE tools) to aid systems analysts in developing and maintaining systems. Provides a framework for systems development and supports various design methodologies
• Methodologies in the Development of Systems

  • Bottom-Up
  • Top-Down
  • Integrated Approach
  • Structured Analysis
  • Object-oriented (O-O) Analysis
  • Joint Application Development (JAD) and Rapid Application Development (RAD)
• Bottom-Up


  Uses the organization's operational level as the base for the system. Begins with the operational level as the core of the organization. Supplies information requirements of intermediate and management levels through operational level data processing stages. Initially prepares future system needs and planning for the operational level
• Top-Down


  Utilizes the organization's management level as the system base. Management defines requirements and system goals
• Integrated Approach


  Combines Bottom-Up and Top-Down methods for maximum benefit. Top-Down method used for initial planning. Bottom-Up approach employed for subsystem planning, ensuring proper alignment with operational level requirements
• Structured Analysis


  Involves techniques and graphical tools for creating user-understandable system specifications. Uses process models to describe systems graphically. The advent of CASE tools in the 1990s facilitated the development and modification of graphical structured analysis and structured design (SASD) models
• Object-oriented (O-O) Analysis


  Combines data and processes into objects. Uses object models to represent data, behavior, and interactions among objects. Describing objects and methods supports business operations and enables the design of reusable components for faster implementation and reduced development costs
• Joint Application Development (JAD) and Rapid Application Development (RAD)


  • JAD: Structured approach to requirements determination and design reviews. Team-based fact-finding involving users, managers, and analysts. Structured meetings over several days to review system requirements
  • RAD: Designed to significantly reduce the time for system design and implementation. Relies heavily on extensive user involvement
• System Development Life Cycle (SDLC)

  • Waterfall Model
  • Alternative Model
• Waterfall Model


  Results of each phase flow sequentially into the next. Adjacent phases interact, depicted by dotted lines. Advantages: Clear progress tracking, effective project management, clarity for engineers on tasks. Problems: Costly to accommodate changes once underway, inflexible partitioning into distinct stages makes adapting to changing requirements difficult. Best suited for well-understood requirements
• Alternative Model


  Planning, analysis, and design interact continuously, followed by implementation and operation and support. Interactive model reflecting real-world practice and ongoing dialogue among users, managers, and systems developers
• 5 Steps in SDLC

  • Systems planning
  • Systems analysis
  • Systems design
  • Systems implementation
  • Systems operation, support, and security
• Systems Planning


  Identifies the nature and scope of the business opportunity or problem. Begins with a systems request describing problems or desired changes. Involves a preliminary investigation determining feasibility based on operational, technical, economic, and time factors, which influences the entire development process
• Systems Analysis


  Aims to construct a logical model of the new system. Answers questions regarding system users, functions, and usage. Involves investigating current systems, identifying improvements, and conceptualizing the new system. Begins with requirements modeling, exploring business processes and documenting system necessities through fact-finding techniques like interviews, surveys, and observation. Produces the System Requirements Document, outlining management and user requirements, costs, benefits, and alternative development strategies
• Systems Design


  Determines system operation, including hardware, software, network infrastructure, user interface, forms, reports, programs, databases, and files. Aims to create a blueprint meeting documented requirements. Identifies outputs, inputs, and processes, involving manager and user participation to prevent misunderstandings. Produces the system design specification. Divided into Logical Design, focusing on business aspects, and Physical Design, specifying technical requirements
• Systems Implementation


  Construct new system. Write, test, and document programs. Conduct file conversion. Train users, managers, and IT staff. Perform system evaluation to ensure proper operation and alignment with expected costs and benefits
• Systems Operation, Support, and Security

  New system supports operations. Maintenance changes correct errors or meet requirements. Enhancements increase system capability by provide new features and benefits. The objective during this phase is to maximize return on the investment. Security controls safeguard the system from both external and internal threats. A well-designed system will be secure, reliable, maintainable, and scalable so it can expand to meet new business requirements and volumes. After several years of operation, systems need extensive changes. SDLC ends with system replacement
• Systems Development Guidelines


  • Stick to an overall development plan
  • Involve users throughout the process, especially when identifying requirements
  • Listen closely to users' needs
  • Create a timetable with major milestones for project review
  • Establish interim checkpoints to ensure schedule adherence
  • Remain flexible as development progresses
  • Provide accurate cost and benefit information to managers at the start of each phase
• Business Case


  Outlines the rationale for a proposal, offering clear project description, justification, and financial impact estimation