Systems Engineering Methodolog Assessing Project Feasibility
Read the following:
You are the Systems Analyst assigned to the ACME Web Application design project. The ACME Web Application will be designed to run the ACME online college's book store in its final delivery. The ACME book store provides student and faculty with digital text books for sale. You as the Systems Analyst should start structuring gathered requirements through conceptual data modeling for a better understanding of the requirements.
Considerations: The context diagram represents the major entities/components at a high level and a general overview of a system with the main entity/component annotated with a zero (0). The level-0 diagram is the context diagram decomposed at the next detail level and annotates entities/components in order of data-flow and processes operation, for example as 1.0, 2.0, 3.0 and etc. as applicable.
Develop a context and level-0 diagram that represents the ACME web book store that includes data flow, data store, process, and source/sink as applicable and at the appropriate diagram level.
The level-0 diagram book store has "only" four decomposed entities/components.
The components for both the context/ level-0 diagrams are described below.
- Student/Faculty/Source (Context and decomposed level-0 diagrams)
- Bookstore (Context and decomposed level-0 diagrams)
- Order (Context diagram and not decomposed)
- Receive order and transform is the interface with the source and receives updates from shopping cart (1.0, decomposed level-0 diagram)
- Update text book sold, this is a file (2.0, decomposed level- 0 diagram)
- Update Inventory, this is the main file and it also stores digital text books (3.0, decomposed level-0 diagram)
- Shopping Cart, receives information from inventory file, facilitates receipt and download of text book (4.0, decomposed level-0 diagram)
- Temporary User/System Messages (notification from shopping cart to notify source of receipt and download of text book).
Using your level-0 diagram, develop an E-R diagram annotating your level-0 diagram entities with their "Cardinality" and dependency between entities and their relationships that describes minimum and maximum cardinality.
For simplicity, use "only" a single line to connect the entities in representing binary and ternary relationships as applicable and the format of 0:0 and 0:0 from our week 6 video 3 discussion to show cardinality of the entities. An example of cardinality maybe one employee works for zero (0) to one (1) departments and a department has (1) to many (M) employees working for it represented as 0:1 and 1:M.