SIA - Module 5

Software Engineering Methods

Structured methods that evolved in the 1970s to analyze manual processes and automate them using diagrams and modular program design.

Data Flow Diagram (DFD)

A diagram that shows how data moves through a system, used to document manual and automated processes.

Functional Decomposition Diagram (FDD)

A diagram that breaks down a system into smaller, manageable functions or processes.

Structure Chart (SC)

A diagram showing the hierarchical structure of a program and how modules interact.

Data Maintenance Chaos

A problem caused by redundant versions of data stores created by different versions of the same process.

Relational Model

A database model developed by Edgar Codd using mathematical set theory; foundation of modern relational databases.

Relational Database Management System (RDBMS)

A database system based on the relational model; early examples include IBM DB2 and Oracle RDBMS.

Normalization

A database design process that eliminates redundant data and ensures consistency.

Information Engineering (IE)

A business-driven, rigorous engineering discipline for data and process modeling; developed by Clive Finkelstein and popularized by James Martin.

Object-Oriented (O-O) Development

A programming and modeling approach that organizes software around objects and classes; uses UML diagrams.

Unified Modeling Language (UML)

A standardized modeling language for object-oriented development, created by Grady Booch, James Rumbaugh, and Ivar Jacobson.

Rational Corporation

A company founded to develop UML tools; later acquired by IBM in 2003.

Enterprise Architecture (EA)

A strategic framework for aligning business processes, data, and technology across an entire organization.

Strategy A (Top-Down EA Implementation)

A rigorous, detailed approach that produces a fully normalized enterprise data model for organization-wide integration.

Strategy B (Selective EA Based on ROI)

An approach that evaluates legacy systems and builds an ROI-based business case before implementing EA.

Strategy C (3-Month Incremental Builds)

A progressive EA approach that delivers high-priority components in short, strategic increments.

Strategic Planning Statements

Mission, vision, values, goals, objectives, issues, KPIs, and strategies identified during strategy analysis.

Priority Area Experts

Managers and business experts responsible for implementing key parts of the strategic plan.

Tactical Business Planning Statements

Detailed plans created in a workshop to execute the organization’s strategic goals.

Data Mapping

A collaborative process where business and IT identify required data and entities for integration.

Strategic Model

A high-level enterprise data model created during facilitated modeling sessions to support EA implementation.