Information Systems Analysis and Design

Study Notes

A complex organizational process used to develop and maintain computer-based systems.
Involves a team of business and systems experts.

The organizational role most responsible for analyzing and designing information systems.

1950s: Focused on efficient automation of existing processes.
1960s: Procedural third-generation languages (3GL) emerged, leading to faster and more reliable computers.
1970s: Systems development evolved towards an engineering discipline.
1980s: Breakthroughs with 4GL, CASE tools, and object-oriented methods.
1990s: Emphasized system integration, GUI applications, client/server platforms, and the internet.
The New Century: Web application development, wireless PDAs, smartphones, component-based applications, per-use cloud-based application services.

A standard, organization-specific process that outlines the steps involved in analyzing, designing, implementing, and maintaining information systems.

A traditional methodology used to develop, maintain, and replace information systems.

Planning: Identifying, analyzing, prioritizing, and arranging an organization's total information system needs.
Analysis: Studying and structuring system requirements.
Design: Transforming a recommended solution into logical and physical system specifications.
- Logical Design: Describing all functional features of the system chosen for development in analysis independently of any computer platform.
- Physical Design: Transforming the logical specifications from the logical design into technology-specific details for programming and system construction.
Implementation: Coding, testing, installing, and supporting the information system within the organization.
Maintenance: Systematically repairing and improving an information system.

Ignores feedback and locks in design specifications even when conditions change, leading to inflexible solutions.
Limited user involvement, restricting their input to the requirements phase.
Excessive focus on milestone deadlines, compromising sound development practices.

CASE Tools: Software that helps with the design and development of information systems.
Agile Methodologies: Focus on short, iterative cycles of development, emphasizing adaptation, people, and self-adaptive processes.
eXtreme Programming (XP): A specific agile methodology utilizing short development cycles, automated tests, two-person programming teams, and tightly integrated coding and testing.

Diagramming Tools: Enable graphical representation of systems.
Computer Displays and Report Generators: Help prototype the "look and feel" of systems.
Analysis Tools: Automatically check for consistency in diagrams, forms, and reports.
Central Repository: Provides integrated storage of diagrams, reports, and project management specifications.
Documentation Generators: Standardize technical and user documentation.
Code Generators: Automate the generation of programs and database code directly from design documents, diagrams, forms, and reports.

Motivated by the recognition that software development is fluid, unpredictable, and dynamic.
Emphasizes three key principles:
- Adopting an Adaptive Approach: Focusing on flexibility and adjusting to changes in requirements.
- Prioritizing People Over Roles: Emphasizing team collaboration and individual expertise.
- Embracing Self-Adaptive Processes: Continuously evaluating and improving processes based on experience and feedback.

When projects involve:
- Unpredictable or dynamic requirements.
- Responsible and motivated developers.
- Customers who understand the process and are willing to participate.

A more extreme version of Agile methodologies known for its:
- Short, incremental development cycles.
- Automated tests.
- Emphasis on two-person programming teams for pair programming.
- Integration of coding, testing, listening, and designing.