Introduction To Systems Analysis And Design

Introduction To Systems Analysis And Designtrident Universitye Bitm426

Draw an FDD of the portal system website for Trident University. Your FDD must consist of 3 levels. Write your assumptions, if any. Draw a context diagram and a diagram 0 DFD that represents the registration system at your school or an imaginary school. Next, you draw a Level 1 DFD exploding the students’ record external entity (agent) and decompose it into processes, data stores, and data flows, using the symbols in Figure 2-10.

Paper For Above instruction

Introduction

Systems analysis and design are fundamental processes in the development of information systems that meet organizational needs effectively. In this paper, I present detailed data flow diagrams (DFDs) and a functional decomposition diagram (FDD) for the Trident University portal and registration system. The diagrams aim to clarify how data moves within these systems, external interactions, and the internal structure of processes, providing valuable insights for system development, enhancement, or redesign. Assumptions made during the modeling process are also discussed.

Part 1: Functional Decomposition Diagram (FDD) of the Trident University Portal System

The FDD provides a hierarchical view of the system's functions. The top level (Level 0) depicts the overall view, showing external entities such as students, faculty, administration, and external systems like payment gateways. Level 1 expands these functions into major processes including student registration, course management, grade submission, and authentication. At Level 2, further decomposition refines each process into detailed sub-processes, such as login, course selection, registration approval, and notification services. This layered approach improves understanding of the portal's functionalities and facilitates modular development.

Assumptions for the FDD include: The system primarily handles online interactions; all data inputs are entered through web interfaces; and external entities like payment providers are considered as black-box systems that interact with the portal via secure data flows.

Part 2: Context Diagram and Diagram 0 DFD of the Registration System

The context diagram illustrates the highest-level view of the registration system at Trident University. External entities include students, instructors, administrative staff, and possibly third-party systems like payment processors. Data flows represent registration requests, student records, course catalogs, and approval notifications. The registration system acts as a central processing unit, managing these data exchanges to facilitate enrollment processes.

Diagram 0 DFD further decomposes this system into core processes such as "Receive Registration Request", "Validate Student Data", "Assign Courses", and "Generate Confirmation". Data stores include "Student Records", "Course Offerings", and "Registration Files". Data flows connect these processes and stores, capturing the movement of registration data, student information, and system outputs.

Part 3: Level 1 DFD Expanding the Students’ Record External Entity

Under the Level 1 DFD, the "Students" external entity is exploded into several processes like "Student Login", "Update Student Record", and "View Student Record". Data flows include "Login Credentials", "Updated Records", and "Student Queries". Data stores such as "Student Personal Info", "Enrollment Status", and "Academic History" are linked to these processes, providing a comprehensive map of internal data management.

The representation adheres to symbols from Figure 2-10, indicating processes, data stores, external entities, and data flows with arrows denoting data direction. This detailed view assists in understanding how student-related data interacts within the registration subsystem and supports system requirements analysis.

Conclusion

This analysis using layered DFDs and an FDD offers a clear visualization of Trident University’s portal and registration systems. The diagrams facilitate better communication among stakeholders, assist in identifying system requirements, and serve as blueprints for system development or improvement. Proper modeling with suitable software tools like yEd ensures clarity and accuracy, essential for effective system design.

References

  • Satzinger, J. W., Jackson, R. B., & Burd, S. D. (2014). Chapter B: The traditional role in requirements. Boston, MA: Course Technology Cengage Learning.
  • Madigson, E. (2016). Data and process modeling part I & II. [Video files]. Retrieved from Madigson, E. (2016). Introduction to systems analysis and design part 2.
  • Burrows, W. (2015). Data flow diagrams examples: Food ordering system. Retrieved from TutorialPoints.
  • LucidChart. (2018). What is an entity relationship diagram. Retrieved from LucidChart.
  • Ambler, S. (2018). UML 2 sequence diagrams: An agile introduction. Agile Modeling. Retrieved from Ambler, S. (2018). Examples of business use case diagrams.
  • Cook, P. (2014). Introduction to structure charts. [Video file]. Retrieved from Cook, P. (2014).
  • Kalodikis, C. (2017). Introduction to structure charts. [Video file]. Retrieved from Kalodikis, C. (2017).
  • yWorks. (2011). yEd graph editor in 90 seconds. [Video file]. Retrieved from yWorks.
  • Dia Diagram Editor. (n.d.). [Open source diagramming software]. Retrieved from Dia Diagram Editor site.
  • Additional scholarly resources on system analysis and design principles, diagramming standards, and case studies on student registration systems.

Related Assignments