“The most common format used for data modeling is entity-relationship (E-R) diagramming. A similar format used with object-oriented analysis and design methods is class diagramming, which is included in a special section at the end of this chapter on the object-oriented development approach to data modeling. Data models that use E-R and class diagram notations explain the characteristics and structure of data independent of how the data may be stored in computer memory. A data model is usually developed iteratively, either from scratch or from a purchased data model for the industry or business area to be supported. Information system (IS) planners use this preliminary data model to develop an enterprise-wide data model with very broad categories of data and little detail. Next, during the definition of a project, a specific data model is built to help explain the scope of a particular systems analysis and design effort. During requirements structuring, a data model represents conceptual data requirements for a particular system. Then, after system inputs and outputs are fully described during logical design, the data model is refined before it is translated into a logical format (typically a relational data model) from which database definition and physical database design are done. A data model represents certain types of business rules that govern the properties of data. Business rules are important statements of business policies that ideally will be enforced through the database and database management system ultimately used for the application you are designing. Thus, you will use E-R and class diagramming in many systems development project steps, and most IS project members need to know how to develop and read data model diagrams. Therefore, mastery of the requirements structuring methods and techniques addressed in this chapter is critical to your success on a systems development project team.” (Modern Systems Analysis and Design, 8th ed, Joseph Valacich)
Objectives:
- explain the role of conceptual data modeling in the overall analysis and design of an information system;
- describe the information gathering process for conceptual data modeling;
- describe how to represent an entity-relationship model and be able to define the terms: entity type, attribute, identifier, multivalued attribute, and relationship;
- distinguish among unary, binary, and ternary relationships as well as associative entities, providing an example of each;
- define supertypes and subtypes, showing how to represent these entity types with entity-relationship diagramming notation;
- define four basic types of business rules in a conceptual data model; and
- explain the role of prepackaged database models (patterns) in data modeling.
Topics:
From Modern Systems Analysis and Design:
8. Structured System Data Requirements
8.1. Conceptual Data Modeling
8.1.1. E-R Diagraming
8.1.2. Super/Sub Types
8.1.3. Business Rules
8.1.4. Databases
From CISA:
3.1. System Development Methodologies
SDLC Phases
3.1.1.1. Acquisition
3.1.1.1.1. Design
3.3.3.3.2.3. Entity Relationship Diagrams
From Secure Software Design
1.9. SDLS and SSD
1.9.1. Incident Response Plan
1.9.2. Final Security Review
1.9.3. Incorporating OWASP and MS SDLC
In this unit, plan to:
- Participate in the class discussion thread
- Read the assigned topics in CISA
- Read the assigned readings in Secure Software Design
- Read chapter 8 in Modern Systems Analysis and Design