Create DFD (3.1), Use case & Process model (3.2), and ERD (3.3) for the t-shirt online shopping system.

Transcribed Image Text:

In this phase, you will design and communicate an appropriate technical solution that aligns with your context, needs, and information architecture. You must align your logical design with functional and non-functional requirements at operational and strategic levels. Non- Functional requirements are requirements or constraints posed by the client or by the problem that do not relate directly to the functions of the system. 3.1 Data Flow Diagrams Translate the system structure into data flow diagrams (DFDs) by drawing the high- level and primitive DFDs: (a) Contextual diagram, (b) Level-0 diagram; and (c) Level- 1 diagrams for the major activities in level-0. Level-1 diagram results from decomposition of the Level-0 diagram. Remember to label ALL processes, datasets, and data arrows (inflow and outflow of data). Your DFDs should be contextualized with a project dictionary (Table) that briefly defines each component of DFDs (processes, data-sets, source, and sinks). Consistency in labeling is crucial here. NOTE: 'Verify' your models with your client/potential users before submission. NOTE: you can use Visio (PC Only), or Lucidchart (cloud-based, recommended) to develop DFDs. 3.2 Use Cases and Process Models You need to draft Use Case diagrams along with their Narratives as the first step toward process modeling. In this section, you should provide: (a) The top-level Use Case diagram from your end-users' perspective (primary actor). (b) Use Case Narratives for your diagrams. Your Use Case defines why end-users interact with your system and what needs to happen (functions) upon interactions in order to address the end-users' requests. Conclude this section with the key functional requirements. You may list system functionalities such as user authentication, user profile creation/update, checking inventory, creating shipping slip, sending notifications, ranking recommendations, visualizing data, sending email reminder etc. After completion, you have to review your DFDs with your teammates to ensure you have consistent documents in terms of requirements and labels. NOTE: Please include all necessary secondary actors, major activities (from DFD Level-1s) that satisfy the end-users' main objective. NOTE on Basic Flow in Use Case Narrative: The optimal or normal (Happy Path) flow of events. The basic flow of events should describe the events that walk through a successful scenario. The basic flow should not include 'if scenarios". In this phase, you will design and communicate an appropriate technical solution that aligns with your context, needs, and information architecture. You must align your logical design with functional and non-functional requirements at operational and strategic levels. Non- Functional requirements are requirements or constraints posed by the client or by the problem that do not relate directly to the functions of the system. 3.1 Data Flow Diagrams Translate the system structure into data flow diagrams (DFDs) by drawing the high- level and primitive DFDs: (a) Contextual diagram, (b) Level-0 diagram; and (c) Level- 1 diagrams for the major activities in level-0. Level-1 diagram results from decomposition of the Level-0 diagram. Remember to label ALL processes, datasets, and data arrows (inflow and outflow of data). Your DFDs should be contextualized with a project dictionary (Table) that briefly defines each component of DFDs (processes, data-sets, source, and sinks). Consistency in labeling is crucial here. NOTE: 'Verify' your models with your client/potential users before submission. NOTE: you can use Visio (PC Only), or Lucidchart (cloud-based, recommended) to develop DFDs. 3.2 Use Cases and Process Models You need to draft Use Case diagrams along with their Narratives as the first step toward process modeling. In this section, you should provide: (a) The top-level Use Case diagram from your end-users' perspective (primary actor). (b) Use Case Narratives for your diagrams. Your Use Case defines why end-users interact with your system and what needs to happen (functions) upon interactions in order to address the end-users' requests. Conclude this section with the key functional requirements. You may list system functionalities such as user authentication, user profile creation/update, checking inventory, creating shipping slip, sending notifications, ranking recommendations, visualizing data, sending email reminder etc. After completion, you have to review your DFDs with your teammates to ensure you have consistent documents in terms of requirements and labels. NOTE: Please include all necessary secondary actors, major activities (from DFD Level-1s) that satisfy the end-users' main objective. NOTE on Basic Flow in Use Case Narrative: The optimal or normal (Happy Path) flow of events. The basic flow of events should describe the events that walk through a successful scenario. The basic flow should not include 'if scenarios".

Answer rating: 100% (QA)

Customer Management Shopping Management New Product Registered Payment Mode ... View the full answer