System Analysis and Design Concepts

System Analyst

• A system analyst serves as an agent of change by advocating for the implementation of information systems
• System analyst needs to consider the user's needs and address the changes in the organization when implementing new systems
• System analyst relies on several sources of knowledge to determine new requirements for an application system

System Analysis and Design

• Rose and Marie disagree on the starting point of analyzing requirements for an existing system
• Rose wants to start with enumerating the inputs for the system
• Marie wants to start with the output of the system
• They can settle the disagreement by combining both approaches, starting with either input or output, then moving to the other
• Both inputs and outputs are crucial for understanding the system

Time of the Day Pattern

• Jose, the analyst, suggests the standard 12-hour format for time representation, e.g., 12:25 PM
• Mari, the programmer, suggests using the number of seconds since midnight to represent time
• To resolve the disagreement, they should consider which format best aligns with the company's needs and existing systems
• Consider factors such as ease of interpretation, consistency with other systems, data storage, and processing requirements

Prototyping

• Prototyping is a systems development technique used to create a working model of a system
• This allows users to interact with the system and provide feedback
• There are two main types of Prototyping, Type I & Type II
• Type I Prototype: Develops a prototype and then uses it as the operational system
• Type II Prototype: Prototype is used as the basis for coding the operational system
• Advantages of Prototyping:
  • Improved communication between the analyst and the user
  • The analyst can better determine the user's needs
  • The user is more actively involved in the development process
  • Less time spent by the programmer and the user in development
  • Implementation is easier as the user knows what to expect
• These benefits reduce development costs and enhance user satisfaction with the delivered system

CASE Tools

• CASE (Computer Aided Software Engineering) tools help improve analyst productivity and enhance communication between analysts and users
• Different types of CASE tools include:
  • Diagramming tools
  • Computer display and report generators
  • Analysis tools
  • Repository
  • Documentation generators
  • Code generators
• Examples of CASE tools include:
  • Microsoft Project
  • Microsoft Visio
  • FourGen®
  • System Architect®
  • Visible Analyst®
  • IBM’s Rational Software Architect

UML (Unified Modeling Language)

• UML is a standard language used by systems analysts to specify, visualize, and construct information systems
• It builds on the semantics and notations of leading object-oriented techniques
• UML includes various techniques and notations:
  • Use Cases: Represent the functional requirements of the system
  • Class diagrams: Show the static structure of data and the operations that work on the data
  • State diagrams: Describe complex models of how objects change their condition in response to events
  • Sequence diagrams: Represent dynamic models of interactions between objects

Agile Methods

• Agile methods are modern development methodologies that emphasize flexibility and rapid response to change
• Contrast with structured analysis, which uses a traditional, more rigid approach
• Agile methods develop a program incrementally by creating prototypes and continuously adapting them to user requirements
• Characteristics of Agile Methodology:
  • Short iterative cycles with extensive testing
  • Active user involvement in establishing, prioritizing, and verifying the system's requirements
  • Small teams of experienced, talented programmers

Agile Manifesto

• The Agile Manifesto outlines a set of principles for agile development
• It stresses a team-based culture
• Some widely accepted agile methodologies include:
  • Extreme Programming
  • Scrum
  • RUP (Rational Unified Process)
  • Kanban

System Development Tools and Techniques

• System development tools and techniques are used in software development to improve routine processes
• Benefits:
  • Improved communication: Clear communication between developers and users
  • Enhanced productivity: Streamline the development process, allowing for faster and more efficient work
  • Reduced errors: Detect and correct errors early in the development process
  • Improved quality: Ensure high-quality software solutions.

Post-Test Analogy Questions

• Question 1: Systems analysis: What :: System Design: How
• Answer 1: (b) What: The relationship is that system analysis defines "what" the system should do, while system design defines "how" it will be implemented.
• Question 2: DSS: Effectiveness oriented :: MIS: __________
• Answer 2: (a) Efficiency oriented: DSS (Decision Support Systems) are effectiveness oriented.
• Question 3: DSS: ______________:: EIS: talks about the future
• Answer 3: (a) Talks about the past: DSS focus on present problems, while EIS (Executive Information Systems) focus on future trends.
• Question 4: DSS: senior managerial levels :: MIS: _____________
• Answer 4: (b) Middle managerial levels: DSS cater to senior managers, making decisions about long-term strategy. MIS (Management Information Systems) are geared towards middle managers.
• Question 5: MIS: analytical capacity :: DSS:_________________
• Answer 5: (c) Analytical and Modeling Capacity: MIS provide analytical capabilities, while DSS go further with modeling and simulation to help analyze data.
• Question 6: MIS: ______________:: DSS: support ill-structured decisions
• Answer 6: (b) relatively structured decisions: MIS support relatively structured decisions, while DSS are designed to support ill-structured decisions.
• Question 7: System planning: define problem :: system analysis:_________
• Answer 7: (a) Conduct investigation: System planning defines the problem. System analysis investigates and gathers information about the problem.
• Question 8: Waterfall Model: _________:: Spiral Model: ineffective for small project
• Answer 8: (a) inappropriate for the Long-term projects: The Waterfall Model is inappropriate for long-term projects.
• Question 9: Waterfall Model: High degree of risk :: Agile Model:_________
• Answer 9: (b) Low degree of risk: The Waterfall Model has a high degree of risk, which relates to the high commitment to completing each phase before moving to the next. Agile Models are less risky, allowing adjustments as development progresses

Explore the roles and responsibilities of system analysts in implementing information systems. This quiz discusses various approaches to analyzing system requirements and the importance of both inputs and outputs in understanding system functionality. Test your knowledge on these fundamental concepts of system analysis.